<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 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:0cm;
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;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think getting the address interpolation lines in from 2008
(rather than 2009) makes sense because it will match the geometry of unchanged
lines currently in the DB (about 89% of the Tiger road data has not been edited
as of now, it was 95% about 6 months ago)… <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'>We could take the lines from 2009, but then matching the roads
they go with could be more difficult… as a background to work on
the 2008 might be better and eaiser to match up. Unless we are thinking
of doing a full road update, then I think we should view this as completing the
import of 2008 by getting the addressing interpolation lines in where possible.<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 we associate the interpolation lines with the roads they apply
to, then when they are then edited in the future the addressing data is
updated. This is particularly important because we see a lot of arial
imagry editing of Tiger data (lots of people fixing roads and connecting
the disconnected tiger road segments). If this is how people are editing
areas then it is very difficult for them to get address data with it. So it
would be cool to get the address lines in with the data so its geometry is
corrected along with the roads geometry.<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'>As for detecting which roads to import, one approach is:<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'>1. Look at the last edit data and user id of the osm data, if
they are all still from the import then they are original and are eligible for
importing interpolation lines around. We could then filter furhter
out any lines that have addressing data on them already, or meet other criteria
(road type, proximity to well edited areas etc). We should be as cautious
as possible here and I think we will still hit most of the 89% yet to be edited.<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'>2. On these eligible lines, If the tiger tags are still
present, then we can use them to fetch the interpolation lines from
Tiger. However, if they are not present for a significnat portion of the eligible
roads then we can do a geometry match (we have planet line tables at CloudMade
in our data warehouse so we could do this…). If we are going to
match on geometry however, we might just want to do this from the start against
a load of the interpolation lines to see which are valid and skip step 1 (not
sure)…<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'>3. In the end we produce the list of interpolation lines to
import and associate.<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 think the idea here is exactly the same as the Tiger import….
It would be to give a back ground data set for people to work against and as
the tiger roads are fixed, the addressing data would be fixed at the same time…
<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'>We would also have a useful set of US addresses in OSM to work
with that would match the Tiger data and evolve with the Tiger data. As
we know, showing data like addressing in routing, maps and geocoding will
encourage people to get in and fix it </span><span style='font-size:11.0pt;
font-family:Wingdings;color:#1F497D'>J</span><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'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As for your point about county data, I agree completely…
we should also be importing county data sources as they come available and can
be validated. Tools that help do this are important. I think that
the tiger data is a valuable backdrop to do this against.<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'><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'>Jim<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'>Aschiell wrote>><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"'> Apollinaris Schoell
[mailto:aschoell@gmail.com] <br>
<b>Sent:</b> 17 September 2009 19:26<br>
<b>To:</b> Jim Brown<br>
<b>Cc:</b> talk-us@openstreetmap.org; tbook@libero.it; Matt Amos<br>
<b>Subject:</b> Re: [Talk-us] Tiger US address importing<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>definitely something which should be continued. but it's not
trivial.<br>
some considerations <br>
<br>
- 2009 update for tiger date should come soon. and hopefully it has less
errors. makes sense to wait for it<br>
- in areas where data hasn't been touched it's also very likely the areas which
are of bad tiger data. adding more broken data doesn't help osm at all.<br>
- areas which haven't been touched are most likely areas no one is interested
in. why clutter the database with more broken data.<br>
- how do you check that tiger data was not changed? You can't take the version
of a way and assume there was no change in geometry there is an ongoing
discussion about deep history and this is a non trivial problem. since all
tiger nodes are cleaned of their obsolete tags any tiger node will be pushed to
version 2 or more. You can not rely on version number. you must verify the
position itself against an old history dump.<br>
<br>
<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'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<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"'> Apollinaris Schoell
[mailto:aschoell@gmail.com] <br>
<b>Sent:</b> 17 September 2009 21:04<br>
<b>To:</b> Richard Shank<br>
<b>Cc:</b> Jim Brown; tbook@libero.it; Matt Amos; talk-us@openstreetmap.org<br>
<b>Subject:</b> Re: [Talk-us] Tiger US address importing<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I know user nmixter has started
to to compile a list for california for free county gis data. Can't connect to
the wiki right now. But easy to find from the California page.<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Thu, Sep 17, 2009 at 11:32 AM, Richard Shank <<a
href="mailto:develop@zestic.com">develop@zestic.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal>Apollinaris Schoell wrote:<o:p></o:p></p>
<p class=MsoNormal><br>
- more and more counties make their data available for the public. I hope such
data is authoritative and much more useful. wherever possible this should be
used instead.<o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Is there a complied list of
these counties? Since everything is handled county by county anyway, this
may be the place to start.<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>