Proposal talk:Queues

Extend to generic entrance/exit paths?

I guess this idea could be extended to a generic footway=entrance and footway=exit for entrance and exit paths? This might help navigation instruction more broadly, also for features where the entrance has no queues. Maybe instead just extend entrance=yes and entrance=exit to usage on highway ways, so the idea can also be used for non-footways. JeroenvanderGun (talk) 15:15, 3 September 2026 (UTC)

Could work- but how to differentiate between types of queues/entrances, like the priority or single-rider ones? Jxpsert (talk) 19:05, 3 September 2026 (UTC)

With special values for entrance? There is already a long list on that wiki page, values like entrance=priority and entrance=single-rider could be added to that list. JeroenvanderGun (talk) 19:28, 3 September 2026 (UTC)

entrance=* is already messy enough. Conceptually this has problem when different queues pass through the same opening, only topologically separated by being different highway=footway lines in the data. They are all entrance=main in the first place.

queue=* can still be used for different queues. Ones indoors can extend beyond the entrance=* to outside. If you mean the entrance=* is mixed, there's either no need to add what it is, or it can be semicolon multival.

Cf footway=sidewalk question, the proposal could simply propose queue=* first without footway=queue or any footway=* , if the whole footway=* has great uncertainties or undecided topics. Avoids the trouble. https://community.openstreetmap.org/t/rfc-feature-proposal-queues/147251/3

Kovposch (talk) 07:51, 4 September 2026 (UTC)

footway=entrance would have problem with entrance=* being used for both entry & exiting, and the entrance=only / exit=no here

Kovposch (talk) 07:51, 4 September 2026 (UTC)