[Talk-us] Address Lookup

Fri May 21 14:56:52 BST 2010

But, you cannot point to point dispatch using an interpolated address; so that's why a database without address points is not that much more valuable than the TIGER db for that purpose. TIGER is not that accurate, but it is precise for an interpolated range set. Without point to point, you are only getting a driver a topologically correct route that gets them in the general area. TIGER's precision (especially TIGER 2009) is enough for this. There is plenty of value above TIGER in other applications where accuracy matters more than precision, just not in the point to point dispatch application; and that is going to be the most valuable application.
The work is not in the ground surveying; that really is relatively quick work if street addressing and point addressing are done at the same time. The work is in building the address to street associations. Unfortunately, I don't see how that can get any easier than how Val has diagrammed. That particular aspect becomes even more burdensome when done separately from the street addressing too (as you have to then search for the right street segment for each address).

Brett Lord-Castillo
Information Systems Designer/GIS Programmer
St. Louis County Police
Office of Emergency Management
14847 Ladue Bluffs Crossing Drive
Chesterfield, MO 63017
Office: 314-628-5400
Fax: 314-628-5508
Direct: 314-628-5407

-----Original Message-----
Date: Fri, 21 May 2010 04:52:26 -0600
From: Peter Batty <peter.batty at gmail.com>
Subject: Re: [Talk-us] Address Lookup
To: Apollinaris Schoell <aschoell at gmail.com>
Cc: "val42k at gmail.com" <val42k at gmail.com>,	OSM Talk US
	<talk-us at openstreetmap.org>
Message-ID: <04041B59-CECC-4B4F-90EA-1C9BA680D86E at gmail.com>
Content-Type: text/plain;	charset=us-ascii

I don't agree that there is no value in address range interpolation like TIGER uses. As anyone who has edited TIGER data knows, it is not very accurate. So cleaning that up (address aspects as well as geometry and attributes) is a valuable thing that we can do in OSM. Getting a viable geocoding function using address ranges is much more achievable in terms of the effort needed than doing individual properties. And the two approaches complement each other anyway - you can always search for a specific property address and fall back to an address range if you don't find it.

Cheers,
    Peter.

On May 21, 2010, at 4:24 AM, Apollinaris Schoell <aschoell at gmail.com> wrote:

> there is not much value to add address interpolation in US. this can be done easier and more consistent by using a plain tiger DB. only if detailed addresses are added to osm there is additional value. 
> and yes this is a lot of work much more than streets. some counties offer detailed data and it can be imported easily. in other places it has to be done by survey. but wasn't that the idea of osm? competing with google in processing public data has no chance anyway. why not concentrate on the strengths of crowd sourcing.
> 
> 
> On 21 May 2010, at 6:45 , Val Kartchner wrote:
>> 
>> The goal of Open Street Map is to eventually do everything that
>> commercial map products do.  This would include address lookup.
>> 
>> I've looked around and the way of associating addresses with streets
>> doesn't seem to work very well.  The simplest way (requiring the fewest
>> nodes) still requires a lot of work.
>> 
>> For instance, for an example I've picked a street around my area: West
>> 2550 North.  This is just the ways needed for the streets themselves.
>> (I didn't include the names on the cross streets because they don't
>> matter for this example.)
>> 
>> A    B          C   D   E
>> |    |          |   |   |
>> |    |          |   |   |
>> +--+-+--+---+---+---+---+--
>>  |    |   |   |   |   |
>>  |    |   |   |   |   |
>>  F    G   H
>> 
>>> From what I understand, next to each place where another street
>> intersects this street I will have to create another node (on each side
>> of the street) tagged with "addr:street" and "addr:housenumber".  I will
>> need to connect the nodes on each side of the street with a relation.
>> The relation I will need to tag with "addr:interpolation" and even/odd,
>> as appropriate.  This makes the "simple" street above now look like
>> this:
>> 
>> A    B          C   D   E
>> |    |          |   |   |
>> |    |          |   |   |
>> *----*--*---*---*---*---*-*
>> +--+-+--+---+---+---+---+--
>> *----*--*---*---*---*---*-*
>>  |    |   |   |   |   |
>>  |    |   |   |   |   |
>>  F    G   H
>> 
>> This is a LOT of data to manually add.  Is there a simpler way?
>> 
>> No, I don't have a better idea.
>> 
>> - Val -
>> 
>> 
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us at openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-us
> 
> 
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us

------------------------------

_______________________________________________
Talk-us mailing list
Talk-us at openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

End of Talk-us Digest, Vol 30, Issue 30
***************************************