[OSM-dev] Map files for entire US (for download): use case for JOSM's layers?

[Dave Hansen]

On Thu, 2007-07-26 at 15:31 -0700, Al Wold wrote:
> The only reason I can think of is if we want to attempt to put the
> address range data into OSM for the initial load.  I think it's a good
> idea because it is probably pretty accurate, it is a piece of data
> that isn't much fun to collect, and will be highly useful for routing
> apps. 
> 
> I think it makes sense to just stuff it in however we can, then it can
> be rearranged later.  I have been meaning to play with the script and
> see if there's a way that makes sense, but I've been really
> busy/lazy. 

There simply isn't a good place to put it, other than the segments.  

The ways as they currently exist in the data span many address ranges
from the TIGER data.  Splitting the ways at this level would make a
very, very large number of ways and would render very poorly.  Avoiding
this was a primary reason I stared working on the scripts.

We could add a series of tags to each _node_.  But, those would have to
reference the ways, and we don't have any ways of maintaining integrity.
There would potentially have to be an address number in each node for
each segment and each way that touches the node.

OSM just doesn't have the data types to handle this right now.
Seriously, though, we have the TIGER tags for each of the nodes and can
recreate these data later on.

-- Dave