I don't get the problem with k=v instead of just v. There is a function called concatenate which solves that.
We should move away from mapping directly with tags, and to a system like iDs, with descriptions that hide tags. For a database it's irrelevant if it's "oneway=yes" or "4658". All this talk about correct k=v combinations is bikeshedding to me. Only DB admins and tag proposers should ever see what a tag looks like. Janko sri, 3. lip 2015. 12:22 Lester Caine <les...@lsces.co.uk> je napisao: > On 03/06/15 10:30, Martin Koppenhoefer wrote: > >> Just what combination is right for a single retail building with a > >> > leisure facility on the ground floor and accommodation above? > > > > I don't think a combination of tags is the best answer to this question, > it's rather a combination of objects (3, one for the building, one for the > ground floor facility, one for the accommodation facility) > > I think my point here was that there is a single building, but a number > of uses within that outline. We don't have a convenient method of > handling different objects on different floors within the one set of > 'ways'. The areas I'm trying to tidy up are small shopping malls which > have shops within shops on multiple levels ... with accommodation above. > A combination of objects is just what I'm looking for, but with > different outlines for each object ... > > -- > Lester Caine - G8HFL > ----------------------------- > Contact - http://lsces.co.uk/wiki/?page=contact > L.S.Caine Electronic Services - http://lsces.co.uk > EnquirySolve - http://enquirysolve.com/ > Model Engineers Digital Workshop - http://medw.co.uk > Rainbow Digital Media - http://rainbowdigitalmedia.co.uk > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
