Apologies for the huge bbox, this revert also caught some hospitals in Algeria imported by the same mapper; I will review them later.

Apologies for the huge bbox, this revert also caught some hospitals in Algeria imported by the same mapper; I will review them later.

Apologies for the huge bbox, this revert also caught some hospitals in Algeria imported by the same mapper; I will review them later.

Apologies for the huge bbox, this revert also caught some hospitals in Algeria imported by the same mapper; I will review them later.

Yes, we have "unclear license", "undiscussed import", "no conflation", "lots of useless GIS tags" all rolled into one - the faster this is gone the better. Even if the importer were to fix the problems manually, it would take them weeks - and we expect that the problems be fixed BEFORE upload not after.

This is broken in so many ways. I will remove all of it.

Please do not use changeset discussions to publicly speculate about the mental health of other people. Say "This vandalism has no place in OSM" instead of insulting the person.

Thank you, that should settle things once and for all, hopefully.

Changing landuse=FIXME to landuse=fixme adds zero information and creates an useless, world-wide changeset. Don't do that. Also, please use better changeset comments (an appropriate changeset comment for this would have been "changed landuse=FIXME to landuse=fixme world-wide").

Please note that should you be making these edits in the course of a business activity, the "organised editing guidelines" require that you clearly explain whom you are working for.

Individually mapped trees are not "spam tags". For many people, a tree is more important than some obscure realty business's opening hours. Don't delete trees.

Hallo Yves, wo finde ich die amtlichen Karten von 1891, von denen Du in diesem Changeset sprichst?

Marked paths as private in osm.org/changeset/120860369 after not having a response from you here, even though you've been actively mapping.

The complaint read: "Votre application indique un passage sur un chemin privé et au sein d’un pré dont l’accès est strictement réservé aux propriétaires et locataires.

Plusieurs applications publiques utilisent vos données et cela pose aujourd’hui un vrai problème et de nombreuses incivilités.

Face aux agressions quotidiennes, je vous demande de bien vouloir retirer l’accès de ce chemin à vos usagers et utilisateurs divers de données."

Can you please point us to the discussion and documentation that are mandatory before executing such an import?

Dear Diego_V, can you clarify the license of the data set that you have imported here? The site you specified as a source is not reachable anymore. If the data is not under a suitable open license, I am afraid you will have to delete it again.

I have requested that HaPe-CZ communicate in English when mapping in the US, and also fix the damage done here: osm.org/user_blocks/5977

@BCNorwich, @Vormond, could one of you at some point in the near future perhaps double-check that this path and this gate accurately reflect the situation on the ground (possibly also upload a photo of potential signage somewhere)? The DWG has received a complaint asserting that this path does not exist. (DWG Ticket#2022042810000131)

Alten Namen in osm.org/changeset/120301918 wieder hinzugefügt und Benutzer für 2 Wochen gesperrt.

Ja, man sollte das aufräumen. Leider produziert der Benutzer kjon schneller neue unsinnige Daten (osm.org/changeset/119748620) als wir die alten wegräumen...