[OSM-talk] Is edit adding private dataset created specially for OSM considered an import or not?

[Mateusz Konieczny]

Feb 3, 2021, 16:25 by osm at dead10ck.com:

> I > don't > think there's any reason to just jump right to reverting a large change. 
>
Definitely, I am not planning to revert anything immediately - whole point
of writing to them, documenting issue etc was to avoid revert and fix it.

I admit that I am positively surprised, that they reacted and I see that they are fixing
problem right now - see now much smaller
https://www.openstreetmap.org/relation/10953749#map=13/0.0383/29.2350- thanks!

I have not really believed that it will happen.

Last time when I found something similar
I tried to contact organization doing this, after month someone claimed that they will definitely fix it,
I waited for months, asked again, got the same reply,  waited again and then in ended in nothing.

In the end I gave up. So I admit that I expected the same here.

I renamed page to make it less aggressive and tweaked some wording.


> If the data is good, then there is absolutely no reason to revert it, other than spite because they "broke the rules." 
>
Though note that data of good geometries that is a copyright violation is not a good data. 

> But it doesn't sound like your concern is the quality of the data.>  
>

It is. If data would be OK I would not be even checking how it appeared.

Source was not explained or documented at all.

It had fake strip of farmland along edge of edited area
https://www.openstreetmap.org/note/2523318

Farmland used as fill over entire area
https://www.openstreetmap.org/note/2523319#map=19/0.09717/29.00294

I was planning to complain here about multipolygon with 933 ways but it is getting fixed :)
See https://www.openstreetmap.org/relation/10953749 - now just 282 ways and it opens
now in iD without trouble at least on modern computer.

Though I still think that it is a bit oversized.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20210203/f121d991/attachment.htm>