[Imports-us] Update on TIGER realignment import
enf at pobox.com
Tue Aug 6 05:47:54 UTC 2013
By the way, the reason way 8824221 isn't relocated is that
node 63427987 can't be moved because it is connected to
node 63427990, which can't be moved because it is connected to
node 63752642, which is part of TLID 76026066 (in way 8824375),
which was both moved and renumbered in the TIGER revision, so we don't know
anything about where it is supposed to be.
This is unfortunate, but I think it's the appropriate conservative choice
The bug is that it didn't also keep node 63427986 from being moved. It let
it through because it had a new location on one side for connected node
63427985, and the other connected node 63427987 is within 25 feet of the
location of a TIGER 2010 intersection, even though it's the wrong
I'll add an explicit check for crossed roads to keep this from happening
again. Thanks again for finding and reporting it.
On Mon, Aug 5, 2013 at 9:05 PM, Eric Fischer <enf at pobox.com> wrote:
> Ouch, that's unfortunate about the road crossing over itself. I thought I
> had made sure that wouldn't happen, but clearly I didn't think of all the
> possibilities. It's great to have a case where it is known to happen so I
> can make sure I really fix it in the next round.
> Thanks to everyone who downloaded a file and looked through it! I'll also
> exclude Massachusetts from future runs so that the false positives don't
> lead to unnecessary tiny edits.
> On Mon, Aug 5, 2013 at 8:42 PM, Josh Doe <josh at joshdoe.com> wrote:
>> On Mon, Aug 5, 2013 at 1:49 PM, Eric Fischer <enf at pobox.com> wrote:
>>> Hi everybody. It's probably time for me to stop just talking about
>>> importing the TIGER realignment and actually do something.
>>> Last night I reran the program (
>>> https://github.com/ericfischer/osm-tiger-update) to generate .osc files
>>> for the entire realignable country. If anyone wants to take a look, I've
>>> started uploading them to http://trafficways.org/tiger/out/ but they
>>> add up to more than 4GB and will take a few more hours to finish copying
>>> from my slow home network.
>> Looks quite good after checking a few places in Fairfax County, VA. I did
>> notice one oddity after merging it (
>> http://trafficways.org/tiger/out/51059-0000.osc) with current data, as
>> two nodes in a way cross over each other (JOSM screenshot
>> http://snag.gy/29CHO.jpg). Also, and probably related, is that one of
>> the ways doesn't seem to get updated, even though it and the constituent
>> nodes haven't been edited by anyone:
>> http://www.openstreetmap.org/browse/way/8824221 (merge the above OSC
>> file with the area around this way)
>> If this happens with any regularity, it would be good to document this in
>> the wiki. Even with this small issue, it is on the whole a great
>> Imports-us mailing list
>> Imports-us at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Imports-us