OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

About three or four years ago, I used OSM to get map information for my autonomous driving test data. However , never had I thought to donate my living experience to the OSM.

On 2026.7.9, I realize that it is time to do it. I update some residents, toilets and cafe’s position. And I also name some unnamed roads and parks where I was born or studied.

Hope to update necessary infomations continiously

Location: 丰庄, 真新街道, 嘉定区, 上海市, 200333, 中国

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.

Location: Los Quilos, Rancagua, Provincia de Cachapoal, Región del Libertador General Bernardo O'Higgins, 2880000, Chile

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

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» نداریم؟ برای همین درست شده. یا نباید نام قدیمی را درون پرانتز نام جدید گذاشت. مگر در معبر خارجی این چیزها وجود دارد؟

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

See full entry

Location: Pääsküla, Nõmme linnaosa, Tallinn, Harju County, Estonia

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

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

И получаем:

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

‿( ́ ̵ _- ` )‿

Posted by frodrigo on 6 July 2026 in English.

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.

See full entry

Posted by Mapper-Jonas on 6 July 2026 in German (Deutsch). Last updated on 8 July 2026.

Hallo zusammen,

in den letzten Wochen habe ich mich mit dem Thema Indoor Mapping vertraut gemacht. Da ich dabei auf einige Probleme gestossen 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 Spass mit der Anleitung für Indoor-Mapping mit OpenStreetMap

Ziel der Anleitung

Diese Anleitung vermittelt die Grundlagen des Indoor-Mappings mit OpenStreetMap (OSM). Das Ziel besteht darin, die Innenräume von Gebäuden, wie beispielsweise Stockwerke, Räume, Korridore, Treppen oder Aufzüge, korrekt zu erfassen und in OSM zu dokumentieren. Die erfassten Daten können anschliessend in verschiedenen Anwendungen und Viewern visualisiert und für Navigations-, Analyse- oder Informationszwecke genutzt werden.

Hinweis: Bei spezifischen Problemen oder wenn du detailliertere Antworten suchst, empfiehlt es sich, einen Blick ins OSM-Wiki zu werfen. Dort findest du weiterführende Informationen, Erklärungen und mögliche Lösungsansätze.

See full entry

Location: Rapperswil, Rapperswil-Jona, Wahlkreis See-Gaster, St. Gallen, 8640, Schweiz

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.

Location: Campamento Puente Alta, Rancagua, Provincia de Cachapoal, Región del Libertador General Bernardo O'Higgins, 2920001, Chile

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

大家好!我目前正在开发一个面向韩国用户的地图项目,计划使用 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 机制?

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

Posted by FaizalPEJAI on 5 July 2026 in English.

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.

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

See full entry

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

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

Posted by b-unicycling on 4 July 2026 in English. Last updated on 8 July 2026.

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:

See full entry