Any idea of when this might start happening? As someone who has been manually cleaning up some of the TIGER data in my area (Tampa), I'm interested in anything I can do to help with this transition, so that what I've done can benefit from the addressing information. Aside from correcting gross topological errors, the biggest changes I've had to make have been in redoing major streets divided by hard medians from single lines to what the tagging system refers to as "dual carriageways". We have a lot of these in the Tampa area, and I've only done a handful because they involve so much work to get the median cuts and driveway access recorded.
I would say that in the Tampa/St. Pete/Clearwater area, even with a couple of fairly active mappers, we still have edited only 5-10% of the TIGER road data for the area. Ed Hillsman ------------------------------- >Date: Fri, 18 Sep 2009 10:13:56 +0100 >From: Jim Brown <j...@cloudmade.com> >Subject: Re: [Talk-us] Tiger US address importing >To: Apollinaris Schoell <ascho...@gmail.com>, Richard Shank > <deve...@zestic.com> >Cc: "tb...@libero.it" <tb...@libero.it>, Matt Amos > <m...@cloudmade.com>, "talk-us@openstreetmap.org" > <talk-us@openstreetmap.org> >Message-ID: > <33309bf8d82798428226c7d50c110651039f8b2...@sha-exch9.shared.ifeltd.com> > >Content-Type: text/plain; charset="us-ascii" > >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)... > >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. > >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. > >As for detecting which roads to import, one approach is: > >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. > >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)... > >3. In the end we produce the list of interpolation lines to import and associate. > >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... > >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 :) ... > >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. _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
