Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map server design for multi-layer maps, multiple map sources, etc. #392

Closed
3 tasks
gbiggs opened this issue Nov 30, 2018 · 1 comment
Closed
3 tasks

Map server design for multi-layer maps, multiple map sources, etc. #392

gbiggs opened this issue Nov 30, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@gbiggs
Copy link

gbiggs commented Nov 30, 2018

After Crystal is out, there are a number of potential improvements to the functionality of the map server that we can make. Some random ideas of things that could be useful are:

  • Allowing a single map server to provide multi-layered maps, with the maps overlaying each other in space and providing different information (one example given is traffic flows to allow robots to avoid crowded areas).
  • Allow a map server to load a map from multiple sources. For example, several bitmap files for an occupancy grid map that are then arranged to provide a single map. This allows maps to be managed and maintained in a more granular fashion, especially for larger spaces.
  • Merging multiple different map data sources into a single map (single layer) based on processing the data when it is loaded and combining the results in some way.

The purpose of this issue is to get discussion going and identify concrete use cases so that these sorts of features can be implemented in the D Turtle development cycle.

@SteveMacenski
Copy link
Member

The other tickets mentioned above reference the specific action items to implement for map server improvements.

As this is a metaticket that hasn't been scheduled for working after more than a year, I'm inclined to close it. The actual action items are totally valid and will remain open, but I think a centralized design effort is unlikely to happen at any time in the foreseeable future without a champion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants