piebro/osm-data huggingface dataset:
viloan (2019-04-17 02:25:16+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
Leo Andreis (2019-04-23 00:05:49+00:00): Bela att
viloan (2019-04-17 02:49:04+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
BrackoNe (2019-06-10 14:51:46+00:00): Hi aaronsta,

I have used Bing imagery and I could see that there are some completed parts. Also I have seen vehicles on it, so it looks like it is fully in use.

I would most kindly ask you to check current edit, and if it is wrong I will revert it. Also please check two roundabouts that are near one to another at the North.

Thank you in advance for your time.

Best Regards,
Nemanja
aharvey (2020-09-26 08:58:29+00:00): hi I updated the name and ref for https://www.openstreetmap.org/way/45728168 based on sinage
Dimacn (2019-04-17 12:41:25+00:00): Дворовые проезды (и внутриквартальные проезды) должны обозначаться тегами highway=service + living_street=yes .  Дороги типа highway=residential обозначают улицы, и обычно имеют название. Подробнее тут: https://wiki.openstreetmap.org/wiki/RU:Key:highway
woodpeck (2019-05-02 16:50:43+00:00): Hello Olyon, I disagree with mapping bays, straits, channels, and various other named water areas as precise, hundreds-of-members polygons in OSM. I think a named node is sufficient. Using polygons means you are creating arbitrary cut lines between various bodies of water, like e.g. https://www.openstreetmap.org/way/684290011. This kind of mapping is very difficult to maintain, prone to breakage, a burden on other mappers working in the area, and adds very little information. I would prefer it if you could stop copying this data into OSM from external sources, or else, have a proper discussion about it on one of the suitable international mailing lists before you embark on global mapping projects like this.
woodpeck (2019-05-02 16:57:02+00:00): Also, I disagree with creating groups of islands like the nNicobar Islands here https://www.openstreetmap.org/relation/9493294 by taking all the individual coastline bits and putting them into one big relation in addition to the individual island relations they are already in. I also think that *if* such mapping made sense, using a type=multipolygon is the wrong relation type to use. If you feel a need to combine these individual islands into one group, I would make the individual island relations a member of a super relation, instead of duplicating information. Someone wanting to edit, say. the coast of Camorta Island will now not only edit a coastline way, but three relations. This is confusing to mappers.
Olyon (2019-05-02 22:23:48+00:00): Hello,
For groups of islands, there is no other way to tag a surface thing. the only way it is to use multipolygons and in the multipolygon, it is necessary to use ways and no other multipolygon https://wiki.openstreetmap.org/wiki/Relation:multipolygon.

If the problem is to maintain them, it would also be necessary to suppress the relations for the majority of the countries which are also relations of hundreds of members.

To represent things very big only with nodes, I do not understand how that could be enough.

The problem of the fuzzy limits, I understand it but it is the case for a lot of thing in osm: like the coastlines, and many of the tags natural=* like the tags landuse=*. Here the limits are, of course, much more fuzzy especially in high seas but is this a reason not to make appear these objects in osm ? We could make appear this uncertainty on the way traced by new tags.
viloan (2019-04-17 04:05:33+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
aharvey (2019-05-10 07:56:19+00:00): I've asked the Data Working Group to look into this, since your source nearmap.com is a commercial imagery supplier and does not (since the OSM license change) make their imagery available to OSM for tracing. To me it's not clear from their TOS if you as a customer of Nearmap can derive information from their imagery and 100% own it free from any IP restrictions, which is why I've asked DWG for advise.

Is this edit part of an organised or directed mapping activity per https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines ?
Glassman (2019-04-17 16:53:45+00:00): Tip: you can square the building by selecting the outline and type "s" - the building will look much nicer that way.
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/69294310
viloan (2019-04-17 05:11:36+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
PeanutButterRemedy (2019-04-27 19:44:28+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
user_5359 (2019-04-18 05:07:36+00:00): Welcome to OSM! I delete your entry after merging with the existing node!
PeanutButterRemedy (2019-04-27 19:43:50+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
PeanutButterRemedy (2019-04-27 19:43:41+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
osmviborg (2019-04-17 08:30:51+00:00): Der er ingen posthus i Ringkøbing.
Hjart (2019-04-17 08:44:23+00:00): Jeg har bare linket til et billede af bygningen,  ikke benævnt det "posthus". Bygningen er måske et tidligere posthus
osmviborg (2019-04-17 08:52:44+00:00): Postnord forlod bygningen 1. januar 2018. Billedet ligger i en kategori der hedder "Post offices in Denmark". Det er noget rod.
Hjart (2019-04-17 09:20:14+00:00): Du er velkommen til at flytte det til "Former post offices in Denmark" eller lignende
PeanutButterRemedy (2019-04-27 19:43:29+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
Apisit U-aram (2019-04-17 06:37:10+00:00): บ้านพักผู้ปฏิบัติ จำนวน5หลัง
FrankXF (2019-05-01 17:37:39+00:00): Hallo Dieter,

die neue Linie Bethofenstraße war nicht verbunden mit der Grafenberger Allee. Korrigiere das gerade.
Hier kann man die PT Relationen checken:
https://ptna.openstreetmap.de/results/DE/NW/DE-NW-VRR-Analysis.html

Mfg, FrankXF
FrankXF (2019-05-01 17:50:17+00:00): Am anderen Ende der Beethofenstraße war diese leider auch nicht mit der Ackerstr. verbunden. Bitte aufpassen.
Mfg, FrankXF
mavl (2019-07-21 15:44:59+00:00): This changeset was redacted. Reason: copyrighted data were used.
adrienandrem (2019-04-17 19:42:59+00:00): Bonjour,
si je comprend bien, il s'agit d'un import,
des données du site balisemeteo.com
À quel endroit peut-on trouver la documentation de cet import svp ?
Merci
https://wiki.openstreetmap.org/wiki/FR:Import/Guidelines
Jim005 (2019-04-18 09:02:55+00:00): Bonjour, merci de ton retour qui éclair un process qui m'était inconnu. Les données proviennent d'ici : https://data.ffvl.fr/pmwiki/  
puis j'ai fusionné les doublons sur JOSM via une recherche API sur "man_made"="monitoring_station" . 
Par contre j'ai pas checké la Guyane, dsl. 

Je vais voir pour reprendre process en suivant la doc. a+
marc__marc (2019-04-19 00:07:33+00:00): en passant, source=survey c'est pour les éléments que tu as vu/noté toi-même sur place.
c'est tout le contraire d'une source externe dont la licence n'est hélas pas compatible en l'état
trial (2019-04-19 20:32:07+00:00): de plus les noms ne sont pas conformes aux règles OSM. Style tout en majuscules et sans accents. Sans compter que Trucmuch pour la poste de Trucmuch ce n'est aps vraiment le nom de la poste, c'est le nom de la ville ou du quartier où se situe le bureau de poste.
Jim005 (2019-04-20 01:53:32+00:00): Les noms ont bien des accents et minuscules, par contre effectivement le nom Truchmuch correspond à la localisation. Je change en quoi : 
- Balise météo FFVL ?
- Balise météo FFVL de Truchmuch
- Vide ?
🙏
trial (2019-04-20 08:44:02+00:00): oups, je me suis trompé de changeset ;-). Vide me semble pas mal, Balise météo FFVL c'est une dénomination plus qu'un nom. FFVL c'est l'operator. Et si en interne la FFVL utilise Trucmuch comme référence, pourquoi pas ref=Trucmuch.
Jim005 (2019-04-21 09:55:06+00:00): Merci de vos retours éclairés !! 
J'ai corrigé :  https://www.openstreetmap.org/changeset/69420624
trial (2019-04-21 11:43:51+00:00): Oui c'est mieux ;-).
Je continue sur ce fil comme ça ceux qui ont commenté peuvent suivre.
>  puis j'ai fusionné les doublons sur JOSM via une recherche API sur "man_made"="monitoring_station" . 
Bien mais insuffisant : exemple de point triple :
- https://www.openstreetmap.org/way/266218948 le socle de l'antenne ?
- https://www.openstreetmap.org/node/619347326 l'antenne
- https://www.openstreetmap.org/node/6410931438 la balise

Il s'agit très probablement d'équipement situés à un même endroit (Cf. cadastre et imagerie IGN). C'est pour cela qu'on recommande des intégrations plus que des imports. Il serait bon de regarder les man_made a proximité.
Jim005 (2019-04-21 13:07:52+00:00): Cool, je progresse :-) .  Ton exemple me pose une question parallèle. Doit-on définir un seul point géographique qui comporte plusieurs éléments : antenne TV, GSM, anémomètre ?

Ma question fait aussi écho au mapping (manuel) sur des caméras de surveillance que je commence dans un petit secteur. Sur certains points il y a 2 caméras (l'une orienté à l'Est, l'autre à l'Ouest). Ainsi je défini 2 points même s'ils sont positionné quasiment au même coin du toit. Devrai-je en faire qu'un ? (je ne ne peux pas définir 2 angles de vue, 2 type, etc.) 

Et donc par rapport à ton exemple, dois-je fusionner les points ? ou simplement les rapprochés (si ils sont sur le même poteau) ?  

merci : )
trial (2019-04-21 17:16:59+00:00): Ma règle pifométrique : si tout peut être sur un même point et l'est dans la réalité, autant le représenter comme tel. Mais man_made=tower;monitoring_station bof. Sinon les rapprocher. Tu pourrais mettre angle=90;270 mais ça empêcherait la plupart des clients d'utiliser l'information: autant les laisser proches. Tu peux aussi les avoir à la même position mais avec une ele (élévation, hauteur) différente. Mais ça c'est une piste à embrouille. On a vu des points géodésiques remplacés par un seul avec un ele avec point-virgule ! N'hésite pas à t'inscrire à [talk-fr](http://gis.19327.n8.nabble.com/France-f5380434.html)
marc__marc (2019-04-22 01:15:54+00:00): Merci de suspendre l'utilisation de cette source tant qu'il y a le problème de licence.
FFVL demande que chaque utilisation de leur donnée fasse l’objet d'une attribution ce qui est en incompatible avec la licence osm. exemple concret : une carte affichant le rendu d'une balise devrait faire un popup disant "la position de la balise affichée sur la carte provient de FFVL"
il faut leur demander une dérogation d'être listé en tant que contributeur en échange du renoncement au devoir de les citer à chaque utilisation de la donnée.
plus de détail sur la page du guide des imports
marc__marc (2019-09-16 11:56:57+00:00): Bonjour Jim005,
où en est-tu dans la demande à la source pour l'autorisation d'utilisation de leur base de donné ?
Jim005 (2019-09-18 14:52:25+00:00): Salut, je viens de recevoir leur autorisation d'intégration dans OSM. Je transfert leur email à qui pour avancer proprement ? :-)
trial (2019-09-18 16:12:00+00:00): Je te réponds en MP
trial (2019-09-18 18:50:44+00:00): En fait autant faire simple : tu peux compléter https://wiki.openstreetmap.org/wiki/Import/Catalogue et faire une page où tu anonymise les données (ou décris l'exception) en précisant message received on <date>.
Si quelqu'un a besoin du message il saura te contacter via le wiki ou OSM.
Tu peux mettre la licence initiale en précisant "with explicit exception".
Jim005 (2019-09-20 09:05:47+00:00): ok, j'ai ajouté une ligne ici :  https://wiki.openstreetmap.org/wiki/Import/Catalogue#Community_imports merci pour les explications
trial (2019-09-20 09:21:03+00:00): Merci, il y a au moins une erreur. Tu mets en référence dans tes objets ref mais sur le wiki tu dis ref:ID. ref:FR:FFVL:ID serait meilleur (il y a peut-être moyen de faire plus court). FR comme France, FFFVL comme FFVL ;-). Après si la FFVL n'a qu'un identifiant pour tout, ID n'est pas nécessaire. Il est peut probable que d'autres FFVL existent mais FR/ c'est plus prudent.
ref est problématique si un même objet peut être référencé dans des bases ayant des clés différentes.
trial (2019-09-20 09:26:37+00:00): Il faut aussi créer une page derrière Import des balises météo de la FFVL expliquant ta démarche (à quels attributs correspondent quoi, comment tu gère les conflits avec les balises déjà en base, etc...) : inspire toi du modèle.
barley383 (2025-11-09 11:39:24+00:00): Bonjour, 

En ajoutant des webcams je vois que les stations météo ajoutés dans cet import ont un tag "contact:webcam". 
Normalement, ce tag doit être mis sur les webcams où le flux vidéo est accessible en ligne. Je ne vois pas ce flux vidéo. 
Est ce que ces stations ont bien des caméras ? 
Si oui, ces caméras ont un flux disponible en ligne ? 

J'ai l'impression que la valeur dans "contact:webcam" est égale au tag "website", est ce une erreur?

 J'ai essayé de trouver la page wiki qui explique l'import mais je ne la trouve pas, si elle existe, je peux avoir le lien ?

Merci ^^
mavl (2019-07-21 15:45:07+00:00): This changeset was redacted. Reason: copyrighted data were used.
PeanutButterRemedy (2019-04-27 19:43:14+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
mavl (2019-07-21 15:45:10+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:45:14+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:45:17+00:00): This changeset was redacted. Reason: copyrighted data were used.
FvGordon (2019-07-14 19:26:10+00:00): With this chngeset you have uploaded about 490 duplicate buildings. Can you please remove the duplicate buildings.
Samwel Kyando (2020-08-09 06:09:54+00:00): okay.. lemme check that... though mass deletion is strictly prohibited by OSM i think.
mavl (2019-07-21 15:45:21+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:45:25+00:00): This changeset was redacted. Reason: copyrighted data were used.
silver mapper (2019-04-17 08:18:05+00:00): source link should read http://robert.mathmos.net/osm/prow/progress/oxon/south-oxon/crowmarsh/
PeanutButterRemedy (2019-04-27 19:41:53+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
eggie (2019-04-17 08:07:35+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
Sosha1996 (2019-05-02 18:32:07+00:00): بخاطر ویرایش‌هایی که روی نقشه میزنید ازتون ممنونم، اما لطفا در کامنت چنجست ننویسید ماکسیم. در کامنت چنجست باید توضیحاتی در مورد تغییراتی که دادید بنویسید.
با تشکر.
لطفا این متن را مطالعه کنید:
https://wiki.openstreetmap.org/wiki/Fa:Good_changeset_comments
Davide_sd (2019-04-17 21:14:50+00:00): Hello, I've seen you deleted the tag type from the trees. In some cases you correctly moved its content into the key "leaf_type". In other cases you moved the content into the key "name", and I argue this is a pointless change, because now we have plenty of trees' names displayed in the map (btw, those names indicates the species of the tree). I understand the need to map, but you should be more careful with your edits: if you are unsure of what you are editing, you must ask for help (OSM forum, or in this case Italian OSM talk list). Now, what are you going to do about the names?
GBAB (2019-04-18 09:49:46+00:00): Caro Davide,

yes, you are right, in part: originally, I just wanted to change the leaf type tags which were originally tagged as simple type, as far as I can remember (which is incorrect since type refers only to relations). Since I didn't want to delete tags in order to avoid losing data I moved some values under different (e.g. name) tags which, perhaps, wasn't the best method.

Anyway, I don't think the maps has become less usable even if there are some tree species now visible on the map.

Saluti: Gábor
Davide_sd (2019-04-19 18:00:04+00:00): Ok, I'll try to extract those trees with the name tag and add a fixme for future mappers. Ciao!
GBAB (2019-04-25 19:13:42+00:00): Caro Davide,
thank for the afterwork! Grazie
Gábor
abakus_uploader (2019-04-17 22:31:20+00:00): (Wiadomość automatyczna)
Cześć!
Otrzymujesz ten komentarz, ponieważ dodałeś lub zmodyfikowałeś adres, który jest niepełny lub błędny.
Adres powinien zawierać minimum trzy znaczniki: addr:city=[nazwa_miejscowosci] + addr:street=[nazwa_ulicy] + addr:housenumber=[numer_porządkowy].
Wyjątkiem są miejscowości bez nazwanych ulic - wtedy stosujemy znaczniki: addr:place=[nazwa_miejscowosci] + addr:housenumber=[numer_porządkowy].
Bez poprawnego oznaczenia adresów, nie będą one brane pod uwagę przez wyszukiwarki, dlatego warto je dostosować do ww. schematu (w zależności od sytuacji).
Więcej informacji na forum: https://forum.openstreetmap.org/viewtopic.php?id=5632 - a pytania najlepiej zadawać tu: https://forum.openstreetmap.org/viewtopic.php?pid=681873
Pozdrawiamy!
PeanutButterRemedy (2019-04-27 19:41:37+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
SomeoneElse_Revert (2019-07-02 16:16:51+00:00): This changeset has been reverted fully or in part by changeset 71796814 where the changeset comment is: Reverting a licence-incompatible import in Italy following a request to the DWG.  See https://lists.openstreetmap.org/pipermail/talk-it/2019-May/thread.html#66440 et al.
L'imaginaire (2019-04-17 10:35:16+00:00): Can you indicate wich path you are talking about? 
If it is a footway that cyclists are allowed to use, you can add bicycle=yes. Or you can decide to tag it as highway=cycleway of it is more a cycleway than a footpath.
tomdw (2019-04-17 11:10:23+00:00): strange, this comment was on another edit #69298744. This edit (#69299184) described a waterway
Vintagejhan (2019-04-17 09:39:17+00:00): 不好意思想確認說人行道是否塗銷以及行道樹被搬移走了嗎？謝謝！
Sosha1996 (2019-05-02 18:32:09+00:00): بخاطر ویرایش‌هایی که روی نقشه میزنید ازتون ممنونم، اما لطفا در کامنت چنجست ننویسید ماکسیم. در کامنت چنجست باید توضیحاتی در مورد تغییراتی که دادید بنویسید.
با تشکر.
لطفا این متن را مطالعه کنید:
https://wiki.openstreetmap.org/wiki/Fa:Good_changeset_comments
PeanutButterRemedy (2019-04-27 19:41:13+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
mavl (2019-07-21 15:45:29+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:45:33+00:00): This changeset was redacted. Reason: copyrighted data were used.
PeanutButterRemedy (2019-04-27 19:40:52+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
Cascafico (2019-04-17 12:04:29+00:00): Benvenuto in OSM!
Dovresti usare delle etichette approvate cos'è "pila"?) altrimenti lascia un generico building=yes