I’ve got a patio for a restaurant tagged as leisure=outdoor_seating. That page says you can add operator=* as a string, but I’m wondering if I can add a Relation between the patio and the restaurant. This is really for semantic reasons, because if the restaurant changes its name or gets a new owner, it would be nice if the patio didn’t then have out-of-date information.

I don’t see a Relation type that’s relevant. I don’t want to just start doing my own thing, so does anyone know of a way to use a Relation here, and if not, is that something that can be proposed?

Thanks for all of the responses on my other questions, btw. This community has been very helpful.

  • @[email protected]English
    6•20 days ago

    My general recommendation with relations: If you can do something without a relation, do it that way. A lot of people don’t understand them and some editor software can’t manage relations well, so there is a big chance that someone will mess it up accidentally in the future.

    Maybe you can tag on the restaurant that outdoor seating is mapped as a separate element with outdoor_seating=separate. It’s not used frequently, but separate means that something is mapped as a separate element.

    If you still want to do a relation you can use a site relation. You can use that for any kind of POIs. I don’t recommend this though for 2 members. Example. Overpass query for all site=restaurant: https://overpass-turbo.eu/s/1QjJ

    If you afraid someone will forget to change the operator, the same editor can forget to update the relation as well, so I think you can’t win this battle.