[OSM-dev] Problems with TIGER Conversion

[Dave Hansen]

On Thu, 2007-07-12 at 02:32 -0700, Al Wold wrote:
> Dave,
> It looks like I'm getting missing data (I think mainly entire ways are
> missing) with the 0.3 version.  I had a file that seemed more complete
> from an earlier version, which I think was 0.2.  I'm regenerating with
> 0.2 and I'll see how it looks when it finishes.  If you want more
> details on what is missing, let me know.  If you don't have time to
> look into it, I may have some time to dig into the code tomorrow.

Gah.  I'm noticing the same thing with larger files.  My own street is
messed up. :)

> The stuff from the earlier version was looking pretty good. I did
> notice that it doesn't seem to incorporate the address ranges.  I
> think you said earlier that the original tiger attributes were being
> carried over so it could be done later, but I don't see them in either
> the ways or segments.  It probably has to be tagged in the segments
> right? 

The nodes and ways have their original tiger attributes in them.  That
means that we can find an individual, original tiger feature, given a
node or way.

> I've got the ruby script to create excerpts from the converted files
> to a decent state, and if you use it to cut the file into decent sized
> blocks, JOSM is able to deal with them without any trouble.  I've
> attached the script for anyone that wants to try it out. 

Hmm.  Perhaps we should integrate this into the actual converter.  Were
there any tricky bits that you ran into?

-- Dave