OSM Parking Lane Tag Updater

From OpenStreetMap Wiki
Jump to navigation Jump to search

The OSM Parking Lane Tag Updater is an online tool that provides support for converting OSM tags for parking along streets from the old parking:lane=* scheme to the new street parking scheme. Old tags can be pasted, automatically converted to the new scheme and transferred back to an OSM editor.

The tool and it's code is free to use for other schemes or conversions if needed.

Functionality

The tool can either load tags directly via the OSM ID of a feature (option 1 after starting the tool) or the tags are copied and pasted (option 2). After that, the tags can be automatically translated, reviewed and copied back into an editor.

Warning notices when converting parking space attributes

For certain tagging combinations, the tool provides warnings if the translated tags need to be completed manually with missing attributes or if no automated translation is possible.

"The primary key `parking:$side=*` is missing."
The primary tag describing the position of the parking is missing in the output list (see the street parking tagging quick guide). If possible, add the tag parking:side (where side is left, right or both). The value can be lane (parking on the carriageway), street_side (in parking bays), on_kerb (on the sidewalk), half_on_kerb (half on the sidewalk), shoulder (on a section beside the carriageway), separate (parking is recorded separately in OSM) or no (no parking at all/parking prohibited).

"The primary orientation key `parking:$side:orientation=*` is missing."
The tag describing the orientation of the parking is missing in the output list. If possible, add the tag parking:side:orientation=* with one of the values parallel (parking parallel to the lane), diagonal (diagonal parking) or perpendicular (perpendicular parking/at 90 degrees to the lane).

"Please fix the fixme=* tags. Details are described in the table below."
Some old tags can be expressed more precisely with the new scheme, resulting in missing information that should be added manually if possible. For example, the former expression parking:lane:right=marked filled the tag for the orientation of the vehicles (actually parallel, diagonal or perpendicular). In such cases, the updater generates a fixme=* tag with a problem description (in this case e.g. "Please provide the orientation of parked cars"), which should be replaced with the correct information if possible, e.g. after comparison with aerial or street images. In the review section of the updater, the appropriate tag can be selected directly from a list of possible values, replacing the fixme.

"If possible, also add `parking:{SIDE}:zone=*`."
In residents' parking zones, parking is not allowed for the general public, but only for residents. The number or code of residents' parking zones should be indicated with parking:side:zone=* to make this clear.

"Tagging `parking:{SIDE}:authentication:disc=yes` is proposed but not approved. You may want to remove it."
Time-restricted parking was recorded according to the old scheme as "disc parking", although parking discs are not used everywhere to control the time restriction. According to the new scheme, the time restriction is simply specified as usual with parking:side:maxstay=*, but the specification of the method of time control is also optionally possible with parking:side:authentication:disc=*. If no parking disc is used, the tag should not be used either. Furthermore, the tag wasn't an official part of the street parking proposal, but rather a mapping suggestion.

"This tag contains more than one @-sign. Please update it manually."
Conditional restrictions can be used to specify e.g. temporary parking restrictions. Since the former, deprecated indications of parking restrictions are partly split into different namespaces by the new scheme (e.g. parking:side:fee=*/maxstay=*/access=* etc.), an automatic translation is more difficult if several conditions are combined. If this is the case, a manually translation is necessary. The Street parking wiki documentation there will help in this case.

"Please double check if this is right." / "This tag has a complex value; please check it manually."
Is displayed for some more complicated tagging combinations, where tagging errors often occurred in the past. It cannot hurt to check the result especially for plausibility and correct translation.

"The tool was not able to update this tag. Please update it manually."
Sometimes there are still tags in the syntax parking:condition:side:default, parking:condition:side:time_interval or parking:condition:side:2/3/4, which have already been replaced by the conditional syntax in an earlier proposal. As this notation is too complicated for an accurate automated translation, it should be adjusted manually. The page Translating deprecated default and time interval tagging helps with the translation.

See also

Web links