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.

… See full entry

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.

… See full entry

This is mostly a test post to see how the blog feature works. If you are reading this, hello.

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 - Trolling around finding new cycleways on the roads (the city seems to have added a lot of sharrows since the last time someone did this)

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.

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.

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

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…

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

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

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.

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.

Impetus

Many routers, such as OSRM,¹ 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.

This quickly adds up to excess penalty for the simple router.² 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.

… See full entry

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.

… See full entry

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

… See full entry

---

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

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

Minggu, 14 Juni 2026

… See full entry

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

… See full entry

https://gis.epa.ie/EPAMaps/

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?

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

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

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.