[Talk-us] border screwup by ToeBee needs reverting
penorman at mac.com
Fri Mar 25 08:44:51 GMT 2011
The first of your examples ('015 node) appears to be more accurate than the
node it replaced in one of the ways,
http://www.openstreetmap.org/browse/node/263660932 which was farther away
from the monument (based on NAIP imagery)
In the second one ('476 node), the changeset improved the position of the
node. It wasn't aligned before. In any case, after the changeset it was only
about 8m off according to NAIP imagery.
I'd say that reverting the border fix changeset would be wrong, given the
number of problems it fixed with the borders. I'd say it was definitely
wrong to attempt to revert it over ToeBee's objections.
> -----Original Message-----
> From: Nathan Edgars II [mailto:neroute2 at gmail.com]
> Sent: Friday, March 25, 2011 12:56 AM
> To: OpenStreetMap talk-us list
> Subject: [Talk-us] border screwup by ToeBee needs reverting
> User ToeBee has, in several changesets in February, aligned state
> borders to exact lat/long. The problem is that this is not how the
> borders are defined; instead they are based on work that the 19th
> century surveyors did with the tools they had. Two obvious examples
> http://www.openstreetmap.org/browse/node/158796015/history is the famous
> "Four Corners":
> http://www.openstreetmap.org/browse/node/158790476/history is the
> northwest corner of Colorado, which is also marked by a large monument,
> visible on aerials.
> It's likely that any border node moved by ToeBee needs to be reverted. I
> tried to do this after informing him (he's currently denying there's a
> problem), but JOSM's reverter plugin is giving hundreds of conflicts.
> This damage needs to be undone.
> Talk-us mailing list
> Talk-us at openstreetmap.org
More information about the Talk-us