On 25-10-2020 14:55, Janko Mihelić wrote: > Relations are definitely safer, but I wanted to add a unique name > version for new editors that are intimidated by relations. > Also for cases when you would have a lot of admission issuers, so we > don't get some humongous relations. Maybe there's a venue for which you > can buy a ticket in any kiosk in town. I would rather tag something like > that with a admission:name=* than add all kiosks to a relation.
Using relations for the first time is tricky, you are right about that. But there are a lot of places in OSM where relations are necessary. I wouldn't worry too much about novice mappers not being able to use them. Any mapper who can use the wiki to look up keys for a scheme like this will probably be able to use JOSM to create relations. When the proposal is settled down on the relation type and roles a prefix could be created for JOSM to help create such a relation, further lowering the bar. I wouldn't be too afraid of large relations, but you might want to add that the ticket office and the poi should (ideally) be geographically close-ish (like, within the same city or area). This is similar to what the site-relation documentation states. I mentioned this on the wiki as well: it might be nice to add an optional role to your relation for the actual entrances (e.g., turnstiles), in addition to the ticket office and the poi, where tickets are checked. For something like a theme park these are definitely mapped, and a clever router could suggest a route going from the ticket office to an entrance with that data available. This looks like a useful proposal. _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
