[Imports] TIGER realignment import

Eric Fischer enf at pobox.com
Wed Aug 7 05:22:05 UTC 2013

I don't quite understand what is going on here because the node that you
have numbered -1708 is -314 in my file (06013-0000.osc)  It is included
because Norine Drive (way 7864991) was reshaped in the new TIGER.

In 16045-0000.osc, node 129052498 would have been included because one of
the ways that contains it was relocated in new TIGER, but I didn't include
the way in the .osc because it didn't have any nodes added or removed, just
relocated. I can add the ways to the output even when they aren't necessary
if it makes things clearer.


On Tue, Aug 6, 2013 at 9:44 PM, Bryce Nesbitt <bryce2 at obviously.com> wrote:

> I looked at three counties I'm familiar with.  In two of them the changes
> were so scattered, so minor, as to to offer some risk but no benfit.
>  Perhaps you could eliminate these very sparse areas, and focus on the big
> swaths of poor data?
> I see a lot of mystery nodes sitting all by themselves, and wonder what's
> up with that. For example:
> Node: -1708
>   Data Set: 539a1a11
>   Edited by: <new object>
>   Coordinates: 38.00206, -121.861428
>   Way: Norine Drive (7864991)
> Node: 129052498
>   State: modified
>   Data Set: 27b2e123
>   Edited by: <new object>
>   Version: 4
>   Coordinates: 44.404665, -116.212349
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20130806/8985f5ba/attachment-0001.html>

More information about the Imports mailing list