Proposal:Service=parking
| service=parking | |
|---|---|
| Proposal status: | Proposed (under way) |
| Proposed by: | DavidDean |
| Tagging: | service=parking |
| Statistics: |
|
| RFC start: | 2020-08-02 |
Proposal
Rather than tagging the main service way through a parking lot with just a bare highway=service, with no service=* tag, it would be better to tag it as service=parking.
Rationale
Without an appropriate service=* tag, it is difficult for data consumers and QA tools (like StreetComplete) to know if a particular service road is providing access to parking, or if it just hasn't been tagged yet with the appropriate service tag (like service=driveway, service=drive_thru, service=alley, etc.). This would work in tandem with service=parking_aisle which denotes subordinate parking ways.
Examples
This approach is already used on the map, as evidenced by taginfo.
One example from overpass including service=parking and service=parking_aisle is here.
Tagging
Main parking ways should be tagged with highway=service, and service=parking. Subordinate parking ways should be tagged with highway=service, and service=parking_aisle. The surrounding area should be tagged with amenity=parking.
Applies to
Ways, less likely to affect nodes and relations.
Rendering
Rendered as current highway=service with no service tag (thicker than service=parking_aisle).
Features/Pages affected
Changes will have to be made to the following pages:
External discussions
Comments
Please comment on the discussion page.