You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the goal should be, to expose the same tags, that StreetComplete uses as presents.
On top of that, the parking revision proposal adds quite a few more tags that can be used to tag parking information in more detail. However, I think this is something to add later (if at all).
@tyrasd I created #674 to document the key and values. However, I am not sure how to handle the $side within those fields. Can you take care of this or give some pointers?
Given the the street parking revision proposal is successful, I think it is now time to add basic support for this schema to the presents (and iD).
What changed …
I think the goal should be, to expose the same tags, that StreetComplete uses as presents.
On top of that, the parking revision proposal adds quite a few more tags that can be used to tag parking information in more detail. However, I think this is something to add later (if at all).
I suggest adding fields for those tags:
Position
Orientation
How to handle
$side
within a present field?@tyrasd I created #674 to document the key and values. However, I am not sure how to handle the
$side
within those fields. Can you take care of this or give some pointers?Deprecation rules
I don't think it is feasible to add deprecation rules for this schema change in iD. There is a separate tool WIP to support mappers with updating data in their reagion https://github.com/osmberlin/osm-tag-updater.
Separately mapped parking
The proposal als updates some tags on the already existing parking presents for separately mapped parking spaces, which I update in #672 and #673.
FYI @SupaplexOSM
The text was updated successfully, but these errors were encountered: