<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16625"></HEAD>
<BODY style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px"
id=MailContainerBody leftMargin=0 topMargin=0 CanvasTabStop="true"
name="Compose message area">
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV class=gmail_quote>
<DIV>> What are you envisioning when you say geo-diff? I'm interested in
geodiff tool too, but haven't been able to get anyone to come up with good ways
of visualizing the difference data.</DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>I did a SQL-based diff of TIGER 2008 -> TIGER
2009. This only looked for changes in named ways; adds and
deletes. Given separate OSM data sets of</FONT></DIV>
<DIV><FONT size=2 face=Arial> </FONT></DIV>
<DIV><FONT size=2 face=Arial> 1.) New ways - load into JOSM
as a separate layer. New ways that I accept and validate can just be
copied to the OSM data layer and stitched in.</FONT></DIV>
<DIV><FONT size=2 face=Arial> 2.) Deleted ways - load into
JOSM as a separate layer. I can validate and delete the ways from
the OSM data layer.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial> 3.) The final dimension to define
a full geo-diff is finding ways that have had nodes added, moved, or
deleted. Once again, load into JOSM, validate and apply to the OSM
data. It would be necessary to ensure that existing edits are
preserved - in most cases existing edits would be preferred and may already
contain the same fix as the updated TIGER.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>A geo-diff is less useful in cases where an entire
county has been refreshed from the county GIS data from more accurate data
because it would basically return the entire TIGER 2010 dataset.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV></DIV></BODY></HTML>