Style | StandardCards

OpenStreetMap Blogs

Friday, 21. August 2026

OpenStreetMap Blog

Thanking Proton, our newest Platinum sponsor

OpenStreetMap Foundation is pleased and proud to announce that Proton AG has been recognised as a Platinum Corporate Member, following two donations over the past two years totalling around €70,000. Proton came to us with unsolicited donations both times. They believe in our project, the Foundation, but most importantly, our community. To quote them directly, […]

OpenStreetMap Foundation is pleased and proud to announce that Proton AG has been recognised as a Platinum Corporate Member, following two donations over the past two years totalling around €70,000.

Proton came to us with unsolicited donations both times. They believe in our project, the Foundation, but most importantly, our community. To quote them directly, “We truly value the partnership with OpenStreetMap”.

These donations, however, were not accidental. The values of the two organisations do align very well on privacy. OSMF values and recognises the privacy of our contributors. More than 10 years ago, we adjusted our consitution to allow community members to become a part of the OSMF, to vote for the board of directors, to financially support the Foundation, without requiring them to give up personally identifying information like a name or address. We recognise there are many good reasons why someone wouldn’t want everything to be recorded. Proton is in the business of offering privacy-respecting emails, VPNs, storage tools, video conferencing and office tools that don’t share your data with anybody, not even Proton themselves. The alignment between us isn’t something either of us had to explain to the other. Maybe they can offer privacy respecting maps too!

OpenStreetMap runs the largest open geographic dataset in the world, built by volunteers and used by humanitarian responders and some of the largest technology companies on the planet. OSM is free to use but running OSM costs money to pay for the servers, infrastructure, and the people who keep it working. Most of that money comes from corporate members who support the project and who subscribe to several sponsorship tiers. Proton gave us unconditional money and didn’t ask for anything in return. We really wanted to acknowledge the gift so, noting that their donations put them over our Platinum tier, our highest level of corporate membership, we have awarded them Platinum status in recognition of their awesome support.

Thank you, Proton.

Thursday, 20. August 2026

OpenStreetMap User's Diaries

GSoC 2026 Final Report: Routing through pedestrian areas in Valhalla

GSoC 2026 with OpenStreetMap Routing through pedestrian areas in Valhalla

During this Google Summer of Code, I’ve solved a very common problem that pedestrian routers have by adding the feature to route through open pedestrian areas, such as squares, plazas, pedestrian zones… instead of routing around the perimeter.

It’s now merged and running on the full planet build. Where pedestria

GSoC 2026 with OpenStreetMap


Routing through pedestrian areas in Valhalla

During this Google Summer of Code, I’ve solved a very common problem that pedestrian routers have by adding the feature to route through open pedestrian areas, such as squares, plazas, pedestrian zones… instead of routing around the perimeter.

It’s now merged and running on the full planet build. Where pedestrians used to be sent all the way around the perimeter, Valhalla now creates a path straight across it.

Before :

Now:

See the Square Plaza de Santo Domingo, Murcia

You can try a demo of the feature on openstreetmap.org: Here


Table of contents


About the project

What is Valhalla

Valhalla is an open-source routing engine that calculates directions using OpenStreetMap data for driving, cycling, walking, and more.

It works by turning raw OSM data into routing graphs that generate routes for different means of transport.

The problem

In OpenStreetMap, open pedestrian areas are often mapped as polygons with the tags highway=pedestrian + area=yes. Valhalla treated these polygons as obstacles because these areas don’t have explicit sidewalks to route through, so it might have routed around the perimeter but never across them.

This led to some cases with extremely long and nonsensical routes. This is a long-standing pain point in pedestrian navigation, even for the big companies.

See one clear example of the problem:

The goal

The goal of my project was to make Valhalla able to cross these open areas. The scope I agreed on with both my mentors was to cover the large majority of areas in the world, in a robust and mergeable way.


How it works

The core idea: the medial axis

We had to choose an algorithm that could solve this problem as efficiently as possible, because there are some known algorithms that might seem like excellent options but are extremely inefficient. After doing extensive research (more detailed comparation in my past diary entry) we selected the medial axis approach.

This is how the skeleton of a medial axis looks on a complex square:

The pipeline

1. Recovering the area geometry

The whole process is integrated into Valhalla mjolnir, the tile builder.

First of all, areas mapped as relations have member ways with no routable tags, so the normal parsing process discarded them. Moreover, areas mapped as ways were also discarded. So naturally the first step was to start parsing them.

This was resolved in two different ways, for the tags discarded at the beginning of the pipeline I had to make some changes to start keeping these areas in the files, see my Pull Request [GSoC] Pedestrian area routing: Detect areas during parsing.

For the member ways, it’s a more complicated case, because Valhalla’s pipeline order makes it impossible for us to collect these member ways before parsing the relations, so we came up with a new stage to recover these ways and preserve their geometry alive. This stage (ParseAreaWays) can be seen in my Pull Request [GSoC] Pedestrian area routing: Build area polygons and generate medial axis.

2. Building the traversal

Next, there is also a new stage (BuildAreas), where for each area, it assembles the polygon (including holes), densifies it, and computes a Voronoi diagram of the points to approximate the medial axis, prunes the branches reaching toward the corners, connects each entrance to the nearest skeleton vertex it can reach and materialises the result as synthetic footways.

These synthetic footways are built as normal footways so they can be processed through the rest of the pipeline just like any other footway. If you are interested in a long explanation of the algorithm you can look for my diary entry: [GSoC] Prototyping medial axis implementation for area routing

And for the explained code see: [GSoC] Pedestrian area routing: Build area polygons and generate medial axis.

3. Synthetic OSM IDS

The generated ways and nodes, as I mentioned before, are treated as “normal” ways and nodes, so they need synthetic OSM IDS. They get ids above the highest real OSM way and node ids, so they never collide with real data, and from there the rest of the pipeline treats them like any other footway.

And for the explained code see: [GSoC] Pedestrian area routing: Build area polygons and generate medial axis.

Design decisions

During the course of the project we had to do some serious thinking about some complex obstacles that I’ll explain further in this document. In addition, there are some other design decisions we made, to keep this feature robust:

  • Areas below a size threshold keep their perimeter instead of having a generated traversal
  • Areas that already have paths mapped inside are left untouched
  • Nearby entrances that can “see” each other are merged
  • The densification tolerance was tuned as a trade-off between speed and detail.

Results

Current state

We achieved having it merged and running on the full-planet build. It covers most of the pedestrian areas in the world and sits behind the mjolnir.pedestrian_areas config option, so it doesn’t affect anyone who doesn’t enable it.

Full-planet build statistics

These are real numbers from a full planet build, not estimates:

Metric Value
Pedestrian areas processed 127,612
Virtual (synthetic) edges generated 915,742
Area parsing time ~2 min
Area building time ~9 min
Tile size impact negligible

This is one of the things I’m most proud of, we achieved to have a first functional version with considerably good performance across the whole world, with a more than expected great result.

Performance journey

The first version took about 114 seconds to process Germany’s areas. Profiling with samply showed that the Voronoi computation was dominating everything else, so I focused on that part, preparing the polygon geometry once, collecting the lookup data in two passes, and feeding the Voronoi fewer points. That brought Germany’s processing time down to about 19 seconds, a ~83% reduction.

See it in action

The feature is now live on the public server, so you can try it yourself right now with no setup needed.

Valhalla powers one of the pedestrian routing engines available directly on openstreetmap.org, and it’s also on the Valhalla demo.

On either one, pick the pedestrian (foot) profile, drop a start and an end point on opposite sides of any square or plaza, and you’ll see the route go straight across the open area instead of tracing the edges of the area. It works anywhere in the world where the area is mapped in OpenStreetMap.

If you test it and find a bug, please take a minute to report it on Valhalla’s github: Valhalla Issues


The code

All the work is linked below.

Pull requests

  • Main PR - pedestrian area traversal generation: #6195 the core of the project.
  • Groundwork PR - optional area handling, and first parsing steps: #6127
  • Documentation PR: #6266
  • Future work / limitations documentation PR: #6279

Documentation

Commit history

  • Last GSoC commit: 5b4d423 anything after this is post-GSoC work.

Challenges and what I learned

The hardest part of this project wasn’t writting the code, it was figuring out what to build. For weeks, before any real implementation, the work was research, prototyping and case studies, because the naive approaches don’t survive contact with real OpenStreetMap data.

  • Choosing an algorithm: My first thought was a Visibility Graph. A Visibility Graph connects each pair of vertex of the polygon that “see” each other in a straight line. But after a case study in QGIS over 10 different real squares comparing approaches, the result was pretty interesting, the Visibility Graph generated too many edges and the routes we believed weren’t very friendly. More of this discussion in the case study mentioned above.

  • Generating the skeleton: Generating the medial axis wasn’t calling a simple function. It was a whole pipeline, that led us to a lot of disorganized segments. Converting them into usable chains was a whole graph problem. Each step of the code was thought and designed.

  • Fitting it into the pipeline: Maybe the biggest design challenge. Areas are detected while parsing the ways, but to build their geometry you need the node coordinates, which are not parsed until later. And the generated crossings need to be turned into edges, which happens even later. So an entirely new phase had to be designed and placed between ParseNodes and ConstructEdges

  • Memory, and making it scale: Throughout the whole process, one of the biggest challenges was constantly thinking about how to make the solution scalable. It was not just about making it work for a small number of areas, but making sure the design would still work efficiently when applied to the entire pedestrian network of a continent. This meant being mindful of memory usage from the beginning, while also continuously looking for ways to improve performance as the implementation evolved

  • Getting into a large codebase: One of the first challenges was getting familiar with a codebase as large as Valhalla. Before implementing anything, I had to understand how the different components interacted and how data flowed through the pipeline. A big part of the process was reading existing code and identifying patterns I could reuse, rather than introducing completely new approaches.


Limitations and future work

This is a first functional version. The known limitations are documented as TODOs in the code and in the docs, each with a plan for how it could be addressed.

Limitations

  • Perimeter footways aren’t detected as mapped paths. A pedestrian way that runs exactly along an area’s boundary, or crosses it in a straight line with only two nodes, isn’t recognised as one, since it has no node strictly inside the polygon, so a traversal may be generated over it.

  • Traversals generated from relations are unnamed. The name of an area mapped as a relation lives on the relation, not on its member ways. Since the name is currently taken from a member way, relation areas either inherit a member’s name or end up unnamed.

  • Generated edges use generic attributes. Both traversal ways and re-emitted entrance nodes get a fixed set of pedestrian attributes rather than inheriting the area’s own tags.

  • Only small areas get their perimeter back. When no traversal is generated, the perimeter is only restored for areas skipped for being too small. Areas skipped for other reasons, such as having no entrances, or having paths already mapped inside, are dropped entirely, even though some of them might still want a routable perimeter.

Future work

Each of the limitations above is a natural follow-up. This section outlines how each could be approached, as a starting point for future contributors.

  • Detecting perimeter footways. The current detection relies on finding a node strictly inside the polygon, which misses ways that only touch the boundary. Adding a geometric check on the segments between consecutive perimeter hits, testing whether they run along the boundary or cross the interior, would flag these ways without depending on an interior node.

  • Naming relation-based traversals. The relation name is available at parse time but isn’t carried forward. Storing it alongside the area relation data, and reading it when the traversal is generated, would let areas mapped as relations take the square’s name instead of a member way’s.

  • Inheriting the area’s attributes. Rather than building traversal ways and entrance nodes from scratch, the attributes could be looked up from the source area and the original nodes and merged. The attributes are already on the source ways at that point, so carrying them through is mostly a matter of routing them through to where the synthetic ways are created.

  • Restoring the perimeter more broadly. This one is more open and would need some investigation first: working out in which cases restoring the perimeter is actually desirable (small areas already do it, but areas skipped for other reasons, like having mapped paths inside, might benefit too), how to detect those cases, and then deciding per skipped area whether to give the perimeter back rather than only triggering on the size check.

  • Turn-by-turn instructions for crossings. Since crossings are ordinary footway edges, they produce a sequence of small maneuvers. Tagging the traversal edges with a dedicated flag, or grouping them in the maneuver generation step, would let the router emit a single “cross the square” instruction.

Beyond those, there are a few internal refinements marked in the source or raised during review:

  • Entrance distance tolerance. The tolerance for matching an entrance to its polygon is currently 0.1. This distance should ideally be zero, it would be worth investigating whether it can be tightened to an epsilon, or reworked so an exact value isn’t needed at all.

  • RAII for GEOS pointers. The GEOS geometries are currently created and destroyed by hand. Wrapping them in a RAII type, as done elsewhere in the codebase, would make the cleanup automatic and safer.

  • Unifying the chain-walking logic. The walk used for pruning the branches and the one used for stitching chains are nearly identical, and could be unified.

  • Separating area ways into their own file. Area member ways are currently emitted into the same file as completely processed ways but in an intentionally incomplete state. Keeping them in a separate file would make the two clearly distinct and the pipeline easier to follow.


Acknowledgements

I don’t have enough words to express my gratitude to my mentors, Kevin Kreiser and Christian Beiwinkel were the best mentors I could have ever asked for. I’m extremely thankful for their guidance, patience and for making me feel encouraged and proud of every little step I was making. It’s incredible how much you can learn from people like them, who have been working on Valhalla for such a long time.

A shout-out also goes to Nils Nolde, who wasn’t my mentor but was really kind during the application process and throughout our interactions during the summer.

Also, I have to thank all the Valhalla and OpenStreetMap community, which, through the forum, diary entries, and the Valhalla repository, helped us to find some things we had to rethink or try in a different way.

This has been a life-changing process, it was a pleasure to get to know my mentors and this community. It’s the end of the program, but I’m sure not the last you’ll see of me around Valhalla.



OpenStreetMap Blog

A Recap of the March Local Chapters & Communities Congress

What is the Local Chapters & Communities Congress? The Local Chapters and Communities Congress 2026 (LCCC 2026) is a virtual event where leaders and members of various OSM communities, whether they are officially recognized Local Chapters of the OSM Foundation or just a regular user group of OSM mappers, come together to share stories and […]

What is the Local Chapters & Communities Congress?

The Local Chapters and Communities Congress 2026 (LCCC 2026) is a virtual event where leaders and members of various OSM communities, whether they are officially recognized Local Chapters of the OSM Foundation or just a regular user group of OSM mappers, come together to share stories and learn from each other. Each year we convenet to see what kinds of organizational efforts we can share together to support and grow our mapping communities. You can see LCCC notes and the full agenda/more info on the wiki page.

What did we discuss?

The group met on a Saturday, March 28, and over the course of 2 hours more than 30 particants joined the Congress from Italy, Indonesia, Greece, the USA, Belgium, Kenya, Canada, Brazil, Malawi, and more! To kick things off, the group went around the room and the participants shared some things their communities were working on. This included mapping rivers and streams in the Philippines, mapping toponyms in Indonesia, Spain having their first SOTM, mapping in Greece, work of the MapRVA group in Richmond VA USA, mapathons in Kenya, mapping in a shareable format for Quebec, and more fun things.

An update from the OSMF Board

In the next part of the event, members of the OSMF Board shared information about the OSMF and what things they have been up to over the year. In 2025 it welcomed new corporate members (e.g., Niantic Spatial, Regione Marche) and secured a Sovereign Tech Fund grant of €384,000 and welcomed AC3 in Colombia as a new local chapter. They are presently fundraising for an additional operations position, planning a Madrid board F2F, establishing a Belgium subsidiary, and organizing SotM 2026 in Paris (Aug 28–30). Catch up with them at the Board AMA in Paris in August!

Open Discussion: Overcoming Challenges in OSM

The next part of the congress was time for the participants to share perspective and experience, with some questions as guidance. The LCCWG used the Menti tool to get feedback asynch from participants and then space was held to discuss. You can see the full notes at this Hackpad.

If a new mapper asked you ‘what’s the hardest part about being in the OSM community’ what would you say?
Answers included challenges with language, unclear entry points, and feeling unwelcome in the community. Here are a few quotes:

  • Documentation mostly in English
  • Hard to explain why OSM is needed when Google Maps, Waze & Apple Maps already exist
  • Not being demotivated by expert mappers who might “yell” at them for doing mistakes while mapping
  • Encountering negative/unproductive discourse in OSM fora, which can be discourage participation from new users
  • If you are not already technologically literate, it’s a lot to learn and unclear where to start

What makes it hard to grow or sustain your community?
Many participants found it hard to find time or funding to organize events and projects, and find it difficult to connect with mappers across a region. Here are a few quotes:

  • The distributed nature of the work can make it hard to reach out to people in the region. I feel we could havea better integrated tool to talk to local mappers directly.
  • Even in English, it’s difficult to find good resources like tutuorials for getting people started with mapping.
  • Volunteer time is in the cracks between ‘more serious’ work. So while it is easy to get new folks in the community it’s hard to get consistent investment over longer time periods.
  • Most members from the community prefer money-yielding activities and the idea of volunteer driven initiatives are not so welcomed.

Is there a gap between the ‘global OSM’ and your local reality? Where do you feel it?

  • Yes, in tagging practices and how to adapt to the local reality
  • There is a gap. People are drawn to local and immediate concerns by default and it’s hard to make people excited about global concerns and problems outside of conferences like SotM.
  • Core infrastructure needs work and innovation, and OSMF seems to struggle making progress. We need more transparency and openness to community input. Local communities need to shape our shared website.

What support do you wish the OSMF or the wider community provided but doesn’t?
Answers to this question mentioned funding, appreciation, clear leadership, and a more friendly community space. Here are additional quotes:

  • Make sure the core software project are active and support/discuss with the community
  • Technical & practical starting packages for community building
  • A mix of more formal and informal meetups, from “let’s hear a presentation about the person’s mapping project” to “let’s meet at a bar and hang out as friends”

What are ways you get your community together?
Answers to this question included virtual mappy hours, annual in person events/sotms, social media & chat groups for messages and announcements, and organized trainings. Here are a few quotes:

  • Online meetings, and make them useful for both new and experienced users so we all learn from each other
  • Daily communication via chat makes us feel close between bigger events
  • Doing projects with free participation w/ a co-work mentality

What ideas do you have to help grow and sustain OSM?
This final question brought in a lot of great ideas. You can see them all in the graphic below.
chrome_5Vu7PMoDjH
chrome_jKzg2PquoE

How to Participate in the Local Chapters & Communities Working Group

As you can see, the LCCC is for everyone to share ideas and meet fellow OSM enthusiasts from around the world. And we’d love for you to join us! Here are a few ways to get involved.

  1. Join the upcoming in person LCCC at State of the Map in Paris, France on August 28
  2. Join a monthly LCCWG meeting. Contact local@osmfoundation.org. We meet at 10amET /14:00UTC first Thursday of the month
  3. Help plan the next virtual LCCC in March 2027 – and join the conversation!

Thanks, hope to see you soon!


OpenStreetMap User's Diaries

65TH PLACE!! (PAGSASALIN SA TAGALOG)

Alam ko na hindi mahalaga ang ranggo at stats dito sa OSM

Alam mo kung ano ang matindi, Na dalawang buwan at isang linggo pa lang ang lumipas, mula nang nagsimula akong mag-ambag sa OpenStreetMap

Sa totoo lang, naniniwala akong isa ako sa pinakamabilis lumaking OSM contributors sa Pilipinas.

Ako ay ika-65 na pwesto sa Pilipinas!

Alam ko na hindi mahalaga ang ranggo at stats dito sa OSM

Alam mo kung ano ang matindi, Na dalawang buwan at isang linggo pa lang ang lumipas, mula nang nagsimula akong mag-ambag sa OpenStreetMap

Sa totoo lang, naniniwala akong isa ako sa pinakamabilis lumaking OSM contributors sa Pilipinas.


State of the Map 2026

I plan to participate in State of the Map 2026 next week.

So, in preparation for it, I read the programme page on the SOTM 2026 website and manually picked out all the topics that I’m interested in.

I plan to use the list below as a guide to help me navigate the programme and decide which events I should attend.

Friday, Aug 28 :
* 14.30 : Guadeloupe - Opening - S

I plan to participate in State of the Map 2026 next week.

So, in preparation for it, I read the programme page on the SOTM 2026 website and manually picked out all the topics that I’m interested in.

I plan to use the list below as a guide to help me navigate the programme and decide which events I should attend.


Friday, Aug 28 :
* 14.30 : Guadeloupe - Opening - SotM Working Group
* 14.50 : Guadeloupe - State of Panoramax (Christian Quest, Adrien Pavie)
* 16.15 : Martinique - Sneaking in OSM data into a big old company (Céline DURUPT, Tristram Gräbener)
* 16.50 : Guadeloupe - Perspectives on editors  (Pieter Vander Vennet) | La Réunion -  The democratic stakes of mapmaking: a cross-community panel (Matthieu Chatry)
* 17.25 : Guadeloupe - Update on attribution enforcement for users of OpenStreetMap servers (Mateusz Konieczny)
* 19.30 : Guadeloupe - Emergency Services using OpenStreetMap in Germany (dadavid)
* 20.05 : Martinique - Publishing 14,000 Businesses to OpenStreetMap: How Community Feedback Reshaped Our Publisher (🇫🇷) (Digitaleo)
* 20.40 : Guadeloupe - Do maps have a future in OpenStreetMap? (Christoph Hormann) | La Réunion - OSMPID: A Persistent ID Specification and an Object Identity Service (Stefan Keller)
* 21.45 : Guadeloupe - Client-Side Transport Maps on OpenStreetMap.org (Andy Allan)  | La Réunion - Mapterhorn Terrain and Imagery (Oliver Wipfli)
* 22.20 : Guadeloupe - Sourdough and Layercake: removing technical barriers to using OSM data for cartography and analysis (Jake Low) | Martinique - Lightning Talks I (SotM Working Group)
* 22.55 : Guadeloupe - MapLibre - from data to rendering, in one status update (Yuri Astrakhan, Frank Elsinga) | La Réunion - State of OpenHistoricalMap: mapping the world's history, openly (Ruben Lopez Mendoza, Minh Nguyễn)

Saturday, Aug 29
* 14.30 : Martinique - OSM Science 2026: Introduction (Yair Grinberger)
* 16.15 : Corse - Centipede-RTK with RTKBase and Millipede: centimeter-level GNSS positioning (Pierre Beyssac)
* 16.50 : Martinique - Reconstructing A High-detailed Lane-Level Road Network Model from OpenStreetMap: A Connectivity-Driven Approach (Chengzhi Rao) | Corse - How OSM inspire CEN standards for cycling infrastructure (Tu-Tho Thai)
* 17.25 : Corse - Making a living on OSM by nurturing the commons : inside the French Federation of OSM professionals (Marina Petkova, Florian Lainez)
* 19.30 : Guadeloupe - Construction ahead (Minh Nguyễn, Pablo Brasero, Ruben Lopez Mendoza) | La Réunion - Why do you contribute to OSM? (Michael Montani) | Corse - Lightning Talks II | 
* 20.05 : Guadeloupe - Upgrading the OSM Front Page (Frank Elsinga) | Martinique - Inter-Faceing the Critique – A Socio-technical Perspective on Humanitarian Mapping with the HOT TM (Charlotte Liebel)
* 20.40 :  Guadeloupe - Running OpenStreetMap.org in the Age of AI (Grant Slater) | Corse - When Maps Mislead: Lessons from Outdoor Navigation with OpenStreetMap (Jakub Zmrzlik)
* 21.45 : Guadeloupe - Clearance: Quality Proxy for OSM Replication. The Roadmap up to v1.0  (Frédéric Rodrigo) | Corse - How OpenStreetMap became the backbone of France's National Cycling Database (Samuel Deschamps-Berger)
* 22.20 : Guadeloupe - Adopt Your Town (Giacomo Alessandroni) | Martinique - Consumed at Scale: AI-Driven Extraction and the Political Economy of OpenStreetMap (Hannah Boettcher) | Corse - Lightning Talks III 
* 22.55 : Guadeloupe - The Power of quality in OpenStreetMap (François Lacombe, Marina Petkova, Tobias Augspurger) | La Réunion - Search and find what you are looking for (Sarah Hoffmann) | Corse - A new stack for OpenStreetMap vector tiles (Matt White)

Sunday, Aug 30
* 14.30 : Guadeloupe - Panoramax Netherlands (Bas Bussink) | La Réunion - Where are my ways? (Michael Reichert) | Martinique - Corporate Editing and Collective Intelligence in OpenStreetMap: A Long-Term Analysis of Southeast Asian Case Studies (Yair Grinberger)
* 15.05 : Guadeloupe - 50 States (and at Least as Many Mappers): Community Building in the US Over the Last Decade (Alyssa Castronuovo, Maggie Cawley)
* 16.15 : La Réunion - Lightning Talks IV 
* 16.50 : Guadeloupe - Making world spinning faster - How we sped up Valhalla graph creation in 3 times (Stefan Kizim) | La Réunion - UN Mappers: Building Local Capacities and Communities to Support Peace with OpenStreetMap (Laura Mugeha, Diego Gonzalez Ferreiro)
* 17.30 : Martinique - OSM contribution analysis in war time (Amine Chebil, Raphaël Bres, Malek Rihani)
* 17.35 : Guadeloupe - Handling Temporary Closures in OpenStreetMap (Matteo) | La Réunion - Milan to Paris via Dundee: ohsome 2.0 has arrived! (Benjamin Herfort) | Martinique - Revealing past railway networks from OSM data (Robert Jeansoulin, Philippe Gambette)
* 19.30 : Guadeloupe - OSMF Board AMA (Laura Mugeha, Héctor Ochoa Ortiz) | Martinique - Making maps with Ultra (Daniel Schep)
* 20.05 : La Réunion - 1000 ways to kill OpenStreetMap in Ghana and elsewhere in Africa (Enock Seth Nyamador) | Martinique - Lightning Talks V
* 20.40 : Guadeloupe - Wonders of OSM (CapitaineMoustache)  | La Réunion - OSMSG : OpenStreetMap User Group Hashtag Stats (Kshitij Raj Sharma, Gaurav Baral, Niruta Neupane)
* 21.45 : Guadeloupe - Closing

Epilogue :


65TH PLACE!!

I know rankings and stats don’t matter here in OSM

You know what’s crazy, That It’s only been 2 months and 1 week, Since I started contributing in OpenStreetMap

For real, I genuinely think, I am one of the fastest growing OSM contributors in the Philippines.

I am 65th Place in the Philippines!

I know rankings and stats don’t matter here in OSM

You know what’s crazy, That It’s only been 2 months and 1 week, Since I started contributing in OpenStreetMap

For real, I genuinely think, I am one of the fastest growing OSM contributors in the Philippines.

Wednesday, 19. August 2026

OpenStreetMap User's Diaries

An example of a (small) territory mapped using the OSM Skeleton methodology

Following the launch of the OSM Skeleton methodology (see this post, featured in weeklyOSM #836), I wanted to illustrate it with an example by resolving the main reports in an area of Senegal where the demo is currently being deployed.

At first, I thought about mapping the Koungheul department, but given the scale of the task, I ultimately settled for one of its arrondissements, Ida Mour

Following the launch of the OSM Skeleton methodology (see this post, featured in weeklyOSM #836), I wanted to illustrate it with an example by resolving the main reports in an area of Senegal where the demo is currently being deployed.

At first, I thought about mapping the Koungheul department, but given the scale of the task, I ultimately settled for one of its arrondissements, Ida Mouride. Arrondissements are the third level of administration in Senegal, after regions and departments.

The small size and limited number of Skeleton reports in this district allowed me to complete the task in about fifteen sessions of my daily OSM mapping routine.

The initial situation as of July 31 was as follows, for the entire department: Skeleton_Koungheul_20260731

And zooming in on Koungheul:

Skeleton_Ida_Mouride_20260730

Here are the same areas today:

Skeleton_Koungheul_20260819 Skeleton_Ida_Mouride_20260819

I created a statistics dashboard to track the progress for each type of report between August 5 and 19 (so my initial edits - which mainly involved about ten large villages without residential zones - are missing). The charts should be read as “Remaining / Total at the Start.” In the example below, the 18 hamlets without residential areas have thus been mapped:

Skeleton_Ida_Mouride_stats_missing_residentia_areas_20260805-20260819

As can be seen across the entire dashboard, there are no longer any reports regarding already identified settlement areas larger than 20 ha. While there is certainly still work to be done on smaller settlement areas, this already means that within the territory of this arrondissement, all settlement areas larger than 20 ha are clearly characterized by a categorized location, are connected to the road network, and are represented by a residential area updated within the last five years with an acceptable number of nodes.

This is a more rigorous approach than mapping an entire territory solely through a supposedly rigorous observation phase using satellite imagery, followed by an additional validation phase using the same approach. It is a first milestone in establishing a reference OSM dataset for this territory.

Other homogeneity milestones will soon be available in the Skeleton methodology with the upcoming addition of report layers to identify settlement areas still missing from OpenStreetMap, verify place categories that seem unusual given the size of their settlement areas, clean up the roads geometries, improve their connectivity, and verify key road network tags, as well as identify different categories of essential objects missing within major urban areas.

Translated from French with DeepL.com (free version)


Un exemple de (petit) territoire cartographié avec la méthodologie OSM Skeleton

Suite au lancement de la méthodologie OSM Skeleton (voir ce billet, repris dans hebdoOSM 836), j’ai voulu l’illustrer avec un exemple, en résolvant les principaux signalements sur une zone du Sénégal, où la démo est actuellement déployée.

J’ai pensé au départ faire le département de Koungheul, mais vu l’ampleur de la tâche, je me suis finalement contenté de l’un de ses arrondissements, c

Suite au lancement de la méthodologie OSM Skeleton (voir ce billet, repris dans hebdoOSM 836), j’ai voulu l’illustrer avec un exemple, en résolvant les principaux signalements sur une zone du Sénégal, où la démo est actuellement déployée.

J’ai pensé au départ faire le département de Koungheul, mais vu l’ampleur de la tâche, je me suis finalement contenté de l’un de ses arrondissements, celui d’Ida Mouride. Les arrondissements constituent le troisième échelon administratif du Sénégal, après les régions et les départements, arrondissements.

La petite taille et le nombre limité de signalements Skeleton que contient cet arrondissement m’ont permis d’en venir à bout en une quinzaine d’occurrences de ma petite séance quotidienne de cartographie dans OSM.

La situation de départ au 31 juillet était celle-ci, à l’échelle du département entier : Skeleton_Koungheul_20260731

Et en zoomant sur Koungheul :

Skeleton_Ida_Mouride_20260730

Voici les mêmes zones aujourd’hui :

Skeleton_Koungheul_20260819 Skeleton_Ida_Mouride_20260819

J’ai créé un tableau de bord statistique pour mesurer la progression pour chaque type de signalement, entre le 5 et le 19 août (il manque donc mes premiers edits, qui ont notamment concerné une dizaine de grands villages sans zone résidentielle). Les graphiques doivent se lire « Restant à faire / Total au départ ». Dans l’exemple ci-dessous, les 18 hameaux sans zone résidentielle ont donc été cartographiés :

Skeleton_Ida_Mouride_stats_missing_residentia_areas_20260805-20260819

On peut voir sur l’ensemble du tableau de bord qu’il ne reste plus de signalements concernant des zones de peuplement déjà identifiées et dont la surface est supérieure à 20 ha. Il reste certes encore à travailler sur les zones de peuplement plus petites, mais cela signifie déjà que sur le territoire de cet arrondissement, toutes les zones de peuplement de plus de 20 ha sont bien caractérisées par un de lieu catégorisé, sont reliées au réseau routier et sont représentées par une zone résidentielle mise à jour il y a moins de cinq ans avec un nombre acceptable de nœuds.

C’est une métrique plus rigoureuse que de cartographier tout un territoire seulement à travers une phase d’observation, supposément rigoureuse, d’une imagerie satellitaire suivie d’une phase de validation supplémentaire utilisant la même approche. C’est un premier jalon dans l’établissement d’une donnée OSM qui fait référence sur ce territoire.

D’autres jalons d’homogénéité seront bientôt disponibles dans la méthodologie Skeleton avec l’ajout prochain de couches de signalements pour identifier les zones de peuplement encore manquantes dans OpenStreetMap, vérifier des catégories de lieux qui paraissent étranges eu égard à la surface de leur zone de peuplement, nettoyer la géométrie, améliorer la connectivité et vérifier les principales étiquettes du réseau routier, ou encore identifier différences catégories d’objets essentiels manquants au sein des grandes agglomérations.


Names, Languages, and UX

I keep getting questions about multilingual names in OpenStreetMap, so I want to state my position clearly in one place.

I understand the OSM data-model argument: name:xx should normally represent a name that actually exists in that language, not simply a machine-generated translation. My mapping practice has evolved accordingly.

However, as a product person, I care

I keep getting questions about multilingual names in OpenStreetMap, so I want to state my position clearly in one place.

I understand the OSM data-model argument: name:xx should normally represent a name that actually exists in that language, not simply a machine-generated translation. My mapping practice has evolved accordingly.

However, as a product person, I care primarily about the user experience.

A map is a product used by real people. If I travel to a country whose writing system I cannot read, a map that shows me only the local script may be technically pure but practically much less useful.

For example, an English-, Russian-, or Georgian-speaking traveller should not need to read Arabic, Chinese, Thai, or another unfamiliar script just to understand what street, station, church, village, or other place they are looking at.

There are several ways to solve this:

  • verified names in the user’s language;
  • standardized transliteration;
  • localized rendering;
  • automatic transliteration or translation at the application layer;
  • sensible fallback rules when no localized name exists.

I do not particularly care which layer solves the problem.

What I care about is the outcome:

the user should be able to understand the map.

Database purity is useful when it improves data quality. It should not become an excuse for poor UX.

OpenStreetMap is a geographic database, but the value of that database ultimately comes from people being able to use it.

For OSM naming guidance, see:

This post also reflects the lessons I took from my earlier discussion about AI-assisted multilingual tagging. I no longer treat automatically generated translations as sufficient evidence that a name:xx exists.

But my broader position has not changed:

when data modelling and usability pull in different directions, I will keep advocating for a solution that gives users both accurate data and a usable map.

If you have a question about my general position on multilingual naming, please refer to this post rather than restarting the same discussion in individual changesets.


Via Crucis in Switzerland [Via Crucis in Svizzera; Chemins de croix en Suisse; Kreuzwege/Stationenwege in der Schweiz ]

Thanks to a note suggested adding a Via Crucis station, I checked how similar routes in Switzerland are mapped in OpenStreetMap.

OSM tags relations for these with worship=stations_of_the_cross (and type=route route=worship ).

These relations model outdoor paths, not stations located inside a single church building.

  • They

Thanks to a note suggested adding a Via Crucis station, I checked how similar routes in Switzerland are mapped in OpenStreetMap.

OSM tags relations for these with worship=stations_of_the_cross (and type=route route=worship ).

These relations model outdoor paths, not stations located inside a single church building.

  • They can be found in traditionally Catholic regions of Switzerland. The ones mapped in OSM are mainly in Ticino and the canton of Solothurn (Soleure).
  • Traditionally there are 14 stations, sometimes 15 stations.
  • The monuments at stations vary: stones, crosses, sculptures, shrines or chapels.
  • Distances and ascent vary: The ones at Sant’Abbondio and Astano follow the walls of the churchyard, the one to Madonna del Sasso has an ascent of almost 200 m.
  • Some paths are old (18th or 19th century), others are more recent.
  • The state of preservation varies greatly.
  • Many routes lead to a chapel.
  • Some paths to chapels feature stations on other subjects. These have route=worship , but not worship=stations_of_the_cross .

RSI counts 54 in Italian-speaking Switzerland; the scope may not match OSM’s outdoor-route tagging. OSM has 10 Via Crucis in Ticino.

OSM has about 2000 wayside crosses and 1200 wayside “shrines” in Switzerland. Some could be part of Via Crucis that aren’t mapped yet.

Here is a short clip of the one above Biasca and a longer video about the one at Klingnau.

List

Here are a few mapped:

Via Crucis canton
Eiken AG
Hornussen AG
Klingnau AG
Sumvitg GR
Horw LU
Maria Bildstein SG
Montlingerberg SG
Wil SG
Erschwil SO
Kappel SO
Kleinlützel SO
Rodersdorf SO
Römerswil Gormund SO
Egerkingen SO
Einsiedeln SZ
Ingenbohl SZ
Bernrain TG
Klingenzell TG
Astano TI
Biasca TI
Bidogno TI
Bigorio TI
Campo Vallemaggia TI
Comano TI
Madonna del Sasso TI
Ongero TI
Sacro Monte di Brissago TI
Sant’Abbondio a Gentilino TI
Burgspitz VS
Meyes VS
Naters VS
Scheibenwald VS
Wickert VS

Mapping

Depending on the location and the structure at each station, they can sometimes be mapped with aerial imagery. Generally paths are already mapped, sometimes also stations (as wayside crosses or shrines) and chapels at the end of the paths (at least as building).

Basic mapping for a Via Crucis route:

  • 1 relation for route
  • 1 start node
  • 1 or many ways for the route
  • 14/15 nodes for station
  • 1 way for chapel at the end

osm.wiki/Tag:worship=stations_of_the_cross#Fixme has a checklist to improve them.

Tuesday, 18. August 2026

OpenStreetMap User's Diaries

1.8公斤的電源你就給我十塊錢?

好的關於這破電源我是非常生氣,一個貼牌電源把我一條記憶體打壞了,下次不用二手的了再用我是小狗。

反正這不是重點,壞了就壞了,誰不會壞嘛。but那個破回收場,明知道裡面都是銅線,還用廢鐵價跟我收,純把我當豬仔宰是吧,還只有十塊錢,十塊錢欸,掛社團我都至少還有一杯手搖,好歹也給我15 20我去買冰水喝,以後不去了,黑。

反正賣完我就嘎拉嘎拉的騎著我的破腳踏車四處閒晃了,三個小時大概騎了20公里吧,沒很累,但到底是誰會把鐵皮屋標廟宇啊,我想說我怎麼沒聽過埔里有這個廟,騎過去一看,還真的鐵皮屋,不過應該是別人家,這人真無聊。還有不知道誰把荒地裡標一個廟宇,我 跑進去被蚊子叮慘了。

今天主要是跑郊區,市區太多要標的了標不完,明天跑田裡的廟吧,車少也好騎。

好的關於這破電源我是非常生氣,一個貼牌電源把我一條記憶體打壞了,下次不用二手的了再用我是小狗。

反正這不是重點,壞了就壞了,誰不會壞嘛。but那個破回收場,明知道裡面都是銅線,還用廢鐵價跟我收,純把我當豬仔宰是吧,還只有十塊錢,十塊錢欸,掛社團我都至少還有一杯手搖,好歹也給我15 20我去買冰水喝,以後不去了,黑。

反正賣完我就嘎拉嘎拉的騎著我的破腳踏車四處閒晃了,三個小時大概騎了20公里吧,沒很累,但到底是誰會把鐵皮屋標廟宇啊,我想說我怎麼沒聽過埔里有這個廟,騎過去一看,還真的鐵皮屋,不過應該是別人家,這人真無聊。還有不知道誰把荒地裡標一個廟宇,我 跑進去被蚊子叮慘了。

今天主要是跑郊區,市區太多要標的了標不完,明天跑田裡的廟吧,車少也好騎。


My 1st contribution

I remember when I first heard about these traffic cameras this guy paid me to listen to apb and manually log the codes to later look up and learn. Thinking about it these people were dangerous but it was normal for me being a military brat who joined the Marines after high school. I reminded the highest ranking ones of my grandfather who served 30 years. I guess it stirred up emotions making th

I remember when I first heard about these traffic cameras this guy paid me to listen to apb and manually log the codes to later look up and learn. Thinking about it these people were dangerous but it was normal for me being a military brat who joined the Marines after high school. I reminded the highest ranking ones of my grandfather who served 30 years. I guess it stirred up emotions making them uncomfortable cause I was clueless of my early departure resulting me in an unforseen path unaligned with my preset destiny.

This contribution is what Google identified as alpr I have a pic of it is just amazing how it doesn’t catch the license plate of a vehicle sitting in the middle of the intersection to prove truth of the occasion. Truth shall set us free


My view on life

Your life is only a see through I never wanted to be you my goal was to necessary to those who needed a new perspective to bring others from the darkness into the light to be abundant. While in the darkness no one tried to save me instead my heart was like a clothes line chopped up into millions of pieces. I answered to the calling of the darkness and won my right to be to be silent. I learned t

Your life is only a see through I never wanted to be you my goal was to necessary to those who needed a new perspective to bring others from the darkness into the light to be abundant. While in the darkness no one tried to save me instead my heart was like a clothes line chopped up into millions of pieces. I answered to the calling of the darkness and won my right to be to be silent. I learned to dim my brightness to a dull roar to respect those imbedded in the deep roots. They know I veil from divine right always seemed to be an outcast. I fell in love with the people everyone of them are necessary. I can’t speak about a certainty to take place when the times right. I understand it’s necessary thanks for not making it scary. Realization of I’m crazy just like you I’ll be a very bitter taste to you. Don’t take something your not willing to part from.


FOSSGIS e.V. / OSM Germany

FOSSGIS und OpenStreetMap auf Maker Faire und FrOSCon

Am dritten Augustwochenende organisierten Aktive aus der OpenStreetMap-Community und des FOSSGIS-Vereins zeitgleich zwei Messe- und Konferenzauftritte auf der Maker Faire Hannover und der FrOSCon.

Maker Faire Hannover

Wie schon in den vergangenen Jahren war der FOSSGIS auch auf der diesjährigen Maker Faire in Hannover wieder mit einem Stand vertreten. Vier am Samstag und am Sonntag sogar

Am dritten Augustwochenende organisierten Aktive aus der OpenStreetMap-Community und des FOSSGIS-Vereins zeitgleich zwei Messe- und Konferenzauftritte auf der Maker Faire Hannover und der FrOSCon.

Maker Faire Hannover

Wie schon in den vergangenen Jahren war der FOSSGIS auch auf der diesjährigen Maker Faire in Hannover wieder mit einem Stand vertreten. Vier am Samstag und am Sonntag sogar fünf Aktive sorgten dafür, OpenStreetMap bekannter zu machen. Das eingespielte Team aus Mappern unterschiedlicher Bereiche beantworten die vielfältigen Fragen der Besucher. An den beiden Tagen wurden jeweils über 70 ausführliche Gespräche mit Besucherinnen und Besuchern geführt.

Auch dieses Jahr zogen die mit einem 3D-Drucker erstellten taktilen Karten wieder großes Interesse auf sich. Doch auch unsere großformatigen Papierkarten für die eigene Wand fanden zahlreiche Abnehmer. Insgesamt haben wir über 50 Karten für die Besucherinnen und Besucher der Messe ausgedruckt. Von den jüngeren Besuchern freuen sich jetzt einige auf die nächste Hydrantensuche mit der Jugenfeuerwehr bzw. über eine neue Karte des Stadionumfeldes ihres Lieblingsfußballvereins.

Wie in den vergangenen Jahren war es ein gelungenes Wochenende um das Projekt bekannter zu machen und den einen oder anderen neuen Teilnehmenden für das Projekt zu begeistern.

FrOSCon

Auch auf der FrOSCon in Sankt Augustin bei Bonn hatte der FOSSGIS einen Stand für das OpenStreetMap-Projekt organisiert. Ebenso wie bei der Maker Faire waren wir mit einem Großformatdrucker vor Ort. Die Möglichkeit zum Drucken individuell gestalteter Karten aus OpenStreetMap-Daten wurde begeistert angenommen und es ergaben sich zahlreiche interessante Gespräche. Martin Raifer, Maintainer des ID-Editors auf openstreetmap.org, hielt einen Einführungsworkshop zu OSM, der sehr gut besucht war. FOSSGIS-Vorstand Falk Zscheile beleuchtete in seinem spannenden Vortrag die rechtlichten Aspekte beim Training von generativer KI mit OSM- und anderen offenen Daten. Ein weiterer Vortrag beschäftigte sich mit der Nutzung von OSM-Daten und freier OpenSource-Software bei der Entwicklung eines Verfahrens zur Lagebewertung von Immobilien, das Banken des Sparkassenverbundes bei Entscheidungen zur Kreditvergabe unterstützt.

Diese eindruckvolle thematische Vielfalt der Beiträge zeigt, dass OpenStreetMap nach 22 Jahren eine große gesellschaftliche Verbreitung erreicht hat. Aufgabe des FOSSGIS-Vereins ist es, Beitragende und Nutzende von OpenStreetMap-Daten und freier OpenSource-Software aus unterschiedlichsten Bereichen von Gesellschaft und Wirtschaft zusammenzubringen.

Unser Dank gilt den Aktiven, die als Standpersonal und Beitragende das OpenStreetMap-Projekt auf Maker Faire und FrOSCon hervorragend präsentiert haben. Ganz besonders danken wir Hartmut Holzgräfe, dem Maintainer von print.get-map.org, der sich sowohl in Hannover als auch in Sankt Augustin um den Aufbau der Großformatdrucker gekümmert hat, indem er am Wochenende zwischen den Veranstaltungsorten hin und her pendelte.

Der OSM-Stand auf der Maker Faire Hannover
OSM-Standteam auf der FrOSCon
Der OSM-Workshop auf der FrOSCon war gut besucht.

Monday, 17. August 2026

OpenStreetMap User's Diaries

So, how far did i actually cycle today?

Several weeks ago, my bicycle finally got fixed, after being abandoned in a broken state for a long time.

Before that, I didn’t even know that my bicycle was actually broken.

All I knew was that this bicycle was really, really, really tiring to use. Even a short-distance trip was enough to tire me out for the whole day.

I didn’t know that this was caused by something bein

Several weeks ago, my bicycle finally got fixed, after being abandoned in a broken state for a long time.

Before that, I didn’t even know that my bicycle was actually broken.

All I knew was that this bicycle was really, really, really tiring to use. Even a short-distance trip was enough to tire me out for the whole day.

I didn’t know that this was caused by something being broken, which meant I had to put in (approximately) twice the effort to make it move (citation needed).

At that time, I simply blamed my own weak body. “Maybe I’m not strong enough to wield this bicycle,” I thought, dejected, considering giving up my whole cycling career prematurely.

Then, one random day, one of my family members used that bicycle, noticed something wrong with it, fixed it, and then it was finally ridable without needing much energy and force.

Alright. Now I can use my bicycle again, I guess.


For short trips, I usually prefer a bicycle to a motorcycle, for several reasons, you name it : hiking gas prices, the need to reduce our own carbon footprint to save the Earth (back then I took the mandatory environmental college course and thanks to that I’m still brainwashed so hard about the need to reduce my own carbon footprint), a nice opportunity to exercise my body, and the previous trauma of using a motorcycle and then suddenly having the engine not start so I had to walk the motorcycle to the nearest repair shop which turned out to be not near at all. Yeah, plenty of reasons.

So this afternoon, I decided to take a long trip to several places in my town, using my recently fixed bicycle.

I started around 4 PM and went home again around 6 PM.

Now it’s night, I’m sitting in front of my laptop, and getting curious : how many kilometers did I traverse this afternoon while cycling?


I didn’t bring a proper GPS device to record my trip this afternoon, but I remember each path that I took today. So, what should I do to calculate the distance?

At first, I tried BRouter.

My plan was, I’m gonna put several of the key places from my trip over there, hoping that its routing engine would show my actual path. After that, I could keep notes of the distance statistics.

But I met several problems.

First, putting several key places into that web UI is hard. There’s no “right click -> show context menu” to add/remove coordinates.

Second, the routing engine itself. It doesn’t show my actual path. There are several routing presets over there. I tried several, but none of them actually showed the path I had taken.

So I tried another alternative solution. This time, the OpenStreetMap.org homepage.

This time, the “right click -> show context menu” feature exists. I can pick “directions from here” and “directions to here” easily by using this neat feature.

But the problem is, it only allows two coordinates: from here and to here. Meanwhile, my trip consisted of plenty of intermediate places. There’s no such feature on OpenStreetMap.org.

So I tried another alternative solution. The OpenStreetMap.org homepage shows several “brands” of routing engines: GraphHopper, OSRM, and Valhalla.

I tried OSRM at first.

Alright. On the OSRM demo page, now I can add plenty of intermediate places. Not just “from here” and “to here.”

But it’s still difficult to properly place a coordinate in this web UI.

It says “press enter to drop a marker,” but nothing happened when I pressed Enter.

Also, when plenty of intermediate points are involved, I can’t add the “second” and “more” intermediate points. When I click on the map, it only changes the first intermediate point, even though I intended to add more intermediate points.

Alright, next. Valhalla.

From their GitHub repository, I went to their documentation page.

At the very bottom of that page, I saw this :

“valhalla-app: A React-based web app for Valhalla, powering https://valhalla.openstreetmap.de/.”

So I opened that link.

And finally, it works properly.

The right-click -> context menu feature shows “directions from here,” “add as via point,” and “directions to here.” Basically, all of my current needs are satisfied.

Then, we can add plenty of intermediate waypoints. It’s easy to delete them and rearrange their order.

And regarding the routing preset, the “pedestrian” preset works well for me.

That preset won’t go “over-creative” to find advanced detours that work well for cars and motorcycles. Instead, it picks the route in a “greedy algorithm” style, which works very well in my context. All of the paths I actually took previously were successfully predicted by using this pedestrian preset.

Thus, by using the Valhalla instance on the OpenStreetMap.de server, I finally uncovered the truth behind my bicycle trip this afternoon.

2.3 km : home - barber
0.8 km : barber - clothes shop A
0.5 km : clothes shop A - clothes shop B
1.7 km : clothes shop B - cake shop
1.2 km : cake shop - home

2.3 + 0.8 + 0.5 + 1.7 + 1.2 = 6.5 km

Alright. 6.5 km distance for today.


Project in the Mud

Oh, where do I start?

It was around October when I had recently imported the barangay boundaries of my hometown, Cauayan City. I had just asked the GIS team at the local Planning and Development Office to adjust the boundaries again, as many issues were identified in the dataset. A while later, I had an idea to try to help the GIS team adjust the boundaries, because I figured, “Why not?”

Oh, where do I start?

It was around October when I had recently imported the barangay boundaries of my hometown, Cauayan City. I had just asked the GIS team at the local Planning and Development Office to adjust the boundaries again, as many issues were identified in the dataset. A while later, I had an idea to try to help the GIS team adjust the boundaries, because I figured, “Why not?” and they’re probably doing a lot of work already, given so many developments in the area.

The current flawed official map

A little back and forth, but then they stopped responding. I mean, it is basically a 50/50 chance that they respond or not. A little later, I dove into further research and stuff, and I thought of asking an institution to collaborate with me on making a dataset for the PDO to use and merge with theirs, so it can be as accurate as possible (I like things accurate).

Thus, Project Cadastral Cauayan (CaCau) was born. I first emailed the Isabela State University. I chose them especially because of the Cauayan Campus. In my eyes, they were the most capable (and probably only) institution in the area to pull this off.

ISU Cauayan Campus

It was February 27 of this year. No response, so I kept trying new email addresses, follow-ups, and at one point, Messenger. Too many alternatives with no response, and about two months later, nothing. Until finally, through the Cauayan Campus’ newspaper email, the Kawayan Communicator, a Messenger notification popped up. It was someone in the newspaper. A little back-and-forth communication, and another month passed, and I realized this person was unreliable.

Northeastern College

Why do you ask? Because he kept delaying. He kept promising that he would bring it up to the offices and such, but never did. I pivoted. Where? Northeastern College, Santiago City, on May 23rd. They were the next closest academic institution in the area that could pull it off. From experience, I emailed their newspaper first. They first responded, but everything after that was pure silence. Another month came by, and the project went nowhere.

Once again, I pivoted. This time, to three. I first tried to contact the PDO once more, which led nowhere. The second one was the University of the Philippines - Department of Geodetic Engineering (UP DGE). They were very responsive, but they rejected it due to alignment reasons with their schedule, focus, etc. I also did them because of how much collaboration existed with OSM and the university. Lastly, was the Cagayan State University. Like always, no response.

It was now August 1. My final pivot, was private geodetic firms local to the city. Two of them. And you can predict what happens with the first one: nothing. They first responded, but then nothing else. The second one, was responsive, but like UP DGE, had rejected it due to alignment reasons.

I was tired by then. And school is eating up my schedule once more soon. So, I closed the project. After 5 and a half months of work, trying to get this project out of the mud, I couldn’t take it afloat anymore. I was also working remotely in Canada, so it is obvious that it also eats up some sleep space to try to align with the time gap.

But, in case, I will keep the files public. So if there is any interest into using the project and/or its files, then feel free to (as long as you comply with the licensing)!

My conclusion is: go as far as you can. This project isn’t failed because it never reached the finish line. It was a success, in research and evidence. It’s a success of the digital space.

Mabuhay, and god bless!


15.08.2026

♦ ♦ ♦ ♦ ♦ ♦
img img img
img img img

給我搞哪來了

呃好吧,我是新來的,可以叫我kiwi,熱愛刷機的kiwi。 先說說我為啥來這好了,我是為了因應「去谷歌化」與「自製BOB包」(好吧我根本就怪人),在網上爬啊爬,並在F-Droid上下載了這個開源地圖。 然後我在我刷了crdroid 8.6的Sony Xperia xz1上安裝了這個軟體,挺讓我驚奇的是,意外的好用,絲滑流暢,甚至在我的低端機上都運行的非常順利。 於是今天我就開始跑點了,我居住的小鎮上有很多無名小店,跑點這個過程讓我感到愉快。 希望各位能多多包涵我這怪人:) My telegram: t.me/taro_7421

呃好吧,我是新來的,可以叫我kiwi,熱愛刷機的kiwi。 先說說我為啥來這好了,我是為了因應「去谷歌化」與「自製BOB包」(好吧我根本就怪人),在網上爬啊爬,並在F-Droid上下載了這個開源地圖。 然後我在我刷了crdroid 8.6的Sony Xperia xz1上安裝了這個軟體,挺讓我驚奇的是,意外的好用,絲滑流暢,甚至在我的低端機上都運行的非常順利。 於是今天我就開始跑點了,我居住的小鎮上有很多無名小店,跑點這個過程讓我感到愉快。 希望各位能多多包涵我這怪人:) My telegram: https://t.me/taro_7421

Sunday, 16. August 2026

OpenStreetMap User's Diaries

Your edits are safe

One thing that usually worries us as OpenStreetMap mappers is having our hard work deleted by someone else, either accidentally or intentionally.

Thankfully, our edits are still in the database.

The delete operation in OpenStreetMap is not really a delete operation. It simply flips the object’s visible flag from true to false, while retainin

One thing that usually worries us as OpenStreetMap mappers is having our hard work deleted by someone else, either accidentally or intentionally.

Thankfully, our edits are still in the database.

The delete operation in OpenStreetMap is not really a delete operation. It simply flips the object’s visible flag from true to false, while retaining its entire history.

And you can resurrect them using JOSM’s “Undelete Object” feature, as long as you have the OSM object’s ID.


weeklyOSM

weeklyOSM 838

06/08/2026-12/08/2026 [1] “OSM Vexillophile” for flag enthusiasts | © watmildon | map data © by OpenStreetMap Contributors. Mapping SherbetS has proposed craft=meat_processing for small-scale facilities where hunters or animal owners bring a carcass to be cut into meat, as distinct from shop=butcher or industrial=slaughterhouse. RFC voting started on 30 July. The proposal grew

06/08/2026-12/08/2026

lead picture

[1] “OSM Vexillophile” for flag enthusiasts | © watmildon | map data © by OpenStreetMap Contributors.

Mapping

  • SherbetS has proposed craft=meat_processing for small-scale facilities where hunters or animal owners bring a carcass to be cut into meat, as distinct from shop=butcher or industrial=slaughterhouse. RFC voting started on 30 July. The proposal grew out of an earlier discussion on how to tag deer processors, where commenters debated craft=butcher, man_made=works, and various animal-specific alternatives before settling on the more general wording. In the RFC thread, several contributors argued that craft=butcher would fit just as well and that ‘meat processing’ sounds too industrial in British English, while others worried the new tag could end up being used for large commercial plants too.
  • Joost Schouppe started a discussion on differentiating police forces by government level (municipal, regional, national, gendarmerie, street warden), which grew into a formal RFC. The proposal defines police:branch=* with four values: gendarmerie, national_police, regional_police, and local_police, to classify which government level operates a police feature, alongside a separate police:specialisation key for topics like traffic or canine units. In the RFC thread, commenters questioned the ‘branch’ naming and whether four generic values can fit countries with far more complex police structures, such as Germany or Italy. The OSM Wiki Proposals account tooted that voting had opened, but Schouppe cancelled it a day later after reviewers asked for country examples and clearer definitions, sending both keys back to RFC.The OSM Wiki Proposals account tooted that voting had opened on fanfouer’s service supplies proposal. The proposal introduces line_management=service_supply to mark nodes where an individual household’s service drop or lateral taps a main utility line, plus an occupancy=* key to count connected supplies without mapping each one. The voting runs until 30 August. The idea was first floated a year ago as a way to ease mapping of overhead wires in dense residential streets, and the proposal has since been fleshed out with examples for power and telecommunications. Early votes are split with one voter having opposed extending line_management to non-power utilities before a separate pipeline proposal exists, while another approved it as filling a real gap.

Mapping campaigns

  • The OpenStreetMap Colombia Community is organising and coordinating on-the-ground mapping to identify damaged or destroyed buildings in the area affected by the earthquake in San Jose del Palmar (Colombia), with the support of UN Mappers and the Humanitarian OpenStreetMap Team (HOT). Emílio Mariscal has created a web map using uMap to support the mapping campaign, which is using the Chat Map. There are projects for collaborative mapping on the HOT Tasking Manager: #61980, #61914, and # 61320.
  • Semir Kahrimanovic has announced a new CompleteTheMap 2026 across Europe. New images from selected cities will be accepted from 10 August to 30 September with the sign-up deadline for entering the competition being 31 August.
  • Italy’s OSM mapping community monthly project for August, ‘Restrizioni, Direzioni e cartelli’, is focusing on improving information on how to get to various places by including details for road navigation and better routing.

Community

  • OpenStreetMap celebrated its 22nd birthday on 9 August and some well-known contributors to the OSM ecosystem responded with kind messages on social media: Yasmila Herrera (via Héctor Ortiz), the OSM LatAm community, Raquel Dezidério with the YouthMappers UFRJ, Dorothea Kazazi, Anne-Karoline Distel, and luiseme.
  • Melany Ventura, a UI/UX designer, is the Trufi Association’s new Featured Volunteer, improving Trufi’s OSM-based journey planner apps, and more.
  • In the latest episode of the Geomob Podcast, Dennis Luxen joined the show to discuss the history, and the technical and community-driven development of the Open Source Routing Machine, an open-source routing engine used in OpenStreetMap.
  • Christoph Hormann commented on the recent discussion in the OpenStreetMap community regarding corporate influence on the project.
  • Rphyrin is conducting a personal mapping campaign to add geolocated images to their corresponding OSM objects using the image=* tag. The results so far are being showcased through an Overpass Ultra query in a Mastodon post thread.
  • Valère Déjo published an article on La Remuante, ‘A new cycle path on the map’, focusing on the city of Saint-Étienne (France), which is introducing new cycle paths and offering the opportunity to map them in OSM using Panoramax.

OpenStreetMap Foundation

  • Grant Slater reported that he is physically installing a new OpenStreetMap tile render server in Dublin, kindly sponsored by QGIS, which is expected to make tile rendering faster on the GIS.

Events

  • In the newest episode of the Projets Libres podcast, Benoît Peyon, a member of the organising committee for State of the Map 2026, was interviewed about the event.
  • The 1st Global Convening on Informal and Shared Mobility (GloCon 2026) will take place in Bangkok from 26 to 28 October. OSM advocates can meet thought leaders improving transport systems worldwide.
  • On 12 August the HOT Asia Pacific Hub held its quarterly Regional Mapathon Asia-Pacific. During the event they announced several upcoming Open Mapping Guru Pro+ events in Sri Lanka, the Philippines, Nepal, and India, and the upcoming October–November 2026 Open Mapping Guru Network recruitment cycle. You can read more details.
  • Wikimedia Italia reported that the University of Trento, together with GFOSS.it, hosted FOSS4G-IT and OSMit 2026 from 9 to 11 July.

Maps

  • Björn showcased Hoscy, a web map where users can compare prices at ad-hoc EV charging stations. Here, ‘ad-hoc charging’ means EV charging where you pay as you go without having a contract, subscription, or membership with the charging network.
  • Jvaclavik announced the release of OpenClimbing 2.0, an open-source climbing guide built on OpenStreetMap and other open data. Since 2023, the OpenClimbing project has been developed alongside OsmAPP in a shared codebase, but the developers recently decided to fork it into a separate repository.
  • Nicofr77 has combined OpenStreetMap cycle route data, with the official French cycle route reference, to identify bike-and-train loops between two stations, allowing people to cycle one way and return by train.
  • Dieter Petereit reported that a Norwegian developer, operating under the pseudonym ‘Flightmussy_CEO’, is currently developing World Train Map, a curated atlas of notable passenger rail routes around the world, which currently showcases 1,269 railway routes.
  • Renaud Zi has developed a free tool that simulates the recent solar eclipse for any location in Europe. It combines building and forest data from OSM with NASA data. It has been pointed out on the forum that a licence is missing, and that strictly speaking, the code that is available for viewing may not be freely reused.

OSM in action

  • Pit Stop App is a mobile app that shows petrol stations, restaurants, accommodation, and must-see attractions at every exit ahead on America’s interstate highways. Powered by OpenStreetMap data, the app determines which interstate you’re on and the direction you’re travelling, then lists everything available at upcoming exits, sorted by the order in which you’ll reach them.

Software

  • [1] Matt Whilden has developed ‘OSM Vexillophile’, a web app that helps OSM users complete all the flags on their ‘How Did You Contribute?’ page by finding MapRoulette, Osmose, or HOT Tasking Manager tasks in countries where they are still missing a flag.
  • Devinius has built Knudli, a Flutter app that helps users discover playgrounds using OpenStreetMap data.

Programming

  • Sarah Hoffmann announced, on the OSM Community forum, that she has lowered limits for clients to be automatically banned on overpass-api.de. She is going to ban apps completely if they receive a high number of HTTP 429 (Too many requests) or are hosted on a fast-deployment platform.
  • Benjamin Altpeter has developed scripts to convert the iD editor’s presets for OpenStreetMap into JOSM presets. This lets users take advantage of JOSM’s powerful advanced features, while still benefiting from the familiar terms and aliases provided by iD presets, making it much easier to find the right preset, even if they don’t already know the correct OpenStreetMap tag.

Releases

  • The team behind the OSM website are back with a recap of the latest changes. The month of July and a bit of August include an all-new notifications page, offering an alternative to the usual emails about new comments, followers, GPX uploads, notes, and diaries. Work has also be done to improve database backups, which in turn benefits the generation of weekly planet files. Moderators can now define zones with disabled anonymous notes themselves.
  • Martin Raifer released OpenStreetMap iD version 2.42.0.
  • Pavel Zbytovský announced the release of OsmAPP versions 1.8.0 and 1.9.0.
  • Anders has announced there is a new beta version of the Mapillary app, which includes two new layers: ‘Best captures’ and ‘Captures needed’, new filters, and the option to display traffic signs and POI features on the map.

Did you know that …

  • … Sybren A Stüvel recently learned about Touch Mapper? This is a web app that uses OpenStreetMap data to create printable 3D models of an area, allowing people with little or no vision to literally get a feel for the place.
  • … Alex Hoferek presented the results of his research, on the profile of OSM corporate editors, at State of the Map 2024? The presentation details the characteristics of their activities, such as length of employment time and the most commonly mapped feature types, as well as the challenges these contributors faced in participating in the OSM ecosystem.
  • … the ‘Sustainable Digitalisation’ community of the German Federal Ministry for the Environment, Nature Conservation, and Nuclear Safety, in collaboration with Wikimedia Germany and the Action Alliance for New Social Media, has published a practical guide titled ‘Free Knowledge’? Among other things, the guide introduces OpenStreetMap, and highlights various resources and ways to contribute to OSM.

OSM in the media

  • In an interview with Heise, OSM contributor Bastian Greshake Tzovaras talked about how OpenStreetMap differs from commercial map providers and which niche OSM fills.
  • Keith Storm explained his ‘Run Greenville Project‘, a personal project to run every road and trail in Greenville County, South Carolina, USA, using the Wandrer app, which relies on OpenStreetMap data. He shared various remarkable experiences from the project, including getting featured by a local news station, becoming involved in a dispute with locals who were not particularly fond of strangers, discovering various historical sites, being swarmed by unidentified animals that eventually led him to undergo a full series of rabies vaccinations, and even encountering traces of crime scenes.

Other “geo” things

  • Nigeria’s crude oil brings prosperity, but also environmental destruction and poverty. The book Black Gold: a blessing or a curse?, by Igbanibo Kubulaemugh Divine, used satellite data and real-life examples to reveal this downside.
  • Through the UN Maps Learning Hub, UN Mappers is offering a self-training platform accessible to anyone and have released a new free QGIS training course.

Upcoming Events

Country Where Venue What When
Hochschule Rhein-Sieg OSM auf der FrOSCon 2026 in Sankt Augustin 2026-08-15 – 2026-08-16
Hannover Hannover Congress Centrum OSM auf der Maker Faire Hannover 2026 2026-08-15 – 2026-08-16
Stadt- und Waagenmuseum Oschatz Kartenwerkstatt Oschatz 2026-08-16
OSM Chennai Mapping Party – Tambaram Market 2026-08-16
Braunschweig Stratum 0 Braunschweiger Mappertreffen im Stratum 0 Hackerspace 2026-08-18
Missing Maps London Mid-Month for Advanced Mappers (no training provided) (Online) [eng] 2026-08-18
Magdeburg Netz39 e.V. , Leibnizstraße 32, 39104 Magdeburg 3. OSM Stammtisch Magdeburg 2026-08-18
Bonn Dotty’s 203. OSM-Stammtisch Bonn 2026-08-18
Chemnitz Kaffeesatz, Chemnitz OSM-Stammtisch Chemnitz 2026-08-18
Derby The Brunswick, Railway Terrace, Derby East Midlands pub meet-up 2026-08-18
Online Lüneburger Mappertreffen (online) 2026-08-18
Karlsruhe Vogelbräu Karlsruhe Stammtisch Karlsruhe 2026-08-19
Amsterdam TomTom HQ Maptime Amsterdam: 2026 Summertime Maptime 2026-08-20
Potsdam MachBar Potsdamer Mappertreffen × 218. OSM-Stammtisch Berlin-Brandenburg 2026-08-21
Stadtgebiet Bremen Online und im Hackerspace Bremen Bremer Mappertreffen 2026-08-24
Berlin Online OSM-Verkehrswende #78 2026-08-25
Düsseldorf Online bei https://meet.jit.si/OSM-DUS-2026 Düsseldorfer OpenStreetMap-Treffen (online) 2026-08-26
Würzburg FabLab Würzburg Würzburger OSM-Treffen 2026-08-26
Wien Schlupfwinkel (Kleine Neugasse 10, 1040 Wien) 79. Wiener OSM-Stammtisch 2026-08-26
OpenStreetMap West Bengal Mapping Party + AnkushTheHero Day 2026-08-27
Cité Descartes State of the Map 2026 2026-08-28 – 2026-08-30
Essen Verkehrs- und Umweltzentrum Essen OSM-Treffen 2026-08-28
Hannover Kuriosum OSM-Stammtisch Hannover 2026-08-31
Hannover Kuriosum OSM-Stammtisch Hannover 2026-08-31
Heidelberg DEZERNAT#16 Rhein-Neckar OSM Treffen 2026-08-31

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, Nakaner, Raquel Dezidério Souto, Strubbl, Ted Johnson, Andrew Davidson, barefootstache, derFred.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

Saturday, 15. August 2026

OpenStreetMap User's Diaries

New Cams

New flock alprs are appearing in neighborhoods near where I go to college. This is scary, do your part.

  • ᵈⁱˢᵗᵃⁿᶜᵉᵈ

New flock alprs are appearing in neighborhoods near where I go to college. This is scary, do your part.

  • ᵈⁱˢᵗᵃⁿᶜᵉᵈ

Learning Path

I’m undergoing the learning path “Open Mapping Essentials” on HOT´s learning centre. In the process I have contributed by mapping local businesses and housing buildings in Managua. I also added a few rural roads in the Esteli area. All my changes are based on local knowledge of the areas. I am looking forward to contributing to the OSM and HOT communities.

I’m undergoing the learning path “Open Mapping Essentials” on HOT´s learning centre. In the process I have contributed by mapping local businesses and housing buildings in Managua. I also added a few rural roads in the Esteli area. All my changes are based on local knowledge of the areas. I am looking forward to contributing to the OSM and HOT communities.

Friday, 14. August 2026

OpenStreetMap User's Diaries

Tagging for the Unhoused

Hi guys.

I would like to emphasize the benefit that the micromapping of certain features can contribute to unhoused communities. Of course, there still needs to be more awareness of OSM within these communities, but the data being there is great for the future and making the map more useful.

Tagging if the seats on benches are separated or not allows people to know where they are

Hi guys.

I would like to emphasize the benefit that the micromapping of certain features can contribute to unhoused communities. Of course, there still needs to be more awareness of OSM within these communities, but the data being there is great for the future and making the map more useful.

Tagging if the seats on benches are separated or not allows people to know where they are able to lay down and thus sleep if they don’t have access to other places to sleep. The tag seats:separated=yes/no is used for this purpose. Ive been adding this to every bench I map. Tagging benches that are not separated is just as important as tagging benches that are.

Drinking water is needed for all humans to live. Knowing where the nearest water fountain is, or the nearest convenience store that will let you fill up a water bottle from their fountain drink dispensers, can be super useful and help when times are tough. Consider looking out for drinking fountains at parks and other public places.

Hope you got something from this, happy mapping and I hope you have a nice day.

Wednesday, 12. August 2026

OpenStreetMap User's Diaries

It's Been 1 Year...

On August 12th, 2025, I made my first edit to OpenStreetMap. It has now been exactly one year since I began editing. Here are some of the coolest things I’ve done in my relatively small amount of time spent on this hobby:

  • 3,095 changesets

  • 226486 contributions

  • Added a “surface=” tag to every primary road, trunk road, and

On August 12th, 2025, I made my first edit to OpenStreetMap. It has now been exactly one year since I began editing. Here are some of the coolest things I’ve done in my relatively small amount of time spent on this hobby:

  • 3,095 changesets

  • 226486 contributions

  • Added a “surface=” tag to every primary road, trunk road, and motorway in Virginia

  • Made changes in 64 countries

  • Procrastinated mountains of homework

It felt like this year went by so fast. I still remember the moment I discovered OpenStreetMap and how I got instantly addicted.

I hope to be an active contributor for years to come and meet tons of mappy people like me!