In other words, you and me can't go there to get a new passport, but this doesn't mean it's not the embassy. There's also a sign in front reading "embassy". It has diplomatic protection, etc. No way this is a "park".

this is part of the German embassy, it is the residence of the Ambassador to Italy, and there are many events taking place here. It is indeed not the chancellery of the German embassy, which is close to Castro Pretorio. But it is part of the embassy.

this changeset makes the residence of the German ambassador a leisure=park and access=private. This seems strange tagging, at least. This is not a park, at most you could see it as a garden, but then the garden would not be the residence but only the garden. As this is about the residence of the ambassador, the object has now lost the diplomatic status (private access is not quite hitting it).

Benvenuto anche da parte mia!

this changeset introduced a lot of duplicate nodes and added a lot of names in the wrong tag (put English names in the tag for the local name). Please do not map for the renderer, rather use a rendering that suits your needs.

From where did you get the name "Area verde Rosa Raimondi Garibaldi"? There aren't any signs with this name, are there?

Secondome non dovresti cancellare "cose" esistenti, siano privati o meno, questi vialetti sono utili anche se non percorribili (per esempio per analizzare la struttura di una zona, oppure per determinare le aree "sigillate" (per l'acqua), oppure per orientarsi (incroci di vialetti con la strada) o per fare un routing che cerca di minimizzare i pericoli (per esempio per bimbi, sempre riferito agli incroci con la strada/marciapiede), ecc. ecc.

IIRR this was discussed on talk-it and still IIRR approved post operam.

si, rimaniamo calmi e cherchiamo di discutere i dissensi. Se proprio devi defecare, non farlo in pubblico, facciamo tutti così ;-)
Quando vedi edits problematici, commenta il changeset. Un saluto, Martin

multipolygons are fine if you can reuse existing geometry or parts of it, but if there are adjacent polygons like the buildings in the eastern part here, you should not add the buildings but rather use only a common outline (i.e. all outside walls can create a closed polygon, do not include the inside walls, do not use overlapping outer ways in mp). I have created a big polygon around everything (and have reused your relation for this), including the outdoor spaces that connect the buildings.

There even a way in version 57 deleted by this. Please be more respectful with other people's work and modify rather than delete / recreate! E.g. way/15564717

looks like an undiscussed mechanical edit. Deletes 767 ways in one changeset, many of which in mature versions (e.g. v19!).

this is likely un discussed import or mechanical edit. Creates also overlapping ways (admin boundaries overlapping 100% roads, with common nodes). The latter does not seem a reasonable way to represent boundaries that are defined by these roads.

I have actually restructured the multipolygon rather than deleting it.

The multipolygon that was created for Cartiera Latina, creates some problems. Also, roles (inner and outer) are mandatory for multipolygon relations, although the data is also interpreted without them. I will convert the multipolygon to a simple polygon to simplify the structure and to improve common data usage.

I've fixed it

At the Terme di Diocleziano in this edit you have added the tag barrier=hedge to an area object with the tags landuse=grass. These are different objects and should be modeled as different objects in OSM as well. The hedge is linear and running around, the landuse is referring to the enclosed polygon (and is not referring to the hedge).

This changeset added a wikidata reference to this node, which is referring to the museum. The museum already has the wikidata reference.

ci dovrei ripassare
grazie della risposta

si, lo sò, 8 anni fa ;-)