add scheme to replace parking:lane:_side_=parallel/diagonal/perpendicular

[tiptoptom]

Deprecated OSM Tag(s)

parking:lane:side=parallel/diagonal/perpendicular

Replacement OSM Tag(s)

parking:side=lane
parking:side:orientation=parallel/diagonal/perpendicular

Link to OSM Wiki page

https://wiki.openstreetmap.org/wiki/Street_parking
old scheme: https://wiki.openstreetmap.org/wiki/Key:parking:lane

Further Information

No response

[tordans]

If this is something that would be merged we can add a few others as well.

In the meantime there is https://github.com/osmberlin/osm-tag-updater and the Zlant editor has a updater integration (well hidden behind the 🔄 icon).

[tyrasd]

Generally, I'd be fine with this tag deprecating proposal (as it was included in the tagging proposal).

But, from a technical standpoint, I have to note that the implementation of tag deprecation rules here does not scale up well if there are many versions of a tag to be considered… I'd say that adding these 9 cases would be still fine, but (much) more than that would be a stretch.

@tordans Do you think you could provide the "business logic" part of the @osmberlin/osm-tag-updater as an npm module? Because, then I could quite easily build that completely into iD directly as a dedicated validation module.

[tiptoptom]

So I will now make a PR for the mentioned 9 cases?

[tordans]

But, from a technical standpoint, I have to note that the implementation of tag deprecation rules here does not scale up well if there are many versions of a tag to be considered… I'd say that adding these 9 cases would be still fine, but (much) more than that would be a stretch.

The proposal lists some data at https://wiki.openstreetmap.org/wiki/Proposal:Street_parking_revision#Numbers_of_usage_of_the_current_schema

Currently (as of the end of October 2022), about 260.000 road segments in OSM have "primary" parking lane tagging (parking:lane:both=, parking:lane:left= or parking:lane:right=*), (…)

All other old tags are tags are well below the 50k mark, so I think we should ignore those for deprecation rules.

Following this logic, we could add a deprecation rule for those cases:

Source: https://osmberlin.github.io/osm-tag-updater/#/list

Old tag	New tag (maybe missing fields)	Compare type	Optional message
parking:lane:{SIDE}=yes	parking:{SIDE}=yes	tag
parking:lane:{SIDE}=separate	parking:{SIDE}=separate	tag
parking:lane:{SIDE}=parallel	parking:{SIDE}:orientation=parallel	tag
parking:lane:{SIDE}=diagonal	parking:{SIDE}:orientation=diagonal	tag
parking:lane:{SIDE}=perpendicular	parking:{SIDE}:orientation=perpendicular	tag
parking:lane:{SIDE}=marked ==> Not this one, too complex	[ "parking:{SIDE}:markings=yes", "fixme=Please provide the orientation of parked cars with parking:{SIDE}:orientation=parallel|diagonal|perpendicular" ]{ "key": "parking:{SIDE}:orientation", "values": [ "parallel", "diagonal", "perpendicular" ], "msg": "Please provide the orientation of parked cars. This information was not recorded previously, which is one of the benefits of the new schema." }	tag
parking:lane:{SIDE}=no	parking:{SIDE}=no	tag
parking:lane:{SIDE}=no_parking	[ "parking:{SIDE}=no", "parking:{SIDE}:restriction=no_parking" ]	tag
parking:lane:{SIDE}=no_standing	[ "parking:{SIDE}=no", "parking:{SIDE}:restriction=no_standing" ]	tag
parking:lane:{SIDE}=no_stopping	[ "parking:{SIDE}=no", "parking:{SIDE}:restriction=no_stopping" ]	tag
parking:lane:{SIDE}=fire_lane	[ "parking:{SIDE}=no", "parking:{SIDE}:restriction=no_stopping", "parking:{SIDE}:restriction:reason=fire_lane" ]	tag

---

@tordans Do you think you could provide the "business logic" part of the @osmberlin/osm-tag-updater as an npm module? Because, then I could quite easily build that completely into iD directly as a dedicated validation module.

In Theorie, yes. However, the app is not prepared for this (no NPM package) and some functions are not exposed properly, yet (the output is constructed during render ATM). It is not just the input-output-migration, but also warnings and notices that need to be added to the UI to make this a propper integration. The Zlant Editor Integration (https://github.com/zlant/parking-lanes) only does parts of what the osmberlin/osm-tag-updater does, which is not ideal, since information gets lost… (but still, its great to have it in there, for advanced users…).

The main reason why we did not invest more time in this is, that we assume that those old should be migrated while also manually reviewing the data. And the parking lane layer for StreetComplete (which also understand the most important old tags) can be used to migrate the data quite well.

---

@tiptoptom:

So I will now make a PR for the mentioned 9 cases?

I general +1. But I think your migration is wrong. Using https://osmberlin.github.io/osm-tag-updater/#/manual I get
INPUT

parking:lane:right=perpendicular
OUTPUG
parking:right:orientation=perpendicular

But your PR suggest

"parking:right": "perpendicular"

[tiptoptom]

@tordans of course you are right. I will add the "orientation" and also "parking:side=lane". And your tags maybe as well?

[tiptoptom]

I think, now it should be fine: 9f70d4b