Requisitos

• Plugin areaselector
• Plugin Scripting

Em locais onde o contraste de cores é bem definido, você pode usar o plugin areaselector para adicionar áreas de forma mais ágil — basta apenas um clique.

O contorno ficará com uma aparência serrilhada, com ângulos de 90°.
O segundo passo é fazer uma suavização usando o plugin Scripting, com o código disponível aqui.

… See full entry

I am a new editor of OSM, and I thought I would explore the tools and update familiar areas for myself. I added and updated areas in Bronte Creek Provincial Park. The OSM tools made it really easy to add new areas, points of interest, add some walking trails and label everything with accurate details. The park was already mapped with buildings, trails, roads, parking lots and much more. A lot of what I found myself doing was adding newly labelled areas, ex. Cow Barn, Cow Pasture. I am very familiar with BCPP, and now anyone looking to go to the park can have a better idea of what is really there. OMS is very easy to navigate, and I enjoyed using this mapping software. Not only is it a great tool to add for other people to use, but it is also great to see what is really in your surroundings.

Ivan ha pubblicato recentemente una mappa dei CAP fatta da koriander sul gruppo Telegram @OpenStreetMapItalia.

Saltava subito all’occhio che c’erano diversi errori nei dati sorgenti su OSM. Perciò ho iniziato a fare delle query con overpass turbo per trovarli.

La prima cosa che ho fatto è stata quella di fare una query per trovare valori del tag addr:postcode che iniziano con una lettera diversa rispetto all’area geografica in cui si trovano. Ad esempio, in Piemonte, i CAP iniziano tutti con “1”, a eccezione delle province di Novara e del Verbano-Cusio-Ossola.

Ho scoperto che alcuni indirizzi sono stati copiati dal web. Di per sé non è un problema, ma lo diventa se il mappatore non capisce che il POI che sta aggiornando non è quello recuperato su Google e quest’ultimo si trova invece a centinaia di chilometri di distanza. Ad esempio questo, questo e questo.

Poi ho fatto una query che restituisce i CAP sintatticamente errati, ovvero che non sono composti da 5 cifre.

Ho così trovato che molti degli attracchi dei vaporetti a Venezia avevano un CAP (!!). La cosa più strana è che il valore era sempre “30121-30176”.

A guardare bene, però, questo fenomeno non era limitato a Venezia. Continuavo a trovare CAP in questo formato in tutto il Nord-Est e non capivo perché. Tra l’altro il tag “addr:postcode” era stato inserito anche nei posti più assurdi (fermate del vaporetto, monumenti ai caduti, ecc).

Poi ho avuto una illuminazione: il dato è stato copiato da Wikipedia senza alcuna verifica.

Dopo aver analizzato un po’ di changeset ho notato che TUTTI gli edit sono stati fatti con Organic Maps.

Ho quindi scoperto che Organic Maps compila automaticamente il CAP prendendo il dato da Nominatim, che a sua volta lo prende dal tag postal_code.

Tutti questi tag postal_code sono stati aggiunti dallo stesso utente nel 2023 (ovviamente copiandoli da Wikipedia).

Fine storia triste.

I cycle around town a lot and I’d like people to join in. One of the barriers to entry is finding safe routes so I thought I’d try and update the map with the cycle infrastructure as it is built.

I was also pointed at StreetComplete so I’ll log more metadata in my area as I wander about.

Quante rastrelliere ci sono?

Censimento in Pisa

Siamo a Pisa, la Fiab ha organizzato un censimento delle rastrelliere presenti in tutto il comune. Attraverso la web-app Ushahidi, dopo aver caricato le rastrelliere già esistenti, sono stati raccolti i dati con l’aiuto di tutti i bikers della città.

Revisione

Ora abbiamo revisionato tutte le pubblicazioni e scaricati su un file CSV.

Pubblicazione

Siamo ora pronti per fare un import su OSM. Se qualcuno ha dei consigli, suggerimenti, e quant’altro si faccia avanti.

Grazie e buon lavoro a tutti.

Ok, my good friend Butterball wanted to pay me a visit from Bree. You all know how he is, super braggy. He told me he just got a brand new iPhone version 1 with 20 KB of RAM. I was like, “Okay, cool, Butterball. We’ll see you. Just don’t be braggy.”

He wrote me a long letter promising me that he wouldn’t be braggy, but then he told me about a problem that he had. He had too many footpaths coming up on his map. He couldn’t find the way easily. Every time he brought up the map, his iPhone crashed. Check out the shire with all of the footpaths!

Crazy Map With Footpaths!

I told him, “Don’t worry, I’ll just modify his map with a new layer with just roads on it instead of all the other extra crap.”

I was like, Open Street Map is pretty awesome, but they include a lot of stuff in their layers, and then they let you just claw back what you want. I think what we want to do is modify it so we only show the tags that we want, so your map doesn’t crash. Does that sound like a good plan?

… See full entry

🚀 Projeto Mapeia Brasil - Mapeia Brasil Project

História do Projeto

O Mapeia Brasil é um projeto que surgiu com a missão de melhorar a qualidade dos dados geográficos no Brasil, com foco na atualização e correção dos nomes das ruas e vias no OpenStreetMap (OSM). A ideia foi originada em 2025, após uma análise comparativa entre os dados do OSM e os dados do IBGE (Instituto Brasileiro de Geografia e Estatística), especificamente do Censo de 2022. Durante esse processo, foi identificado que 13 cidades brasileiras precisavam urgentemente de atualizações nos seus dados de vias. O projeto visa corrigir essas informações para melhorar a navegação, os serviços públicos e facilitar o uso de aplicativos de transporte, compras online e outros serviços essenciais.

… See full entry

I have a couple of web maps, and they are supposed to show pedestrian crossings. If there’s some crossing infrastructure (for example - zebra stripes, or tactile paving and a lowered kerb) you’re supposed to see a “crossing” icon. If there are traffic signals associated with the crossing, that icon should be replaced with a “traffic signals” one.

Years ago it was straightforward - you’d get a highway=crossing tag on a node on the roadway, and there would be another tag, such as crossing_ref to say what sort of crossing it was. Some crossings (such as pelican, puffin and pegasus) have traffic signals; others (zebra and informal crossings) tend not to.

Unfortunately, it has got a lot more complicated.

Sometimes, the highway tag is crossing;<something> or <something>;crossing. Sometimes that something should be ignored and treated as a crossing.

… See full entry

One of the most important things I learned about mapping with OpenStreetMap is how collaborative and detailed the global mapping community is. Every edit, no matter how small, contributes to a shared, constantly evolving map that supports navigation, humanitarian efforts, and local development. I realized how crucial accuracy and verification are, each feature needs to be placed and tagged correctly so that it’s useful for others. The most challenging part of editing OSM was learning the tagging system and ensuring that my edits followed mapping conventions. I mainly mapped in areas that lacked detailed data. Overall, the experience showed me how open data and collective participation can create powerful geographic resources that benefit communities around the world.

I edited an area where I grew up and frequently return. I chose to focus on some features in this area, as I figured some would be missing or incorrect due to fewer resources to investigate them and their lower priority given the town’s smaller size. I decided to start with elements I knew were recent in the town, such as the opening, closing, or rebranding of businesses. Then I moved into land-use elements, as some areas were assigned to a broader category when a more specific use could be assigned. I updated some other features as well, like microfeatures in Murphy Park and Canada Post mailboxes, but I mainly focused on businesses and updating the elements around them. I learned that, in OSM, you can get a lot more detail on land use in an area, which I thought was a really nice feature. One of the challenges for me was finding the aforementioned resources. If I had not frequented this area, it would be difficult for me to understand what to update or add, as the larger mapping services are also outdated. I foresee this as a challenge with OSM: without someone in a small town committed to making changes, they will slowly lag behind the already slow giants in the industry.

The areas I mapped are familiar to me, so I was able to add new things that haven’t been marked on OpenStreetMap before. The most important thing about OpenStreetMap, to me at least, is how much contribution is needed to keep everything accurate and up to date. There were some edits in that area that were made 15 years ago, some that haven’t been modified to accurately display the area (under LuLu’s Variety, the block of houses is labelled as a park 15 years ago, when it isn’t a park now). The most challenge I had while editing was trying to accurately name certain buildings. For example, Itec Equipment is a building material supply store, but there weren’t any labels like “Supply Store” or “Building Supply Store”; the best I could label it with was “Rural Supplies Store, but I’m not sure if that is accurate.

For this OpenStreetMap activity I focused on adding and improving features in an area I am familar with. I contributed information based on places I know, such as my University campus, which made the mapping process both meaningful and interesting to me. I think it is very important to share accurate and local information in OSM, because small details can make a big difference. I also noticed that some information around my area is outdated or incomplete, so in the future I would like to contribute more.

Paused due to seasonal work. I’ll get back to this at some point January.

I seem to have started on the questionable task of adding all the bus routes in Halifax.

I’ve been grabbing the route description from the Halifax Transit website, creating the route relations via Id and then adding to the relation with OSM Simple Route Editor. (I’d prefer to use OSM Relatify, but it seems to take a while to notice that the relation has been created or is having some other issue.) I have been using Relatify to verify that the route is correctly ordered and connected. I have also used the sort feature in JOSM “PT Assistant” plugin to deal with grumpy route alignment.

I have been doing inbound and outbound legs of the bus route as separate routes to avoid the complications from using the same way twice. In the case of the 1, they were already split like that with a master route that joined the two which seems rather elegant. But, it may be worth seeing if there is a way to join the halves together after the fact.

Here’s the overpass-turbo query I cobbled together to find current OSM routes (it mostly worked):

[out:json][timeout:25];
// gather results
(
  relation["type"="route"]["route"="bus"]["network:wikidata"="Q14875719"]({{bbox}});
  relation["type"="route"]["route"="bus"]["operator"="Halifax Regional Municipality"]({{bbox}});
  relation["type"="route"]["route"="bus"]["network"="Halifax Transit"]({{bbox}});
);
// print results
out meta geom;

So far I have found these routes either in OSM or via the current list of route descriptions:

… See full entry

Ich suche gerne erstmal in blogs, aber hier geht es leider nicht, oder ich weiß nicht, wie. Eigentlich bin ich über die App “nora” darüber gefallen, daß eine Straße mit PLZ einem Ortsteil zugeordnet wurde, aber nicht dem Hauptort, wo diese Straße wirklich ist. Wie kann man so etwas korrigieren ?

Mit +++ gekennzeichnete Einträge basieren auf von mir programmierten Erweiterungen. Diese werden regelmäßig aktualisiert; im Kopf dieser Seite wird der Zeitstempel der letzten Aktualisierung angezeigt.

• +++ OpenStreetMap-Wiki DE:How to map a [A..Z]
  Aus dem OSM-Wiki DE:How to map a wird jede Seite des alphabetischen Registers [A..Z] ausgewertet; alle Attribute (EN: tags) werden auf einer Seite gelistet, ein Suchfeld erlaubt die Filterung auf Teilstring-Filter.

• OSM Telefonnummern-Validierung

我主要绘制地图的地方都是我熟悉的地段。伦敦的地图早已细致得无可挑剔，我所能做的，不过是依照自己的实地探访，添几笔修补与更新。而那些我真正想描绘的地方——韶关、狮山——在地图上却几乎是一片空白。于是我盯着卫星影像，凭借记忆，一条一条地把它们补上去。

然而，一旦动笔，记忆便被无声地唤醒。

狮山的郊外，是满目灰尘与机器轰鸣的工业区。但在那段短暂的大四下学期——也正是中国放开三年疫情封控的时节——我几乎把所有空闲都花在漫步上。我终于能重新走出校门。那是一种久违的自由，也是一种怅然的陌生。我在风尘漫天的乡村与工业区之间走走停停，感受空气、阳光，还有一种模糊的“重生”的气息。如今每当我在地图上画下那一条条路，心里都能重新浮现当时看到的一切：斜阳下的厂房、贴着褪色标语的围墙、被工厂分割得七零八落的农田……

狮山的城区，则是我课余时常去的地方。几个广场、几座公园，见证了太多微小却清晰的瞬间——我记得每一次同行的人，记得谈笑的片段，甚至记得那时吹过的风。

而狮山大学城，那更不必说。四年光阴的流动，几乎都沉淀在那片土地上。无数的晨昏交替、无数未完的对话、无数被时间吞没的小事——都化作我记忆的一部分。

再往前追溯，就是韶关，我的故乡。那座夹在群山之间的袖珍小城，从小到大承载了太多我的生活。每一条街道、每一个转角，都藏着旧日的故事。那是一个人生命中最初的坐标，是无论走多远都无法抹去的印记。

所以，当我坐在远在数千公里外的伦敦，往这些空白的区域绘图的时候，心里总会冒出一个问题：

——我到底该留在哪里？

年初的时候，我曾以为这一年会让我找到答案。但时至今日，犹豫仍在。

文化上，我当然认同留在广东。嗰度嘅语言、食物、人情，都系我最熟悉、最舒服嘅空气。

可与此同时，也有些记忆在暗暗提醒我：不要回去。那些过去几年留下的痕迹——恐惧、疏离、无力感——仍像一层薄雾，笼罩在记忆的上空。我怀念那片土地，也被它深深刺痛。

​I love my country, but not the party.

我爱这片土地，也爱生活在其上的人们。

但那份爱并不来自，也不属于盘踞在那片土地之上的权力、旗帜，与口号。

也许我找不到一个可以真正安放自己的地方。但我希望，那些我亲手画下的线，能在虚拟二维的OpenStreetMap里，延续我对故土最温柔的告白。

Não gosto muito de falar em público ou coisa assim mas me deu vontade então vou falar coisas

Algo que eu percebi é que no openstreetmap aparecem as localidades como Jurerê, Campeche, Lagoa, etc… mesmo elas não tendo fronteiras certas, e também que tem um monte de distrito que não tá no mapa Mas agora começaram a oficialização dos bairros aqui e eu acho isso muito bom mas agora eu não sei quem vai atualizar pq sem contar eu eu só vi tipo 1 ou 2 pessoas aqui editando Enfim só isso

Some news and visions about topic focused contribution monitoring capabilities of Podoma software

Podoma platform

For more than 6 years, former ProjetDuMois platform now Podoma was used to plan, encourage and monitor “Projects of the month” by French community (and some other countries too). It has been a significant progress for people responsible of those very short projects as it has freed us from the hassle of counting changesets and provides a mappers-friendly customized editor.

… See full entry

出于个人的隐私考虑，本人的 OpenStreetMap 账户的用户名使用化名，敬请谅解。

简介&来意

我是一名陕西省咸阳市的中学生，在探索开源软件的过程中遇到了 Organic Maps、CoMaps 和 OsmAnd~，并认识了 OpenStreetMap。由于对开源软件的热爱，以及发现 OpenStreetMap 对中国大陆的小城市（包括我居住的城市）的数据支持不够完善，因此想做出一些贡献，用这种方式帮助自己身边的人以及需要的人（虽然周围的人没有一个知道 OpenStreetMap，但是万一他们哪一天需要呢）

一直以来，坐标系统的不一致导致 Google 地图和其他海外地图在中国大陆的卫星影像和人工标注的道路信息差了上百米，国内的地图软件对国外的数据支持也有限，更重要的是国内外主流的地图产品出于商业考虑不向公众共享地图数据，OpenStreetMap 在这一点上无疑是很好的开源替代品。但其在中国大陆（在国外也可能符合这个规律）的地图数据的详细程度大致与这个地区的经济发展状况成正比关系（正常，商业地图公司的员工开车全国跑，地图数据也要详细的多），这容易让人误解：某个地方除了道路什么也没有。

编辑地图只是出于我对开源软件和开放数据的热爱，而且也不是我的正事，因此我每天不会花太多时间在这件事上。

事件

1. 在 2025 年 10 月 29 日，我收到了贡献者 booktiger 发送的一封欢迎消息，并且阅读并了解了中国的法律情况和编辑指南（说实话我只是想完善一下居民区建筑信息以及店铺信息，我连监狱都不想往上画，更不要说国家机密了），也阅读了他参与的一些讨论（比如 397559）。

   本人对政治并不感兴趣，但这并不意味着本人没有一点政治常识。对于台湾问题，我很庆幸 OpenStreetMap 上没有标注国界线，这避免了许多潜在的争议（虽然一些人将水陆分界线当成了国界线并且发表自己的意见，比如 395824）。但是如果你因为 OpenStreetMap 没有给“台湾”后面加“省”感到特别生气，也可以在网络上发表自己的意见。我绝不会干涉任何一方的言论自由，而且也不会修改台湾（省）本地的任何信息。

這篇是拖了一段時間的參與心得，先從比較有官方色彩的開放街圖基金會的相關記錄與討論開始，再來比較個人的交流與觀察。

大會第三天在閉幕式前的 OSMF 時段，由具備理事身份的人座談。OSMF理事長談到一些花費是這麼說的，大家覺得努力募款增加捐款數字，但目前很多幫助來自業者服務捐贈，如CDN、Bing衛星圖、伺服器等，如果任何業者決定中止捐增，會導致 OSMF 有很嚴重的財務缺口。而圖客參與畫地圖才能一直維持地圖的活力，所以社群經營也是重要的挑戰。理事Otris提到，他們目前重點是讓硬體設備能支援未來的需求，很努力進行開發與硬體架構設備。

OSM Award Brandon 被提名，然後他們自己不知道，他開完笑說知道他被提名還可以拉一些票，再來是多位獲獎者不在現場，需要由人代領。

https://awards.openstreetmap.org/

HOT 主力的大會

這次以HOT Asia Pacific Map Guru身份參與State of the Map 2025大會，不只是講者的身份，或是地方社群組織者，還有HOT身份，有點汗顏台灣不是HOT AP優先區域，也不大需要靠OpenStreetMap去成為救災主力圖資。 ## 東亞與南亞社群的聯結 我再次遇到韓國社群的成員，先前在台灣時已經在COSCUP遇到他了，鼓勵南韓的Dong Hwang也可以參與HOT相關訓練課程，其內容都蠻實用的。 從日本社群的古橋大地桑聽到PLATEAU建築資料集的故事，原來背後推動人士瞭解社群，知道怎麼調和彼此關注之處，從而引路社群機制來共同編輯資料集。 與印度社群交流，他們也有類似台灣弄學校資料的整理，由於關注度因素得弄獨立的MediaWiki站，然後他們不同單位有不同代碼，不只需要弄一個代碼。

台灣經驗分享

這次演講題目細數台灣曾經做過的專案，談論將OpenStreetMap與Wikidata彼此連結的經驗。儘管我沒太講工具的部分，但有口頭講在維基媒體生態系的工具生態系較成熟，有運用在Wikidata上的自動表格工具Listeria，監控Wikidata上即時的項目，例如所有台灣的國中小、教會、廟宇、村里行政區之類。目前 OpenStreetMap 上面則沒有太好用的監控維護工具，所以得先在 Wikidata 上確定資料完整，再回過頭檢查 OpenStreetMap 的物件。 近期熟悉OpenRefine是相當好的工具，不過來不及在演講時敘述。OpenRefine是適合做維護工具，有一份相對穩定的有維護的清單，去比對在Wikidata上面是否資料為即時的。

SotM 2025我的講場是第二天一早，我這一軌下一個講場則是烏干達維基人分享自己怎麼做圖書館資料的繪製。他們狀況是並沒有政府維護的圖書館清單，所以得自己依靠社群去收集圖書館基本資訊，如照片、位置等。我的講場與他的講場差別在，有資料集可以用與否，蠻有意思的比較。

另外除了我之外，還有兩位來自台灣的參與者，Proton Maps 的創辦人Brandon 跟他搭同班一早的長榮航班飛來馬尼拉，不過他沒有議程，純來交流。積丹尼是當初破解台電變電箱外數字，被稱為電力座標，其實是 TWD67座標系，則是投稿一場，又有一場lightning talk。跟他聊原來他已經搬到北屯了，不在東勢山區了，聽說原由是他跟鄰居吵架導致他不能住他的農舍了。我還調侃Minh應該常需要檢視積丹尼對 OpenStreetMap、OSM-Carto 接近無理取鬧的討論提議，他是笑笑覺得還好。他現在是 OpenStreetMap Foundation 的工程師，應該也習慣非技術討論，偏向政治的議題討論狀況了。

積丹尼的講場圍繞地址相關議題，用程式方式分析菲律賓一帶地址標示狀況，來檢視其邏輯，他的lightning talk講題偏倡議，則在推廣 grid 的地址系統，認為是最棒的。其實積丹尼的講場應該也可以去投稿學術軌

密切交流

… See full entry