On Thu, Aug 19, 2010 at 10:31 AM, Simone Saviolo <simone.savi...@gmail.com> wrote: > 2010/8/19 Anthony <o...@inbox.org>: >> On Thu, Aug 19, 2010 at 10:27 AM, Simone Saviolo >> <simone.savi...@gmail.com> wrote: >>> 2010/8/19 Anthony <o...@inbox.org>: >>>>> And what happens if the name is not exactly the same ? >>>> >>>> Then there's an error that needs to be fixed. >>>> >>>>> That's why some contributors prefer the relation. >>>> >>>> Right problem, wrong solution. >>> >>> So, if the name of a street is changed for whatever reason, I have to >>> go through the, maybe, several hundreds of house numbers on that way, >>> change the addr:street on every single one of them, and then hope the >>> name isn't changed again too soon? Is this the right solution? >> >> No, the right solution is to have the API support references. > > They do, sort of. You create a relation which holds a "reference" to the > street.
That's backwards, though, and the implementation is quite costly from a performance perspective. You want the address to reference the street, not the street to reference the address. See http://wiki.openstreetmap.org/wiki/Talk:Relations/Relations_are_not_Categories#Partly_disagree Richard, you're on this list. What do you think? Is the associatedStreet relation an appropriate use of relations? _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
