To-do: Add bus route 42 stops through Highton and Belmont. Will be referring to McHarry’s route map and ensuring match with Transport Victoria resources.
Users' Diaries
Recent diary entries
Posted by evyy on 1 August 2026 in German (Deutsch).
Gerade eben mappe ich den Bayern-Park detaillierter. Durch meine frühere Jahreskarte konnte ich den Park oft besuchen und kenne daher viele Bereiche aus eigener Erfahrung. Jetzt nutze ich dieses Wissen, um Details des Parks in OpenStreetMap zu verbessern.
Als Ziele habe ich folgende:
- Alle POIs überprüfen und ggf. eintragen/aktualisieren
- Alle (oder zumindest den größten Teil von allen) Wege überprüfen und ggf. hinzufügen/aktualisieren
- Generell mehr Details hinzufügen
I am currently focusing my mapping work on the Taiping Heritage Zone. Most of the shoplot footprints and major buildings have been completed, and I am now working on detailed micromapping for schools, museums, and government buildings.
Please feel free to contribute by adding any missing information, such as shop or stall names, building levels, address numbers, or other relevant details that I may have missed.
Let’s work together to make Taiping one of the most complete and detailed small-town maps in Malaysia on OpenStreetMap.
As explained in this french diary entry I left a bunch of notes, took a bunch of traces while visiting Mongolia in July. The main reason, was that I was playing with StreetComplete and firing Vespucci would have annoyed my wife adding notes was easier. So I left notes, for later. Today I decided to start editing based on my memory and some of the notes. While editing, I saw a very high number of these in the center of UB. screenshot of the browser Firefox showing Openstreetmap.org in edit mode with notes visible. You see a lot of these notes in a very small area
Many are old, and the imagery is old. Is there a process to clean up notes? Are there people willing to spend time taking these notes and making the edits that for some are probably needed?
この diary は アカウントロックされた経緯の説明 の関連記事です。
DWGが仕事をしていないようなので催促しました
Glassmanによる不当なアカウントロックと ‘int_name’の大量削除問題 を3月に「通報」したのですが、なんの進捗もないようなので催促のメッセージを送りました。 osm.org/user_blocks/19857
原文はこちらです(英語)
Re: 2026年08月 1日 04:27
日本のコミュニティ向けに日本語の翻訳を示します。
[Ticket#2026013110000088]https://www.openstreetmap.org/messages/1338706
DWG(Data Working Group)への声明(日本語訳)
DWGの皆様へ
まず、返信が遅れたことをお伝えいたします。
この遅延は意図的なものであり、int_name に関するコミュニティフォーラムでの議論が一定の段階に達し、適切な説明が可能になるまで待つ必要があったためです。
https://community.openstreetmap.org/t/key-int-name-must-be-deprecated/142316/49
この期間中、DWGからのコミュニケーションにおいて重大な誤解が存在することが明らかになりました。
DWGは、私 hayashi を別のマッパー「無限の刃」と繰り返し混同しています。
この誤認により、本来別の人物に向けられるべき指摘や警告が私に対して送られ、DWGのメッセージには一貫性がなく、対応不能な状態が続いていました。
私は hayashi です。
私は 無限の刃 ではありません。
int_name の削除を提案し、実際に削除を行ったのは 「無限の刃」氏であり、私ではありません。
1. 「あなたの主張」という誤った認識について
DWGは以前、次のように述べています。
> I'm not sure you have people convinced with your argument.
> あなたの主張で人々を納得させられたかどうかは、定かではありません。
しかし、この評価は事実に反しています。
-
int_nameの廃止を主張したのは 「無限の刃」氏 です。 -
int_nameを大量削除したのも 「無限の刃」氏 です。 - 日本コミュニティからの警告を無視したのも 「無限の刃」氏 です。
- この行為を通報したのは 私 hayashi です。
私は int_name を削除していません。
私は int_name の廃止を主張していません。
私はただ、int_name を廃止する理由を質問しただけであり、その質問には一度も回答がありません。
参照: https://community.openstreetmap.org/t/key-int-name-must-be-deprecated/142316/38
さらにコミュニティフォーラムでは:
- 「無限の刃」氏の提案を支持する投稿は 一つもありません
- 私の意見を「一方的」と批判する投稿も 一つもありません
- 多くのマッパーが「無限の刃」氏の一方的な行動に懸念を示しています
DWGが「私の主張がコミュニティを説得できていない」と述べたのは、人物の取り違えによる誤認です。
2. 私への「コミュニティ参加の推奨」を繰り返すのはやめてください
DWGは繰り返し、私に「ローカルコミュニティに参加するように」と促しています。
これは不適切であり、直ちにやめるべきです。
私は長年、日本のOSMコミュニティに積極的に参加してきました:
osm.org/user/hayashi/diary/408467
日本コミュニティではすでに:
-
name:enの用法が議論され - Wikiに合意内容がまとめられ
-
int_nameの扱いについても共通理解が形成されています
DWGが私に「コミュニティのフィードバックを求めよ」と指示するのは、以下の事実を無視しています:
- コミュニティの合意はすでに存在する
- 私はその合意形成に参加している
- コミュニティ参加を拒否しているのは 「無限の刃」氏である
DWGの繰り返しの指示は、日本コミュニティの実態を把握していないことを示しています。
DWGは次のようにも述べています:
> What is the most active Japanese community discussion place?
> 日本コミュニティの主要な議論場所はどこか?
Posted by googlenaut on 31 July 2026 in French (Français).
Last updated on 2 August 2026.
Le Tour des Cimetières approche la fin. dernière étape : Lyon - Saint Étienne. 55 des 3882 tâches subsistent. :) .. Fini !!! .. terminé en moins de 12h.
Cette année encore, j’ai eu la chance d’aller en Mongolie. Grâce à neostumbler, je suis en mesure de montrer l’intégralité de mon voyage: Capture d'écran de l'application neostumbler, montrant mon parcours avec les extrémités Est et Ouest de celui-ci. Dadal à l'est, pas loin d'UB à l'Ouest
Upgraded from the Max to the Max2. Going to publish my settings here so it’s easier for me to find.
Walking
- Same settings as Bicycle Settings below, except set the Interval to 1 or 2 seconds depending on walking speed. 2 if casually walking, 1 if brisk.
- Very important: Use a selfie stick and hold camera at least 6 inches above head to capture better images. The higher the better.
Bicycle, My main method of capturing imagery. Most tested.
- Time Lapse 360 Video
- Resolution 8K
- Interval 0.5 Seconds
- Bit Depth 10-Bit
- EV Comp 0
- ISO Min 100
- ISO Max 800
- Color Natural
- Sharpness Low
- Denoise Low
- Bit Rate Max
Car
Still need to test and figure out the settings. I currently use a dash cam for a car and I don’t have an exterior mount for my GoPro. Dash cam I use is an AZDOME GS63H. Very simple to use and great quality images. And one of the few dash cams that work with Mapillary for less than 100ドル. I got mine on Ebay for about 50ドル.
Androidアプリ「OSM郵便マップ」をリリースしました
OpenStreetMapのデータを利用した、日本郵便向けの地図アプリです。 登録されているPOIの可視化に加え、煩雑な収集時刻の入力を補助する画面など、編集向けの機能も搭載しています。
Wiki: osm.wiki/JA:OSM郵便マップ
GPS距離判定で現地入力を強いていますが、実装検証はエミュレータではなく現地に足を運んで試してました
これから
- ゆうゆう窓口の営業時間対応
- ゆうちょ銀行ATMの表示 辺りを実装しようと考えています
8月最初の月曜日
近隣を所管する田富郵便局の平日1便の収集ルートと時間が変わるようで、サーベイした1週間後には平日収集時刻が変わることが判明しています。巡回しなきゃ...。
According to the Alaska Department of Fish and Game, there are over three million lakes in Alaska with a surface area larger than five acres!
Currently, in OpenStreetMap, there are roughly two hundred and forty two thousand elements in Alaska tagged with natural=water, which is a generic tag for an area filled with water.
So, I have decided to embark on mapping natural areas filled with water!
I use the USGS elevation data for alignment, as it seems to have the best alignment to where things actually are on the ground. The USGS imagery is sometimes aligned with the elevation data, but sometimes is not, so the Mapbox and ESRI Clarity imagery is instrumental in areas where it is more accurate to the elevation data.
The National Map Topographic is extremely useful for some lakes, for those where it matches the elevation data well. Often though, it does not match the elevation data.
I posted about this in the OpenStreetMap Slack, and have received help from Watmildon, who has been very kind and extremely helpful! He is helping with the technical aspects of this, and has brought the 3DHP program to my attention, a hydrology program from USGS that is based on elevation data and thus much more accurate than the older NHP data. He is helping to setup a website where one can view the differences between OpenStreetMap, NHP, and the 3DHP, and eventually I hope to be able to overlay the 3DHP data onto an OpenStreetMap editor so I can use it to assist the mapping.
Thanks for reading and happy mapping!
Sources:
https://www.adfg.alaska.gov/index.cfm?adfg=rivers.main
https://taginfo.geofabrik.de/north-america:us:alaska/search?q=natural%3Dwater
在 2026 年 7 月初,Wikidata 台灣與 OpenStreetMap 台灣社群一同在嘉義高鐵站集合,架設好車頂相機,在目標區嘉義縣海線一帶鄉鎮的廟宇以及其聚落,也一邊開車一邊記錄沿途的街景。
從嘉義高鐵站旁的糖鐵車站出發,兵分多路前往嘉義縣沿海太保市、朴子市、東石鄉; 義竹鄉、布袋鎮與鹿草鄉,記錄當地欠缺的地圖圖資與照片。在車上奔馬記錄沿途街景,然後到了廟宇則下車記錄內外觀與攃拜主神。中午大家在湖口飯吃休息用中餐,而傍晚則在鹿草安溪中寮城隍廟集合,觀察廟會活動,為第一天的踏查畫下句點。
第二天的工作坊則是下午進行,在嘉義市區的活動場所台灣圖書室進行,介紹 OpenStreetMap、Wikidata 與維基導遊。
在台灣,維基與開放街圖常面臨上網人口少的地方,比較沒有人願意參與貢獻的窘境。藉由兩個社群活躍成員去台灣各地在地人低度參與的地方去記錄地方地圖圖資以及在地廟宇,補足缺少的資訊。而藉影像補捉工具的協助,如手機相機拍廟宇的外觀與內景,架在車上的 360 相機或相機記錄沿途街景,則讓我們的貢獻延伸至兩天的踏查與工作坊之後,繼續各自在電腦前面整理資料與繪製當地的地圖圖資。
在 OpenStreetMap 的發源地英國,常有一間接一間酒吧接力飲酒聊天談論社群的事情,也順便將沿途的商家記錄下來。在台灣的街景踏查團,則是一間一間的廟宇接連進行踏查,除了記錄,也順便進行 OpenStreetMap 圖資的更新。在台灣,廟宇常是當地聚落的中心點,許多公共事務在廟宇協調與分配,大型的廟宇甚至也會吸引商販前來擺攤做生意。
感謝台灣維基媒體協會與地圖公司 TomTom 的協助,提供舉辦活動所需要的資源。
Test
試機1
Posted by christopheCD22 on 28 July 2026 in French (Français).
Bonjour, Je travaille à l’exploitation des routes départementales au Conseil Départemental des Côtes d’Armor. Afin de mener à bien nos missions, nous utilisons des application informatique dont la carto est basée sur OSM. Nous constatons de nombreuses erreur d’affectation de route. En effet de nombreux déclassement de route de route départementale vers route communale n’apparaissent pas. Nos données carto sont en open data et utilisés par l’iGN qui met donc ses cartes à jour régulièrement. Comment faire pour les cartes OSM soient le plus à jour possible. Merci
Posted by christopheCD22 on 28 July 2026 in French (Français).
Bonjour, Je travaille à l’exploitation des routes départementales au Conseil Départemental des Côtes d’Armor. Afin de mener à bien nos missions, nous utilisons des application informatique dont la carto est basée sur OSM. Nous constatons de nombreuses erreur d’affectation de route. En effet de nombreux déclassement de route de route départementale vers route communale n’apparaissent pas. Nos données carto sont en open data et utilisés par l’iGN qui met donc ses cartes à jour régulièrement. Comment faire pour les cartes OSM soient le plus à jour possible. Merci
One day, in a certain neighborhood, there was a heated discussion about naming an unnamed road.
At first, the discussion was about deciding what name they should choose for the road.
But can you guess the final consensus of that discussion?
They preferred not to be mapped.
The status quo was good enough, they said. The road looked like a maze, with little or no clue on how to properly navigate it. They argued that if they named the unnamed road, it would give "outsiders" a clue on how to navigate it, which was "bad" for the internal security of the people who lived there.
This made me think about the ethical grounds of conducting large-scale mapathon campaigns remotely.
We generally work under the assumption that "the more mapped places, the better." But what if the locals don’t consent to being mapped?
What if they prefer not to be mapped?
Querying OpenStreetMap Data with the Overpass Turbo Wizard
If you’re new to OpenStreetMap (OSM), writing Overpass queries from scratch can seem intimidating. Fortunately, Overpass Turbo provides a built-in Wizard that generates queries automatically based on simple search phrases. This makes it easy to retrieve geographic data without learning the full Overpass Query Language (Overpass QL).
What is the Overpass Turbo Wizard?
The Wizard is a feature in Overpass Turbo that converts plain-language search terms into valid Overpass queries. Instead of manually writing code, you can describe the data you want and let the Wizard generate the query for you.
For example, if you want to find schools in the current map area, you can simply enter:
text
amenity=school
The Wizard will create the corresponding Overpass query automatically.
How to Use the Wizard
- Open Overpass Turbo.
- Zoom the map to your area of interest.
- Click Wizard in the toolbar.
- Enter a search expression such as:
amenity=hospital
or
shop=supermarket
- Click Build and Run Query.
- The matching features will appear on the map.
The generated query can also be viewed and edited if needed.
Example
Suppose you want to locate restaurants in the visible map area. Enter:
amenity=restaurant
The Wizard generates an Overpass query and displays all matching restaurants from OpenStreetMap within the current map view.
Exporting the Results
After the query runs successfully, you can export the results for use in GIS software or other applications.
- Click Export.
-
Choose a format such as:
- GeoJSON for web mapping and GIS tools.
- KML for Google Earth.
- GPX for GPS applications.
- Raw OSM Data for OpenStreetMap-based workflows.
- Save the file to your computer.
GeoJSON is the most commonly used format because it works well with tools like QGIS, Leaflet, and Mapbox.
Conclusion
Pola Keyword SEO Spam Judi Online di Indonesia
Hasil pengamatan menunjukkan bahwa changeset SEO spam judi online di OpenStreetMap memiliki pola yang relatif konsisten. Brand umumnya menggunakan akhiran "88", sedangkan komentar changeset berisi kumpulan kata kunci promosi yang diulang untuk kepentingan optimasi mesin pencari (SEO), bukan untuk mendeskripsikan perubahan data OpenStreetMap.
Observations indicate that SEO spam changesets related to online gambling in OpenStreetMap follow a relatively consistent pattern. Brand names commonly use the "88" suffix, while changeset comments consist of collections of promotional keywords repeated for search engine optimization (SEO) purposes rather than describing the actual OpenStreetMap data edits.
Keywords are ordered by descending frequency
Very High / Dominant Frequency
–88 (brand suffix)
slot
gacor
judi
casino
terpercaya
terbaik
High Frequency
login
daftar
link alternatif
RTP
maxwin
jackpot
bonus
deposit
withdraw
mahjong
zeus
Pragmatic Play
PG Soft
togel
toto
–77 (suffix)
–99 (suffix)
–138 (suffix)
–168 (suffix)
–188 (suffix)
–303 (suffix)
–777 (suffix)
Moderate Frequency
pola
cashback
free spin
scatter
wild
multiplier
cuan
menang
sabung ayam
SV388
poker
domino
QQ
Habanero
Joker
Spadegaming
Microgaming
Playtech
Unique Study: Trojan Horse Spam
Pada teknik ini, komentar changeset tampak sepenuhnya normal dan tidak mengandung kata kunci yang berkaitan dengan perjudian. Sebaliknya, konten spam disembunyikan di dalam tag objek OSM, sehingga deteksi yang hanya mengandalkan kata kunci pada komentar changeset menjadi kurang efektif.
In this technique, the changeset comment appears completely legitimate and contains no gambling-related keywords. Instead, the spam is concealed within the OSM object’s tags, making keyword-based changeset detection less effective.
Contoh / Example:
I’ve been mapping out every building I can that is visible from satellite imagery and Bing Streetside throughout Mount Pleasant. I’m currently focused on finishing up the neighborhoods and businesses that are on Chuck Dawley and Coleman Blvd, and I have almost finished filling in that large area made up from those major arteries.
I really wish I could use Charleston County’s GIS viewer for addresses and building shapes (especially for newer buildings, since people keep moving here ):< ), but of course the county puts all of their GIS data under copyright. That would be fine, but I tried contacting the GIS office to see if I could get permission to use their data, specifically their address data, but they never even responded. There are a few other ways that I could "request" address data but I don’t know if those requests would even be useful for mapping purposes. Best thing to do is to go to these neighborhoods myself and mark down any addresses that I couldn’t have gathered from Streetside. I’m not sure how I will do that without looking like a creep stopping at people’s houses and marking their address down. Guess I’ll have to grow a pair and do it anyway!
I do wish Bing Streetside had better image quality. The best images are from 8 years ago, and some houses have been demolished and replaced in that time according to Esri imagery (the most up to date imagery here, probably around only a year off). There are some spots with 2020 imagery but it just looks so awful. Even with the higher quality 2014 imagery you can barely make out small details like addresses at all. It really makes you appreciate what Google Street View provides, but we can’t use that at all. No wonder Bing Streetside completely shut down.
Posted by SomeoneElse on 27 July 2026 in English.
All the hospitals in the UK and Ireland, in about 10 seconds
Note that this is an update of a previous diary entry. This version uses updated Overpass software from a fork.
Many people have noticed that publicly available Overpass servers have been suffering from overuse (a typical "tragedy of the commons"). OSM usage policies generally contain the line "OpenStreetMap (OSM) data is free for everyone to use. Our tile servers are not". Unfortunately, there have been problems with overuse of the public Overpass servers, despite the usage policy. "Just blocking cloud providers" isn’t an option, because (see here - use the translate button below) lots of different sorts of IP addresses, including residential proxy addresses, are the problem.