On Sun, Sep 7, 2008 at 10:53 PM, Norbert Wenzel <[EMAIL PROTECTED]> wrote:
> Shaun McDonald wrote: > >> The problem with this is that none of the editors support having >> duplicate key values, even so the 0.5 API supports it. The 0.6 API will >> not support duplicate key values. >> > > I think the support of duplicate keys is a very much needed feature and I > personally would drop it only, if there are really good reasons (e.g. > breaking fast queries, etc.) to drop it. > > It would be possible to tag something like "amenity=supermarket; > post_office;" but as stated in another discussion yesterday that would make > searching for entries much more complicated. > > Just to name a few very common cases where duplicate keys would be > necessary I'd like to point out the very common case of hotels also having a > publicly available restaurant. Of course one could draw a building and drop > all needed amenities inside, but I think that wouldn't be routable unless > you add the addr: properties to every node inside that building. > > So personally I think duplicate keys would be the easiest and best way to > tag such double-uses. > > Norbert > Just make two different nodes, each located closest to the amenity concerned. There's nothing that makes it non-routable. It's just a point--the routers will get you as close to the point on the road as possible. The addr: property definitely isn't going to help in making it routable. Karl
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
