[OSM-dev] Rendering of TIGER data (and a new version of the scripts)

Dave Hansen dave at sr71.net
Fri Aug 10 00:07:39 BST 2007


First of all, I have a new version of the conversion scripts, fixing
some bugs, but no complete show stoppers.

	http://sr71.net/~dave/osm/tiger/tiger-to-osm-v0.6.tar.gz

I've uploaded Hood River County, Oregon, and it was in the last planet
dump.  It is now appearing on the map:

	http://www.openstreetmap.org/index.html?lat=45.7090343713106&lon=-121.52713777738832&zoom=16

I quite like how it looks.

The entire US is still available for download here:

	http://sr71.net/~dave/osm/tiger/counties/

But, I'll be replacing those over the next few days as I re-run with the
latest version.

Changelog from v0.5:
- There was an occasional glitch in the data, mostly with long forest
  service roads where it looked like the segments weren't put in place. 
  I found the cause:
	rt1_record.rt2_records.sort! do |a,b| a[:rtsq] <=> b[:rtsq] end
  That was sorting a number *ALPHABETICALLY*, and would assemble some of
  the TIGER ways into OSM ways in the wrong order
- Stopped outputting ways with no segments.  This was a byproduct of not
  fully deleting ways when they were coalesced into another.  I also
  released an extension to the JOSM validator plugin to find and fix
  these, just in case you have them in a data file. 
- slightly reduced memory footprint, again
- will hopefully skip over missing (but non-critical) TIGER shapefiles
- Don't feed "raw_tags" into the tags_to_feature_type() function,
  because the raw ones aren't real strings


-- Dave





More information about the dev mailing list