Indoor OSM user meeting at FOSSGIS Konferenz 2025

From OpenStreetMap Wiki
Jump to navigation Jump to search

https://pretalx.com/fossgis2025/talk/DSHE3R/, notes translated from German

Meeting Notes

Introduction of attendees and their work

  • Holger (mfdz, stadtnavi)
    • routing for transfers in public transport
    • accessibility routing
  • Volker (KDE)
    • indoor maps and routing for train stations, airports, event venues etc for a free software travel assistance app
    • (accessible) transfer public transfer routing for Transitous/MOTIS
  • Felix (MOTIS)
    • intermodal public transport routing with indoor support
    • accessibility routing
    • considering elevator status in routing
  • Michael (OSM)
    • hard to map indoor data manually, interested in how to do that
  • Jaques-Maurice, Richard, Jan (TU Dresden)
    • 2.5D visualization of OSM indoor data
    • see https://pretalx.com/fossgis2025/talk/RMMA9H/
    • Github repository with their implementation available
    • stair/elevator rendering in 3D
    • accessible maps
    • did import using CAD SVG and evacuation maps for TU Dresden buildings
    • mapping accessibility relevant details, tactile rendering

Discussion

3D Map Usability

  • hard to get right
  • reduce level of detail to not overwhelm the user
  • TU Dresden only shows +/-1 level, with non-current levels being semi-transparent
    • interactions: rotation, level changes, 2D/3D transition
    • searchable rooms, but no routing yet
    • fully based on SIT, re-using accessible maps infrastructure
    • stairs tagging very important, using center path for 3D reconstructions
    • accessibility tagging has a lot variations
  • scaled level height to 12m (x4) for better overview

Stair tagging

  • ambiguities in SIT spec found by TU München
  • stair case vs. center line vs. stair polygon
  • level tags vs. point highest/lowest vs incline up/down
  • indoor=pathways vs highway=stair vs highway=steps vs indoor=corridors vs indoor=areas
  • conflicting proposals and tagging schemas

SIT vs routing paths

  • TU Dresden and TU München are using fully SIT-compliant area-only mapping
  • DB/SNCF (additionally) use routing paths, MOTIS also relies on that
  • polygon based routing is significantly more expensive

Level topologies

  • how to connect indoor <-> outdoor in non-flat environments, for routing and for rendering
  • TU Dresden renderer doesn't cover outdoor environments
  • MOTIS assumes elements without a level tag connect with arbitrary level, any additional restrictions (door, entrance, etc) don't practically work. When levels exist on both sides they have to match (or their has to be a level change element)
  • 3D rending needs to know at the building outline where there outdoor floor connects

TU München BIM data access

  • long process to negotiate with university, understanding their concerns, building personal relations
  • would prefer thick wall model for old/historic buildings
  • TU Dresden: thick wall are a big problem for tactile maps
  • thick walls are better for high-detail (3D) rendering
  • thick walls provide better input for area routers
  • indoor=barrier? foyers with big artworks blocking the way
    • better: reuse existing outdoor tags, e.g. barrier=block, barrier=yes

Fractional levels vs fully synthetic levels

  • also: inclined rooms, short steps not changing the levels
  • use full levels if there's more than just stair landings
  • use fractional levels for stair landings

Inclined rooms/corridors, multi-floor rooms

  • unsolved tagging