Curtis L. Olson wrote:
I'd be interested in working with the Tiger data as well. Did you
create any code to parse/chop the data?
If I had a chance to work through the process I might be able to track
down some of these problems/issues.
I got myself a copy of the 2004 Tiger data in shapefile format from
http://xastir.tamu.edu/2004/ (which unfortunately seems to be down at
the moment) - I'm sure it's available elsewhere.
Then I used ogr2ogr (from the gdal package) to extract the information I
was interested in from the shapefiles, and fed it to shape-decode. This
can probably be done far more efficiently if shape-decode is modified to
understand the Tiger data types. Sorry for the linebreaks:
ogr2ogr -where "CFCC like 'A11' or CFCC like 'A21'"
split/CA_San_Francisco_County-Motorway.shp CA_San_Francisco_County.shp
shape-decode --line-width 35 --max-segment 1000 split/$root-Motorway
$work/Tiger-Motorways Freeway
That gives you a directory full of polygons that you can then feed to
the tilebuilders.
Jon
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
