เลขที่ 93/324 ถนนสุขุมวิท แขวงบางจาก เขตพระโขนง กรุงเทพมหานคร 10260
Users' Diaries
Recent diary entries
So, I’ve been using Altilunium LocationPad for several of my personal projects until now. But recently, I encountered several problems.
I dabble with multiple projects at once, but this app saves everything in a single database. I want this app to be able to create several separate “canvases”, so I can manage several of my projects at once, without mixing them with other projects.

[English] BetterIME is a JOSM plugin that automatically manages Chinese IME state based on focus context, preventing IME from intercepting keyboard shortcuts while editing the map. GitHub: https://github.com/nj-yzf/josm-BetterIME
问题背景
使用中文输入法编辑 OpenStreetMap 时,JOSM 的快捷键(如 S 选择、A 添加节点、W 提高路径精度等)经常被输入法拦截,导致快捷键失效。每次都要手动切换输入法,非常影响编辑效率。
为此我开发了 BetterIME 插件,让 JOSM 根据当前操作场景自动控制输入法状态。
功能介绍
插件将输入法控制分为三种场景:
自动切换至中文输入法: - 编辑 name、name:zh、name:zh-Hans、name:zh-Hant、alt_name、operator 标签时 - 打开 F3「搜索预设组合」对话框时
默认英文,可手动切换: - 其他文本输入框(如 Ctrl+F 查找、其他标签编辑等)
禁用输入法(快捷键正常工作): - 地图视图、工具栏等非文本组件,Shift/Ctrl+Space 也无法意外切换至中文
此外,插件还释放了 Ctrl+Space 快捷键(JOSM 默认绑定为「搜索菜单项」),让它回归系统输入法切换功能。
首选项设置
通过 编辑 → 首选项 (F12) 打开 BetterIME 设置页,可以:
- 启用/禁用自动输入法切换(总开关)
- 启用/禁用 F3 搜索预设对话框中的中文输入法
- 启用/禁用基于标签键的自动检测
- 自定义触发中文输入法的标签键列表(支持添加、删除、重置)
所有设置即时生效,无需重启 JOSM。
安装方式
方式一:JOSM 内置插件管理器 1. 打开 编辑 → 首选项 → 插件 2. 搜索 BetterIME 3. 勾选启用,重启 JOSM
方式二:手动安装 1. 从 GitHub Releases 页面下载 BetterIME.jar:https://github.com/nj-yzf/josm-BetterIME/releases 2. 将 JAR 文件复制到 JOSM 插件目录(Windows: %APPDATA%\JOSM\plugins\) 3. 在 编辑 → 首选项 → 插件 中勾选启用,重启 JOSM
兼容性
- JOSM 19555 及以上版本
- Java 11 及以上
- 目前仅在 Windows 上测试过,macOS 和 Linux 上的输入法框架不同,可能无法正常工作,欢迎反馈测试结果
反馈
如果遇到问题或有功能建议,欢迎在 GitHub 提交 Issue:https://github.com/nj-yzf/josm-BetterIME/issues
许可证:GPL-2.0-or-later(与 JOSM 一致)
I was recently reading Demographic deposit, dividend and debt by Sonalde Desai. Following the Standard Operating Procedure, I looked up this Sonalde person and turns out she is a researcher at a research institute in Delhi called National Council of Applied Economic Research. The work of this organization felt interesting to me, so I had to pause my studies and see its location on OpenStreetMap.
Nothing. Looks like the place hasn’t been mapped yet. I searched for 11, Indraprastha Estate since that was mentioned on their contact page and this time I did find an object. A person called “n’garh” had added the address back in July 2014 and I am so glad that I was quickly able to push a changeset (#180878526). Another win for address mapping!
This post was first released on my website with 💜 under CC BY-NC-SA 4.0.
Hey everyone,
the new version of UrbanEye3D, namely 2.0.0, is out!
This is a major update for the plugin. It’s been a lot of work and took about 2.5 months, but I’m confident it makes the 3D view significantly more useful and enjoyable to work with.
For those who haven’t heard of UrbanEye3D before: it’s a JOSM plugin that renders a 3D world from OpenStreetMap data directly inside JOSM. This lets you preview objects in 3D before uploading your changes to the OSM database.
What’s New
1. 2D Ground Plane
Buildings no longer float. The ground surface is displayed with “flat” objects - roads, lawns, rivers, and lakes. This flat layer is rendered based on downloaded OSM data using a custom MapCSS style. Alternatively, a satellite background can be enabled, as before.

2. Trees
I just published a hacky but effective tool to fix wrong tag values. This lead to some 50 edits only this morning.
More info: https://www.grulic.org.ar/~mdione/glob/posts/correcting-openstreetmap-wrong-tag-values/
これは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からの返信
2026年04月04日、現時点での愛知県瀬戸市にある全バス停のマッピングを完了しました。 また、04月01日にダイヤ改正が行われた菱野団地住民バスの情報を追加しました。 今後は、新ダイヤでの情報、バスの走行する経路の情報の追加や、近隣の尾張旭市・長久手市のバス停のマッピングなど行っていきたいです。
انا احب الخريطه لأنها جعلتني اذهب الى اماكن لم أكن اتوقع الذهاب اليها او من الصعب الذهاب اليها أصبحت مساهمات المدينه يحتويها الضمير لجعل الخريطه اكثر دقه ووضوح
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
- I imported the full Europe PBF into PostgreSQL/PostGIS using osm2pgsql with a custom flex style
- POIs are extracted across 22 categories based on OSM tags (amenity, shop, leisure, healthcare, etc.)
- Each H3 hex cell gets a count of nearby POIs with k=1 neighbor expansion
- Livability scores are computed from essential categories (grocery, healthcare, transit, parks, education, safety)
- Activity scores come from lifestyle categories (dining, nightlife, cafes, culture, shopping)
- 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
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.
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.
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
الأماكن التي وضعها احد المساهمين في المدينه تحتوي على مساهمات غير موجوده لذالك احاول حذفها من بيانات الخريطه لجعل الخريطه ذات مصداقيه ودقه
………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………
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

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?
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:
قمت بمحاولة تنظيف بيانات الخريطه من المساهمات الوهميه والغير موجوده وذالك لجعل الخريطه ذات مصداقيه للمستخدمين
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