Hi Tekim, yes I can. I will do that when I'm at my desk.

Hello Tekim,

No one seems to have a problem with the contents of my changesets so far, only with the method, which I think is ridiculous because it's one of the few ways to get this kind of thing done.

I wouldn't call it a mechanical edit, because I reviewed all of the tag combinations before I changed them to avoid losing any information.

If you have suggestions to update deprecated and misspelled tags, I'm all ears.

Best regards

Casper

I can't code, so automating this process is out of the question for me, but I have figured out a workflow with taginfo, overpass turbo and JOSM to update deprecated tags reliably on a large scale.

If you have the skills to automate this process with smaller bboxes, I invite you to create a bot like that, so we can feed it deprecated tags to update.

Hi Michael,

These changesets need to be done globally to avoid fixing the same thing six or more times. As someone else I spoke to has pointed out: "Honestly it needed doing."

If it helps you, I will make a separate changeset for the German-speaking countries next time.

Best regards,

Casper

That would take me 4 to 6 times as much time with no real benefit. I would understand this request for smaller changesets, but the ones I made yesterday were just too big for that.
---

Published using OSMCha: https://osmcha.org/changesets/108430155

I only just noticed, lol. These bboxes need to be big so I can save myself some time.

Thank you for the reply.

I would prefer that you create a second account that you use to only or mostly delete things, because that would be perfectly valid and also much more helpful than bothering other mappers while you can just press delete yourself.

(If you chose to do it this way, an easy way would be to open iD in a different browser and simply delete outdated data with that, because I suspect that's faster than relogging in JOSM. )

Hello JriSv250. Can you please stop reusing nodes to mix the history of objects? See osm.wiki/Keep_the_history#Don.27t_mix_the_history for reference.

Mixing the history of objects makes it difficult for analysers and contributors of data to understand how and when certain data was made. Not only I, but also many other people (see the discussions on Discord) strongly advise against this practice.

Thank you in advance.

Kind regards,

Casper

My apologies for removing the information and thank you for restoring it. As you can read from my changeset comment, removing information wasn't part of the plan.

Hi. Thank you for the notice. The issues I fixed are barely worth mentioning, like fixing an opening hours syntax. I'll do my best to make smaller changesets in the future. Enjoy your weekend :)

Hello again Shaho Reza. I asked it before and I will ask again: could you please write comprehensive changeset comments according to the guidelines?

Since I got no response and the changeset is full of errors, I'm reverting this.

Hello. Could you write more specific changeset comments, please? See osm.wiki/Good_changeset_comments for more info.

Hello. What did you do with these roads and routes in this changeset? Single roads shouldn't have a route on them, let alone two. Also, way/643674367 and the one next to it don't look like trunk links to me, because they don't link a trunk to a different classification.

Hoi Sregels.

Je hebt hier twee bruggetjes ingetekend die niet verbonden zijn met het wegennet. Om errors te voorkomen is het verstandig om deze of met het wegennetwerk te verbinden of als een vlak met man_made=bridge te mappen.

way/956403544 heb je ook getagd met tags als bicycle=no, foot=yes, horse=no etc etc. Het is veel makkelijker om deze simpelweg als highway=footway te taggen, Dan heb je alleen nog een access=* tag nodig, indien van toepassing. Waarom staat er access=no op?

Mvg,

Casper

Hi Guillaume,

Thank you for bringing this to my attention.

This was a very rare key, and as such I already regarded it as either a mistake or as obsolete.

Kind regards,

Casper

you're welcome :)

Ik ben het eens met A67-A67.

changeset comment klopt niet, is ander fort

Hallo vrondisjeuk. Bedankt dat je interesse toont. Ik zal vertellen hoe ik dit gedaan heb:

Ik heb met https://overpass-turbo.eu/ gezocht naar dorpen zonder wikidata tag. Dat heb ik in de JOSM editor gedownload. Vervolgens heb ik elke plaatsnaam bekeken en vergeleken met wikidata.org.

Als ik in Wikidata de plaatsnaam met omschrijving "village in Groningen" of iets dergelijks vond, dan was dat natuurlijk de juiste combinatie van dorp in OSM en Wikidata object, en zo heb ik die Wikidata-tags aan OSM-objecten gekoppeld.

Ik zie dat je een redelijk nieuwe mapper bent. Als dit ingewikkeld voor je klinkt, zeg het dan gerust, ik leg graag de stappen in meer detail aan je uit.

Met vriendelijke groet,

Casper