[OSM-dev] Questions about TIGER import

[Nolan Darilek]

I was recently looking over the TIGER data specification. Man, if  
there's ever a case to be made against format design by committee,  
the TIGER specification is it. :)

I know that OSM doesn't yet support addresses in any standard way. My  
understanding is that the current TIGER import tags nodes with this  
information so we'll at least have it for future work. If this is  
true, my question is whether or not we're tagging address ranges in  
terms of which side of any given segment are even and which are odd?  
In looking at the spec, it seems like this information is included,  
but I'm not sure if we're including it in our proposed imports. If  
not, I'd like to urge its inclusion and to discuss mechanisms for  
tagging it.

I'm also curious, do the TIGER scripts import RT7 (I.e. landmarks?)  
There are a few for my county which would be cool to have, I'm just  
not seeing them in my imports of the map, but it's possible that my  
importer has goofed and isn't noticing them in its criteria for  
determining whether a given node is a POI or part of a segment.

But that isn't as big of a deal to me as encoding which side of a way  
contains even addresses and which odd. :)