Rectify & describe map server tickets

[SteveMacenski]

I've looked at themes of tickets we have in the stack and we have a number (10+) of tickets around map server:

• representing multi level maps
• change maps service
• data storage for multi level maps
• submap sources
• etc

Many of these cover largely the same ideas but in different ways, or in partial. I'd like to see someone that has a vision for this collapse these tickets into 1-3 tickets that covers a path forward, even if not today prepared to start on it. We have alot of pieces but no roadmap.

I'm excluding the keep out / safety zone / map labeling items since I think we have that ticket now

[SteveMacenski]

Ticket list:
#392 #547 #548 #549 #1226

The way I'd classify this set is: multi-story or multi-map source map server. I'm thinking that this would be similar to the layed nature of the costmaps where we have multiple sources that can come in with some given position/orientation from a global frame, stacked, and served. This would also enable multistory buildings but someone would have to request a specific layer and not the "master" output that would be pretty garbled up. In terms of data structures, I'd think we'd want separate files so that each map is still usable independently of the whole, and for the case of occupancy grids being able to just open a png and see them.

There are others #1010 #239 that are map servery but standalone tasks

[SteveMacenski]

Doesn't seem like there's much interest in this front. Closing.