これは2026-04-04に開催予定の「OSM Japan」への説明資料です

ことの発端

無限の刃に「int_name」の削除をやめるよう促した

• ことの発端は 2025-07-02 に無限の刃から私に送られてきた「変更セット167515107」の議論に始まります

この変更セットでは無限の刃が * int_nameをname:enに書き換えています。

2025-06-28 from 無限の刃
あなたの編集による、名称キー使用法の誤りを修正しました。交差点名は明白に英語であり、国際名キー「int_name」から英語名キー「name:en」に変更しました。また、削除された日本語名キー「name:ja」再追加しました。これらの私による編集は、OSM Wiki の記述に基づきます。 [https://wiki.openstreetmap.org/JA:Key:name](https://wiki.openstreetmap.org/JA:%E5%A4%9A%E5%9B%BD%E8%AA%9E%E3%81%AE%E5%90%)

※ 原文は変更セット167515107

この時点では、「交差点名は明白に英語であり」との記述以外はよくある「int_name」を知らない人の反応なので、いつもどおり情報源の確認のために返信を送りました

2025-07-03 to 無限の刃
あなたが追加したという「name:ja」の情報源は何でしょうか？
単に[name=*]の値をコピーしただけでしょうか？もし、コピーならその情報は冗長な情報です。
また、「name:en」の情報源は何でしょうか？
もし、「int_name」以外の情報源から「name:en」を持ってきたのならその情報源を明示して、「int_name」と併記してください。
「int_name」単なる「英語表記」以上の意味が含まれています。
変更セットのコメントに示したように、Mapillaryの画像を解析して主に信号機等に付属している「案内標識」の”観光客むけの表記”の部分を確認し、現地の状況と一致している確認が取れたものを「int_name」に昇格させています。「name:en」では単なる「翻訳名」の可能性がありますが、「int_name」にすることで「現地に表示された表記」を示しています。
地名等が現地でどのように表記されているかというのはとても重要な情報ですので「int_name」を軽々しく削除しないでください。 

※ 原文は変更セット167515107

• これ以後、無限の刃からの返信は非常に長文で意味不明な記述になりましたので割愛します。

2025-08-01 to 無限の刃
再度警告いたします。
「int_name」を機械的に削除するする前にコニュニティーによる「検討」が必要です。
ご自分が正しいと確信しているのならコミュニティでのコンセンサスを取り付けてください。 

DWG登場

2025-08-03 from DWG Glassman
DWGは、推奨タグのname<:xx>ではなく、int_nameタグを使用していることに関する苦情を受けました。詳細はosm.wiki/Key:nameをご確認ください。
日本に関する詳細は、https://wiki.openstreetmap.org/Multilingual_names#Japanをご参照ください。
int_nameタグの使用を中止することに同意いただけますか？

※ 原文は「[`int_name`を廃止する提案](https://community.openstreetmap.org/t/key-int-name-must-be-deprecated/142316)」

DWGからのメールには問題があります

• DWGはコミュニティの合意やOSMwikiの記載事項を無視して『int_nameタグの使用を中止』するよう強制してきました

2025-08-03 Glassmanへ日本の「int_name」の重要性を説明しました

• To Glassman : 『具体的な例や「int_name」が必要な理由および問題点を示しましたので https://wiki.openstreetmap.org/JA_talk:Key:name をご覧ください。』
• To Glassman : 『日本には「int_name」が実存しますので、地物として存在するものを使ってはいけないとする合理的な理由を示していただけないでしょうか？』

2025-08-03 DWGからの返信

… See full entry

2026年04月04日、現時点での愛知県瀬戸市にある全バス停のマッピングを完了しました。 また、04月01日にダイヤ改正が行われた菱野団地住民バスの情報を追加しました。 今後は、新ダイヤでの情報、バスの走行する経路の情報の追加や、近隣の尾張旭市・長久手市のバス停のマッピングなど行っていきたいです。

Egypt needs to update its data to keep pace with OSM

Strado – Neighborhood Livability Scores from OpenStreetMap

I’ve been working on Strado, a free tool that scores every neighborhood across 50 European cities using data from OpenStreetMap. I wanted to share the project with the OSM community since it’s built entirely on your work.

What it does

Strado analyzes 22 categories of POIs from OSM – restaurants, healthcare, transit stops, parks, schools, nightlife, grocery stores, and more – and computes livability scores at the street level using an H3 hexagonal grid (resolution 9, ~174m edges).

The idea is simple: if you’re moving to a new city, you should be able to compare neighborhoods by what’s actually within walking distance. Not opinions, not sponsored listings – just data.

How it works

1. I imported the full Europe PBF into PostgreSQL/PostGIS using osm2pgsql with a custom flex style
2. POIs are extracted across 22 categories based on OSM tags (amenity, shop, leisure, healthcare, etc.)
3. Each H3 hex cell gets a count of nearby POIs with k=1 neighbor expansion
4. Livability scores are computed from essential categories (grocery, healthcare, transit, parks, education, safety)
5. Activity scores come from lifestyle categories (dining, nightlife, cafes, culture, shopping)
6. Everything is served as PMTiles vector tiles from Cloudflare R2 – no backend server needed

The scoring engine runs client-side in the browser using MapLibre GL JS. The entire infrastructure costs $0/month.

The data

• ~78 million POIs from OpenStreetMap
• 50 cities from London to Athens
• 22 scoring categories
• 20.5 million hex cells scored

Try it

• Interactive map – click any hexagon to see the score breakdown
• City pages – browse all 50 cities with neighborhood rankings
• Rome example – top neighborhoods, category breakdown, FAQ

All data is attributed to OpenStreetMap contributors under ODbL. Every page includes the attribution.

What I learned about OSM data quality

… See full entry

Following up on osm.org/user/lhirlimann/diary/404921, I discovered today that newer/better aerial imagery for some parts of Mongolia were available, hence doing me doing some edits.

As reported on the Irish OpenStreetMap website, we recently “finished” mapping all the buildings in Co. Down. Due to my goal to get high up in the UK statistics (I made it to #1), I apparently mapped 3,283 tasks, if I’m reading the statistics right. Thanks to the grid system, that led to a fairly systematic coverage under my watchful eyes, resulting in the spotting of 13 potential unrecorded archaeological sites. It took me until today to write the reports to the department in Northern Ireland, because it’s not as much fun as mapping.

Link to overpass-turbo query

I usually add a note=might be a something site, discovered by b-unicycling YYYY-MM-DD to the way, so that I can look for them in overpass-turbo, once I get around to writing the reports to the respective government department. I then add reported by b-unicycling YYYY-MM-DD or something along the lines to the note, so that I know I have reported that one already. This is really only to help me keeping track of what I have discovered and what I have reported.

… See full entry

Introduction

Welcome to The #questionable-edits OSM Iceberg!

Over the past 5 months I have been collating some of the strangest, funniest and most excruciating examples of vandalism, mistakes and creative mapping. This Iceberg takes its name from the #questionable-edits channel on the OSM World Discord where we share the weird, wild and wonderful things we’ve seen while mapping. It should be made clear, the intent of #questionable-edits (and my Iceberg) is not to mock, demean or dissuade novice mappers, but to educate about common mapping pitfalls and share some of the entertaining things that have been found. I myself am guilty of a number of things listed below! I’ve included over 80 items in my Iceberg, ranging from the well-known to the downright unhinged. This Iceberg is also available on the OSM forums.

It shouldn’t have to be said, but please do not harass or otherwise antagonise any users whose edits may be visible in these examples. The screenshots and changesets linked below are intended as illustrative examples, and aren’t intended to target individual mappers.

Happy April Fools everybody! (Yes I might be a day late, but I was last year too). Enjoy!

The Iceberg

… See full entry

OpenStreetMap The most important map

………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………

I really love JOSM, and the more I use it, the more I discover that it offers some very useful features… that some of you may not be aware of ! Even if some are less useful, simply knowing they exist opens up the possibility that you might find them useful!

I’d like to show them to you here.

This diary post is a follow-up to my previous one on JOSM: Building drawing tips, a perfect guide.

1st manipulation: Use JOSM

… See full entry

En Málaga ya se han realizado contribuciones significativas a OpenStreetMap gracias al esfuerzo conjunto de pequeños grupos de personas. Sin embargo, a menudo resulta difícil encontrar un espacio donde estas iniciativas de colaboración local se coordinen de forma organizada y participativa.

Para cubrir este vacío, he creado un grupo de trabajo dedicado al mapeo colaborativo del municipio. Su objetivo es servir como punto de encuentro para mapeadores locales interesados en trabajar juntos en proyectos concretos, mejorando la organización y facilitando la participación.

Este grupo se centra en iniciativas locales específicas y no funciona como un foro de conversación general. Por ello, el acceso es mediante invitación, asegurando un entorno enfocado, respetuoso y productivo.

Logo de OSM Málaga. Fuente: trabajo propio (CC BY-SA 4.0) derivado de un trabajo previo de Aury88, disponible en el Wiki de OSM.

¿Por qué usar Zulip para el grupo?

… See full entry

The Hub, Edinburgh rendered with Beakerboy’s OSM Building Viewer https://beakerboy.github.io/OSMBuilding/index.html?id=42997989

I’m working on a project using OSM building data so I thought I’d familiarise myself with the building:part and roof tags and see what the editing process is like.

The Hub only had height data and a basic outline tagged for the spire, so as the highest man made point in Edinburgh, it made for a good candidate to get stuck in.

I used height data from the OGL licensed Scottish LiDAR Phase 5 DSM that covers Edinburgh, and photos of the building from Wikimedia Commons

The elevation profile tool in QGIS proved useful for exploring the LiDAR data (after I worked out how to right-click to confirm the path). I normalised the elevation to zero with the raster calculator and set a custom colour ramp to aid visualisation:

… See full entry

Egypt needs to update its data to keep pace with OSM Why doesn’t MapsMe keep up with OSM? Doesn’t he care about updating the map to match OSM? All programs update the map and keep pace with OSM Why MapsMe?

Back “home” with Mom for the weekend, when I picked her up after church, I was advised by everyone that taking the back exit from the church parking lot. What back exit? It wasn’t on OSM or GM. (Makes sense, last time I was in that parking lot, it was all mud and construction; this exit doubles as cover for new water main or something.)

So of course I went out the normal exit, around the block and in and out of the new back entrance/exit to trace both lanes with the GPS. It is indeed now visible in our newest Mapbox imagery.

osm.org/changeset/180651021#map=17/43.834318/-70.432577&layers=VN

此文本同時提供 英文版本 This article is also available in English

---

OpenStreetMap 是一張由和你一樣的使用者共同協作編輯的地圖，這種協作既是它最大的優點，也是資料品質持續出現問題的原因之一。當成千上萬的貢獻者各自為商店、餐廳、診所和政府機關添加 phone 標籤時，每個人都會帶入自己的格式習慣。對臺灣而言，結果就是一個資料庫中同一個國家代碼可能出現 +886、+886+ 或 +886(2)，而光是一個城市的電話號碼就可能跨越十幾種不同的慣例。

都亂成一鍋粥了，趁熱喝了吧。（悲

這篇文章記錄了我們在掃描六個直轄市及另外五個縣市的 OSM Elements 時所發現的情況，我們正在開發正規化工具（normalizer） 一勞永逸。

---

問題的規模

在十一個隨機取樣的區域中——包括所有六個直轄市（臺北市、新北市、桃園市、臺中市、臺南市、高雄市）加上苗栗縣、新竹市、臺東縣、連江縣、金門縣——我們在 49,229 個元素上發現了 49,260 個標籤（phone 或 contact:phone）。在將以分號分隔的多重值欄位拆分後，總共得到 50,643 個獨立的電話號碼字串進行分類。

格式類別	數量	佔比
E.123 空格 (+886 2 1234 5678)	41,842	82.6%
RFC 3966 連字號 (+886-2-1234-5678)	6,655	13.1%
無分隔符號 (+886212345678)	1,158	2.3%
本地格式，無國家代碼 (02-1234-5678)	854	1.7%
錯誤/誤打的國家代碼 (+866 …, +886(2)…)	92	0.2%
其他（錯誤國家、垃圾內容）	42	0.1%

大約 每 5 個獨立值中就有 1 個 偏離了最常見的貢獻者慣例，這種不一致性使得去重（deduplication）、顯示和機器解析變得複雜。

… See full entry

此文本同時提供 台灣華語版本 This article is also available in Taiwanese Mandarin

---

OpenStreetMap’s collaborative nature is both its biggest strength and a source of persistent data-quality issues. With thousands of contributors independently adding phone tags to shops, restaurants, clinics, and government offices, each person tends to follow their own formatting style. For Taiwan, that means a database where the same country code can show up as +886, +886+, or +886(2), and a single city’s worth of phone numbers might span a dozen different conventions.

This post catalogues what we found when we scanned OSM elements across all six special municipalities and five additional counties — we are working on a normalizer to fix the issue.

---

The Scale of the Problem

Across eleven cached regions — all six special municipalities (臺北市, 新北市, 桃園市, 臺中市, 臺南市, 高雄市) plus 苗栗縣, 新竹市, 臺東縣, 連江縣, 金門縣 — we found 49,260 tags (phone or contact:phone) on 49,229 elements. After splitting multi-value fields on semicolons, that yields 50,643 individual phone number strings to classify.

Format class	Count	Share
E.123 space (+886 2 1234 5678)	41,842	82.6%
RFC 3966 dash (+886-2-1234-5678)	6,655	13.1%
No separator (+886212345678)	1,158	2.3%
Local format, no country code (02-1234-5678)	854	1.7%
Corrupt/typo country code (+866 …, +886(2)…)	92	0.2%
Other (wrong country, junk)	42	0.1%

Roughly 1 in 5 individual values deviates from the most common contributor convention, creating inconsistency that complicates deduplication, display, and machine parsing.

… See full entry

The Virtual Institute for Sustainable Development - IVIDES.org® , a virtual research institute on the SD matter, and the IVIDES DATA®, a small Brazilian company on information technology consultancy, are lauching a new partnership with the State University of Campinas (UNICAMP) in order to use OpenStreetMap on the collaborative mapping of disaster risk for coastal communities on the nlNorthern Coast of the State of São Paulo (Brazil).

---

First meeting on March, 2026. Source: project collection. Map data (c) OpenStreetMap contributors.

---

… See full entry

%{count} contribution(s) in the last year

section on the user page, should be edited. For numbers greater than four digits, periods are placed in groups of three for easier reading, but OSM user profiles have numbers that are difficult to read, such as 1234565885. If we write this as 1.234.565.885 or 1,234,565,885. The contribution counter will be easier to read.

Yesterday, I attended the OpenStreetMap Local Chapters and Communities Congress 2026 online.

There were at least 15 participants who signed the attendance list on the event’s HackMD document, representing a range of countries including the Philippines, Italy, the United States, Canada, Greece, Indonesia, Belgium, Kenya, and Brazil. The document is available publicly here.

After introductions and updates from the OpenStreetMap Foundation Board, the session moved into a group discussion titled “Challenges in OpenStreetMap and overcoming those challenges.” This discussion was conducted through Mentimeter, allowing participants to submit anonymous responses to guided questions.

Here is a (selected) summary of the discussion results:

---

Question 1 : If a new mapper asked you “what’s the hardest part about being in the OSM community?” what would you say.

“So many smart people. All with their strong opinions about how things should be done.”

“Dealing with abusive community members.”

… See full entry

testblog