close
Image Image Image
Style | StandardCards

OpenStreetMap Blogs

Tuesday, 07. July 2026

OpenStreetMap User's Diaries

Actualización de vías y poblaciones.

Martes 7 de Julio de 2026.

Se realizo:

  1. Se agrega etiqueta de Condominio Río Lircay, Barrio Los Pinares IV, se separa Los Pinares II y III.

  2. Se agrega nombres de calles en Los Pinares IV; Huircaleo, Cuminao, Huenchulaf, Huenupan, Calfumil, Kuden, Curiman, Namuncura, Felipe Camiroaga y Antilaf.

  3. Se corrige tramo de v

Martes 7 de Julio de 2026.

Se realizo:

  1. Se agrega etiqueta de Condominio Río Lircay, Barrio Los Pinares IV, se separa Los Pinares II y III.

  2. Se agrega nombres de calles en Los Pinares IV; Huircaleo, Cuminao, Huenchulaf, Huenupan, Calfumil, Kuden, Curiman, Namuncura, Felipe Camiroaga y Antilaf.

  3. 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.

  4. Se agrega nombres de calles en Los Pinares III; Calfupan, Caulín, Huenchelu, Eyetun, Kopahue, Inacayal, Llacantu, Felipe Camiroaga, Coyanco, Yafu, Malal.

  5. Se agrega nombres de calles en Los Pinares II; Lonco, Cuyen, Ela, Piren, Callen, Peuma.


Како обележити да нека продавница алата продаје и Stihl производe?

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

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

[1] community.openstreetmap.org/t/

Другар 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


mongr20.com — a free GR20 (Corsica) trail planner built entirely on OSM data

Last year I hiked the GR20 across Corsica, and afterwards I built a small non-commercial website around it: 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

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:

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.


قانون «همراهی حروف و عدد»

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

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


Second Pass Done!

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.

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.

Monday, 06. July 2026

OpenStreetMap User's Diaries

Deriving `recycling:*` keys from colour of recycling container. Part 2

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 packagi

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.

Colours used for waste bins across the EU, 2023 survey 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.


Страна Оз.

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

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

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

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

  • «оз. Белое» на «Белое озеро»
  • «оз. Пятницкие» на «Пятницкие озёра»
  • «оз.Бол.Захарьевское» на «Боль

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

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);

И получаем:

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

‿( ́ ̵ _- ` )‿


Clearance v0.5

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 ru

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


Anleitung für Indoor Mapping

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 Te

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


Modificación Villa Galilea, Etapas G2 y G1

Viernes 3 de Julio de 2026.

Se realizo:

  1. Modificación de ejes de calles en Villa Galilea G2 y G1 en base al mapa de ESRI.

  2. Se agrego etiqueta de población por ambas etapas.

  3. Se agrego nombre de calle; Santa Clara de Asis.

Viernes 3 de Julio de 2026.

Se realizo:

  1. Modificación de ejes de calles en Villa Galilea G2 y G1 en base al mapa de ESRI.

  2. Se agrego etiqueta de población por ambas etapas.

  3. Se agrego nombre de calle; Santa Clara de Asis.


ای کسانی که در ویرایش کردن تنها واگردانی بلدند

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

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


关于中国区域地图语言显示的问题

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

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

1. 遇到的问题(Current Issue)

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

2. 我的目标(Goal)

我想实现中国境内(至少是主要城市如北京、上海、广州等)的底层街道和主要地理要素能够尽可能

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

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

1. 遇到的问题(Current Issue)

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

2. 我的目标(Goal)

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

3. 想向大家请教与求助(Questions)

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

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


随着时间去旅行吧

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

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

Sunday, 05. July 2026

OpenStreetMap User's Diaries

Return For Mapping

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 res

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

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…

Continue read

25/06/2026-01/07/2026

lead picture

[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 ImageImage 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 Image 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 Image, 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 Image 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 Image about the OpenStreetMap x Wikidata Monthly Meetup, which will be held on Monday 13 July, on Chongqing South Road (Taipei, Zhongzheng). You can view Image the list of events and the WikiProject Taiwan community’s page Image.

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 ImageImage 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 ImageImage her presentation materials. Smellman reported ImageImage on a tile server implementation, and alt9800 also gave a presentation themed around taking screenshots. Yuiseki reported that they have developed Image 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 ImageImage the fourth session of their 2026 OSM Workshop Series ImageImage 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 Image 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 ImageImage on GitHub.
  • François Andreaux posted ImageImage, on LinkedIn, about the THT, a web map that shows Image 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 Image and GdeBENZ.ru Image 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 ImageImage, 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 Image 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 ImageImage the page of the project’s foundation. The files are available on GitHub.

OSM in the media

  • clubic reported ImageImage that IGN has inaugurated Image 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 Image 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 ImageImage 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 Image and supplementary documentation Image are available to download free of charge as PDF files from the RSG website.
  • clubic reported ImageImage 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

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

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 an

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

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.

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

Контакт (не игра)

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

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

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

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

И про vkontakte:

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

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

nwr["contact:vk"~

Теперь (предыдущая серия) начнём с простого, с 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;

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

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

(
  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"]


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

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

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

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

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

Saturday, 04. July 2026

OpenStreetMap User's Diaries

Mapping (wheelchair) accessibility

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 Ope

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:

map of wheelchair accessibility in Kilkenny based on OpenStreetMap data

availability of ramps for steps in Kilkenny, based on OpenStreetMap data

Additional ones could be:

highways crossings and availability of tactile paving in Kilkenny, based on OpenStreetMap data

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


Straßenbilder für den Landkreis Fulda

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 Unt

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!


contact:website? Нет, contact:vk

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

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

Ну поехали

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

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

Всегда ли https?

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

Всегда ли http?

nwr["contact:website"~"^vk\

Увидя 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


First changeset review insights for Andhra Pradesh, India

📊 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 g

📊 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.1 Despite diverse OSM review tools and processes, there were few studies about OSM new editor data quality at country level.2 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 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:

  1. Flag:Mark the changeset as “Good” or “Bad”.
  2. 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).
  3. 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 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:

  1. Tags: Use of abbreviations like Rd for ‘Road’, all upper case text or non standard tags, Violation of OSM policies like Personally identifiable information.
  2. Feature geometry: Creating both a way and a node to represent the same feature.
  3. 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.
  4. Comments: Unclear comments
  5. 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 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 OSMCha showing sample review of changesets for Andhra Pradesh, India

OSM newbie editor changesets quality (severity) distribution 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 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 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

  1. 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.
  2. 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.
  3. 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

  1. Analyzing the Changesets of OSM Newcomers, Heigit, 29 January 2024. 

  2. 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. 

Friday, 03. July 2026

OpenStreetMap User's Diaries

The night the earth shook, strangers started to draw

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.

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

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