Hi, please fix your editor. You are mixing up ways and nodes. This is the object you intended to fix: way/83992026

Reverted changeset that dragged a way halfway across the globe

changeset/178369402

Hi, I see that you deleted a lot of `
construction:railway:etcs=2` tags here. Does this mean that this railway no longer has any etcs signalling?

Thanks for pointing that out. I did not notice that the member relations were also modified. I've restored the original situation in: changeset/178039405

Reverted pokemon-go edits

changeset/178015318

Reverted pokemon-go edits

changeset/178015318

Reverted pokemon-go edits

changeset/178015318

Reverted pokemon-go edits

changeset/178015318

Reverted pokemon-go edits

changeset/178015318

Reverted pokemon-go edits

changeset/178015318

I appreciate what you were trying to do here, but you simply have to first make sure you are following the import guidelines. This is not optional.
osm.wiki/Import/Guidelines

A screenshot of the written permission can be linked on this page: osm.wiki/Contributors

Hello Aleksandar (and the others on your team no doubt),
Thanks for getting back to me so quickly.

I'll address that last point first. Woodpeck states that it "can be useful", I find it hard to interpret that as him stating that this import can go ahead.
The diary post itself is from almost 7 years ago, it talks about 4500 datapoints and one from a different source. The post itself talks about written permission, but I was unable to find this written permission myself.

The data that has been imported over the last 4 months itself amounts to over 28k datapoints and was imported with the knowledge that there were many glaring issues going on that would need to be fixed *after* the fact.

Most of these datapoints included incorrect tag usages and other data issues such as:
* mapping natural=coastline or natural=water as a point.
* Included the undocumented source:type or misused the source:name tag.
* The description and source:type tag seem to duplicate eachother a lot of the time, or simply state "Ø", which I interpret as empty or null.
* fixme tags stating that the exact location still needs to be determined.
* A lot of these objects were already on the map, leading to duplicate objects.
* Another undiscussed import by them 4 years ago left behind a number of `OFFICIAl=*` tags which are still there to this day. Meaning there is no guarantee all this data will eventually end up getting fixed. changeset/109415380
The import guidelines exist exactly to prevent thes sorts of things from happening. osm.wiki/Import/Guidelines

The issue with your team here is the copying of data from nodes to new or existing objects. You've essentially made it imposible to easily revert all this data due to the hundreds of changesets that moved the imported data onto existing or new objects.

I was not made aware of the fact that these names could be plainly found in available/usable topographic maps of Greenland. If this holds true, then I think it might be ok to just remove the source:type and description tags you and your team have copied over, but I will first need to have a closer look later when I have time available. I will get back to you with that.

In the meantime, please keep your efforts at fixing this import in Greenland paused.

See also my discussion with andershl here: changeset/176706570

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group

Hello,

Please cease attempting to fix this import in Greenland. It was undiscussed and will be reverted.

Also, in the future, please make sure the import you are attempting to fix was actually discussed by the community. Your involvement has made reverting everything significantly more complex.

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group

Hello,

Please cease attempting to fix this import in Greenland. It was undiscussed and will be reverted.

Also, in the future, please make sure the import you are attempting to fix was actually discussed by the community. Your involvement has made reverting everything significantly more complex.

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group

Hello,

Please cease attempting to fix this import in Greenland. It was undiscussed and will be reverted.

Also, in the future, please make sure the import you are attempting to fix was actually discussed by the community. Your involvement has made reverting everything significantly more complex.

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group

Hello,

Please cease attempting to fix this import in Greenland. It was undiscussed and will be reverted.

Also, in the future, please make sure the import you are attempting to fix was actually discussed by the community. Your involvement has made reverting everything significantly more complex.

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group

Hello,

Please cease attempting to fix this import in Greenland. It was undiscussed and will be reverted.

Also, in the future, please make sure the import you are attempting to fix was actually discussed by the community. Your involvement has made reverting everything significantly more complex.

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group

Thanks for being understanding.

I'll be honest here and say that it is a real shame that this needs to be reverted. This data probably is very valuable to have. But without a guarantee that OSM is allowed to use this data, or some systems in place to make sure that the data is imported without issues, there is just too much that can (or has) gone wrong. Take a look at the TIGER data that was imported in the US all the way back in 2007. People are still not done fixing all of that data. These things can be near impossible to fix after the fact. osm.wiki/TIGER_fixup

What I would recommend you do is go through the import process in full. Make sure the dataset is compatible with OSM, make sure the community agrees with this data being imported, and develop a more sophisticated import process that doesn't involve having to fix or conflate tens of thousands of objects after the fact.

Best regards,
Taya Snijder

I am going to ask you to pause your import immediately I'm afraid.

This is not how we do imports. Bad imports can have negative effects that can be impossible to revert and take years to fix. I am going to have to ask you to stop fiddling with the data you imported for the time being while everything can be reverted.

On OSM, imports have to follow the import guidelines as explained here: osm.wiki/Import/Guidelines

This ensures that we have permission to use the dataset that is being imported, that the community agrees with said data being imported, and that the data will be imported in a competent manner.

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group

Objecten zijn puur gekopieerd zonder bewerkingen. De reden hiervoor was om privégegevens te verbergen.