Talk:TIGER
From OpenStreetMap
Contents |
One way streetmap
Has any movement happened on the tiger files. As soon as they are imported I think it would be great to start a distributed one way project. If that were completed this would be on par with commercial data. -- User:Dcsmith77 - 07:28, 8 March 2007
TIGER -> .osm file ruby script is ready
We have ruby scripts producing .osm files that can be opened in JOSM and viewed. I can give the scripts to anyone who would like them, or I can produce one and send you any county you like. We need to sanity-check these things to make sure the scripts are behaving themselves. Just email dave [at] sr71 [dot] net. - DaveHansen 06:08, 19 June 2007
JOSM mapping overwritten?
What's going to happen to JOSM-drawn U.S. content when the TIGER data is imported? Is it going to get overwritten? I.e., is there any sense in users working on U.S. data before then? Thanks. raf 06:55, 20 February 2007 (UTC)
Current Status?
Did a bit of a tidy up on this page just now, to try to clarify the current status, and separate out info about the previous 'initial run'.
I might be misinterpreting things. There was an initial run which was abandoned and data purged, and the import script is not running currently (still under development) right?
Well anyway feel to free to tidy up my tidying if it was wrong! -- Harry Wood 15:43, 1 March 2007 (UTC)
$200 million contract
Wowzers! I just surfed onto the TIGER Accuracy Improvement Project. Hey there U.S.! We'll improve your TIGER data for a donation of $200 million! -- Harry Wood 09:48, 7 June 2007 (BST)
Merging TIGER and non-TIGER data
Is there a general strategy for merging TIGER data where there is existing data? Here's what I'm thinking:
- Download a county's worth of pre-TIGER data from the OSM server.
- Save it to a local file (because it is in some respects better than the TIGER data).
- Delete that data from the OSM database.
- Import the TIGER data into the OSM database.
- Tweak the new TIGER data in the OSM database, using the previously saved pre-TIGER data -- e.g. opened as a separate layer in JOSM -- for reference.
Rationale:
- I can't see a way to easily merge features from one layer to another in JOSM.
- No layer support in the database itself. Otherwise we could have TIGER and pre-TIGER data in different layers temporarily.
- Don't want to delete any TIGER data, because of all the extra attributes it carries.
Pitfalls:
- People may be perturbed when their work is deleted. How could I push my pre-TIGER snapshot of the given county to them?
Specifically, this is for Santa Clara county, California. I think 95% of the pre-TIGER data there is from me, anyway. I have converted the TIGER data to OSM for this county -- it's just sitting in a file for now.
Thoughts? --raf 04:13, 6 October 2007 (BST)
Rivers?
Doesn't the TIGER data have rivers? There should be a river running through Reno for example.
Actually I mention this example because I was comparing our Reno map with one here which was produced as a one man effort by somebody with a python script back in 2004. I was about to pitch in on the discussion there, and mock* their puny TIGER rendering effort. But actually... hmmm.... we seem to be missing a river.
*I mean... invite them to join our better project.
-- Harry Wood 16:13, 20 December 2007 (UTC)
