Talk:Tag:entrance=main

Assigning (multiple) main entrances to a business

How should businesses with multiple main entrances be mapped? Should the operator=* be used? -ViriatoLusitano (talk | contribs) 01:10, 4 January 2026 (UTC)

First of all it should be asked, is this necessary? If there's only one feature in a single building=* , all entrance=* can be easily interpreted and used. What cases are you thinking of?
There's type=provides_feature (more useful for one entrance=* to many features), type=associated_entrance , type=preferredentry , and possibly type=site
operator=* is not clear for this, as the doorways may be said to be "operated" maintained by the building=* / shop=mall management. The feature's operator=* may not be the same as name=* either, for identification. What should be shown would be similar to destination=* (but this should be reserved for the exact signage, which may be different) for both navigation (including the search before routing), and browsing.
access=customers has customers=* corresponding to name=* , not relying on either feature's operator=*
I have thought about using to=* borrowing from route=*
The problems are the one-to-many case, and application in routing. is ideal for both. It saves the effort of manually copying, which can further have typos and other editing mistakes. Routers can use the database linkage directly, without needing to preprocess, or do name-matching on-the-fly. It won't break from users forgetting, or not knowing to update them when the name=* has changed (new tenant, or simply renamed).
—— Kovposch (talk) 15:47, 5 January 2026 (UTC)