[OSM-talk] Address interpolation

[Jochen Topf]

On Tue, Sep 08, 2009 at 01:18:33PM +0100, Brian Quinion wrote:
> On Tue, Sep 8, 2009 at 1:05 PM, Valent
> Turkovic<valent.turkovic at gmail.com> wrote:
> > Hi, I'm using address interpolation for the first time so I would like to
> > ask if somebody can check if I did it ok or if there are some errors:
> >
> > http://www.openstreetmap.org/?lat=45.544703&lon=18.718653&zoom=18&layers=B000FTF
> 
> They seem OK - and my processing code can interpret them (yeh!) but
> I'd suggest a couple of changes
> 
> For
> 
> http://www.openstreetmap.org/browse/node/489432179
> 
> I'd suggest moving all the following tags
> 
> addr:city = Osijek
> addr:country = 385
> addr:postcode = 31000
> addr:street = Starigradska
> 
> to the way (rather than the individual nodes).  And I'd suggest that
> addr:country = 385 is unlikely to be understood.

No! Please don't do that. That makes it harder to use. Then there are two
possible ways, where data can be. Please use only addr:interpolation on
the way and everything else on the nodes. (Of course those tags *can*
be on ways, but that has a different meaning: Thats for building outlines
that get tagged with an address. Another reason for keeping those things
separate.)

> In general creating a polygon / relation for anything above street
> level is probably more useful than adding it to individual nodes (or
> even ways) - so just draw a rough polygon for the city of Osijek and
> tag that instead.

No. Creating polygons and relations willy nilly makes this harder to use.
Again, it means there are several places where the software has to look
for the data and several places where people have to look for the data.
Especially relations are easy to break and easy to overlook, so they should
be used rarely.

The Karlsruhe schema in its most basic form where all this data is on the
node might duplicate lots of data, but it is very robust.

Jochen
-- 
Jochen Topf  jochen at remote.org  http://www.remote.org/jochen/  +49-721-388298