Talk:Key:entrance

Mapping question

Where do I put the entrance point? The description does not mention this. I presume, that if there is a building area, then I should create a point ON the path at the side where the entrance is, and put the entrance tag on this point. This way, the point is connected to the building.

Correct. --Klumbumbus (talk) 00:12, 29 December 2014 (UTC)

useful for apartment house?

I saw several times the usage of Key:entrance for the doors of apartment houses. I wonder if this the the right way. OsmAnd then shows only the door pic and not the house number. Addresses could be found but the map does not show the numbers.

See tagging for the renderer. In short, if the data is correct (i.e. in your case, if the house number is related to the entrance), then the software can be fixed, but software can't fix broken or incomplete data. Alv (talk) 17:42, 10 February 2016 (UTC)

definition for entrance=emergency is bad tagging

If this tag should be used for emergency exits, it's completely misleading. Should be either exit=emergency or stretching meaning of the word entrance, it could be entrance=emergency_exit. The tag entrance=emergency should be reserved for emergency entrances (to an emergency area in a hospital)--Dieterdreist (talk) 13:00, 11 March 2017 (UTC)

I agree --Pink Duck (talk) 12:56, 30 March 2017 (UTC)

I agree, though I am unable to spend time on proposal for that Mateusz Konieczny (talk) 01:55, 2 April 2022 (UTC)

I agree. Martianfreeloader (talk) 19:08, 3 April 2022 (UTC)

I agree and created a proposal (Proposed features/exit) to address this. --Push-f (talk) 16:40, 10 June 2022 (UTC)

Considering that emergency=designated isn't formalized yet, I am now planning to address this with Proposed features/emergency access & exits. --Push-f (talk) 02:01, 20 June 2022 (UTC)

definition for entrance=home is not clear

What is a "private house" in this context? Why is the value "home" if this is only for houses? --Dieterdreist (talk) 13:06, 11 March 2017 (UTC)

I've seen that this has now been amended ("private house, home or apartment") which is IMHO much clearer now (i.e. I read it as not including entrances / access doors to "semi-private", shared property areas like stairs, elevators, corridors, courtyards, and other distribution areas. I agree with this definition, but maybe we could be even more explicit in the wording? --Dieterdreist (talk) 09:31, 13 March 2017 (UTC)

This is implied by being on a building=house way and with access=private. entrance=home means I can't tag a main entrance, other entrance and service entrance to a house. Aharvey (talk) 02:16, 11 April 2017 (UTC)

Entrance = home is unnecessary. Every building has min one main entrance. If only public_building should have "entrance=main", so what is with commercial or office buildings? --Pyram (talk) 19:42, 11 July 2018 (UTC)

I tend to agree, as I don't like the "home" value. What the entrance leads to should be made clear based on what way it is part of. An entrance node in the outline of a building=house, for example, is an entrance to a home. This information does not need to be repeated on the entrance node. --Tordanik 19:54, 12 July 2018 (UTC)

Some mappers think that the value of building=* is only meant to describe the original constructed form of the building, not the current use, so a building=house might now be a doctor's office, and a building=warehouse might now be converted into loft apartments (flats). --Jeisenbe (talk) 00:19, 23 September 2019 (UTC)

I'm one of these mappers, actually. :) But to keep this discussion simple and focussed on the topic at hand, I assumed a building where original construction and current use are identical. For buildings where that isn't the case, there will generally still be some tagging indicating the current use, be that building:use=* or an amenity/shop/... tag, so I don't think it fundamentally changes the argument that these entrance values duplicate information from whatever the entrance leads to. --Tordanik 20:03, 28 October 2019 (UTC)

I think we should deprecate entrance=home, you should map the main entrance to a home with entrance=main and other entrances to the home with entrance=yes or entrance=secondary, as others have noted here, no need to try and encode the type of building into the entrance tag. What is the argument for a dedicated entrance=home tag? --Aharvey (talk) 00:36, 8 March 2021 (UTC)

I, at least, see nothing wrong with entrance=main for main entrance to a private house Mateusz Konieczny (talk) 01:56, 2 April 2022 (UTC)

Entrance=exit

This tag doesn't make sense semantically. Why not use the key exit=*? This way we can better differentiate between entrance only, exit only and both. I'm adding a reference to this now, because the exit key is already used more than 5000 times. --Dieterdreist (talk) 09:18, 12 October 2017 (UTC)

I agree and created a proposal (Proposed features/exit) to address this. --Push-f (talk) 16:41, 10 June 2022 (UTC)

entrance=staircase conflicts with function

entrance=staircase was introduced in [2013] without discussion. It describes a physical property of what is behind the entrance, not the entrance itself. The approved proposal was about describing the function of the entrance, such as main, service or emergency. How would I tag the main entrance that leads to a staircase? --Polarbear w (talk) 20:29, 20 January 2018 (UTC)

I don’t fully agree with your assessment that staircase is not about a function, because staircases are about vertical distribution, and such would be an entrance to a staircase. On the other hand, there is no definition, and it is not clear when not to apply this tag, e.g. stairs leading to a cellar? Stairs within the same (multilevel) unit? Emergency only staircases? Etc. —Dieterdreist (talk) 11:03, 21 January 2018 (UTC)

It is an extra property that was not considered in the original values. Thus it should be a separate key, e.g. entrance=main + staircase=up/down/both or so. --Polarbear w (talk) 12:47, 21 January 2018 (UTC)

Exactly. An emergency exit should be mapped as entrance=emergency regardless of if it has stairs behind it, same with the main entrance should be entrance=main regardless if stairs behind it. I'm for removing this key. --Aharvey (talk) 00:38, 8 March 2021 (UTC)

I have seen it used (and used) for apartment buildings with multiple staircases where each has a separate entrance and it is a bit unusual to consider each of 10 entrances as "main" Mateusz Konieczny (talk) 02:01, 2 April 2022 (UTC)

entrance, gate or locality?

How to tag the named entrance of an enclosed area ?
Example : Porte Surcouf of Brest's naval base.

Nominatim don't find entrance=* or barrier=gate but seem to find place=locality.
Also, barrier=gate is rendered but not his name.

City gate is indexed by nominatim, but I guess this is the main tag building=* that is indexed, not historic=city_gate.
Example : Porte Dauphine of Citadel of Blaye.

--Pyrog (talk) 08:30, 29 March 2018 (UTC)

entrance is for entrances in a building, barrier=gate for access to an area. If nominatim doesn’t find named gates it should be fixed on the nominatim side, not by modifying the data (particularly locality doesn’t seem to fit here)—Dieterdreist (talk) 20:12, 30 March 2018 (UTC)

"but seem to find place=locality" - that is not a reason to map nonexisting objects Mateusz Konieczny (talk) 07:11, 13 July 2018 (UTC)

"barrier=gate is rendered but not his name" on which map? Mateusz Konieczny (talk) 07:11, 13 July 2018 (UTC)

Regarding "barrier=gate for access to an area" But what if there isn't a gate? Blackboxlogic (talk) 18:54, 3 March 2021 (UTC)

Entrance inside building outline

In case of a building that starts above ground, and has an entrance from below (through a staircase), is it correct to place the entrance inside the building outline? --Goodlost (talk) 16:05, 29 October 2019 (UTC)

I think it is OK. See e.g. https://www.openstreetmap.org/node/3796852650 --Hlv (talk) 16:29, 29 October 2019 (UTC)

Seems perfectly fine. Though placing it at outline of building:part=yes would be possible in many cases Mateusz Konieczny (talk) 16:36, 29 October 2019 (UTC)

Big entrances

What about entrances that are many tens of meters wide? Are you sure you just want a single point? No they are not always gates. Jidanni (talk) 15:44, 22 December 2019 (UTC)

Power assisted entrances

Anyone know how to tag if an entrance is power assisted or not? I looked around for a good tag to use, but couldn't find one. --Adamant1 (talk) 20:55, 17 September 2020 (UTC)

We should consider using actuator=electric_motor Fanfouer (talk) 21:36, 13 August 2021 (UTC)

Combination with door=*

door=* has been continuously used for years and reach a significant amount of occurrences. Should we make links between entrance=* and door=* more prominent? Fanfouer (talk) 21:38, 13 August 2021 (UTC)

I think it would be useful to make it clear what the relationship between entrance and door (or gate) is. I would think they could be used together as entrance describes the usage, door the physical feature but it would be good to confirm. TrekClimbing (talk) 09:41, 23 August 2021 (UTC)

Yes, they can be used both together and separately (not all entrances are doors, not all doors are entrances). The key is mentioned in "See also", but it could also be added to the "useful combination" section. --Tordanik 18:43, 20 September 2021 (UTC)

Mapping kerb height on an entrance

Quite a few entrances have a small doorstep. Mapping this is important for e.g. wheelchair users, but how should we map it. It propose to use 'kerb:height' (with a height in meters) as this key already exists and is intuitively clear. (If there is no doorstep, one can use 'kerb:height=0' and/or 'no:kerb=yes')

I've also seen 'wheelchair:step_height' in use, but this one seems undocumented and very interpretative. Pietervdvn (talk) 21:20, 4 December 2021 (UTC)

Shop

I'd like to introduce entrance=shop for multi-purpose buildings (e. g. flats + shop on ground level) where the shop entrance is separate from entrance=main. Any opinions? Martianfreeloader (talk) 19:27, 13 February 2022 (UTC)

Not a fan of the idea because it mixes different kinds of information (what type of entrance it is and what it is an entrance to) in the same key. I don't like the 'home' value for the same reason. What if the shop has a main entrance and a side entrance? What if there are two shops with separate entrances? --Tordanik 19:48, 3 April 2022 (UTC)

Do you have an alternative suggestion? Martianfreeloader (talk) 09:30, 4 April 2022 (UTC)

I strongly support this entrance=shop. It's very important to know that a certain entrance is not primarily to the building but to one shop (or other venue). This way, it nicely complements entrance=home which has the same function for apartment entrances. Regarding Tordanik's concern above: the way I see it, the main entrance to a shop is tagged entrance=shop (unless it's the main entrance of the building at the same time) and any side entrances are less relevant as well as secondary in the context of the building and can be tagged simply entrance=secondary. (If you want more precision, you soon need a relation something like Relations/Proposed/Associated_Entrance anyway.) Also note that there's plenty of use of entrance=shop already [1]. --TuukkaH (talk) 07:39, 23 May 2022 (UTC)

tunnel entrances and exits

For a big freeway's eastbound tunnel, besides mapping the tunnel itself, I'll use

entrance=tunnel
distance=123.45
name=Nerdsboro Fastway eastbound tunnel entrance

and

exit=tunnel
distance=124.56
name=Nerdsboro Fastway eastbound tunnel exit

Hope I'm right. Jidanni (talk) 04:13, 26 February 2023 (UTC)

No, you shouldn't do that. That's also a descriptor label not belonging to name=* . Only add the highway=milestone . In some cases, there are official names for tunnel portals, but then this would be the same for both bounds. --- Kovposch (talk) 05:48, 22 June 2023 (UTC)

Side entrances

Some secondary entrances, are usually called side entrances, which is indeed clearer in such cases. Jidanni (talk) 21:14, 21 June 2023 (UTC)

associate entrance to poi

mapping a building=retail containing a office=coworking_space on level>=1 and a shop=mobile_phone on level=0

there are 3 relevant entrances. 2 at the corner of the building, that lead into the shop and one on the south end that leads to the office space. the current placement of the POIs leads to routers giving wrong directions. fixing that and clearly linking those POIs to their entrances seems to require adding relations, which is tedious to do

i was wondering if anyone has advice or can point to related discussion? --Robertgzr (talk) 13:14, 20 August 2024 (UTC)

There are really no other solutions. Don't forget routers still don't support them yet , even if you add them. Most discussions were in Proposal talk:Provides feature there. Nothing in Relation:preferredEntry with fewer instances. Proposal:Associated Entrance seems forgotten.
I doubt whether any router uses entrance=shop , and entrance=office is basically not used. Obviously it doesn't work when there are only one of them, or multiples of them. Fundamentally, entrance=shop has a problem of not allowing entrance=main , entrance=secondary , and entrance=service of shops being distinguished either. It's orthogonal, a different aspect.
For alternatives, I have considered whether destination=* can be used for signage in walkways, escalators, elevators, and stairs before. Maybe to=* could be considered to show where the entrance=* leads to, by matching the name=* of those shop=* and office=* . This would be similar to customers=* , although it is not very good either (eg mixing pre-defined customers=public_transport with freeform text names is a broken format) .
—— Kovposch (talk) 08:01, 21 August 2024 (UTC)

Hi there. Found a 2012 mailing list thread for the original. Strangely Google didn't have any results for it. https://tagging.openstreetmap.narkive.com/qe2WJOt7/new-relation-type-provides-feature
—— Kovposch (talk) 09:03, 21 August 2024 (UTC)