Hello everyone. I've used `type=site` relations many times to group buildings and other elements (leisure, parkings ...) that could not be gathered to one area as they're scattered among other features. For example at a university, buildings belonging to the same department are not necessarily grouped nearby each other, they are scattered within the campus or even kilometers away. As far as I know the attribute is still in a proposed state (?) and is *not found by OSM search engine nor rendered on the map*. So I am *asking* if *using this type of relation is still suitable* or should I use `type=multipolygon` instead? How should I proceed? Thanks.

Hello everyone. I've used `type=site` relations many times to group buildings and other elements (leisure, parkings ...) that could not be gathered to one area as they're scattered among other features. For example at a university, buildings belonging to the same department are not necessarily grouped nearby each other, they are scattered within the campus or even kilometers away. As far as I know the attribute is still in a proposed state (?) and is *not found by OSM search engine nor rendered on the map*. So I am *asking* if *using this type of relation is still suitable* or should I use `type=multipolygon` instead? How should I proceed? Thanks.

Hello everyone. I've used `type=site` relations many times to group buildings and other elements (leisure, parkings ...) that could not be gathered to one area as they're scattered among other features. For example at a university, buildings belonging to the same department are not necessarily grouped nearby each other, they are scattered within the campus or even kilometers away. away. As far as I know the attribute is still in a proposed state (?) and is not *not found by OSM search engine nor rendered on the map. map*. So I am asking *asking* if using *using this type of relation is still suitable suitable* or should I use `type=multipolygon` instead? How should I proceed? Thanks.

Hello everyone. I've used `type=site` relations many times to group buildings and other elements (leisure, parkings ...) that could not be gathered to one area as they're scattered among other features. For example at a university, buildings belonging to the same department are not necessarily grouped nearby each other, they are scattered within the campus or even kilometers away. As far as I know the attribute is still in a proposed state (?) and is not found by OSM search engine nor rendered on the map. So I am asking if using this type of relation is still suitable or should I use `type=multipolygon` instead? How should I proceed? Thanks.