[Tagging] Twisted semantics of entrance=exit and entrance=emergency

Tobias Knerr osm at tobias-knerr.de
Fri Jun 10 16:59:58 UTC 2022


Am 10.06.22 um 15:50 schrieb Martin Koppenhoefer:
> We have a different key for every payment type and one for every type of fuel

Payment type and fuel are attributes/sub tags, entrance is an object 
type/main tag. From a data modelling perspective, it is nicer for each 
element to have exactly one main tag.

 > which problem is big enough to make us undergo a painfull transition 
from the current entrance=* and exit=* tags to something different?

I'm not sure if there's a big enough problem to change anything about 
entrance tagging, really. I'm ok with tagging emergency exits using the 
entrance=* key. But _if_ we're changing something, then I'd rather 
change the term we use to mean "entrance-or-exit", not the decision to 
treat these as the same general kind of object.

>> Having separate top-level keys for entrances and exits is undesirable. Perhaps the strongest of several reasons for this is that the vast majority of such features can be used as both an entrance AND an exit.
> 
> so what? We can imply exit=yes for entrance=* unless explicitly stated.

I predict that some users are going to insist that untagged means 
unknown, as they do with all sorts of other information (see numerous 
debates surrounding StreetComplete quests for things that were formerly 
considered implied), and start tagging entrance=yes + exit=yes for 
normal doors on buildings.

> You are assuming with “such features” that an emergency exit and a main entrance are something of the same kind, but this isn’t the only possible interpretation

Not the only possible interpretation, but a sensible one. I'd rather not 
consider something as an entirely different kind of object just because 
someone prints out an "entrance prohibited" sign and tapes it to a door.

Entrances and exits are going to be treated similarly in many 
circumstances and in many kinds of software software. They have similar 
attributes (door, height, width, ...), similar mapping conventions about 
being a way node of a building or amenity outline, and so on.



More information about the Tagging mailing list