|Definition:||Indoor pedestrian route|
[[Category:Proposals with "rejected" status|]]
Indoor spaces can be mapped for wayfinding and navigation using Simple Indoor Tagging, along with indoor-specific tags such as Tag:indoormark=beacon. However, existing tags and tools do not easily support routing within indoor spaces. Pedestrian routes can be marked with Tag:highway=footway, but this tag is used mostly outdoors. The proposed tag footway=indoor would be used in concert with highway=footway to specify that a pedestrian pathway represents a route through a building.
The tags highway=footway and footway=indoor should be used to supplement existing Simple Indoor Tagging rather than replace them. Indoor areas that are to be mapped should have rooms and corridors mapped with Simple Indoor Tagging before routes are added using highway=footway and footway=indoor.
The Simple Indoor Tagging tags indoor=room and indoor=corridor use areas to outline the walls and barriers that define the structure of a building. However, they do not specify routes that a traveler could take through a building. There may be unmapped obstacles at the center of a route, and the path from an entrance to an exit may be unclear. Using highway=footway and footway=indoor specifies the distance, turns, and paths that a traveler should take to navigate a room. This is of special interest to travelers with visual impairments, for example, who may need more information to avoid obstacles and navigate the space.
The tag highway=footway fits with existing routing solutions, and footway=indoor simply specifies that this is an indoor route.
The APH Wellness Team Walking Path is a route within the American Printing House for the Blind used for employee exercise as well as public tours of the building. The rest of the building has been mapped with Simple Indoor Tagging.
This section of the LouieLink Downtown Skywalk System is part of a pedestrian skywalk route that passes through a building; the publicly-accessible areas of the building have also been mapped with Simple Indoor Tagging.
It is proposed to apply this tag to a way already tagged with highway=footway in areas that could be defined with Simple Indoor Tagging.
|required||highway||footway||Mandatory tag for pedestrian ways||All|
|required||footway||indoor||Mandatory tag for indoor pedestrian routes|
|required||level||Integer or String||Defines level at which this feature occurs as described in Simple Indoor Tagging|
An indoor footway should connect to room door nodes ( Key:door ), building entrance nodes ( Key:entrance ), and perhaps other important navigational POIs. An indoor footway (which would have the tag footway=indoor) connected to the door node (tagged entrance=main) can thereby connect to exterior sidewalks and other exterior routes (which would not have the tag footway=indoor), forming a connected exterior-to-interior navigation route.
Pedestrian routes inside buildings.
Comments and discussion were posted on the OSM tagging list. Some of these include:
- How does this relate to Tag:highway=corridor?
- The tag highway=corridor is related to an earlier indoor tagging scheme that is not mentioned.
- It is not documented how highway=corridor should be used with Simple Indoor Tagging.
- It may be that highway=corridor is being used for other features, such as exterior passages through buildings (like tunnel=building_passage) or underground shopping concourses (such as at a large train station).
- There are 13,763 ways tagged highway=corridor according to taginfo, compared with 10,164 objects tagged indoor=corridor (2019-09-12).
- Should routing engines generate routes from indoor maps rather than using mapper time to specify indoor routes? On the other hand, can routing engines generate indoor routes from Simple Indoor Tagging in the near term?
- Someone cited as problematic the "use of highway=footway, rather than a new tag which would have no effect data consumers which don't opt in ...sharing the same tag for both use cases (hints for routers without good indoor support which should be ignored by more advanced routing engines, versus routes which should always be preferred over automatically derived routes)."
Please comment on the discussion page.
- I oppose this proposal. The section "External discussions" raises the question how this relates to highway=corridor, but doesn't answer it. From reading this proposal, I get no idea what's the difference between those tags, and why we need a new tag. With its ~14000 instances, highway=corridor can already be considered a de-facto standard, so we need good reasons and a clear distinction when introducing a similar tag. --Fkv (talk) 21:28, 26 September 2019 (UTC)
- I oppose this proposal. It seems to me that conflict/duplication of highway=corridor remains unexplained Mateusz Konieczny (talk) 16:16, 27 September 2019 (UTC)
- I oppose this proposal. I agree with at least partial overlap with highway=corridor, and also want to point to indoor=yes which is used significantly with highway=*: see taginfo, currently 60286 instances of this combination (of which 34335 are highway=footway). --Dieterdreist (talk) 09:04, 30 September 2019 (UTC)
- I have comments but abstain from voting on this proposal. It's not perfect, and I would have wanted some of the comments from #External discussions addressed, but even in its current state, I'd rather people used this tag (with its clearly defined relationship to SIT) instead of the ad-hoc highway=corridor tag (which doesn't really fit into any comprehensive indoor mapping concept). --Tordanik 15:54, 30 September 2019 (UTC)
- I would prefer to keep footway=* for the typology and not have all indoor footways as just one type. From what I found, highway=footway with indoor=yes is the defacto standard currently, and I do not see an improvement in the proposed tags, rather it would take away the possibility to distinguish different kind of footways on this tag level.--Dieterdreist (talk) 17:53, 30 September 2019 (UTC)
- I oppose this proposal. Agree with Dieterdreist - not clear how this is better than highway=corridor or footway + indoor=yes (which is supported by iD) - I'd recommend using highway=corridor, so that indoor hallways are not considered routable ways by database users who don't know about this tag. --Jeisenbe (talk) 02:21, 4 October 2019 (UTC)
- I oppose this proposal. no significant improvement over already used tagging --Waldhans (talk) 07:18, 5 October 2019 (UTC)
- I oppose this proposal. There's already highway=footway + indoor=yes and highway=corridor. Instead of introducing a new tag, i'd prefer that there were only one tag (or tag combination). --SelfishSeahorse (talk) 17:16, 6 October 2019 (UTC)
- I oppose this proposal. This overlaps with highway=corridor und I would prefer a simple indoor=yes --chris66 (talk) 17:38, 6 October 2019 (UTC)