Proposal:Rideshare Access
| Rideshare Access | |
|---|---|
| Proposal status: | Draft (under way) |
| Proposed by: | ccorthell |
| Draft started: | 2020-10-09 |
| RFC start: | 2020-10-14 |
Proposal
The proposal is an access tag value which specifies the legal access policy for rideshare [1] vehicles to way, eg roads. Rideshare vehicles do not always enjoy the same legal standing as other vehicles, such as taxis, private vehicles, public service vehicles, or car sharing vehicles. Rideshare vehicles can potentially be specifically prohibited or permitted on a given road, at a given curb, a given parking lot, etc.
Across the world, there are many different rideshare services. Examples include Bolt, Cabify, Careem, Didi, Gett, GoCatch, Gojek, Grab, Lyft, Shebah, TappCar, Uber, Via, Wingz, Yandex/Yango.
Rationale
access=* tags denote the legal policy of restriction or permission. As rideshare companies have become a more common mode of transportation, the designated and signed legality for such vehicles has come into more common use. This is most common in locations where traffic is controlled and rideshare vehicles are common, such as at large stadiums and airports.
At present, there is no combination of tags that can designate the access legality for use of rideshare vehicles. While psv=* designates taxi=* as “vehicles used in a passenger service (no matter how many seating positions they might have)”, rideshare vehicles are often differently legally designated from taxis, and right-of-way signage can distinguish differing policies for each. A policy applying to public services vehicles psv=yes does not universally apply to rideshare, just as the policy subset taxi=yes does not universally apply to rideshare vehicles.
Right-of-way access for rideshare vehicles can be distinct in regulation. It is exclusive from other uses in 2-track motorized vehicle access, as such would appear in “by use”:
- psv=* (public service vehicle)
- hov=* (high-occupancy vehicle/carpool)
- car_sharing=*
- emergency=*
- hazmat=*
- disabled=*
- rideshare=* (a private vehicle driven for hire, typically coordinated via mobile application)
This would ensure the appropriate routing of any rideshare vehicles dependent on the legal policy of the managed or public right-of-way, as tagged in OSM.
Tagging
Exclusive case: if accessible exclusively to rideshare
access=no rideshare=yes
Prohibitive case: if accessible to all except rideshare
access=* rideshare=no
Examples
Case #1: Denver Airport
To showcase an example of using these tags, exclusive access for rideshare at the Denver Airport has been mapped in both Terminal East and Terminal West.
- Video evidence: https://vimeo.com/342326841
- Changesets: https://www.openstreetmap.org/changeset/91122304
- Overpass: https://overpass-turbo.eu/s/YTp
Case #2: Pittsburgh Airport
The Pittsburgh Airport has roads which are exclusively accessible to rideshare. The parking lot used by rideshare vehicles is accessible only to “Emergencies and Authorized Vehicles Only” and “Lyft Uber Staging” as shown in imagery evidence. This traffic pattern has been confirmed by the airport and communicated to drivers.
Applies to
Rendering
No change to rendering proposed.
Features/Pages affected
- access=* See: "Rationale" section above proposes addition to access ontology
- taxi=* Should mention rideshare, as a similar but potentially differently regulated vehicle designation.
External discussions
Comments
Please comment on the discussion page.