<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ian,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Coming at it from a time perspective, I would want to just to remove the old stuff and replace it with the new stuff. There maybe a few cases where someone updated a road centerline in OSM that is not in the new GIS dataset, but in my opinion this would be pretty rare and it would take forever to compare each line one by one on an import. The counties do a good job keeping the road centerlines accurate because they have to for E911 purposes. At least for horizontal accuracy, names and even address ranges. The exception might be if an OSM users adds a tag like speed limit.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would much rather see OSM have 98% of the road centerlines by correct for MN and see the update taking minimal time versus trying to compare every line for accuracy and having the process take years. I only think this is a valid point for road centerlines. I think there are other datasets that you would not want to take this approach in OSM like place of interest points, parks, buildings, etc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If you want me to get you a County road centerline file let me know, I’m sure I can come up with some county in MN (maybe Douglas, Rock or McLeod) that I could give to you. This might be a good way to test your methodology for an import tool, at least with road centerlines.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Just my 2cents.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Brian Fischer,</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#595959'>CFM GIS Project Manager<br><b>Houston Engineering, Inc.</b><br>Phone: Direct: 763-493-6664 / W: 763.493.4522 / M: 763.229.2734<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> tcmug-bounces@lists.osgeo.org [mailto:tcmug-bounces@lists.osgeo.org] <b>On Behalf Of </b>Ian Dees<br><b>Sent:</b> Thursday, August 19, 2010 10:29 AM<br><b>To:</b> tcmug@lists.osgeo.org<br><b>Subject:</b> [TCMUG] How do you match up two datasets?<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi TCMUG,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I've been pondering a way to help people import into OSM while respecting the existing data. To that end, I'm wondering if anyone on the list could talk about how they would go about applying one (newer, presumably better) dataset to another. I'm thinking of the usecase where MetroGIS has old street centerline data from 1990 and receives an update from 2010. How would you go about doing that? What tools would you use and what are they called?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I'm envisioning a web map that allows you to view the new data as an overlay on the existing data, marking whether or not to import each new feature and how the import should happen (completely remove old stuff and replace with new stuff, update the metadata on the old stuff with the new stuff, or something else). However, when there are a gazillion things to import, it might not make sense to do that one-by-one.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks for your thoughts!<o:p></o:p></p></div><div><p class=MsoNormal>Ian<o:p></o:p></p></div></div></body></html>