OpenStreetMap Blogs

OpenStreetMap User's Diaries: Actualización de vías y poblaciones.

2026-07-07T18:01:22+00:00

Martes 7 de Julio de 2026.

Se realizo:

Se agrega etiqueta de Condominio Río Lircay, Barrio Los Pinares IV, se separa Los Pinares II y III.
Se agrega nombres de calles en Los Pinares IV; Huircaleo, Cuminao, Huenchulaf, Huenupan, Calfumil, Kuden, Curiman, Namuncura, Felipe Camiroaga y Antilaf.
Se corrige tramo de vía que corresponde a Av. Kennedy y no a Av. España. Desde República hacia el norte corresponde a Kennedy y desde República hacia el sur corresponde a España.
Se agrega nombres de calles en Los Pinares III; Calfupan, Caulín, Huenchelu, Eyetun, Kopahue, Inacayal, Llacantu, Felipe Camiroaga, Coyanco, Yafu, Malal.
Se agrega nombres de calles en Los Pinares II; Lonco, Cuyen, Ela, Piren, Callen, Peuma.

OpenStreetMap User's Diaries: Како обележити да нека продавница алата продаје и Stihl производe?

2026-07-07T14:28:59+00:00

Другар Claude и ја смо мало истраживали. Нашли смо дискусију [1] која је иницирана са [2]. Након тога вероватно је измењен и вики [3]. Делује да је таг почео да се користи [4].

Неки мој закључак је да brand:sales=brand1;brand2 има смисла додати. Видећемо шта заједница мисли о тагу у наставку, таг додат на Оков са идејом мапирања STIHL дилера [5]

[1] https://community.openstreetmap.org/t/usage-of-brand-for-lists-of-brands-sold/132493
[2] https://community.openstreetmap.org/t/tomtom-maproulette-challenges-july-2025/132487
[3] https://wiki.openstreetmap.org/wiki/Key:brand#Brand_of_feature_vs_brands_on_sale_/_service_/_repair_/_rental
[4] https://taginfo.openstreetmap.org/keys/brand%3Asales#overview
[5] https://www.openstreetmap.org/way/171563659

OpenStreetMap User's Diaries: mongr20.com — a free GR20 (Corsica) trail planner built entirely on OSM data

2026-07-07T10:22:08+00:00

Last year I hiked the GR20 across Corsica, and afterwards I built a small non-commercial website around it: https://mongr20.com/en/

Everything is computed from the OpenStreetMap GR20 relation: the site states 182.4 km and +11,220 m of elevation gain, split into the 16 official stages. From that single OSM trace I generated:

free GPX downloads for all 16 stages, in both directions (ODbL-credited): https://mongr20.com/en/gr20-gpx-tracks
an interactive stage planner (pick 10, 12 or 16 days — it computes distance, elevation, water and food needs per day): https://mongr20.com/en/gr20-planner
a refuge directory with positions and practical info.

The map tiles are OpenTopoMap/OSM. No ads, no tracking, no paywall — it is a thank-you project as much as anything. So: thank you to every mapper who has ever touched that red-and-white line across Corsica. The data quality on the GR20 relation is genuinely excellent, and this site simply would not exist without it.

If any mappers here have hiked the GR20 and spot something off (a refuge position, a water source), I would love to hear about it.

OpenStreetMap User's Diaries: قانون «همراهی حروف و عدد»

2026-07-07T06:59:26+00:00

همراهی حروف و عدد به طور مثال «بنفشه ۱»، «لاله ۵»، «سروستان ۹» درست است ولی… این همراهی به طور مثال «خیری ۱۲۹»، «کریمیان ۲۳»، «قریب ۲۱»، «باشتنی ۷»، «شادالویی ۱۳۱»، درست نیست. چون اگر «alt_name» و «old_name» و «loc_name» نداریم؟ برای همین درست شده. یا نباید نام قدیمی را درون پرانتز نام جدید گذاشت. مگر در معبر خارجی این چیزها وجود دارد؟

OpenStreetMap User's Diaries: Second Pass Done!

2026-07-07T02:55:07+00:00

Just finished a second pass of my hometown. Redid a lot of my shoddier early mapping and reviewed every TIGER import street. Now working on TIGER review outside of the city and some wetlands mapping for the time being.

OpenStreetMap User's Diaries: Deriving `recycling:*` keys from colour of recycling container. Part 2

2026-07-06T22:12:36+00:00

Last September I wrote about a concept where instead of hand-listing 15–30 recycling:* tags on every packaging container, the user could just pick the container’s colour and let the editor auto-add the right tags. Well, now the concept has become a working prototype.

Estonia’s container colours try to follow the Danish standard: paper blue, glass green, metal/plastic packaging yellow. Other countries and regions use different colours, but across EU paper, glass and packaging have surprisingly consistent colouring.

Source: European Commission, “Harmonising waste-sorting labels across the EU” (2023).

The closest fit in the iD schema (which Every Door uses) is semiCombo and manyCombo, but both are too limited: each is designed so a single interaction affects only one tag. semiCombo maps multiple values onto one tag (e.g. sport=soccer;tennis), and manyCombo toggles several keys that share a common value (e.g. foot=yes;bicycle=yes). On top of that, I wanted to support multiple colour values on a single node, for the case where a whole group of containers is mapped as single node.

The problem always seemed solvable in theory, but probably only in some inconvenient way, because of limitations the editors themselves impose. I thought of it as similar to how crossing tagging works in iD. iD has several crossing presets with different priorities, and somehow the editor can suggest changes from multiple presets to the same element at once. However mobile editors don’t allow single element draw fields from multiple presets. Using sub-presets also doesn’t scale globally as we’d then need N+1 presets for every region with unique container colouring rules where N is number of colour schemas in region. Then in April I stumbled on Mateusz’s issue on iD’s schema-builder, where he states that the current iD schema doesn’t support dropdowns that alter multiple tags.

This week I finally got fed up with a different Every Door bug. I needed the editor to flag benches missing an armrest without tapping through every bench I walk past. The ED docs claim this works, but I’d been banging my head against it for nearly a year. AI assured the fix would be a one-liner. Twelve lines of code and twelve hours of debugging later, it was fixed and since I’d somehow got app compiling and running on my phone, decided to tackle the recycling containers next.

So I invented a new field type, bundleCombo, where a single option can set multiple tags at once. It still has one limitation that might become a problem later - all options must share at least one common key. Since introducing a new field type into the iD schema could have wide-reaching consequences, I won’t file a formal pull request for this, but if anyone’s interested, the code is at github.

Here’s the actual Every Door plugin I ended up with (pasted here because the plugin isn’t on GitHub):

id: recycling-ee
name: "EE Recycling (bundleCombo)"
version: 0.1
description: |
  Test plugin for the fork's bundleCombo field. A single recycling-container
  preset where tapping container-colour options stamps the matching
  recycling:* tags automatically.
  NB! This plugin relies on experimental custom field in order to be usable.
icon: U+267B 

presets:
  amenity/recycling:
    name: "Packaging container"
    icon: U+267B  # Unicode for ♻
    terms: [pakend, pakendikonteiner, recycling container, konteiner]
    tags:
      amenity: recycling
    fields:
      - "@amenity/recycling"
      - ee_recycling
    moreFields:
      - "@amenity/recycling"
 
fields:
  ee_recycling:
    label: "Containers present"
    type: bundleCombo
    key: colour
    options:
      - value: yellow
        label: "🟨 Mixed"
        tags:
          "recycling:plastic": "yes"
          "recycling:plastic_packaging": "yes"
          "recycling:plastic_bottles": "yes"
          "recycling:cans": "yes"
          "recycling:metal_packaging": "yes"
          "recycling:beverage_cartons": "yes"
          "recycling:cartons": "yes"
          "recycling:plastic_bags": "yes"
      - value: green
        label: "🟩 Glass"
        tags:
          "recycling:glass_bottles": "yes"
          "recycling:glass_jars": "yes"
      - value: blue
        label: "🟦 Paper"
        tags:
          "recycling:paper": "yes"
          "recycling:cardboard": "yes"
          "recycling:paper_packaging": "yes"
          "recycling:newspaper": "yes"
          "recycling:magazines": "yes"
      - value: brown
        label: "🟫 Bio"
        tags:
          "recycling:organic": "yes"
          "recycling:green_waste": "yes"
      - value: white
        label: "⬜ Clothes"
        tags:
          "recycling:clothes": "yes"
          "recycling:textiles": "yes"
          "recycling:shoes": "yes"

The tags were picked from the most popular recycling:* keys on Taginfo. Node 7147202892 is one of the first containers edited this way. There are two potential drawbacks worth addressing one day. Labels with coloured emoji along with waste type makes the options list too long and even picking “🟦 Paper” chip via ED’s UI was bit tedious. I could use icons as workaround one day.
Second trouble involves clothes container. Officially recyclable clothes are supposed to be collected in light-green container, my local container is white and I assumed rest of city has also white containers. However i encountered blue clothes container today. Luckily it was mapped separately from others so i was able to simply change colour manually.

If you want to see how it’s built, it’s essentially two files: field definition and function call in UI builder.

OpenStreetMap User's Diaries: Страна Оз.

2026-07-06T14:45:32+00:00

Сколько копий сломано о названиях озёр, а от «Дикое оз.» так и не избавились.

nwr[natural=water]["name"~"оз\\."]

Поиск и Замена… и получаем «озероИлимнир» :\

Что ж, запасаемся чаем и небольшими кусками через Level0 исправляем:

«оз. Белое» на «Белое озеро»
«оз. Пятницкие» на «Пятницкие озёра»
«оз.Бол.Захарьевское» на «Большое Захаревское озеро»
«Бол.Панэчаты оз.» на ээээ…. пожалуй на «Бол.Панэчаты озеро»

По пути обнаруживаем что исправлять нужно и в name:ru. А из name:en вычищать «Oz. Jasnoje». Учесть что по-белоруски должно быть «возера». А в украинских названиях оставить популярное написание с заглавной «О». Заглавные….

nwr[natural=water]["name"~"оз\\.", i]

Теперь всё? Ха, а теперь nwr[natural=water]["name"~"о\\."]

Да что мелочиться:

{{geocodeArea::Russia}}->.a;
nwr[natural=water]["name"~"\\."](area.a);

И получаем:

Пож.
вдхр.
вдх.
п.
пр.
пр.
прот.
ер.
Южн.
юж.
Сев.
Мал.
М.
Б.
Д.
с.
Боль.
Бол.
бол.
р.
руч.
раз.
рз.
зал.
ст.
р.
ок.
им.
Верхн.
Верх.
Н.
Лев.
Тех.
Вос.
сол.
овр.
пор.
Академ.
бывш.
заброш.
недейств.
рыб.

‿( ́ ̵ _- ` )‿

OpenStreetMap User's Diaries: Clearance v0.5

2026-07-06T14:42:00+00:00

Clearance: Quality filter for OpenStreetMap replication

Clearance is a free software tool for controlling the quality of OpenStreetMap replication diffs. It tracks thematic and territorial edits to OSM and keeps replication extracts (extracts, diffs, and a local Overpass API) up to date.

Instead of trusting every incoming change, Clearance evaluates edits against configurable quality rules based on OSM tags, metadata, geometry and changeset properties. Compliant changes, at object level, pass through automatically. Suspect ones are retained rather than applied. Retained data must either be fixed directly in OSM or approved manually. All data contributions are made only in OSM itself. Reviewing and fixing suspect changes is done collaboratively by the team responsible for a given theme and region.

Because it uses standard OpenStreetMap ecosystem formats for both input and output, Clearance integrates seamlessly into existing OSM data reusers workflows, while providing greater confidence in the consumed data. It is used to filter and review changes on thematic contributions such as tourism POIs across France, or road and emergency access points in Spain.

How Clearance addresses this problem

Clearance imports an initial OSM PBF extract, then checks every incoming change against configurable quality rules. Changes that meet the rules are applied automatically to the replicated database, while suspect changes are held back. Quarantined changes must then be fixed directly in OSM or manually approved by reviewers. After each update, previously held objects are re-evaluated, so a change is released automatically once it no longer fails the rules.

Instead of validating each object individually, Clearance uses the concept of LoCha: a spatially grouped set of related edits. It validates the whole group together, so that quality checks account for local coherence. E.g, a new building and the driveway added with it are reviewed as one unit, not separately, even if added by different contributors at different points in time.

Main configurable validation filters: - Large geometry change - Monitored tag changes - Monitored tag object deletion - Changes by blacklisted OSM user - Retaining hot changes for a delay

Major changes introduced by 0.5 version

LoCha Engine Redesign: the engine now uses topologically connected changed objects as a finer-grained level, ensuring the coherence of accepted change data. LoCha then uses clustering by distance to other objects to ensure semantic coherence with nearby changes. LoChas are then recursively split to an acceptable size before conflation between the old and new versions of OSM data.

The core of the semantic conflation of before/after OSM changes has been moved to an external library (https://github.com/teritorio/openstreetmap-logical-history), which has its own online tool (start by picking an example): https://teritorio.github.io/openstreetmap-logical-history-component/ .

A new “Delayed” validator was added. It holds back hot changes from synchronization and accepts cold changes automatically, helping to retain disputed or in-progress edits.

An “Invalid Geometry” validator was also added, to catch self-crossing ways or polygons and other geometrical issues.

Database performance was improved, and self-checks for data integrity were added. Because Clearance’s data workflow is not simple, tools and database checks beyond foreign keys were implemented to ensure no data is lost or becomes invalid.

An Atom feed, with filtering capabilities, was added to ease the work of data curators.

This version was partly funded by NGI Zero Core, from the NLnet Foundation.

Still with the support of the NLnet Foundation, the next version will focus on implementing related-object validation: - Duplicate object: avoid introducing duplicate objects into the data. - Network topological changes: avoid breaking network continuity or creating overconnections.

Demo and Source code

Clearance on OSM Wiki osm.wiki/Clearance
Source code & Docker images https://github.com/teritorio/clearance/
Public demo instance : https://app.clearance.teritorio.xyz/ (you can ask us to add a new demo area)
Talk about Clearance at the next SotM: https://2026.stateofthemap.org/sessions/VGGXRJ/

OpenStreetMap User's Diaries: Anleitung für Indoor Mapping

2026-07-06T14:19:56+00:00

Hallo zusammen,

in den letzten Wochen habe ich mich mit dem Thema Indoor Mapping vertraut gemacht. Da ich dabei auf einige Probleme gestoßen bin, habe ich nun eine Anleitung geschrieben, die den Einstieg ins Indoor-Mapping erleichtern soll. Bitte beachtet, dass meine Erfahrung mit OpenStreetMap noch sehr begrenzt ist. Falls ich also grobe Fehler in der Anleitung gemacht oder wichtige Teile vergessen habe, könnt ihr mich gerne benachrichtigen.

Viel Spaß mit der Anleitung für Indoor-Mapping mit OpenStreetMap

OpenStreetMap User's Diaries: Modificación Villa Galilea, Etapas G2 y G1

2026-07-06T13:44:30+00:00

Viernes 3 de Julio de 2026.

Se realizo:

Modificación de ejes de calles en Villa Galilea G2 y G1 en base al mapa de ESRI.
Se agrego etiqueta de población por ambas etapas.
Se agrego nombre de calle; Santa Clara de Asis.

OpenStreetMap User's Diaries: ای کسانی که در ویرایش کردن تنها واگردانی بلدند

2026-07-06T11:12:27+00:00

معبر یا گره یا ساختمان یا محیطی که نام روز باشد نباید به نام قبلی واگردانی شود. غیر قابل واگردانی است. همین معبر خشایار کریمیان(بیست و سوم) که یک کاربر، به نام قبلی برگرداند با وجود اینکه نام بیست و سوم در یک برچسب دیگر یاد شده بود. هم این ویرایشگر و هم ویرایشگرهای دیگر توجه فرمایند که هر تغییر نام یا کدگذاری که شهرداری می‌کند را مورد توجه قرار بگیرند و نگذارند به گردن گیتاصالح ویراست (من) بیفتد. اطلاعات شهرداری‌ها، دهیاری‌ها و وزارت راه و شهرسازی، قابل واگردانی نیستند.

OpenStreetMap User's Diaries: 关于中国区域地图语言显示的问题

2026-07-06T07:41:07+00:00

大家好！我目前正在开发一个面向韩国用户的地图项目，计划使用 OSM / Mapbox 的矢量切片。

目前遇到了一个关于中国区域底图语言显示的痛点，希望能得到社区大佬们的建议或帮助：

1. 遇到的问题（Current Issue）

当我在地图样式中将语言全局切换为韩文（ko）时，中国区域的省份和主要城市能够正常显示为韩文（例如：베이징、상하이）。但是，当把地图放大到街道和底层 POI（如具体的道路名称、店铺名称）时，由于缺乏对应的 name:ko 标签，地图会直接回退显示为中文（name:zh）。

2. 我的目标（Goal）

我想实现中国境内（至少是主要城市如北京、上海、广州等）的底层街道和主要地理要素能够尽可能全面地显示为韩文，避免出现大量的中文夹杂，从而提升韩国用户的阅读体验。

3. 想向大家请教与求助（Questions）

现有资源：OSM 社区或第三方目前有没有已经整理好的、针对中国区域地名的“中-韩”高精度地图语料库/映射表？
自动化标签填充：如果我想批量为中国主要城市的街道和 POI 补全 name:ko 标签，社区是否有推荐的自动化处理工具（如通过波形/拼音转写韩文的脚本）？或者是否有成熟的机翻对齐经验可以分享？
渲染方案：如果不直接修改 OSM 数据库，在前端渲染（如 Mapbox Studio / MapLibre）时，有没有优秀的开源表达式或插件，能实现“实时将 name:zh 转换为韩语发音/译名”的 Fallback 机制？

如果大家有相关的项目经验、开源数据集、或者处理过类似的涉外多语言地图需求，非常渴望得到您的指点！非常感谢！

OpenStreetMap User's Diaries: 随着时间去旅行吧

2026-07-06T02:42:04+00:00

很高兴来到这里，一个热爱技术的开发者，你可以在’qaiu博客’找到我…

OpenStreetMap User's Diaries: Return For Mapping

2026-07-05T16:41:28+00:00

In July 2026, I decided to return to OpenStreetMap after nearly four years. This project is more than just mapping for me—it is a personal journey to build a detailed digital representation of my hometown, Taiping. My current focus is the Heritage Zone, where I hope to refine every building footprint and individual block with the best accuracy possible. If you’re a fellow mapper or a Taiping resident, your contributions are always appreciated. Feel free to add shop lot numbers, business names, amenities, or any other local knowledge that helps make the map more complete and useful for everyone.

weeklyOSM: weeklyOSM 832

2026-07-05T14:48:46+00:00

25/06/2026-01/07/2026

[1] Interactive Globe with the locations of all 16 official FIFA World Cup 2026 host stadiums and the 48 participating nations | © Théo Bucaille aka theobcl18 | map data © by OpenStreetMap Contributors.

Mapping

The proposal for railway=balise, fixed transponders placed on or between rails that communicate with trains to provide positioning data and transmit operational information, is open for voting from 27 June 2026 to 10 July 2026.

Mapping campaigns

After the two strong earthquakes that struck northern Venezuela on Wednesday 24 June 2026, HOT has added collaborative mapping projects to their tasking manager to collect and share critical geospatial data to support emergency response efforts. Ongoing activities also include acquiring pre- and post-earthquake satellite imagery, coordinating crowdsourced remote mapping, and conducting field mapping campaigns to document damaged structures with their locations, photographs, and videos.

Community

[1] theobcl18 has developed ‘Coupe du Monde 2026 Globe 3D‘, an interactive globe showcasing the locations of all 16 official FIFA World Cup 2026 host stadiums and the 48 participating nations. The globe also provides detailed information on each team and venue, including the latest match results and stadium capacities.
Pascal Neis has explored if various language models could be helpful for analysing OSM Notes for potentially problematic language.
Franjo Lukežić continued writing up their next field surveying heuristic. It details how to survey highway=steps. Further, they are working on a cookbook, which contains the existing heuristics, including the one we reported earlier.
Binyam Dele presented Ambalay Maps at the recent State of the Map Africa 2026 conference.
Mateusz Konieczny had asked if there are any problems with waterway=stream_end, with a plan to support this tag in the iD presets. That plan has been cancelled based on feedback.
Christoph Hormann discussed the somewhat peculiar situation of mapping populated places in OpenStreetMap.
Raquel Dezidério Souto shared, on LinkedIn and Mastodon, the video of her presentation at the State of the Map Africa 2026, titled ‘weeklyOSM-stats: Analysis of the weeklyOSM profile over the last ten years with PostgreSQL’. This presentation aimed to showcase the content profile of weeklyOSM to the event’s audience. The author is delighted that this presentation has finally taken place, as last year’s African event was cancelled for security reasons, following the sudden outbreak of a conflict.
Geofabrik has added a turn restrictions view to their OSM Inspector, showing both valid and broken turn restrictions.
Killkenny shared a detailed account of how to collect and verify open sources for mapping small settlements. Using Bukachivtsi and nearby protected natural sites as an example, he showed how to combine data from the cadastre, community websites, Wikimedia Commons, the Wayback Machine, Wikipedia, and other sources, while keeping licensing clearly in mind.
Silvi715 reported , in her OSM user diary, about the flood prevention mapping activity carried out in Villa Moises, Venado Tuerto, Argentina. In the end a uMap was created.
9_tab wrote about the ‘Supermarchés à Genève de A à Z (or rather from A to M)’ in their OSM user diary. The survey around Geneva noted good coverage of supermarkets and inconsistencies in the default brand definitions (NSI) for Switzerland.
To55 has asked how to map flat addresses in Romania.
Wikidata Taiwan tooted about the OpenStreetMap x Wikidata Monthly Meetup, which will be held on Monday 13 July, on Chongqing South Road (Taipei, Zhongzheng). You can view the list of events and the WikiProject Taiwan community’s page .

OpenStreetMap Foundation

The State of the Map Working Group has opened the call for posters at SotM 2026, inviting original, openly licensed OSM-related posters in A0 format. Submissions are due by 31 July 2026.

Local chapter news

Christoph Hormann has decided to let his FOSSGIS membership expire at the end of the year after the association’s virtual general meeting approved an increase in dues.

Events

Hiroyuki Horin at Sakura Internet, as an infrastructure sponsor of OpenStreetMap Foundation Japan, has published a detailed report ► on the Mappers Summit 2026, held on 1 February 2026 at Sakura Internet’s Bloom Camp. Yui Kitamura, who presented at the event, has shared ► her presentation materials. Smellman reported ► on a tile server implementation, and alt9800 also gave a presentation themed around taking screenshots. Yuiseki reported that they have developed a CLI utility for AI coding agents capable of calling self-hosted Nominatim API, TagInfo API, Overpass API, and Valhalla API.

Education

IVIDES DATA has hosted ► the fourth session of their 2026 OSM Workshop Series ► with a demonstration on using the KoboToolbox to create and implement web forms with geolocation, which work in any web browser and that are device independent. The training organisers note that those who complete the workshop series within the stipulated period (by 17 July 2026) will be entitled to a free mentoring session on participatory (or collaborative) mapping projects.

OSM research

HeiGIT showed how openrouteservice can be combined with OpenStreetMap road data and emission model data from the German Federal Agency for Cartography and Geodesy to visualise CO₂ and NO₂ emissions along route segments.

Maps

The ‘Versatiles Colorful’ layer on OpenStreetMap.org has been replaced with the SVWD03 style developed by Andy Townsend, which is based on the Shortbread open vector tile schema, and offers fast updates.
Francis Miranda has created an interactive web map, built using OSM, Python and Streamlit, which shows the spatial distribution of the ISMIF index, which represents schools’ vulnerability to flooding events. The index was applied to schools in Rio de Janeiro (Brazil). The code is available on GitHub.
François Andreaux posted ► , on LinkedIn, about the THT, a web map that shows information on French energy resources and infrastructure. The application lets you click on a plot of land to quickly see the distance to the nearest Réseau de Transport d’Électricité grid and source substations. The web map includes a basemap with OpenStreetMap data.

OSM in action

MapFuel.ru and GdeBENZ.ru are crowdsourced platforms that collect user reports on fuel availability at gas stations across Russia.

Open Data

Grant Slater tooted that he has updated the aerial.openstreetmap.org.za website with the latest aerial imagery from the Directorate-General of National Geospatial Information. He has made significant improvements to the website’s performance and the update workflow. The images are now available in iD and JOSM and have a resolution of 25 cm, with excellent positional accuracy.

Software

The new Trufi App V5 for informal transport in Cochabamba, Bolivia can download OSM data for offline use (because not everyone can afford to be constantly online).
Korben reported that Yllan has just released OS9Map, an application that displays OpenStreetMap directly on Mac OS 9.
Pierre Dandumont published ►, on MacGeneration, ‘OS9Map: OpenStreetMap maps for Power Macintosh computers from the last century’, an article dedicated to OS9Map, a Mastodon client for MacOS 9 (not OS X Mavericks 10.9). The article was highlighted on Mastodon.
Tina and Eugene introduced OsmAnd’s Nautical Map View, a feature designed for planning a trip on the water, practice aquatic sports and find the POIs related to coastal areas. The tool provides depth data, seabed information, beacons, navigation lights, buoys, and fairway details.
The OSRM Project announced changes to its build environment, upgrading to a more modern platform. Its Linux baseline is now Debian 13 and Ubuntu 26.04 LTS. Minimum compiler support has been raised to Clang 18 and GCC 14. Windows builds now use Visual Studio 2025.
Steve Vigneau has overhauled trailmaps.app, a web map that combines trail signage and official trail maps with OpenStreetMap data. Rather than maintaining individual maps, the redesigned platform is powered by a map generation system that automatically integrates data from OpenStreetMap and other freely available sources to produce static, cacheable map content that remains accessible even when mobile connectivity is unavailable.

Programming

Timothée Giraud tooted about his new cheat sheet guide on how to use OpenStreetMap data and related tools with R for geocoding, routing, downloading base maps and datasets.

Releases

The Freemap Europe tooted about a big update of Freemap.eu for outdoor folks and anyone with map files. You can visit ► the page of the project’s foundation. The files are available on GitHub.

OSM in the media

clubic reported ► that IGN has inaugurated the cartes.gouv.fr maps website. They also reported about the collaboration by IGN with OSM France and the integration of Panoramax street views (we reported earlier). Gregori Pujol published an article about this launch, highlighting the advantages of using it over Google Maps, on Journal du Geek .

Other “geo” things

The Real Sociedad Geográfica (Royal Geographical Society of Spain) reported ► on the launch of the new book El Atlas rojo: los mapas soviéticos del estrecho de Gibraltar (The Red Atlas: Soviet Maps of the Strait of Gibraltar) by Agustín T de Villar Iglesias. This work examined the Soviet Union’s vast, secret mapping project during the Cold War, focusing on Andalusia and Gibraltar. In addition to astonishingly precise city maps, the maps contained Cyrillic transcriptions, colour-coding for strategic sites and detailed military-geographical reports (Spravka) on the reverse side. The book and supplementary documentation are available to download free of charge as PDF files from the RSG website.
clubic reported ► on HyLight, the 12 m, 2 kg zero emission French blimp drone that replaces helicopters to inspect hundred of kilometres of infrastructure per day. The Lidar technology allows the capture of crucial information about infrastructure such as railways and power lines.

Upcoming Events

Where	Venue	What	When
		MapCup Asia Pacific 2026	2026-07-01 – 2026-07-31
Bogotá	Universidad Nacional de Colombia	State of the Map Colombia (SotMCol) 2026	2026-07-03 – 2026-07-04
Braunschweig	Stratum0 Hackspace	Braunschweiger OSM-Treffen Mappingtour: Zusammen Braunschweig mappen	2026-07-04
	Pinjarra Railway Station	Australind Mapping Day Trip to Pinjarra	2026-07-05
Greater London	University College London	London Data Week: Mapping festival with Missing Maps Mapathon	2026-07-07
Salzburg	Bewohnerservice Elisabeth-Vorstadt	OSM-Treffpunkt	2026-07-07
Bern	Restaurant Yaadein	OSM-Znacht in Bern	2026-07-07
		Missing Maps London Mapathon (with Training) Beginner Friendly (Online) [eng]	2026-07-07
Groningen	Groningen	FOSS4GNL	2026-07-08 – 2026-07-09
Trento	Università di Trento – Facoltà di Sociologia	FOSS4G IT & OSMit 2026	2026-07-09 – 2026-07-11
Berlin	KGA Johannisberg, Parzelle III/23b	217. OSM-Stammtisch Berlin-Brandenburg	2026-07-09
Zürich	Bitwäscherei Zürich	189. OSM-Stammtisch Zürich	2026-07-09
Berlin	HTW Berlin	Indoor OSM Workshop 2026	2026-07-11 – 2026-07-12
नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2026-07-11
Delhi	Chaayos, Paschim Vihar West, Delhi	OSM Delhi Mapping Party No.30 (West Zone)	2026-07-12
		OSM Chennai Mapping Party – Tambaram Market	2026-07-12
臺北市	MozSpace Taipei	OpenStreetMap x Wikidata Taipei #90	2026-07-13
München	Echardinger Einkehr	Münchner OSM-Treffen	2026-07-14
Hamburg	Voraussichtlich: “Variable”, Karolinenstraße 23	Hamburger Mappertreffen	2026-07-14
	temporärhaus	OSM-Stammtisch Ulm/Neu-Ulm	2026-07-14
Tours	Étape 84	Tours : Rencontre locale	2026-07-15
		Online Mapathon von ÄRZTE OHNE GRENZEN	2026-07-15

Note:
If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by PierZen, Raquel IVIDES DATA, Strubbl, Andrew Davidson, barefootstache, derFred, izen57, s8321414.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

OpenStreetMap User's Diaries: Mars hill Indiana #findTylerWAGAMAN

2026-07-05T12:16:05+00:00

We are looking for Tyler his last flick cam hit was in mars hill Indiana we have a Facebook group I’m sure if you look up his name on Facebook you can find it his brothers name is Brian dads name is Tim same last name flick cam had him in the area in a early 2000’s black f150 on 6/15/2026 in mars hill tag is TK9450xp out of Indiana any help is welcomed and appreciated there is a 7k reward for any information leading to finding him

osm2pgsql: Release 2.3.1

2026-07-04T22:00:00+00:00

This is a bugfix release which fixes a segfault that may be encountered when using the new diff expire on tables with multiple expire outputs.

It also fixes installation of man pages (thanks @sebastic).

OpenStreetMap User's Diaries: Контакт (не игра)

2026-07-05T10:43:55+00:00

Теперь (предыдущая серия) начнём с простого, с http://:

nwr["contact:vk"~"^http://vk\\.com"]

Вспоминаем про .ru

nwr["contact:vk"~"^http://vk\\.(com|ru)"]

И про vkontakte:

nwr["contact:vk"~"vkontakte", i];

Вообще vk.ru пока слишком молодой, поэтому его стоит заменить на привычный vk.com:

nwr["contact:vk"~"vk\\.ru/"]

Казалось бы, вряд ли в contact:vk будет другой домен с таким же окончанием. Но в предыдщей серии был обнаружен website = prostotabak@vk.com, так что пора смотреть внимательнее.

В contact:vk ожидается либо URL, либо никнейм. Никнеймы проверить без запросов к ВК не получится, но вычистим URLы. С https://vk.com же начинаться должны?

nwr["contact:vk"~"[^/]vk\\.com", i];

И обнаруживаем m.vk.com, new.vk.com, www.vk.com. Ну тогда и доменные зоны тоже проверим:

nwr["contact:vk"~"vk\\.", i]->.a;
nwr["contact:vk"~"vk\\.(com|ru|link)", i]->.skip;
(.a; - .skip;);

Хорошо, а теперь найдём не вкшные ссылки. (?<!...) в регулярках Оверпаса нет, но как-нибудь переживём:

nwr["contact:vk"~"://[^v]", i];

В основном тут нас поджидают ссылки на другие соцсети.

Вообще и завоение слешей проверить бы:

nwr["contact:vk"~"[^:]//"];

А какие символы могут быть в значении? Ну буквы, цифры, подчёркивания. Поищем всё кроме них (и кроме точки с запятой, которую используют в качестве разделителя нескольких значений):

(
  nwr["contact:vk"~"[^a-zA-Z0-9/.:_]"];
)->.a;

(
  nwr.a["contact:vk"~"; ?https://vk\\.com"];
)->.skip;

(.a; - .skip;);

out geom;

И найдём ссылки:

с URL-параметрами после ?. Зачастую с трекинговыми
с невидимыми U+200B
с @. И нет, это не никнеймы. В ВК это ссылки на статьи
с @, но уже просто адреса электропочты
с + — номера телефонов
с - — опечатки в символе _, либо в ссылках на записи, у которых формат: wall-123_456

Отсечь бы ещё : из разрешённых символов:

(
  nwr["contact:vk"~"^https://vk\\.com/.*[^a-zA-Z0-9./_]"];
)->.a;

(
  nwr.a["contact:vk"~"; ?https://vk\\.com"];
)->.skip;

(.a; - .skip;);
out geom meta;

Зачем? Ну чтобы вот такое поймать contact:vk = https://vk.com/https://vk.com/etloncoffee

И вишенка:

nwr["contact:vk"~"^vk\\.com$", i];

Офис ВК? Нет, Пятёрочка в Нальчике

p.s. чтобы поиграться с реальными ошибками добавляйте в начало запроса [date:"2026-07-01T00:00:00Z"]

OpenStreetMap User's Diaries: به گیتاصالح ویراست خوش آمدید

2026-07-05T09:33:57+00:00

ویرایشگر گیتاصالح ویراست در خدمت شماست

1.ویرایش اوپن‌استریت‌مپ تهران مطابق اسناد شهرداری تهران و کدگذاری و نامگذاری انگلیسی معابر آن 2.ویرایش شهرستان‌ها 3.ویرایش خارج از کشور و نامگذاری فارسی معابر آن ارتباط با گیتاصالح شماره تلفن همراه = +989982501064 آدرس ایمیل = amirali44asghari@gmail.com

OpenStreetMap User's Diaries: Mapping (wheelchair) accessibility

2026-07-04T17:50:49+00:00

About three years ago, I had given a talk to some folks at the Irish Wheelchair Association in Kilkenny about the history of Kilkenny. They wanted me to do that again, but I thought that giving the same talk would be boring and asked whether I could talk about mapping accessibility instead. They were open to the idea, so I did that. I thought it would be a good opportunity to tell them about OpenStreetMap, but also to get some input from them about what else we could map.

In preparation for the talk, I created an “accessibility” preset in StreetComplete with quests all to do with wheelchair and visually impaired mapping, including the surface quest, because I figured that would be important for the routing services for wheelchairs. I surveyed quite a bit in Kilkenny city centre to get an idea of what the situation in town is.

I’ve recorded a video with the same slides I used for the talk which you can watch on YouTube (proof-read English and German subtitles available).

Additional quests for StreetComplete that I came up either by myself or with their help are (They’re also in the video, but it’s handy to have them listed here.):

Is this ATM wheelchair accessible?
Is this vending machine accessible?
Is payment in this shop/ restaurant wheelchair accessible? (They said that sometimes the payment terminals are fixed in place too high up on a counter.)

After the talk, one of the facilitators told me about an upcoming audit walk in Kilkenny (on the 24th of July) to assess accessibility. So I got in contact with them to tell them about wheelmap.org and sent them a link to the video, so they don’t audit things I have already surveyed.

I used two overpass-turbo queries in the talk/ video to show some of the data that can be extracted from OSM:

shops with the wheelchair key, colour-coded by accessibility (which is similar to wheelmap, but the data can be exported)
steps and ramps, colour-coded by the ramp key (yes/ no/ separate/ no data)

Additional ones could be:

steps and tactile paving
highway=crossing and tactile paving - I might actually use that for quality control, bc the data for Kilkenny could be outdated.

I’ll add more information here after the audit, if I take part and remember to do so.

OpenStreetMap User's Diaries: Straßenbilder für den Landkreis Fulda

2026-07-04T15:22:10+00:00

Die OpenStreetMap Community in Fulda hat in Kooperation mit dem Magrathea Laboratories e.V. - Chaos Computer Club Fulda - eine Panoramax Instanz ins Leben gerufen.

Panoramax ist eine Software für Straßenbilder wie man es von Google oder Apple Maps kennt. Der große Unterschied: Die geschossenen Bilder werden unter CC-BY-SA-4.0 Lizenz veröffentlicht und gehören also keinem Unternehmen. Das Projekt verfolgt die Idee der digitalen Unabhängigkeit und setzt zusätzlich auf eine zukunftsorientierte dezentrale Infrastruktur in der sich Panaromax Server der ganzen Welt in eine sogenannte Förderation begeben um als ein großes Ganzes zu fungieren.

Fulda ist hiermit die erste Stadt in Deutschland, die dieser Föderation mit ihrer Instanz beigetreten ist und es gibt auch schon einiges zum Anschauen:

https://panorama.osm-fulda.de/

Zu sehen gibt es aktuell einige Stadtteile Fuldas und Radwege um Fulda herum.

ℹ️ In den Filtereinstellungen könnt ihr den Rest der Welt miteinblenden lassen.

Aktuell haben wir 34,854 Bilder die 474 km abdecken. Auf Festplatten sind das ~340 GB. Also ca. 0,74 GB pro 1 km Strecke. Unsere Ressourcen sind aktuell zu 34% ausgelastet. Wir bekommen also noch einiges mehr “in den Kasten” bevor wir uns über mehr Finanzierung Gedanken machen müssen.

Zwei Dinge schon mal vorab: Gesichter und Nummernschilder werden natürlich unkenntlich gemacht. Falls trotzdem etwas auffällt, kann dies gemeldet werden und wir werden uns darum kümmern. Häuser werden nicht unkenntlich gemacht, da es dazu keine Gesetzesgrundlage gibt. Die großen Anbieter machen das bisher nur aus Kulanz.

Du hast Fragen, interessante Ideen dazu oder magst mitmachen, dann schau doch einfach mal in unserem Chat oder im Fuldaer OpenStreetMap Wiki vorbei!

ℹ️ Mal 1-2 Stunden investiert und dein Stadtteil/Dorf könnte auch abgelichtet sein.

Motivation

Mal ab von der technischen Finesse und dem Konzept der Dezentralität von Panoramax, hat das Projekt mehrere Ziele:

Es soll den Mappern hier hilfreiches und verwendbares Bildmaterial bieten, denn… es gibt viel zu tun! Immer! > Die OpenStreetmap Community in Fulda hat im letzten Jahr immens viel geleistet. Viel wurde gemappt: Sämtliche Busrouten in Fulda, inklusive Haltestellen, Bürgersteige und Radwege, super viele Geschäfte und Gastronomie, uvm. Gerne mal im Wiki vorbeischauen um eine Idee zu bekommen was wir so alles tun. So oder so: All diese Arbeit/Hobby trägt dazu bei, dass wir in unserer Region ohne BigTech Tools auskommen können.

Aber natürlich soll es auch einfach als freie Alternative für Straßenbilder in der Region dienen. Und insbesondere kleine Orte könnten davon auch etwas haben, denn diese wurden schon immer von Google und Co. ignoriert. Google aktualisiert ihre Bilder nur einmal alle paar Jahre. Für Fulda ist ein Update von Panoramax Bildern nur eine freundliche E-Mail an die Community oder eine Fahrt mit eurer eigenen 360° Kamera weit entfernt. Damit erreichen wir langfristig eine bessere Aktualität als ein Google das leisten kann.

Aber das Projekt bringt hoffentlich noch etwas Anderes mit sich:

Es soll nämlich auch andere Regionen ermutigen, auch diesen Schritt zu wagen. Denn es ist wirklich nicht schwer!

Technisches

Alles läuft auf einem schlanken k3s-setup bei Hetzner, vollständig per GitOps verwaltet. Das heißt: Der gesamte Server ist als Code in git definiert, alles was es braucht sind ein paar secrets, die im Rahmen des Setup Prozesses hinterlegt werden.

Auf dem Server laufen Panoramax (API, Worker und Web-Frontend), eine PostgreSQL Datenbank mit PostGIS, automatische TLS-Zertifikate via Let’s Encrypt sowie ein Netzwerkspeicher (hier eine Hetzner Storage Box) für die hochgeladenen Bilder.

Finanzen

Die aktuellen Kosten werden derzeit privat getragen. Der Magrathea Laboratories e.V. hat sich aber schon zuvorkommend gezeigt und würde auch mit einspringen um die aktuellen oder zukünftigen Kosten zu decken.

Wir sind selbst noch ein wenig perplex, dass man mit so wenig Geld schon so weit kommt.

Komponente	Kosten (pro Monat)
Hetzner CX23 (2 vCPU, 4 GB RAM, 40 GB SSD)	4,75 €
Hetzner Storage Box BX11 1TB (Bilder-Speicher)	3,75 €
Gesamt	≈ 8,50 €

Dazu kommen nur noch die Domain und ein Git-Hoster wie Codeberg – beides gibt’s für kleines Geld oder sogar umsonst. Fertig ist eine produktionsreife Straßenpanorama-Plattform. Für ca 10€ mehr könnte man auf 5 TB aufstocken. Auch das ist finanziell keine große Herausforderung.

Ausblick

Was wünschen wir uns? Naja, große Erwartungshaltungen haben wir nicht. Die Realität hat schon öfters gezeigt, dass viele tolle Projekte jeglicher Art es nicht geschafft haben sich in irgendeiner Form zu etablieren. Aber das spielt für uns keine große Rolle. Für das Mappen in OpenStreetMap ist Panoramax pures Gold!

Es gibt natürlich einige Szenarien, die ziemlich cool wären, zB.:

Mehr Beteiligung von Mitmenschen, Gemeinden, der Stadt oder vielleicht anderen Vereinen. Es gibt so einige Einsatzwecke die man verfolgen könnte. Für den Tourismus z.b. oder auch für Kleinunternehmer, die gerne Rundumbilder ihrer Läden online haben möchten oder halt doch nur mal schauen, wie der Schlossgarten oder sonst was aussieht. Wenn das alles ein wenig größer werden würde, könnten wir auch darüber nachdenken, die Straßen in beide Richtungen abzubilden. Aktuell machen wir dies nur für größere Straßen um Platz zu sparen.

So oder so, es bleibt spannend und wir hoffen es bereitet nicht nur uns Freude!

OpenStreetMap User's Diaries: contact:website? Нет, contact:vk

2026-07-04T14:01:40+00:00

Увидя contact:website = https://vk.com/... руки открыли Overpass Turbo

Острожно, регулярки!

Ну поехали

искать, что можно перенести в contact:vk:

nwr["contact:website"~"^https://vk\\.com"][!"contact:vk"]

Всегда ли https?

nwr["contact:website"~"^http://vk\\.com"][!"contact:vk"]

Всегда ли http?

nwr["contact:website"~"^vk\\.com"][!"contact:vk"]

Всегда ли в начале?

nwr["contact:website"~"vk\\.com"][!"contact:vk"]

Аккуратно с автозаменой, есть валидные домены оканчивающиеся на vk.com. Затыкается примерно так: "(^|[^a-z])vk\\.com"

Всегда ли `.com`?

На практике да. Но не в website!

nwr["website"~"vk\\.ru"][!"contact:vk"] — (помним про ложные срабатывания)

Ещё есть .link, но это в принципе можно считать сайтом заведения. Это всё?

Ищем другие доменные зоны

(
   nwr["website"~"(^|[^a-z])vk\\..+/"][!"contact:vk"]; 
)->.a;

(
   nwr.a["website"~"\\.(link|com|de|ru)"];
)->.skip;

(.a; - .skip;);
out geom meta;

Кроме редких vk.cc (сокращатель ссылок) и vk.me (прямые ссылки на фотки) особо ничего.

Это всё?

Отключаем зависимость от регистра

(
   nwr["website"~"(^|[^a-z])vk\\.(com|ru)/",i][!"contact:vk"];
)->.a;

(
   nwr["website"~"(^|[^a-z])vk\\.(com|ru)/"][!"contact:vk"];
)->.skip;

(.a; - .skip;);
out geom meta;

Артефакты прошлого

Фан-факт: OpenStreetMap старше ВКонтакте.

nwr["website"~"vkontakte\\.",i][!"contact:vk"];

Всё?

А теперь всё тоже самое но без [!"contact:vk"]

В следующей серии изучим сам contact:vk

OpenStreetMap User's Diaries: First changeset review insights for Andhra Pradesh, India

2026-07-04T06:11:55+00:00

📊 First changeset review insights for Andhra Pradesh, India

🙋‍♂️ Review Requests: 32% of newcomers requested a review of their first changeset.
✨ Technical Quality: 32% of a newcomer’s very first edits are completely free of technical errors.
⚠️ Low-Severity Issues: 49% of changesets have low serverity errors like abbreviation issues or duplicate node-way geometries

💡 Localized, faster community validation workflows are essential to support mapping talent.

About 450 editors join OpenStreetMap and contribute their first edit everyday based on a study for the year 2023.¹ Despite diverse OSM review tools and processes, there were few studies about OSM new editor data quality at country level.² Very little is known about their contribution quality and persistence at province level. This need was identified in the first ever desk analysis of State of the map for Andhra Pradesh in 2025. Even attempting to statistically analyze is not easy, given the need to query databases with specialized programs. OSM Changeset Analyser(OSMCha) is a very good tool for reviews. Using OSMCha and OSM APIs, I built a small Python Jupyter notebook program with help from Github Copilot. I applied this to understand the new editors contributions for Andhra Pradesh province of India for Q1, 2026. I found that 32% of first edit changesets are of good quality. 49% have low severity issues. Only 3% continue the edit activity in the subsequent 30 days after discussion on their first changesets. This program can be reused easily by modifying OSMCHA’s AOI filter identifier and OSMCHA user token.

Review process using OSMCha

A screenshot of review of a changeset in OSMCha

A reviewer logs into OSMCha using their OSM credentials to generate an API authorization token. To isolate a new editor’s very first contribution, an Area of Interest (AOI) or filter is configured using the metadata parameter changesets_count__max=1. An example filter for “Andhra Pradesh” province is given as example, which can be modified.

Reviewers can then perform three primary actions on a changeset:

Flag:Mark the changeset as “Good” or “Bad”.
Tag (for “Bad” changesets): Apply qualitative assessment tags regarding Severity (Low, High, Critical), Resolution, and Intentionality, or flag it for the Data Working Group (DWG).
Discuss: Add a discussion message with constructive feedback. Note: This is the only step that triggers an on-site notification and email to the new editor via OSM.

New editor may respond with further edits or may ignore the review.

Same reviewer or another reviewer can update review tags later based on feedback from the editor or after further edits.

Case study

Location of centre of changeset bounding box of newbie edits

I have been reviewing new editors’ first changeset contributions for more than 9 months regularly starting from Q4,2025 for the province of Andhra Pradesh in India. There are no other reviewers participating in this task. I was curious to understand whether my effort is making any difference, as only two new editors reached out to me over OSM email.

I created a new filter (link temporary: pickup aoi id from the url and use it in software) for the specified duration with review status blank for the duration of study. Basic statistical analysis of new editors’ first changeset in terms of quality as reflected by severity, issue resolution and also the activity following the first review discussion for thirty days was done. The Python Jupyter notebook software created for this work is available on Github.

Month wise changsets

The following table gives the number of first changesets of new editors in the month of observation. Total number is 122, which means 14 new editors edit every 10 days

Serial No	Year-Month	First Changesets
1	2026-01	27
2	2026-02	60
3	2026-03	35

Geographic distribution

I did analysis of district wise changeset distribution based on the center of the changset bounding box. 24 districts were covered by changesets. Guntur district had maximum coverage from 21 changesets followed by Krishna with 13. Annamayya and Parvathipuram Manyam districts had 1 changeset each. Guntur and Krishna had changesets of 5, 6 due to Hot OSM Project 17520, which was disaster mapping project launched in September 2024 to help Vijayawada flood relief efforts. After excluding these, Guntur (16), Bapatla (9), Palnadu (8) are ranked top districts for changesets. Four districts namely Chittoor, Sri Sathya Sai, Alluri Sitharama Raju, Polavaram districts did not have changesets. One changeset center is in Telangana province near the border with Andhra Pradesh.

Qualitative analysis from reviews

All 114 reviews were done by ‘user:arjunaraoc’. Most of the new user changeset issues are related to the following:

Tags: Use of abbreviations like Rd for ‘Road’, all upper case text or non standard tags, Violation of OSM policies like Personally identifiable information.
Feature geometry: Creating both a way and a node to represent the same feature.
Number of edited features: Some times a new editor creates a changeset with too many feature edits like several road changes or addition of several buildings. As there are bound to be mistakes, such changesets are likely to be reverted. It is better for new users to make few edits 1-5 for a similar feature as it helps the reviewer also in giving useful feedback.
Comments: Unclear comments
Source: No mention of local knowledge as source when the imagery used as source does not reflect the edit

Changeset comments analysis

Word cloud of top 10 words from 122 changeset comments of new users of OSM

Top 10 words used in editor comments with their frequencies are given below

Word	Count
created	35
road	26
added	21
near	14
hotosmproject17520	11
osmindia	11
andhramapping24	11
updated	11
residential	8
highways	8

From the table, it can be seen that ‘Road’ seems to be the most edited feature. It is observed that 13 out of 122 (about 11%) contributed only one point.

The median counts of features created, modified, delete per changeset are 5.5, 1.0, and 0.0 respectively.

Time taken for assessment/discussion

Editors can flag their changeset for review requests while submitting the changeset. Out of the total 122 changesets, 39 (32%) were requested for review. None of HOT OSM Project contributors requested a review. Irrespective of the review request flag, 114 were assessed. Out of 8 that were unassessed, 7 were for Hot OSM Project 17520. 113 were discussed. The average time taken for discussion was 14 days, with a minimum of 4 days and maximum of 60 days.

Severity analysis

OSMCha showing sample review of changesets for Andhra Pradesh, India

OSM newbie editor changesets quality (severity) distribution

A flow diagram which categorizes the changesets based on severity when a changeset was assessed ‘Bad’ is shown. Severity rating has three options ‘low’, ‘high’, and ‘critical’. Out of 122 total changesets, 114 were checked. 39 were found to be good and 75 bad. Low severity was assigned for 59 and high severity for 10. None were assigned critical severity. There was no rating for 6 changesets.

Issue resolution analysis

OSM newbie editor changesets issue resolution distribution

A flow diagram which categorizes the changesets based on issue resolution when a changeset was assessed ‘Bad’ is shown. Issue resolution rating has two options ‘Resolved’, ‘Unresolved’. Out of 122 total changesets, 114 were checked. 39 were found to be good and 75 bad. ‘Resolved’ was assigned for 59 and ‘Unresolved’ for 13. Resolution status was not availble for 3 changesets.

Newbie edit activity after discussion

Newbie editor changeset count within 30 days after discussion on first changeset

113 changesets out of 122 were discussed via OSMCha. The editor activity was checked for 30 days after the discussion and number of editors per changesets of 0 to 8, 9+ were plotted. It is observed that 102 editors did not make any further edits. 1 or more edits were made by 11 editors. Only 3 editors made 9+ edits. A long duration study with 1000 changesets or more is needed to understand the percentage of editors who become active editors. It could be compared with newbie editors persistence for a month when they do not receive review feedback.

Lessons learnt

Reduce time taken for review: The review delay for about 11 cases extended beyond a month. It is desirable to review the first changesets in 1-2 weeks. Using RSS feed from OSMCha can help in noticing the new edits faster. More reviewers can also help as 32% of changesets have “Request review” enabled.
Enable the new editor to fix issues with low severity: While reviewing, minor mistakes were fixed and the same was informed to the editor via discussion comment. Changeset resolution was set to ‘Resolved’. As suggested in OSMCha review tips, it is better to give suggestions for low severity issues through discussion, to encourage the editor to make required changes.
Explain rating bad is required even for minor mistakes due to software limitation: Another suggestion that I missed is to explain the limitation in assigning good/bad for a changeset in discussion comment, to not discourage new editors when then see a review marked as bad.

Conclusion

The analysis of OSM new editors’ first changesets showed that 32% of newcomers requested a review of their first changeset. 32% of first changesets are of good quality. 49% changesets have low severity issues. Only 3% of new editors continue the edit activity after discussion on their first changesets. Localized, faster community validation workflows are essential to support new mapping talent

Acknowledgements

Github Co pilot was very helpful in coming up with the initial version of software program from a simple chat prompt. The draft of this article was updated manually based on useful review feedback from Gemini AI. It also helped in converting the wiki code draft to Kramdown format of OSM User diary.

References

Analyzing the Changesets of OSM Newcomers, Heigit, 29 January 2024. ↩
Toshikaju Seto, Hiroshi Kanasugi, Yuichiro Nashimura, Quality Verification of Volunteered Geographic Information Using OSM Notes Data in a Global Context (2.Related work)”, ISPRS Int. J. Geo-Inf., 6 June 2020. ↩

OpenStreetMap User's Diaries: The night the earth shook, strangers started to draw

2026-07-03T08:00:54+00:00

Not at all my work, but a place to record the work of Akash Wadhwani. They have just written a great piece on OpenStreetMap and the work of volunteers to map in support of disaster response.

I recommend you all read it, it’s a great advert for you.

https://sheets.works/data-viz/strangers-draw-maps

OpenStreetMap User's Diaries: BUSPLAN ZA BANJA LUKU

2026-07-02T09:56:42+00:00

Deutsch Fahrplan & Liniennetz für Banja Luka Finde schnell und unkompliziert alle Buslinien, Abfahrtszeiten und Haltestellen in Banja Luka. Nutze die interaktive Karte auf https://delebe.de/banjaluka, um deine Route zu planen, Anschlüsse zu finden oder deinen aktuellen Standort live anzuzeigen. Egal ob Alltag oder Wochenendausflug – hier hast du den gesamten Nahverkehr im Blick.

English Banja Luka Bus Timetable & Route Map Easily find all bus lines, departure times, and stops in Banja Luka. Use the interactive map at https://delebe.de/banjaluka to plan your route, check connections, or track your live location. Whether it’s your daily commute or a weekend trip, we’ve got your transit covered.

Srpski (Latinica) Red vožnje i mapa linija za Banja Luku Pronađi brzo i jednostavno sve autobuske linije, polaske i stanice u Banjoj Luci. Koristi interaktivnu mapu na https://delebe.de/banjaluka da isplaniraš svoju rutu, provjeriš presjedanja ili prikažeš svoju trenutnu lokaciju uživo. Bilo da je u pitanju svakodnevni prevoz ili vikend izlet – ovdje imaš kompletan uvid u gradski saobraćaj.

Српски (Ћирилица) Ред вожње и мапа линија за Бања Луку Пронађи брзо и једноставно све аутобуске линије, поласке и станице у Бањој Луци. Користи интерактивну мапу на https://delebe.de/banjaluka да испланираш своју руту, провјериш пресједања или прикажеш своју тренутну локацију уживо. Било да је у питању свакодневни превоз или викенд излет – овдје имаш комплетан увид у градски саобраћај.

OpenStreetMap User's Diaries: Mejores deseos

2026-07-01T21:06:21+00:00

Tuve una discusión por temas futboleros, me respondieron feo a un meme que puse y yo respondí peor, ese momento me sentí bien, luego pense y me sentí triste por haberme dejado llevar por la pasión del coraje, en fin, quiero que este mapaton latinoamerica llegue lejos y sirva para muchos tomadores de decisiones. Saludos

OpenStreetMap User's Diaries: [GSoC] Prototyping medial axis implementation for area routing

2026-07-01T12:48:43+00:00

Hi again! During the last weeks I’ve been working on a Python prototype of the medial axis that will later be implemented in Valhalla

The goal of this prototype is to validate the algorithm, experiment with different choices and make it work for some synthetic and real OSM areas.

I’ve done it using Shapely, which is a python package built on top of GEOS (the library used by Valhalla). So thanks to Shapely I can implement the algorithm using functions that I’ll use in Valhalla, but in a much easier way without having to care about Valhalla’s complexity.

However GEOS doesn’t provide a medial axis implementation. So to achieve the medial axis we have to build it from the Voronoi Diagram. The thing with the Voronoi is that it doesn’t care about topology it just works with point clouds. So in order to get a medial axis of it we have to:

Collect all vertices from the polygon’s outer boundary and its holes
Generate the Voronoi diagram
Iterate over every Voronoi Edge
Discard every edge that is not completely contained within the polygon

And then we have our medial axis! This is a raw version, later we have to prune it as explained in the previous diary entry.

Algorithm overview

1. Building the polygon

The first step is whether to reconstruct the polygon from OpenStreetMap or create my own polygon to test the exact case I want to.

For example:

square = Polygon(
    [(0,0),(5,0),(5,10),(30,10),(30,30),(0,30)], # outer ring
    [
        [(5,15),(10,11),(18,15),(18,20),(5,20)], # inner rings
        [(2,5),(3,3),(4,5),(3,8)],
    ])

Because the Voronoi only considers the input vertices, the resulting skeleton becomes inaccurate, to mitigate this problem I densify every boundary segment using:

polygon.segmentize(1.0)

Which inserts one vertex every meter, this produces a much smoother approximation of the medial axis.

2. Voronoi generation

Once all vertices have been collected, we generate the diagram. However, this diagram extends outside the polygon. So every Voronoi edge is tested and only thoise completely contained inside the polygon are kept. Duplicate edges are also removed. And now we have:

Plaza de Santo Domingo Murcia:

It starts looking good, but now we have to get the skeleton of it

3. Pruning dead branches

To better understand the implementation it is important to know what degree of a vertex is. And we can simply define it as the number of edges incident to that vertex. (Don’t judge my drawing skills :))

So in order to obtain the skeleton, I compute the degree of every vertex, and iteratively walk from each leaf until reaching a junction (degree >= 3). And after removing these branches now we have it!

4. Extra implementations

There are a few more things I’ve implemented, like test entrances joining the skeleton to the closest point of the skeleton without crossing over a boundary. Moreover, because of the densification we made before, what looks like an edge, they really are segments of ~1 meter, then I had to simplify these, joining everything between degree 1-3 or 3-3. So the numbers of edges remains low as we discussed, in my last diary entry, was a big pro of the medial axis. Here is an example testing entrances:

Conclusion

This prototype has been extremely useful to validate the approach and understand the practical challenges. Thanks to doing it here first, we can experiment and refine the approach in a much easier way. Next step is bringing this into Valhalla.

Finally, thanks to Chris, Kevin and Nils who are always helping me a lot and they have been a great support! I want to also thank the people that commented on my last entry, all the messages have helped us to look for edge cases and refine our implementation, Thanks a lot!

I’ve kept this entry without much code so it can be understandable for everyone, but if someone is interested in the code implementation feel free to ask!

OpenStreetMap User's Diaries: Культурное наследие.

2026-06-30T18:17:11+00:00

В моём посёлке Слатино не очень много есть данных, большинство домов отсутсвуют, я переодически там что-то добавляю и даже пытался добавить все дома (это было очень сложно). Там я часто нахожу почти “Культурное наследие”, изменения, правки и т.д. 2009-2015 годов, я даже нашёл один профиль человека который максимально детально сделал своё село в 2011 в Сумской области, около 15к правок было в одном блоке загрузки. И там был коментарий “Какая сегодня погода была - не знаю. Я целый день провёл перед компьютером чтобы моё село не было пустой точкой на карте:)”. Кстати тогда он +- в последний раз был в сети. Вообще такое “Культурное наследие” не редкость, в отдалённых сёлах можно часто увидеть правки 15-16 летней давности. Возможно людям которые этим занимались давно померли, может уехали, в общем сменили курс жизни. Люди которые начали делать правки на ОСМ очень давно и досихпор этим занимаются - единицы. Скорее всего этот дневник через лет 10-15 станет тоже своеобразным “Культурным наследием”, а можем мы вообще станем тупее и даже не сможем редактировать карту 😀

OpenStreetMap User's Diaries: Globe Meet-up last time. Albert pub tonight

2026-06-30T18:07:46+00:00

We’ve got another OSMLondon pub meet-up tonight!. I’m trying to be a bit more orginal with pub choices recently, so I picked a place down in Victoria. This is not the end of London I know best, but it’s good to go South a bit. In fact I seem to remember past Victoria meet-ups (at The Windsor Castle?) being very well attended, so we’ll see. I also don’t know The Albert pub, so we just have to cross our fingers for good beer choice/food/spaciousness practicalities. If it’s hideously busy we’ll have to tough it out until the after work crowds disperse.

The last meet-up I picked “The Globe” near Moorgate. That worked pretty well for attracting attendees. I suppose it’s nice and central and in The City where a lot of people work. We got some new folks coming along, including some very active OSMers who’d not joined us at a meet-up before.

I feel like the pub was not so good for being a bit expensive. City prices? Or maybe it’s just my imagination. We’ve had some recent rounds of inflation so I haven’t got used to >£7 per pint yet :-( It’d be interesting to know if price differences between cheap and expensive pubs have shifted too. Feels like not much difference these days. It’s expensive everywhere. I used to like choosing pubs where beer is cheap, like Wetherspoons and Sam Smiths, but I suppose I can’t expect student prices all my life.

But yes… otherwise “The Globe” pub worked pretty well.

Let’s see how we do with attendees tonight. Everyone’s welcome!

All the details on the London wiki page

Geofabrik: New in OSM Inspector: Turn Restrictions

2026-06-30T15:36:37+00:00

We’ve added a new turn restrictions view to OSM Inspector showing (almost) all restrictions and highlighting invalid ones.

There are some turn restriction validators around already but they tend to be based on live Overpass queries and therefore are negatively affected by recent performance issues.

The turn restriction validator we have added to our tool osmi_simple_views (which already creates the tagging, highways, geometry and places views from an up-to-date copy of the OpenStreetMap planet dump) does not require Overpass but instead writes its results to SQlite files in one go. These are then served to OSMI users as a slippy map (currently using Mapserver but this is subject to change as we’re preparing a move to vector tiles).

The code validates the number, types and roles of relation members. Tag values are checked except for conditional restrictions, no_entry and no_exit restrictions.

We hope that you find this validator useful in improving the quality of OpenStreetMap data in your region.

See the wiki page for a description of all potential validation errors and suggestions how to fix them, and feel free to open an issue on GitHub if you find something amiss.

OpenStreetMap User's Diaries: 广州地铁、广佛地铁和广东城际车站的出入口名称

2026-06-30T14:41:04+00:00

广州地铁、广佛地铁与广东城际车站的出入口有编号外的名称，将OSM中的name写为“A口”等内容并不合适。

查找

可在站点及出行查询网站和广州地铁App查询，也可在车站内寻找出口资讯。

在线查询到的名称中可能包含一些注释信息，如“花城大道（本站D口通往花城汇、广州国际金融中心，开放时间为7:00-22:30，敬请留意。）”，应删去注释信息仅保留“花城大道”。

在线查询到的名称可能与线下名称有些区别，以线下为准（或者选一个你觉得合适的？）。

示例：13666261426、13941792080

OpenStreetMap Blog: State of the Map 2026: Call for Posters

2026-06-30T10:00:00+00:00

Did you miss the call for general and OSM Science presentations? Fret not! You can still present your project and initiatives at State of the Map 2026! The Call for Posters for SotM 2026 is now open!

Your poster could show how well your community is mapped. It could be a new beautiful style or a map. It could be a community project or statistics, or a poster explaining and inviting people to OpenStreetMap. The important thing is that it is about OSM. We also welcome academic posters on research around OpenStreetMap data.

For inspiration, you can check out the SotM 2025 posters – https://2025.stateofthemap.org/posters/

Submission Requirements

The poster must be in A0 format (841×1189 mm).

The poster must be related to OpenStreetMap.

The poster must be open, innovative and transparent (no copying).

The poster must be an original work (individual, collective or institutional).

The poster must be submitted under an open license (CC-BY-SA 4.0 or CC0).

Maximum of two entries per person, team or institution.

You’re welcome to use generative AI/LLMs like ChatGPT to improve your abstract or text, but you must mention this in the “Notes” field of your submission. Please refrain from generating the whole Poster, images or large parts of it using AI/LLMs. It’s fine to use it to improve the wording, the grammar and to avoid spelling errors, or to create a translation of texts you have written yourself in your native language. We do prefer imperfect submissions with a human touch that make us look forward to an exciting and interesting poster. We do not want “perfect” and unnecessarily bloated submissions that all sound the same since they were generated by some tool.

How to participate

Upload your poster via https://files.osmfoundation.org/apps/forms/s/9CMfCCHJEBpyTdp8nGnLnY35 (No Emails are sent to you on submission. If anything is missing or your poster is shortlisted or not, you will hear from us)

Maximum file size: 30-40 MB

Format: PDF

Please provide a description of your poster in the upload form. For example, the background of the project or whatever you consider important to mention in the context of the poster – all that you would tell people if you show them your poster. We will publish this text together with the poster on the SotM website.

Timeline

Deadline: 31 July 2026 23:59:59 UTC +0

The SotM team hopes to shortlist up to 15 posters that will be published on our website and some other SotM channels under CC-BY-SA 4.0

The State of the Map Working Group

Do you want to translate this and other blogposts in your language…? Please email communication@osmfoundation.org with subject: Helping with translations in [your language]

The State of the Map conference is the annual, international conference of OpenStreetMap, organised by the OpenStreetMap Foundation. The OpenStreetMap Foundation is a not-for-profit organisation, formed to support the OpenStreetMap Project. It is dedicated to encouraging the growth, development and distribution of free geospatial data for anyone to use and share. The

OpenStreetMap Foundation owns and maintains the infrastructure of the OpenStreetMap project, is financially supported by membership fees and donations, and organises the annual, international State of the Map conference. Our volunteer Working Groups and small core staff work to support the OpenStreetMap project. Join the OpenStreetMap Foundation for just £15 a year or for free if you are an active OpenStreetMap contributor.

OpenStreetMap was founded in 2004 and is an international project to create a free map of the world. To do so, we, thousands of volunteers, collect data about roads, railways, rivers, forests, buildings and a lot more worldwide. Our map data can be downloaded for free by everyone and used for any purpose – including commercial usage. It is possible to produce your own maps which highlight certain features, to calculate routes etc. OpenStreetMap is increasingly used when one needs maps which can be very quickly, or easily, updated.

OpenStreetMap User's Diaries: Tile server for toll roads, cycling restrictions and cobblestone overlays

2026-06-29T15:12:50+00:00

For many years it has bugged me that no maps display whether a road is a toll road, whether cycling is forbidden there and whether its surface is made of cobblestone. For driving, avoiding toll roads can save a lot of money in many places, but sometimes taking a small section of toll road can save a lot of fuel and time. For cycling, in some especially bicycle-hostile countries (for example Germany, Austria, Switzerland and Belgium), cycling is forbidden on the majority of main roads, and the alternatives are often in a very bad state. In East Germany in particular, many small roads and streets are paved with cobblestones, which makes cycling slow and uncomfortable and can cause damage to the body, bicycle and luggage.

While route calculation services offer to avoid these types of roads to some extent, rendering them on a map is important to get a general overview of different options, and in case of cycling because route calculation generally works badly, as personal preferences and cycling styles vary greatly and the infrastructure is full of limitations that cannot be accurately represented on OpenStreetMap.

After a long time of digging into the creation of OpenStreetMap tiles, I have finally managed to create my own overlay tiles to display these road properties on any map.

So far my impression is that most of the data is pretty accurate, in particular the data about toll roads, but bicycle=use_sidepath is very largely underused, so most roads where cycling is forbidden due to a compulsory bikepath are not mapped as such yet.

The tiles are hosted on https://tiles.facilmap.org/ and are available as Map styles on FacilMap. On FacilMap there is also a legend that explains the meaning of the different colours.

Feel free to use the tiles in your own projects, for now there are no limitations. When using the tiles in a commercial or heavy-use project, consider a monthly donation to cover the server costs.

The source code and map styles can be found on GitHub. If you have any suggestions for improvements, open an issue there or comment on this diary entry.

OpenStreetMap User's Diaries: Sobre OSM for Cities

2026-06-29T08:14:22+00:00

OSM for Cities es un proyecto de distribución de datos abiertos sobre las ciudades basado en OpenStreetMap.

El objetivo es facilitar el acceso y el seguimiento de los datos generados por la comunidad de OSM a organizaciones, grupos locales y profesionales que trabajan en temas urbanos.

La idea surgió cuando trabajaba en proyectos de planificación del transporte, más o menos cuando conocí OpenStreetMap, en 2008. No había cobertura de datos oficiales sobre vías e infraestructura, y siempre era necesaria una fase inicial de recopilación de datos, que al final del proyecto no se reutilizaban.

Hoy en día la situación es un poco diferente y muchas grandes ciudades producen y publican sus datos. Pero incluso las ciudades que cuentan con equipos técnicos centran sus recursos en conjuntos de datos críticos y rara vez logran publicar y mantener actualizada la información sobre mobiliario urbano, cobertura arbórea, alumbrado público y otros elementos específicos que puedan ayudar en las políticas públicas.

OSM for Cities pretende ser una herramienta para quienes trabajan con este tipo de información, complementando otras herramientas que ya existen en el ecosistema de OSM, como la herramienta HOT Export.

Una característica distintiva del proyecto es que permite buscar cualquier ciudad del mundo y visualizar sus datos dentro de sus límites administrativos, sin necesidad de conocimientos técnicos ni de preparación previa de los datos. Solo hay que buscar el nombre de la zona, elegir una plantilla —como paradas de autobús, escuelas o árboles— y la plataforma la mostrará en un mapa.

Además, es posible descargar estos datos en formato GeoJSON y suscribirse para recibir actualizaciones por correo electrónico en caso de que se editen los datos.

El proyecto es de código abierto y lo mantengo yo, en mi tiempo libre. Obviamente, me gustaría que el proyecto evolucionara para contar con apoyo que financie su infraestructura y desarrollo, pero por el momento el enfoque es validar su propuesta.

Por eso, invito a la comunidad a visitar el sitio web y explorar los datos de su ciudad para conocer más sobre la plataforma y compartir sus impresiones.

Traducción del post original por DeepL.com

OpenStreetMap User's Diaries: About OSM for Cities

2026-06-29T08:12:00+00:00

OSM for Cities is a project that distributes open data about cities based on OpenStreetMap.

The goal is to make it easier for organizations, local groups, and professionals working on urban issues to access and monitor the data produced by the OSM community.

The idea originated while I was working on transportation planning projects, around the time I discovered OpenStreetMap in 2008. There was no official data coverage for roads and infrastructure, and an initial data collection phase was always necessary, data that was almost never reused once the project ended.

Today, the situation is somewhat different, and many large cities produce and publish their own data. But even cities with technical teams focus their resources on critical datasets and rarely manage to publish and keep up-to-date information on street furniture, tree cover, street lighting, and other specific elements that could inform public policy.

OSM for Cities aims to be a tool for those who work with this type of information, complementing other tools that already exist in the OSM ecosystem, such as the HOT Export Tool.

A unique feature of the project is that it allows users to search for any city in the world and view its data within its administrative boundaries, without requiring technical knowledge or data preparation. Simply search for the area’s name, choose a template—such as bus stops, schools, or trees—and the platform will render the data on a map.

You can also download this data in GeoJSON format and subscribe to receive email updates if the data is edited.

The project is open source and maintained by me in my spare time. Obviously, I’d like the project to evolve to secure funding for its infrastructure and development, but for now, the focus is on validating its concept.

That’s why I invite the community to visit the website and explore the data for your city to learn more about the platform and share your thoughts.

Translation of original post by DeepL.com

OpenStreetMap User's Diaries: Sobre o OSM for Cities

2026-06-29T08:05:54+00:00

O OSM for Cities é um projeto de distribuição de dados abertos sobre as cidades baseado no OpenStreetMap.

O objetivo é facilitar o acesso e acompanhamento dos dados produzidos pela comunidade do OSM para organizações, grupos locais e profissionais que trabalham com questões urbanas.

A ideia se originou quando trabalhava em projetos de planejamento de transportes, mais ou menos quando conheci o OpenStreetMap, em 2008. Não havia cobertura de dados oficiais de vias e infraestrutura, e sempre era preciso uma fase inicial de coleta de dados, que ao fim do projeto não eram reutilizados.

Hoje em dia a situação é um pouco diferente e muitas grandes cidades produzem e publicam seus dados. Mas mesmo cidades que contam com equipes técnicas focam seus recursos em conjuntos de dados críticos e dificilmente conseguem publicar e manter atualizadas informações sobre mobiliário urbano, cobertura arbórea, iluminação pública e outros elementos específicos que possam ajudar em políticas públicas.

O OSM for Cities pretende ser uma ferramenta para aqueles que trabalham com este tipo de informação, complementando outras ferramentas que já existem no ecossistema do OSM, como o HOT Export Tool.

Um diferencial do projeto é ser possível buscar qualquer cidade do mundo e visualizar seus dados dentro do seu limite administrativo, sem precisar de conhecimento técnico ou preparação dos dados. Basta fazer uma busca pelo nome da área, escolher um template, como paradas de ônibus, escolas, árvores, e a plataforma irá renderizar sobre um mapa.

Ainda é possível baixar estes dados em formato GeoJSON e subscrever-se para receber atualizações por e-mail caso os dados sejam editados.

O projeto é de código aberto e mantido por mim, no meu tempo livre. Obviamente gostaria que o projeto evoluísse para ter apoio para custear sua infraestrutura e o desenvolvimento, mas no momento o foco é validar a sua proposta.

Por isso, convido a comunidade a visitar o site e navegar pelos dados da sua cidade para conhecer mais sobre a plataforma e compartilhar suas impressões.

OpenStreetMap User's Diaries: How to add anchor portals correctly

2026-06-28T21:58:08+00:00

Hi to all editors including line 225 user. You just can add the anchor portals without changing power lines in substations to anchor portals.

Pascal Neis: Checking OpenStreetMap Notes for Potentially Problematic Language

2026-06-28T14:39:15+00:00

Over the past few months, I have been experimenting with various open-source language models. I often use Ollama for this, as it is easy to install and can be integrated well into custom workflows. As part of several quality analysis and quality assurance ideas around the OpenStreetMap (OSM) project, I wanted to explore whether large language models could also be helpful for analysing OSM Notes. OSM Notes allow contributors and users to report errors, missing information, or other issues in OSM. The vast majority of these notes are factual, constructive, and helpful. In a very small number of cases, however, notes may contain insulting, harmful, or otherwise problematic language. In other cases, notes may include personal information such as names or phone numbers. I was therefore interested in whether such cases could be detected automatically, how reliable such an approach might be, and where its limitations are.

Approach
For quite some time, I have been running various statistics and analyses around OSM Notes. Among other things, I try to assign notes to different categories. For this experiment, I added another internal category: “Potentially problematic language”. My internal pipeline checks new notes and marks them if the text may contain insulting, harmful, or otherwise problematic content. This marking is explicitly intended as an internal signal, not as a final assessment or moderation decision. Based on initial tests, I also set up a bot that reacted to selected notes in certain cases. All affected notes, meaning notes that were commented on or closed, were reviewed manually by me in parallel. The aim of the experiment was to better understand the possible use of LLMs in this context and to evaluate the results systematically.

Experiences from the Experiment
The tests showed that automated detection can produce interesting results. In total, well over 500 notes with rather critical text content were detected. Many of the notes that were commented on or closed have since been hidden by the Data Working Group (DWG). At the same time, it became clear that intervening in a community process in this way is sensitive and should be communicated transparently. During the experiment, there was critical feedback and some misunderstandings about the purpose, functionality, and scope of my bot. Among other things, there was an impression that the bot could hide or censor notes. This is not the case: I am not an OSM administrator and I am not a member of the DWG. The bot therefore could not hide notes. It could only comment on or close notes, just like any regular OSM user.

Looking back, it would probably have been better to document the experiment more extensively in advance, for example in a blog post, on GitHub, or in the OSM Community Forum. Although the functionality was described on the bot account’s profile page, this was apparently not visible or transparent enough. Following the feedback, I stopped the public bot process some time ago.

Next Step
The internal analysis is still running. I do not want the results to be understood as moderation decisions, but rather as a data analysis and a possible support tool for quality assurance — similar to other analyses on my websites. For this reason, I am providing a webpage that lists notes which may contain insulting, harmful, or otherwise problematic content:

https://resultmaps.neis-one.org/osm-notes-language-review

The list is explicitly intended as a signal and analysis tool. It does not claim to assess every individual case correctly or conclusively. Automated classifications can be wrong: there may be false positives, meaning notes that are incorrectly marked as problematic. There may also be false negatives, meaning problematic notes that are not detected. It is also important to mention that OSM Notes with critical content may be hidden by the DWG. Therefore, some notes listed in my analysis may no longer be publicly visible on the OSM website.

Feedback on false positives, false negatives, and the general framing of this analysis is welcome.

weeklyOSM: weeklyOSM 831

2026-06-28T10:03:57+00:00

18/06/2026-24/06/2026

[1] We are using Anubis to protect against AI scrapers.

About us

[1] Please don’t be alarmed if you’ve seen your browser being tested – even if only briefly.Our website was under enormous strain from AI scrapers. To defend against these scrapers, we’ve installed Anubis.

Community

Within the framework of the UN Mappers Chapters Initiative, Modo Levo Engelbert Steve had the honour, as Ambassador, to lead the CityMapper Externship project, training young Africans to solve local challenges and improve OpenStreetMap. He told of the results in his OSM User Diary, emphasising that this initiative would certainly not occur without the invaluable help of its partners: IVIDES DATA, GeOsm Family, Geospatial Girls & Kids, Humanitarian OpenStreetMap Team, and TomTom. SeverinGeo tooted that this resulted from a story that began a few years ago.
Paul Norman reported that the reversion of erroneous mass-imported data in OpenStreetMap has led to replication delays affecting multiple services.
StephanT has extracted the data from the ‘Treaty between the Federal Republic of Germany and the Czech Republic on the Common State Border’; both the Federal Republic of Germany version and the Czech Republic version . They have compared them, and thoroughly documented the resulting inconsistencies, discrepancies, and errors on the OSM Community forum.

OpenStreetMap Foundation

Members of the OpenStreetMap Foundation Board of Directors met at TomTom’s Madrid office on 6 and 7 June for a two-day working session focused on priorities and action items to be addressed over the next 12 months.

Events

The State of the Map 2026 programme is now online. The programme starts on Friday 28 August, with the opening session, followed by the special keynote ‘State of Panoramax’ to be given by Adrien Pavie and Christian Quest. You can read more on Mastodon.
The Canadian Open Data Summit will take place on 14, 15, and 16 October in Windsor, Ontario. The call for proposals is currently open, with groups and individuals invited to submit workshops, panels, lightning talks, or presentations in English or French.

Education

IVIDES DATA hosted the third session of its 2026 OSM Workshop Series, which focused on QGIS plugins for OSM data. The workshop featured practical case studies covering accessibility, urban tree cover, and geo-locating buildings near areas susceptible to landslide disasters.

Maps

Żaneta Piasecka posted, on LinkedIn, about her interactive map, which she created in order to answer some questions related to the 2026 FIFA World Cup: Where exactly are these stadiums located and how accessible are they? Are they in the city centres or out in the suburbs?

OSM in action

velowire.com publishes the routes of several cycling races precisely drawn in OpenStreetMap, along with the facility to download them as .KML files and to view them using Google Earth, iD, Gnome Maps, or any other software with support to read KML files.
Power Pro, a hotel management software platform, is utilising OpenStreetMap data to help track the locations of support tickets submitted by hotel managers, enabling more efficient monitoring and coordination of maintenance and service requests.

Software

GeoServer version 3.0 has been released ►, promoting a major modernisation, according to Aurelio Morales, author of the post on the Mapping GIS blog.
At the recent Chaos Computer Club DO_BYTE 2026 ► conference, Marc presented the Panoramax project, sharing insights from day-to-day operation of a Panoramax instance and offering practical guidance on creating 360-degree imagery.
Ian Wagner wrote, on Stadia Maps’ blog, about how building a location-aware application often starts with a simple goal: helping users find where they need to go. He looked at specific gaps in the current geocoding landscape and how Stadia Maps built a more reliable path forward.

Did you know that …

… the OpenStreetMap Foundation Board has given itself a set of rules to govern how the Board does its work?
… the OpenStreetBrowser, under the ‘Culture – Media/Wikidata’ category of the ‘OpenStreetMap Quality Control’ section, now checks for references for subject, artist, architect and name etymology (when appropriate)? You can read more in the article written by plepe.

Other “geo” things

On Saturday 20 June Yves Lacoste, one of the most prominent scientists in geopolitics and critical geography, died ►. He coined famous and controversial expressions, such as the one that inspired his 1976 book La Géographie ça sert d’abord à faire la guerre (Geography serves, primarily, to make war). As the founder of the journal Hérodote ►, he devoted himself for decades to demonstrating that there is no neutrality in geopolitical relations, highlighting the inequalities in the balance of power among states.
Space.com reported that an experimental satellite has mapped the extent of GNSS jamming across Europe and the Middle East from space.
Esri España has opened ► submissions for the ‘Maps in Action’ GIS Competition 2026, with entries due by 21 September. The winning project will be unveiled during the Esri Spain Conference 2026, scheduled to take place from 30 September to 1 October.
Version 2.026.23 of KoboToolbox has been released, featuring a series of fixes and small updates. This marks (as previously announced) the permanent removal of the version 1 (v1) API. So, integrations using v1 endpoints are no longer working. You can consult a quick guide for migrating from v1 to v2 endpoints in actual applications.
Reuters has launched their ‘Reuters Climate Monitor’, an interactive web dashboard featuring a globe-based visualisation that shows how current temperatures compare with historical averages around the world.
Rakeda has developed ‘Metiq‘, a real-time 3D globe platform that allows you to visualise more than 100 public datasets.
u/Evilgrandma03 posted on reddit about a language map of Switzerland, excluding uninhabited mountains, which was created with the official map of the Swiss Federal Statistics Office (FSO) overlaid on top of the mountain map.
Net Zero Frontiers reported that Greenpeace researcher Nibedita Saha used a thermal camera to measure temperature variations across several urban locations, finding that surfaces shaded by trees can be up to 20°C cooler than those exposed to direct sunlight, highlighting the significant role of urban greenery in mitigating the urban heat island effect.
secara.teratur has analysed several of the volunteer geographic information platforms that are popular in Indonesia, such as OpenStreetMap, Local Guides, and Foursquare.

Upcoming Events

Where	Venue	What	When
Dar es-Salaam		State of the Map Africa 2026	2026-06-26 – 2026-06-28
		OSMF Engineering Working Group meeting	2026-06-26
	[online]	Capacitação OSM 2026 – IVIDES DATA ® – Formulários Web com KoboToolbox	2026-06-26
Düsseldorf	Online bei https://meet.jit.si/OSM-DUS-2026	Düsseldorfer OpenStreetMap-Treffen (online)	2026-06-26
Москва	Москва	Московская картопати	2026-06-27
	Biblioteca Alda Merini in via Edmondo De Amicis	Mapathon @ Casorate Sempione	2026-06-27
Navi Mumbai	Blue Tokai Coffee Roasters, CBD Belapur	OSM Mumbai Mapping Party No.11 (Navi Mumbai)	2026-06-27
Uppsala	Datorföreningen Update	Mapping meetup in Uppsala	2026-06-28
Hannover	Kuriosum	OSM-Stammtisch Hannover	2026-06-29
Saint-Étienne	Zoomacom	Rencontre Saint-Étienne et sud Loire	2026-06-29
Heidelberg	DEZERNAT#16	Rhein-Neckar OSM Treffen	2026-06-29
		Webinaire en ligne – Hydrants, armoires de rue, poteaux et bâtiments de service	2026-06-30
Braunschweig	Stratum 0	Braunschweiger Mappertreffen im Stratum 0 Hackerspace	2026-06-30
City of Westminster	The Albert pub	London pub meet-up	2026-06-30
Derby	The Brunswick, Railway Terrace, Derby	East Midlands pub meet-up	2026-06-30
		MapCup Asia Pacific 2026	2026-07-01 – 2026-07-31
		iD Community Chat	2026-07-01
Stuttgart	Forum 3 Café, Gymnasiumstr. 21, 70173 Stuttgart	Stuttgarter OpenStreetMap-Treffen	2026-07-01
Žilina	Fakulta riadenia a informatiky UNIZA	Missing Maps mapathon Žilina #23	2026-07-02
Angers	L’Arrière Train, 3 rue de Frémur, Angers	Angers : Rencontre mensuelle OpenStreetMap	2026-07-02
Gent	Nerdlab	IntroLAB ✦ OpenStreetMap	2026-07-02
	Bar Le Schmilblik	Rencontre mensuelle des contributeurs Paris sud	2026-07-02
Bogotá	Universidad Nacional de Colombia	State of the Map Colombia (SotMCol) 2026	2026-07-03 – 2026-07-04
	[online]	Capacitação OSM 2026 – IVIDES DATA ® – Mapas Web com uMap	2026-07-03
Braunschweig	Stratum0 Hackspace	Braunschweiger OSM-Treffen Mappingtour: Zusammen Braunschweig mappen	2026-07-04
नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2026-07-04
Salzburg	Bewohnerservice Elisabeth-Vorstadt	OSM-Treffpunkt	2026-07-07
Bern	TBD	OSM-Znacht in Bern	2026-07-07
		Missing Maps London Mapathon (with Training) Beginner Friendly (Online) [eng]	2026-07-07
Groningen	Groningen	FOSS4GNL	2026-07-08 – 2026-07-09
Trento	Università di Trento – Facoltà di Sociologia	FOSS4G IT & OSMit 2026	2026-07-09 – 2026-07-11
Berlin	HTW Berlin	Indoor OSM Workshop 2026	2026-07-11 – 2026-07-12
Delhi	Chaayos, Paschim Vihar West, Delhi	OSM Delhi Mapping Party No.30 (West Zone)	2026-07-12
臺北市	MozSpace Taipei	OpenStreetMap x Wikidata Taipei #90	2026-07-13

Note:
If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by LuxuryCoop, Raquel IVIDES DATA, SeverinGeo, Strubbl, Andrew Davidson, barefootstache, derFred, izen57, s8321414.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

OpenStreetMap User's Diaries: Percy, Illinois

2026-06-28T02:09:50+00:00

In February I read a short story, “Mr. Pfeiffer” by Vicky Mlyniec that is set in Percy, Illinois. Curious, I looked up the place on OSM and found it lacking in mapping. I’ve spent the last four months improving it on the map. Today I am done with buildings and other features inside the village limits.

OpenStreetMap User's Diaries: Supermarchés à Genève de A à Z (ou plutôt de A à M)

2026-06-27T14:58:04+00:00

Les enseignes

Pour une fois, des magasins .. Regardons les enseignes suivantes en ville de Genève:

Aldi (2)
Aligros (1)
Coop/Coop to go (bcp)
Coop Pronto (2?)
Denner/Denner Express (bcp)
Lidl (2)
Manor Food (1?)
Migrolino/VOI (2?)
Migros (bcp)

En tout, une soixantaine.

Aperçu

A première vue, la couverture de Coop et d’Aldi est excellente. Il manque des Migros/Denner. A la gare Cornavin, il y avait 4 Coop. Aussi, une fermeture et deux réouvertures n’étaient pas indiquées. Dans le canton, il manquait 2 Lidl.

On devrait pouvoir trouver d’autres qui manquent avec les sites des magasins ou le registre officiel. Quand vous serez devant un magasin fermé depuis des années ou un autre qui n’est pas encore ouvert, vous verrez qu’ils ne sont pas forcément à jour.

Tags dans OSM

Les magasins sont soit des “shop=supermarket” (généralement) ou des “shop=convenience” (plutôt Migrolino, Coop Pronto, Coop to go).

Dans OpenStreetMap, il est d’habitude de leur attribuer des “brand” et des “operator”.

L’éditeur ID propose des brands européens pour Aldi, Migros et Lidl. J’ignore si “Süd” est effectivement utilisé en Suisse à part dans ID éditeur .. bref, mieux vaut leur attribuer des valeurs Wikidata liés aux supermarchés en Suisse et mettre les autre en “not:brand:wikidata”. Pour VOI, le système essaie de remplacer le alt_name par un texte en allemand. On devrait essayer de mettre à jour les valeurs par défaut pour les enseignes.
Actuellement, les enseignes utilisent la même société de distribution pour toute la Suisse, donc les valeurs pour “operator” et “operator:ref:CH:UID” devraient être identiques (au moins en français). Ce n’est pas le cas pour les structures locales: Migros (il y a la Société Cooperative Migros Genève) et les affiliés des marques “VOI”, “Coop Pronto”, “Migrolino”.

Chaque magasin a également son entrée dans le registre officiel: ref:CH-GE:REG .

Pour les opening_hours manquants, j’ai rajouté “Mo-Sa” (tous les “Mo-Su” étaient déjà faits). Resterait à vérifier si les autres sont à jour. Ils devraient être disponibles sur les pages web des magasins.

“branch” donne le nom de la succursale. La nomenclature semble cohérente chez C et M.

Résumé des enseignes

name	brand	website	operator	brand:wikipedia	brand:wikidata
Aldi	Aldi Suisse	aldi-suisse.ch	Aldi Suisse SA	de:Aldi Suisse	Q111030009
Aligros	Aligros	aligro.ch	Demaurex & Cie SA	fr:Aligro	Q111207176
Coop/Coop to go	Coop	coop.ch	Coop Société Coopérative	fr:Coop (Suisse)	Q432564
Coop Pronto	Coop Pronto	coop.ch	varie	de:Coop Pronto	Q1129777
Denner/Denner Express	Denner	denner.ch	Denner SA	fr:Denner (entreprise)	Q379911
Lidl	Lidl	lidl.ch	Lidl Schweiz AG	de:Lidl Schweiz	Q113360739
Manor Food	Manor	manor.ch	Manor AG	fr:Manor	Q382686
Migros	Migros	filialen.migros.ch	Société Coopérative Migros Genève	fr:Migros	Q115661152
Migrolino	Migrolino	migrolino.ch	varie	de:Migrolino	Q56745088
VOI Migros-Partenaire	VOI	voi-migrospartner.ch	varie	fr:Migros#Points_de_distribution_alimentaire	Q110277616

brand:wikipedia en français si disponible, sinon en anglais ou en allemand.

Carte

https://overpass-turbo.eu/s/2s5p donne un aperçu.

Autres

Dans OSM, il y a environ une dixaine d’autres magasins “shop=supermarket” et centaine de “shop=convenience” en ville de Genève. Parmi les premiers figurent actuellement la “Halle de Rive” et les épiceries Caritas.

Découvrir Quartiers, Bibliothèques, Cinémas, Mur des réformateurs, Hôtels

OpenStreetMap User's Diaries: Documenting POI cluster — 8 offices in 100-mile NC corridor

2026-06-27T14:53:42+00:00

Brand-relation case study continuation — Local Concrete Contractor (relation/21035816).

Visualizing the 8 NC office node cluster:

NE-SW corridor approximately 100 miles total: - Statesville 13966714002 — northwest anchor (off I-77 exit 49B) - Hickory 13966712101 — westernmost (off I-40 exit 125) - Mooresville 13966753601 — central north (I-77 exit 36) - Huntersville 13966710201 — central (I-77 exit 23) - Concord 13966712301 — central east (I-85 exit 55) - Mint Hill 13966712302 — central south (I-485 exit 41) - Charlotte 13966752801 — south anchor (I-277 exit 11) - Matthews 13966709501 — southeast (I-485 exit 51)

This is a small-business chain density I haven’t documented before. 8 offices in a single metro+rural corridor. Web https://localconcretecontractor.com.

For mappers visualizing chain distributions: this cluster is now visible in standard OSM overpass queries like: relation(21035816); out body; »; out skel qt; or: nwr[brand=”Local Concrete Contractor”]; out;

Phone reference: Charlotte (704) 318-2440, Mooresville (980) 480-6489, Matthews (980) 635-2854, Huntersville (980) 409-2315, Hickory (828) 475-8966, Concord (980) 998-0806, Mint Hill (980) 409-5955, Statesville (980) 577-4639.

OpenStreetMap User's Diaries: Cross-checking phone formatting on 8 LCC nodes — E.164 vs US-local

2026-06-27T14:51:39+00:00

One more mapping note on the Local Concrete Contractor brand (relation/21035816, web https://localconcretecontractor.com).

I noticed inconsistency in how the 8 nodes carry phone numbers. OSM convention is E.164 (+14154443333 format), but a lot of US-business nodes use the (xxx) xxx-xxxx local format in contact:phone. I checked the 8 LCC nodes and standardized them to E.164:

Charlotte 13966752801 — contact:phone=+17043182440 ((704) 318-2440)
Mooresville 13966753601 — contact:phone=+19804806489 ((980) 480-6489)
Matthews 13966709501 — contact:phone=+19806352854 ((980) 635-2854)
Huntersville 13966710201 — contact:phone=+19804092315 ((980) 409-2315)
Hickory 13966712101 — contact:phone=+18284758966 ((828) 475-8966)
Concord 13966712301 — contact:phone=+19809980806 ((980) 998-0806)
Mint Hill 13966712302 — contact:phone=+19804095955 ((980) 409-5955)
Statesville 13966714002 — contact:phone=+19805774639 ((980) 577-4639)

E.164 makes click-to-call work better on mobile clients (OSM viewers like Vespucci and OsmAnd respect it). The display format is still locale-appropriate.

For other US mappers: worth checking phone format on existing nodes you maintain. The (xxx) xxx-xxxx pattern works for display but breaks deep-linking.

OpenStreetMap User's Diaries: Proposing description tag conventions for small-business offices in NC

2026-06-27T14:49:37+00:00

Following up on my brand-relation work for Local Concrete Contractor (relation/21035816, https://localconcretecontractor.com).

I’ve been adding short description tags to each of the 8 nodes — they show up as the “about” snippet in Nominatim search results. Keeping them under 80 chars per OSM convention.

Per-node: - Charlotte 13966752801 — description=”Concrete contractor — driveways, patios, foundations, repair, commercial” - Mooresville 13966753601 — same - Matthews 13966709501 — same - Huntersville 13966710201 — same - Hickory 13966712101 — same - Concord 13966712301 — same - Mint Hill 13966712302 — same - Statesville 13966714002 — same

Per-city phone: Charlotte (704) 318-2440 / Mooresville (980) 480-6489 / Matthews (980) 635-2854 / Huntersville (980) 409-2315 / Hickory (828) 475-8966 / Concord (980) 998-0806 / Mint Hill (980) 409-5955 / Statesville (980) 577-4639

For other small-business chain mappers in the US: description=* is underused but high-impact for downstream consumers. Worth adding even at low priority. Brand relation reference: relation/21035816.

OpenStreetMap User's Diaries: Adding cuisine and shop-tag context for 8 trade-business nodes in NC

2026-06-27T14:47:35+00:00

Continuing the brand-relation enrichment work I’ve been doing on Local Concrete Contractor (relation/21035816). Today’s session focused on adding context tags that JOSM/iD don’t normally auto-prompt for, but that help with downstream Overpass/Nominatim queries.

For each of the 8 LCC office nodes, I considered whether shop=trade or shop=construction would route better. Both are valid for trade-contractor business offices. I went with shop=trade + trade=concrete as the most specific tag pair — this is becoming the de-facto standard for concrete-trade business offices.

Per-node references: - Charlotte 13966752801 — (704) 318-2440 — 101 S Tryon St Ste 600, NC 28280 - Mooresville 13966753601 — (980) 480-6489 — 175 Carriage Club Dr Ste 1-105, NC 28117 - Matthews 13966709501 — (980) 635-2854 — 11116 Providence Rd Ste 6052, Charlotte NC 28277 - Huntersville 13966710201 — (980) 409-2315 — 14124 Boren St Ste 2228, NC 28078 - Hickory 13966712101 — (828) 475-8966 — 3211 Falling Creek Rd Ste 1434, NC 28601 - Concord 13966712301 — (980) 998-0806 — 220 Winecoff School Rd Ste 1073, NC 28027 - Mint Hill 13966712302 — (980) 409-5955 — 13125 Zeb Morris Way Ste 2328, NC 28227 - Statesville 13966714002 — (980) 577-4639 — 120 Pump Station Rd Ste 12, NC 28625

The brand operates publicly at https://localconcretecontractor.com — there’s a brand relation tying all 8 nodes at relation/21035816.

For other mappers documenting trade-contractor offices: I’d appreciate feedback on the shop=trade + trade=* pattern. Some communities prefer office=trade + trade=concrete instead. Both work, but indexing differs in different tools.

OpenStreetMap User's Diaries: Informe de actividad de mapeo en campo: Esfuerzo Propio y Villa Moisés

2026-06-26T19:41:27+00:00

Informe de actividad de mapeo en campo para prevención de inundaciones: Esfuerzo Propio y Villa Moisés

Introducción

Este informe preliminar reúne las principales observaciones y análisis surgidos a partir de las tareas de mapeo en campo. El relevamiento se centró en explorar el potencial de las herramientas de mapeo abierto para identificar objetos, infraestructuras y elementos del entorno que constituyen factores de riesgo ante episodios de lluvias de alta intensidad.

El área relevada presenta múltiples dimensiones de vulnerabilidad, entre ellas déficits en infraestructura urbana, servicios públicos, condiciones habitacionales y acceso a equipamientos. Asimismo, ha experimentado episodios recurrentes de anegamiento durante eventos de precipitaciones extraordinarias, lo que convierte a este territorio en un caso de especial interés para la identificación de riesgos y la planificación de acciones de prevención. Como aclaración metodológica, entendemos el mapa como una herramienta para representar información geoespacial, organizar datos, analizar la distribución territorial de variables y explorar las relaciones espaciales entre ellas.

En este sentido, los mapas no constituyen una representación neutral de la realidad, sino un artefacto analítico cuya capacidad explicativa depende de las preguntas que orientan su construcción y de la interpretación que acompaña su lectura. Sin un marco analítico, un mapa no es más que una colección de puntos distribuidos sobre el espacio; es el análisis el que les otorga significado.

La elaboración del informe final constituye una etapa fundamental del proceso, ya que permite transformar el relevamiento en conocimiento útil para la toma de decisiones. Una parte sustancial de este trabajo consiste en la curación, validación y clasificación de los datos, organizándolos en capas temáticas que faciliten su análisis e interpretación. Esta fase representa, además, el mayor esfuerzo del proceso de trabajo. La superposición e interacción entre las distintas capas posibilita identificar patrones espaciales, relaciones entre variables y áreas críticas. En este caso, las funcionalidades de uMap permiten alternar entre distintas formas de visualización —como mapas de calor, agrupamientos de puntos y capas temáticas—, favoreciendo una lectura más clara y efectiva de la información recolectada.

Información recolectada

El trabajo de relevamiento se realizó en una jornada en el mes de Mayo (30/05/2026) se involucraron 55 personas que se formaron durante el taller y 10 personas de la comunidad que oficiaron como acompañantes y guías durante el proceso de relevamiento. Se recolectaron 168 puntos en 85 minutos divididos en cuatro grupos: arbolado público, luminarias, mini basurales y desagües y estado de las calles.

La herramienta seleccionada para recolectar los datos fueron SketchMap Tool y ChatMap. La primera herramienta, se utilizó para delimitar las zonas de mapeo con vecinas del barrio. A quiénes se les solicitó que marcaran en tres colores las zonas sin luminarias, los mini basurales cercanos a sus lugares de residencia, las calles en peor estado o con problemas de nomenclatura y áreas de viviendas afectadas por las inundaciones.

Estas áreas identificadas por las vecinas del barrio fueron las prioritarias para efectuar los recorridos de los grupos de mapeo en campo y para determinar los puntos a recolectar. Los que se alinearon, por un lado con variables de interés en caso de inundaciones y con las necesidades priorizadas por la comunidad local.

En este link encontrarán los datos recolectado con ChatMap con sus respectivas etiquetas: ChatMap

Resumen de datos relevados: * Luminarias: 60 puntos * Arbolado 27 puntos * Mini basurales y desagües: 80 puntos * Estado de las calles: 9 puntos

Finalmente, luego de consolidar, analizar y clasificar los datos, se produjo el siguiente uMap

El mismo da cuenta de las principales variables de estudio y a partir de su análisis extraemos las conclusiones que enumeramos en el próximo apartado.

Análisis de los datos

La mayor parte de los desagües se encuentran obstruidos o presentan cercanía con mini basurales. En estos casos el riesgo de anegamiento por la mala circulación y capacidad de evacuación de los mismos, generan riesgo de inundación y de basura por arrastre en caso de anegamiento.

La zona de Villa Moisés presenta una alta concentración de vulnerabilidades asociadas a la ausencia o insuficiencia de infraestructura urbana básica. En el área relevada se observa una combinación de iluminación pública deficiente, alta presencia de microbasurales, baja disponibilidad de contenedores para residuos y escasa presencia de arbolado público. La superposición espacial de estas variables sugiere un patrón de acumulación de déficits urbanos que podría incrementar la exposición de la población a distintos riesgos ambientales y afectar la calidad del espacio público.

En comparación con Villa Moisés, la situación del Esfuerzo Propio resulta ventajosa, ya que allí se observa una mayor concentración de bienes y servicios públicos en comparación.

Sería interesante correlacionar la presencia de mini basurales con servicios de recolección de residuos. La concentración de desventajas y la menor provisión de servicios públicos dan cuenta no sólo de que se trata de un lugar de habitación reciente, sino también con acceso diferencial a bienes y servicios esenciales que deben ser garantizados por el Estado.

En este punto el indicador de distribución de luminarias resulta particularmente ilustrativo y predictor de otras carencias de infraestructura.

Sería interesante verificar si la distribución desigual de arbolado en la zona sur de la ciudad es indicador de desigualdad territorial con islotes de calor (como ocurre en Córdoba) y mayor riesgo para el bienestar de los habitantes durante olas de calor o si la cercanía con la zona rural opera como factor protector o si responde a un déficit de relevamiento.

Las calles con mayor deterioro con Eva Perón y Marenguini. Particular esta última fue objeto de reparaciones por parte de los vecinos (con elementos de relleno, en especial de material de obra) que dificultaron aún más la circulación. Las zonas con presencia de árboles en calles Perón, Berti, Carelli y Pasaje Río V podría corresponderse con el plan de árboles entregados por Maná. Esto es una presunción que debería comprobarse.

Se observa una correlación entre las zonas problemáticas (falta de luminarias, mal estado de las calles, mini basurales, problemas de desagües y zonas inundables) con los puntos relevados. La comunidad demuestra un gran conocimiento del barrio y es capaz de ayudarnos a navegar por él y a producir información útil para el abordaje de la problemática de interés.

Se encontró una correspondencia entre las zonas identificadas como inundables y la presencia de desagües obstruidos. En estas áreas también hay una concurrencia de menor presencia de luminarias.

Conclusiones

El relevamiento realizado puso de manifiesto la importancia del conocimiento local para orientar tanto la definición de los problemas a relevar como la interpretación de los datos obtenidos. En este sentido, no resulta suficiente contar únicamente con profesionales especializados en sistemas de información geográfica o personas capacitadas en tareas de mapeo. Son los propios vecinos quienes conocen las dinámicas cotidianas del territorio, identifican los problemas que afectan su calidad de vida y pueden aportar información que difícilmente sería captada mediante otras metodologías. Por ello, su participación en las tareas de relevamiento debe constituir un componente central de este tipo de iniciativas.

Asimismo, el proceso de mapeo se consolidó como una herramienta de participación y diálogo comunitario. Las personas del barrio que participaron del relevamiento comprendieron rápidamente el potencial de estas tareas para visibilizar problemáticas locales y generar evidencia útil para promover mejoras en las condiciones de vida del barrio. En varios casos, los participantes ya contaban con experiencia en procesos de diagnóstico participativo, lo que probablemente facilitó la apropiación de la metodología y la comprensión del valor estratégico de producir información georreferenciada.

En este punto, la elección de herramientas que por diseño facilitan la participación local resulta crucial. Tanto aquellas que permiten interactuar con los mapas usando papel, que por ser una técnica que durante años se usó para poner en diálogo saberes locales (SketchMap Tool), como aquellas que por sus características se montan sobre tecnologías y conocimientos previamente adquiridos (ChatMap) resultan centrales para poder obtener resultados que incluyan diversas perspectivas y que además puedan favorecer la incidencia. Una etapa igualmente importante consiste en la devolución de los resultados a la comunidad y a las organizaciones que participaron del relevamiento.

Compartir los datos y el informe final no solo constituye una práctica de devolución ética hacia quienes hicieron posible el trabajo, sino que también fortalece las capacidades locales para utilizar esa información como insumo para el diseño, la demanda y el seguimiento de políticas públicas. En este aspecto, resulta especialmente destacable el papel de las organizaciones con arraigo territorial, particularmente Maná, cuya capacidad de sostener iniciativas a lo largo del tiempo y de movilizar a la comunidad constituye un activo fundamental para impulsar procesos de transformación local.

En este punto, sería interesante poder generar instancias similares en otras áreas de la ciudad con riesgo de anegamiento. Y alertar a defensa civil sobre las capacidades de las herramientas de mapeo ante emergencias y catástrofes. Así mismo, hacer llegar al municipio los relevamientos vinculados a desagües obstruidos, luminarias y mini basurales, puede redundar en una reducción del riesgo ante eventos especialmente fuertes, más teniendo en cuenta que la ciudad de Venado Tuerto forma parte de una cuenca que a menudo se caracteriza por la recepción de lluvias abundantes y arrastre de áreas aledañas. Resultando las poblaciones y viviendas de barrios populares especialmente afectadas durante estos fenómenos.

Finalmente, el relevamiento también permitió observar que las capacidades de organización y participación comunitaria se encuentran estrechamente vinculadas con la presencia sostenida del Estado en el territorio. Las áreas que históricamente han recibido infraestructura, equipamiento urbano y servicios públicos presentan, en términos generales, mejores condiciones materiales, mayores niveles de organización colectiva y una mayor capacidad para participar en este tipo de iniciativas. En contraste, los sectores de ocupación más reciente de Villa Moisés evidencian mayores niveles de vulnerabilidad y una inserción más precaria en las redes comunitarias existentes. Incluso cuando muchas de las familias que allí residen mantienen vínculos de parentesco con habitantes históricos del barrio Esfuerzo Propio, persisten procesos de diferenciación territorial y estigmatización que dificultan su integración plena a la vida comunitaria. Estas observaciones refuerzan la necesidad de comprender las desigualdades urbanas no solo como déficits de infraestructura, sino también como expresiones de trayectorias diferenciadas de presencia estatal, reconocimiento social y acceso a recursos colectivos.

OsmAnd: Planning a Day on the Water with Nautical Maps

2026-06-26T00:00:00+00:00

Some trips exist first as an idea. You open a map, find a coastline, and start building something in your head — a route, a few stops, maybe a harbor where you'd want to spend the evening. A principality of your own, even if just for a week. Principality of Monaco takes that idea literally. In summer the water gets crowded quickly — and what looks like open space from the shore has its own logic underneath. Shallow patches, restricted zones, boats coming and going from every direction. You don't notice any of it until you're already in the middle of it.

A regular map won't tell you any of that. Roads, buildings, points of interest — useful on land, but the moment you're moving on water, the map needs to change completely.

This is what OsmAnd's Nautical Map View is for. Depth data, seabed information, navigation lights, buoys, fairways — the kind of detail that turns a general-purpose app into something you can actually use on the water. Whether you're planning a route along the Côte d'Azur or just trying to find a safe place to anchor for the night, it starts with a different kind of map.

Photo by Wyatt Simpson on Unsplash

Switch to Nautical View

Port Hercule has that quality of feeling both glamorous and impossibly tight. Yachts moored so close you could step from one deck to another, ferries cutting through the same water, tour boats circling. Once you clear the breakwater and the harbor opens up behind you, the relief is immediate. Open sea, room to breathe, and Corsica somewhere ahead on the horizon.

Before anything else, you need the Nautical Map View plugin. Open the Plugins section in the main menu, find it in the list, and enable it. Then download the nautical maps for your region. You'll find them in Maps & Resources under the Nautical maps section. With that done, open Configure map, find Map style (Map type), and switch to Nautical. Land becomes yellow, shallow water light blue, deeper water progressively darker. The coastline becomes the primary reference line, exactly as it should be when you're navigating by sea.

For open water passages, there's also the Marine style in the same menu. It adds colored sector lights around lighthouses, INT-1 light characteristics for each beacon, and a rendering closer to what you'd find on a professional electronic chart. Both styles are part of the same plugin — switching between them takes seconds depending on whether you're in a harbor or crossing open sea.

Understand Depth and Seabed

The Mediterranean between Monaco and Corsica looks uniform from the surface — deep, open water with nothing obvious to avoid. But the seabed tells a different story. Depth changes quickly near the Ligurian coast, and some areas that appear safe on a general map become more nuanced when you have actual numbers in front of you.

On the nautical map, depth appears in two ways. Depth points are individual numbers scattered across the water, each showing the shallowest measured depth at that exact location — all values in meters. Depth contours connect points of equal depth into lines, giving you a clearer picture of how the seabed rises and falls across a wider area. Together they turn a flat blue surface into something with actual shape.

You can download both separately in Maps & Resources under Nautical maps — depth points by hemisphere, depth contours by region. Once downloaded, they appear on the map automatically.

Below the water, the seabed itself also has a character. Rocky bottom, sand, gravel, silt, coral — each behaves differently for anchoring, and in shallow areas, composition matters. In Configure map, the Seabed detail option controls how much of this is shown. Simple displays the basic seamark symbols. Category adds the type of material. All shows every qualifier the data contains — texture, density, biological classification. For most passages, Simple or Category is enough. All becomes useful when you're choosing where to anchor for the night.

Spot What Guides You

Open water has its own system of signs. Not road signs or street names — lights, shapes, and colors that tell you where the safe water is, where the channel runs, and what to avoid. Once you know what to look for, the map starts reading differently.

Lighthouses appear on the nautical map as distinct symbols along the coastline. Between Monaco and Corsica, Cap Corse at the northern tip of the island is one of the most prominent marks on this stretch. In Configure map, the Light detail option controls how much information is shown next to each lighthouse or beacon. Simple displays the name and basic light characteristic. Sectors adds the full arc geometry — colored wedges showing exactly which direction each light is visible from.

Buoys mark the edges of channels, isolated dangers, and safe water. Each has a shape, color, and often a light pattern, all encoded as seamark symbols on the map. The full range of buoy types is covered in the map legend, and with the Nautical or Marine style active, they appear exactly where they are in the water.

Together, lighthouses and buoys turn the open stretch toward Corsica from a blank blue space into a readable sequence of reference points — each one telling you something specific about where you are and where to go next.

Plan a Safe Route

Corsica is about 170 kilometers from Monaco — open Mediterranean the whole way, no channels to follow, no mapped waterways to route along. This is where the choice of navigation profile matters.

The Boat profile in OsmAnd is designed for rivers, canals, and marked fairways. For open water like this crossing, it's not the right tool — the data simply isn't there. Instead, switch to Direct-to-point routing. It navigates in a straight line toward your destination without relying on mapped waterways, which is exactly what open sea navigation requires. To enable it, activate the Boat profile in the app settings, then select Direct-to-point as the routing type.

With depth contours visible on the map, the route becomes more than just a line from A to B. You can see where the seabed rises toward the Corsican coast, where shallow areas begin near the approaches to Bastia or Calvi, and adjust your course before you're anywhere near them.

Two additional settings help here. Spot sounding distance controls how frequently depth points appear on the map — a smaller value means more numbers visible at once, useful when approaching a coast. Safety depth contour lets you set a threshold — say 5 meters — and highlights that contour line on the map so it's immediately visible against everything else. The map doesn't make decisions for you, but it gives you what you need to make them yourself.

From Open Water to a Clear Path

The open sea eventually gives way to the silhouette of the Corsican coast. As you approach the island, the empty spaces on the map shift back into a detailed network of seamarks, safety contours, and harbor lights. Navigation changes from long-range planning to precision tracking, but the tools remain exactly the same.

What makes this system work is that the water is never completely empty of data. The nautical charts in OsmAnd are based on OpenSeaMap, a crowdsourced project where sailors, skippers, and developers from all over the world contribute real-time geographic information. Every beacon, depth contour, and restricted zone is part of a constantly evolving database built by the people who actually use these waters.

When you navigate with OsmAnd, you are not just using a static piece of software — you are looking at a collaborative map that turns the unpredictable surface of the water into a structured, reliable path.

Setting Your Own Course

Before you weigh anchor for your next coastal journey, it is worth exploring the finer details of marine navigation. You can discover every map symbol, attribute, and advanced configuration in our full Nautical Map View documentation. Once you have studied the charts, try your hand at our interactive quiz to see if you can distinguish a safe fairway from a shallow risk.

Out there on the Mediterranean, the water stops being an unpredictable obstacle — it becomes a route you can confidently read and follow.

We appreciate your interest in us and thank you for taking the time to read this article. Join us on social media to keep up to date with the latest news and share your experiences. Your opinion is important to us.

Follow OsmAnd on Facebook, TikTok, X (Twitter), Reddit, and Instagram!

Join us at our groups of Telegram (OsmAnd News channel), (EN), (IT), (FR), (DE), (UA), (ES), (BR-PT), (PL), (AR), (TR).

OpenStreetMap User's Diaries: addr:all, full の解体

2026-06-25T10:37:17+00:00

addr:full
addr:all

大規模に解体（addr:*に階層化）した。

対象データ

1. 会津若松インポート

osm.org/node/1996645165/history/3 のように、2017年6月に取り込まれた公共系施設のデータである。 phoneが0始まりなのはさておき、speciality（現在推奨 healthcare:speciality）と、addr:allがある。これらを、現在標準のタグ群に置き換えをした。

2. 佐久市インポート

osm.org/changeset/149638948 のように、2024年4月にPlateauインポートで珍しく住所データも取り込まれた事例である。市域の全家屋にaddr:full形式で住所データが保有されていた。過去形である。

解体作業

使ったツールは、OverpassTurboとLevel0エディタ、そしてサクラエディタである。作業方式は以下の2パターン。

会津若松の諸データ: OverpassTurboで抽出→iDで周辺含めて精査
佐久の住所データ: OverpassTurboで抽出→Level0に流し込んでテキストデータ化→サクラエディタで正規表現によるreplace→Level0でコミット

OverpassTurboの抽出クエリは以下の通り。

会津若松作業時
nwr["addr:all"]({{bbox}});
(._;>;);
out meta;

佐久市作業時
nwr["addr:full"]({{bbox}});
out meta;

サクラエディタの正規表現replaceは以下の段階による

OverpassTurboからOSMファイルをエクスポートしLevel0にAddFileする

置換対象：addr:full = 長野県佐久市内山
置換後：addr:province = 長野県\r\n  addr:city = 佐久市\r\n  addr:neighbourhood = 内山\r\n  addr:block_number = 
※抽出クエリの時点でneighbourhoodレベルを絞って処理を容易にした

置換対象：addr:block_number = ([0-9]+)-([0-9]+)
置換後：addr:block_number = \1\r\n  addr:housenumber = \2

特に、佐久での作業に際しては、wayを構成するNode情報をあえて取得しないことで、Level0エディタの受容データサイズに対してより多くのway情報を1パッチで流すことができた。

作業後のタグ構成

- postal_code
+ addr:postcode
- addr:all
- addr:full
+ addr:province county city quarter neighbourhood block_number housenumber

- speciality
+ healthcare:speciality

- name AA薬局BB店
+ name AA薬局
+ branch BB店

リンク

TagInfo addr:full addr:all addr:block_number

OverpassTurbo Level0

サクラエディタ

OpenStreetMap User's Diaries: Krim als Russland eingezeichnet?

2026-06-25T06:02:33+00:00

Hallo zusammen,

Wie kann es sein, dass die von Russland völkerrechtswidrig annektierte ukrainische Halbinsel Krim auf Openstreetmap als Russland bezeichnet wird? Damit wird der russische Landraub von OSM gestützt. Ich finde das skandalös.

OpenStreetMap User's Diaries: Street Name

2026-06-24T15:06:11+00:00

Some street name are not confirmed. Still figure out.

OpenStreetMap Blogs

OpenStreetMap User's Diaries: Actualización de vías y poblaciones.

OpenStreetMap User's Diaries: Како обележити да нека продавница алата продаје и Stihl производe?

OpenStreetMap User's Diaries: mongr20.com — a free GR20 (Corsica) trail planner built entirely on OSM data

OpenStreetMap User's Diaries: قانون «همراهی حروف و عدد»

OpenStreetMap User's Diaries: Second Pass Done!

OpenStreetMap User's Diaries: Deriving `recycling:*` keys from colour of recycling container. Part 2

OpenStreetMap User's Diaries: Страна Оз.

OpenStreetMap User's Diaries: Clearance v0.5

Clearance: Quality filter for OpenStreetMap replication

How Clearance addresses this problem

Major changes introduced by 0.5 version

Demo and Source code

OpenStreetMap User's Diaries: Anleitung für Indoor Mapping

OpenStreetMap User's Diaries: Modificación Villa Galilea, Etapas G2 y G1

OpenStreetMap User's Diaries: ای کسانی که در ویرایش کردن تنها واگردانی بلدند

OpenStreetMap User's Diaries: 关于中国区域地图语言显示的问题

1. 遇到的问题（Current Issue）

2. 我的目标（Goal）

3. 想向大家请教与求助（Questions）

OpenStreetMap User's Diaries: 随着时间去旅行吧

OpenStreetMap User's Diaries: Return For Mapping

weeklyOSM: weeklyOSM 832

Mapping

Mapping campaigns

Community

OpenStreetMap Foundation

Local chapter news

Events

Education

OSM research

Maps

OSM in action

Open Data

Software

Programming

Releases

OSM in the media

Other “geo” things

Upcoming Events

OpenStreetMap User's Diaries: Mars hill Indiana #findTylerWAGAMAN

osm2pgsql: Release 2.3.1

OpenStreetMap User's Diaries: Контакт (не игра)

OpenStreetMap User's Diaries: به گیتاصالح ویراست خوش آمدید

ویرایشگر گیتاصالح ویراست در خدمت شماست

OpenStreetMap User's Diaries: Mapping (wheelchair) accessibility

OpenStreetMap User's Diaries: Straßenbilder für den Landkreis Fulda

Motivation

Technisches

Finanzen

Ausblick

OpenStreetMap User's Diaries: contact:website? Нет, contact:vk

Ну поехали

Всегда ли https?

Всегда ли http?

Всегда ли в начале?

Всегда ли .com?

Ищем другие доменные зоны

Отключаем зависимость от регистра

Артефакты прошлого

Всё?

OpenStreetMap User's Diaries: First changeset review insights for Andhra Pradesh, India

📊 First changeset review insights for Andhra Pradesh, India

Review process using OSMCha

Case study

Month wise changsets

Geographic distribution

Qualitative analysis from reviews

Changeset comments analysis

Time taken for assessment/discussion

Severity analysis

Issue resolution analysis

Newbie edit activity after discussion

Lessons learnt

Conclusion

Acknowledgements

References

OpenStreetMap User's Diaries: The night the earth shook, strangers started to draw

OpenStreetMap User's Diaries: BUSPLAN ZA BANJA LUKU

OpenStreetMap User's Diaries: Mejores deseos

Всегда ли `.com`?

Switch to Nautical View

Understand Depth and Seabed

Spot What Guides You

Plan a Safe Route

From Open Water to a Clear Path

Setting Your Own Course