Talk:Tag:building=entrance
Entrance identification
What is the best way to tag the identification, i.e. number etc., of the entrance? If the house for instance has addr:housenumber=13, how am I going to map door A? One natural way would be to add ref=A to the entrance. I have earlier thought of addr:housenumber=13 A, but that would yield redundancy. --Erik Lundin 10:13, 22 October 2009 (UTC)
- I've used ref=*, too, but lately I have been using addr:staircase=* instead (a native speaker might prefer addr:entrance, who knows). People in some countries might consider each staircase/entrance an individual address even when in a single building; such countries might end up using the form addr:housenumber=13 A for each entrance. Yet some houses can have a letter already as a part of the house number, so one could have an another entrance with addr:housenumber=13a A nearby, which can be a source for confusion when searching. On the other hand, there's hardly a reason why a ref=* on any building=entrance node couldn't be understood by any software that (eventually) understands entrances in the first place. Alv 11:31, 22 October 2009 (UTC)
- You don't have a staircase as destination, a destination is naturally a door, so "entrance" is preferred. Also the staircase might be somewhat apart from the entrance.
- It is not confusing when one building with one housenumber has two or more entrances with addr:housenumber. It is just reality.
- If there are many entrances for one housenumber, I propose to use entrance:is_main=yes + entrance:ref=A/B/C or whatever the entrance number is. + optional entrance:wheelchair=yes/no Lulu-Ann
House numbers, again
A lighting talk is no reason to bypass other countries conventions - not mapping conventions, but the concept of what the house number refers to. And a talk misses the opportunity for discussion (that we've had). Even if tagging a addr:housenumber always on the entrance nodes works near you, it produces bad data in other countries. It would mean, for example on the building where I live, that either
- There would be 12 times a addr:housenumber=7, on each door. 11 of those would have an additional addr:staircase (or ref), with 7 distinct values (A to F, and a C;D), and one without - the basement. In reality everybody (including the tax office, cadastral records, postal service) in this country refers to the whole building as having a house number "7", but now I'd have the number entered 12 times, and always have 12 destinations to choose from. If a user requires a specific entrance/staircase, it has to be separate from the house number, and the software needs to handle such cases.
- There would be two nodes of each (housenumber=7 A, =7 B, =7 E, =7 F), nodes with 7 C and 7 D both once, once a "7 C; 7 D" (ugh), and one with no housenumber at all or a plain 7. There could be a separate detached building with the house number "7 a" (and only one entrance) next to this, of which the user knows nothing of - software can't just guess, and neither can the user guess that "7 A" is, or isn't, a valid or correct destination when he only knows the number 7.
This building is even a simple case, as the building has a house number only on one street. Nearby there are buildings (I've linked to them before), where each entrance can be freely referred to as both "Sofianlehdonkatu 11 A" and "Vähänkyröntie 4 A" (letters A to E, IIRC). A single housenumber tag on every entrance would always be missing information.
There are cases and places where either, but not both, ways is misleading or wrong - it means that your way isn't the only way or should be recommended as the right one. I've tried to convey this with the last changes I made. Alv 12:58, 7 September 2010 (BST)
- So let us approach the problem not from the data view but from the usecase view. A blind OSM user got your address. He might approach from any direction. So if there are many entrances with the same house number, how does he know at which entrance the taxi has to stop? If there are two entrances called 7 A and they are both close to your appartment, then 7 A is just the right information to stop the taxi at the first approached entrance, right? Lulu-Ann
- If one refers to "7 a", it can be the staircase door, and the detached building on the small lot that was split from this buildings lot. (Not reality just here, but could be, and is in other suburbs). Without separating the house number from the entrance, one can not always know which door they should seek. We've already separated the house number part of the address from the street part, (and postal code etc.), so why wouldn't we have a separate field for the next level down? Even further down the address tree, identifying each aparment within the staircase as a separate housenumber (think highrise buildings) would scale badly. Besides, in many places the building number is visible only once on the wall ("this is building 7") and the staircase doors have only the letter identifier. Alv 16:41, 14 September 2010 (BST)
When there is a double address on one entrance, I propose to have two nodes on the same position, each one carriyng one set of addr:-tags. If reality is double, mapping has to be double. Lulu-Ann
- One door, one node. Just as we don't do double ways for roads with two refs. Alv 16:41, 14 September 2010 (BST)
Remove interpolation when housenumbers are on nodes
I propose to remove the interpolation lines, when housenumbers are completele mapped on that line as nodes.
Exit only
If you have a turnstile or an automatic door, it is possible that a door in a building is only usable as an exit. I think we coult tag it building=exit then. But what with turnstile exits of non buildings (like parks)? Is exitonly=yes better? Do we need a oneway tag for nodes? --Lulu-Ann 08:41, 13 January 2011 (UTC)
emergency exit
Continuing on the exit_only, maybe we should also think of a way to tag emergency exits. --Polyglot 06:52, 24 April 2011 (BST)