<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt">> Then, decide how if/when it is appropriate to write over the old TIGER<br><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;">> stuff with new. Or, to merge it somehow.<br><br>Be very, very careful here.<br><br>Conflation is a difficult thing. I used to work at Tele Atlas, and there was a major project to conflate Tele Atlas North American data and GDT data (a company they just acquired). They had at least a hundred people committed full time to completing the task in a year (I don't know the exact number), with tens of millions in funding - and they failed in a big way. The head of the North American division got axed as a result.<br><br>If there's a particular layer that has useful
info, that's not already present - that could be imported successfully. Otherwise, the most useful thing would be some sort of set-up where someone could view changes to the new TIGER data simultaneously with the OSM data, and choose what to import. Or - if you can determine if a whole region was untouched - replace previously imported data with new data.<br><br>What you don't want to mess up is the careful work people have done to improve the quality of data in a region manually. If you try to merge data automatically without careful oversight, you could destroy a lot of hard work. A one-time import - to create a starting point for people to edit - makes all the sense in the world. Subsequent updates are a much harder thing.<br><br>-Alan<br></div></div></div></body></html>