open-rmf / open-rmf/next_gen_prototype
[Feature request]: Add `map_name` to `Region`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 10
- Forks
- 9
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
Description
Currently Region does not define the map name. In the event robots have different maps it is not possible to distinguish between regions. On the other hand GraphElementKey does define a "map" field. Should we consider adding a map field to the target Region message?
Implementation Considerations
No response
Alternatives
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read rmf_prototype_msgs/msg/Region.msg alongside rmf_prototype_msgs/msg/GraphElementKey.msg, then trace how Region is defined and used. Resolve whether Region should carry the existing map identifier and confirm that the resulting message can distinguish regions from different maps.
Written by the indexing model from the issue text.
Assessment
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100