Talk:Tag:request stop=yes
Jump to navigation
Jump to search
Request stops per bus route
I like this tag for stops that are 'request stops' globally for all buses passing it. But there do exist stops that are only 'on request' for some individual bus lines (routes) passing it. E.g. city bus line stops unconditionally, but a long haul bus line stops only on request. Or daytime bus lines stop unconditionally, but nighttime bus lines stop on request only. Then maybe the role of the stop/platform in the relation (PTv2) should be 'stop_request' or similar, which doesn't exist yet. Aceman444 (talk) 21:52, 21 February 2021 (UTC)
- @Aceman444: I had this question too, so I asked on the tagging mailing list: [1] – Minh Nguyễn 💬 01:13, 28 August 2021 (UTC)
- (Context: https://osmus.slack.com/archives/CDDASU2KX/p1629901258030800) Do you need Role:platform_request too? It may get very long to Role:*_*_only_request when combined with Role:*_*_only. Single
already gets complicated in directional Roles for recreational route relations. Another advantage of request_stop=* is it can theoretically handle time-based or other requirements by request_stop:conditional=*. - https://taginfo.openstreetmap.org/relations/route#roles Existing instances:
- ---- Kovposch (talk) 07:16, 28 August 2021 (UTC)
- @Kovposch: Yes, conditionals could complicate things as well. The problem is that roles are the only data structure that enables us to express the relationship between a stop or station and a route relation. A role is only a single value, and it's already being used for other purposes. (If only OSM's data model had a key-value store for each membership instead of just a role.) At this point, I'm considering tagging the stop or station node with request_stop:route_ref=Orange or request_stop:conditional=yes @ (ref=Orange). It isn't ideal to work around relations like that, but at least most public transportation routes do have refs. – Minh Nguyễn 💬 06:58, 30 August 2021 (UTC)