OSM Indoor Meeting 2024-03-06

OSM Indoor Meeting 2024-03-06

Previous meetup: https://wiki.openstreetmap.org/wiki/OSM_Indoor_Meeting_2023-12-08

Mailing list/forum posts topics

• https://community.openstreetmap.org/t/indoormapping-und-veranstaltungsraume/107765 - indoor room tagging question
• https://community.openstreetmap.org/t/looking-for-developer-collaboration-on-indoor-data-donation-project/109544/1 - BIM to OSM conversion Prototype Fund project
• https://lists.openstreetmap.org/pipermail/indoor/2024-February/000013.html - elevator proposal from OPENER next

FOSSGIS Konferenz 2024 sessions

• https://pretalx.com/fossgis2024/talk/LXGXQJ/ - BIM to OSM conversion by Helga
• https://pretalx.com/fossgis2024/talk/SBKZFZ/ - indoor routing by OPENER next
• https://pretalx.com/fossgis2024/talk/QTMLRT/ - indoor discussion/networking session

Next Online Meetup

2024-06-05 18:00 CEST (first Wednesday of the third month of each quarter at 18:00 CE[S]T)

IndoorLoc

Markus and Steffen presenting their work on indoor localization.

Needed/missing information in OSM for this:

• detailed stair model for matching barometric sensor data
• floor heights (height information on indoor=level, but rarely used)
• wall materials: in particular for metal as it interferes with radio signals, such as fire protection doors
  • we currently can't model into which direction a hinged fire door would be moved in a default open state
• escalator and moving walkways speed - see https://wiki.openstreetmap.org/wiki/Key:conveying - duration tag
• elevator entrances - see https://wiki.openstreetmap.org/wiki/Proposal:Elevator_dimensions
• intermediate floors/fractional levels

Stairs Modeling Proposal

Jan's work on modelling stairs: https://hackmd.io/RdID_VHRRJmV8O8_RClJdg?both

Feedback/questions:

• can indoor=pathway also be tagged as highway=steps, to make this explict rather than relying on this being contained in indoor=room + stairs=yes
• explicit contour polygon in addition to the center way vs. https://wiki.openstreetmap.org/wiki/Key:width tagging
• lowest/highest tags are redundant and can be determined by the level tag
• there is no way to determine the height for intermediate landings explicitly, but could be seen as a fraction of the full floor height
• repeat_on conflicts with explicit level tags on pathway nodes
• depth/height of single steps? -> computable based on https://wiki.openstreetmap.org/wiki/Key:step_count, https://wiki.openstreetmap.org/wiki/Key:incline as an angle also exist

Level topology

• limits on modeling uneven floors in complex/old buildings
• level order is assumed in many places:
  • user display
  • level ranges
  • level heights are incremental
• https://wiki.openstreetmap.org/wiki/Simple_Indoor_Tagging is the authoritative source for the level tag, https://wiki.openstreetmap.org/wiki/Indoor_Mapping describes an outdated use
• https://wiki.openstreetmap.org/wiki/Key:level:ref is the human readable label for a level

Implicit walls on indoor=corridor

Discussion based on https://lists.openstreetmap.org/pipermail/indoor/2024-February/000012.html by Volker and Antoine's reply https://lists.openstreetmap.org/pipermail/indoor/2024-March/000014.html.

Suggested approach:

• indoor=corridor has no implicit walls
• we fix TU Dresden (and other affected buildings) by using indoor=room + room=corridor instead
• add explicit outer walls where needed (indoor=wall)