Style | Standard • Cards

OpenStreetMap Blogs Last Update:

Florian Lohoff - Nov 20

RouteQA2: How to use - Part 1

So now that RouteQA2 is running for Germany for a week i share some ways of how i use it to debug routing in Openstreetmap. I am doing that since 2013 so one gets a trained eye for things which are not obvious.

First lets have a look at the Grid. Its basically the sum of all routes, unified by their segments. Each segment gets counts on how many routes it is used by, which clusters these 6 hours ago

So now that RouteQA2 is running for Germany for a week i share some ways of how i use it to debug routing in Openstreetmap. I am doing that since 2013 so one gets a trained eye for things which are not obvious.

First lets have a look at the Grid. Its basically the sum of all routes, unified by their segments. Each segment gets counts on how many routes it is used by, which clusters these routes belong too and links to some of the routes.

As all nodes we calculate routes between are on the higher class network, e.g. tertiary or better, the assumption is that all routes are basically "through traffic" and should not leave the higher class road network.

So when looking at the grid a lot of violations of this assumption can be seen, and sometimes even be fixed.

For example see this screenshot. You can see a thin blue line passing through a farmyard. Its thin because its only a few routes, possibly only a single one.

♦

Looking at the data it shows all the road segments are only tagged highway=service not a driveway. So routing assumes it okay to use it. So - retag it as service=driveway and the issue should be gone.

But even further. By inspecting the aerial imagery one can see gates or lift gates in all directions. Adding the gates, and the inner road segments with access=private.

After 30 minutes you can see routing has changed. The road segments on the farmyard have vanished from the grid. They will be shown for the next 24h as red dotted lines fading lighter over time.

♦

And this is how it looks for a single route in the notification when the check came back. You see the old and the new route. And the changeset bounding boxes.

♦

6 hours ago

OpenStreetMap User's Diaries - Nov 19

My Experience at SOTM Nigeria Uyo 2026

My experience at state of the map Nigeria was a wonderful experience. I was given the privilege to volunteer as the registrar for SOTM 2026. And I was given a certificate, I also got a badge from sci stater. I love my experience there!! Thank you #uniquemappersnetwork

a day ago

My experience at state of the map Nigeria was a wonderful experience. I was given the privilege to volunteer as the registrar for SOTM 2026. And I was given a certificate, I also got a badge from sci stater. I love my experience there!! Thank you #uniquemappersnetwork

a day ago

OpenStreetMap User's Diaries - Nov 19

State of the map Nigeia, Uyo 2026.

Am here at SOM Nigeria, Uyo2026. Having had knowledge of GIS and Remote sensing, my mind is opened up for a wonderful experience in actually getting ready to contribute to global mapping initiative. I can’t wait to do it.

a day ago

Am here at SOM Nigeria, Uyo2026. Having had knowledge of GIS and Remote sensing, my mind is opened up for a wonderful experience in actually getting ready to contribute to global mapping initiative. I can’t wait to do it.

a day ago

OpenStreetMap User's Diaries - Nov 19

A thought on careful, source-backed mapping

Good maps grow through careful observation, clear sources, and respectful review. Before changing a feature, it helps to check the existing data, explain the reason in the changeset, and confirm that the published result reflects the intended edit.

For boundary-related work, I think it is especially useful to keep official reference maps clearly attributed and separate from OpenStreetMap a day ago

Good maps grow through careful observation, clear sources, and respectful review. Before changing a feature, it helps to check the existing data, explain the reason in the changeset, and confirm that the published result reflects the intended edit.

For boundary-related work, I think it is especially useful to keep official reference maps clearly attributed and separate from OpenStreetMap’s community-maintained data. A detected change should lead to an evidence-based review of the object history and sources, rather than assumptions about the contributor’s intentions.

This general project note is shared by the operator across accounts in the same mapping workspace. It does not announce a map edit or claim a community consensus.

a day ago

OpenStreetMap User's Diaries - Nov 19

Roslyn, South Dakota

When I started the street names hadn’t even been added. Now every building and nearby land use is mapped to the best of my ability using the Day County data.

a day ago

When I started the street names hadn’t even been added. Now every building and nearby land use is mapped to the best of my ability using the Day County data.

a day ago

Florian Lohoff - Nov 18

OpenStreetmap RouteQA refresh

2013 i started a project to monitor routing in parts of Germany. I recalculated ~200K routes every 30 to 60 Minutes and watched them over time whether they changed due to OpenStreetmap data changes. It was a very clunky UI and nobody really understood it, and its notifications. So for 13 years i mostly fixed routing issues coming up in that tool by myself. I covered the higher class road network 2 days ago

2013 i started a project to monitor routing in parts of Germany. I recalculated ~200K routes every 30 to 60 Minutes and watched them over time whether they changed due to OpenStreetmap data changes. It was a very clunky UI and nobody really understood it, and its notifications. So for 13 years i mostly fixed routing issues coming up in that tool by myself. I covered the higher class road network from tertiary to motorway in a part of Northrhine-Westfalia.

The last couple of days/weeks i reimplemented everything. A new engine to calculate the routes based on C++, OSRM and Postgres/Postgis and Tilemaker and a Webinterface based on Mojolicious, Maplibre, Leaflet. And here we are - RouteQA2.

As i gained a lot of speed i am now easily running on whole of Germany. Most of the time is spent on bringing the Germany.pbf up to date. The calculation of the 1.25 Million routes takes only 128 Seconds. So we are happily running on a 30 Minute cycle.

I have 58K nodes in Germany split in 4510 Clusters. Routes are calculated any2any within each cluster. Whenever time, distance or geometry changes a notification for that cluster is being sent that something changed.

Changes are being matched on changeset bounding boxes, so one can actually see where the changesets were in relation to the changed route geometries.

Mappers may then analyze whether change was legitimate change, an accidental breakage, or a fix for some issue. Processes like opening notes to track construction. Remove forgotten tags or quickly fix leftovers are now possible within 30 minutes.

Its not a static analysis tool for OpenStreetmap data. It does not make any sense out of the current data, or tries to tell whether the current state is right or wrong. It shows you how the Routing adapts to changes to OpenStreetmap data and gives mappers the opportunity to quickly inspect possible errors.

Mappers can log in and tag notifications with typical issues, comment on notifications if there are additional findings, and create their very own RSS/Atom feed for notifications.

Some stats for a typical run:

Stats: 4510 clusters, 58755 nodes, 1259544 routes calculated (15 without route)
Stats: OSRM returned 2218420 routes (26309 equivalent alternatives), 244 geometry checks
Stats: 0 new, 1259483 unchanged, 61 changed, 6 notifications
Stats: runtime 274.9 s (routing 128.9 s)

All routes are then brought together to show the grid of the network which was used the last time all routes were calculated. This helps to get a glimpse on what the monitored network is. With a trained eye one can also spot issues here e.g. roads which are completely unused etc.

So have a look: osm.zz.de/routeqa2

So here some Screenshots:

♦ ♦ ♦

2 days ago

OpenStreetMap User's Diaries - Nov 18

Betrachtung des NSI als Teil des osm-apps-catalogue aus Sicht der Barrierefreiheit

Der richtige Name ist noch kein stufenloser Weg

Stellen wir uns einen Umstieg in Wien vor. Die Straßenbahnlinie ist richtig benannt, das Verkehrsnetz stimmt, der Bahnsteig liegt an der richtigen Stelle. Am Eingang hängt ein Zettel: „Aufzug außer Betrieb. Bitte den gegenüberliegenden Zugang benutzen.“ Wer einen Rollator schiebt, möchte wissen, ob dafür eine Bordsteinkante überwunden werden muss. 2 days ago

Der richtige Name ist noch kein stufenloser Weg

Stellen wir uns einen Umstieg in Wien vor. Die Straßenbahnlinie ist richtig benannt, das Verkehrsnetz stimmt, der Bahnsteig liegt an der richtigen Stelle. Am Eingang hängt ein Zettel: „Aufzug außer Betrieb. Bitte den gegenüberliegenden Zugang benutzen.“ Wer einen Rollator schiebt, möchte wissen, ob dafür eine Bordsteinkante überwunden werden muss. Wer den Zettel nicht sehen kann, braucht die Information erst einmal in einer anderen Form. Und wer die Ersatzroute für OpenStreetMap prüfen will, steht vor einer ganz praktischen Frage: Welches Werkzeug nehme ich mit, und was kann ich damit verlässlich feststellen?

Was der Apps-Katalog noch nicht verrät

Der OSM Apps Catalog führt Anwendungen und Dienste zusammen, die OSM-Daten nutzen; seine Angaben stammen unter anderem aus dem OSM-Wiki, Wikidata, GitHub und Taginfo. Für diesen Beitrag habe ich den Katalogstand vom 18. November 2026 ausgewertet: Von 2.353 Einträgen hatten nur 13 überhaupt einen Wert im Feld screenReader, ausdrückliche Nein-Angaben mitgezählt. Das bedeutet nicht, dass nur 13 Apps mit Screenreadern bedienbar sind. Es bedeutet, dass jemand, der darauf angewiesen ist, diese Frage anhand des Katalogs fast nie entscheiden kann.

Dabei gibt es gute Werkzeuge: WalkersGuide beschreibt Kreuzungen und ist für die Nutzung mit TalkBack ausgelegt; Touch Mapper erzeugt tastbare Karten; AccessMap berücksichtigt persönliche Präferenzen zu Steigungen und Hindernissen, ist aber auf ausreichend gute lokale Fußwegdaten angewiesen. Im Katalog würde ich deshalb zwei Fragen nebeneinanderstellen: „Was weiß die App über die Zugänglichkeit eines Ortes?“ und „Kann ich die App selbst bedienen?“ Ein Rollstuhl-Routingprofil beantwortet die zweite Frage ebenso wenig, wie eine tastbare Papierkarte die Unterstützung einer Braillezeile belegt.

Was der Name Suggestion Index damit zu tun hat

Der Name Suggestion Index ist im Katalog bereits verzeichnet. Er ist kein zweites App-Verzeichnis, sondern eine Sammlung wieder-verwendbarer Tagging-Vorlagen für Marken, Betreiber, Verkehrsnetze und Flaggen; iD schlägt damit passende Tags vor, Every Door nutzt den Index beim Aktualisieren von POIs, und Osmose kann damit mögliche Marken-Zuordnungen zur Prüfung melden (NSI im OSM-Wiki). Interessant wäre für mich weniger ein weiteres Logo im Katalog als die Auskunft: Welche App verwendet den NSI wofür? Einen Vorschlag beim Tippen zu bekommen ist etwas anderes, als bestehende Objekte nach möglichen Fehlern zu durchsuchen.

Gerade für die Geowissenschaften lohnt sich ein Blick über die Ladenketten hinaus. Im österreichischen NSI-Bestand findet sich das BEV als Betreiber von Vermessungspunkten; für Messstationen ist GeoSphere Austria hinterlegt. Wer im Gelände eine entsprechend beschriftete Station vor sich hat, muss die Betreiberkennung nicht abtippen. Der Vorschlag verrät aber weder, was dort gemessen wird, noch ob die Station in Betrieb oder öffentlich zugänglich ist. Gerade diese Grenze macht die Vorlage nützlich: Sie erspart Schreibarbeit, ohne den Befund vorwegzunehmen.

Auch beim Wiener Umstieg ist die Trennung wichtig. Die NSI-Vorlage für Straßenbahnrouten in Wien unterscheidet network=VOR von operator=Wiener Linien. Sie gilt für die Route, nicht pauschal für jeden Bahnsteig, Eingang oder Aufzug in ihrer Nähe; für Stationen und Haltepositionen unterstützt der NSI laut seiner technischen Dokumentation derzeit keine entsprechenden Vorlagen. Ein korrektes operator:wikidata ist also ein Gewinn. Für wheelchair=yes ist es kein Beleg.

Ein gemeinsamer Qualitätstest für einen Mapping-Nachmittag

Ich würde klein anfangen: ein Umsteigeknoten, zwei Zugänge, ein Team aus Mapper:innen, Menschen mit unterschiedlichen Mobilitäts- und Wahrnehmungsbedürfnissen und jemandem aus Vermessung oder Betrieb. Nicht alle müssen dieselbe App bedienen. Wohl aber sollte jede Person einen Befund beisteuern und später erkennen können, was daraus geworden ist.

  • Vorher: das Werkzeug testen. Lässt sich ein vorhandenes Objekt ohne Karten-Tippen auswählen? Kann eine blinde Mapper_in den vorgeschlagenen Betreiber vor dem Speichern per Screenreader kontrollieren? Wird eine Meldung auch als Text ausgegeben, wenn ein gehörloser Kollege den Signalton nicht hört? Das Ergebnis gehört mit Plattform, Version und Testdatum in die App-Dokumentation. „Nicht getestet“ wäre eine ehrliche und nützliche Katalogangabe.
  • Draußen: Vorschlag und Beobachtung auseinanderhalten. An der Ersatzquerung zählen die engste nutzbare Breite, die Bordhöhe und eine auffindbare taktile Führung. Wer misst, sollte den betroffenen Abschnitt und die Messmethode so festhalten, dass ein zweites Team dieselbe Stelle wiederfindet. QField kann etwa die Positionsqualität dokumentieren; ein präziser Standort ersetzt aber keine Messung der Bordhöhe. Die vorübergehende Aufzugsstörung würde ich im Betriebskanal mit Zeitstempel führen, nicht als dauerhafte bauliche Eigenschaft eintragen.
  • Nachher: den Fehler an der richtigen Stelle beheben. Ist nur ein OSM-Objekt falsch zugeordnet, wird dieses Objekt anhand des Befunds korrigiert. Ist die Vorlage selbst falsch oder regional zu weit gefasst, gehört ein belegtes Beispiel zum NSI-Projekt. Ist die Vorlage dort schon richtig, aber im Editor veraltet, lohnt zuerst der Versionsvergleich: Änderungen erreichen nachgelagerte Anwendungen nicht sofort (NSI-Dokumentation). Fehlt dagegen nur die Information, dass die getestete App solche Vorschläge macht, lässt sich die Beschreibung für den Apps-Katalog verbessern. Eine Prüfliste ist kein Auftrag zur ungeprüften Serienänderung (OSM-Verhaltenskodex für automatisierte Änderungen).
Womit wir morgen anfangen könnten

Für den Katalog schlage ich zwei kleine Ergänzungen vor: „NSI-Nutzung: Vorschlag beim Erfassen / Prüfung bestehender Objekte“ mit Beleg und „Bedienbarkeit: getestet mit …“ samt Datum. Für den Außendienst müssen wir nicht alles neu bauen: QField zeigt ein Projekt mit OSM-Grundkarte, und StraboField verbindet geologische Beobachtungen, Fotos und Messungen offline; sein Handbuch dokumentiert OSM Streets als Grundkarte. Unter ihren Produktnamen waren beide im untersuchten Katalogbestand nicht auffindbar. Das wären für mich zwei konkrete Aufnahmekandidaten, ohne ihnen damit NSI-Unterstützung oder getestete Barrierefreiheit zuzuschreiben.

Ob bis 2030 doppelt so viele Apps im Katalog stehen, interessiert mich weniger als eine einfachere Frage: Findet die nächste Person das Werkzeug, mit dem sie eine offene Frage vor Ort wirklich beantworten kann? Wenn ihr einen kleinen Beitrag leisten wollt: Nehmt eine App, die ihr kennt, prüft eine konkrete Aufgabe und ergänzt genau einen belegten Befund. Besonders interessieren mich die Fälle, in denen ein plausibler Vorschlag am falschen Objekt gelandet wäre, oder in denen erst eine gemeinsame Begehung gezeigt hat, was auf der Karte noch fehlt.

2 days ago

OpenStreetMap User's Diaries - Nov 17

Cima Conturines

How can I add the second Italian name Cima Conturines to Piz dles Cunturines - the first Italian name being Cima Cunturines ?

osm.org/node/2409254827 46,5757050 and 11,9777711

This other name is mentioned in Wikipedia English and Italian :

en.wikipedia.org/wiki/Piz_dles_Cunturines

3 days ago

How can I add the second Italian name Cima Conturines to Piz dles Cunturines - the first Italian name being Cima Cunturines ?

osm.org/node/2409254827 46,5757050 and 11,9777711

This other name is mentioned in Wikipedia English and Italian :

en.wikipedia.org/wiki/Piz_dles_Cunturines

3 days ago

osm2pgsql - Nov 16

Happy Birthday osm2pgsql!

Today 20 years ago Jon Burgess committed the first version of osm2pgsql to the repository. Since then osm2pgsql has been improved in many ways by many people. Originally started to enable rendering of OSM data into raster tiles, it has now many more uses. It is still the software behind many of the most important (raster or vector) OSM maps, especially when minutely updates of the data are needed. 4 days ago

Today 20 years ago Jon Burgess committed the first version of osm2pgsql to the repository. Since then osm2pgsql has been improved in many ways by many people. Originally started to enable rendering of OSM data into raster tiles, it has now many more uses. It is still the software behind many of the most important (raster or vector) OSM maps, especially when minutely updates of the data are needed.

If you want to know more about the history of the project, our website has an overview. We also showcases some of our users there.

We keep working on osm2pgsql, some ideas for that are on our road map, but we always like to hear about your needs and ideas, too.

Osm2pgsql is free to use and always will be. But it is not free to make. Please support us in any way you can.

4 days ago

OpenStreetMap User's Diaries - Nov 16

Native Mappers Begins Its Journey at HNBGU: Encouraging Students to Explore Open Mapping

Image: Students and faculty coming together to build the Native Mappers community at HNBGU, Uttarakhand.

♦

22 August 2026 Department of Geography, Chauras Campus, Hemvati Nandan Bahuguna Garhwal University, Uttarakhand, India

A new student-led mapping initiative, Native Mappers, is taking shape at Hemvati Nandan Bahuguna Garhwal University (HNBGU), 4 days ago

Image: Students and faculty coming together to build the Native Mappers community at HNBGU, Uttarakhand.

♦

22 August 2026 Department of Geography, Chauras Campus, Hemvati Nandan Bahuguna Garhwal University, Uttarakhand, India

A new student-led mapping initiative, Native Mappers, is taking shape at Hemvati Nandan Bahuguna Garhwal University (HNBGU), Uttarakhand. The initiative aims to bring university students closer to OpenStreetMap (OSM), collaborative mapping and the wider open mapping community.

The first meeting at the Department of Geography, Chauras Campus, introduced students to the idea of building a university-based mapping community where they can learn practical skills, contribute geographic information and work together on local mapping projects.

Connecting Local Mapping with Global Opportunities

During the introductory talk, Dr. Narendra Kumar (OM GURU) discussed the importance of open mapping, community participation, and the growing role of geospatial technologies in education, research, and humanitarian work.

Drawing on his engagement with the Humanitarian OpenStreetMap Team (HOT), the HOT Open Mapping Hub ecosystem and the Open Mapping Guru Fellowship, Asia-Pacific, he shared perspectives on how students can become part of the wider open mapping movement.

The discussion highlighted the importance of OpenStreetMap as a collaborative, freely accessible geographic database and the opportunities it offers young people to contribute to humanitarian mapping, disaster preparedness and community development.

Students Taking the Lead

Inspired by YouthMappers’ student-led chapter approach, Native Mappers aims to give students an active role in building and managing their mapping community.

The proposed chapter structure includes a President, Vice-President, Secretary, and student leads for mapping, training, research, outreach and communication. Faculty mentorship will provide academic guidance, while students will take responsibility for organising activities and developing projects.

From Training to Community Mapping

The proposed activities include:

  • OpenStreetMap introduction and practical editing.
  • GIS, GPS and field-mapping training.
  • Collaborative mapathons and mapping campaigns.
  • Mapping roads, health facilities, educational institutions and water resources.
  • Humanitarian and disaster-response mapping.
  • Community-based research using open geospatial data.

The initiative also aims to connect with colleges, universities and other mapping communities to encourage wider student participation.

Starting Locally, Connecting Globally

Native Mappers begins with a simple idea: students should have the opportunity to learn mapping by actually contributing to maps.

From the Garhwal Himalaya to the wider open-mapping community, the initiative hopes to encourage young people to document their surroundings, share local knowledge, and contribute to geographic information that everyone can use.

Map Local. Think Global.

Learn • Map • Research • Serve

Website: nativemappers.github.io/

Instagram: www.instagram.com/nativemappers/

NativeMappers #OpenStreetMap #YouthMappers #HOTOSM #OpenMappingHub #OpenMappingGuru #AsiaPacific #HumanitarianMapping #CommunityMapping #HNBGU #Uttarakhand 4 days ago

OpenStreetMap User's Diaries - Nov 16

Getting rid of source tags of an ancient mass import in Nederland

History

In 2010, a paper map by 3dShapes was digitized and imported, to map landuse in Nederland. The import project was well conducted and properly documented in the OSM-wiki. This was a major step in filling in the space on OSM.

Some problems remained after import, to be dealt with later. For instance, where trees had been planted in multiple rows, it was imported as an orchard. As a r 4 days ago

History

In 2010, a paper map by 3dShapes was digitized and imported, to map landuse in Nederland. The import project was well conducted and properly documented in the OSM-wiki. This was a major step in filling in the space on OSM.

Some problems remained after import, to be dealt with later. For instance, where trees had been planted in multiple rows, it was imported as an orchard. As a result, our motorways were suddenly lined with orchards, on OSM-based maps. This has been fixed by organized mappings. Another example: the paper map had a tile grid of thin black lines. These lines were seen as cut lines, resulting in unnecessary and awkward splits of the imported areas. The import procedure did detect this problem, but couldn’t automate a fix, so this was left to the future mappers. It took 15 years before a crazy mapper got rid of this in a solo project lasting 2 months. Guess who?

The issue

Not much of a problem, more of an annoyance, really: All polygons were tagged with “source=3dShapes”. A significant part of the polygons still carry this source tag. Many polygons have not been touched since import; many others have been edited but kept the original source tags; and many have been significantly altered or replaced thereby losing the original source tag. As a result, the tag is now generally meaningless. It only tells you that the former 3dShapes donated their map, but it tells you nothing about the current size, shape, object type, and tagging. These can be from unaltered to completely different.

The current consensus is that source tags should not be attached to objects, but to changesets. Why not just mass remove this outdated source tag?

Mass remove the 3dShapes source tag?

Re Attribution: 3dShapes attribution is in the Wiki import pages and in the contributor list for Nederland. No need to keep it in every single imported object. Re History: Where history has been preserved, the v1 user (creator) is 3dShapes, even when the source tag is removed. Re Signal function: Some mappers (me included) remove the 3dShape source tag after significant edits of the polygon. If all mappers did that, the tag would signify untouched 3dShapes polygons that probably need checking and editing. But many more mappers just ignore the source tag, even when splitting or completely reshaping and retagging the element. So the signal function is lost.

It is true that the 3dShapes tag combined with the history is significant. But you don’t need the 3dShapes source tag for that signal, just the history! To illustrate: There are MapRoulette challenges based on the presence of the source=3dShapes tag. The challenges contain enormous amounts of unordered objects, many of which have already been edited at some point. Will never be completed.

A IMO much better method is what I used for another old import: AND road import. I selected highways having nodes that were last touched by the import user. You could copy this method: select polygons having nodes that were last touched by user 3dShapes. This still finds lots of already edited polygons, but chances are they still need fixing. Because: 1. many edits just touch one side of the polygon; 2. In Nederland, hardly anything remains exactly the same for 15 years, so nodes untouched for 15 years are outdated anyway. And it does not need the totally tainted tag, making it completely redundant.

4 days ago

Geofabrik - Nov 19

Download Server Housekeeping

Every now and then, you look at the tools in your trusted old workshop and you think to yourself, I could organise this better! This has been us looking at our download server lately. It’s coming up to 20 years of age and it shows. As a first step in a brush-up that will likely […] a day ago

Every now and then, you look at the tools in your trusted old workshop and you think to yourself, I could organise this better! This has been us looking at our download server lately. It’s coming up to 20 years of age and it shows. As a first step in a brush-up that will likely take a couple more months, we’ve rearranged the files slightly, moving overview pages from /some/where/place.html to /some/where/place/index.html (or /some/where/place for short). Here’s some examples illustrating the change:

old URL (example) new URL (example) country overview /europe/france.html /europe/france/ sub region /europe/france/alsace.html /europe/france/alsace/ pbf file /europe/france/alsace-latest.osm.pbf /europe/france/alsace/alsace-latest.osm.pbf gpkg file /europe/france/alsace-latest.gpkg.zip /europe/france/alsace/alsace-latest.gpgk.zip updates /europe/france/alsace-updates/state.txt /europe/france/alsace/updates/state.txt

We’ll be keeping old URLs alive via HTTP redirects, so if you find an old download server URL somewhere in a document, or if you update an old database with the update URL stored somewhere in its bowels, all this will continue to work.

We’ve also re-wired some of the internals of the download server which will allow us to serve current data quicker (relying on an older and slower server only for older files), and we’ve switched the web interface to a templating engine so we can make some long-overdue improvements in the user interface down the line. Let us know if you find any bugs or if something doesn’t work like it used to – it might take a day or two for the new setup to settle in.

(Update on 20 Nov: We’ve switched from HTTP 308 redirects to HTTP 301 for the benefit of very old Osmosis and PyOsmium 3.1.x based setups which could not cope with the newer form.)

a day ago

OpenStreetMap User's Diaries - Nov 19

Roundabout islands: my take on them.

(I’ll keep the roundabouts round for this article; other shapes are not that different where it comes to mapping.)

Structure

Usually there is a central circle, the central natural/landuse/leisure, surrounded by a paved ring, surrounded by a wedgeshaped circle of kerbstones: the apron (aka truck apron).

Central natural/leisure/landuse

The days of plain grass roundabout islands ar a day ago

(I’ll keep the roundabouts round for this article; other shapes are not that different where it comes to mapping.)

Structure

Usually there is a central circle, the central natural/landuse/leisure, surrounded by a paved ring, surrounded by a wedgeshaped circle of kerbstones: the apron (aka truck apron).

Central natural/leisure/landuse

The days of plain grass roundabout islands are over, in Nederland. You can still find them, but most centre islands have bushes, art, trees, shrubberies, hedges, flowerbeds, statues and monuments, even hills, paths, walls and landscape examples. Many are used for commercial purposes, e.g. as garden showcases.

My take on that is to map it as what it’s made to look like. If it is made to look like a beach, garden, wood or park, I tag it as a round beach, garden, wood or park, usually with access=no (there are exceptions even to that!).

The apron ring

The apron ring is most often paved with stones, but I have seen many other materials. My take on this is: I don’t map the apron ring itself, only the apron kerb ring.

The apron kerb

Apron kerbs are designed as easily traversable barriers, but the further you traverse them, the more unpleasant it gets. Regular cars will usually not traverse the apron kerb, even though it would not harm the car. I map the kerb by drawing the outside kerb circle and tag it as barrier=kerb, + kerb=apron (ATYL).

The whole island

The central island is the whole area within the apron kerb way, including the central natural. I tag it as area:highway=central_island (YOLO, I mean, ATYL). I could put the tag on the apron kerb way, but that mixes features as wel as data types. Luckily, there is an established method to use tagged way elements a outlines of an area: the multipolygon. In this case the MP is very simple: only one outer, no inner. The apron kerb way is the outer, and the area:highway=central_island tag goes on the MP area.

And that’s it! As far as I am aware, no data users use apron kerbs and central islands, no matter how they are tagged.

a day ago

OpenStreetMap User's Diaries - Nov 19

A thought on careful, source-backed mapping

Good maps grow through careful observation, clear sources, and respectful review. Before changing a feature, it helps to check the existing data, explain the reason in the changeset, and confirm that the published result reflects the intended edit.

For boundary-related work, I think it is especially useful to keep official reference maps clearly attributed and separate from OpenStreetMap a day ago

Good maps grow through careful observation, clear sources, and respectful review. Before changing a feature, it helps to check the existing data, explain the reason in the changeset, and confirm that the published result reflects the intended edit.

For boundary-related work, I think it is especially useful to keep official reference maps clearly attributed and separate from OpenStreetMap’s community-maintained data. A detected change should lead to an evidence-based review of the object history and sources, rather than assumptions about the contributor’s intentions.

This general project note is shared by the operator across accounts in the same mapping workspace. It does not announce a map edit or claim a community consensus.

a day ago

OsmAnd - Nov 19

Arranging Buttons and Layout for a Clear Map

Think of a painting you really liked. You probably don't remember the frame, and that's the best thing you can say about a frame. It was there to hold the picture, and that's all. 2 days ago

Think of a painting you really liked. You probably don't remember the frame, and that's the best thing you can say about a frame. It was there to hold the picture, and that's all.

On the OsmAnd screen, the map is the picture. Buttons, widgets and the compass in the corner are the frame. With the phone in your hand on a city street, you hardly see them. Then one day the phone goes onto the handlebar of a motorcycle, sideways, you pull on your gloves, and now the frame is all you see. The zoom buttons sit right on the road you're about to take, the search button hides the next village, and pressing the right thing with a glove on is mostly luck.

The map didn't change. The frame just got too big for it. So let's make it smaller, quieter and easier to hit with gloves, and make sure it stays out of the way when the phone turns.

♦

Photo by Gijs Coolen on Unsplash

What Stays in the Frame​

The easiest way to give the map more room is to show fewer buttons. In Default buttons, every standard button has its own switch, so you can just turn off the ones you don't use on the bike. Search, for example. You won't be looking anything up while riding, and at a stop you'll take the phone in your hand anyway. The compass can stay, but set it to appear only when the map is rotated.

If there's something you do on almost every ride, you can give it a separate button. Custom buttons are made from Quick Actions. With a helmet headset, for example, it could be a button that turns voice prompts off and back on, so you don't have to go into the settings for that.

Custom buttons can be moved with a long press, so you can put them where they're easier to reach. They snap to an invisible grid in the corners of the screen, and when widgets or panels change, OsmAnd shifts them so they don't overlap.

The map can also make more room for the road ahead. With Display position set to Bottom (on iOS, it's called Location position on screen), your location sits a little below the center, so you see more of what's coming than of what you've already passed.

♦♦ Buttons You Can Hit with Gloves On​

Take the voice prompts button from the previous section. On the map it looks small and tidy, and that's fine right up until you try to press it with a glove on. Every button has its own appearance settings, and on Android you can also change all default buttons in one go (on iOS, it's one button at a time).

Start with the icon, because it can do more than just sit there. A dynamic icon changes with the state of the action, so the button itself tells you what's going on. You can also give a button the icon of one of the actions you've added. And if you'd rather it always looked the same, pick a specific icon and it won't change.

Then make it bigger. Drag Size up, and the button becomes something your thumb finds without searching. Corner radius changes the shape, from sharp square corners to smooth rounded ones. A little rounding is usually enough.

A bigger button covers more of the road, though, and that's what the background is for. On Android, Background opacity goes from 0 to 100%: keep the button solid, make it partly transparent, or turn it down until only the icon with a light shadow is left. On iOS, the Background setting has two types. Solid works the same way, with an opacity slider from 0 to 100%. Liquid Glass turns the button into a piece of glass on top of the map: Clear lets more of the map show through, and Tinted makes it a bit more solid when there's a lot going on behind it.

Every change shows up right away in the preview, so you can play with it until the button feels right, and only then save it.

And if you'd rather not touch the screen with gloves at all, OsmAnd works with external input devices, such as Bluetooth keyboards and WunderLINQ controllers. Their buttons can zoom the map and run Quick Actions, so the voice prompts switch can live on the handlebar instead of the screen.

♦♦ Portrait or Landscape​

Painters had these two words long before phones did. A portrait is tall, a landscape is wide, and nobody expects one picture to work in both. On a motorcycle, you get both in one day. The phone rides sideways on the handlebar, and at a stop you take it in your hand and hold it upright.

By default, OsmAnd uses the same widgets in both orientations, so whatever you set up for the handlebar follows you into portrait too. To keep them apart, turn on Separate layouts on Android or set Screen elements to Independent on iOS. Configure screen then has Portrait and Landscape tabs, and changes in one don't touch the other. You don't have to start from scratch, either: a panel's widget list can be copied from the other orientation and adjusted from there.

Landscape has its own catch. The screen is wide but not very tall, and the top and bottom panels end up right next to the map buttons. Panels layout decides how they share the space. Wide stretches the top and bottom panels across the whole screen, and Compact fits them between the side panels and the map buttons. You can choose it separately for portrait and landscape (on Android, the option appears once Separate layouts is on).

The widgets themselves can be adjusted too, panel by panel: their height, whether icons are shown, text colors for day and night, and the background, which can also be transparent. A custom background color is a paid feature. Each widget also has its own size, Small, Medium or Large. Speed and the next turn are worth making Large, because on the road you read them at a glance. If one panel or another profile already looks the way you like, you can copy its appearance instead of setting everything again. On iOS with Independent screen elements, all of this is set separately for each orientation.

♦

A Frame for Every Trip​

All of this belongs to one profile. The screen you put together for the motorcycle stays in the Motorcycle profile, and the ones you use on foot or in the car stay exactly as they were. Nothing you changed for the handlebar follows you into the city.

Even within one profile, the screen doesn't have to look the same all day. The left and right panels can hold up to five pages of widgets, so one page can show what matters on the move and another what you check at a stop.

If another profile should get the same buttons, you don't have to set them up again. In Default buttons, Copy from another profile brings over which buttons are visible and how they look. Custom buttons are shared between profiles, and in each one you just decide whether a button shows up. Switching profiles can be a Quick Action as well, so going from the bike to walking around town takes one tap.

Back to the painting from the beginning. A good frame is the one you don't remember, and after a day on the road, you probably won't remember the buttons either. Just the road.

We appreciate your interest in us and thank you for taking the time to read this article. Join us on social media to keep up to date with the latest news and share your experiences. Your opinion is important to us.

  • Follow:

    Follow OsmAnd on Facebook, TikTok, X (Twitter), Reddit, and Instagram!

  • Join:

    Join us at our groups of Telegram (OsmAnd News channel), (EN), (IT), (FR), (DE), (UA), (ES), (BR-PT), (PL), (AR), (TR).

  • Get:  

    ♦♦ ♦

2 days ago

OpenStreetMap User's Diaries - Nov 18

Landcover

When I joined the OSM-community, landcover was being proposed. The idea ws to get non-landuse landuse tags and non-natural natural tags out of the landuse and natural keys. I especially dislike landuse=grass because grass is not landuse. If grass is used for something, it is meadow or farmland or e.g. decoration, separation and the like. So the landcover seemed a goed idea to me.

Since t 2 days ago

When I joined the OSM-community, landcover was being proposed. The idea ws to get non-landuse landuse tags and non-natural natural tags out of the landuse and natural keys. I especially dislike landuse=grass because grass is not landuse. If grass is used for something, it is meadow or farmland or e.g. decoration, separation and the like. So the landcover seemed a goed idea to me.

Since then, I’ve changed my view. Only two values make sense: grass and trees. Trees already has two alternatives: natural=wood and landuse=forest. At the data user side, both just mean an areas of mainly trees. Landcover=trees only adds a third option to tag the same thing. Grass has three estrablished tags: landuse=grass, landuse=meadow and natural=grassland. These are more distinctive than the tree tags, but that is mainly at the mapper’s side; they think they make a distinction, but on the data user side it’s all just land covered with grass.

All the other proposed values are covered by the appropriate values in the natural key, and there is nothing wrong with that: objects in the natural key are objects which grow, flow or form by nature: life forms, and geological forms, in contrast to man_made objects. When man mimics natural objects they are still categorized as naturals: beach, water bodies, tree rows. Workable.

And, trees and grass also have appropriate natural tags: natural=wood and natural=grassland. This makes a move to the landcover key unnecessary. Combined with the fact that currenty the landcover tags are usually added to one of the established tags for grass and trees, which means that the full transition will never occur, I now opt for dropping the landcover key and using established naturals instead.

For trees, just use natural=wood. It’s treated as equivalent to landuse=forest. For real forestry, alternatives are available. For grass, just use natural=grassland. The general idea is that grassland is more wild and variable than landuse=grass, but that is a very loosely defined distinction. Even urban greenery comes in many variations. Maybe we could reserve landuse=grass for nicely trimmed lawns of just grass.

2 days ago

OpenStreetMap User's Diaries - Nov 17

OSMLondon at The Volunteer pub!

The next London OSM meet-up will be December 9th at the Monkey Puzzle.

Last time we were at “The Volunteer” pub! Obviously with a name like that, I hoped this would be a good pub for us to have our gathering of volunteer mappers, and to show solidarity with the unpaid bar staff. But it turns out this pub was pretty noisy and busy, and what’s more, I suspect the staff were actually being 3 days ago

The next London OSM meet-up will be December 9th at the Monkey Puzzle.

Last time we were at “The Volunteer” pub! Obviously with a name like that, I hoped this would be a good pub for us to have our gathering of volunteer mappers, and to show solidarity with the unpaid bar staff. But it turns out this pub was pretty noisy and busy, and what’s more, I suspect the staff were actually being paid :-) I booked a table for 8 but got a table with four places. I suppose the idea was that it’s big enough for 8 people to drink around, which we put to the test, and then about 12 people arrived, and then we ordered food. So it was a bit of squeeze, but fun!

♦

User spiregrain was there (impressive editing run!). He’s from Statford, so we talked about mapping there, and we were remembering having a massive Westfield shopping mall mapping party there. Looking back at the old diary entry now, I see this was 2011. I’d forgotten we organised to go there shortly after the mall opened.

Terrence Eden was at the pub! I feel like I could’ve chatted to him all evening about the fascinating tech topics (and indeed other topics) I’ve read about on his blog, but keeping it OSM-adjacent, I asked him about OpenBenches.org, the bench-themed crowd-sourced open geodata project! I did some bench mapping recently during the 31 Day OSM Challenge. I only mapped boring benches in OSM for that, but I have added benches (including photos of benches) into OpenBenches in the past, generally when I find a really good juicey bench.

OpenBenches has operated and inter-operated with OpenStreetMap for many years now. It is a separate database, so not like things like wheelmap.org where OSM is the database, and it’s not synced in any automated way, but we do tag OpenBenches ids in OSM, and there are some mechanisms for user-driven syncing, the main one being mapcomplete.org/benches. I was saying I found myself wanting a tool to look through all the benches I have added to OpenStreetMap, to sync & conflate that data into OpenBenches and vice versa. Thinking more widely I don’t know if we’ve found the best way to organise these kinds of parallel geodatabases (and there are many other examples). We don’t particularly want OpenStreetMap to be the one and only centralised source for such things (although the wheelmap.org approach does work well). Automated syncing is possible but fraught with problems, and so we drift into this kind of loosely-coupled community-driven ad-hoc syncing situation.

And then Michiel Riechart User:Nakaner walked into the pub! He’s very busy in all things OSM, working at geofabrik in Karlsruhe, and apparently he decided to pop over to London because he was making the most out of an interrail ticket. True to form as a railway obsessive! (He operates openrailwaymap.org and has given some SOTM talks on how to do ludicrously detailed railway signal mapping). Being such a noisy pub I don’t know if he himself had railway mapping conversations, but on my side of the table he was inspiring others to talk about railway mapping by his mere presence!

We talked about sysadmin challenges dealing with overzealous scraping by/for AIs. Firefishy and TomH have been working hard to keep a lid on it with OpenStreetMap sites. Maybe the topic also came up because Terrence has had his own battles with the bots lately. I heard wikimedia have been trying to contact scraper organisations and ask them nicely. I see isolated success stories but presumably that isn’t a full solution. No doubt they’re still spending a lot of resources on fending off abusive traffic hitting the wikipedia website.

We also chatted about good old spam, which feels quaint by comparison. Firefishy told us how OSM accounts can be erroneously closed as spammer accounts sometimes. One particular source of mistakes has been u-map. That system allows users to register by authorizing with an OpenStreetMap account. That in turn means that some folks end up creating an OSM account purely for their interactions over on one particular umap. These might be people who know very little about OpenStreetMap, but they might well create a profile description including links which they’ll write in relation to whatever the particular umap is about, and the OSM account shows no editing activity within OSM. That can all easily look like spam, and gets wiped. Not sure whether this is considered a big problem for OSM/u-map, or what solutions have been discussed, but it seems to me u-map should probably support more login providers, and get these rolled out on more instances. For example I see umap.openstreetmap.de only supports login with an OSM account.

User profile description spam in general is much more common than people trying to spam the map data or anything more sophisticated like that. Just automated web bots registering and putting spammy links on their profile description. Mostly zapped in an automated way too, but some profile spam can look vaguely map-adjacent. Me and Matt were laughing about spam claiming to offer “Best plumber in London”. As London home-owners, the phone number of a genuinely good plumber is like gold dust! So we decided we need a new policy: A user should be allowed to keep their “Best plumber in London” profile, but only if they come round and fix our plumbing problems! :-)

Clearly our solutionizing was getting more silly as the evening progressed. The pub wasn’t getting any quieter either as after-work crowds gave way to crowds of trendy-looking young people. We fitted right in of course. And the staff gave us all a free slab of cheese cake at the end of the night. Maybe the pudding chef is the volunteer!

That was fun. Maybe next time will be even more fun because it’s the Christmas meet-up! Come join us at the good old Monkey Puzzle pub in Paddington on December 9th. More details on the wiki

3 days ago

OpenStreetMap User's Diaries - Nov 17

Mapping the Southern African grid from OpenStreetMap, and where the gaps are

I run Aloe Energy, a small not-for-profit initiative working on energy access in Sub-Saharan Africa. We published a free interactive map of the Southern African Power Pool grid, and OpenStreetMap is its backbone, so I wanted to share how it was built and where OSM could use help.

What we did. We took every OSM power line of 66 kV and above across the 12 SAPP countries (country extracts f 3 days ago

I run Aloe Energy, a small not-for-profit initiative working on energy access in Sub-Saharan Africa. We published a free interactive map of the Southern African Power Pool grid, and OpenStreetMap is its backbone, so I wanted to share how it was built and where OSM could use help.

What we did. We took every OSM power line of 66 kV and above across the 12 SAPP countries (country extracts from November 2026). Where OSM had no line but an older public map did, we filled the gap from TANESCO (2015) and World Bank (2017) grid maps, but only for lines recorded as existing, with a known voltage, and more than about 3 km from any OSM line. A “Source and age” view on the map colors each line by where it comes from, so you can see exactly what is OSM and what is gap-fill.

Where OSM is thin. Coverage is weakest in Tanzania, DR Congo and Angola. Those are the places where the map still leans on maps that are close to ten years old, and where new mapping would change the picture most. Substations named in national plans are often missing too.

The map: aloeenergy.org/research/sapp-grid. There are also maps for the Eastern Africa Power Pool and Madagascar built the same way.

OSM data is credited as “OpenStreetMap contributors (ODbL)”, and the OSM-derived line data is available on request under the ODbL. The project register and plant list we compiled are free to download under CC BY 4.0 at aloeenergy.org/data. If you map power in the region and spot something wrong, I would be glad to hear about it and point people to fix it in OSM.

3 days ago

OpenStreetMap User's Diaries - Nov 17

Když potoky pod Kletí vysychají

V předchozích letech jsem si všímal stavu malých vodních toků v okolí mého bydliště. Přes léto se výrazně projevovalo sucho, ale ještě před pár lety byly ty potůčky slabé, přesto trvalé. V roce 2024 a 2025 už došlo na potoku Hučnice k zásadní změně. Prostě přestal téct.

Místní, co mají v okolí své zahrádky, měli dokonce podezření, zda Hučnice neztrácí vodu nějakou konkrétní událostí. Ať 3 days ago

V předchozích letech jsem si všímal stavu malých vodních toků v okolí mého bydliště. Přes léto se výrazně projevovalo sucho, ale ještě před pár lety byly ty potůčky slabé, přesto trvalé. V roce 2024 a 2025 už došlo na potoku Hučnice k zásadní změně. Prostě přestal téct.

Místní, co mají v okolí své zahrádky, měli dokonce podezření, zda Hučnice neztrácí vodu nějakou konkrétní událostí. Ať už přirozenou cestou, protože někde hluboko pod potokem jsou štoly bývalého grafitového dolu, nebo snad lidským zásahem, že by někdo vodu čerpal. U Hučnice nebylo co odhalit. Voda Hučnice prostě z jižního úpatí Kleti zmizela.

Ostatní potůčky okolo Českého Krumlova taky nemají vyhráno. A Chvalšinský potok s Polečnicí, což jsou zde v okolí největší přítoky Vltavy, měl letos docela nízký stav vody. Při mapování se pak věnuji úpravě vodních toků tam, kde v nich voda už dlouho netekla.

Odkazy

O tématu vody v krajině jsem psal

  • 2026: sucho, podhoubí a vápencové podloží nedaleko Kleti na iNaturalist
  • Stopy v krajině: Meliorace i obnova vodní rovnováhy na loukách Jižních Čech
  • Změny klimatu a vysušování krajiny na mapách
3 days ago

OpenStreetMap User's Diaries - Nov 16

Mapeando bairros de Aratiba - RS

♦

Até agora foram mapeados: * Rio Novo * Centro * São Pedro

(vou sair agr pro vôlei, qualquer coisa explico melhor dps 😭)

4 days ago

♦

Até agora foram mapeados: * Rio Novo * Centro * São Pedro

(vou sair agr pro vôlei, qualquer coisa explico melhor dps 😭)

4 days ago

OpenStreetMap Blog - Nov 16

Call for SotM 2027 logo designs

After a successful State of the Map 2026 in Paris, we are excited to announce that the conference will be heading to Bogotá next! The logo is a crucial part of SotM – it defines the design and colors of the official website and sets the visual style for the conference across all OSM platforms. […] 4 days ago
♦

After a successful State of the Map 2026 in Paris, we are excited to announce that the conference will be heading to Bogotá next! The logo is a crucial part of SotM – it defines the design and colors of the official website and sets the visual style for the conference across all OSM platforms. It will also live on in our much-loved SotM merchandise and swag (t-shirts, stickers, and more), turning your best conference memories into lasting keepsakes. Whether you’re a seasoned designer or a graphic design enthusiast trying it for the first time, everyone is welcome to participate and share their original idea with the community!

Our 2027 host city, Bogotá, is recognized for its visual richness and unique graphic identity. From the city brand system that turns the letter “A” into the mountain range embracing the high plateau, to the expressive force of the comparsas that parade down Carrera Séptima during the city’s birthday celebrations, design in Bogotá has been a tool for gathering, memory, and collective expression.

We invite participants to draw inspiration from this visual and cultural richness, integrating into their proposal:

  • Cartographic, geographic, or urban elements related to the city: These may evoke the silhouette of the Eastern Hills, the urban grid spreading across the high plateau, or the network of bike lanes that crosses the capital, for example.
  • Motifs and colors alluding to a celebration that honors life and collective memory.
  • A sense of community strengthening, reflecting the collaborative and open spirit of OSM.

Contest guidelines

The logo design should:

  • Be an original artwork, not AI-generated.
  • Refer to OpenStreetMap (OSM), the virtual State of the Map (SotM), and the spirit of Bogotá, Colombia, and its culture. 
  • Focus on the sense of global community and its core values.
  • Be easily recognizable and be adaptable to various formats. 
  • Open licence: CC BY-SA 4.0
  • Be submitted by 13th December ,2026 23:59 UTC

Call process:

To facilitate the participation of beginner designers, community members, and professionals, the process will be divided into two phases:

  • Phase 1: Proposal submission.
  • See “How to enter” 
  • Phase 2: Final development.
  • After the vote, the finalist proposal will be invited to refine its design, if needed, incorporating color variants, textures, horizontal/vertical formats, complementary graphic elements, and a basic logo usage guide (brand manual)
  • The winning proposal will receive a conference ticket, and a recognition through the event website and/or social media with a link to their website and/or portfolio.

How to enter:

Please submit your logo proposal via email to sotm@openstreetmap.org, subject: SotM 2027 Logo Proposal “Name”

  • In the email content, give us your information:
    • Name
    • Country
    • OSM username
    • Social media (If you want) 
  • Attach:
    • The design file in PNG format and a scalable file format (like PDF or SVG). 
    • A basic logo presentation deck.
    • Mockups are welcome but not mandatory.

Winner selection:

The SotM working group will review the submitted artworks, and the winning logo will be decided by vote. The official logo will then be announced in December or early January.

Looking for some inspiration?

Take a look at the logos from the past SotMs – wiki.openstreetmap.org/wiki/State_of_the_Map. If you have any questions about the call, feel free to contact the State of the Map Working Group at sotm@openstreetmap.org.

The State of the Map conference is the annual, international conference of OpenStreetMap, organised by the OpenStreetMap Foundation. The OpenStreetMap Foundation is a not-for-profit organisation, formed to support the OpenStreetMap Project. It is dedicated to encouraging the growth, development and distribution of free geospatial data for anyone to use and share. 

The OpenStreetMap Foundation owns and maintains the infrastructure of the OpenStreetMap   project, is financially supported by membership fees and donations, and organises the annual, international State of the Map conference. Our volunteer Working Groups and small core staff work to support the OpenStreetMap project. Donate or Join the OpenStreetMap Foundation for just £15 a year or for free if you are an active OpenStreetMap contributor.

OpenStreetMap was founded in 2004 and is an international project to create a free map of  the world. To do so, we, thousands of volunteers, collect data about roads, railways, rivers, forests, buildings and a lot more worldwide. Our map data can be downloaded for free by everyone and used for any purpose – including commercial usage. It is possible to produce your own maps which highlight certain features, to calculate routes etc. OpenStreetMap is increasingly used when one needs maps which can be very quickly, or easily, updated.

4 days ago