Proposal:Parking lane conditionals
The Feature Page for the approved proposal Parking lane conditionals is located at Key:parking:lane |
The Feature Page for the approved proposal Parking lane conditionals is located at Key:parking:condition |
Parking lane conditionals | |
---|---|
Proposal status: | Approved (active) |
Proposed by: | Riiga |
Tagging: | parking:lane:*, parking:condition:*=* |
Applies to: | |
Definition: | Introducing conditionals for parking lanes and deprecating the use of certain older tags. |
Draft started: | 2021-08-24 |
RFC start: | 2021-12-18 |
Vote start: | 2022-01-07 |
Vote end: | 2022-01-21 |
Proposal
In a nutshell
- Use the conditional restrictions scheme for conditional parking restrictions.
- Cleanly separate tagging of physical alignment (parking:lane=*) and condition to park (parking:condition=*).
- Update some wording to better reflect practice and new tagging.
- Parking positions remain unchanged. See the current wiki page for this.
Affected tags
- Introduce parking:condition:*:conditional=* following the conditional restrictions scheme.
- Adopt the current maxstay=* syntax for parking:condition:*:maxstay=*, including conditional restrictions.
- Introduce parking:condition:reason=* to describe the reason for a certain parking condition (if any is given on the sign).
- Deprecate parking:condition:*:default=* and parking:condition:*:time_interval=*.
- Move the values no_parking and no_stopping for parking:lane=* to parking:condition=*.
- Move the value fire_lane to parking:condition:reason=*.
- Document parking:lane=yes and refine parking:lane=no.
Rationale
The current proposal from 2012 uses non-standard tags like time_interval to specify a time range and is not very flexible with handling parking lanes that have different conditions throughout the day. This means that many parking restriction signs cannot currently be mapped in OpenStreetMap. This proposal aims to introduce support for conditional restrictions to alleviate this.
Tagging
Current practice | Proposal | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Parking spacesThe parking:lane tag is used to describe the "physical" properties of the road. This means space properties. Please note that the latter three are considered "physical" tags, this means: parking is not possible, so no parking:condition tag (see below) is required in those cases.
|
Parking spacesThe parking:lane tag is used to describe the physical properties of the road. This means space properties. Please note that this tag only describes the space properties, not the actual condition. A parking:condition tag is required in those cases. See below.
|
Current practice | Proposal | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Parking conditionsThe parking:condition tag describes the legal properties of the parking space.
Type of vehiclesIf the condition is valid only for some vehicles, use
Residential permitsArea based residential permits often carry some sort of letter or code identifying the area wherein they are valid; this can be recorded using the key: parking:condition:side:residents. When parking is requires a ticket or a residential permit, the following combination is often used: More usual OSM tagging convention would, for the same purpose, suggest:
Time dependenceIn many occasions, parking conditions are time limited, especially for disc and residents parking. This can be specified by using the following tag: parking:condition:side:time_interval. Values specify both days and times, plus it can be multiplied. It uses the same syntax for values as opening_hours.
The format is complicated to define technically, but easy to understand by examples:
Intervals may be joined by semicolons with optional whitespace:
With multiple differing conditionsIn the simplest case you have free parking at night, and ticket parking at day on workdays; for example,
Sometimes specifying one default condition is not enough. In these cases we end up with an abundance of tags, for example:
In this example, we couldn't use plain parking:lane:right=no_stopping, as parking is allowed at some times of the day. Maximum stayUse parking:condition:side:maxstay to specify maximum stay limits; especially applicable for disc parking. It should take values precisely as per maxstay. |
Parking conditionsThe parking:condition tag describes the legal properties of the parking space. This tag is also the default value when used in combination with conditonals. Note: Do not confuse condition with conditional. The former is part of the parking:condition tag while the latter is for conditional restrictions and only added at the end of a key.
Type of vehiclesIf the condition is valid only for some vehicles, use
If vehicles are only allowed at certain times, use conditional tags, like so
or
A total ban on lorries would be
Residential permitsArea based residential permits often carry some sort of letter or code identifying the area wherein they are valid; this can be recorded using the key: parking:condition:side:residents. When parking requires either a ticket or a residential permit (named "A" in this example), specify both conditions in the main value and further describe the residential permit in another tag that is specific to that condition
Time dependence (conditional)On many occasions, parking conditions are time limited, especially for disc and residents parking. This can be specified by using the conditional tag: parking:condition:side:conditional. It uses the same syntax for values as conditonal restrictions. In the simplest case you have free parking at night, and ticket parking at day on workdays; for example,
Sometimes specifying one default condition is not enough. In these cases we end up with an abundance of tags, for example:
Note: The use of additional namespaces (:1, :2, etc.) is deprecated.
Maximum stayUse parking:condition:side:maxstay to specify maximum stay limits; especially applicable for disc parking. It should take values precisely as per maxstay. If this applies only part of the day, use parking:condition:side:maxstay:conditional. Reasons for the condition (optional)It is often useful to indicate why certain conditions apply. This allows telling a fire lane from a loading zone or an implicit condition (e.g. no parking near a crossing) from an explicit condition (no stopping sign on a busy throughfare). Use the parking:condition:side:reason tag to describe the reason for prohibitions in the condition when needed. Note: Tagging this is optional. The list of reasons below is not a complete list, just a collection of the most common ones.
|
Examples
Simple signage
All examples below assume a parking lane on the right side of the road.
Sign | Tags |
---|---|
parking:condition:right=free (This is a free parking with no other restrictions.) | |
parking:condition:right=free (By default, this is a free parking with no other restrictions.) | |
parking:condition:right=free (By default, this is a free parking with no other restrictions.) | |
parking:condition:right=no_parking (No parking anytime.) | |
parking:condition:right=no_parking (By default, no parking.) | |
parking:condition:right=no_stopping (No stopping anytime.) | |
parking:condition:right=free (When the conditional restriction is not in place, this is a free parking.) | |
parking:condition:right:hgv=free (This is a free parking, but only for lorries and trucks.) | |
parking:condition:right:hgv=no_parking (Parking is prohibited, but only for lorries and trucks.) | |
parking:condition:right=no_parking (No parking anytime.) | |
parking:condition:right=no_parking (By default, no parking.) | |
parking:condition:right=ticket (Paid parking.) | |
parking:condition:right=free (This is a free parking.) | |
parking:condition:right=free (By default, this is a free parking.) | |
Road section within the junction |
|
parking:condition:both=no_stopping (No stopping anytime) or parking:condition:both=no (No explicit signage, also OK but no_stopping is a bit more preferable) | |
parking:lane:right=parallel |
Complex signage
(note "expand" toward the right side)
Sign | Tags |
---|---|
parking:lane:right=parallel | |
parking:lane:right=parallel | |
parking:lane:right=parallel | |
parking:lane:right=parallel | |
parking:lane:right=parallel (This is a physical space that allows vehicles in parallel.) | |
parking:lane:right=perpendicular | |
parking:lane:right=parallel parking:lane:right=parallel | |
parking:lane:right=parallel parking:lane:right=parallel | |
parking:lane:right=parallel parking:lane:right=parallel | |
3 HR PARKING MAY 1-OCT 31 9 AM-9 PM METERED NOV 1-APR 30 9 AM-6 PM NON-METERED |
parking:lane:right=parallel |
parking:lane=perpendicular | |
parking:lane=no (It's not a parking lane.) | |
parking:lane:right=parallel | |
parking:lane:right=parallel parking:lane:right=parallel | |
parking:lane:right=parallel | |
parking:lane:left=parallel | |
parking:lane:right=parallel |
Other signage
(note "expand" toward the right side)
Sign | Tags |
---|---|
In first half of month: No parking on side with even housenumbers. In second half of month: No parking on side with odd housenumbers. parking:condition:left:conditional=no_parking @ (Jan 1-15, Feb 1-15, Mar 1-15, Apr 1-15, May 1-15, Jun 1-15, Jul 1-15, Aug 1-15, Sep 1-15, Oct 1-15, Nov 1-15, Dec 1-15) | |
No parking on odd days of the month. parking:condition:*:conditional=no_parking @ (Jan 1-31/2, Feb 1-29/2, Mar 1-31/2, Apr 1-30/2, May 1-31/2, Jun 1-30/2, Jul 1-31/2, Aug 1-31/2, Sep 1-30/2, Oct 1-31/2, Nov 1-30/2, Dec 1-31/2) | |
No parking on even days of the month. parking:condition:*:conditional=no_parking @ (Jan 2-30/2, Feb 2-28/2, Mar 2-30/2, Apr 2-30/2, May 2-30/2, Jun 2-30/2, Jul 2-30/2, Aug 2-30/2, Sep 2-30/2, Oct 2-30/2, Nov 2-30/2, Dec 2-30/2) Note: The opening hours syntax does not support something like: parking:condition:*:conditional=no_parking @ (Jan-Dec 2-30/2) | |
On odd days of the month: No parking on side with odd housenumbers. On even days of the month: No parking on side with even housenumbers. parking:condition:left:conditional=no_parking @ (Jan 2-30/2, Feb 2-28/2, Mar 2-30/2, Apr 2-30/2, May 2-30/2, Jun 2-30/2, Jul 2-30/2, Aug 2-30/2, Sep 2-30/2, Oct 2-30/2, Nov 2-30/2, Dec 2-30/2) | |
No parking in first half of month. parking:condition:*:conditional=no_parking @ (Jan 1-15, Feb 1-15, Mar 1-15, Apr 1-15, May 1-15, Jun 1-15, Jul 1-15, Aug 1-15, Sep 1-15, Oct 1-15, Nov 1-15, Dec 1-15) | |
No parking in second half of month. parking:condition:*:conditional=no_parking @ (Jan 16-31, Feb 16-29, Mar 16-31, Apr 16-30, May 16-31, Jun 16-30, Jul 16-31, Aug 16-31, Sep 16-30, Oct 16-31, Nov 16-30, Dec 16-31) |
Features/Pages affected
External discussions
Comments
Please comment on the discussion page.
Voting
Voting on this proposal has been closed.
It was approved with 29 votes for, 0 votes against and 1 abstention.
- I approve this proposal. Great work, and thank you for persistence on refining this Proposal for each and every edge case I and others were throwing at you on the discussion page. Also thank you for all the examples with pictures, when incorporated in the main page, it will be very helpful --Westnordost (talk) 14:38, 7 January 2022 (UTC)
- I approve this proposal. --Riiga (talk) 14:41, 7 January 2022 (UTC)
- I approve this proposal. Thanks for patience in dealing with all related and sort of related things on the talk page. Overall it appears a noticeable improvement and I see no problems with changes being made. It is nice to be able to support more exotic tagging and gain a bit of consistency in tagging Mateusz Konieczny (talk) 14:47, 7 January 2022 (UTC)
- I approve this proposal. --AntMadeira (talk) 15:36, 7 January 2022 (UTC)
- I approve this proposal. --Nmombo12 (talk) 16:32, 7 January 2022 (UTC)
- I approve this proposal. This would make tagging a bit more consistent and I'd be more than happy to re-tag parking restrictions I've previously mapped to this scheme. I wish I'd seen it when it was first proposed. --Rskedgell (talk) 18:34, 7 January 2022 (UTC)
- I approve this proposal. Well written proposal, especially with the comparison between the old and new situation --Cartographer10 (talk) 20:24, 7 January 2022 (UTC)
- I approve this proposal. --Emilius123 (talk) 20:29, 7 January 2022 (UTC)
- I approve this proposal. Thank you for your patience as we went down this epic rabbit hole fixing so much technical debt in the parking lane tagging scheme. I likewise plan to update my existing parking lane tagging in the U.S. and look forward to mapping parking lanes more often, now with a more expressive scheme. – Minh Nguyễn 💬 20:35, 7 January 2022 (UTC)
- I approve this proposal. --Mashin (talk) 22:33, 7 January 2022 (UTC)
- I have comments but abstain from voting on this proposal. I support this, but don't like keeping some of the syntax. ---- Kovposch (talk) 06:35, 8 January 2022 (UTC)
- I approve this proposal. --Nw520 (talk) 15:56, 8 January 2022 (UTC)
- I approve this proposal. Incredibly detailed, but also confusing! Definitely going to need a cheat-sheet to use it! :-)--Fizzie41 (talk) 05:45, 9 January 2022 (UTC)
- I approve this proposal. --mnalis (talk) 13:50, 9 January 2022 (UTC)
- I approve this proposal. --Srdjan02131 (talk) 19:38, 11 January 2022 (UTC)
- I approve this proposal. --Chris2map (talk) 20:00, 11 January 2022 (UTC)
- I approve this proposal. --K4pl4n (talk) 23:56, 12 January 2022 (UTC)
- I approve this proposal. And hope that in the follow-up we can perhaps also aim to "reform" of the parking lane scheme itself (see talk page). Thank you already for your good work. --Supaplex030 (talk) 17:19, 13 January 2022 (UTC)
- I approve this proposal. Good work! I particularly like the `loading_zone` and `passenger_loading_zone` addition --Tjuro (talk) 10:01, 14 January 2022 (UTC)
- I approve this proposal. --EneaSuper (talk) 11:52, 16 January 2022 (UTC)
- I approve this proposal. --Shogun-18 (talk) 14:28, 16 January 2022 (UTC)
- I approve this proposal. --Mweper (talk) 14:47, 16 January 2022 (UTC)
- I approve this proposal. --Cafeconleche (talk) 14:51, 16 January 2022 (UTC)
- I approve this proposal. --HirschKauz (talk) 16:29, 16 January 2022 (UTC)
- I approve this proposal. --TheBlackMan (talk) 20:30, 16 January 2022 (UTC)
- I approve this proposal. --Adiatmad (talk) 03:19, 17 January 2022 (UTC)
- I approve this proposal. --Reino Baptista (talk) 09:46, 18 January 2022 (UTC)
- I approve this proposal. This proposal does not resolve all discrepancies between subtags for parking lanes and parking areas, but a good chunk of them, so it's a big and well-executed step in the right direction. --Tordanik 15:51, 18 January 2022 (UTC)
- I approve this proposal. --Rmikke (talk) 19:39, 20 January 2022 (UTC)
- I approve this proposal. --快乐的老鼠宝宝 (talk) 06:12, 21 January 2022 (UTC)