this is a good one because i had a back and forth discussion with somebody that 
was 
calling me out on my edit because from space this looked like a flat surface 
and then explaned
how to list it as non active.
 
https://www.openstreetmap.org/way/802256628#map=16/42.1110/-87.8160
 
but the thing is the river was a 10 year old 81 mile download that maye should 
not be as to the Wiki.
and this guy must be a river freak just like the bus stop guy who thought he 
own the map.
  
>Wednesday, June 10, 2020 2:26 PM -05:00 from Mateusz Konieczny via talk 
><talk@openstreetmap.org>:
> 
>Can you link any specific changeset damaging data
>or object that was deleted and should not be?
> 
>Linked ones
>http://nrenner.github.io/achavi/?changeset=86230442
>http://nrenner.github.io/achavi/?changeset=85357849
>appear to not be problematic
> 
>(  https://www.openstreetmap.org/relation/233949#map=9/41.8982/-87.7286
>is on boundary of unreasonably large relation, but it is not
>something very problematic)
> 
>Jun 10, 2020, 15:27 by talk...@openstreetmap.org:
>>    Last week I edited a 10 year old, 81 mile  MultiPolygon with GHOSTS in 
>>the ID editor, all I know, Someone
>> 
>>took offence to that,   
>>https://www.openstreetmap.org/changeset/85357849#map=13/42.0813/-87.8854
>> 
>>and attacked all my edits of that day, and as he moved from north to south, 
>>every thing I did for the
>> 
>>last year.    https://www.openstreetmap.org/changeset/86230442  , with things 
>>other people had already
>> 
>>called me on, (discussion). so    exposing  my self everything I have done in 
>>the last 24 hours is under question
>> 
>>from people who are not local but in Europe. even my visit to the golf course 
>>is in question a 7 year stale edit.
>> 
>> 
>> 
> 
>_______________________________________________
>talk mailing list
>talk@openstreetmap.org
>https://lists.openstreetmap.org/listinfo/talk
 
 
 
 
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Reply via email to