A convention on how to tag stairs and staircases in indoor settings.
Please discuss this proposal on its wiki talk page.
Not against the idea, but how are you going to map https://cdn.rt.emap.com/wp-content/uploads/sites/4/2023/02/14093446/shutterstock_196171220-scaled.jpg with everything stacked on top of each other?
1 Like
In general I have doubts about using highway=steps for every single indoor steps, with no way to differentiate them from highway=steps forming part of passage through a building that is more general part of pedestrian ways
(applying indoor=yes to both does not solve it)
3 Likes
=steps
- Why do you need a proposal if “The tagging does not change. It is already documented as such, what changes is that the documentation of Simple Indoor Tagging reflects what is already documented on Tag:highway=steps”? That seems to be a wiki discussion. It doesn’t provide new solutions.
- Lack of formal justification on why a user should draw winding lines for stacked staircases
indoor=area: Again, questions remain unanswered
- No formal explanation documented, justified, or proposed to unify on why not
=corridor, and lines for the flight not landings - No solution for the flight area
The same way things are mapped indoor, by just repeating things on the levels where it repeats.
I.e. level=0-1, level=1-2, ..
repeats_on is a bit confusing when it comes to things that cover multiple levels, so I would just repeat the geometry.
I don’t think there is a footway on the platforms, at least according to the definition
used for mapping minor pathways which are used mainly or exclusively by pedestrians
If you are talking from a router support, I think this is sort of tagging for the router, where the router should do area based routing instead.
There usually don’t exist footways on landings, so I don’t think they should be added.
I think highway=corridor is deprecated for this usage according to the wiki
hallway inside a building with some indoor tagging schemes. Some more recent tagging systems, such as Simple Indoor Tagging, use a different set of tags under the
indoor=*key.
indoor=corridor is the walled alternative to indoor=area.
Since landings generally are now walled, indoor=area is the correct way to tag this.
If the landings for your stairs have walls, tagging them as indoor=corridor might be possible, but this would require doors to enter the landing, which we don’t want.
Because stairs are usually fairly regular, landings are usually anything but.
You can add the already existing area:highway=steps tag, if this is required for your geometry.
I simplified this away from Proposal:Detailed indoor stairs mapping - OpenStreetMap Wiki because I thought that this is resonably complicated to tag and editor support in this area is too poor to propose something into this direction.
If you want this added, I can do so, would not change the proposal, since this is already Status: de facto
I can add it, but don’t currently have examples for stairs that require this tagging.
I don’t fully follow what problem you are referring to
This seems a bit undocumented.
My thought of this process was that any signifincant change (in this case: how to handle stairs and their landings) should go through the proposal process.
If I was wrong and in fact this is already clear how to handle stairs and landings, that would be good, but I did not see evidence of this on the wiki.
Good point, so lets talk about an example, since I think this is simpler to be discussed on an example.
How would you use these stairs differently if one is a large stair vs a small stair?
I think
- routing: no difference, both “go up/down stais”.
- indoor rendering: no difference, both are drawn as stairs, one is larger.
- tactile rendering: no difference, both are hatched, one is larger.
- outdoor rendering: no difference, both are ignored due to having the
leveltag. - 3d rendering: no difference, both are a stair.
So why should they be tagged differently?
Eh, I remember that only indoor=room is walled by definition but not indoor=corridor and the Wiki agrees with this. The only difference between corridor and area is that the former represents a linear way (akin yo area:highway=*) whereas the latter an unenclosed POI (akin to highway=pedestrian + area=yes) but both have in common that they’re unwalled unlike indoor=room.
mapping landings as highway=footway is common practice in OpenStreetMap, at least outdoors.
2 Likes
why it would exclude it?
Okay, so I see that the tagging proposal that was worked out in Correct way to map indoor stairs seems not to be very majority-capable.
So gathering the input, below would be what is requested?
I don’t like that this would specify tagging each steps 2x and each landing 2x as well.