Indoor OSM user meeting at FOSSGIS-Konferenz 2026

From OpenStreetMap Wiki
Jump to navigation Jump to search

https://pretalx.com/fossgis2026/talk/MVPRLD/, notes translated from German

Meeting Notes

Attendees and their areas of interest

  • Volker (KDE): routing in train stations, see also https://pretalx.com/fossgis2026/talk/CYW3VL/
  • Tobias (OSM2World): original SIT author
  • Frank (TU München): importing 36k rooms of TU Munich from BIM data, "thick wall" mapping
  • Christoph (DB Infrago): station information for passengers, see also https://wiki.openstreetmap.org/wiki/FOSSGIS_2026/OSM-Samstag/Ergebnisse#Bahnhof_mappen
  • Michael (NRW Mobidrom): MOTIS, routing for public transport transfers
  • Moritz (TU Darmstadt): MOTIS, area/indoor routing
  • Felix (TU Darmstadt): expanding the eixsting basic indoor routing in MOTIS
  • Michael (OSM mapper)
  • Roman: (OSM mapper): best practices for indoor mapping
  • Richard (TU Dresden): 2.5D indoor renderer (see FOSSGIS-Konferenz 2025), semi-automatic indoor routing graph generation (https://pretalx.com/fossgis2026/talk/XR3EJ7/)
  • Jonas (Graphmasters): navigation map für Köln Messe, multi-level routing for cars, indoor in parking garages on a specific floor
  • Christiane (Uni Marburg): historic building mapping/routing
  • Rafael (OSM mapper): pedestrian area routing
  • Mila (RMV): displaying stations, stair mapping, routing currently separate, want to merge this into a single dataset

Intro to existing communication channels

Discussion

Outdoor/Indoor transition

  • car ways end at parking garage entrance
  • charging stations are highly relevant POIs for car routing, and might be on a different floor level
  • mix of way-based and area-based mapping for pedestrians
  • layer vs level tagging outdoor
  • can level tags be added to "outdoor" elements?
  • -> move away from the strict in/out separation, level=* is allowed everywhere
  • -> layer is mostly legacy tagging for the renderer, doesn't imply a floor level

Vertical resolution

  • "level" as a unit is bad
  • proper level heights would be much more useful, but hard to map
  • indoor=level, name=* for naming, indor=level, height=* for plain levels exists but isn't widely used
  • buildings on hillsides are tricky
    • doable for router by way connection
    • impossible for rendering with current modeling
  • level domains, different level heights in connected buildings: possible solutions but very complex and not yet worked out in detail
    • site relation as a possible way to connect that

Mapping vs import

  • is this done by manually measuring buildings, or plan-based/import-based?
  • geometry import mostly from plans, semantics/naming/etc on site

Routing

  • Richard's work: graph-based, doors extremely relevant
  • Volker's work: area-based
  • lecture halls can't be modeled properly yet, or inclined rooms in general
  • mapping level of detail is key for good routing
  • mapping tactile guides is important

Thick walls

  • should indoor=wall, area=yes be allowed?
    • walls with non-uniform width are highly relevant for historic buildings
  • different trade offs between 2D rendering, 3D rendering and routing
Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=Indoor_OSM_user_meeting_at_FOSSGIS-Konferenz_2026&oldid=2972451"