On Sat, 13 Apr 2019 at 14:44, bkil <[email protected]> wrote: > > check_in=airport/camp_site/hotel/hospital/seaport/event_venue/... > would work around this issue as well, wouldn't it? >
To some extent. It's possible to conceive of situations where it wouldn't. Maybe not for check_in itself but some of the other tags where people said namespacing was unnecessary. What if the airport checkin handles both the hotel and the flights? What if the place is a nexus of airport and seaport sharing a common checkin? Semicolons can be used but they are thought by some to be problematic in the way some data consumers handle them. Also the user interface would be more error-prone. In iD with namespacing you'd type "check in" into the search box and be shown a list of large(ish) icons labelled "airport checkin", "hospital checkin" etc. But with a list of values for a checkin=* tag you get just text and it's a lot easier to click on the wrong one by mistake. But yes, it's an alternative to namespacing. And preferable to having check_in=yes for all types of checkin. -- Paul
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
