How to Properly Tag Multiple Rental Properties and Their Buildings Under One Business

[Tsanny]

Hello everyone,

I’m currently mapping five different rental properties that belong to the same family-run business. These properties are all located in the same general area and offer a variety of amenities (e.g., swimming pools, spas, tennis courts, and annex buildings for events like weddings or team-building retreats).

I have a few questions:

1. Tagging Each Property:
   For each property, I’ve drawn an area polygon to represent the land it occupies. Should I also map and tag each individual building (e.g., main house, annex, spa building) within that property? If so, how do I clearly indicate that these buildings belong to the same property area?
2. Relating Buildings to the Property:
   Is it enough that the buildings lie within the property’s polygon, or should I consider using a relation (such as a “site” relation) to explicitly group them together?
3. Representing All Properties Under One Business:
   Since all five properties are operated by the same business, what’s the best practice to show that these distinct properties are part of a single company’s portfolio? Should I link them via a relation, use a common operator tag, or something else?

I’d appreciate any guidance or examples on how to best model this situation. My main goal is to accurately represent the properties, their amenities, and their common ownership so that future map users can understand the layout and relationships of these sites.

Thanks in advance!

[PeterCooperJr]

Just my first thoughts; others might have different ones.

@Tsanny

For each property, I’ve drawn an area polygon to represent the land it occupies. Should I also map and tag each individual building (e.g., main house, annex, spa building) within that property?

Yes, it’s pretty normal to map both an area that has some sort of amenity or tourism tag, as well as the buildings within it. See, for instance, the wiki documentation for tourism=hotel or amenity=school, which both have examples of a “campus” with multiple buildings in it.

@Tsanny

If so, how do I clearly indicate that these buildings belong to the same property area?
Is it enough that the buildings lie within the property’s polygon, or should I consider using a relation (such as a “site” relation) to explicitly group them together?

I think just having the building within the area is clear enough. I wouldn’t bother with a fancy relation unless there’s something more complicated that you’re trying to record. Saying “this building is a part of this area” is fairly straightforward by the building just being there inside the area.

@Tsanny

Since all five properties are operated by the same business, what’s the best practice to show that these distinct properties are part of a single company’s portfolio? Should I link them via a relation, use a common operator tag, or something else?

I think a common operator tag is sufficient. If you want to get fancier, or especially if the name of the operator might be ambiguous with similarly named organizations, then adding an operator:wikidata with a Wikidata id for the operator (making a Wikidata item if it doesn’t already exist, as I’d assume this kind of entity would meet Wikidata’s notability criteria) can be helpful for making it clear that they’re all run by the same organization and giving a pointer to more information about it.