On Wed, May 27, 2015 at 11:38 AM, Markus Lindholm <[email protected]> wrote: > Otherwise they make bad routing targets
Complete addresses may indeed be unique, but the "housenumber" part can be and is in may countries the same for, for example all apartments in an apartment building. In other countries each apartment may have a running "housenumber", i.e. unique within that street. Effectively, all software working with osm data has to "support" (i.e. build an index of) nodes and ways with addr:* tags, no matter whether they are a part of a way or a relation, or whether they stand alone. In most cases, if not in all use cases, the different properties and objects it might refer to can then be algorithmically extracted; if that is absolutely necessary. Hence, I would say that address info on a node is never wrong; it accomplishes the goals and every application can find it, but IF the address is the only address of some "thing" (being an entrance or a building), it's better to have it on the node or the way depicting that feature. When a feature has several addresses, the most simple solution is again a node for each address; everybody can extract and use all those addresses. -- alv _______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
