[OSM-dev] Questions about TIGER import

[Dave Hansen]

On Mon, 2007-08-13 at 19:45 -0500, Nolan Darilek wrote:
> 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.

The nodes are tagged with the original TIGER data sources so that we can
go and add the address data at a later time.  However, there is no
address data itself in the TIGER import.

> 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.

We simply don't have the mechanisms in OSM today to support the objects
between nodes in a way having any kinds of tags.  There is no way to say
that the part of way 99 between nodes 22 and 44 have these tags.

> 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.

Nope, we don't touch RT7, yet.  I was just looking at including the
towns/cities/village points that we can get from TIGER.  That stuff is a
piece of cake compared to the roads.  If the current import continues
well, I'll probably do those next.

-- Dave