<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.73">
<TITLE>Re: [OSM-talk] Merging data sets (was: web site map enhancement,los angeles)</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>A source identifier attributes makes a lot of sense. Although, I </FONT>
<BR><FONT SIZE=2>would make it a bit more generic, say <tag k="Source" v="TIGER" />. </FONT>
<BR><FONT SIZE=2>The reason for this is that other governments may release road </FONT>
<BR><FONT SIZE=2>network layers that could potentially be imported into OSM. There are </FONT>
<BR><FONT SIZE=2>actually two recently released, publicly available Canadian road </FONT>
<BR><FONT SIZE=2>network layers. One produced by Statistics Canada, which is similar </FONT>
<BR><FONT SIZE=2>in nature to the US TIGER/Line road layer, that uses a combination of </FONT>
<BR><FONT SIZE=2>Statistics Canada and Elections Canada data. The second, which is </FONT>
<BR><FONT SIZE=2>distributed by Natural Resources Canada, and uses data from local </FONT>
<BR><FONT SIZE=2>provincial and municipal governments along with NRC's own data. At </FONT>
<BR><FONT SIZE=2>some point, someone may consider uploading parts of one of these two </FONT>
<BR><FONT SIZE=2>layers into OSM, so a more general data source identifier would be </FONT>
<BR><FONT SIZE=2>useful.</FONT>
</P>
<P><FONT SIZE=2>Dan</FONT>
</P>
<P><FONT SIZE=2>On 7-Apr-06, at 3:01 AM, Etienne Cherdlu wrote:</FONT>
</P>
<P><FONT SIZE=2>> On 4/7/06, Tom Carden <tom@tom-carden.co.uk> wrote:</FONT>
<BR><FONT SIZE=2>>> On 4/7/06, Dan Karran <dan@karran.net> wrote:</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>> I also believe it should be a manual process, but with the amount of</FONT>
<BR><FONT SIZE=2>>>> data in question, that process is going to have to be simplified to</FONT>
<BR><FONT SIZE=2>>>> avoid overwhelming users with masses of data. As Imi says, we need</FONT>
<BR><FONT SIZE=2>>>> coders. If only I knew Java... (I sense the onset of a sharp </FONT>
<BR><FONT SIZE=2>>>> learning</FONT>
<BR><FONT SIZE=2>>>> curve)</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>> Using the API, you could write a tool in whatever language you </FONT>
<BR><FONT SIZE=2>>> wanted.</FONT>
<BR><FONT SIZE=2>>> This is a specialised task, not one that the main OSM applet really</FONT>
<BR><FONT SIZE=2>>> needs to be able to deal with all the time.</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> If TIGER data was imported with, say, <tag k="TIGER" v="true"/><tag</FONT>
<BR><FONT SIZE=2>> k="read-only" v="true"/> then it would be possible for the server to</FONT>
<BR><FONT SIZE=2>> reject regular updates to these nodes and segments. If there was then</FONT>
<BR><FONT SIZE=2>> some easy way to copy elements from this 'layer' to the normal layer</FONT>
<BR><FONT SIZE=2>> we could have the best of both worlds.</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> Rendering clients could choose whether to display or ignore TIGER</FONT>
<BR><FONT SIZE=2>> data, depending on what they are trying to achieve.</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>>> Regarding import of TIGER as a static 'gps-like' layer - do people</FONT>
<BR><FONT SIZE=2>>> really think manually tracing and correcting TIGER on OSM would be a</FONT>
<BR><FONT SIZE=2>>> useful application of their time? I would think that even for areas</FONT>
<BR><FONT SIZE=2>>> with a reasonable amount of existing data, TIGER would be at least an</FONT>
<BR><FONT SIZE=2>>> order of magnitude more complete right now. With respect to those</FONT>
<BR><FONT SIZE=2>>> who've been working on OSM in the US, I doubt we'd be losing much </FONT>
<BR><FONT SIZE=2>>> (but</FONT>
<BR><FONT SIZE=2>>> of course we should check).</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> There is significant work that has been done in the Washington DC</FONT>
<BR><FONT SIZE=2>> area. Apart from that I've dabbled in California a bit. I don't know</FONT>
<BR><FONT SIZE=2>> of anything else.</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> I doubt that much of the stuff that I did in California (canyon</FONT>
<BR><FONT SIZE=2>> walking) will be in TIGER, although I'm sure all of the freeways will</FONT>
<BR><FONT SIZE=2>> be (but are HOV lanes, for example, recorded separately in TIGER?).</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> Etienne</FONT>
<BR><FONT SIZE=2>> (Forgot to reply to the list again)</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> _______________________________________________</FONT>
<BR><FONT SIZE=2>> talk mailing list</FONT>
<BR><FONT SIZE=2>> talk@openstreetmap.org</FONT>
<BR><FONT SIZE=2>> <A HREF="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk" TARGET="_blank">http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk</A></FONT>
</P>
</BODY>
</HTML>