[OSM-dev] TIGER upload automation

[Dave Hansen]

On Fri, 2007-08-31 at 00:07 +0100, Robert (Jamie) Munro wrote:
> Dave Hansen wrote:
> > If somebody wants to put together a correlation between number of OSM
> > objects in a county and its population and prioritize counties with a
> > low number of OSM objects per capita, I might be more compelled.
> 
> Full spreadsheet (tab separated text)
> http://arjam.net/population.txt
> 
> Upload queue format:
> http://arjam.net/upload-queue.txt
> 
> NY/TGR36061.ZIP,New York contains 1025 people per way.
> 
> TX/TGR48301.ZIP,Loving contains 0.06 people per way.

It's hard to argue with that.

I haven't adopted the entire queue that you posted, but I did move some
of those large counties up to the head of the queue after my Oregon
counties.

But, before we actually go and process them, we probably need to get in
contact with the mappers in those areas to see what they want done with
their existing data.  I really hate to create a big mess by uploading
over their data, but I'd also hate to just destroy it.

One note: all of the TIGER uploads from here on out will have a tag like
tiger:county=County, STATE.  They also have a
'tiger:upload_uuid=YYY-ZZZ...' tag.  That's just in case I manage to
upload a county twice, hopefully it will have two different uuids.  It
also makes it possible in JOSM to search and unselect the TIGER data.
This is probably a good nugget for the wiki if anyone's keeping
track. :)

-- Dave