Skip to content
James Heselden edited this page Feb 3, 2025 · 3 revisions

Envirionment Map Access

As detailed in ROS2-Package#access, the system uses a bash file named Environment.sh to handle accessing contained maps.

The environment.sh file contains exports for each of the maps contained within the template, with check conditions to verify the files are contained correctly.

This file is stored in the config directory.

This file exports each file path and sources the properties.sh file.

Property Definitions

For additional information about the site, the properties.sh file can be used.

This file can contain information such as:

  • site name
  • site ownership
  • site foundation

Included maps by Version 1.0.1

In the latest version, the following maps are included and considered:

  • location
    • data.yaml
    • fence.kml
    • satellite.png
  • metric
    • map/costmap.yaml
    • map/costmap.pgm
    • map/costmap.png
    • map/costmap-tp.png
    • map/costmap.kmz
  • topological
    • network.tmap.yaml
    • network.tmap2.yaml
    • navgraph.yaml
    • osm.kml
    • interactions.kml
    • network.kml
  • world
    • fiducial_markers.yaml
    • gazebo.world.xml
    • openrmf.building.yaml
    • known_obstacles.yaml
    • custom_models/

As detailed in PR#4, version 1.0.2 will contain a collection of new map formats. Systems/maps planned for inclusion under this version:

  • metric
    • octomap.yaml
  • topological
    • ANYBotics topological map
  • world
    • POI.tmap2.yaml
    • Simio DES Digital Twin

Heirarchy

The heirarchy is divided up based on information type, categorising into: Location, Objects, Occupancy, and Topology.

More about this can be found HERE