[OSM-dev] Guys I trusted you, I removed my checks...

Gregory Williams gregory.williams at purplegeodesoftware.co.uk
Tue May 19 13:26:53 BST 2009


> -----Original Message-----
> From: dev-bounces at openstreetmap.org [mailto:dev-
> bounces at openstreetmap.org] On Behalf Of Gregory Williams
> Sent: 19 May 2009 13:09
> To: OSM-Dev Openstreetmap
> Subject: Re: [OSM-dev] Guys I trusted you, I removed my checks...
> 
> > -----Original Message-----
> > From: dev-bounces at openstreetmap.org [mailto:dev-
> > bounces at openstreetmap.org] On Behalf Of Stefan de Konink
> > Sent: 18 May 2009 23:57
> > To: OSM-Dev Openstreetmap
> > Subject: [OSM-dev] Guys I trusted you, I removed my checks...
> >
> > ...but again this trust was misplaced. No, it is not Potlatch 0.9a,
> it
> > cannot be Potlatch is the perfect user tool and introduction to OSM.
> It
> > must be API 0.6 that didn't solve all our problems, as was promised.
> > Instead but it opened the gates of hell, a parallel universe within
> > OSM...[/melodramatic] [start fanfare tune + brass]
> >
> > http://api.openstreetmap.org/api/0.6/way/8115655/full
> >
> > http://api.openstreetmap.org/api/0.6/node/255483811/history
> >
> >
> > I probably have to blame myself; I was a fool to speed up my
> converter
> > by removing the consistency checks. But since when do we support more
> > than -180/+180 ?
> 
> Looking at the data, it was modified on 2008-05-11. That was within the
> API 0.5 timeframe. So surely it was the 0.5 -> 0.6 upgrade process that
> didn't catch the data anomaly, rather than the current API 0.6 code?
> After all, the data hasn't been changed since API 0.6 went live.
> 
> It's good to see that Iván has posted a very plausible reason for why
> those particular longitudes were getting shown. I found the location of
> the lake in question on Wikipedia and see that the latitudes have
> changed significantly as well. I've written a little bit of code to
> revert the nodes to their most recent valid positions and committed the
> result after checking that it looked reasonable in JOSM.

Ooops! I'd actually rolled it back two versions by mistake there (silly combination of looking for the previous version and a version with valid lat / lon in the code). Corrected now.

Gregory




More information about the dev mailing list