Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecated parking #1390

Merged
merged 8 commits into from
Dec 20, 2024
Merged

Deprecated parking #1390

merged 8 commits into from
Dec 20, 2024

Conversation

tiptoptom
Copy link
Contributor

Description, Motivation & Context

There was already a PR #918 about this. I'm willing to finish it now.

Related issues

Closes #879

Links and data

Relevant OSM Wiki links:

Relevant tag usage stats:

Checklist and Test-Documentation Template

Read on to get your PR merged faster…

Follow these steps to test your PR yourself and make it a lot easier and faster for maintainers to check and approve it.

This is how it works:

  1. After you submit your PR, the system will create a preview and comment on your PR:

    🍱 You can preview the tagging presets of this pull request here.
    If this is your first contribution to this project, the preview will not happen right away but requires a click from one of the project members. We will do this ASAP.

  2. Once the preview is ready, use it to test your changes.

  3. Now copy the snippet below into a new comment and fill out the blanks.

  4. Now your PR is ready to be reviewed.

## Test-Documentation

### Preview links & Sidebar Screenshots

<!-- Use the preview to find examples, select the feature in question and **copy this link here**.
     Find examples of nodes/areas. Find examples with a lot of tags or very few tags. – Whatever helps to test this thoroughly.
     Add relevant **screenshots** of the sidebar of those examples. -->

<!-- FYI: What we will check:
     - Is the [icon](https://github.com/ideditor/schema-builder/blob/main/ICONS.md) well chosen.
     - Are the fields well-structured and have good labels.
     - Do the dropdowns (etc.) work well and show helpful data. -->

### Search

<!-- **Test the search** of your preset and share relevant **screenshots** here.
     - Test the preset name as search terms.
     - Also test the preset terms and aliases as search terms (if present). -->

### Info-`i`

<!-- **Test the info-i** for your fields and preset and share relevant **screenshots** here.
     The info needs to help mappers understand the preset and when to use it.
     [Learn more…](https://github.com/openstreetmap/id-tagging-schema/blob/main/CONTRIBUTING.md#info-i)
 -->

### Wording

- [ ] American English
- [ ] `name`, `aliases` (if present) use Title Case
- [ ] `terms` (if present) use lower case, sorted A-Z
<!-- Learn more in https://github.com/openstreetmap/id-tagging-schema/blob/main/GUIDELINES.md#2-design-the-preset -->

Copy link

🍱 You can preview the tagging presets of this pull request here.

Copy link
Collaborator

@tordans tordans left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets remove those that are about below 1k as commented inline.
We have new guidelines on this in https://github.com/openstreetmap/id-tagging-schema/blob/main/GUIDELINES.md#tag-updates-and-additions which don't have a strict number, but we want to only have entries here with relevant usage.

"replace": {"parking:both": "yes"}
},
{
"old": {"parking:lane:both": "no"},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +1276 to +1279
{
"old": {"parking:lane:both": "fire_lane"},
"replace": {"parking:both": "no", "parking:both:restriction": "no_stopping", "parking:both:restriction:reason": "fire_lane"}
},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can keep this (even though below 1k) because the new tagging is complex.

"replace": {"parking:both": "no", "parking:both:restriction": "no_stopping", "parking:both:restriction:reason": "fire_lane"}
},
{
"old": {"parking:lane:both": "separate"},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"replace": {"parking:right": "no", "parking:right:restriction": "no_stopping", "parking:right:restriction:reason": "fire_lane"}
},
{
"old": {"parking:lane:right": "separate"},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"replace": {"parking:right": "separate"}
},
{
"old": {"parking:lane:right": "diagonal"},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"replace": {"parking:right": "yes", "parking:right:orientation": "diagonal"}
},
{
"old": {"parking:lane:right": "parallel"},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"replace": {"parking:right": "yes", "parking:right:orientation": "parallel"}
},
{
"old": {"parking:lane:right": "perpendicular"},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"replace": {"parking:right": "yes", "parking:right:orientation": "perpendicular"}
},
{
"old": {"parking:lane:right:parallel": "on_street"},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tordans
Copy link
Collaborator

tordans commented Dec 19, 2024

@SupaplexOSM could you have a look at the tag update definitions – you will spot issues that might be there more easily than me.

Update: He messaged me with a "looks good at first glance"

@tordans tordans self-assigned this Dec 19, 2024
Copy link
Collaborator

@tordans tordans left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good to be merged.

We could argue to remove the "parking:both": "yes" which is not the ideal migration scenario. In my migration tool https://osmberlin.github.io/osm-tag-updater/#/manual I did not use this migration path but instead told users to add the proper value. But we don't have this kind of tooling for iD easily available and the UI handles the case quite OK:

(Testlocation)

Migration info:

Bildschirmfoto 2024-12-20 um 17 10 54

Which then shows as "unspecified" in the UI, which I think is OK:

Bildschirmfoto 2024-12-20 um 17 11 02

I will merge this now in order to get it going and maybe improve upon it later.

@tordans tordans merged commit 02d1552 into openstreetmap:main Dec 20, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

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