OSM exists now since more than 20 years. During this time, a tagging scheme evolved. It has undergone several changes since, is partly approved by the community, but never anything was forced. The freedom to invent new tags is considered a strength of OSM.

The OSM tagging scheme is clearly a result of swarm intelligence, which is sometimes said to be superior. I wondered how well this worked and thus started to analyse it. I’ll probably blog about this in a loose series of blog posts, starting today with looking at the highway tag, which according to the wiki identifies “any kind of road, street or path.”

In most cases, OSM elements are categorised in a hierarchical manner, with every step narrowing the meaning of the former step: highway=service, service=driveway, driveway=garage for example. A top level type=highway is missing and has to be derived implicitly.¹

The values of a certain tag should ideally be choosen in a way, that there is a match for every object in the real world belonging to this category. And there should be only one match. So, a highway=service must not qualify for a highway=footway at the same time.

Restricting my study further, I choose to look only at values used for linear features, that is, way elements. There are about three dozen of common values in the database. They match the values listed at the wiki page.²

 

The Present: Criteria used for Highway Classification

When you are faced by a highway feature on the ground, which is not yet in the database, you have to decide about the value of the highway tag.

While it’s sometimes really easy to decide which value is correct, other situations lead to endless discussions in the forums. Such discussions are a hint that there is something wrong with these values. So I asked myself, by which criterion the values have been decided. As it turns out, there are severeal criteria in use, and they are mixed.

… See full entry

🌍 Sobre o Projeto GeoCEP

O GeoCEP nasce como uma iniciativa voltada para a comunidade, com o objetivo de facilitar a busca e visualização de CEPs e endereços a partir de dados livres do OpenStreetMap (OSM).

O projeto reforça a importância da colaboração aberta, já que toda a base utilizada vem do esforço coletivo de milhares de mapeadores voluntários que contribuem diariamente para melhorar a qualidade da informação geográfica.

O aplicativo foi pensado para ser simples, acessível e inclusivo, servindo não apenas aos membros da comunidade OpenStreetMap, mas também a alunos, professores, pesquisadores e cidadãos em geral que buscam uma ferramenta confiável, educativa e livre para explorar os dados de endereços no Brasil.

… See full entry

I once walked past a small building, spotted that it’s got an address, and added it to OSM. Then I walked past it again, the building had its facade updated–and the address was nowhere to be seen.

We map a lot of ‘virtual’ objects in OpenStreetMap, boundaries and routes, but even addresses, the holy grail of survey, often end up virtual.

Take osm.org/way/1173366729: there isn’t an address on the building’s facade, yet 2GIS and Yandex.Maps have one.

Is there a private data agreement between the government and map services? 2GIS had some kind of city district polygons (elections related?) that someone even gave a review to asking what they were, and the Ministry of Information and/or of Digital Development already love giving out personal data of citizens to random software companies and banks in the name of ‘digitization’ (my bank’s app has everyone’s status with the police inspectorate and the psychoneurological dispensary and boldly let you see your own!), so it’s very likely.

P.S. The first building is on the cadastre, but there’s no building number, and the latter isn’t even on there at all :/ And don’t even ask whether one may copy from there.

I have noticed that the Apple mapping team, in their work within Kazakhstan, consistently mismapped various highway=* ways, for example:

• Mistagging of courtyard highways from highway=service to highway=residential.[2]
• Retagging of a highway=footway to a highway=residential, seemingly without any on-the-ground knowledge.[3][4]
• Various other bizarre additions or edits to service highways (also often mistagged), that I sometimes corrected or rolled back.[5]

If the Apple team does not have familiarity with how the highway tags are applied in a country[6] (a country here with a small OpenStreetMap community at that), or the specifics of urban development that span half the continent, then they, simply, should not map, and definitely not make the state of the map ever so slightly worse.

• [1] Betteridge’s law of headlines applies…
• [2] osm.org/way/458088367
• [3] osm.org/way/458088370 (both from the changeset 161673895)
• [4] Truly it isn’t a footway, as seen on Google Streetview, but may have been impassable for cars in the past!
• [5] Here, based entirely on my subjective idea that if there isn’t a curve in the highway area, then the highway centerline shouldn’t curve: osm.org/way/1192930242
• [6] There aren’t Kazakhstan-specific guidelines, but the Russian guidelines are applicable, where внутридворовые проезды (courtyard passages) are highway=service: osm.wiki/RU:Highway_classification

P.S. If anyone wants to fix the scary copy-pasted magically north-aligned square houses that were mapped all across the country, which previously, in part, made me register an alternative account and instead map pointless foreign stuff you’re welcome :P

UMAP OF THE ATTENDEES CITIES - III WORKSHOP ON PARTICIPATORY MAPPING AND SOCIAL CARTOGRAPHY - MPCS 2025

---

– Portuguese below

We would like to thank the 462 participants from 151 cities in eight countries for taking part of our event!

Tomorrow, August 27th, 2025, at 2 p.m. (UTC-3), the program of lectures, mapping workshop with OpenStreetMap, mapathon, and the release of the book Case studies in collaborative and participatory mapping (book in portuguese).

Information and registration on the portal:

https://eventyay.com/e/b4950013

Follow the entire program 100% ONLINE and LIVE on the Virtual Institute for Sustainable Development channel - IVIDES.org on YouTube:

https://www.youtube.com/@IVIDES

Event’s Chairwoman: Dr. Raquel Dezidério Souto (IVIDES and UFRJ, Brazil)

 

See the full map - Veja o mapa em tela cheia

Map Data (Dados do mapa) 2025 © OpenStreetMap Contributors. License.

 

---

 

… See full entry

A few bike lanes were added in the part of town I live in (yay!) and I’d like to add them.

However, I’ve mostly been using these apps to map things: * everydoor * map complete website * go map !! (rarely)

I cant find any way in map compete to add bike lanes – they added on the street, so effectively making the space for the cars narrower. Is there any simple way of going about and adding these types of lanes?

Thanks!

I’d like to share a simple method I’ve devised to map unfamiliar areas outdoors. Suppose you’d like create a GPX track of a park under the following constraints:

• GPS data is inherently inaccurate, so you’d like to walk each path exactly twice to improve accuracy.
• You’d like to finish an the exact point you started.
• You’re in the field, so you want to keep things simple and not use something too complicated.

Since the diary does not allow posting GIFs, the full post is in the community forum.

🎉 GSoC 2025 Final: Temporary Road Closures Database and API

Google Summer of Code 2025 • OpenStreetMap Foundation • Archit Rathod

After 15 weeks of intensive development, I’m thrilled to announce the successful completion of my Google Summer of Code 2025 project: Temporary Road Closures Database and API for the OpenStreetMap Foundation! 🎯

🚀 Live Demo - Try It Now!

Frontend: https://closures.osm.ch/
Backend API: https://api.closures.osm.ch/
GitHub: https://github.com/Archit1706/temporary-road-closures
GSoC Project: summerofcode.withgoogle.com

🎯 Problem Solved

OSM provides excellent static map data, but temporary road closures (construction, accidents, events) aren’t captured quickly enough for navigation apps. This project creates an open platform where communities can report closures in real-time and navigation apps can calculate closure-aware routes.

✨ What We Built

Complete Backend System

• FastAPI + PostgreSQL + PostGIS - Production-ready API with 25+ endpoints
• OpenLR integration - Universal location referencing for cross-platform compatibility
• OAuth2 + JWT authentication - Secure user management with Google/GitHub login
• Advanced spatial queries - Bounding box searches, proximity filtering, route analysis

Modern Frontend Application

• Next.js 15 + TypeScript - Interactive web interface with mobile optimization
• Leaflet maps - Real-time closure visualization with OpenStreetMap tiles
• Multi-step reporting - Guided forms for accurate closure submission
• Demo mode - Full functionality without registration for immediate testing

Closure-Aware Routing Innovation

• Valhalla API integration - Calculate routes that avoid relevant closures
• Transportation filtering - Car, bicycle, and pedestrian-specific closure relevance
• Route comparison - Direct vs. closure-aware route analysis
• Real-time optimization - Live route calculation considering current conditions

🌟 Key Innovations

OpenLR Integration

… See full entry

24.08.25 Все добре 😑

 ‼️

Mały wąwóz

( kilka - kilkadziesiąt metrów, bez wody / PL: 1-2.5 m szer. i mniej)) osm.wiki/Pl:Tag:natural%3Dgully

Żleb

• osm.wiki/Pl:Tag:natural%3Dearth_bank
• https://pl.wikipedia.org/wiki/%C5%BBleb

Dolina

• głównie do oznaczenia nazwy osm.wiki/Pl:Tag:natural%3Dvalley

Skarpa

• uskok skalny natural=earth_bank + earth_bank=scarp

Strome, trawiaste zbocze natural=earth_bank + earth_bank=grassy_steep_slope

Latitude and Longitude: The Foundation of Map Reading

… See full entry

tl;dr: slightly less than an hour.

This was prompted initially by a forum comment (I can’t actually remember exactly where or by whom) that creating maps based on OSM was for “developers” and not “normal people” (not in those exact words), and by the thread here. The “slightly less than an hour” actually includes setting up a development environment from scratch on a new PC.

On that new PC I’ve already installed a text editor and a web server (“apache2”).

cd ~/src
git clone https://github.com/SomeoneElseOSM/SomeoneElse-vector-web-display
git clone https://github.com/systemed/tilemaker

In the first of those repositories there are a selection of map styles, including one that uses the OSMF demo vector tiles. Let’s first test that that works:

… See full entry

I checked my changesets and it seems i broken my editor: I added data at location 0,0. This has to be reverted but I’m to tired and might introduce more mistakes.

So a job for tomorrow.

(english translation by OpenAI/chatgpt)

RETEX: Tagging Choices for My Urban Recycling Trekking

Hesitations, discussions, collisions with other contributors, changes, hesitations… but convergence.

to be continued maybe:

• journal entry (upcoming): Existential questions about my encounter with Panoramax

At first, tagging the operator since it’s the target of the trekking.

The operator is known here as GPSEO, or GPS\&O, or Grand Paris Seine and/& Oise… Which name to choose? Likewise, I encountered clothing containers from Le Relais or Emmaüs, and again, which names should be used?

my encounter with Wikidata

Thanks to the forum, I was guided towards Wikidata, which allows assigning a unique code to a large number of resources (companies, operators, municipalities, associations, widely known people, …).

Once the resource in question is given a Wikidata code, its Wikidata entry contains important data (name, website, Wikipedia reference, revenue, …) and thus allows all Wikipedia collaborative applications to access these elements in a common way. So it is enough to reference the operator’s Wikidata code in OSM tags to identify it uniquely and stably. From this code, it’s easy to retrieve the operator’s website, its Wikipedia reference, and other useful information without having to explicitly add them as OSM tags (which would require updating OSM every time the data changes).

A single concession seems necessary: I retrieved the operator’s official name from its Wikidata entry and added it as an OSM tag for readability.

And therefore:

operator=GRAND PARIS SEINE ET OISE operator:wikidata=Q19945071

Tags deliberately omitted because the information is evolving and can be found in the operator’s Wikidata article:

operator:wikipedia, operator:website, operator:short

And similarly:

operator=Emmaüs operator:wikidata=Q989437

operator=Le Relais operator:wikidata=Q16654240

ref or operator:ref

… See full entry

RETEX : Les choix de tag pour mon trekking urbain recyclage

Hésitations, discussions, collisions avec d’autres contributeurs, changements, hésitations, … mais convergence.

à suivre peut-être :

• entrée de journal (à venir) : Questions existentielles sur ma rencontre avec panoramax

Au départ, taguer l’opérateur puisque c’est la cible du trekking.

L’opérateur est connu ici sous le nom GPSEO, ou GPS&O, ou Grand Paris Seine et/& Oise …. . Quel nom retenir ?
De même, j’ai rencontré des conteneurs à vêtements du Relais ou de Emmaüs et, là encore, quels noms retenir ?

ma rencontre avec wikidata

Grâce au forum, j’ai sur ce sujet été orienté vers wikidata qui permet d’affecter un code unique à un grand nombre de ressources (sociétés, opérateurs, communes, groupements, personnage à portée large, …).

Une fois la ressource concernée dotée d’un code wikidata, son entrée wikidata contient les données importantes (nom, site web, référence wikipedia, chiffre d’affaires, … ) et permet ainsi à toutes les applications de la sphère collaborative wikipedia d’accéder de façon commune à ces éléments. Il suffit donc de référencer le code wikidata de l’opérateur dans les étiquettes OSM pour identifier celui-ci de façon unique et stable. A partir de ce code, il sera aisé de retrouver le site WEB de l’opérateur, sa référence wikipedia et autres renseignements utiles sans avoir à les mettre comme étiquettes explicites de OSM (ce qui obligerait à mettre à jour OSM chaque fois que ces données changent).

Une seule concession nécessaire, me semble-t-il : j’ai récupéré le nom officiel de l’opérateur dans ses données wikidata et l’ai mis en étiquette OSM pour plus de lisibilité.

Et donc :

operator=GRAND PARIS SEINE ET OISE
operator:wikidata=Q19945071

étiquettes omises volontairement car les informations sont évolutives et peuvent être trouvées dans l’article wikidata de l’opérateur :

operator:wikipedia, operator:website, operator:short

Et, de même :

… See full entry

Night bed

Q4205816 and Q131521518 might seem two pretty obscure numbers formatted in an odd way. Plug them into a Wikidata Timeline, and you can see what has and has not been recorded

Greetings whoever is reading this, including my future self who may be the only audience.

I was invited earlier this year to take part in an exhibit called [“Compass Roses”] (https://www.compassroses.art/), which will be on view at Opalka Gallery in Albany, NY this Fall.

“Compass Roses: Maps by Artists is a national artwork co-curated by Nadine Wasserman and Renee Piechocki. The project offers a selection of maps created by visual, literary, and performing artists. “

I chose to make a map of Gun Violence Memorials in Albany. I was inspired by a memorial called Chyna’s World, a mural in memory of an 18-year old high school senior named Chyna Forney. Chyna was killed in crossfire in an incident when her boyfriend fired over 30 rounds at another man. The mural is painted at the location where the incident took place. After seeing this mural, I wondered if there were others like it.

I have been aware of the problem of gun violence for this entire century. I have perceived it from three aspects that touch but are distinct: school shootings, the eclipse of streetfighting, and police murder. I might say more about those three in this diary over the next few months, but for now I will just say that these have been buried the past five years by the sheer numbers of tragic gun deaths in this country, in my city, in my neighborhood, on my street. There were 10 shootings on my street when the world broke down during New York Pause, from April 27 2020 a few weeks into the pandemic through December 19, 2021. The nadir was the late night murder of 15-year old Destiny Greene, on a magical little street called Wilbur. I remembered the temporary monument that Destiny’s family had set up on Wilbur Street, and the attempts by some neighbors to set up a permanent memorial for shooting victims.

… See full entry

agondjé château