Proposal:Role:request stop
| Role:request stop | |
|---|---|
| Proposal status: | Proposed (under way) |
| Proposed by: | Pavvv |
| Draft started: | 2024-04-15 |
Proposal
Add request_stop and request_platform roles to public transport (PTv2) relations. This would also include combinations such as request_stop_entry_only, request_platform_exit_only, etc. This could potentially deprecate the request_stop=yes tag in some way.
Rationale
In many cities there often exist public transport lines which have certain stops on demand. They are commonly parts of night bus lines, however regular lines can also have some less popular stops as request stops. The reason why this role would be better than the request_stop=yes tag is because a stop could still be a permanent stop for most public transport lines while being a request stop for others.
Tagging
The request_stop role should be used just like regular stop roles, likewise request_platform should be used on the corresponding public transport platform. Combinations such as request_stop_entry_only can also be used.
Examples
A bus line which has certain stops on demand should have request_stop and request_platform roles on those stops.
Features/Pages affected
External discussions
Comments
Please comment on the discussion page.