Style | Standard • Cards

OpenStreetMap Blogs

Sunday, 20. September 2026

OpenStreetMap User's Diaries

Edificios colapsados por el temblor de agosto 10 con epicentro en El Palmar

El pasado 10 de agosto de 2026, Colombia fue golpeada por un fuerte sismo en la zona occidental de Colombia, en el departamento de Chocó.

Las afectaciones se dieron en muchos lugares de Colombia, donde las ciudades de Pereira, Cali y Chocó tuvieron muchas afectaciones, como edificios colapsados.

Debido a que monté un canal de WhatsApp para ChatMap muy temprano el mismo día del te

El pasado 10 de agosto de 2026, Colombia fue golpeada por un fuerte sismo en la zona occidental de Colombia, en el departamento de Chocó.

Las afectaciones se dieron en muchos lugares de Colombia, donde las ciudades de Pereira, Cali y Chocó tuvieron muchas afectaciones, como edificios colapsados.

Debido a que monté un canal de WhatsApp para ChatMap muy temprano el mismo día del temblo, se han podido recoger muchos datos en terreno de las afectaciones. Igualmente, con el apoyo de la empresa Rumbo Digital pudimos una aplicación para funcionamiento offline y recolección masiva de reportes en terreno con fotos.

Todo ese proyecto de recolección de datos en terreno quedó documentado en https://d.osm.lat/palmar, y gracias a la Comunidad OpenStreetMap Colombia, como también el apoyo de HOTOSM y UN mappers, se pudo curar el contenido y tener un mapa que permite identificar las afectaciones graves.

Igualmente, gracias a la empresa FlyNorth, se han podido obtener ortofotos aéreas de zonas afectadas, con lo que estamos actualizando osm.

Este es el mapa con todos los datos que tenemos: https://umap.openstreetmap.fr/en/map/activaciones-de-mapeo-en-osm-por-terremoto-en-el-p_1450567

Aquí, una consolidación de todas las construcciones colapsadas, las cuales ya se mapearon o se deben actualizar en OpenStreetMap como demolished. Se tiene la dirección, el elemento en osm (o el más cercano), una visualización en Google StreetView y las fotos de los reportes.

Quibdó

Dosquebradas

Pereira

Arabia

osm.org/way/268093768 - https://maps.app.goo.gl/nnaKa13n2VphaBsFA - https://chatmap.hotosm.org/api/v1/media/9ba9f643-0840-4915-ba69-c1dc74a8b6f2.jpg

Calima el Darién

Cali

20:44 • a day ago

weeklyOSM

weeklyOSM 843

10/09/2026-16/09/2026 [1] Geolocation of text data | © Image: DLR | Map data © by OpenStreetMap Contributors. Mapping v7.2.0 of the iD tagging schema has been released and includes tweaks to labels, new icons, changed fields for various presets, new search terms, better documentation, improved build scripts, and more. Helper presets for some subvariants of…

Continue reading →

10/09/2026-16/09/2026

lead picture

[1] Geolocation of text data | © Image: DLR | Map data © by OpenStreetMap Contributors.

Mapping

  • v7.2.0 of the iD tagging schema has been released and includes tweaks to labels, new icons, changed fields for various presets, new search terms, better documentation, improved build scripts, and more. Helper presets for some subvariants of aerialway stations, silos, and parking spots were added to make mapping easier. An actual new preset was added for offshore platforms. It includes bugfixes such as dropping bad suggestions, taginfo report includes addTags, and post boxes in USA no longer have duplicate drivethrough fields. Work continues in the background on some larger features, but changes listed above will soon be present in iD, GoMap!!, EveryDoor, StreetComplete, and other editors.

Community

  • Andy Allan gave a talk at State of the Map 2026 about how OpenStreetMap’s transport layer migrated from server-side rendered map tiles to client-side rendered vector styles.
  • The CoMaps team shared their experience of attending State of the Map in Paris.
  • dia-jules explained, in the context of the USA, how unnecessary traffic light penalty times arise in OSRM and similar route planners, and how to reduce them specifically. If junctions on shared trunk roads are tagged as usual with highway=traffic_light at each node, the router counts multiple delays per junction, even though in reality only one set of traffic lights is passed. The more precise method instead places the tag individually at the stop line using traffic_light=signal and traffic_light:direction, so that each route passes through only one traffic light junction. To prioritise the revision, dia-jules drew on traffic volume and accident data from the Illinois Department of Transportation for the Greater Chicago area.
  • Emmanuel Arrechea looked back on State of the Map 2026, held at the École Géodata in Paris, where he and other members of LaNum Pays Basque and Mapadour joined 535 participants from 45 countries. He picked out five points from more than 180 talks and workshops, among them the sponsorship of the conference by companies such as Michelin, TomTom, Esri, Thales, and Capgemini, and the way organisations including IGN, SNCF, and Géovélo build their services on OSM data. He also highlighted Grant Slater’s talk on AI crawlers straining OSMF infrastructure and driving some 400 fake account registrations a day. Most sessions are available on OSM France’s PeerTube channel with French subtitles.

OpenStreetMap Foundation

  • Chris Fleming explained, in an OSM Blog post, how naming works in OpenStreetMap, from the primary name= tag to additional keys such as name:en= and official_name=. He used the recent official_name:en-US=Lake America addition to Lake Ontario as an example of how the name tag remains unchanged even after an official renaming, so the lake remains findable under both names. He also noted that OpenStreetMap volunteers have mapped over 115 million names to date.

Local chapter news

  • Jochen Topf and Katja Haferkorn of FOSSGIS reported ► that the German Federal Ministry for Digitalisation and Public Sector Modernisation is inviting the open data community, stakeholders, and the interested public to participate in an online consultation to gather proposals and suggestions for a more developed framework, to be known as the ‘Roadmap for Open Data’. FOSSGIS has also compiled a statement on the topic.

Events

Education

  • High5apps explained how to add a website tag to a shop or amenity using JOSM. This short tutorial sparked quite a discussion on HackerNews.
  • Aoyama Gakuin University’s Furuhashi Laboratory have published a video lecture for the 2026 academic year’s ‘Basic Spatial Information Science B’ course, which covers various topics related to OpenStreetMap.

OSM research

  • HeiGIT presented an analysis of cycling infrastructure in 885 European cities, using OpenStreetMap data together with tree canopy and heat-stress data to assess how well cycling routes are protected from heat.
  • HeiGIT presented new indicators for its hiWalk tool, developed in collaboration with Walk21, that use OpenStreetMap and other open data to assess factors such as path lighting, tactile paving, tree shade, and access to everyday services, providing a more comprehensive picture of urban walkability.

Maps

  • cultours.app is a free interactive map of roughly 100,000 cultural heritage sites in Germany: castles, churches, ruins, memorials including Stolpersteine, Roman and prehistoric sites, towers, and viewpoints. Data comes from OpenStreetMap via Overpass, enriched with Wikipedia and Wikidata. No login, no cookies, no tracking. The developer introduced the project in the German community forum and is looking for feedback on a couple of tagging questions there.
  • Dachlast.de presented an OSM-based camping map for Germany and neighbouring countries, which combines a route planner with eight data layers. The map shows campsites, motorhome pitches, drinking water points, toilets, showers, supply and disposal points, charging points, and petrol stations along the planned route. The data is ‘harvested’ weekly from OpenStreetMap and, according to the operator, comprises around 400,000 points in the area stretching from Denmark to northern Italy, eastern France and western Poland.
  • The Planet Thinks is a fully turnable globe displaying live changesets on OpenstreetMap as coloured sparks.

OSM in action

  • [1] The Institute of Data Sciences at the DLR (German Aerospace Centre) explained ► how geoparsing, that is, the identification of place names in texts and their association with geographical points, lines, or polygons, makes geodata usable for crisis management, supply chains, and research. The team is developing methods for toponym recognition and disambiguation, comparing these against multilingual benchmark data and applying them in various DLR projects, such as geolocating social media content during crises or analysing supply chains in the aviation industry. These methods are also being incorporated into the EU project OpenWebSearchEU, which aims to create a European alternative to dominant search providers, as well as into the collaboration with the Joint Research Centre on news analysis for European decision-makers.
  • Heise reported that the interactive map by the action alliance ‘Heiße Luft‘ shows the locations of planned and under-construction data centres in Germany.
  • Greenways Ireland presented the official website of the Irish Department of Transport for the country’s growing network of car-free cycle and walking routes. The interactive map uses OpenStreetMap with proper attribution and can be filtered by region, theme, and route length. As well as route descriptions, the site provides up-to-date information on route closures and an overview of the national greenway strategy.
  • The Bayreuther Tagblatt reported ► that St.-Georgen-Straße in Bindlach will be completely closed for around four days from 21 September due to development work. One positive point is that the map of the surrounding area used in the article is credited as ‘© openstreetmap.org/copyright’.
  • Dominik Hochwarth, of Ingenieur.de, reported ► that TU Graz has developed an OpenStreetMap-based tool that estimates the amounts of concrete, brick, and wood contained in buildings. The programme first determines a building’s size and geometry using OpenStreetMap data, then incorporates its building type, year of construction, construction method, and energy efficiency class. Based on this information, the software identifies a suitable building archetype and calculates which materials were likely used in its construction.

Software

  • Steven Hooper has built BadCaddie, an app that uses OpenStreetMap golf-course data for course discovery and hole maps, alongside GNSS yardages, scorekeeping, and club suggestions, based on recorded shot distances. It is available for iPhone with an Apple Watch companion and as a plugin for Even Realities G2 glasses.
  • Ian Wagner explained how Stadia Maps has been taking a fresh look at the cartographic decisions at every level of their map stack. Their recent water layer changes and water label updates have made a visible difference to the Stamen Terrain style.
  • Tina reported that OsmAnd now allows users to colour their tracks based on speed, altitude, or slope data. Custom colour palettes help turn complex GPX data into clear, meaningful visual stories.

Releases

  • The CoMaps team has released version 2026.08.31, which is now out across all release channels. New features include the display of reviews from Mangrove Reviews and a new transport modes UI on iOS.
  • The OpenStreetMap Carto maintainers have prepared version 6.1.0 of the OpenStreetMap Carto stylesheet. Christoph Hormann detailed the visible changes introduced by this release in an OSM diary post.

Other “geo” things

  • TechCrunch reported that Tern has won a contract from the US Army to deploy its low-cost GNSS alternative technology. The US$11.26 million contract will see the Army use Tern’s navigation technology in vehicles. According to its official website, Tern is developing a positioning system that does not rely on satellites, signals, or external infrastructure. It has been tested by the US Departments of Transportation and Defense.
  • ABC Science’s Julian O’Shea explored how Australia has been mapped ‘wrong’ from a 1547 world map to modern GPS.

Upcoming Events

Country Where Venue What When
🇩🇪 Kiel Kieler Innovations- und Technologiezentrum OSM auf der Kielux 2026 2026-09-18 – 2026-09-19
🇮🇳 Mumbai Lokhandwala Garden, Andheri OSM Mumbai Mapping Party No.14 (Andheri) 2026-09-19
🇮🇳 Delhi Too Mikkii Tapas, South Extension OSM Delhi Mapping Party No.31 (South Extension) 2026-09-20
🇪🇸 Madrid Online Mappy Hour OSM España 2026-09-22
🇬🇧 Derby The Brunswick, Railway Terrace, Derby East Midlands pub meet-up 2026-09-22
🇩🇪 Berlin Online OSM-Verkehrswende #79 2026-09-22
🇮🇹 Catania Piazza Roma, Catania (Punto di incontro) Mappiamo le piste ciclabili – Catania 2026-09-22
Building 4A, First Floor – Politecnico di Milano PoliMappers Maptedì 2026-09-23
🇫🇷 Nantes Le Wagon Nantes OpenStreetMap, la carte à la carte ! 2026-09-23
🇩🇪 Hannover Kuriosum Stammtisch 2026-09-23
🇩🇪 Würzburg FabLab Würzburg Würzburger OSM-Treffen 2026-09-23
🇬🇧 City of Westminster Blue Posts pub London pub meet-up 2026-09-23
Pravidelný Missing Maps CZ-SK online Mapathon 2026-09-24
🇧🇷 100% online 🇧🇷 Lançamento de livros sobre mapeamento colaborativo 2026-09-24
🇩🇪 Freiburg im Breisgau CCCFR, Adlerstr. 12 a, Freiburg/Br. OSM-Treffen Freiburg/Br. 2026-09-24
🇮🇳 Bengaluru NIMHANS Convention Center OSM India @ IndiaFOSS 2026 2026-09-25 – 2026-09-27
UN Mappers Mappy Hour 2026-09-25
🇲🇽 Torreón Universidad Tecnológica de Torreón Conferencia “OpenStreetMap: Datos abiertos y más” 2026-09-25
🇲🇽 Torreón Universidad Tecnológica de Torreón Taller “Mapeando mi entorno” 2026-09-25
🇩🇪 Düsseldorf Online bei https://meet.jit.si/OSM-DUS-2026 Düsseldorfer OpenStreetMap-Treffen (online) 2026-09-25
🇩🇪 Karlsruhe Geofabrik, Amalienstraße 44, 76133 Karlsruhe Karlsruhe Hack Weekend September 2026 2026-09-26 – 2026-09-27
🇫🇷 Nantes Le Wagon Nantes OpenStreetMap, la balade de la data 2026-09-26
Sudan Solidarity Series 2026-09-26
🇸🇪 Uppsala Datorföreningen Update Mapping meetup in Uppsala 2026-09-27
CartONG : Mapathons en ligne 2026-2027 2026-09-28
🇩🇪 Magdeburg Netz39 e.V. , Leibnizstraße 32, 39104 Magdeburg 4. OSM Stammtisch Magdeburg 2026-09-29
🇺🇸 Palo Alto Startup Island Taiwan South Bay Wiki and OpenStreetMap Meetup 2026-09-29
🇩🇪 Mannheim RaumZeitLabor, Mannheim Rhein-Neckar OSM Treffen 2026-09-30
🇫🇷 Angers L’Arrière Train, 3 rue de Frémur, Angers Angers Rencontre mensuelle OpenStreetMap 2026-10-01
🇫🇷 Bar Le Schmilblik Rencontre mensuelle des contributeurs Paris sud 2026-10-01
🇮🇹 Messina Fablab Messina (via Croce Rossa 63, 98124 Messina) Hackathon Wikimedia & OSM 2026-10-02 – 2026-10-04
🇩🇪 Essen Linuxhotel Essen FOSSGIS-OSM-Communitytreffen Nr. 26 im Linuxhotel 2026-10-02 – 2026-10-04
🇪🇸 Langreo Casa de la Cultura “Escuelas Dorado” GeoCamp 2026 2026-10-03
🇮🇳 नई दिल्ली Jitsi Meet (online) OSM India – Monthly Online Mapathon 2026-10-03
🇩🇪 Essen Verkehrs- und Umweltzentrum Essen OSM-Treffen 2026-10-03
🇹🇼 臺北市 MozSpace Taipei OpenStreetMap x Wikidata Taipei #93 2026-10-05

Note:
If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

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

11:31 • a day ago

Saturday, 19. September 2026

OpenStreetMap User's Diaries

Heritage railways and bikes on board: four changesets, two modelling questions

I build Tisseur de Voies, a site that computes loops where you ride one way and take the train back. Heritage railways fit that model well, because many of them carry bikes for free in a dedicated van, where regular regional trains count them. Trying to use them, I found the same situation almost everywhere: the tracks are in OSM, the service line is not. A data consumer sees a railway, with no

I build Tisseur de Voies, a site that computes loops where you ride one way and take the train back. Heritage railways fit that model well, because many of them carry bikes for free in a dedicated van, where regular regional trains count them. Trying to use them, I found the same situation almost everywhere: the tracks are in OSM, the service line is not. A data consumer sees a railway, with no way to tell that a train runs on it, where it stops, or who operates it. So I started adding them, one line at a time.

What I have contributed so far:

  • Le Mastrou, Ardèche, 10 August (changeset 187233238): two route=train relations, one per direction, plus their route_master.
  • Velay Express, Haute-Loire, 12 August (changeset 187362618): the same, with bicycle=limited on both directions.
  • Chemin de Fer de la Baie de Somme, 19 September (changeset 189261499). Here two relations already existed, but as route=railway, with from and to swapped with respect to the geometry. I retagged them route=train, named them after the operator’s own routes, and filled in operator.
  • Le Grand Large, the same day (changeset 189262951), the creation behind my first question.

1. One journey sold end to end, but two trains and a 200 m walk

The Chemin de Fer de la Baie de Somme sells three journeys on its metre-gauge network: « Entre Terre et Prés-Salés » between Le Crotoy and Saint-Valery, « Les Bas-Champs » between Saint-Valery and Cayeux-sur-Mer, and « Le Grand Large », Le Crotoy to Cayeux in 1 h 35. The third one combines the other two, and the change happens at Saint-Valery between two stations two hundred metres apart, on foot.

I mapped it as a third route=train relation. Its ways form a continuous chain from end to end, since the track does link the two Saint-Valery stations (I added the sixty metres that were missing along the quay), and yet no single train runs the whole thing. That is what bothers me, and I would rather raise it than let someone find it.

A route_master grouping the two short journeys would match what the trains actually run, at the cost of losing the single ticketed, timetabled journey that exists end to end. Leaving it out of OSM entirely hides the only itinerary that crosses the whole network. How do you handle this elsewhere, a walking transfer inside a single commercial product?

2. Declared stops, when the station node sits away from the track

On these lines, some stations are mapped as a railway=station node on the station building, a few dozen metres from the rails. Anyone looking for stops by walking the nodes of the member ways misses them. That is exactly what happened to me on Velay Express, where Saint-Agrève, the end of the line that matters most for a loop, was nowhere to be found.

So I listed the stations as role=stop members of the relation, including those whose node is off the track. The list becomes explicit, and a data consumer no longer has to infer it from topology. This departs from the letter of PTv2, where role=stop expects a public_transport=stop_position on the way, these relations being tagged public_transport:version=1. On a heritage line, should I also add a stop_position on the track facing each building, or is the declared list enough?

What it adds up to

These four changesets show up directly in the data I publish: four bike loops with a heritage-train return, on Tisseur de Voies. The Baie de Somme one, 29 kilometres of which 28 on signed cycle routes, did not exist before the 19 September relation. Alignments and stations come from OSM, the cycle routes from OSM and the French national reference.

Corrections welcome, including on the first point. If the right answer is to delete the « Le Grand Large » relation, I will delete it.

Nicolas

19:27 • 2 days ago

Trains touristiques et vélo à bord : quatre changesets, deux questions de modélisation

Je construis Tisseur de Voies, un site qui calcule des boucles où l’on part à vélo et où l’on rentre en train. Les lignes touristiques m’intéressent pour une raison simple : beaucoup embarquent les vélos gratuitement, dans un fourgon prévu pour ça, là où le TER les compte. En cherchant à les exploiter, j’ai trouvé la même situation presque partout. Les rails sont dans OSM, la ligne de service n’

Je construis Tisseur de Voies, un site qui calcule des boucles où l’on part à vélo et où l’on rentre en train. Les lignes touristiques m’intéressent pour une raison simple : beaucoup embarquent les vélos gratuitement, dans un fourgon prévu pour ça, là où le TER les compte. En cherchant à les exploiter, j’ai trouvé la même situation presque partout. Les rails sont dans OSM, la ligne de service n’y est pas. Un consommateur de données voit une voie ferrée, sans savoir qu’un train circule dessus, ni où il s’arrête, ni qui l’exploite. J’ai donc commencé à les ajouter, une ligne à la fois.

Ce que j’ai contribué jusqu’ici :

  • Le Mastrou, en Ardèche, le 10 août (changeset 187233238) : deux relations route=train, une par sens, et leur route_master.
  • Velay Express, en Haute-Loire, le 12 août (changeset 187362618) : le même geste, avec bicycle=limited sur les deux sens.
  • Chemin de Fer de la Baie de Somme, le 19 septembre (changeset 189261499). Là, deux relations existaient déjà, mais en route=railway, avec des from et to inversés par rapport à la géométrie. Je les ai passées en route=train, renommées avec les noms que l’exploitant donne à ses parcours, et j’ai renseigné operator.
  • Le Grand Large, le même jour (changeset 189262951), la création qui pose ma première question.

1. Un parcours vendu de bout en bout, mais deux trains et 200 mètres à pied

Le Chemin de Fer de la Baie de Somme vend trois parcours sur son réseau métrique : « Entre Terre et Prés-Salés » entre Le Crotoy et Saint-Valery, « Les Bas-Champs » entre Saint-Valery et Cayeux-sur-Mer, et « Le Grand Large » qui relie Le Crotoy à Cayeux en 1 h 35. Ce troisième parcours cumule les deux autres, et le changement se fait à Saint-Valery entre deux gares distantes de deux cents mètres, que l’on franchit à pied.

J’en ai fait une troisième relation route=train. Ses ways forment une chaîne continue d’un bout à l’autre, la voie reliant bien les deux gares de Saint-Valery (j’ai complété les soixante mètres qui manquaient le long du quai), et pourtant aucun train ne la parcourt d’un seul trait. C’est le point qui me gêne, et je préfère le poser ici plutôt que de le laisser se découvrir.

Un route_master regroupant les deux parcours courts collerait mieux à ce que roulent les trains, au prix du trajet vendu, horairé et chronométré de bout en bout, qui disparaîtrait des données. À l’inverse, laisser ce troisième parcours hors d’OSM rend invisible le seul itinéraire qui traverse le réseau entier. Comment traitez-vous ce cas ailleurs, une correspondance à pied à l’intérieur d’un produit commercial unique ?

2. Des arrêts déclarés, quand la gare est en retrait de la voie

Sur ces lignes, une partie des gares est mappée en nœud railway=station posé sur le bâtiment voyageurs, à quelques dizaines de mètres des rails. Qui cherche les arrêts en parcourant les nœuds des ways membres passe à côté. C’est exactement ce qui m’est arrivé sur Velay Express, où la gare de Saint-Agrève, le bout de ligne le plus utile pour une boucle, manquait à l’appel.

J’ai donc listé les gares en membres role=stop de la relation, y compris celles dont le nœud est en dehors de la voie. La liste devient explicite, et un réutilisateur n’a plus à la deviner par topologie. Cela s’écarte de la lettre de PTv2, où role=stop attend un public_transport=stop_position posé sur la voie, ces relations étant d’ailleurs en public_transport:version=1. Faut-il, sur une ligne touristique, poser en plus un stop_position face à chaque bâtiment, ou la liste déclarée suffit-elle ?

Ce que ça donne à l’arrivée

Ces quatre changesets se lisent directement dans les données que je publie : quatre boucles vélo avec retour en train touristique, sur Tisseur de Voies. Celle de la baie de Somme, 29 kilomètres dont 28 sur voie balisée, n’existait pas avant la relation du 19 septembre. Les tracés et les gares viennent d’OSM, les véloroutes d’OSM et du référentiel national.

Je prends volontiers les corrections, y compris sur le premier point. Si la bonne réponse est de supprimer la relation « Le Grand Large », je la supprimerai.

Nicolas

19:26 • 2 days ago

Fall 2026

For fall of 2026, I’ve recently resumed contributing and have transitioned from focusing on Paola, KS to Lawrence, KS. This is a move I hope to also make in real life in early 2027; until then it will mostly be working off of Esri aerial imagery and mapillary street level photos.

Once moved I’ll be able to survey things properly, and in the medium term after that the hope is also to sta

For fall of 2026, I’ve recently resumed contributing and have transitioned from focusing on Paola, KS to Lawrence, KS. This is a move I hope to also make in real life in early 2027; until then it will mostly be working off of Esri aerial imagery and mapillary street level photos.

Once moved I’ll be able to survey things properly, and in the medium term after that the hope is also to start to capture 360 camera imagery by bicycle. I don’t have one due to price and the fact that I couldn’t justify one when mapping Paola.

Things that have caught my interest:

  • Adding parking downtown
  • Seeing if I like micro mapping things like land use. (will probably do this as a palette cleanser between working on other groupings of tasks)
  • Adding crossing ways to the bike paths instead of just nodes
  • Finding bicycle parking and repair stands
  • Searching for cycleways

Observation on bike routes

The bike route signage situation on the ground is a bit unclear. In some areas the mapillary coverage is good enough to start to tackle that now. In lower traffic areas it will probably be necessary to be in the area to handle properly. Bicycle route relations exist for the area, but seem to have been done by several people and don’t have a coherent style. Making them consistent will likely be a long term project that will require actually having the local network already in my head.

Searching for cycleways via Aerial Imagery

Using the Esri imagery, which seems to date from 2024, I’ve found several streets where cycleways were tagged, and a few areas where tagging needed to be removed.

W 21st bike boulevard

bicycle_road and cyclestreet both exist, I’m unsure if they should be used or not.

To be mapped:

  • Sharrows
  • Bike Lanes
  • Streetside parking boxes
  • Chicanes
  • Turn lanes (are these done?)
  • lane markings (seen in chicanes)

Searched Areas

Completed

  • Everything Between Mass and Haskell
  • Everything East of Haskell (excluding venture park)
  • Prairie Park
  • North Lawrence
  • Park Hill and Breezedale Neighborhoods

Notes for the the future

  • In North Lawrence, it looks like sharrows have been added since the Esri images were taken, seen on mapillary on area of 8th and Walnut
  • It looks like 11th street east of mass had a stretch of sharrows that wore away before the Esri imagery was taken, needs surveyed to see if they’ve been repainted.
  • It looks like Connecticut had sharrows that wore away before the Esri imagery was taken, needs surveyed to see if they’ve been repainted.
14:42 • 2 days ago

Aubin Grove Diary - Log 1

Log 1

7:00 PM 19/08/2026

Beginning of Aubin Grove Development. Preview of my home-suburb on the OSM map provides little to no information of locations and landmarks. Using memory of my previous home when I was a child, I was able to remember parts of the house people wouldn’t be able to see on a map very easily with the low-resolution satellite imagery. House address 12 Cape Le G

Log 1

7:00 PM 19/08/2026

Beginning of Aubin Grove Development. Preview of my home-suburb on the OSM map provides little to no information of locations and landmarks. Using memory of my previous home when I was a child, I was able to remember parts of the house people wouldn’t be able to see on a map very easily with the low-resolution satellite imagery. House address 12 Cape Le Grand Avenue is added for the first marked residential building in Aubin Grove.

Locating my original Primary School, Aubin Grove Primary School, was easy from memory. I noticed multiple discrepancies and immediately improved to location. All discrepancies were fixed and possibly more zones will be added in the future logs.

11:02 • 2 days ago

Friday, 18. September 2026

OpenStreetMap User's Diaries

Day 1.1

Every single driveway and sidewalk connection on every road beginning with A has been done. 17 of… 602. AGH.

Every single driveway and sidewalk connection on every road beginning with A has been done. 17 of… 602. AGH.

21:52 • 3 days ago

Day 1

Fucking diaries? Hell yeah. Anyways, I wanna clean my town up. Driveways and sidewalks are woefully unmapped… I have little idea what I’m doing on a styleguide level. Stared at the wiki, learned a little bit of Overpass to pull up a list of every road in town, and now I’m just alphabetically working through it all…

Fucking diaries? Hell yeah. Anyways, I wanna clean my town up. Driveways and sidewalks are woefully unmapped… I have little idea what I’m doing on a styleguide level. Stared at the wiki, learned a little bit of Overpass to pull up a list of every road in town, and now I’m just alphabetically working through it all…

16:04 • 3 days ago

Actualización de ubicación

Una de las opciones que probé fue la actualización de ubicación, e muy precisa

Una de las opciones que probé fue la actualización de ubicación, e muy precisa

13:58 • 3 days ago

Thursday, 17. September 2026

OpenStreetMap User's Diaries

Hello

New here, but excited to help. I’ve been using StreetComplete on my commute to help get some things updated and cleaned up here in Vermont

New here, but excited to help. I’ve been using StreetComplete on my commute to help get some things updated and cleaned up here in Vermont

17:19 • 4 days ago

Chvála "old_name"

Moc prosím: když někdo mění názvy nějakého objektu, přeneste starý název do old_name. Ať už je to jméno budovy, ulice nebo zastávky MHD.

Je úplně úžasné, když existuje místo, které plní i funkci “historického překladače”. Když mluvíte se starousedlíkem, který vás posílá na Tesco u tramvaje “Zahrádky”, ale v ostatních mapách nic takového není, protože zastávka byla přejmenová

Moc prosím: když někdo mění názvy nějakého objektu, přeneste starý název do old_name. Ať už je to jméno budovy, ulice nebo zastávky MHD.

Je úplně úžasné, když existuje místo, které plní i funkci “historického překladače”. Když mluvíte se starousedlíkem, který vás posílá na Tesco u tramvaje “Zahrádky”, ale v ostatních mapách nic takového není, protože zastávka byla přejmenována na “Třebovice, OC”. Nebo když starousedlíci mluví o “Bachnerovi”, protože “Prior Horník” se vždy tak nějak pletl s “Prior Úderník” o dvě ulice vedle a s “Prior Hutník” o tři ulice a náměstí vedle. Dneska je tam “Bang Bang” a kdo ví, co to bude za rok.

Zejména na budově Sokolská 1, Ostrava je vidět význam této položky, když 80-letý řekne “Ander” nebo “ASO”, 50-letý něco jako “Starý Prior u Masarykáče, chvilku to bylo taky Laso”, 30-letý “stará VZP” a pro mladší je to prostě “ten barák jak se tam čeká na zastávce Sýkorák, dole se střídají různé sekáče s hadrama a je tam dost nachcáno”. A ano, všechny ty názvy jsou živé.

Najít stránku, kde je toto vše zdokumentováno, zabralo docela dost času a pro neznalé by byl problém si ji zase naopak spojit s konkrétními souřadnicemi… to je obecně podivný neduh různých historických stránek o architektuře, že neuvádějí souřadnice. A OSM má díky old_name unikátní vlastnost historii a souřadnice propojit.

09:47 • 4 days ago

Wednesday, 16. September 2026

OpenStreetMap User's Diaries

Actualización de vía y ubicación _puerto de engabao

He verificado la vía Guayas 129 en Puerto Engabao, Punta de Piedra. Confirmo su recorrido y coordenadas. Todo coincide con lo que se ve en el terreno.

He verificado la vía Guayas 129 en Puerto Engabao, Punta de Piedra. Confirmo su recorrido y coordenadas. Todo coincide con lo que se ve en el terreno.

23:19 • 5 days ago

Prioritizing Traffic Light Penalties with Traffic Counts

Impetus

Many routers, such as OSRM,1 set penalties for barriers like traffic lights or at-grade crossings, to estimate time lost at these points. For intersections with traffic lights, the standard procedure is to put a tag of highway=traffic_light at the intersecting node. For divided highway intersections, common practice is to tag each intersecting node also.

♦

T

Impetus

Many routers, such as OSRM,1 set penalties for barriers like traffic lights or at-grade crossings, to estimate time lost at these points. For intersections with traffic lights, the standard procedure is to put a tag of highway=traffic_light at the intersecting node. For divided highway intersections, common practice is to tag each intersecting node also.

Example of excess traffic light penalty

This quickly adds up to excess penalty for the simple router.2 On a cross-traffic turn (left turns in the United States), this will lead the router to count three penalties per intersection. But, time spent at these intersections is not near three times the normal intersection, especially considering a cross-traffic turn often has first priority and protected access along divided highways.

The more-detailed method of tagging removes the unnecessary penalties. Instead of tagging highway=traffic_light at every intersection, a node is placed at every stop line to the intersection.

Now, in every road-legal path, the route will pass through only one traffic light node, with the following tags:

OSM highway = traffic_light traffic_light = signal traffic_light:direction = forward/backward

The directionality tag is not necessary on one-way segments, but it is better to keep explicit and consistent with two-way segments.

Although this tagging is ideal, it would be intensive for mappers to correct every intersection like this. An intersection of two undivided highways, for instance, need not be updated, since the node graph already adds only one traffic light penalty. But any intersection with at least one divided highway has a route that will pass through multiple intersecting nodes.

To prioritize the routes most in-need of review, I searched for intersections likely to accumulate the most delay from these penalties. The first method analyzed high-volume roadways, and the second analyzed intersections with the most accidents.

Highway traffic volume

My first method was to look at stretches of highway with the most annual average daily traffic (AADT). Due to being high volume, these roads are likely to be divided, and are also guaranteed to have vehicles passing through key intersections (resulting in lots of total excess penalty).

I downloaded the 2026 data on AADT from IDOT’s webpage.3 I removed all motorways without traffic lights and filtered the data for segments in Chicagoland with an AADT over 40,000 vehicles per day (sorted by distance from downtown), returning the following short list:

  • Cicero Ave (Ogden–87th),
  • Harlem (Stevenson–50th),
  • First Ave (Ogden–Stevenson),
  • North Ave (Mannheim–1st),
  • Mannheim Ave (I-194–Butterfield),
  • 87th St (Roberts–Central),
  • La Grange Rd (143rd–191st),
  • Roosevelt Rd (Meyers–I 294),
  • Kingery Ave (Touhy–Stevenson),
  • Butterfield Rd (Veterans Tlwy–22nd),
  • North Ave (Gary–Kingery),
  • and a few small sections of road between Elgin and Addison)

I reviewed every intersection on these segments for divided highways, and tagged appropriately.

Intersection crashes

The second method was to analyze which intersections them receive the most crashes per year. By itself, an intersection with many crashes indicates that drivers already have some difficulty in navigating the roadway, so the extra detail is doubly appropriate.

IDOT also maintains a database of vehicle crash data by year.4 Based on the 2025 data, I found 70,287 intersection-related crashes in Chicagoland, out of 300,000 total crashes in Illinois. I clustered the individual crashes to a radius of 400 feet (the average length of a block in Chicago). Below is a table with the most total crashes, as well as their neighborhood.

Cluster name Crashes in 2025 Neighborhood
Ohio Street off-ramp 224 Near North Side, Chicago
Congress Parkway off-ramp 157 Loop, Chicago
Wacker/Michigan Ave 141 Loop, Chicago
79th/Stony Island/South Chicago 127 South Shore, Chicago
Ohio/Michigan 108 Near North Side, Chicago
Ohio/Dearborn 100 Near North Side, Chicago
111th/Harlem 77 Worth, IL
Pershing/Western 72 McKinley Park, Chicago
95th/Stony Island 68 South Deering, Chicago
Stevenson Expwy/Cicero 60 Garfield Ridge, Chicago
I 57/Halsted 54 Washington Heights, Chicago
Madison/Cicero 54 Austin, Chicago
Ogden/Lincoln 52 Montgomery, IL
Golf Rd/Wolf Rd (Cumberland Circle) 58 Des Plaines, IL

Downtown clusters of crash data.

The cluster radius of 400 feet turned out to be too large to analyze individual intersections, but it was still useful for generating high-crash areas.

  • Ohio Street off-ramp (Kennedy–LSD)
  • Michigan Ave (LSD–Balbo)
  • Ida B. Wells Dr
  • Roosevelt (Halsted–LSD)
  • Stony Island Ave (71st–Bishop Ford)

All of these stretches were reviewed for special traffic lights via CookOrtho2025 imagery, licensed from NearMaps.

  1. Project OSRM, OSRM Backend, “penalty.feature.” ↩

  2. I could not find a router which clusters close-together traffic lights into one. Either way, explicit tagging is better for all routing purposes, at the cost of being less clear for network maps. ↩

  3. Illinois Department of Transportation, Annual Average Daily Traffic, 2026. ↩

  4. Illinois Department of Transportation, Crashes - 2025. ↩

15:38 • 5 days ago

What 689 cycling routes look like when you measure them against OpenStreetMap

I run cyclists.com, a library of cycling routes. Every route page tries to answer what a rider wants to know before setting off: how much of it is on busy roads, whether it is paved, where the water and cafés are. Nearly all of those answers come from OpenStreetMap, so I wanted to explain how we use the data and pass back a few things we found in it.

What we measure along a route

We don

I run cyclists.com, a library of cycling routes. Every route page tries to answer what a rider wants to know before setting off: how much of it is on busy roads, whether it is paved, where the water and cafés are. Nearly all of those answers come from OpenStreetMap, so I wanted to explain how we use the data and pass back a few things we found in it.

What we measure along a route

We don’t use Overpass. A few hundred routes would be unfair load on a public instance, so everything runs against local Geofabrik extracts. For each route line we sample a point every 100 m, take the nearest way within 80 m and read its tags:

  • Road class: highway=* grouped into cycle path, quiet street, minor road, main road (primary/secondary), major road (trunk) and motorway.
  • Cycle provision: highway=cycleway, any cycleway*=* tag that isn’t no, or bicycle_road=yes.
  • “Main roads without a cycle lane”: km on primary, secondary, trunk or motorway ways with none of the above.
  • Fast roads: km where maxspeed is 80 km/h or more (mph converted).
  • Surface: surface=* first; then tracktype; then the road class (a primary road with no surface tag counts as paved, a track as unpaved). Anything else is shown as “no data” rather than guessed.
  • Services: cafés, bakeries, shops, drinking water, toilets, bike shops and railway stations within a few hundred metres of the line, placed by km along the route, plus the longest stretch with none.

Where a sample point is more than 80 m from any way, it counts as unmapped. We say so on the page instead of filling the gap.

A typical result, for a loop in the Hajar mountains above Fujairah: “Most of it (42.6 km) is on main roads without a cycle lane, 16.4 km where the limit is 80 km/h or more. The first 30 km has no café, shop or water.” And for the Deeside Way out of Aberdeen: “62% is on cycle paths or roads with a cycle lane. 52% is mapped as paved and 47% as gravel or unpaved.”

Elevation comes from the Copernicus DEM, not from OSM or from the GPS.

Signed cycle routes as route pages

In Scotland and Wales we turned every route=bicycle relation into route pages: 177 sections in Scotland, 68 in Wales, each with a GPX file. Long routes are cut at towns into stages, so the Border Loop is a four-day tour. Ferries stay in the line but end a stage.

The lesson: don’t chain a relation’s members in order. That broke at every one-way split and dual carriageway. It worked once we read each relation as a network instead:

  • snap way ends to junctions within 50 m
  • ride around roundabouts rather than along them
  • prune dead-end spurs under 2 km
  • bridge small breaks of up to 500 m once
  • take the longest path through what is left

The surface split comes from the member ways’ own tags.

Relations we couldn’t read

These are the ones worth a look if you map in Scotland or Wales. Paste the number into the search box (e.g. r11361). I’m not saying they’re wrong: some may be deliberate, and I haven’t checked each on the ground.

Fragmented (members don’t join into a rideable line):

  • NCN 73 (r11361) and NCN 753 (r2293737). My guess is that the ferry crossings aren’t members, so the island and mainland sections don’t connect.
  • NCN 776 (r105443), NCN 83 (r1328554), NCN 1: Loch Leven to Dundee (r15978437), EuroVelo 12 in Scotland (r9476219)
  • Radnor Ring (r32882), NCN 47 (r8201445), Rhondda Fawr Community Route (r8281902)

No name or ref, so we couldn’t tell riders what the route is (Scotland): r5497214, r10023468, r10023578, r10023686, r13317477, r15979588, r20395370

Generic names with no ref: “National Cycle Network National Route” (r116667), “National Cycle Network Route” (r1662719), “National Cycle Network” (r2810169), and one named just “885” (r2454549).

Two limits on our side rather than in the data. Routes that cross into England were cut off at the edge of the country extract. And a figure-of-eight route that rides one segment twice (the Gallovidian Gravel) comes out as one loop, because we don’t yet read a route that uses a way twice.

Attribution

All of this is © OpenStreetMap contributors under the ODbL, credited on every page. Thank you to everyone who tagged a surface, a speed limit or a café somewhere remote. It changes what we can tell a rider about a road they’ve never seen.

If a route page describes your area wrongly, every page has a “Let us know” link at the bottom, and I read them.

15:08 • 5 days ago

What 689 cycling routes look like when you measure them against OpenStreetMap

I run cyclists.com, a library of cycling routes. Every route page tries to answer what a rider wants to know before setting off: how much of it is on busy roads, whether it is paved, where the water and cafés are. Nearly all of those answers come from OpenStreetMap, so I wanted to explain how we use the data and pass back a few things we found in it.

What we measure along a route

We don

I run cyclists.com, a library of cycling routes. Every route page tries to answer what a rider wants to know before setting off: how much of it is on busy roads, whether it is paved, where the water and cafés are. Nearly all of those answers come from OpenStreetMap, so I wanted to explain how we use the data and pass back a few things we found in it.

What we measure along a route

We don’t use Overpass. A few hundred routes would be unfair load on a public instance, so everything runs against local Geofabrik extracts. For each route line we sample a point every 100 m, take the nearest way within 80 m and read its tags:

  • Road class: highway=* grouped into cycle path, quiet street, minor road, main road (primary/secondary), major road (trunk) and motorway.
  • Cycle provision: highway=cycleway, any cycleway*=* tag that isn’t no, or bicycle_road=yes.
  • “Main roads without a cycle lane”: km on primary, secondary, trunk or motorway ways with none of the above.
  • Fast roads: km where maxspeed is 80 km/h or more (mph converted).
  • Surface: surface=* first; then tracktype; then the road class (a primary road with no surface tag counts as paved, a track as unpaved). Anything else is shown as “no data” rather than guessed.
  • Services: cafés, bakeries, shops, drinking water, toilets, bike shops and railway stations within a few hundred metres of the line, placed by km along the route, plus the longest stretch with none.

Where a sample point is more than 80 m from any way, it counts as unmapped. We say so on the page instead of filling the gap.

A typical result, for a loop in the Hajar mountains (Fujairah Loop via Fayyad and Minazif): “Most of it (42.6 km) is on main roads without a cycle lane, 16.4 km where the limit is 80 km/h or more. The first 30 km has no café, shop or water.” And for the Deeside Way out of Aberdeen: “62% is on cycle paths or roads with a cycle lane. 52% is mapped as paved and 47% as gravel or unpaved.”

Elevation comes from the Copernicus DEM, not from OSM or from the GPS.

Signed cycle routes as route pages

In Scotland and Wales we turned every route=bicycle relation into route pages: 177 sections in Scotland, 68 in Wales, each with a GPX file. Long routes are cut at towns into stages, so the Border Loop is a four-day tour. Ferries stay in the line but end a stage (Oban to Corran finishes at the Corran ferry).

The lesson: don’t chain a relation’s members in order. That broke at every one-way split and dual carriageway. It worked once we read each relation as a network instead: - snap way ends to junctions within 50 m - ride around roundabouts rather than along them - prune dead-end spurs under 2 km - bridge small breaks of up to 500 m once - take the longest path through what is left

The surface split comes from the member ways’ own tags.

Relations we couldn’t read

These are the ones worth a look if you map in Scotland or Wales. I’m not saying they’re wrong: some may be deliberate, and I haven’t checked each on the ground.

Fragmented (members don’t join into a rideable line): - NCN 73 (r11361) and NCN 753 (r2293737). My guess is that the ferry crossings aren’t members, so the island and mainland sections don’t connect. - NCN 776 (r105443), NCN 83 (r1328554), NCN 1: Loch Leven to Dundee (r15978437), EuroVelo 12 in Scotland (r9476219) - Radnor Ring (r32882), NCN 47 (r8201445), Rhondda Fawr Community Route (r8281902)

No name or ref, so we couldn’t tell riders what the route is: - Scotland: r5497214, r10023468, r10023578, r10023686, r13317477, r15979588, r20395370

Generic names with no ref, e.g. “National Cycle Network National Route” (r116667), “National Cycle Network Route” (r1662719), “National Cycle Network” (r2810169), and one named just “885” (r2454549).

Two limits on our side rather than in the data. Routes that cross into England were cut off at the edge of the country extract. And a figure-of-eight route that rides one segment twice (the Gallovidian Gravel) comes out as one loop, because we don’t yet read a route that uses a way twice.

Attribution

All of this is © OpenStreetMap contributors under the ODbL, credited on every page. Thank you to everyone who tagged a surface, a speed limit or a café somewhere remote. It changes what we can tell a rider about a road they’ve never seen.

If you spot a route page that describes your area wrongly, every page has a “Let us know” link at the bottom, and I read them.

13:52 • 5 days ago

Die familienfreundliche Karte: kinderfreundlicheorte.de

Also Vater kenne ich das Problem: Wo ist die nächste Wickelmöglichkeit? Welcher Spielplatz hat eine Schaukel? Welches Café hat eine Spielecke? Darum habe ich kinderfreundlicheorte.de gebaut – eine Karte familienfreundlicher Orte, komplett basierend auf OpenStreetMap-Daten.

Stand heute:

  • Deutschland: 149.182 Orte
  • Österreich: 13.482, Schweiz: 16.096, Liechtenstei

Also Vater kenne ich das Problem: Wo ist die nächste Wickelmöglichkeit? Welcher Spielplatz hat eine Schaukel? Welches Café hat eine Spielecke? Darum habe ich kinderfreundlicheorte.de gebaut – eine Karte familienfreundlicher Orte, komplett basierend auf OpenStreetMap-Daten.

Stand heute:

  • Deutschland: 149.182 Orte
  • Österreich: 13.482, Schweiz: 16.096, Liechtenstein: 95, Luxemburg: 1.538, Südtirol: 1.208

Die Pipeline fasst Spielplatzgeräte (Schaukeln, Rutschen, Wippen) mit ihrem Spielplatz zusammen, indiziert u.a. changing_table, kids_area, highchair und Besucher können Ausstattung über „Ausstattung melden” nachtragen – geprüfte Meldungen wandern per OSM-API zurück in die Datenbank.

Meine Bitte an die Community: Wenn ihr mappt, tragt changing_table, kids_area oder Spielplatzgeräte ein, wo ihr sie seht. Ich hab selbst damit angefangen. Kleine Tags, große Wirkung für Eltern!

Hinweis: Die Seite ist derzeit nur auf Deutsch und deckt nur deutschsprachige Regionen ab (DE, AT, CH, LI, LU, Südtirol).

13:28 • 5 days ago

Tuesday, 15. September 2026

OpenStreetMap User's Diaries

Kegiatan Latihan Calisthenics bersama Muslim Calisthenics Jakarta pertama kali dalam sekali

Kegiatan saya mengikuti latihan Muslim Calisthenics Jakarta pertama kali dalam sekali :-D

Minggu, 14 Juni 2026

pada saat saya ikut kegiatan latihan Muslim Calisthenics Jakarta ke-68 pertama kali di Taman Menteng Jakarta, saya dan para peserta komunitas Muslim Calisthenics Jakarta yang baru pertama kali masuk dan ikut, saya mengikuti langkah pemanasan yang diikuti oleh coach kak I

Kegiatan saya mengikuti latihan Muslim Calisthenics Jakarta pertama kali dalam sekali :-D

Minggu, 14 Juni 2026

pada saat saya ikut kegiatan latihan Muslim Calisthenics Jakarta ke-68 pertama kali di Taman Menteng Jakarta, saya dan para peserta komunitas Muslim Calisthenics Jakarta yang baru pertama kali masuk dan ikut, saya mengikuti langkah pemanasan yang diikuti oleh coach kak Ilham Alif dan coach lainnya yang beberapa baru saya kenal muka dan namanya yang bernama kak Raihan Farhan, coach Idam dan coach Yoga, tapi sayang, mereka kakak pelatih berdua si coach Idam dan coach Yoga tidak hadir di tempat latihan tersebut karena ada urusan atau kepentingan, dan saya pun melanjutkan latihan calisthenics dengan pemanasan terlebih dahulu dan setelah pemanasan, baru latihan untuk pemula, awalnya pertama kali, kaki dan tangan saya ngerasa pegal atau kayak kram gitu pas saat latihan dan sesudah latihan dan saya melewati hal yang dari pemula ringan seperti koordinasi tubuh dengan otak dan clue-nya, latihan badan dengan push-up, pike push-up, perut, dan terlentang, setelah itu, lanjut ke tiang gantung untuk menguji seberapa pemula dan pro yang kuat pull-up berkali-kali dan pas saya disitu lah saya susah melakukan pull-up bahkan cuma sekali mau naik ke dua kali aja pun susah.

setelah saya selesai mengikuti latihan Muslim Calisthenics Jakarta ke-68 pertama kali, saya dengan lainnya pun foto bareng dan bikin video komunitas Muslim Calisthenics Jakarta dengan aba-aba "Muslim Calisthenics Jakarta" oleh anak-anak, lalu dilanjutkan dengan teriakan secara serentak "where are nothing without Allah!" dan setelah itu saya dengan sesama grup komunitas Muslim Calisthenics tersebut boleh bersantai bahkan sampai pulang pun boleh karena kegiatannya selesai pada pagi jam 10 lebih. dan saya pun meluangkan nongkrong atau ngobrol dengan sesama grup komunitas Muslim Calisthenics Jakarta dengan topik tentang lemak di tubuh yang digunakan untuk energi cadangan atau energi yang digunakan sehari-hari, pas saya mau makan mie ayam yaminlah dan beli air minum di botol dengan es kelapa di gelas, saya makan sendiri dengan lahap dan meminum es kelapa dan air putih yang ada di botol. 

setelah saya selesai makan dan minum, saya pun kembali dengan teman sesama Muslim Calisthenics Jakarta yang baru dan teman sesama Muslim Calisthenics pun juga ikut makan mie ayam tapi sayang, saya udah makan duluan sebelum saya tau kalo teman saya yang baru sesama Muslim Calisthenics pun mau ikut makan, dan sejak saat itu, saya mengobrol dengan kak Regi ngobrol tentang masalah pemetaan dan isu buta map atau tidak bisa membaca yang terjadi di era saat ini terutama masyarakat indo yang di kampung atau pedesaan sulit mengakses pendidikan terutama pendidikan seperti geografi untuk membaca peta agar tidak buta peta atau sering disebut tidak bisa membaca peta dan saya menceritakan hal isu tentang kejanggalan pengeditan peta openstreetmap oleh oknum yang tidak bertanggung jawab yang mengakibatkan komunitas openstreetmap Indonesia yang ikut terkena dampak dari oknum yang mengubah peta secara sembarangan tanpa diperhatikan data peta dan histori perubahan data peta dari foto citra satelit bumi

setelah mereka selesai makan mie ayam dan lanjut sholat dzuhur karena sudah azan dzuhur barusan, setelah itu saya ke masjid dekat pas belakang taman menteng, mengambil air wudhu dengan bareng beberapa teman komunitas Muslim Calisthenics Jakarta lalu lanjut dengan sholat dzuhur dan setelah saya dengan teman tersebut selesai sholat dzuhur, teman tersebut pulang pamit dengan saya dan saya pun akhirnya istirahat atau tidur di masjid tersebut sambil mengecas baterai ponsel saya hingga penuh karena baterai ponsel saya lowbatt :-), dan setelah selesai tidur dan pengisian daya baterai telah menyetuh ke 65%, saya akhirnya langsung pulang dengan selamat, aman, dan tenang :-)

Lokasi tempat Latihan Muslim Calisthenics Jakarta

Kegiatan Muslim Calisthenics Jakarta 14 Juni 2026

17:42 • 6 days ago

La communauté mondiale OpenStreetMap s’est réunie à Paris, nous y étions !!

Pour la première fois, fin août 2026, la France accueillait le State Of The Map Monde, la réunion annuelle de la communauté OpenStreetMap, dans les locaux de l’Ecole Géodata Paris, temple français de la géomatique. Comme plusieurs membres de Mapadour, LaNum Pays Basque était présente parmi les 535 participant⋅es venant de 45 pays.

♦

Comment résumer les plus de 180 conférences, at

Pour la première fois, fin août 2026, la France accueillait le State Of The Map Monde, la réunion annuelle de la communauté OpenStreetMap, dans les locaux de l’Ecole Géodata Paris, temple français de la géomatique. Comme plusieurs membres de Mapadour, LaNum Pays Basque était présente parmi les 535 participant⋅es venant de 45 pays.

Les membres de Mapadour présents au SOTM

Comment résumer les plus de 180 conférences, ateliers, démonstrations qui ont illustré ce qu’il est possible de faire avec les données OSM ?

Nous partageons les 5 faits qui nous ont le plus marqué pendant ces 3 jours.

1. Des acteurs industriels de la tech valorisent la communauté OSM

A une époque où plusieurs événements tech connaissent des difficultés, les SOTM sont soutenus chaque année par des entreprises comme Michelin, TomTom, esri, Thales, Capgemini démontrant l’intérêt de ces groupes.

Deux géants de la tech américaine Amazon et Fastly font des donations techniques pour permettre le téléchargement mensuel :

  • de 394 Térabytes de données ;
  • de 1,7 Pétabytes de fonds de carte ;
  • des 1,6 milliard de requêtes sur le site web mondial.

En 2020, Accenture avait valorisé la base de données OSM à plus d’1,6 milliards de dollars.

2. Des organisations intègrent OSM dans leurs stratégies

L’IGN collabore avec la communauté OSM pour créer Panoramax, intègre ses données dans son application phare cartes.gouv.fr et institue une « démarche géocommuns ».

Le SOTM a permis à des acteurs de la mobilité comme la SNCF, Ile-de-France Mobilité ou Géovélo de témoigner de leurs contribution dans OSM pour déployer des services numériques performants.

Digitaleo, qui opère une plateforme de marketing local pour gérer la présence numérique de plus de 14 000 points de vente en France, est venu expliquer que la communauté OSM connaissait mieux le territoire que ses clients et s’appuyait sur elle pour améliorer ses services.

3. L’engagement et les compétences de la communauté OSM

Cette confiance provient de la nature même de la communauté OSM. En France, elle a fait l’objet de deux études à 8 ans d’intervalle (2016 et 2024). Retenons qu’elle est composée à 81% d’hommes, en majorité très diplômés (76% bac+3 et plus) en informatique et en géomatique.

Photo de groupe prise lors du SotM 2026 à Paris - © SotM Paris

Déformation professionnelle sans doute, les contributeur⋅rices sont très précis⋅es et très engagé⋅es dans la qualité de leurs contributions, ils/elles prennent un soin important à le faire. Les discussions que nous avons eu avec les différent⋅es participant⋅es confirment cette impression.

4. Le modèle de gouvernance d’OSM garantit la souveraineté des données

Sébastien Soriano, directeur de l’IGN est intervenu pour défendre une vision de la souveraineté numérique basée sur la collaboration. Si un acteur public souhaite être souverain, il a deux choix possibles : soit tout contrôler, soit faire en sorte que personne ne contrôle tout.

C’est ce modèle de gouvernance distribuée qu’il a plébiscitée et elle prend tout son sens à l’heure où le président Trump décide de débaptiser le lac Ontario en lac d’Amérique. Google suit dans la foulée tandis que la communauté OSM débat librement et cherche un consensus entre contributeur⋅rices.

5. Les IA submergent les services d’OSM

Grant Slater, Senior Site Reliability Engineer (SRE) de la Fondation OpenStreetMap, a réalisé une présentation très éclairante sur les dégâts réalisés par les sociétés éditrices de solutions d’IA pour les services ouverts et partageurs comme OSM.

Les robots d’indexation de ces sociétés collectent massivement les contenus OSM (site web, le wiki, les listes de diffusion) car ils sont gratuits et de qualité. Ils le font d’une manière particulièrement violente et de façon anonyme pour ne pas être filtrés. La Fondation Wikimédia en est aussi victime.

Concrètement, il en résulte une augmentation du trafic et une consommation énorme et continue sur les serveurs de la Fondation qui ne peuvent plus suivre la cadence et dégradent ses services. De plus, les IA favorisent la création de faux comptes OSM (400 par jours) pour augmenter artificiellement la visibilité de pages web commerciales ou produire du spam.

Pour aller plus loin

De très nombreux autres sujets ont été abordés pendant ces 3 jours, la plupart des interventions ont été filmées et diffusées sur la chaine Peertube d’OSM France. Bien qu’en langue anglaise, elles sont toute de même accessible grâce à l’option sous-titres traduits en français.

D’autres contributeur⋅rices ont produit des comptes-rendus qui ont été répertoriés sur la page wiki du State of the Maps 2026

12:15 • 6 days ago

Monday, 14. September 2026

Sunday, 13. September 2026

OpenStreetMap Blog

What’s in a name? Naming things in OpenStreetMap

Whether you are from, Saint-Louis-du-Ha! Ha!, Springfield or Ea names are important. They help us identify where we are, where we are from and where we want to go to. Almost everything has a name and OpenStreetMap volunteers have mapped 115 million names. Local name of features on www.openstreetmap.org In OpenStreetMap, the verbal identifier with which […]
a Road Sign, Pointing to the right is HAM (1/2) and below than SANDWICH (3) To the left is Finglesham (1/2) and DEAL (4)
Ham Sandwich sign by Oast House Archive. © Copyright Oast House Archive and licensed for reuse under CC BY-SA 2.0.

Whether you are from, Saint-Louis-du-Ha! Ha!, Springfield or Ea names are important. They help us identify where we are, where we are from and where we want to go to.

Almost everything has a name and OpenStreetMap volunteers have mapped 115 million names.

Local name of features on www.openstreetmap.org

In OpenStreetMap, the verbal identifier with which people refer to something is documented by the name= tag. This usually is the most common name in the local language and is the most obvious name of the feature. For example, if you are in France and map a road called “Rue des Beaux-Arts”, you add name=Rue des Beaux-Arts so that everyone knows what that road is called.

There are many map styles based on OpenStreetMap data. On www.openstreetmap.org, we display “osm-carto” style by default, with a layer switcher for many others.

There are a few simple rules that the OpenStreetMap community follows, including:

  • name= is typically the commonly used name in the local language. A street in Paris has as name= its French name, not the name in English.
  • name= should be verifiable.
  • name= should be a proper name – not a description or a reference id.

The recording of names is a complex issue, but these are the main rules we use.

The OpenStreetMap community tries to ensure that the name= tags in the OpenStreetMap database are correct, for mapped features with names such as shops, places, streets, lakes or even oceans.

Additional names of features on www.openstreetmap.org

In addition to the local name, set by name=, objects in OpenStreetMap very often have one or more names. Such additional names are classified by their function – how they are used in contrast to the local name, or what purpose they serve for data users. We can store old names, local names, official names, and alternative names.

Both local and other name keys can also be suffixed with a language code. If you want to add a name in another language, you use a separate tag like name:en= for English or name:fr= for French, and leave the name= tag in the local language. The ISO language code system we use allows more details, such as the writing system used, or even the region and dialect. The English spoke in Britain isn’t the same as that spoken in Australia.

Therefore, the OpenStreetMap database contains features with multiple names.

On the default layer of the www.openstreetmap.org website (osm-carto) we don’t show different names based on where you are, this means everyone will see the name of the feature in the local language. It’s important that the website has a layer where this is the case. This is mostly a technical reason.

While only name= is displayed on the default layer of www.openstreetmap.org, there are additional layers on the website and there is ongoing work on the new Vector layer to show names in your local language, but more about that in a later post. There are other map styles showing names only in German, or only in English.

One database – unlimited maps: create the map you want

It is important to note that OpenStreetMap data is offered to everyone for free, under the ODbL licence, and used for any purpose – including commercial usage.

It is possible to produce your own maps which, for example, show only a subset of the mapped names or features. The www.openstreetmap.org website’s main purpose is to facilitate OpenStreetMap mappers and not to be a single map for every use. OpenStreetMap data is used by individuals, big companies, game companies, grassroot organisations, governmental agencies, humanitarian groups and many others and the data can be used to create unlimited maps and for other purposes.

What about official names?

Mostly the official name will match the commonly used name of a feature. Sometimes people will continue to use the original name, so our name tag will stay. We can store the official names of mapped features when different, in the official_name= tag

In cases like the executive order related to Lake Ontario, it’s not unusual that there will be a community discussion and in this case the tag official_name:en-US=Lake America has been added to the lake on OpenStreetMap, to record the new official en-US name. The primary name of the lake remains the same. Since a lot of people still use the name “Lake Ontario” we keep it as name. The addition of the official_name:en-US=Lake America name means that anyone searching for Lake America on www.openstreetmap.org and apps/services using OpenStreetMap data which have all the feature names, will find Lake Ontario.

The Name of the Game

OpenStreetMap’s flexible data model means that if you want to show a map, with certain names, or certain langauges, we provide a world-wide freely-usable database for you to use. Just adjust your map style to prefer one name tag over another, and you’ll automatically get the map you want.

OpenStreetMap’s community base, and non-commerical freedom, international project structure, and “on the ground rule” means that if you use the name tag, then the names on the map will be based on what people are actually using.

When it comes to maps, OpenStreetMap is the only name in town!

19:52 • 8 days ago

OpenStreetMap User's Diaries

Planning a geo nerd trip

Today I ran across an article about Vienna’s Globe Museum.

That reminded me I’ve never been to Vienna before. Now I definitely need to go: Looking at old maps is an aesthetic experience, and it’s a great way to see how politics, wars and peace have passed.

And when I go, I might as well extend the trip in a south-east direction and visit another city where I haven’t been before:

Today I ran across an article about Vienna’s Globe Museum.

That reminded me I’ve never been to Vienna before. Now I definitely need to go: Looking at old maps is an aesthetic experience, and it’s a great way to see how politics, wars and peace have passed.

And when I go, I might as well extend the trip in a south-east direction and visit another city where I haven’t been before: Bucharest in Romania, because they have a museum of old maps.

What do you think – are there other places I should put on my bucket list of destinations which are interesting for folks interested in maps and mapping?

12:05 • 8 days ago

weeklyOSM

weeklyOSM 842

03/09/2026-09/09/2026 [1] ediyes, who has not only been an active member of the Spanish weeklyOSM team for years, but is also a successful mapper | © HOT Macro Mapaton Regional | Mapping Voting has started on the lgbtq=* proposal and is open until and including 19 September. Mapping campaigns In a talk at State of…

Continue reading →

03/09/2026-09/09/2026

lead picture

[1] ediyes, who has not only been an active member of the Spanish weeklyOSM team for years, but is also a successful mapper | © HOT Macro Mapaton Regional |

Mapping

  • Voting has started on the lgbtq=* proposal and is open until and including 19 September.

Mapping campaigns

  • In a talk at State of the Map 2026, Enock Seth Nyamador explained how massive mapathon campaigns carried out by paid mappers affiliated with large companies or organisations could potentially ‘kill’ the OpenStreetMap movement in Ghana.

Community

  • [1] The editors at weeklyOSM don’t just collect and write articles to keep you as well informed as possible about the OSM universe; they also map , some with such great success. We would like to offer our warmest congratulations to @ediyes, from our Spanish team, on this achievement! With her Peruvian team , Edith came second , behind the Guatemalan team .
  • rphyrin explained the situation around Jakarta following the recent Anak Krakatau eruption, while showing how OpenStreetMap data is being used in an early warning system to alert people about the areas expected to be affected by volcanic ash. Anak Krakatau, meaning ‘child of Krakatau’, is an active volcano in the Sunda Strait between Java and Sumatra that emerged from the caldera left by the catastrophic 1883 Krakatau eruption, which killed an estimated 35,000 people.

Local chapter news

  • Katja Haferkorn reported ► that the FOSSGIS e.V. networking meeting took place on 2 September, with 25 participants joining the online networking platform. The next networking meeting will be held on 9 December 2026.

Events

  • Are you a Stadia Maps customer? They just announced that they’re sponsoring local meet-ups to align with their core values of providing fair, transparent treatment for developers.
  • Christoph Hormann shared a general commentary on the State of the Map 2026 conference in Paris, which he had recently attended.
  • State of the Map Asia 2026 was held in Osaka, Japan, on 6 and 7 September.

OSM research

  • Maurizio Napolitano wrote ► about ‘Stress in bici’, an experimental map based on OpenStreetMap that shows bicycle routes in Italy, colour-coded according to stress level. The development of the platform is also described in a research paper, ‘TS-BikePlan: A Data-Driven Tool for Enhancing Cycling Infrastructure and Safety’, published in the Journal of Urban Technology .
  • Giuliano Cornacchia et al. have studied the recommended routes given by software navigation services and found out that as adoption increases, route diversity declines. Further, traffic and emissions converge onto fewer roads leading to lesser benefits (which eventually turn negative over a certain threshold) in terms of CO₂ emissions and traffic load. For the purposes of this study, the road networks were sourced from OpenStreetMap.
  • The OSM Road Monitor team presented their work at SotM 2026 in Paris. By combining community-driven mapping with independent Earth observation data, the project aims to support more reliable and timely road information.

Maps

  • Continuing the discussion around the recent UN shift from the Mercator to the Equal Earth projection, the OpenStreetMap community on Reddit has started discussing whether OSM should make the switch as well. Meanwhile, back in 2025, also prompted by a discussion about OSM map projections, Andy Townsend had already shown us that anyone can render OSM data in whatever projection they want.
  • Mathias has published a map, ‘Polizeikarte’ , which brings together public press releases from German police authorities. It shows around 63,600 incidents from 260 locations across 14 federal states. Geocoding is handled by Nominatim, whilst the visualisation is provided by MapLibre GL JS using tiles from OpenFreeMap. Official reference layers can be overlaid, such as the accident atlas from the statistical offices, which contains 585,815 accidents from 2018 to 2025. The project is non-commercial and is not affiliated with any public authority.

Open Data

  • Iconem has recently updated terrain-viewer, an app made to ingest, style, and render open-data terrain-sources for relief visualisation, feature detection, and mapping! They’re using it to detect archaeological sites, and there is some overlap with mapping landmarks within OSM from terrain sources, whether public worldwide like Mapterhorn, or national, since the tool can ingest custom national mapping agencies data sources.

Software

  • Stadia Maps explained the distinction between forward geocoding and reverse geocoding and how choosing the right endpoint and parameters can make a big difference for any application.
  • Strongly motivated by the urge to avoid getting a speeding ticket, Moonshot Studios GmbH have developed YouSpeed, a mobile intelligent speed-assistance app powered by OpenStreetMap speed-limit tags, area context, and daily diffs. Other apps of Moonshot Studios include Woladen (where to charge your electric car) and Tankzeit (best time to fuel up your car).
  • rphyrin has made ‘ivebeen_here’, a platform for OSM users to share their personal stories about particular places.

Programming

  • Agasta08 published the full report for their 2026 Google Summer of Code project, ‘Category Support in Nominatim’, thanking mentors Sarah Hoffmann and Marc Tobias, as well as OpenCage for sponsoring the development server used for the planet-scale database setup. Agasta explained how the category model has been implemented in Nominatim.
  • Inspired by a discussion at the recent State of the Map, rphyrin tried out ‘Photon‘, an open-source geocoder built for OpenStreetMap data, and built a custom front end that allows users to copy the coordinates of search results.

Releases

  • OsmAnd released version 5.4 for iOS with a redesigned My Places interface, a rebuilt Plan a Route tool, and a new Astronomy plugin. The Android release came with a refreshed Search UI, the ability to attach media to Favorites, and 3D Buildings with roof shapes.
  • Altilunium LocationPad v26.9.5 has been released – a web app for marking, labeling, and revisiting places on an OpenStreetMap-based map.
  • Sourtest v26.9.6 has been released.
  • The August 2026 release of Organic Maps has been released, introducing several new features, including multi-selection for bookmarks and tracks, a CarPlay dashboard, the ability to hide tracks on the map, and more readable share links.

Did you know that …

  • … the recent ChatGPT update can now show OpenStreetMap-based map data based on your chat query, complete with proper OpenStreetMap attribution?

OSM in the media

  • Brian Bergstrom has launched Dulcet GIS, a podcast about cartography and civic mapping. The first episode covers the UN General Assembly’s adoption of the Equal Earth projection and sets it alongside the executive order renaming Lake Ontario, noting that OpenStreetMap was the only major map that did not change the name. The episode explained the on the ground rule and how disputed names are handled in the data model, and closed by pointing listeners to OSM-based apps and to the Humanitarian OpenStreetMap Team.
  • The latest event of the Ingolstadt Citizens’ Network was held ► on Sunday 6 September, focusing on the theme ‘Navigation using OpenStreetMap data’. The event demonstrated how OpenStreetMap can be used in everyday life, which apps are based on it, and how people can contribute to improving the maps themselves. The event was free and open to everyone, with no prior knowledge required.

Other “geo” things

  • The United Nations General Assembly has voted by an overwhelming majority in favour of adopting a world map based on the 2018 Equal Earth projection, which more accurately reflects the actual size of countries and continents, moving away from the Mercator projection. In New York, 164 states voted in favour of the resolution, which was sponsored by Togo and backed by the African Union. The United States was the only country to vote against ► it, describing the initiative as an ‘ideological agenda’. Six countries abstained.
  • Scientists, led by space physicist Endawoke Yizengaw of The Aerospace Corporation in the US, have discovered that the solar flares of 11 November 2025 caused widespread, coast-to-coast disturbances in the atmosphere across the continental US. The disturbances could potentially throw GNSS positioning off by more than 10 metres in some places, the researchers say, significant enough to disrupt precision agriculture and autonomous vehicles.
  • After announcing that Lake Ontario would continue to be called that on their maps, the MapQuest app went to number one for navigation on the iOS App Store in the US.
  • Maggie Downs, of the BBC, visited Vienna’s Globe Museum, the only public museum in the world dedicated entirely to globes.
  • Oliver Bünte, of Heise, reported that the US Department of Defense’s Defense Innovation Unit has tested a quantum sensor-based flight navigation system over the Pacific that allows an aircraft’s position to be determined precisely without relying on GNSS. Instead of relying on signals from navigation satellites, the system detects changes in the Earth’s natural magnetic field and creates a magnetic field map from these measurements. Based on this map, the system can determine an aircraft’s position entirely independently of GNSS signals, weather, and visibility conditions.

Upcoming Events

Country Where Venue What When
🇩🇰 København Cafe Bevar’s OSMmapperCPH 2026-09-13
🇬🇧 Greater London 1 Cabot Square, 7th Floor, Canary Wharf E14 4QJ EAW Volunteering Event 2026-09-14
CartONG : Mapathons en ligne 2026-2027 2026-09-14
🇪🇸 Madrid Online Mappy Hour OSM España 2026-09-15
Missing Maps London Mid-Month for Advanced Mappers (no training provided) (Online) [eng] 2026-09-15
🇺🇸 San Francisco Near BART 24th St. Mission station Bay Area WikiSalon 2026-09-15
🇫🇷 Lyon Tubà Réunion du groupe local de Lyon 2026-09-15
🇩🇪 Bonn Dotty’s 204. OSM-Stammtisch Bonn 2026-09-15
🇩🇪 Chemnitz Kaffeesatz, Chemnitz OSM-Stammtisch Chemnitz 2026-09-15
🇦🇹 Stainach-Pürgg Online 22. Österreichischer OSM-Stammtisch (online) 2026-09-15
🇺🇸 San Jose Online South Bay Map Night 2026-09-15
🇩🇪 Online Lüneburger Mappertreffen (online) 2026-09-15
🇨🇭 St. Gallen Rosenbergstrasse 59, 9000 St.Gallen Map The Climate! Ein Mapathon 2026-09-16
🇫🇷 MJC de vienne Réunion du groupe local de Vienne 2026-09-16
🇩🇪 Köln Lokal K, Hackländer Straße 2, Köln-Ehrenfeld OSM Stammtisch Köln 2026-09-16
🇫🇷 Nantes COntrib’atelier 2026-09-16
🇺🇸 San Francisco Et al. A Synesthete’s Atlas: Cartographic Improvisations Between Eric Theise, Gusty Winds May Exist, Ron Heglin, and Petra Zélie 2026-09-16
🇩🇪 Karlsruhe Schwarzer Kater Stammtisch Karlsruhe 2026-09-16
🇩🇪 Kiel Kieler Innovations- und Technologiezentrum OSM auf der Kielux 2026 2026-09-18 – 2026-09-19
OSMF Engineering Working Group meeting 2026-09-18
🇮🇹 Catania Centro Atena, via Fimia 34, 95128 Catania (CT) Modifichiamo Wiki e OSM insieme! – Catania 2026-09-18
🇮🇳 Mumbai Lokhandwala Garden, Andheri OSM Mumbai Mapping Party No.14 (Andheri) 2026-09-19
🇮🇳 Delhi Too Mikkii Tapas, South Extension OSM Delhi Mapping Party No.31 (South Extension) 2026-09-20
🇪🇸 Madrid Online Mappy Hour OSM España 2026-09-22
🇬🇧 Derby The Brunswick, Railway Terrace, Derby East Midlands pub meet-up 2026-09-22
🇩🇪 Berlin Online OSM-Verkehrswende #79 2026-09-22
🇮🇹 Catania Piazza Roma, Catania (Punto di incontro) Mappiamo le piste ciclabili – Catania 2026-09-22
🇫🇷 Nantes Le Wagon Nantes OpenStreetMap, la carte à la carte ! 2026-09-23
🇩🇪 Hannover Kuriosum Stammtisch 2026-09-23
🇩🇪 Würzburg FabLab Würzburg Würzburger OSM-Treffen 2026-09-23
🇬🇧 City of Westminster Blue Posts pub London pub meet-up 2026-09-23
Pravidelný Missing Maps CZ-SK online Mapathon 2026-09-24
🇧🇷 100% online 🇧🇷 Lançamento de livros sobre mapeamento colaborativo 2026-09-24
🇩🇪 Freiburg im Breisgau CCCFR, Adlerstr. 12 a, Freiburg/Br. OSM-Treffen Freiburg/Br. 2026-09-24
🇮🇳 Bengaluru NIMHANS Convention Center OSM India @ IndiaFOSS 2026 2026-09-25 – 2026-09-27
UN Mappers Mappy Hour 2026-09-25
🇲🇽 Torreón Universidad Tecnológica de Torreón Conferencia “OpenStreetMap: Datos abiertos y más” 2026-09-25
🇲🇽 Torreón Universidad Tecnológica de Torreón Taller “Mapeando mi entorno” 2026-09-25
🇩🇪 Düsseldorf Online bei https://meet.jit.si/OSM-DUS-2026 Düsseldorfer OpenStreetMap-Treffen (online) 2026-09-25
🇩🇪 Karlsruhe Geofabrik, Amalienstraße 44, 76133 Karlsruhe Karlsruhe Hack Weekend September 2026 2026-09-26 – 2026-09-27
🇫🇷 Nantes Le Wagon Nantes OpenStreetMap, la balade de la data 2026-09-26
Sudan Solidarity Series 2026-09-26
🇸🇪 Uppsala Datorföreningen Update Mapping meetup in Uppsala 2026-09-27
CartONG : Mapathons en ligne 2026-2027 2026-09-28

Note:
If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by MarcoR, MatthiasMatthias, Rob Yoegel, Strubbl, Andrew Davidson, barefootstache, derFred, tkk.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

11:24 • 8 days ago

Friday, 11. September 2026

OpenStreetMap User's Diaries

Перше виконане завдання EDR

Силка на наш телеграм канал t.me/Enduro_Travel_Help

Тиждень тому засновник EDR поставив ціль: привести в порядок околиці с. Бехи (20+ км), а також розпочати кампанію з повного позначення всього в межах 50 км від Коростеня. Мета кампанії — розвиток ендуро в Коростені. Карти OSM станом на 2025 рік приблизно на 25–30% неправильні в Коростенському районі в плані туристичних доріг (путівців т

Силка на наш телеграм канал t.me/Enduro_Travel_Help

Тиждень тому засновник EDR поставив ціль: привести в порядок околиці с. Бехи (20+ км), а також розпочати кампанію з повного позначення всього в межах 50 км від Коростеня. Мета кампанії — розвиток ендуро в Коростені. Карти OSM станом на 2025 рік приблизно на 25–30% неправильні в Коростенському районі в плані туристичних доріг (путівців тощо).За понад тиждень наша команда провела роботу майже над усіма точками даних OSM в радіусі 25 км від с. Бехи. Робота виконувалася в таких локаціях:С. Бехи та околиці (5+ км): додано річку Октасувака, а також додано й відредаговано путівці.С. Вороневе та околиці: додано житлову зону, кладовище, путівці, а також болота, ставки та лісові масиви.С. Немирівка: робота ще триває, але вже додано новозбудовану дорогу, а також видалено й відредаговано наявні путівці та дороги.Робота над двома дачними масивами: збільшено об’єм (русло) річки Уж на карті, додано кросову трасу. С. Васьковичі: також додали річку. Компанія з розвитку околиць с. Бехи триває. У планах до початку зими — повністю довести до ладу 50+ км околиць міста Коростень.

20:06 • 10 days ago

OSM Edit MCP: reviewing local GPX surveys before road edits

I maintain OSM Edit MCP, an MIT-licensed Python tool that connects an MCP-compatible AI assistant to an OpenStreetMap survey-review workflow. It is alpha software, and I would welcome feedback from mappers on its review steps and failure cases.

The workflow is: local GPX → selected segment → current/proposed geometry preview → explicit confirmation → changeset. The mapper chooses the sur

I maintain OSM Edit MCP, an MIT-licensed Python tool that connects an MCP-compatible AI assistant to an OpenStreetMap survey-review workflow. It is alpha software, and I would welcome feedback from mappers on its review steps and failure cases.

The workflow is: local GPX → selected segment → current/proposed geometry preview → explicit confirmation → changeset. The mapper chooses the surveyed section and the target road; the tool does not select a road or infer junctions automatically.

For production writes, the normal profile requires a separate confirmation in the MCP client bound to the exact proposal digest. It rechecks the OSM account and object versions before an atomic upload. These checks do not establish that a proposed edit is correct: GPS accuracy, topology, tagging, permitted sources and local knowledge still need human review. This is not a bulk-import or autonomous mapping tool.

Version 0.2.1 is available with uvx osm-edit-mcp. The README includes client configuration. Starting the server, analyzing a local GPX and previewing a selected segment need no OAuth. Preparing an account-bound road-edit proposal does require authentication, even before an upload. Start with read-only inspection and the separate OSM development API.

The server does not upload the GPX as an OSM trace. The newer nearby-discovery profile documented in the repository is still unreleased.

I am particularly interested in which topology warnings and before/after views you would need before trusting a proposal. OSM community, import and automated-edit policies still apply; per-edit confirmation is not a substitute for community consultation.

13:45 • 10 days ago