Proposal:Parking:position
| parking:position | |
|---|---|
| Proposal status: | Obsoleted (inactive) |
| Proposed by: | Supaplex030 |
| Tagging: | parking:lane:side:position=*, parking:position=* |
| Applies to: |  , 
|
| Definition: | Simplifying the tagging of parking lane positions (e.g. on street or on kerb) and allowing the tagging of parking positions on separately mapped parking areas. |
| Draft started: | 2022-10-10 |
| RFC start: | 2022-10-11 |
 | This proposal has become obsolete due to the complete revision of the parking lane schema (see discussion page). |
Proposal
We have an established tagging for parking lanes in OSM (parking:lane=*), which allows to map the orientation and position of parked vehicles on the road. This proposal aims to simplify the position tagging by using the key parking:lane:side:position instead of the current notation parking:lane:side:type, that should be deprecated.
In addition, for separately mapped street parking areas (amenity=parking + parking=street_side/lane), an equivalent tagging for the position of the parking area is proposed: parking:position=*.
Rationale
Mapping parking lanes with the parking:lane scheme is becoming increasingly popular. Along with this, the weaknesses of this scheme (which exists since the early years of OSM) are also becoming more apparent - for example, the tagging of parking restrictions has been reworked at the beginning of this year.
There is also potential for improvement in the tagging of the parking lane position, meaning the area of the street where vehicles can be parked. The current notation parking:lane:side:type is unnecessarily complicated because the specific orientation (type) of the parking lane is included as part of the key. This notation offers no advantages, but it does have some disadvantages:
- It is more complex to understand and to use this tagging and the mapping the parking position may therefore be less attractive for casual mappers.
- It is more vulnerable to mistakes and can lead to inconsistencies if the orientation/type is changed without also adjusting the position's key.
- The parking position cannot be specified with a single both key for both sides of the road, if the position is the same, but the orientation/type is different.
- The evaluation and/or interpretation of the tagging requires high effort, as it needs the inclusion of all possible orientations/types.
The orientation and the position of parking should be regarded as two independent attributes. The proposed tagging simplifies the tagging of the parking position and thus aims to further improve the existing parking:lane scheme and make it more applicable.
Furthermore, there is still no documented possibility to tag the parking position at separately mapped parking areas, which will also be done with this proposal. The naming of the new key parking:position=* is based on the already existing and documented key parking:orientation=*.
Tagging
If parking lanes are mapped as attributes of the highway line: Tag the parking position with the new key parking:lane:side:position, where side means the referring side of the street. The previous key parking:lane:side:type (where type means the orientation of the parking lane) has to be deprecated and replaced over time.
If parking areas are mapped as separate features: The parking position can be tagged with the new key parking:position=*. In general, it's not necessary to explicitly use this tag because parking=street_side implies the position street_side and parking=lane implies the position on_street. However, parking areas on or half on the kerb, sidewalk or shoulder can be specified more precisely with this key (see examples).
The established values for the parking position (especially on_street, on_kerb, half_on_kerb, street_side...) remain as before.
Examples
If parking lanes are mapped as attributes of the highway line: The following table illustrates the new tagging by comparing it with the current variant (assuming that the highway line is pointing "into" the picture).
| Example picture | New tagging | For comparison: current tagging |
|---|---|---|
 |
|
|
 |
|
|
Example of using the new tag parking:position=* on a separately mapped parking area:
| Example | Tagging |
|---|---|
|
Features/Pages affected
- The already existing position section for the parking:lane scheme needs to be updated.
- Examples of how to use the parking:lane scheme in the wiki need to be updated (especially on the parking:lane=* page itself, and possibly on related pages).
- A new page parking:position=* needs to be created for documenting the proposed tagging and example for separately mapped parking areas.
Comments
Please comment on the discussion page.