[Talk-GB] worrying edit to junction (now reverted)

[Ken Kilfedder]

Thanks for the suggestions, Edward and Robert.

I've added the old roundabout with a razed: prefix (https://www.openstreetmap.org/changeset/97833986 ) which will hopefully protect this particular junction from a recurrence.



---
https://hdyc.neis-one.org/?spiregrain
spiregrain_osm at ksglp.org.uk

On Wed, 20 Jan 2021, at 10:30 AM, Robert Skedgell wrote:
> I've done something similar at a farm in Essex redeveloped as very
> expensive housing. The new housing is clearly visible on Bing and Maxar
> Premium, but the older farm buildings which had been mapped previously
> are still in Esri Clarity. I've used the demolished: and removed:
> prefixes for buildings and service roads respectively, although razed:
> for both might have been better.
> https://osmcha.org/changesets/97558382/
> 
> On 20/01/2021 09:41, Edward Catmur via Talk-GB wrote:
> > One thing you can do is to leave the old ways in place, retagged with a
> > lifecycle prefix (probably razed:), and with dates if known. It won't
> > necessarily stop people replacing them, but it should give them pause.
> > 
> > On Wed, Jan 20, 2021 at 9:15 AM Jon Pennycook <jon.pennycook at gmail.com
> > <mailto:jon.pennycook at gmail.com>> wrote:
> > 
> >     Amazon had a habit of drawing old roads in construction sites,
> >     including putting old roads through the middle of new parks, based
> >     on old aerial imagery - all in areas that I had already mapped (and
> >     sometimes where I had supplied imagery to Mapillary). They reversed
> >     the changes when I noticed them, but it is annoying when people use
> >     old imagery. 
> > 
> >     Jon 
> > 
> >     On Wed, 20 Jan 2021, 08:40 Ken Kilfedder,
> >     <spiregrain_osm at ksglp.org.uk <mailto:spiregrain_osm at ksglp.org.uk>>
> >     wrote:
> > 
> >         __
> >         I write for advice on couple of related, very annoying edits
> >         that happened in my area yesterday.  One of the two users
> >         responded to a changeset message, and reverted the change.
> > 
> >         I suspect they were involved in doing mass or part-automated
> >         edits for Facebook.   The two offending changes are:
> > 
> >           * https://www.openstreetmap.org/changeset/97788019
> >             <https://www.openstreetmap.org/changeset/97788019>  /
> >             https://osmcha.org/changesets/97788019/
> >             <https://osmcha.org/changesets/97788019/>
> >               o (Remodelled a T-junction back to the roundabout it was 2
> >                 years ago - complete with entry lanes etc. a very nice job)
> >           * https://www.openstreetmap.org/changeset/97789682
> >             <https://www.openstreetmap.org/changeset/97789682> /
> >             https://osmcha.org/changesets/97789682/
> >             <https://osmcha.org/changesets/97789682/>
> >               o (Patched up the resulting gaps in route relations, etc)
> > 
> > 
> >         Like I say, the users have at least put everything back, and
> >         have engaged in conversation on the subject.   So it's not a
> >         matter for DWG.
> > 
> >         But my concern is that one of them has around 1000 edits to his
> >         name; and that the two user names *imply* dozens (hundreds?) of
> >         others a blundering about replacing accurate in-person mapping
> >         with nice-looking but incorrect data from who-knows-what sources?
> > 
> >         Is anyone keeping a log of similar incidents from FB mappers
> >         and/or our other corporate benefactors?
> > 
> >         Am I making a mountain out of a molehill?  Happy to wind my neck
> >         in, if so.
> > 
> >         ---
> >         https://hdyc.neis-one.org/?spiregrain
> >         <https://hdyc.neis-one.org/?spiregrain>
> >         spiregrain_osm at ksglp.org.uk <mailto:spiregrain_osm at ksglp.org.uk>
> 
> _______________________________________________
> Talk-GB mailing list
> Talk-GB at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>