OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

大家好!这里是monhiko!(/ω\)

这是本人的第二篇日志,之所以要写这篇文章,是因为最近注意到我们一些mapper在看到我画的这边的情况后就觉得“哇、他画得这么好,我也要向他学习!”然后就就跟着我这边画了,然后也跟着出现了奇奇怪怪的说法,甚至更有甚者提出来要将我这边作为“典范”。这些说法吧,有些嘛。。。过于浮夸了。

所以今天呢,我主要站在一个普通mapper的角度啊,跟大家分享一下画图的一些历程,同时呢也借这个机会跟各位mapper分享一下我个人的一些想法。

希望各位小伙伴们看完后记得一键三连(bushi)

一、绘图经历

本人嘛。。。最初是2021年3月的时候开始接触OSM的,之所以决定在OSM绘图,主要是认为OSM上的数据在一定程度上是有助于科研的,毕竟哪怕是现在很多论文里涉及到道路啊用地数据之类的主要数据来源都是OSM。一开始我主要是顺着两条线索,一个是城市道路、用地、建筑三个大的内容,因为这些数据在分析城市肌理构成及特征时会用上,比如一个城市它是如何发展的,它为什么会一步步由古代最早道路布局、演变到现在大家所看到的城市格局的,以及它在自身发展的过程中是如何在不断巩固自身原有的布局理念的同时不断吸收外来的新的城市布局理念,从而产生了属于自己特色的城市布局风格的,这些实际上借助OSM就可以很好地表现、反映出来(高德、百度也有路网数据,但他们偏向于导航,所以不好应用于肌理研究);另外一个是城市内的各类商业数据、绿化数据以及各类点类数据,因为这些数据尽管它很难在大的地理尺度上表现出来,但是它对于将来的某些研究兴许会用得上。但不管这两条线索它会怎么发展延伸,核心就只有一个,那就是:

“在不危害国家安全这一大的根本前提下,让OSM尽可能地为我们的科学研究服务”

确定了这一基本原则和这两条线索后,我就这么每天顺着自己的心情东画画西画画下去了。然后就这么坚持了一年多。这时候突然开始有mapper发私信来跟我说“哇、你画的好棒啊!”然后我才回过头来看发现,诶、不对啊,就短短一年的时间城区已经基本上实现覆盖了,而且对于城市科学研究已经基本上够用了。

“那接下来要做什么?”一个疑问出现在我的脑海里。最开始我是想画了一年多也比较熟了,那就去看看大城市怎么画讨讨经验吧。于是我就去看国内外很多大城市的优秀案例。到了这时我才发现,原来我已经向前走了很多步了。。。

于是在那时我就做出了一个决定:将原来的两条线索扩展为“三个方向+两个线索”。哪三个方向呢?

第一,继续补充,因为尽管城区已经画完了,但是也仅画完了城区,农村是一点数据也没动,但众所周知(?)啊,我们并不是像西方国家一样在上世纪七八十年代就接近完成了城市化,截至目前我们国家城镇化率是百分之六十多,也就是说至少还有百分之三十几的人是在农村的,而我们国家有相当大一部分农村在发展过程中结合我国传统营城理念以及当地的自然地理特点形成了自身的风貌特色,但这些风貌特色我们往往没注意到、或者说由于近三十年的高度城市化发展使得我们忘记了农村存在的意义导致这些特色被我们“刻意地”遗忘了,结果就造成我们在城市化过程中有些城市因为不顾自身发展历程以及自身自然地理特点盲目照搬照抄西方城市经验建设,导致出现了“城是城风、乡是乡貌”,城乡风貌极大割裂(当然这也是西方国家的通病了),所以就有必要在一定程度上借助OSM使人们能够直观地看到我们农村的“肌理特征”,进而将这些特征融进我们城市建设当中,从而实现“城乡肌理风貌融合”,而恰巧我们OSM上还有很大空白,这就意味着还有很多仍然保持着自己的特色的农村值得去画,所以农村(包括城郊附近的农村)仍然是值得去画的;

第二,尝试去画其他的一些县市,因为它们的地理特征、城市风貌、城市结构特征都不太相同,但正是这些不同能够锻炼自己的绘图能力,能够让自己能够更好加强判断“哪些能画、哪些不能画”的能力,从而坚持“在不危害国家安全这一大的根本前提下,让OSM尽可能地为我们的科学研究服务”这一基本原则,同时呢也能够为各地的科学研究提供更多素材;

第三,关注地区内绘图动向,因为“科研无国界、但科研人有国界”,在这个世界还没实现“大道之行也”之前,我们都要时刻警惕一些搞破坏的人。那么如何坚守阵地、不被别人搞破坏呢?那就首先要从宣传、教育讲起,于是就有了我的那篇“基于2023版《公开地图内容表示规范》在OpenStreetMap上标注的解读”(基于2023版《公开地图内容表示规范》在OpenStreetMap上标注的解读)。

我认为啊,只有我们坚守住了这三个方向,OSM这个工具才能真正成为我们日常科研的好助手。

二、关于自己对于OSM以及绘图的想法

See full entry

Posted by Mikhail Kuzin on 16 June 2025 in Russian (Русский). Last updated on 17 June 2025.

Пересечения и перекрестки

Описание пересечений в OSM как и многое достаточно хаотично и лоскутно. См Key:junction Чтобы готовить перекрестки более совершенными надо систематизировать существующие тэги и …. добавить еще немного хаоса)))

node: 
    junction = controlled|uncontrolled|inout|joint 

Продолжая развивать тему тэгирования точек, в настоящее время существуют и применяются тэги junction=yes, junction=uncontrolled При работе над рендером мы провели классификацию пересечений, которые вероятно стоит различать и предлагаем расширить этот список, но саначала…

Основные признаки пересечений

  • Участники - точка принадлежит 2м и более way
  • Размер - неотъемлемым, хотя и невсегда явным атрибутом пересечения будет являться некая фигура, площадь, многоугольник - нечто что будет соотносится(описывать,вписывать) с реальными линейными размерами места, где будет(не обязательно) происходить конфликт участников движения. В OSMPIE мы предложили использовать окружность и соответсвенно радиус, как аттрибут см junction:radius
  • Связность - появляются такие понятия(точки) входа и выхода в пересечение и необходимости указания(атрибуции) их связи друг сдругом. См connect:lanes, relation[type=connectivity], turn:lanes
  • Конфликтные точки - необязательный, часто присутствующий признак - конфликтности одних связей с другими и место(координаты) этого конфликта.

Существует еще один признак пересечений, но от уже относится не к пересечению самому по себе, а к их множествам. Пересечения склонны группироваться в сложные объекты - “перекрестки” - то есть образовывать явные и конечные множества - кластера.

Самым оптимальным вариантом атрибутирования, который бы мог управлять процессом и соответственно результатом кластеризации тоже является радиус окружности - см. тэг junction:cluster:radius

Классификация пересечений:

See full entry

No regresso de um passeio à praia, reparei que havia um caminho que ainda não estava no mapa. É só uma edição rápida, antes de ir almoçar, pensei eu. Adicionado o o caminho, falta ligá~lo à estrada principal. E reparo que a passadeira no mapa não está no sitio atual. É só mais uma ediçãozinha. Mas este caminho está trocado com a via dedicada a bicicletas. Bom, já que estou com a mão na massa…

E o landuse está no sitio errado. E não é que esta área está toda ainda com a versão de imagens aereas de 2014…

E para acabar, claro que não posso fazer upload sem corrigir os avisos associados à todos os objetos que toquei…

Três horas depois, com um almoço pelo meio, a rápida adição de um caminho está concluída. E só foi preciso adicionar 146 objetos, modificar 197 e eliminar 12. E pelo meio consultar os dados de toponímia da câmara municipal.

Posted by ader308 on 15 June 2025 in English.

Today is a special day—my birthday. I woke up feeling grateful and hopeful. Another year of life is not something to take for granted. I feel happy, not just because it’s a celebration, but because I’ve come a long way, and I’m ready for more. Birthdays are not just about cake, candles, or greetings. They are about reflection, growth, and new beginnings.

As I look ahead, I’m deeply motivated to grow—not just in age, but in wisdom, character, and capacity. I want to build myself professionally and personally. My journey so far has been full of lessons, and I know there is much more to learn. I believe in continuous improvement, and that belief fuels my ambition to keep pushing forward.

This year, my focus is on professional development—gaining new skills, strengthening what I already know, and becoming more confident in my work. I plan to seek opportunities for learning, whether through training, mentorship, or real-life experience. I want to become more capable, resourceful, and impactful in everything I do.

At the same time, I also want to grow emotionally and mentally. Maturity isn’t just about work—it’s also about how we treat people, how we handle challenges, and how we understand ourselves.

So, on this birthday, I’m not just celebrating the past—I’m preparing for the future. I feel proud of the person I am becoming. I will keep dreaming, working hard, and building the life I envision.

Here’s to a new year of growth, purpose, and becoming the best version of myself.

The situation

This is something I encountered mapping bike infrastructure in the Austrian town of Neuhofen an der Krems: what one might assume is a continuation of a shared bike/pedestrian path over a pretty unimportant side road is actually a legal trap for cyclists and people walking. View it on Mapillary and look closely: a sign indicates that the cycling/walking path ends, only for it to continue right after the crossing. This means that pedestrians and cyclists no longer have right of way and have to yield to cars coming out of the residential road.

A safety nightmare

It is unfortunately a bit hard to make out using imagery, but the sight lines at this crossing are horrible. Not only is it basically impossible for cars from the south to see anyone cycling by before it’s too late, it’s also pretty much impossible to see any cars coming as a cyclist, even when slowing down. This is exactly the sort of situation one should avoid as a planner, but it is strikingly obvious that the bike path here was just an afterthought.

Intersections like this are common all over (Upper) Austria and often “solved” by applying this “interrupted cycle path” treatment. This means that if a cyclist and car were to collide here, the cyclist (person far more likely to die) would have to be the one explaining why they didn’t yield, and not the car driver (person driving a multiple-ton death machine) - just adding insult to (literal) injury. This is especially bitter because the bike path connects a fairly sizeable (by Austrian standards) part of town with the town center, while the side road only serves a handful of houses.

What should be done

See full entry

Location: Dambach, Neuhofen an der Krems, Bezirk Linz-Land, Upper Austria, 4501, Austria

My journey as an OpenStreetMap contributor began in 2022, with a humble yet impactful project: mapping roads in Mugu, Humla, and Jumla—three of Nepal’s most remote and mountainous districts. Since then, I’ve grown into an active mapper, dedicated validator, and proud member of the global OSM community. In 2023, I was recognized as an OSM Guru and listed among the top contributors, a reflection of my deep passion and consistency in open geodata contribution.

Areas of Focus My primary interest lies in mapping buildings and roadways, especially in critical and under-mapped areas. I’ve also actively contributed to tools like MapRoulette and MapSwipe, which help bring micro-edits and mobile contributions to the mapping ecosystem.

Highlighted Contributions “Map Roads, Make Your Way” Project Recognized as a top-quality mapper, I contributed significantly to this project—led by HOT, Open Asia Pacific Hub, KIRDARC, and OSM Nepal—focusing on mapping roads in Humla, Jumla, and Dolpa. This initiative was a pivotal moment for me, helping improve accessibility in some of the most remote regions of Nepal.

Digital and Spatial Technologies for Anticipatory Action Volunteered in this 5-day event organized by NAXA Nepal, where we mapped roads, waterways, buildings, and land use across six municipalities. Using ESRI imagery on the HOT Tasking Manager, we enhanced maps to support community resilience and disaster preparedness. We focused on: Mapping open spaces critical for evacuation and aid Digitizing health posts, schools, power lines Improving road networks and land use classifications

Global Solidarity Through Mapping Solidarity Mapathon for Myanmar (HOT) Climate Change Challenge with HOT, TOMTOM, Open Asia Hub Participated in multiple Kathmandu University mapathons—both as a mapper and organizer, including events under NEPGEOM

See full entry

Location: Junction, Dhulikhel-04, Dhulikhel, Kavrepalanchok, Bagamati Province, 09771, Nepal

Testing, Heading

Subheading, Subheading

  • List
  • List continued

Hello World!

I just completed my first university GIS course and I absolutely love mapping. The course enabled me to contribute to the Humanitarian OpenStreetMap team. This experience is excellent and I am thankful to sharpen my digitizing skills while helping others.

This Diary feature is new to me and I’m not sure what it does. Good to experiment with! :)

When I first received the email notifying me of my selection for the YouthMappers Leadership Fellowship 2024 in Thailand, it was a surreal moment. I was doing my assignments all frustrated but suddenly when the notification popped up, and I couldn’t contain my emotions. I jumped with joy, overwhelmed by the thought of being chosen for such an incredible opportunity. That email was the start of an unforgettable journey—one that would take me to new places, connect me with passionate individuals, and leave me with memories I’ll cherish forever. The dream of the dreamer started since then. The preparation for the fellowship began months in advance. YouthMappers, a global community of students, researchers, educators, and scholars that use public geospatial technologies to highlight and directly address development and environmental challenges worldwide ensured we were well-prepared with pre-departure sessions and constant communication through emails and WhatsApp. They guided us every step of the way, taking care of us with unmatched warmth and care. From learning how to say “Sawadike” (hello) and “Khapunka” (thank you) in Thai, to planning and packing for the trip, every moment was filled with excitement. The day of departure was momentous—my first international flight, passport in hand, and butterflies in my stomach. Along with my Nepali peers, we clicked countless photos at the airport, thrilled to embark on this journey. As our flight landed in Bangkok, the sparkling city lights welcomed us to a country that truly never sleeps. Angela, our warm and wonderful guide, greeted us at the airport, setting the tone for an amazing experience.

First Impressions and New Connections

See full entry

Jika anda ingin membuat/menyunting peta OpenStreetMap untuk wilayah Indonesia, akun ini menyarankan menggunakan foto udara dari BHUMI ATR/BPN yang digunakan oleh akun ini selama 2 bulan. Dari editan lamanya anda bisa menemukan link foto udara yang didapatkan.

BHUMI ATR/BPN dipilih oleh penulis akun ini karena kualitas fotonya lebih baik dari yang disediakan Bing/Esri, namun sama dengan OpenAerialMap dengan kualitas yang ditawarkan oleh para voluntir-voluntir OAM yang masih terikat erat dengan Humanitarian OSM sama primanya. Sayangnya, ruang lingkup OpenAerialMap sangat terbatas di Indonesia ketimbang BHUMI ATR/BPN.

Karena berupa data terbuka, dibuat oleh instansi pemerintah (Kementerian Agraria & Tata Ruang/Badan Pertanahan Negara (ATR/BPN)) dan tidak memiliki catatan hak cipta, per UU Hak Cipta No. 28/2014, pasal 43 ayat B, maka seharusnya BHUMI ATR/BPN terbuka untuk umum.

Di balik sisi positif ini, selalu ada kekurangan. Ada beberapa data foto udara berkualitas tinggi yang Kementerian ATR/BPN tidak miliki maupun datanya rusak dan/atau ketinggalan zaman sehingga perlu dilakukan beberapa langkah seperti kroscek ke foto udara Bing/Esri dan melakukan zoom in/out untuk melihat data yang “hilang” tersebut.

Sebagai penutup, ada dua harapan. Semoga voluntir OAM dari Indonesia memperbanyak foto udaranya, menyosialisasikan OAM kepada pengguna drone tanah air dan Kementerian ATR/BPN serutin-rutinnya membuat foto udara berkualitas untuk kebaikan bersama.

If anyone who want to edit Indonesian maps, I recommend using BHUMI ATR/BPN aerial imagery data as source. You may see the links from my last 2 months of renewed editing career of OpenStreetMap.

The primary reason I use BHUMI is their data quality is crisper and detail than Bing/Esri data (but as crisp as OpenAerialMap data), more extensive (OAM has limited coverage; in Indonesian context, their coverage is tinier than a grain of rice) and as a work of Ministry of Agrarian and Spatial Planning (Kementerian Agraria & Tata Ruang/Badan Pertanahan Negara), based from open data and their BHUMI website does not mention the copyright, it is in public domain (art. 43 point B of 2014 Copyright law/UU No. 28 Tahun 2024).

(You may object the last one, as I judge it solely on their website’s statement and my limited understanding to Copyright Law. In their website, the term of use is only limited to general responsibility using BHUMI ATR/BPN data. If you consider their data as copyrighted, that means 2 months’ worth of cleanup. Not an easy task, I hope don’t let it happen!)

However, some of their data might be not up to date or broken, so please cross-check with less than detail Bing/Esri data and zooming in and out, because you could get detail out of it.

I have big wish about this: ATR/BPN keep making high-quality imagery, and Indonesian OAM contributors to do the same, not just waking up when they do a mapathon!

Posted by pnorman on 10 June 2025 in English.

Load testing vector tiles

As part of bringing the new vector tile servers into production, I had to benchmark their performance. Since there’s a cache in front of the servers, it’s challenging to benchmark them accurately. Although we’ve never had a heavy load on the vector tile servers, we’ve been running raster tile servers for years.

All tile requests on the standard layer are logged, and from those logs, I can generate a list of tiles to benchmark the vector tile servers. The logs are stored as Parquet files, which I query using Amazon Athena, a hosted Presto database.

Vector tiles and raster tiles typically have different scales at the same zoom level. To convert raster tile requests to equivalent vector tile requests, I divide the x and y coordinates by 2 and decrease the zoom level by 1. I also skip zoom 0 raster tile requests to simplify the process, as these don’t affect performance since zoom 0 is always cached.

The OSMF shortbread tiles have a maximum zoom of 14. Lower scales (higher zoom levels) are achieved by overzooming on the client side. Requests from zoom 1 to 15 should have their zoom level lowered by 1. Requests from zoom 16 to 19 need their zoom level decreased by the difference between their level and 14. I divide the x and y coordinates by 2 the appropriate number of times to match the new zoom level.

Filtering to have only cache misses gets me a request list on the backend servers.

SELECT 
    CASE WHEN z > 15 THEN 14 ELSE z - 1 END AS v_z,
    bitwise_right_shift(x, CASE WHEN z > 15 THEN z-14 ELSE 1 END) AS v_x,
    bitwise_right_shift(x, CASE WHEN z > 15 THEN z-14 ELSE 1 END) AS v_y
    z, x, y
FROM fastly_success_logs_v1
WHERE year=2025 AND month=5 AND day = 1 AND hour = 1
    AND z >= 1
    AND cachehit = 'MISS';

Unfortunately, this is the wrong list.

See full entry

Posted by Jack_Regan on 10 June 2025 in English.

I’ve undertaken the task of mapping Inveralmond Industrial Estate, which lies close to my location but is currently not mapped in any great detail. While most buildings were drawn onto the map fifteen years ago, only about 25 businesses have been added since then—and I contributed half a dozen of those entries just a few months ago. At least two businesses that were added years ago have since closed permanently. Last Sunday, I conducted a preliminary survey of the area, capturing dashcam footage that helped me compile a list of fifty additional unmapped businesses. This number will likely grow substantially, as I left out the minor roads in the estate during this initial pass. My estimate is that the final count could easily reach one hundred businesses. This pattern reflects a broader issue: industrial areas consistently suffer from poor mapping coverage. That’s my take on it anyway from the areas I’ve looked at. I’m currently testing the iOS app Every Door, and plan to conduct comprehensive field mapping in the coming weeks. My goal is to document everything from the largest manufacturing facilities down to the most modest infrastructure, including grit bins. osm.org/#map=16/56.41782/-3.47651

Location: Inveralmond Industrial Estate, Tulloch, Bertha Park, Perth and Kinross, Scotland, United Kingdom

–Rapport de cartographie locale - Commune de Fareins (Ain)

  1. Présentation générale La commune de Fareins, située dans l’Ain en région Auvergne-Rhône-Alpes, compte environ 2 500 habitants. Son tissu urbain se compose d’un centre historique, de quartiers résidentiels, de zones rurales et d’infrastructures variées. Le travail de cartographie locale vise à fournir une représentation détaillée et à jour de la commune sur OpenStreetMap.

  2. Historique de la cartographie à Fareins

Début des contributions en janvier 2022 avec la création d’un compte OSM, initialement orienté vers les bornes incendie via OSM Hydrant.

Reprise active de la cartographie en juin 2024, avec des contributions hebdomadaires et une couverture étendue.

Activité parallèle d’un autre contributeur local,ArthµrC2016, sur certains thèmes similaires.

  1. Données cartographiées Cartographie considérée très complète sur les thèmes suivants :

Réseaux électriques (HTA, BT, poteaux, transformateurs, lampadaires)

Voirie : rues, trottoirs, passages piétons, ralentisseurs, limitations de vitesse

Mobilier urbain : bancs, panneaux, poubelles, défibrillateurs, aires de jeux

Points d’eau incendie : bornes, bouches

Bâti : maisons, piscines, haies, portails, clôtures, projets de construction

Végétation : arbres isolés, haies, bois, fossés, ruisseaux

Points d’intérêt : commerces, panneaux d’information, plans, œuvres d’art, points de vue

  1. Méthodologie et outils

Relevés sur le terrain avec prise de notes manuscrites et numériques

Utilisation de Mapillary, iD Editor, Map Complete et Street Complete

Consultation de données ouvertes (Volta, cadastre, orthophotos IGN)

  1. Dernières zones d’amélioration

Cartographie des poteaux télécom (en cours)

Mise à jour périodique des projets urbains

Vérification continue de l’actualité des données

See full entry

Location: Le Remolard, Fareins, Bourg-en-Bresse, Ain, Auvergne-Rhône-Alpes, France métropolitaine, 01480, France

Es ist ein gewaltiger Unterschied, ob man Blog-Beiträge erst nach zwei Klicks oder schon prominent auf der eigenen Benutzerseite eingeblendet sieht. Dann sollte man Blog-Beiträge auch löschen können. Was hier nun bei OSM gemacht wurde, ist für mich ein absolutes Unding.

Es kann durchaus sein, dass ich deshalb alle Blogbeiträge mit je einem Punkt für Überschrift und Inhalt ersetze.

Welcher Teufel hat jene geritten, die auf solche Ideen kamen?

The Community Bonding Period officially wrapped up on June 1, and the coding phase is already off to a solid start.

During CBP, we successfully migrated the legacy 3DMR repo from GitLab to the new official GitHub repo. This cleanup made collaboration and discussions way easier. I also dove into pygltflib to handle glTF files, experimented with the obj2gltf converter.

I spent a good chunk of time mapping with the iD and JOSM editors, focusing on features from my home village. It’s oddly satisfying to see buildings you’ve walked past for years show up as polygons and tags. I plan to keep adding more local features whenever time allows. I experimented rendering both my mapped data and some iconic Indian landmarks using OSM2World, let’s just say it made my village look unexpectedly fancy.

With coding underway, my first priority was building out the test suite. The project didn’t have one before, which would’ve made every upgrade feel like defusing a bomb in the dark. I’ve opened a PR for it, currently under review. While working on this, I found a few minor bugs lurking quietly in the codebase for years, filed them, fixed them, and thankfully had those PRs merged.

The Django 5.2 upgrade is nearly done and is clinging on my forked repo as i am writting this… Most dependency updates and refactoring are complete. Now I’m exploring edge cases, making sure nothing’s hiding in the shadows ready to throw a 500 error when nobody’s looking. Once the test suite merges, we’ll be in a much safer spot to modernize the stack.

On the personal side: I’m a long-distance runner and have been using summer break to improve my endurance. I run 5 to 7 kilometers daily, a good counterbalance to all the screen time, long debugging sessions, and occasional existential dread that come with working through old code 🙃. I also have a few books lined up, both fiction and non-fiction, hoping to get through them—unless I get distracted again.

See full entry

Location: Anchla Nawadih, Garhwa, Jharkhand, 822114, India