Should be reviewed.

Thanks for your reply!

👍

👍

You're welcome! I think there are sadly still a few corner cases like this. I designed the bot with the goal of not reverting an entire changeset, but instead trying to keep any "good" tags from a changeset. However, doing a full revert would definitely be much simpler for such spammy edits ... 🙂

Thanks @iandees

You're welcome! And thanks again for pointing it out. It's always helpful to get feedback, especially if something doesn’t work properly, so I can fix it quickly.

Thanks for the kind words, Christopher!

I'm really glad to hear that NeisBot is helpful, and it's great to see others in the community caring about keeping OSM clean as well. I'll keep doing what I can on the tooling side, and feedback like yours really helps keep the motivation up 🙂

Hi taxi777,

Could you please explain the reason for renaming several streets here from Ukrainian names to Russian ones?

Thanks.

Hi taxi777,

Could you please explain the reason for renaming several streets here from Ukrainian names to Russian ones?

Thanks.

Hi taxi777,

Could you please explain the reason for renaming several streets here from Ukrainian names to Russian ones?

Thanks.

Thanks for correcting
changeset/178845714 and changeset/179219443

Hi @CAM-Gerlach_Revert,

ah, thanks for noticing, good catch :)

My bot did not remove all added tags. I have fixed this in @NeisBot, so it should not happen again.

Best reagrds,
Pascal

Thanks for reverting @CAM-Gerlach_Revert

Hi CAM-Gerlach_Revert, CAM-Gerlach,

there are no "artificial limitations" involved here. As I wrote in the changeset discussion (changeset/179243590), this was caused by a bug in the bot’s rule set. The issue has been fixed, so this constellation should not normally occur again.

Best regards,
Pascal

Hi CAM-Gerlach_Revert,

I think something went wrong here. Both of your nodes contain spammy descriptions.

Best regards

Hi CAM Gerlach,

thanks for pointing this out.

In this case, the user changed the description from the added node (v1) to an updated version (v2), which was not properly covered by my bot’s rule set and therefore caused the incorrect revert. I have fixed the rule so this should not happen again.

Best regards.

Hi CAM Gerlach,

thanks for pointing this out.

In this case, the user changed the description from the added node (v1) to an updated version (v2), which was not properly covered by my bot’s rule set and therefore caused the incorrect revert. I have fixed the rule so this should not happen again.

Best regards.

Hallo,

dann bitte einmal die folgende OSM Wiki Webseite anschauen: osm.wiki/Organised_Editing

Danke und viele Grüße

Hallo,

in dem Link von Bing ist unten rechts (c) TomTom zu sehen. Ich bin sicherlich kein Linzenzexperte, denke aber dies kann/sollte genauso wenig als Quelle genutzt werden.

Verstehe ich es ansonsten richtig, dass der Account @navship als Importer für die Daten einer App genutzt wird?

Viele Grüße