piebro/osm-data huggingface dataset:
Teiron (2020-03-30 07:31:04+00:00): ten zestaw zmian jest b. dobry, tylko brakuje mu komentarza
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/81291111
jptolosa (2022-10-04 21:46:00+00:00): Hola, de dónde obtuviste exactamente el nombre "San Ramón" para un caserío ubicado en el camino a Potrero Grande Chico? Hay alguna señalética en el lugar? Porque según las fuentes que manejo podría llamarse "Bajada de Rengo" (nombre que tenía antes de esta edición) o bien "Santa Laura".
Saludos.
PT-53 (2020-02-21 08:38:37+00:00): Hallo Neuschwadener,
Willkommen bei OSM.

Für Firmen bitte nicht nur den Namen eintragen sondern immer auch den Firmenzweck.
Hier solltest Du die passenden Merkmale finden:
Wiki - office:
https://wiki.openstreetmap.org/wiki/DE:Key:office
Grüße
ToniE (2020-02-21 11:14:37+00:00): office=it hinzugefügt
Polarbear-repair (2020-02-25 02:02:55+00:00): Please refrain from removing the more modern tagging of "natural=water + water=reservoir". Repaired.
Marek-M (2020-02-28 09:01:40+00:00): Widzę, że zmieniłeś ścieżki rowerowe na chodniki dla pieszych. Mógłbym wiedzieć skąd taka zmiana? Z tego co wiem, to ostatnio nic się tam nie zmieniało i wciąż to wygląda tak jak na obrazku ze zdjęciem satelitarnym: https://imgur.com/IxxLC3B
Szymson (2020-02-22 19:59:48+00:00): Hej, widzę że jesteś nowy w OSM, z tego powodu pragnę Ci zwrócić uwagę na kilka spraw. Otóż SOR to nie amenity=hospital tylko amenity=clinic (patrz przykład z Krakowa: https://www.openstreetmap.org/node/3036817877), to samo tyczy się stacji dializ, zapraszam do lektury artykułu na wiki OSM o szpitalach: https://wiki.openstreetmap.org/wiki/Pl:Tag:amenity%3Dhospital

W razie problemów czy pytań, to śmiało, zapraszam do dyskusji :)
osm2327 (2020-02-20 22:37:37+00:00): Reapertura hoy de la calle Albia de Castro, con doble sentido ciclista

fuentes:
- publicaciones:
https://www.rioja2.com/n-139808-3-se-reabre-la-calle-albia-de-castro-con-aceras-mas-anchas-y-mayor-accesibilidad/
https://www.facebook.com/logronoenbici/posts/2614010982042456
- fóto plano oficial: https://framapic.org/gallery#TTnupelxuhwb/JrzKqLpdfpwy.jpeg (enlace vigente 1 año)
- visita víspeda de apertura:
  - fótos: https://framapic.org/gallery#gXMMybU3j0CH/LOKsFk8ijefV.jpg,K9SweEtnUVpN/42JNIKGAQyqo.jpg,fPkmZHWsC9LY/InIFdz0LW7z0.jpg,YJwkc2BqSnqb/USiTvDfABR8m.jpg
  - video recorrido: https://framadrop.org/r/a3qyPFhwlO#5hOZwFTnDdTplwpGbhIdMFJpKtUObwEJq7Rfb68/sxU= (enlace vigente 1 mes)
eggie (2020-02-20 23:10:35+00:00): Dag Pepe..  Kijk voor opening_hours even hier naar het juiste formaat. Selecteren en het resultaat in de "waarde" plakken.
openingsuren-tool:

http://projets.pavie.info/yohours/

MVG,
Eggie
eggie (2020-02-22 09:14:02+00:00): Openingstijden aangepast conform wiki.
Adamant1 (2020-02-22 13:40:44+00:00): What's with the micromapping of the roads? The name tag isn't meant to be used as a way to describe something like your using it here. It should only be used for names. Anyway, its uncessary to describe what roads the road is between, people can tell by looking at the map. Plus, it just pointlessly adds clutter.
Tyler Brown Cifu Shuster (2020-02-22 15:24:16+00:00): Good point. I'll leave them unnamed
Mike Raust (2020-09-23 23:49:07+00:00): "Esri World" is not the newest, please don't use it exclusively.
frosm (2020-02-21 10:56:23+00:00): Bonjour et bienvenue https://wiki.openstreetmap.org/wiki/FR:France/bienvenue
merci pour la maj, j'ai complété l'url et enrichi les attributs
bonne continuation
TagaSanPedroAko (2020-08-12 00:54:43+00:00): Is Pili-Sagñay traditional or modern jeepney route? I'm going on retagging and fixing that route.
DP24PH (2020-08-12 14:54:41+00:00): Traditional/Classic PUJ Route.
TagaSanPedroAko (2020-08-12 20:37:42+00:00): Terminals?
user_5359 (2020-02-21 05:18:46+00:00): Welcome to OSM! Note that in OSM classification of the objects has the highest priority. Objects that have only name and description, have little sense. As home page for the question "How do I describe you?" I recommend the web site http://wiki.openstreetmap.org.
olo81 (2020-03-02 00:00:55+00:00): Ale fajnie :) A zastanawiałem się gdzie znaleźć takich miejsc więcej. 
Oj będzie coraz więcej odwiedzających :D
BCNorwich (2020-02-21 08:03:50+00:00): Hi, Welcome to OpenStreetMap.
I've removed the width=0 tag from Way: 133033448 as it does not allow use of the track.
I removed the name from Sparse trees and nettle border (775132613, v1), I very much doubt if that's is a formal verifiable name.
I've removed the width=0 tag from Way: 775132612 as it does not allow use of the path, if the width can't be determined please don't put 0 width as that's incorrect and says there is no path, (routers would not select that way as usable because of the restriction).
Removed a white space from the end of your fixme tag as it made the fixme invalid. Usually any extra so space (so called white space) makes a tag invalid.
Otherwise pretty good start, don't be put off by a few mistakes as there's a lot to learn about OSM mapping. Please just ask if you need help.

Regards Bernard.
BCNorwich (2020-02-21 08:08:30+00:00): I then found more white space in that fixme, you double spaced between fullstops and capital letters.
Tom-6 (2020-02-21 19:05:29+00:00): Hi :) Thanks for fixing my errors and letting me know about the house-style. 

Yeh, that was not a formal name, i just wanted to emphasize it because i realised it's a really clever way of handling so many potential problems and the play-park seems under-used. I was hoping that width=0 would be treated differently.  In effect the path is the width of the play-park as people use all sorts of different routes between the gates.  Prior to my edit it looked as though the path just suddenly stopped and became impassable until you zoomed in enough to see the play-park clearly.  The path i use just slightly north of that is similarly fuzzy-edged.  The grass tends to grow a bit longer off either side of the 3m(ish) wide path except where freshly eaten by the herd of cows. If the herd is on that path i just walk through the longer grass and keep my distance - but the line on the map shows the average (median) route, the route one hopes to take if pressed for time.

So i tried to treat the route through the play-park in the same way so that it is visibly a viable route too.

Anyway, thanks for fixing all those things for me :) Now i have a better idea of how to handle such problems in the future :)  

Thanks and regards from a Tom-6 :)
user_5359 (2020-02-21 05:17:23+00:00): Welcome to OSM! Note that in OSM classification of the objects has the highest priority. Objects that have only name and description, have little sense. As home page for the question "How do I describe you?" I recommend the web site http://wiki.openstreetmap.org.
ralley (2020-02-22 11:50:30+00:00): As discussed via PM I have undone this change and all the others that wronly changed Saint Lukes to St Lukes.  This is as per https://wiki.openstreetmap.org/wiki/Naming_conventions#Don.27t_use_abbreviations
Omnific (2020-02-21 02:05:03+00:00): Hi, just a heads up, these schools have what are called school grounds (they show up yellow) that surround the main building. The convention is to only name the grounds, not the building with the name of the school. Otherwise there is a duplicate entry for every school. 

Let me know if you have any questions. 

Thanks for your edits though!
user_5359 (2020-02-21 05:15:01+00:00): Welcome to OSM! Short question to https://www.osm.org/way/651799193/history and https://www.osm.org/way/25053472/history. Why did you overwrite the ameinty=school and the building key with area? Did you know the difference between layer and level and building:level?
aconver (2020-02-21 17:11:32+00:00): @omnific thanks for your feedback. I understand not wanting duplicates, but if the school buildings aren't assigned names it means that they can't be identified when exported through OSM Buildings. Is there a work around for this issue?
Omnific (2020-02-21 18:43:26+00:00): One of the key rules is never to "tag for the renderer", which OSM buildings essentially is in this case. OSM buildings is third party software, and therefore should not be used as the basis for changing the core OSM dataset. We had similar issues with people changing data to make certain things happen in the game Pokémon Go. I'd submit a request to whoever maintains that software to add a conflation algorithm to conflate the names from the amenity=school area onto the biggest building within the bounds of the school area or just add the school areas directly to the map.
mbethke (2020-02-21 06:15:48+00:00): Why are you doing this? It makes absolutely no sense. There are no tunnels.
rskedgell (2020-02-21 09:53:35+00:00): Hi, just a quick question about putting the highway=traffic_signals node "before" the cycleway=asl node.

The wiki entry for cycleway=asl has "a marked area for cyclists in front of the stop line for motor traffic", together with a diagram only showing the case where there is a single highway=traffic_signals (where obviously the ASL can only be mapped "before" the traffic signals).

I wonder if it's worth raising it on the tagging list, particularly wrt processing the nodes for routing, then updating the wiki entries to clarify.

I have always mapped the nodes the other way around, so I may have a few edits to make...
MacLondon (2020-02-21 17:26:40+00:00): Hi. As you mention, the problem with the wiki is that it only considers the situation where the junction node has the traffic_signal and doesn't deal with situations where the traffic_signals are mapped separately on each of the junction roads.

In the past, after reading the wiki, I also used to do the way you seem to be doing it, so I can understand the confusion. It seemed illogical that cyclists were stopped for a traffic_signals that was behind them, yet that was how asl's were being generally mapped.

However I later realised what people were were doing is mapping a traffic_signals node where the stop line for motorists is (the point where the traffic_signals control takes effect), and that this node was not being used for where the traffic_signals are physically located.

Although cyclists have a waiting area in advance of this, it is the cyclists' stop line (i.e. the front line of the box) that is the cycleway=asl.

Basically, cyclists would be subject to the traffic_signal node 'behind' the asl but can pass in advance of this traffic_signal node to stop at the asl.

It's very possible that a definition of an 'Advanced Stop Line' could be the motorists' stop line rather than the cyclists' stop line, but I can't see why a "cycleway=*" tag in OSM would be used for the purpose of mapping the rear stop line (instead of a "motor_vehicle=asl").

I don't think the asl tagging is satisfactory, but I'm also not sure how much it's being used in routing etc.
rskedgell (2020-02-21 18:32:18+00:00): I think you're right, but I'll start a discussion on the tagging list before doing anything rash like updating the wiki pages or transposing the order of the nodes in my edits.
cleatsstore (2020-02-25 10:14:20+00:00): https://cleatsstore.com/
Adam Franco (2020-03-06 18:11:58+00:00): Hi andrepoiy, Just this past year the city has restarted its plans to build out these parts of I-189:
https://vtdigger.org/2019/08/25/decades-later-champlain-parkway-construction-finally-nears/

As well, even if construction had been abandoned or on hold indefinitely, there still is on-the-ground concrete in these locations. The construction area is commonly accessed by pedestrians, so I think that leaving it as highway=construction is appropriate.
andrepoiy (2020-03-06 18:32:50+00:00): Construction hasn't actually started, which is why I think highway=construction is inappropriate. Perhaps using the disused tag  would be more appropriate.
A67-A67 (2020-02-21 02:30:13+00:00): Hallo Fireman2130,
Dit stukje weg hoort wel gewoon highway=unclassified te zijn. Een weg op een kruising krijgt de hoogste wegclassificatie die van dat stukje weg gebruik maakt. In dit geval is dat de zijweg Machineweg-Korteraarseweg, dus unclassified.

Link-wegen gebruiken we voor afritten en 'gekanaliseerde' stukken weg op kruisingen. Daar is hier geen sprake van. Zie ook https://wiki.openstreetmap.org/wiki/Highway_link
FM2441 (2020-02-21 04:32:04+00:00): Hallo A67-A67,

Dank voor de tip!
A67-A67 (2020-02-21 02:32:14+00:00): Ook hoort de weg gewoon highway=secondary te zijn. Zie ook https://wiki.openstreetmap.org/wiki/Highway_link
A67-A67 (2020-02-21 02:34:06+00:00): Ik heb deze en de kruising bij de Machineweg hersteld.
Mevess (2021-12-01 14:04:53+00:00): Bonjour Olyon,

Eyzin-Pinet semble bel et bien le nom officiel de la commune, pourquoi l'avoir changé ? Le cas semble similaire à Cour-et-Buis plus au sud

Cordialement, 

Mevess
Olyon (2021-12-04 17:59:34+00:00): Bonjour  Mevesscartographie,
Je n'ai pas changé le nom de la commune 
https://www.openstreetmap.org/relation/168953
qui est bien Eyzin-Pinet mais sur la commune il y a 2 villages Eyzin et Pinet donc dans osm 2 nodes place=village (Pinet est peut être plus un hameau mais comme il donne son nom à la commune ça "augmente" son importance).
Pour Cour-et-Buis, si c'est la même chose, 2 villages qui s'appellent Cour pour l'un et Buis pour l'autre, il devrait y avoir 2 place=* avec ces noms.
Cordialement,
Olyon
user_5359 (2020-02-21 05:07:43+00:00): Welcome to OSM! The key "building:levels" counts the level of a building above the ground. It is therefore a number. Please check the given value.
Supaplex (2020-06-18 13:55:15+00:00): 恭喜您完成第一次的地圖編輯！ 歡迎加入開放街圖，群眾共同參與，繪製生活週遭大家關心事物的共編地圖。以下是相關的參考資料，歡迎隨時指教與提問。

編輯須知
台灣的標示依循準則可參考 http://wiki.openstreetmap.org/wiki/Taiwan
常見的圖徵標示方式可參考 http://wiki.openstreetmap.org/wiki/Zh-hant:Map_Features
給Pokemon Go玩家的建議：https://wiki.openstreetmap.org/wiki/Tips_for_new_(Pokemon_Go)_mappers
組織性編輯指南：https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines

台灣社群網站
台灣 OpenStreetMap 網站 https://osm.tw/
臉書粉絲頁OpenStreetMap台灣 https://www.facebook.com/openstreetmaptaiwan/
台灣社群Facebook社團 https://www.facebook.com/groups/OpenStreetMap.TW/
郵件論壇 https://lists.openstreetmap.org/listinfo/talk-tw
Telegram OpenStreetMap Taiwan https://t.me/joinchat/Aqu2IgnTuIidMfREdNmomQ
Telegram OpenStreetMap Asia https://t.me/OpenStreetMapAsia
Slack https://osm-tw.signup.team/

Happy Mapping!
viloan (2020-02-21 02:38:42+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 você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
Hb- (2020-02-28 00:07:41+00:00): Please do not create overlapping areas. I revert this changeset in #81567266
SomeoneElse (2020-03-08 22:04:31+00:00): Hello Hb-,

It's perfectly normal for a park or a residential area to contain woodland.  Can you explain exactly what the problem is with the overlap here?  

Best Regards,

Andy
Hb- (2020-03-09 00:05:31+00:00): "Overlapping areas" are in principle bad and therefore marked as such by any reasonable editor.

A piece of land should not have landuse=residential and landuse=forest together. Logically landuse=forest is the same as natural=wood.
SomeoneElse (2020-03-09 01:17:28+00:00): > "Overlapping areas" are in principle bad
Can you explain why?  Can you point to anywhere in OSM where such a consensus has been accepted?
Hb- (2020-03-09 12:21:52+00:00): You ask me to explain why overlapping areas are bad?

Please see: https://josm.openstreetmap.de/browser/trunk/resources/data/validator/geometry.mapcss#L185
SomeoneElse (2020-03-11 22:14:05+00:00): Sorry, but how is that relevant in any way?
Hb- (2020-03-12 10:50:33+00:00): What is bad with the current state of the objects in the map?
SomeoneElse (2020-03-12 11:09:15+00:00): > What is bad with the current state of the objects in the map?
Well that's an entirely different question to " Can you explain exactly what the problem is with the overlap here?" and "Sorry, but how is that relevant in any way?", and the answer is it depends on how things look on the ground and how they got to be how they are.  If the stand of trees predate the establishment of the park and its existence is irrelevant to theirs, I'd probably map the trees as one lot.  If they're obviously separately maintained (something you'd probably only be able to see on the ground) I'd probably map them as two.
But as I said, that's an entirely different question to the ones that you were asked.
REgards,
Andy
Warin61 (2020-03-12 21:53:14+00:00): >What is bad with the current state of the objects in the map?

Cons:

Increases data bloat.

Increases probability of future editing errors.

Increases mapper work load

Increases render work load

Pros:
None.

------------------------
There is nothing 'wrong' with having the trees as a continuous area, any overlap is not a problem unless the thing overlapped is another land cover.
muralito (2020-02-21 11:02:21+00:00): Hola.

Por favor tené mas cuidado, sobre todo con los datos ya existentes. Borraste la rotonda y quedaron rotas varias lineas de transporte.

Y a la que dibujaste nueva para sustituir no le pusiste ningun dato y quedaron faltantes.

Hace cambios mas bien chicos y de cosas del mismo tipo, asi si hay errores se pueden revertir facil sin perder lo que tengan hayas hecho bien.
Kaissner (2020-02-21 23:17:55+00:00): hoy las iba a terminar, viajo casi todos los dia por esa rotonda y algunas lineas de colectivos ya no pasaban por ahi, podrias haberlo simplemente marcado como fix me, estuve 4 horas haciendo cambios pequeños por toda la ciudad
muralito (2020-02-26 12:54:10+00:00): El ruteo es de las funciones principales y borrar la rotonda y dibujarla de nuevo como hiciste dejo rotas muchas cosas y perdia la historia de cambios. Revertirlo era la forma de recuperar lo anterior.

Como recomendé antes, es mejor hacer cambios chicos por separado, y no agrupar muchos no relacionados en uno grande.
LucasLarson (2020-03-18 03:53:45+00:00): ✅ I merged the information from both nodes into the older one and deleted the newer one (see changeset 82326689)
DP24PH (2020-02-21 06:56:12+00:00): It looks like the PITX -> Lucena -> Dalahican is present as of this date since 13 August 2019 upon PITX FB Page, and it needs immediate secondary fix.
Supaplex (2020-06-18 13:55:32+00:00): 恭喜您完成第一次的地圖編輯！ 歡迎加入開放街圖，群眾共同參與，繪製生活週遭大家關心事物的共編地圖。以下是相關的參考資料，歡迎隨時指教與提問。

編輯須知
台灣的標示依循準則可參考 http://wiki.openstreetmap.org/wiki/Taiwan
常見的圖徵標示方式可參考 http://wiki.openstreetmap.org/wiki/Zh-hant:Map_Features
給Pokemon Go玩家的建議：https://wiki.openstreetmap.org/wiki/Tips_for_new_(Pokemon_Go)_mappers
組織性編輯指南：https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines

台灣社群網站
台灣 OpenStreetMap 網站 https://osm.tw/
臉書粉絲頁OpenStreetMap台灣 https://www.facebook.com/openstreetmaptaiwan/
台灣社群Facebook社團 https://www.facebook.com/groups/OpenStreetMap.TW/
郵件論壇 https://lists.openstreetmap.org/listinfo/talk-tw
Telegram OpenStreetMap Taiwan https://t.me/joinchat/Aqu2IgnTuIidMfREdNmomQ
Telegram OpenStreetMap Asia https://t.me/OpenStreetMapAsia
Slack https://osm-tw.signup.team/

Happy Mapping!
maxerickson (2020-02-22 12:31:45+00:00): Some empty tags introduced in this changeset.
iandees (2020-02-22 14:34:49+00:00): Thanks for pointing it out. I'll fix the data.
tastrax (2020-03-22 03:12:42+00:00): Hi folks FYI - Phone numbers in Australia should be added according to the following format +61 x xxxx xxxx as per the wiki guidelines https://wiki.openstreetmap.org/wiki/Australian_Tagging_Guidelines - I have just updated a recent addition that you made to OSM - Cheers
Polarbear-repair (2020-03-09 03:06:34+00:00): More precisely, this is a mechanical removal of brand:wikipedia tags itself.
tastrax (2020-03-22 02:59:27+00:00): Hi folks FYI - Phone numbers in Australia should be added according to the following format +61 x xxxx xxxx as per the wiki guidelines https://wiki.openstreetmap.org/wiki/Australian_Tagging_Guidelines - I have just updated a recent addition that you made to OSM - Cheers
viloan (2020-02-21 03:43:37+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 você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
viloan (2020-02-21 04:03:47+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 você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
dpolovinkin (2024-05-27 12:16:46+00:00): hi! I don't know what happened, but what you mapped here is extremely crude and just incorrect, will delete it all and remap

Thanks!
mbethke (2020-02-21 06:34:38+00:00): Hi,
that's not exactly an office, is it? You can use man_made=tower with tower:type=communication here.

cheers,
Matthias
Warin61 (2020-03-07 07:33:50+00:00): Hi,
Way 775161958 tagged highway=footway with construction=yes is not how OSM does that ... it is highway=construction with construction=footway. Fixed this one.