F3DB Workshop Erlangen
Members of the OpenStreetMap community with interest in 3D and indoor mapping development met for the first time at the F3DB Workshop This meeting adressed open/not well arranged aspects of 3D and indoor mapping in OSM.
- 91058 Erlangen suburb: Tennenlohe (Germany/Bavaria), Elektrobit Automotive GmbH building, Am Wolfsmantel 46
Chart with marked building...
- Proposed hashtag (twitter etc.) tbd.
- Local contacts: Marek Strassenburg-Kleciak
Eat and drink
Breakfast, lunch and drinks ( Water, Coke, Coffe, Juice ) are provided free of charge.
During the weekend we could talk about the most aspects.
- 10.00-10.30 Acquaintance round, snacks
- 10.30-12.00 General idea presentation. How much of 3D do we need?
- 12.00-13.00 Presentation of existing solutions, improvement of S3DB.
- 13.00-13.30 Lunch
- 13.30-16.00 Tagging discussion, alternatives
- 16.00-16.15 Coffee break
- 16.15-18.80 Tagging discussion,
- 10.00-12.00 Tagging discussion
- 12.00-12.30 Lunch
- 13.30-14.00 Conclusions, next steps
The F3DB wikipage should be changed in november 2014 bz Thomas Greichen and Marek. Be patient.
Protocol F3DB Workshop Erlangen (tagging discussions only)
- mapped rooms should represent "brutto areas" (consensus, with comment by Vladimir)
- same tags as outside should be used for facilities (consensus)
- mapping the indoor areas is the first step; adding walls for "3D" representation of floors is not required (but recommended)
- default width of walls (e.g. 10 cm inner wall, 25 cm outer wall) can be overwritten
- no consensus whether a separate element type for "room" with walls by default should exist
- "corridor" elements are problematic because of multi-use spaces
Windows, doors, openings:
- should be mapped as nodes
- the concept of an "opening" distinct from windows and doors was discussed, perhaps to be tagged as door=opening, window=opening?
- door opening direction should be based on wall direction, as this solution is unambiguous. Editor styles should be configured to show wall directions.
- rooms are automatically ceilings for the floor below (consensus)
- for some cases (e.g. concert hall) the ability to explicitly map ceilings might be useful in the future
- there should be a seamless transition between 2.5D (~ simple indoor) to full 3D
- no consensus whether artificial ways for routing should be manually added in addition to the indoor areas to avoid the more complex algorithms for area-based routing
Stairs and elevators:
- stairs should be mapped as a way with tags (e.g. step_count). Their nodes can be tagged with level/height tags.
- inconclusive discussions about elevators (e.g. whether there should be only one area or one per level) -> participants should continue to think about the problem
- Marek introduces a tagging scheme for roofs: each face of the roof is mapped as an area, and 3+ nodes of each area need to have a height tag
- the new roof tagging scheme could replace Aschillis "roof lines" and represent even vertical roof faces
- the JOSM validator should be modified to no longer issue a warning for nodes with the same lat/lon, but different height
- the basic idea is to have numbers that are independent from the local level names
- the F3DB wiki page will be updated with results from a discussion with Thomas Graichen
|Marek Strassenburg-Kleciak||F3DB||Germany Erlangen, Poland||by foot||own flat|
|Thomas Graichen||F3DB,University Chemnitz||Germany Sachsen||by wire :-)|
|Mockup indoor website||Poland||team||TBC|
|OSM2World||Germany Passau||by train|
|Hongchao Fan||University Heidelberg, Team Prof. Zipf||Germany Heidelberg||by car|
|Roland Olbricht||OSM API 0.7||Germany Bonn||by car|
|nn||Opensciencemap, university Bremen||Germany Bremen||by train|
|Markus Bärlocher||OpenSeaMap||Germany||by car||own flat|
|Stefan Langguth||N-Solut GmbH||Germany||by train|
|Stefan Scholz||Elektrobit GmbH||Germany|
|Oleksandr Fesenko||Mapper||Ukraine||by car|