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

change field site_type to archaeological_site #720

Closed
b-unicycling opened this issue Dec 27, 2022 · 2 comments
Closed

change field site_type to archaeological_site #720

b-unicycling opened this issue Dec 27, 2022 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@b-unicycling
Copy link

I've tried this before being a complete newbie to GitHub, and I didn't succeed, so now I brought a picture to make myself understood.
site_type field
Can you please change the form for archaeological sites, so that both the form and the key say "archaeological_site" rather than "site_type", because site_type is deprecated.

There are now new sites being mapped with "site_type", because it hasn't been changed yet.

@arch0345
Copy link
Contributor

Duplicate of #677

This issue was fixed in f2eef8e, however this change won't appear in iD until the next release is published (the fix linked was from 2 weeks ago while the latest release was published 3 weeks ago)

@tordans
Copy link
Collaborator

tordans commented Dec 29, 2022

There are now new sites being mapped with "site_type", because it hasn't been changed yet.

Just to add to this: This will always be the case with OSM. Whenever we change tags we have to prepare to cleanup for at least a year or even longer until the old data is out of the "system" (tools, qa-tools, "heads"). For the update of parking-tagging we build a tag update helper and plan to create MapRoulette Challenges per Country to "accompany" the update process.

@tyrasd tyrasd added the duplicate This issue or pull request already exists label Jan 10, 2023
@tyrasd tyrasd closed this as completed Jan 10, 2023
@tyrasd tyrasd closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2023
@tyrasd tyrasd closed this as completed Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants