OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

Posted by jbcharron on 22 January 2026 in French (Français).

Cet article est un retour d’expérience sur la contribution aux commerces sur plusieurs années dans une métropole.

La contribution aux commerces est un sujet qui a toujours eu une importance dans la communauté OSM, car ce sont des données essentielles à tout à chacun au quotidien pour se repérer dans l’espace et répondre aux besoins primaires. C’est aussi une thématique de contribution qui permet de rendre OSM crédible auprès du grand public face aux applications et plateformes développées par les GAFAM et un point d’entrée pour commencer à contribuer.

Un regain d’intérêt a eu lieu sur cette thématique dans la communauté OSM France depuis environ 1 an avec l’émergence de nouveaux outils de contribution.

Une des difficultés étant d’assurer une pérennité de la donnée dans le temps, de l’exhaustivité et de la qualité (cela s’applique bien sûr à toute donnée dans OSM).

OSM vs réalité

Premier défi rencontré dans mon territoire, les commerces ont été mis à jour en majorité il y a plusieurs années par des contributeurs locaux et plus grand-chose ne correspondait à la réalité. En cause notamment la transformation du centre-ville, le développement de centres commerciaux et zones commerciales en périphérie de la métropole et la transformation des modes de déplacements en zone urbaine.

Dans cette situation, la contribution depuis le terrain était obligatoire pour pouvoir mettre à jour rapidement les commerces.

Ils existaient déjà plusieurs outils mobiles à disposition pour contribuer aux commerces sur le terrain :

See full entry

Posted by jonnymccullagh on 22 January 2026 in English.

A Mapathon has been organised for Saturday 21st February 2026 from 11am to 1pm in Belfast. Pizza will be provided at QUB Geosciences building on Elmwood Avenue behind the Student’s Union. Numbers are limited to 30 attendees.

Sign up on eventbrite here: https://www.eventbrite.co.uk/e/belfast-openstreetmap-workshop-tickets-1981332125724

Event Location: osm.org/#map=19/54.585251/-5.939057

Location: Malone Lower, Windsor, Belfast, Belfast City District, County Antrim, Northern Ireland, United Kingdom
Posted by steveman1123 on 22 January 2026 in English.

I’ve dabbled with overpass turbo on and off for maybe a year now, but I feel like I’ve just now started to get a better understanding of how it works.
I’ve been using it to find hikes that can lead to ruins or abandoned places:

(
nwr['abandoned']({{bbox}});
nwr['historic'='ruins']({{bbox}});
);
out;

and for campsites:

(
nwr['tourism'='camp_site']({{bbox}});
nwr['tourism'='camp_pitch']({{bbox}});
);
out;

And while those are certainly useful, especially for hard to find places that won’t show up on AllTrails or other popular spots, I didn’t feel like I learned much since they’re fairly simple queries.
The way I understand it at the moment: the Overpass query language treats things as sets. There is a default set (named “_”) that gets populated with the queries.

In the case of the camping, there are two lines enclosed in parentheses which groups the two requested object sets as a union (or OR operation) to store in the default set which is then output with the “out” statement
The “nwr” is a shorthand for “node” “way” “relation” so it indicates what kinds of objects we’re looking for (we could replace it with any one type depending on what we’re looking for).

The ({{bbox}}) portion indicates where to look for the objects, {{bbox}} is a predefined area based on the overpass turbo site’s map, otherwise it should be set to a 4-value array indicating the borders of the area to search (read more here)

Let’s break down the next query I’ve found to be very useful, finding local cafe’s! (Google’s results have been getting pretty bad and overlooking a bunch of great options)

[out:csv(
         name,
         "addr:housenumber",
         "addr:street",
         "addr:city",
         website;true;",")];
nwr['amenity'='cafe',i]["name"!="Starbucks"]({{bbox}});

out;

There’s a couple familiar things there: “out”, “({{bbox}})”, and “nwr”

nwr['amenity'='cafe',i]["name"!="Starbucks"]({{bbox}});

See full entry

Las notas de OpenStreetMap son una ventana al conocimiento local y a la colaboración en tiempo real. Para aprovechar mejor esta información, he desarrollado un conjunto de scripts en Bash que permiten mantener una base de datos actualizada con las notas, sus comentarios y cambios de estado en menos de 10 segundos.

El sistema se apoya en herramientas comunes de Linux (curl, awk, sed, grep, jq, psql, entre otras), evitando dependencias complicadas. Con ellas se procesa el dump diario de notas del Planet, se convierte en CSV, se carga en PostgreSQL y se georreferencia por país o límite marítimo. Un daemon se encarga de mantener la base sincronizada con el API de OSM.

Esto abre la puerta a múltiples aplicaciones: análisis de actividad comunitaria, visualización de notas recientes por región, o desarrollo de nuevas herramientas basadas en este componente. El código está disponible en GitHub: OSM-Notes-Ingestion.

¡Me encantaría conocer tus ideas y aportes!

Przystanki w Powiecie Koszalińskim

Zabieram się za dodawanie i poprawianie nazw przystanków według uchwał przystankowych konkretnych gmin w Powiecie Koszalińskim. Linki do uchwał: * Gmina Będzino, * Gmina Mielno, * Gmina Biesiekierz, * Gmina Sianów, * Gmina Polanów, * Gmina Bobolice Nie znalazłem nowszej wersji * Gmina Świeszyno

Location: Nowobramskie, Osiedle Morskie, Koszalin, województwo zachodniopomorskie, 75-132, Polska

Years of Growth and Community Impact

I joined the Humanitarian OpenStreetMap Team with a simple interest in mapping, not fully aware of how profoundly it would shape my personal journey and the growth of the OSM Kenya community. What started as basic mapping tasks gradually evolved into deeper involvement in humanitarian mapping, data quality, and community-driven impact.

Over these years, HOT has played a critical role in strengthening my technical skills and perspective on geospatial data. Through initiatives such as the ESA Hub Validation Fellowship, I progressed from mapping to advanced validation and third-pass quality assurance, where accuracy and data integrity are paramount. I contributed to humanitarian projects in Sudan, supported disaster response mapping for Hurricane Mellisa in Jamaica, and worked on local risk-reduction initiatives such as the Elgeyo Marakwet landslide mapping project. These experiences highlighted how reliable geospatial data directly supports preparedness, response, and resilience.

HOT’s impact has extended well beyond individual growth to the wider OSM Kenya community. Through continuous collaboration on HOT Tasking Manager projects and capacity-building programs like FAir, our community has improved technical skills, strengthened quality standards, and fostered a strong culture of mentorship and collaboration. In addition, OSM Kenya has partnered with HOT on thematic campaigns that address social as well as physical vulnerabilities. One notable example is the Mental Health Mapping Campaign, where our community collectively contributed to mapping essential services that support mental health awareness, access, and inclusion demonstrating that humanitarian mapping goes beyond disasters to support overall community well-being.

See full entry

Posted by BeardMD on 17 January 2026 in English.

Earlier this week, I accepted a PR to our codebase that made a bad and duplicated phone numbers. What happened was, that we use contact:phone=* per convention, but many entries used phone=*, which was not detected by our dupe scanner.

That’s 100% on me. I should have been more vigilant on that one, should have checked better (the few I checked on did not have phone=, so that’s another lesson for the books), and should have checked more vigilantly afterwards as well.

What I did: wrote a rescue to check all 600 edits we did, removed phone= dupes, and moved all phone= that were still there to contact:phone= in the process.

We also do contact every albergue we list (and thus sync) and ask them about their preferred/working phone numbers. So we went ahead and removed stale numbers that no longer worked, and updated those that did to a fully working set.

Of course the code is now fixed as well, and all edits have been too. Sorry again, this is 100% on me.

Location: As Granxas, Melide, Terra de Melide, A Coruña, Galicia, 15800, Spain

I’ve run into a strange behaviour in my OSM user diary entry when documenting a batch/ffmpeg command.

This line in a code-block (ignore formatting):

ffmpeg select=eq(pict_type,I)</br>

is automatically turned into:

ffmpeg https://wiki.openstreetmap.org/wiki/Tag:select=eq(pict_type,I)

This happens even inside code blocks (<pre>, fenced code, etc.). It does not happen if I add spaces around the = (e.g. select = eq(pict_type,I)), but I cannot change the code because it must stay exactly as written.

<nowiki>...</nowiki>, <pre>...</pre>, <nowiki><pre>...</pre></nowiki> and similar combinations do not stop the autolink.

Is this a known issue with the OSM Wiki parser or is this a feature?

In order for OpenStreetMap to thrive, we need to attract and retain new mappers. To be welcoming to newcomers, we should avoid high barriers to starting mapping and instead support contributions that can be made with limited time, context, and experience. StreetComplete is a great example of this approach: by asking simple, well-scoped questions, it enables contributors to improve data quality in small, incremental steps. An effort-inclusive tagging philosophy builds on this idea by encouraging tagging schemas where each additional piece of information can be added independently and still be useful on its own. For example, amenity=bench is still a bench regardless if mapper knew about backrest=* and armrest=*.

I am writing this because I have encountered cases where newcomers are advised to follow practices that I consider unnecessarily demanding for basic contributions. A particularly stark example appears in the context of CCTV and ALPR mapping, where a sub-community recommends mappers to take high-resolution photographs, research manufacturers and exact models at home, and consult product datasheets for adding a single camera to OSM. While such detailed work can be valuable, it not only risks discouraging participation, but also makes incorrect data harder to detect if mapper misidentifies the model.

See full entry

Posted by Greg_Rose on 15 January 2026 in English.

In Fall 2024, I broke my radius (arm) at the wrist of my dominant hand, and didn’t map at all for 2 months, gradually picking things up as my arm healed and gained strength. It was agonizing to not have my daily OSM fix - and a palpable relief when my wrist could once again handle an extended session with a mouse.

Not content with my previous mapping outage, in Fall 2025 I had a cancerous tumor in my parotid (cheekbone salivary gland) removed - except that a relatively straightforward 2 hour surgery turned into a 13-hour marathon and an overnight hospital stay ballooned into 8 days in a hospital bed. The cancer had spread to lymph nodes, to one of my jugular veins and into muscle tissue in my neck. Recovery from the surgery turned into immediate chemotherapy + immunotherapy and radiation.

So now I map when I’m able, which unfortunately is not very frequently. My #Mali project gathers dust, with almost all of my current OSM edits focused around related work with my one remaining freelance client. There does appear to be light at the end of the tunnel (I’m pretty sure it’s not a train). My body has responded well to treatment, and there’s talk of moving me off chemo and onto straight immunotherapy. Looking forward to that possibility.

All of this to say: treasure the time you have. If the difference you make is measured in your OSM edits, then by god make those edits. But more importantly, if the difference you make is measured through those around you that are intertwined into your life, make sure you give sufficient time to them. Your life-changesets are important too.

The More You Know…… ;)

GR

Posted by zorothepirate on 14 January 2026 in English.

I’ve been updating bus routes;
it’s a fun task, but takes a real long time; slow progress in the wiki: osm.wiki/Braga

i’ve added tons of sidewalks and crosswalks and i’m totally happy to see them start rendering on OSMAnd;

if ppl actually used OSM while driving they would get vocal warnings for crosswalks, i’ve tried it before and it works and its really good to know whenever you approach a sidewalk as a driver; ofc this is a feature which is pedestrian centered, so the whole point is to especially help people navigate on foot; also i really like the added complexity layer when sidewalks appear on the map and you can actually start navigating the city through sidewalks, footways, footpaths and informal paths, the city is more interesting when seen through a walking perspective

we need to properly address this, i’m thinking of starting activism, we cant have 300 ppl getting run over per year (just in braga!)

i’m quite confused if and how exactly i should mark informal crossings (especially in cases where theres heavy crossing pedestrian and bike traffic (see: node/1888043292); it may seem easy but im afraid that ppl could get misled into crossing in a bad place;

there should be a more compreensive aproach to these situations so we can map this for safety first; then, we should take this stuff to city hall and press for more permanent proper solutions, like new crossroads and better safety measures!!!

as to sidewalks, it’s a bad situation; there are not as many as i believe there should be (this gets really bad as you get farther from the city center).

so many of the newer roads and rotundas dont even have a proper sidewalk, like whaaat;

See full entry

Spherical panoramics in Palmanova, Italy by Protezione_Civile_FVG_Rilievi @ Mapillary, CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0>, da Wikimedia Commons © Protezione_Civile_FVG_Rilievi @ Mapillary, CC BY-SA 4.0 https://creativecommons.org/licenses/by-sa/4.0, da Wikimedia Commons

Questa notizia è stata segnalata dall’utente fabiotofy che ringrazio per la cortesia.

La Protezione civile del Friuli Venezia Giulia ha recentemente montato1 una fotocamera Insta360 Titan 11K sul tettuccio di un proprio veicolo 4x4 e percorso le strade meno mappate della Regione autonoma per acquisire fotografie a 360° ad altissima definizione, che poi vengono caricate su Mapillary.

L’intento è quello di permettere ai cittadini, alle amministrazioni e ai soccorritori di avere a disposizione gli stessi strumenti e di migliorare conseguentemente l’efficacia e la rapidità degli interventi di emergenza del numero di emergenza unico europeo (NUE) 112.

Il progetto ha finora raccolto oltre 150 mila foto con una copertura totale di più di 500 chilometri.

See full entry

Location: San Paolo, Partidor, Udine, Friuli-Venezia Giulia, 33100, Italia