OpenStreetMap
I had a fantastic time at SOTM US. Thanks to all at OSM US for their work putting the event together.
I gave two presentations, one on MapRoulette and one on the new Meet Your Mappers tool. I posted annotated slides for the MapRoulette talk on my blog.
UPDATE: Overture has since addressed many of my concerns regarding the language on their website. See here for more.
Dear Overture Team and OpenStreetMap Community,
This diary entry is a follow-up to an in-person conversation I had with some of the Overture team at State of the Map U.S. To their credit, they were quick to admit to and apologize for some of these omissions and verbally committed to making appropriate changes. I am therefore posting this entry for the following reasons:
In my opinion, Overture does not take care to spell out the necessity of OpenStreetMap attribution on their Attribution and Licensing page. After an optional citation comes the following language:
The Overture Maps Foundation does not require text attribution or an OMF logo on maps, visualizations, and graphics created with our datasets. If you would like to credit Overture, we suggest:
© Overture Maps Foundation.
So far it seems pretty easy to use Overture data. We can attribute…but only if we want. Easy peasy! After that, the potential for additional attribution requirements is raised:
Some of the data sources we use in Overture datasets do require their own attribution, according to their licenses. For example, our Explore tool displays several Overture datasets that are made wholly or in part from OpenStreetMap data, so we added the following line of attribution to adhere to the requirements of the Open Database License:
© OpenStreetMap contributors, Overture Maps Foundation.
DIARI SAYA #AWAIT #WAITTT
Just reached 1000 edits, so thought it would be good to dump what I have learnt so far.
I started using OSM during the COVID 19 lockdown living in Hampshire, there were many walks available but the routes were not always clear on google maps. OSM was far better and I used it for information about walks before proceding. The level of detail was great and really useful.
Fast forward to 2023 and I decide to start contributing using StreetComplete and MapComplete. I drive an Electric vehicle and the information on charge points is so obscure I wanted to contribute. This led me down a rabbit hole of StreetComplete, filling in addresses, road surfaces, bus stop shelter. Anything and everything. I learnt the importance of information that would be useful to users.
Only in the last year, have I picked up mapping, this time using ID editor, chnaging tags was a little daunting but I slowly got there. I noticed some areas around me were missing house numbers. I learnt the importance of doing a survey on foot. There’s so much to learn from looking around IRL.
The last few weeks, I have been mapping out areas that had no buildings, only Residential Areas. A few thousand terraced houses later (feels like it) and quite a few places are on the map around Yarmouth (yeah I moved from Hampshire in this time!). Most imporatntly, check the alignment of background layers before starting a new edit! It is also useful to turn off layers not used, really makes things easier to see.
Latest update, I own a drone and can produce aerial images, very useful for areas not on Bing maps. This also gives me access to a 3D view of the area, very useful for double checking my survey notes!
Maybe I’ll do another one of these at 2000 edits?
Didn’t think would see a day(again) where I have to use tor with bridge as proxy AND a vpn for accessing internet including OSM and it’s wiki but here we are… Sighs 🤦🤦🤦
Those guys at government always can and will shock/surprise civilians to the death (yet again)
Never a dull moment!
다중다각형 어떻게 만들어요??? (Pls teach me how to make “type: polygon”)
Hi everyone. I recently started contributing to the map around my university’s campus, and I thought I should get in touch with the community a little. I’ve only labeled major buildings in the campus plus some road fixups, but I hope to continue contributing more to the map around here.
Oh yeah, this account is old, but I don’t even remember having it until I tried to sign up lol.
I typically write my notes in English when they can be resolved by anyone. Even residents from another country than Sweden.
Om anteckningarna pekar mot att en behöver kunna förstå svenska för att fixa ett problem så tenderar skriva jag på svenska istället.
韓国の百科事典・ナムウィキのオープンストリートマップの記事には以下のような記述があります。
【ネット右翼が独島（韓国名）の関連するすべての情報を消したこともあり、独島を日本が主張する行政区域である島根県沖ノ島に名前に変更する事例もあり、鬱陵島から独島へ行く航路の名前を「不正入国海路」に変更しながら独島関連の地物を日本語に変えるなど、島を水没させる編集もあった。 独島を竹島と表記して日本領土に編集する場合が多く起きるので、関心を持ってみるのも良い。 独島削除と竹島で作ったり消したりする問題は現在進行形だ。 独島の衛星写真はうまく出ていないので、すべて消してしまえばJOSMのような高度なツールでない限り、再編集するのが難しい点がある。 】
まあ、そうだろうなあと思い適当な地物をクリックしてみました。私は東アジア地域で地名の日本語表記を書くのに四苦八苦しているので、竹島は興味深い場所です。
いくつかのポイントは実効支配を行っている韓国側が定めたと考えられる日本語名称が書かれているのですが、肝心な『独島里』の日本語名称が削除されているではありませんか！
ちなみに、韓国での『里』は日本では小字に該当します。
削除した理由は『日本ではそう呼称されていないから』だそうです。しかも、政治的意図はない←？？？？？
この理論が罷り通るなら北方領土では同様な編集が行われていないのも疑問です。
実効支配を行っている国の呼称を削除するのは、日本人の私ですら甚だ理解できません。当該編集は私が修正しましたが、おそらく、今後もこのような編集が行われると推測されます。
日本の立場を表明することは重要ですが、【政治的意図のない編集】や【竹島は日本の領土】という編集をここで行って何になるというのでしょうか？
少し愚痴りたくなったので書かせて頂きました。
Spending countless hours terracing thousands of buildings yet didn’t even bother to correct the errors caused by it?
Hello OSM community,
My name is Nicole and I’m on the governance team at MapSwipe a humanitarian mobile phone app and web app where volunteers can contribute to geospatial data projects.
I presented a talk, “MapSwipe Today and Its Future in OSM” at State of the Map US 2025 in June in Boston, Massachusetts. The talk had two main purposes:
Let people know more about MapSwipe, its history, and what it can do with it today
Begin a discussion within the OSM community about what it might mean for MapSwipe to become its own OSM editor, especially if AI or machine learning models are involved.
You can view the talk on YouTube.
The MapSwipe community wants to ensure that if we are going to move forward with any ideas and planning around becoming an editor that has any AI in the mix, that we also make sure the OSM community is present in our discussions.
This diary post is to collect thoughts from the OSM community on this topic.
Some items we’d like to discuss with the OSM community are:
Looking forward to the discussion!
Nicolelaine
ใ
This week I’ve been mapping rural communities in Honduras, focusing on areas within the Tegucigalpa Health Region. My work has included adding paths, correcting road alignments, and identifying visible structures such as houses and community centers.
Today we at Unique Mappers did our weekly presentation were I made a presentation on Humanitarian Use of OpenStreetMap where i talked about OSM what it is why it is crucial in Humanitarian context how it provides critical data in poorly mapped or un mapped areas. I still talked about the basics( getting started with OSM), the intermediate OSM data use(Analysis and virtualization) and advanced used of OSM. I still talked about the tools and resources( software) used with OSM and example is the HOT tasking manager, QGIS [qgis.org], Umap and many other software, site, organisation using OpenStreetMap
Hi :) I am mapping Eritrea these days and found some objects I am not able to identify. Can you help me with your wisdom?
I suspect those are some living buildings, but I might be wrong.
As I write in my profile, I was really peeved off, that dozens of “Camino Apps” (apps used to track users along the Ways of St. James, the Caminos de Santiago) did ask their users for updates to opening hours or bed counts in albergues, but never contributed back to OSM what they’d discovered.
I launched a “test balloon” in 2023, renaming an accommodation to reflect its real name, and lo and behold, of the 23 apps I checked, 22 had suddenly also changed the name, meaning they used OSM data, but didn’t ever give back to the community.
So I changed it, wrote a Camino App that did contribute back. We don’t expect our users to have OSM accounts. Instead, we recruited a bunch of volunteers, who are served the changes, check them personally, and then contribute them back to OSM.
First step: fountain potability. Along the Caminos are thousands of fountains providing drinking water to the 500k pilgrims walking the Way every year. Spain is excellent, when it comes to drinking water quality, but sometimes fountains dry out, become undrinkable, or become drinkable again. Nothing sucks more than going 1000m out of your way to find out that fountain has been closed.
I’ll semi-manually start updating fountain “drinking_water=” tags over the next 30 days along the most famous route, the Camino Francés. Once that’s stable and enough volunteers have been trained and shown that they can do this without harming the dataset, we’ll expand to hostel data.
node.tags {
junction:cluster:radius: number[1..N]
}
Когда этот тэг применяется для объектов типа node, эта эта точка должна являться пересечением - junction. См статью про это.
Тэг указывает радиус окружности в которую может быть вписана функциональная зона для данного пересечения.
Это означает, что в данной зоне другие объекты (парковки, переходы, стоп-линии и так далее) могут отображаться или интерпретироваться
как-то иначе. В какой-то степени это понятие соотносится с понятием функциональная зона перекрестка, только в данном случае - простейшего пересечения.
Главной мотивацией введения данного тэга было обеспечить возможность группировки нод соседних пересечений в обобщающее понятие “Перекресток”. Для этого у нас есть несколько различный вариантов, как это может быть сделано:
type:intersection, members[node1,...,nodeN, way1,..., wayM]
junction:cluster = name or id
junction:cluster = 5
Плюсы и минусы первых двух подходов очевидны. Опять relation, ссылочная целостность, генерация тэга. Все эти способы решают одну задачу - управляемая кластеризация нод пересечений в некую более сложную структуру данных.
Рассмотрим 3 способ.
node.tags {
junction:radius: number[1..N]
}
way.tags {
junction:radius:lanes: number[1..N]|number[1..N]|...
junction:radius:lanes(:forward|backward)(:start|end) number[1..N]|number[1..N]|...
}
Когда этот тэг применяется для объектов типа node, эта эта точка должна являться пересечением.
Тэг указывает радиус окружности в которую может быть вписана зона конфликта путей для данного пересечения
junction:radius - радиус окружности соотносящийся с зоной конфликта, в котором участвуют
транспортные средства
Когда этот тэг применяется дл объекта way, то обязательно применять суффикс lanes. Значения переопределяют радиус конфликтной зоны пересечения индивидуально для каждой полосы, если заданы.
Рассмотрим несколько примеров. На рисунках ниже голубая окружность в правой части рисунка и есть визуализация значения данного тэга.
Пример 1
junction:radius = 4
Зона конфликта не описывается окружностью указанного радиуса(ширина и количество полос), значение задано неверно.
node.tags {
junction:shape: rectangle|oblique|staggered
}
Этот тэг применяется только для объектов типа node и эта точка должна являться пересечением двух или 4х way.
Для самых распространенных пересечений 2х дорог или одной дороги пешеходного перехода.
Он отражает форму пересечения и отношения между воображаемыми или реальными стоп линиями конфликтующих путей в этом пересечении.
Две дороги могут пересекаться под совершенно разными углами, см примеры ниже, но углы пересечения иногда не отражает, как автомобили или пешеходы или другие транспортные средства, будут останавливаться перед этим пересечением. Форму задает проект организации дорожного движения и фантазия проектировщика.
rectangle - стоп линии конфликтующих путей находятся под углом ~ 90 градусов друг относительно друга.
Точки стоп линий для каждой полосы lanes откладываются по перпендикуляру от осевой.
Стоп линия одна - общая линия для всех lanes (рисунки 1,4,5).
oblique - стоп линии конфликтующих путей находятся под углом меньше чем 90 градусов (~ 30 - 70).
Точки стоп линий для каждой полосы lanes откладываются по параллельно пути, который конфликтует с данным.
Стоп линия одна - общая линия для всех lanes (рисунки 2,4,5).
staggered - некое промежуточной состояние между rectangle и oblique, угол пересечения может быть любой, главное отличие
в том, что для каждой lane своя отдельная стоп линия на разных расстояниях от node (рисунок 3,5).
Per ogni regione vengono fornite:
una query overpass che visualizza i comuni d’Italia (livello amministrativo 8) per cui non è presente in OSM un node/way/relation con amenity=townhall ma per cui è noto un palazzo comunale in wikidata
una query wikidata che elenca ordinati per comune i suddetti palazzi comunali
una query overpass che visualizza i comuni d’Italia (livello amministrativo 8) per cui non è presente in OSM un node/way/relation con amenity=townhall di cui neppure in wikidata è noto un palazzo comunale
Nota1: per efficienza le query lavorano su un sottoinsieme di comuni di cui era stata accertata al 29/8/2025 (a) la mancanza del municipio in OSM e (b) la presenza/assenza di palazzi municipali in Wikidata. Nel caso il municipio sia stato aggiunto in OSM dopo suddetta data le mappa generate dalle query overpass mostrano sia il territorio comunale che il municipio. Nel caso il palazzo municipale sia stato aggiunto dopo suddetta data, la query wikidata non lo estrae comunque.
Nota2: le query overpass aprono una nuova pagina browser in autorun ed impiegano fino a 30 secondi a completarsi nei casi più complessi; ottenuto il risultato i dati dei comuni sono consultabili cliccando su ciascuna delle aree evidenziate in giallo
Nota3: le query wikidata aprono una nuova pagina browser senza autorun per cui serve premere il bottone blu di avvio; ottenuto il risultato, le informazioni sul palazzo comunale sono consultabili con il link nella colonna “bene”
01 - Piemonte
* municipio “OSM no Wikidata si”: overpass, wikidata - 41 comuni
* municipio “OSM no Wikidata no”: 0 comuni
02 - Valle d’Aosta: nessuna eccezione
03 - Lombardia: nessuna eccezione
04 - Trentino-Alto Adige/Südtirol: nessuna eccezione
* Nota: il comune di Kuens - Caines ha i propri uffici comunali sul territorio del confinante comune di Riffian - Rifiano.
05 - Veneto: nessuna eccezione
06 - Friuli Venezia Giulia: nessuna eccezione
07 - Liguria: nessuna eccezione