On Sat, Apr 13, 2019 at 3:25 PM Paul Allen <[email protected]> wrote: > Namespacing is guaranteed to fix it. The only thing is that in some (not > all) cases namespacing > might be overkill. Not wrong, just unnecessary. So check_in=* might be > suitable for all the > cases we have now and will have in the future, but camp_site:check_in=* (and > airport:check_in > and all the rest) will never be wrong whereas at some future date check_in=* > could be a problem. > > It's not just editors but also overpass-turbo queries. You want to search > for airport checkins but > with check_in=* you'll get camp site and hotel checkins too. I don't think > overpass-turbo has > a mechanism for requesting check_in=* within the boundary of some other > object (I could be > wrong) but if it did then it would be computationally expensive. Possibly > very expensive if > there's a naked check_in=* and it ends up expanding the search for the > enclosing feature until > it covers the whole world (or hits whatever bounding box you chose). You > could solve that > with a relation, but that's asking a lot of many mappers who don't understand > or use > relations for anything. Namespacing solves that problem (transparently if > the editors > support the tag). >
check_in=airport/camp_site/hotel/hospital/seaport/event_venue/... would work around this issue as well, wouldn't it? _______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
