OSM Indoor Meeting 2024-12-04

The December 2024 OSM Indoor Meetup will take place on BigBlueButton. Details on OSMCal: https://osmcal.org/event/3276/

Upcoming Events

Next OSM Indoor Meetup: 2025-03-05 18:00 CET in the same room
FOSSGIS Konferenz: 2025-03-26 - 2025-03-29 - https://fossgis-konferenz.de/2025/ - includes offline OSM Indoor Meetup again
Expected: OSM Hackweekend Karlsruhe - February 2025

Tobias: working on osm2world (funded by Prototype Fund), includes 3D Tiles with preparations for client-side level filtering
Christoph: GIS infrastructure for modernization of train stations
Volker: Indoor map and routing in conference companion app: https://volkerkrause.eu/2024/07/06/kde-kongress-venue-maps.html
- used successfully during a ~200 people/1 week conference in September in Würzburg
- using OSM changesets on top of base map for transient content, using conditional tag syntax for time-dependent content
- level of detail barely enough for display, not good enough for routing, let alone wheelchair routing
- multi-level auditoriums especially tricky to model
Volker: Discussed access to building maps with FOSDEM team, does not look promising due to concerns of the university.
Volker: MOTIS (FOSS public transport router) gets indoor routing support in v2 (see also FOSSGIS 2024 talk by OPENER next)
- Demo: https://europe.motis-project.de/
- Level separation in map view
- Wheelchair profile
- Can considers live elevator state (not included in the demo).
- Routing is way-based, not area-based.

Does railway=platform_edge impact routing? Not for way-based routing, but helps area routing to the correct location on a platform.

Should this be tagged using a node for the sign, or a segmented platform_edge?
- in Germany: DB models this as signs, not as areas. Where tagged at all, nodes at the sign locations are used.
- in France: nodes for the signs also commonly used, but SNCF also uses area markings on the floor which can be mapped as such or as segmented platform edges.

Example: 9473938493 9473938493
- Node connects an indoor way (level!=0) and an outdoor way without a level tag.
This is assumed to be connected (ie. routable), if it isn't this shouldn't be using the same node.
Unsure: reused nodes between two indoor ways with different level values. No known example though.
Possibly tag the connecting node as entrance to reduce ambiguity.

Example: 374421947 374421947
- A few thousand occurrences (compared to 500k level=*).
Assumed to be a tagging error, treat as alias for level.
In the example this was changed explicitly a few years ago away from level, ask the author why that was done.