[Talk-ca] duplicate address data

[dega]

Today, Gerd Petermann wrote:
> - wrong data like 
>  * addr:interpolation ways crossing the road
>  *  addr:interpolation ways with nodes that have equal numbers

I don't see any problem with addr:interpolation ways going from the beginning 
up to the end of a street. If it cause a problem in the renderer, it should be 
addressed by the renderer developers.
If the purpose is accuracy, we may add 2 address nodes in the interpolation 
way.

For the mapper (surveyor), the address vector is, (in most cases) a linear set 
of data.
In most cases, a street should be a single way. Same for adddress 
interpolation. If a strret is segmented (because of a change in spped limits, 
for example), it should not affect the interpolate way.

If the constraint (addr:interpolation crossing a junction) is  removed, then 
segments can be merged and duplicated addresses will not be a problem anymore.

dega

Le 28 mars 2015, 08:15:56 talk-ca-request at openstreetmap.org a écrit :
> Date: Sat, 28 Mar 2015 09:15:40 +0100
> From: Gerd Petermann <gpetermann_muenchen at hotmail.com>
> To: "talk-ca at openstreetmap.org" <talk-ca at openstreetmap.org>
> Subject: [Talk-ca] duplicate address data
> 
> Hi Stewart,
> 
> I am not sure what you try to say here.  I don't care much about special
> cases.
 My understanding is that the normal scheme in Canada is to have
> - odd  numbers on one side and even numbers on the other side of a road
> (as in Germany)
> - numbers seem to be related to distance, one should not expect to find 20
> houses
 when an addr:interpolation=both way connects two nodes with 1 and
> 20 This is also documented here:
> http://en.wikipedia.org/wiki/House_numbering#North_America
> 
> In Germany I would expect to find 20 houses or a large building with 20
> different entries.
 as described here:
> http://en.wikipedia.org/wiki/House_numbering#Western_and_Southern_Europe
> 
> I wanted to point out that the OSM data base for Canada contains a huge
> amount of 
 - useless data like duplicated addr:interpolation ways
> including nodes from different imports which IMHO should be removed ASAP. I
> don't know how to automate that process, but I volunteer to help.
> 
> - wrong data like 
>  * addr:interpolation ways crossing the road
>  *  addr:interpolation ways with nodes that refer to a different street 
>  *  addr:interpolation ways with nodes that have equal numbers
> 
> Do you suggest that programs using the OSM data should tolerate these
> errors
 and try to guess what is meant?
> Of course each programmer can do that, but I think the right way is to try
> to 
 have good data in OSM and let programs report the data that is not
> plausible. 
> Gerd