Style | Standard • Cards

OpenStreetMap Blogs

Thursday, 19. November 2026

Geofabrik

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 […]

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 indefinitely 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.


OpenStreetMap User's Diaries

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.

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.


Bkk

Bkk

Bkk


Ayy

Home

Home


OsmAnd

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.

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.

Motorcycle Ride

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.

Default ButtonsCustom Button on the Map

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.

Button Appearance AndroidButton Appearance iOS

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.

Landscape

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.

Wednesday, 18. November 2026

Florian Lohoff

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

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: https://osm.zz.de/routeqa2

So here some Screenshots:


OpenStreetMap User's Diaries

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

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.


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.

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.

Tuesday, 17. November 2026

OpenStreetMap User's Diaries

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

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!

OSMLondon at the volunteer (not quite during peak crowdedness)

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


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

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 :

https://en.wikipedia.org/wiki/Piz_dles_Cunturines


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

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: https://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 https://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.


osm2pgsql

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.

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.


OpenStreetMap User's Diaries

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ť

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

Monday, 16. November 2026

OpenStreetMap User's Diaries

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),

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

Native Mappers First Meeting at HNBGU

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: https://nativemappers.github.io/

Instagram: https://www.instagram.com/nativemappers/

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


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 😭)

Mapa

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

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


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

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.


OpenStreetMap Blog

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. […]

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 – https://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.

Sunday, 15. November 2026

OpenStreetMap User's Diaries

service=parking_aisle

osm.org/changeset/105681 One of my Changesets from 2008 when I proposed service=parking_aisle osm.wiki/Proposal:Service%3Dparking_aisle

Changesets were implemented in April 2009 API v0.6. My first retroactive changeset recorded was 1 Jun 2008  osm.org/changeset/11289 where I was mapping out Nevis Island where one of my friends had gone to med school. Anything I did prior wasn’t reco

osm.org/changeset/105681 One of my Changesets from 2008 when I proposed service=parking_aisle osm.wiki/Proposal:Service%3Dparking_aisle

Changesets were implemented in April 2009 API v0.6. My first retroactive changeset recorded was 1 Jun 2008  osm.org/changeset/11289 where I was mapping out Nevis Island where one of my friends had gone to med school. Anything I did prior wasn’t recorded, but I started mapping Chicago area roads and highways November 08, 2007.


OpenStreetMap Blog

Announcing SotM 2027 in Bogota

It’s time to reconnect with familiar faces and meet new friends from the OpenStreetMap family around the world! We are excited to share that State of the Map (SotM), the international gathering of the OpenStreetMap community, will take place in Bogotá, Colombia in 2-4 July 2027! This edition will gather mappers, open data advocates, developers, […]

It’s time to reconnect with familiar faces and meet new friends from the OpenStreetMap family around the world!

We are excited to share that State of the Map (SotM), the international gathering of the OpenStreetMap community, will take place in Bogotá, Colombia in 2-4 July 2027! This edition will gather mappers, open data advocates, developers, and community leaders from across the world to celebrate OSM, open collaboration and community-driven mapping. Learning from past conferences, our goal for 2027 is to open the doors even wider, making it easier for more people to join, contribute, and be heard in this global celebration of open mapping.

Together with our amazing local team in Bogotá, we are working to build a creative, welcoming, and truly inclusive SotM experience, where every session and activity is designed with our global community in mind.

A message from the Bogota Local Team:
¡Hola desde Bogotá! For the Colombian and Latin American OpenStreetMap communities, hosting State of the Map is a dream come true. Our local team, led by AC3, the OpenStreetMap chapter in Colombia, brings together mappers from Bogotá, Medellín, Cúcuta, Yopal, Puerto López and beyond, and we are preparing a conference that feels like home for everyone. You will meet us at the Universidad Nacional de Colombia, a green and historic campus in the heart of the city, 2,600 meters closer to the stars. Bring your questions, your maps and your curiosity: we will bring the coffee, the music and a very warm welcome. ¡Nos vemos en Bogotá!

Save the date and start getting ready for SotM 2027! More details on speakers, program, tickets, and ways to get involved will be coming soon. So bring your maps, bring your ideas, and let’s make this an edition to remember!

SotM Organising Committee

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.


OpenStreetMap User's Diaries

Capitole du Libre 2026

Hier soir, j’ai présenté dans l’amphithéâtre C002 au sein du campus de enseeiht à Toulouse, « Contribuez à OSM ». La bonne surprise fut le taux de remplissage de la salle. J’ai compté plus d’une vingtaine de personnes. La présentation était articulée en deux parties : la première, un tout petit peu de théorie et pas de présentation d’outils ; la deuxième, des démonstrations, des petits trucs fac

Hier soir, j’ai présenté dans l’amphithéâtre C002 au sein du campus de enseeiht à Toulouse, « Contribuez à OSM ». La bonne surprise fut le taux de remplissage de la salle. J’ai compté plus d’une vingtaine de personnes. La présentation était articulée en deux parties : la première, un tout petit peu de théorie et pas de présentation d’outils ; la deuxième, des démonstrations, des petits trucs faciles pour commencer, puis des trucs plus « grands » (de l’infrastructure). En trente minutes, j’avais plié ma présentation. Il restait vingt-cinq minutes, qui se sont très, très facilement remplies par de très nombreuses questions. Merci au plublic pour ces questions. Merci à l’organisation du Capitole du Libre. La présentation est disponible à https://files.hirlimann.net/talks/cdl2026/.


Flow of the River Ilagan

It’s been two months since I started to edit the Ilagan River again. While I had done so in the past, way before these two months, this period turned out to be a great adventure that I’m still hiking.

It was a time after Project CaCau. When I put it to an end, I felt not only disappointed, but ambitious. Why exactly? Well, I don’t know, but the roaring engine I had used to keep me going

It’s been two months since I started to edit the Ilagan River again. While I had done so in the past, way before these two months, this period turned out to be a great adventure that I’m still hiking.

It was a time after Project CaCau. When I put it to an end, I felt not only disappointed, but ambitious. Why exactly? Well, I don’t know, but the roaring engine I had used to keep me going through that project was still on, and I couldn’t just stop it. So, I had to redirect it somewhere.

For a bit, I had just redirected it to OSM. I experimented with multiple things and tried to pick up my old stuff. But one in particular caught my attention. A while ago, I was editing the river area of the Ilagan River. I never picked it up again until then. Despite that, it just stuck. Starting in the 15th of September, I got into the flow of the edits, and I never stopped.

I didn’t just do the main river either. I had also started doing its tributaries because my satisfaction didn’t get put with just that. Then, suddenly, the Bintacan River got finished, then the Nanaguan, and then I was suddenly speeding through the headwaters of the Abuan. I was now pushing 2K-3K edits a day, with the little free time I had.

My satisfaction didn’t stop; I had also started mapping the landslide areas. Now, at that point, I was satisfied. I had forgotten Project CaCau and its shadow that burdened me. Then, I realized: why not make this run official? Make it a project? So, I did.

Enter, Project KarayanIlagan. It meant “Ilagan River” in Ilocano: Karayan as River, and Ilagan as itself. Nothing changed in my workflow; just that I finally had a name to keep it going and back it up, putting hashtag comments for it as #KarayanIlagan (and later on with #ChasingWaterways for my fellow mappers’ initiative), and to give it a history and recognition.

Now, we place it here, right now. By the time I made this diary, I had gotten to 2nd in most map changes in the whole Philippines. I am still going, editing the waters of the River Abuan to contribute to my own project, ChasingWaterways, OpenStreetMap, and the Philippines itself. Eventually, I will finish, but for now, I will keep going.

To the people who see this, please hope for me to succeed. God bless, and Mabuhay!


Tweaked Every-Door editor a bit

I have custom branch of EveryDoor since July. Namely because for recycling containers i need tagging preset with custom field types not supported by iD schema and for ED plugin engine which has a annoying bug regarding NeedsInfo selectors.
Opening and searching presets was occasionally super slow and past few nights ive tried to fix annoyances. Turned out the performance fix was trivial as i

I have custom branch of EveryDoor since July. Namely because for recycling containers i need tagging preset with custom field types not supported by iD schema and for ED plugin engine which has a annoying bug regarding NeedsInfo selectors.
Opening and searching presets was occasionally super slow and past few nights ive tried to fix annoyances. Turned out the performance fix was trivial as i had compiled app with wrong parameter which caused app to not be able to compile something related to presets lookup.

Anyways, 2 nights later, achievements include:

  • saving downloaded map data at least 20x faster (by using already existing db index which existing query disregarded)
  • zoom no longer jams at zoom level 15. Technical reason is that ED has internally 2 map views for different zoom ranges and ones min and other’s max zoom was lvl 15.
  • amenities list scrolling is now vertical instead horizontal (which i thought was unintuitive and waste of space)
  • tiles are loaded while zooming, in current version, after zooming tiles are downloaded only on map drag event. Fixed by updating map library.
  • i discovered ED already has special overview map of downloaded osm data (dark-green rectangles at Menu -> Data Management -> Download tiles), but they are rather useless as they denote simply areas that was downloaded at some point. Merged rectangles into rasterized layer to show up to date and outdated areas as one.
  • haven’t been able to test, but cached map tiles should cleared after 1 month to prevent out of date background layer. I have previously created multiple false positive notes about missing road or building only to find my map layer was outdated
  • dragging to add new element while moving and tracking gps, won’t cause unexpected jumps and zoom changes as user’s location changes.
  • few more changes related to map interactions i forgot

Branch is at https://github.com/kallejre/every_door/tree/stable-dev. I should file PR, but half of those changes are really personal preference, not justifying to change UX flow for lots of people.

In future i wish to look into plugin manager, why is it impossible to update plugins without uninstalling previous version first.


weeklyOSM

weeklyOSM 851

♦[1] Mapped Chronicles: the real places behind books, films and games | map data © by OpenStreetMap Contributors. 05/11/2026-11/11/2026 Mapping Telegram Sam proposed tagging seaplane bases with aeroway=seaplane_base instead of aeroway=aerodrome, as they have no runways or aprons and more closely resemble harbours. The water landing area should use seamark:type=seaplane_landing_area instead of aerow
weeklyOSM 851
[1] Mapped Chronicles: the real places behind books, films and games | map data © by OpenStreetMap Contributors.

05/11/2026-11/11/2026

Mapping

  • Telegram Sam proposed tagging seaplane bases with aeroway=seaplane_base instead of aeroway=aerodrome, as they have no runways or aprons and more closely resemble harbours. The water landing area should use seamark:type=seaplane_landing_area instead of aeroway=runway, while landuse=industrial with industrial=port prevents retagged bases from disappearing from maps. The discussion is ongoing in the forum.

MaggieMaps and Jake Low are proposing to describe wetlands using the new keys wetland:connectivity, wetland:vegetation, and wetland:landform to specify their water source, vegetation, and terrain position, and extending the use of salt=* and anthropogenic=yes to wetlands. OpenStreetMap US is working with the Environmental Policy Innovation Center on OpenWetlandsMap, an OSM-based dataset. The discussion is ongoing on the Wiki and in the OpenStreetMap US Slack.

Mapping campaigns

  • Rphyrin used osm_pantau to highlight where mappers participated in the HOT Global Solidarity Mapathon 1 on Friday 6 November 2026.

Community

  • Rtnf has noticed a growing trend of new tools bringing the Wikidata and OpenStreetMap ecosystems closer together.

  • OSM user infraboiii has analysed the current state of vending machine tagging in France.

  • In the interview at OpenCage, Frank März shared the story behind OpenFireMap, a free web map of fire stations, hydrants, water supply points, and defibrillators from OpenStreetMap data across dozens of European countries. He rebuilt the map with AI assistance and it now serves pre-computed data for most countries with Overpass as a backup.

  • Mateusz Konieczny worked on improving iD and its tagging schema, with funding from the OpenStreetMap Foundation and the European Union through the NLnet Foundation, and has shared an update on the work completed so far.

  • Following a thread on the OSM Community forum, the OpenStreetMap France community started drafting rules to be applied on the forum given the recent influx of generative artificial intelligence issues such as servers and tools overload, wrong map contributions, and self promotion of vibe-coded applications. Some reminders are given, e.g. that LLM-copied code is stolen code, the forum isn’t a self-promoting place, non-free software won’t receive support from the community, and LLM usage should not become common practice.

  • Andres Gomez Casanova is proposing to translate the OSM tag building as ‘Edificación’, a Spanish term encompassing any built structure, regardless of size. Translating it as ’edifício’ would exclude structures such as sheds, kiosks, garages, greenhouses and petrol station canopies.

  • Andy Mabbett, in a blog post made on Remembrance Sunday, described how war memorials and the people named on them can be recorded as open, linked data. This includes photos with transcribed names on Wikimedia Commons, a page on WikiTree, a Wikidata item and a point on OpenStreetMap. The IDs of the services are then cross-referenced so that, for example, Wikidata contains the OSM ID and the OSM point contains the Wikidata ID. The Brierley Hill war memorial served as an example.

OpenStreetMap Foundation

  • Craig Allan, Chair of the OpenStreetMap Foundation Board, will speak at State of the Map Nigeria 2026 on ‘Community Mapping for Climate Change’.

Local chapter news

  • Eugene Alvin Villar, on behalf of the OSMF’s Local Chapters and Communities Working Group, opened a community discussion on the application from Asociación OpenStreetMap España to become an official OSMF Local Chapter. Although its geographic scope overlaps with that of the newer OSM Català chapter, both groups have stated that they do not object to the other’s status. The discussion runs until 24 November 2026.

Events

  • OpenStreetMap US has announced three events: Mapping USA is back as a free two-day virtual conference on 29 and 30 January 2027, with talk proposals open. The November Mappy Hour celebrates the 100th anniversary of Route 66 on 11 November 2026, and State of the Map US will take place in Baltimore, Maryland, from 11 to 13 June 2027.

  • To prepare for the upcoming State of the Map Nigeria 2026, the organising team, led by Victor N Sunday, Chair of SotM Nigeria 2026, paid a courtesy visit to the University of Uyo on Friday 6 November 2026.

  • Diego Gonzalez Ferreiro, Chief of the Solutions and Support Unit at the United Nations Global Service Centre, will speak at State of the Map Nigeria 2026 on ‘Open Geospatial Information for Peace, Development and Resilience: The UN Mappers Approach to Capacity Building, Collaborative Mapping and Humanitarian Action’.

  • The Open Transport Community Conference 2026, an (un)conference about Free Software and Open Data for mobility and public transport, was held at SBB Headquarters in Bern, Switzerland, from 6 to 9 October 2026. Recordings of the event are available on media.ccc.de.

Education

  • Jean-Christophe Becquet announced the return of his OpenData and OpenStreetMap course for undergraduate and master’s students at the Institut d’Urbanisme et de Géographie Alpine, Université Grenoble Alpes. The course aims to explain copyright and free licences, demonstrate the potential of open and collaborative data, and encourage students to contribute.

OSM research

  • AE35 has compared 38 recreational features, such as benches, fire pits, shelters, toilets, and outdoor artworks, in OpenStreetMap Denmark and the municipal dataset GeoFA since May 2024. The increased feature count is taken as an estimation: in OSM, the total number of features increased from 57,700 to 175,500; in GeoFA, it rose from 5,300 to 15,800. This means that OSM contained 159,750 more objects, thus it was approximately 10.9 times more efficient. The full analysis of all 38 objects can be found in a Google sheet. OpenStreetMap wins on every parameter.

Maps

  • Dim Kandin has made Adrenalin Spots, a map showing seasonal locations for kitesurfing, surfing, skiing, climbing, diving, sailing, and other sports throughout the year. The map covers around 580 spots and calculates a nightlife score based on nearby bars, clubs, restaurants, and cafés from OpenStreetMap data queried via Overpass, with locations within 5 km weighted more heavily than those within 15 km. The base map uses OpenFreeMap.

OSM in action

  • [1] Mapped Chronicles shows the real-world locations behind books, films, games, myths, and historical events on maps. Its currently 973 routes guide users through stories, stop by stop, with data, sources, and information about how accurately each location has been identified and whether it can be visited. Through the ‘Studio’, users can design their own routes and submit them for moderation review. The map is based on OpenStreetMap data.

  • MikeHur has been developing Wandering Around, a free browser game that lets players explore any town or city in the world using OpenStreetMap data.

Software

  • The Mangrove Reviews platform now allows people to import their Google Maps reviews by releasing them under an open licence, permitting their reuse in OSM-based tools like MapComplete and CoMaps.

  • devenzi has released ‘Devenzi Map Studio’, a WordPress plugin that embeds OpenStreetMap maps into websites without the need for an API key or account. The vector maps are sourced from OpenFreeMap and are rendered using MapLibre. They are designed in a full-screen editor featuring locations, areas, routes, and 3D buildings. If desired, the map can be set to load only after a click, ensuring that the integration is possible without a cookie banner and is GDPR-compliant.

  • Tina explained how to organise track data using OsmAnd’s Smart Folders feature.

  • A CoMaps contributor wrote a blog post about how the integration of Mangrove reviews with OSM data works.

  • tydo has launched ‘Tourello’, an offline app for hiking, mountain biking, and skiing (Android, iOS, macOS), which generates vector maps using OSM data via Geofabrik, elevation models from Mapterhorn, and BRouter for offline route planning. The OSM wiki lists which tags, such as sac_scale, mtb:scale, trail_visibility, and piste:difficulty the app evaluates. The beta version is free until the end of March 2027; a subscription service is planned thereafter, a move which drew criticism on the OSM Community forum because the app is not open source and free feedback is being sought there. Sarah Hoffmann, who operates Waymarked Trails, pointed out that the site’s terms and conditions only permit open-source, non-commercial use, whereupon tydo removed the API query and now builds the routes directly from OSM relations. According to wiki, the app is proprietary.

Programming

  • Geofabrik has published terms of use for its free Postpass service, which allows users to query OSM data through PostGIS. The service is intended for learners and the OSM community. To use it, a meaningful User-Agent or Referer header is required. Scraping and repeated requests is prohibited. Geofabrik offers a paid tier for commercial users and heavily used applications, or can help them set up their own server.

Releases

  • StreetComplete has just passed Apple’s review and is now officially available on the App Store.

Other “geo” things

  • A research team from National Cheng Kung University in Taiwan and the NASA Goddard Space Flight Centre have found that the manoeuvres carried out by the Artemis 2 rocket in April 2026 altered the ionosphere and disrupted GNSS signals. According to the study published in Geophysical Research Letters, ground-based GNSS systems recorded changes in electron density during three manoeuvres, which can lead to inaccurate position measurements.

  • The German Federal Cartel Office is investigating potential restrictions of completion by Google related to their map services for use in vehicle infotainment systems and is asking car manufacturers and other map service providers for input.

  • David Ding runs ‘Localingual’, an interactive world map where you can listen to recordings of languages and dialects. Clicking on a colour-coded country plays its voices; clicking again shows the regions; and volunteers can contribute their own recordings via their browser. Jornal Nota reported ► that by 2019 the site had around 18,000 recordings.

  • In an editorial, The Guardian argued that Ordnance Survey maps remain a superior way to navigate the landscape.

Upcoming Events

Country Where Venue What When
🇮🇳 Kottayam Kottayam, Kerala State of the Map Kerala (SoTM Kerala) 2026-11-14 - 2026-11-15
🇮🇪 Dublin 4 Inns Court, Winetavern Street, Dublin, D08 XY00 OpenStreetMap Ireland AGM - 2026 2026-11-14
🇹🇷 Hackerspace İstanbul OpenStreetMap İstanbul Mapathon 2026-11-15
🇮🇳 Delhi Avaya Cafe and Bakery, Green Park OSM Delhi Mapping Party No.34 (South Zone) 2026-11-15
🇫🇷 Point Com Rencontre Mapadour 2026-11-16
Politecnico di Milano, Building 4A, Aula Fassò Introduction to OpenStreetMap 2026-11-16
CartONG : Mapathons en ligne 2026-2027 2026-11-16
🇫🇷 Grenoble La Turbine Réunion du groupe local de Grenoble 2026-11-16
State of the Map Nigeria(SotM Nigeria) 2026-11-17 - 2026-11-20
Missing Maps London Mid-Month for Advanced Mappers (no training provided) (Online) [eng] 2026-11-17
🇫🇷 Lyon Tubà Réunion du groupe local de Lyon 2026-11-17
🇩🇪 Chemnitz Kaffeesatz, Chemnitz OSM-Stammtisch Chemnitz 2026-11-17
🇩🇪 Berlin Online FOSSGIS AG OSM und Outdoor 2026-11-17
🇩🇪 Bonn Dotty’s 206. OSM-Stammtisch Bonn 2026-11-17
🇩🇪 Online Lüneburger Mappertreffen (online) 2026-11-17
🇬🇧 Mott MacDonald Offices Mott MacDonald GIS Day Mapathon [18/10/2026] 2026-11-18
🇬🇧 Manchester Pegasus Group Mapathon Charity Day 2026-11-18
UO GIS Day- Knight Library Eugene Bike Infrastructure Mapathon 2026-11-18
🇺🇸 Cal Poly Humboldt Library 121 Cal Poly Humboldt GIS Day Mapathon 2026-11-18
Dublin Office / Online Tetra Tech Ireland GIS Day Mapathon 2026-11-18
🇫🇷 MJC de Vienne Réunion du groupe local de Vienne 2026-11-18
🇩🇪 Karlsruhe Schwarzer Kater Stammtisch Karlsruhe 2026-11-18
Internationale GeoWeek - Online Mapathon ÄRZTE OHNE GRENZEN (AT/CH/DE) 2026-11-18
🇨🇿 Praha Kanceláře Lékařů bez hranic - Qubix Pražský GeoWeek mapathon s Lékaři bez hranic 2026-11-19
GeoWeek Luxembourg Mapathon [FR/EN] - Hybrid 2026-11-19
🇧🇪 Gent Gemeenschappelijke ruimte Wijgaard Meetup in Gent 2026-11-19
Jena EGEA Jena - Mapathon 2026-11-19
OSMF Engineering Working Group meeting 2026-11-20
🇬🇧 Leicester University of Leicester Friends of MSF Leicester Mapathon 2026-11-20
🇫🇷 Metz Espace Arob@se - Metz Atelier OpenStreetMap Metz 2026-11-21
🇫🇮 Espoo Aalto-University, Space 21. OSM Suomi 2026 2026-11-21
DTU Lyngby Building 357 + Aarhus location TBA EWB Student Mapathon Denmark 2026-11-22
🇩🇪 Magrathea Laboratories e.V. 1. OSM Stammtisch Fulda 2026-11-22
🇨🇿 Brno Univerzitní kampus Bohunice, Kamenice 753/5, Brno, Listopadový brněnský Missing Maps Mapathon na Ústavu botaniky a zoologie 2026-11-23
🇬🇧 Llanfairfechan Library Mapwyr Cymru: Mapathon Gogledd Cymru #2 🏴󠁧󠁢󠁷󠁬󠁳󠁿 2026-11-23
CartONG : Mapathons en ligne 2026-2027 2026-11-23
🇩🇪 Stadtgebiet Bremen Online und im Hackerspace Bremen Bremer Mappertreffen 2026-11-23
Room VIII, Viale del Risorgimento 4, Bologna Unibo Mapathon 2026-11 2026-11-24
Pravidelný Missing Maps CZ-SK online Mapathon 2026-11-24
🇺🇸 San Jose Online South Bay Map Night 2026-11-24
🇬🇧 Derby The Brunswick, Railway Terrace, Derby East Midlands pub meet-up 2026-11-24
🇩🇪 Berlin Online OSM-Verkehrswende #80 2026-11-24
🇫🇷 La Fabrique des possibles Réunion du groupe local de Nancy 2026-11-25
🇩🇪 Düsseldorf Online bei https://meet.jit.si/OSM-DUS-2026 Düsseldorfer OpenStreetMap-Treffen (online) 2026-11-25
🇩🇪 Würzburg FabLab Würzburg Würzburger OSM-Treffen 2026-11-25
🇩🇪 Mannheim RaumZeitLabor, Mannheim Rhein-Neckar OSM Treffen 2026-11-25
🇩🇪 Freiburg im Breisgau CCCFR OSM-Treffen Freiburg/Brsg. 2026-11-25
Prírodovedecká fakulta UK Bratislava Missing Maps mapathon Bratislava #15 2026-11-26
CartONG : Mapathons en ligne 2026-2027 2026-11-30

This weeklyOSM was produced by Bastian Greshake Tzovaras, MatthiasMatthias, PierZen, Strubbl, Andrew Davidson, barefootstache, derFred, vicksun.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

Saturday, 14. November 2026

OpenStreetMap User's Diaries

Mi experiencia en el Mapatón Nacional de México 2025: cartografiar edificios para fortalecer la información territorial

Mi experiencia en el Mapatón Nacional de México 2025: cartografiar edificios para fortalecer la información territorial

¿Cómo podemos analizar los riesgos de una comunidad si ni siquiera contamos con información suficiente sobre las edificaciones que existen en su territorio?

Esta pregunta resume una de las razones por las que considero tan importante la cartografía abierta para

Mi experiencia en el Mapatón Nacional de México 2025: cartografiar edificios para fortalecer la información territorial

¿Cómo podemos analizar los riesgos de una comunidad si ni siquiera contamos con información suficiente sobre las edificaciones que existen en su territorio?

Esta pregunta resume una de las razones por las que considero tan importante la cartografía abierta para la Gestión Integral del Riesgo de Desastres.

Durante agosto y septiembre de 2025 tuve la oportunidad de participar como voluntaria en el Mapatón Nacional de México 2025, una iniciativa de cartografía colaborativa vinculada con el Centro Nacional de Prevención de Desastres (CENAPRED), la Secretaría de Desarrollo Agrario, Territorial y Urbano (SEDATU), la Universidad Autónoma del Estado de México (UAEMéx) y Humanitarian OpenStreetMap Team (HOT).

El objetivo fue contribuir a la actualización y precisión de la cartografía base utilizada para la gestión del riesgo y la planeación territorial.

¿En qué consistió mi participación?

Mi actividad se concentró en la digitalización de edificaciones en localidades del estado de Chiapas, donde existían vacíos de información cartográfica.

A través de OpenStreetMap participamos en la identificación y representación de edificios, contribuyendo a mejorar la disponibilidad de información geoespacial abierta.

Aunque pudiera parecer una tarea sencilla, representar correctamente las edificaciones tiene implicaciones importantes para el conocimiento del territorio.

¿Qué relación tiene esto con la Gestión Integral del Riesgo?

Para analizar un riesgo necesitamos conocer, entre otros aspectos, las amenazas presentes, los elementos expuestos y sus condiciones de vulnerabilidad.

La cartografía de edificaciones constituye uno de los insumos que pueden utilizarse para identificar espacialmente elementos potencialmente expuestos a fenómenos como inundaciones, sismos o movimientos de ladera.

Por supuesto, la presencia de un edificio en el mapa no permite determinar por sí sola su vulnerabilidad, ocupación o nivel de riesgo. Para ello se requieren otras fuentes de información, trabajo de campo y metodologías de análisis.

Sin embargo, disponer de una cartografía base más completa representa un avance importante para desarrollar evaluaciones territoriales mejor fundamentadas.

Lo que me dejó esta experiencia

Como consultora especializada en Protección Civil y Gestión Integral del Riesgo de Desastres, esta participación reforzó mi interés por integrar la cartografía abierta, los sistemas de información geográfica y el análisis de datos en los procesos de prevención.

También me permitió valorar el trabajo de las comunidades de mapeadores que, mediante contribuciones voluntarias, ayudan a mejorar información territorial que puede ser utilizada por investigadores, autoridades, organizaciones y ciudadanía.

El 6 de octubre de 2025 recibí el Certificado de Participación Activa en Proyecto de Impacto Social, por mi colaboración en el Mapatón Nacional de México 2025.

Una línea de trabajo que quiero continuar

Soy colaboradora de OpenStreetMap desde diciembre de 2011 y actualmente busco dar mayor continuidad a mis aportaciones, especialmente en temas relacionados con edificaciones, infraestructura esencial, accesibilidad y cartografía útil para la prevención.

Desde mi actividad profesional en Prevención Total, me interesa seguir explorando cómo los datos geoespaciales abiertos pueden complementar los estudios de riesgos, la planeación preventiva y la resiliencia territorial.

Porque antes de analizar los riesgos de un territorio, necesitamos conocerlo.

Y aquello que no está representado en nuestros datos puede quedar fuera de nuestros análisis.

Lizette Adriana Llamas Escamilla

Consultora en Gestión Integral del Riesgo de Desastres y Protección Civil.

Prevención Total Protección Civil 4.0