that's how the schema works, one polygon for the outline, then fill it with building parts.

"The building outline represents the area of land covered by the union of all parts of the building."
"A building should have a single area tagged building=*."

"The entire building outline should be filled with building:part=* areas"

In general multipolygons "are used to represent areas (polygons), typically complex ones with holes inside, or consisting of multiple disjoint parts". This area didn't have holes or disjointed parts, so a multipolygon wasn't needed, as Mannivu noted.

> I disagree to have only 1 polygon because different parts of building does not have the same height, it will just hide all other parts.

Where do you see this behaviour? The current standard is the "Simple 3D Buildings": osm.wiki/Simple_3D_Buildings
If a renderer doesn't render stuff properly, the renderer should be fixed, not our tagging be adapted to it (some people adds height=0 to the outline, for example...).

Yep, no need to make the outline as a multipolygon with parts as outers. A simple polygon is enough if there are no inners. Also "building:part=no" it's problematic, since it's treated by some 3D renderers (that do no parse different values) as a building:part.

Hi Frans S,

node/9476167774

what's the meaning of species=sp. A?

Hi xrt,

node/12386918988

are you sure this (the one linked and the five around it) six trees are pinus? usually pinus are needleaved trees

thanks and good mapping

Hi Virgile1994,

node/3622988452

are you sure this is a pin? usually they are evergreen, not deciduous

thanks and good mapping

Hi user_5589,

please do not add values such as "Quercus sp.". The proper tag is "genus=Quercus". More details can be found in this discussion: https://community.openstreetmap.org/t/adding-the-type-of-tree-species-genus/96432/8

Si possono ripristinare elementi di chiunque, non solo utenti bloccati: osm.wiki/Change_rollback

Ma perché trasformare semplici poligoni in multipoligoni con un solo outer? Mi sfugge il beneficio della modifica

Questi elementi sono tra l'altro segnalati da Osmose: https://osmose.openstreetmap.fr/it/issue/1fd9696c-0ae3-12c3-56e4-4eced274e954

Hi wegavision,

I wonder why you did delete the multipoligon I made for the grass landuse? relation/14947272/history

thanks and good mapping

Ciao demon_box,

vedo che hai revertato delle mie modifiche, ad esempio:

way/622143827/history

qua hai cancellato il tag dalla way, e trasformato la way nel solo outer di una relazione con un solo membro. Come mai?

Avevo già notato la stessa cosa due anni fa ma senza risposta: changeset/149979060

After 8 months, the website link was still broken. I removed it

Ciao demon_box,

way/1494723546

qualcosa deve essere andato storto qua, riesci a dargli un'occhiata?

grazie per gli edit e buon mapping!

Ciao Alessandro,

cosa significa barrier=all?

way/80840033

After four here: changeset/182254557

Ciao Martino,

nel 2021 ti invitai a una discussione in mailing list sui comuni sparsi: changeset/113368974

il consenso fu quello di mappare la label dei comuni sparsi come place=municipality: https://lists.openstreetmap.org/pipermail/talk-it/2021-November/073085.html

ora dopo quattro anni stai ri-cancellando gli stessi elementi. è cambiato il consenso?

Hi emilthaug,

I guess you uploaded that Panoramax image by mistake?

Ciao jakp3,

node/11083202695/history

qua avevi trasformato un albero in un parco. Era voluto o è stato un errore?

In Italy we mostly use the destination schema documented in the CAI wiki page: osm.wiki/IT:CAI#Luoghi_di_posa

Seems like this is a vibe-coded editor?

Just for the record, this changeset has since been reverted.