Style | Standard • Cards

OpenStreetMap Blogs

Wednesday, 18. November 2026

Florian Lohoff

OpenStreetmap RouteQA refresh

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

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

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

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

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

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

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

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

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

Some stats for a typical run:

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

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

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

So here some Screenshots:

Tuesday, 17. November 2026

OpenStreetMap User's Diaries

OSMLondon at The Volunteer pub!

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

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

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

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

OSMLondon at the volunteer (not quite during peak crowdedness)

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

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

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

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

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

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

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

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

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


Cima Conturines

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

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

This other name is mentioned in Wikipedia English and Italian :

en.wikipedia.org/wiki/Piz_dles_Cunturines

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

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

This other name is mentioned in Wikipedia English and Italian :

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


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

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

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

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

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

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

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

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


osm2pgsql

Happy Birthday osm2pgsql!

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

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

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

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

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


OpenStreetMap User's Diaries

Když potoky pod Kletí vysychají

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

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

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

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

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

Odkazy

O tématu vody v krajině jsem psal

Monday, 16. November 2026

OpenStreetMap User's Diaries

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

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

♦

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

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

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

Native Mappers First Meeting at HNBGU

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

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

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

Connecting Local Mapping with Global Opportunities

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

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

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

Students Taking the Lead

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

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

From Training to Community Mapping

The proposed activities include:

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

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

Starting Locally, Connecting Globally

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

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

Map Local. Think Global.

Learn • Map • Research • Serve

Website: https://nativemappers.github.io/

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

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


Mapeando bairros de Aratiba - RS

♦

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

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

Mapa

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

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


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

History

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

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

History

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

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

The issue

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

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

Mass remove the 3dShapes source tag?

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

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

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


OpenStreetMap Blog

Call for SotM 2027 logo designs

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

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

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

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

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

Contest guidelines

The logo design should:

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

Call process:

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

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

How to enter:

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

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

Winner selection:

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

Looking for some inspiration?

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

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

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

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

Sunday, 15. November 2026

OpenStreetMap User's Diaries

service=parking_aisle

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

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

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

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


OpenStreetMap Blog

Announcing SotM 2027 in Bogota

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

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

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

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

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

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

SotM Organising Committee

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

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

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


OpenStreetMap User's Diaries

Capitole du Libre 2026

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

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


Flow of the River Ilagan

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

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

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

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

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

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

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

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

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

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


Tweaked Every-Door editor a bit

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

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

Anyways, 2 nights later, achievements include:

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

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

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


weeklyOSM

weeklyOSM 851

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

05/11/2026-11/11/2026

Mapping

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

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

Mapping campaigns

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

Community

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

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

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

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

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

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

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

OpenStreetMap Foundation

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

Local chapter news

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

Events

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

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

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

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

Education

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

OSM research

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

Maps

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

OSM in action

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

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

Software

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

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

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

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

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

Programming

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

Releases

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

Other “geo” things

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

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

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

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

Upcoming Events

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

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

Saturday, 14. November 2026

OpenStreetMap User's Diaries

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

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

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

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

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

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

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

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

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

¿En qué consistió mi participación?

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

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

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

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

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

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

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

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

Lo que me dejó esta experiencia

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

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

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

Una línea de trabajo que quiero continuar

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

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

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

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

Lizette Adriana Llamas Escamilla

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

Prevención Total Protección Civil 4.0

Sentinel-2 в ложных цветах в JOSM бесплатно через Copernicus

Если вы картируете сельскую местность, вам знакома проблема: снимки Bing или Esri старые, в облаках или просто не показывают, асфальтирована дорога или грунтовая. Sentinel-2 во многом решает эту проблему. Это бесплатные спутниковые снимки, которые обновляются каждые несколько дней, с разрешением 10 м и инфракрасными каналами, невидимыми глазу.

В композиции ложных цветов (каналы B8, B4 и

Если вы картируете сельскую местность, вам знакома проблема: снимки Bing или Esri старые, в облаках или просто не показывают, асфальтирована дорога или грунтовая. Sentinel-2 во многом решает эту проблему. Это бесплатные спутниковые снимки, которые обновляются каждые несколько дней, с разрешением 10 м и инфракрасными каналами, невидимыми глазу.

В композиции ложных цветов (каналы B8, B4 и B3) растительность становится красной, а асфальт выглядит тёмным и контрастным. Асфальтированные дороги, пересекающие кустарник или поля, видны очень отчётливо.

Sentinel-2 в ложных цветах в JOSM: асфальтированная дорога видна как тёмная чёткая линия, растительность красная

Sentinel-2 в ложных цветах в JOSM, сельская местность штата Сеара, Бразилия. Содержит изменённые данные Copernicus Sentinel (2026). Изображение: Wikimedia Commons, CC BY-SA 4.0.

В этом руководстве я покажу, как добавить этот слой в JOSM с помощью бесплатного сервиса Copernicus Data Space Ecosystem Европейского союза.

Важное ограничение: 10 м на пиксель подходит для шоссе, широких грунтовых дорог, воды, растительности, землепользования и гарей. Для зданий и узких городских улиц это не подходит.


1. Создайте аккаунт Copernicus Data Space

  1. Откройте https://dataspace.copernicus.eu и нажмите Login → Register.
  2. Заполните форму и подтвердите e-mail.

Аккаунт бесплатный и включает ежемесячную квоту обработки, которой хватает для обычной работы в JOSM.


2. Создайте конфигурацию и получите свой ID

JOSM не обращается к Copernicus Browser напрямую. Он использует WMS-сервис, который настраивается один раз.

  1. Откройте https://shapps.dataspace.copernicus.eu/dashboard/ под тем же аккаунтом.
  2. В боковом меню откройте Configuration Utility.
  3. Нажмите New configuration.
  4. Задайте имя (например, JOSM) и в поле Create configuration based on выберите Simple Sentinel-2 L2A template.
  5. Нажмите Create configuration.

Не используйте другие шаблоны Sentinel-2. CC Europe покрывает только Европу, а 120 m Mosaic слишком грубый. «L2A» означает снимки с атмосферной коррекцией.

Конфигурация уже содержит несколько готовых слоёв. На левой панели, в разделе Service endpoints, указан ID конфигурации — код вида xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Скопируйте этот ID: он понадобится в URL для JOSM.

Внимание к названиям: слой «False color» из Copernicus Browser в шаблоне называется Color Infrared (vegetation), его ID — COLOR_INFRARED. Слой False color (urban) — это другая композиция (B12, B11, B4). Всегда проверяйте точный ID в столбце Id вашей конфигурации.


3. Добавьте слой в JOSM

  1. В JOSM откройте Правка → Настройки (F12) → вкладка Подложки (Imagery).
  2. Внизу нажмите + WMS.
  3. Вставьте URL ниже, заменив ВАШ_ID на ID, скопированный на предыдущем шаге:

    https://sh.dataspace.copernicus.eu/ogc/wms/ВАШ_ID?SERVICE=WMS&REQUEST=GetMap&VERSION=1.3.0&LAYERS=COLOR_INFRARED&FORMAT=image/png&TRANSPARENT=TRUE&STYLES=&CRS={proj}&BBOX={bbox}&WIDTH={width}&HEIGHT={height}&TIME=2026-08-01/2026-11-14&MAXCC=30&PRIORITY=leastCC
    
  4. Если JOSM предложит загрузить список слоёв, включите опцию ручного задания сгенерированного WMS URL (Set generated WMS URL manually) и вставьте тот же URL в поле WMS URL.
  5. Задайте имя, например Sentinel-2 Ложные цвета, и подтвердите.
  6. Включите слой через меню Подложка (Imagery).

Быстрый способ: все слои сразу

Если не хочется собирать URL по одному, я написал скрипт, который добавляет все слои вашей конфигурации в меню Imagery JOSM: josm-sentinel2 на GitHub. Перед запуском закройте JOSM.

  • Windows: скачайте josm-sentinel2.bat (Download ZIP или Raw), запустите двойным щелчком и вставьте свой ID. Windows может показать предупреждение SmartScreen, так как файл скачан из интернета.
  • macOS и Linux: скачайте josm-sentinel2.sh и запустите в терминале: bash josm-sentinel2.sh ВАШ_ID

Скрипт спрашивает у Copernicus, какие слои есть в вашей конфигурации, и добавляет только их, с теми же названиями. Бонусные слои (NDWI, NDBI, NIR) появятся, только если вы их создали. Он использует снимки за последние 3 месяца (облачность до 30 %, сначала наименее облачная сцена) и делает резервную копию preferences.xml перед изменением. Повторный запуск обновляет даты без дублирования слоёв. Это обычные текстовые файлы: при желании откройте их в редакторе и проверьте перед запуском.

Что означает каждый параметр

Параметр Назначение
LAYERS=COLOR_INFRARED Какую композицию показывать. Замените на ID другого слоя, чтобы получить другую визуализацию
TIME=2026-08-01/2026-11-14 Диапазон дат используемых снимков. Настройте под нужный период
MAXCC=30 Отбрасывает сцены с облачностью более 30 %
PRIORITY=leastCC Собирает мозаику, отдавая приоритет наименее облачным сценам

Если JOSM игнорирует TIME, MAXCC или PRIORITY: так бывает, когда слой выбран из списка (загрузка слоёв): JOSM строит собственный URL и отбрасывает дополнительные параметры. Надёжнее задать их в самом слое в Configuration Utility: Time range (выберите Relative, например последние 3 месяца, чтобы снимки оставались актуальными), Cloud coverage и Mosaic order (Least cloud coverage).

Совет: создайте две записи с разными датами — одну для сухого сезона и одну для сезона дождей. В засушливых регионах это полностью меняет картину, особенно для водохранилищ и пересыхающих рек.

Частые проблемы

Симптом Вероятная причина Решение
Ошибки тайлов только при сильном отдалении Сервис отклоняет слишком большие области Приблизьте карту. Это нормально
Layer XXX not found ID слоя не совпадает с конфигурацией Проверьте столбец Id в Configuration Utility. Регистр, _ и - имеют значение
B8 is not defined или Failed to evaluate script Скрипт слоя в старом формате Замените скрипт (см. примеры в бонусном разделе)
Смещённое изображение или ошибка координат JOSM в проекции WGS84 (EPSG:4326) Используйте проекцию по умолчанию Mercator (EPSG:3857)
Пустое изображение Нет сцен с облачностью ниже MAXCC % за период Расширьте TIME или увеличьте MAXCC

Чтобы увидеть точную ошибку, щёлкните правой кнопкой по проблемному тайлу → Показать информацию о тайле (Show tile info).

Лицензия

Данные Sentinel открыты (лицензия Copernicus) и могут использоваться для картирования в OSM. Укажите в пакете правок что-то вроде source=Copernicus Sentinel-2.


Бонус: дополнительные слои

Помимо слоёв из шаблона, я создал несколько, которые очень помогают. Чтобы добавить слой, откройте Configuration Utility → New Layer, введите имя (оно станет ID), выберите Source: Sentinel-2 L2A, нажмите на карандаш у Data processing, вставьте скрипт и сохраните.

NDWI: вода

Выделяет водоёмы синим. Отлично подходит для водохранилищ, прудов и рек.

//VERSION=3
// NDWI (McFeeters): (B03 - B08) / (B03 + B08)
function setup() {
  return {
    input: ["B03", "B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndwi = (s.B03 - s.B08) / (s.B03 + s.B08);
  let c = colorBlend(ndwi,
    [-0.8, -0.3, 0.0, 0.2, 0.5],
    [[0.0, 0.5, 0.0], [0.6, 0.8, 0.4], [0.95, 0.95, 0.85], [0.3, 0.6, 1.0], [0.0, 0.0, 0.6]]);
  return [...c, s.dataMask];
}

NDBI: застроенные территории

Выделяет застройку и открытый грунт жёлтым/красным. В засушливых регионах сухая почва тоже даёт высокие значения, поэтому используйте его вместе с ложными цветами.

//VERSION=3
// NDBI: (B11 - B08) / (B11 + B08)
function setup() {
  return {
    input: ["B08", "B11", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndbi = (s.B11 - s.B08) / (s.B11 + s.B08);
  let c = colorBlend(ndbi,
    [-0.5, -0.1, 0.0, 0.1, 0.3],
    [[0.0, 0.3, 0.8], [0.2, 0.7, 0.3], [0.9, 0.9, 0.6], [0.95, 0.6, 0.2], [0.8, 0.1, 0.1]]);
  return [...c, s.dataMask];
}

NIR в оттенках серого: дороги и берега

Только канал B08 (ближний инфракрасный, 10 м). Растительность светлая, а вода и асфальт тёмные. Просто и чётко для отрисовки дорог и берегов рек и водохранилищ. Предложение сообщества, спасибо!

//VERSION=3
// NIR grayscale (B08)
function setup() {
  return {
    input: ["B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let v = 2.5 * s.B08;
  return [v, v, v, s.dataMask];
}

False color (urban): исправленный скрипт

Если слой False color (urban) выдаёт ошибку B8 is not defined, замените его скрипт на этот:

//VERSION=3
// False color (urban): B12, B11, B04
function setup() {
  return {
    input: ["B12", "B11", "B04", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(sample) {
  return [2.5 * sample.B12, 2.5 * sample.B11, 2.5 * sample.B04, sample.dataMask];
}

Какой слой использовать для какого картирования

Чтобы переключить слой в JOSM, достаточно изменить LAYERS= в URL. Имеет смысл создать отдельную запись для каждого часто используемого слоя.

Слой (название в шаблоне) LAYERS= Каналы Лучше всего для
Color Infrared (vegetation), «ложные цвета» COLOR_INFRARED B8, B4, B3 Асфальтированные дороги (тёмные на фоне красной растительности), границы растительности, посевы, прибрежные леса
Natural color (true color) TRUE_COLOR B4, B3, B2 Общий обзор, проверка объектов, открытый грунт, городские территории
False color (urban) COLOR_INFRARED__URBAN_ B12, B11, B4 Городская и застроенная территория. Помогает отличить асфальт от грунтовки
Vegetation Index - NDVI VEGETATION_INDEX (B8−B4)/(B8+B4) landuse=farmland, natural=wood/scrub, вырубки, круговое орошение
NDWI (бонус) NDWI (B3−B8)/(B3+B8) natural=water: водохранилища, пруды, широкие реки, поймы
NDBI (бонус) NDBI (B11−B8)/(B11+B8) landuse=residential/industrial, рост городов, новые посёлки
NIR в оттенках серого (бонус) NIR B8 Отрисовка дорог, берегов и границ растительности с максимальным контрастом
Moisture Index MOISTURE_INDEX (B8A−B11)/(B8A+B11) Водно-болотные угодья (natural=wetland), поймы, орошаемая и сухая растительность
SWIR SWIR B12, B8A, B4 Гари, открытый грунт, карьеры, вода (очень тёмная)
Agriculture AGRICULTURE B11, B8, B2 Границы полей, различие посевов и пастбищ
Geology GEOLOGY B12, B4, B2 Скальные выходы, карьеры, natural=bare_rock
Atmospheric penetration ATMOSPHERIC_PENETRATION B12, B11, B8A Дни с дымкой или дымом, когда естественные цвета плохие
Bathymetric BATHYMETRIC B4, B3, B1 Побережье, рифы, отмели на мелководье. Использует B1 (60 м), поэтому изображение более размытое: не используйте для точной отрисовки

Моя любимая комбинация: ложные цвета для дорог и растительности, NDWI для воды и естественные цвета для проверки. Для водохранилищ в засушливых регионах сравните снимок сезона дождей со снимком сухого сезона и картируйте обычный уровень воды (intermittent=yes, если водоём пересыхает каждый год).

Удачного картирования!

Эта запись также доступна на португальском, английском, французском и испанском.


Sentinel-2 en falso color en JOSM, gratis, con Copernicus

Si mapeas zonas rurales, conoces el problema: las imágenes de Bing o Esri son antiguas, tienen nubes o simplemente no muestran si un camino está asfaltado o es de tierra. Sentinel-2 resuelve buena parte de esto. Son imágenes satelitales gratuitas, actualizadas cada pocos días, con 10 m de resolución y bandas infrarrojas que el ojo no ve.

En la composición de falso color (bandas B8, B4 y

Si mapeas zonas rurales, conoces el problema: las imágenes de Bing o Esri son antiguas, tienen nubes o simplemente no muestran si un camino está asfaltado o es de tierra. Sentinel-2 resuelve buena parte de esto. Son imágenes satelitales gratuitas, actualizadas cada pocos días, con 10 m de resolución y bandas infrarrojas que el ojo no ve.

En la composición de falso color (bandas B8, B4 y B3), la vegetación se ve roja y el asfalto aparece oscuro y muy contrastado. Las carreteras pavimentadas que atraviesan el monte o los cultivos se destacan muchísimo.

Sentinel-2 en falso color en JOSM: la carretera asfaltada aparece como una línea oscura y nítida y la vegetación en rojo

Sentinel-2 en falso color en JOSM, zona rural de Ceará, Brasil. Contiene datos Copernicus Sentinel modificados (2026). Imagen: Wikimedia Commons, CC BY-SA 4.0.

En este tutorial muestro cómo añadir esta capa a JOSM usando el servicio gratuito Copernicus Data Space Ecosystem de la Unión Europea.

Limitación importante: 10 m por píxel sirve para carreteras, caminos rurales anchos, agua, vegetación, uso del suelo y áreas quemadas. No sirve para edificios ni para calles estrechas dentro de la ciudad.


1. Crea una cuenta en Copernicus Data Space

  1. Entra en https://dataspace.copernicus.eu y haz clic en Login → Register.
  2. Completa el registro y confirma tu correo.

La cuenta es gratuita e incluye una cuota mensual de procesamiento, suficiente para mapear normalmente en JOSM.


2. Crea la configuración y obtén tu ID

JOSM no accede directamente al Copernicus Browser. Usa un servicio WMS que configuras una sola vez.

  1. Entra en https://shapps.dataspace.copernicus.eu/dashboard/ con la misma cuenta.
  2. En el menú lateral, abre Configuration Utility.
  3. Haz clic en New configuration.
  4. Ponle un nombre (p. ej. JOSM) y, en Create configuration based on, elige Simple Sentinel-2 L2A template.
  5. Haz clic en Create configuration.

No uses las otras plantillas de Sentinel-2. CC Europe solo cubre Europa y el 120 m Mosaic tiene una resolución demasiado baja. “L2A” significa imagen con corrección atmosférica.

La configuración ya trae varias capas listas. En el panel izquierdo, en Service endpoints, aparece el ID de la configuración, un código con el formato xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Copia ese ID, porque va en la URL de JOSM.

Ojo con los nombres: la capa “False color” del Copernicus Browser se llama Color Infrared (vegetation) en la plantilla, con ID COLOR_INFRARED. La capa False color (urban) es otra composición (B12, B11, B4). Revisa siempre el ID exacto en la columna Id de tu configuración.


3. Añade la capa a JOSM

  1. En JOSM, abre Editar → Preferencias (F12) → pestaña Imágenes.
  2. Abajo, haz clic en + WMS.
  3. Pega la URL de abajo, cambiando TU_ID por el ID que copiaste en el paso anterior:

    https://sh.dataspace.copernicus.eu/ogc/wms/TU_ID?SERVICE=WMS&REQUEST=GetMap&VERSION=1.3.0&LAYERS=COLOR_INFRARED&FORMAT=image/png&TRANSPARENT=TRUE&STYLES=&CRS={proj}&BBOX={bbox}&WIDTH={width}&HEIGHT={height}&TIME=2026-08-01/2026-11-14&MAXCC=30&PRIORITY=leastCC
    
  4. Si JOSM pide obtener las capas, marca la opción para establecer manualmente la URL WMS generada (Set generated WMS URL manually) y pega la misma URL en el campo de la URL WMS.
  5. Ponle un nombre, por ejemplo Sentinel-2 Falso Color, y confirma.
  6. Activa la capa desde el menú Imágenes.

Atajo: todas las capas de una vez

Si prefieres no armar las URL una por una, hice un script que añade todas las capas de tu configuración al menú Imágenes de JOSM: josm-sentinel2 en GitHub. Cierra JOSM antes de ejecutarlo.

  • Windows: descarga josm-sentinel2.bat (Download ZIP o Raw), haz doble clic y pega tu ID. Windows puede mostrar un aviso de SmartScreen por ser un archivo descargado.
  • macOS y Linux: descarga josm-sentinel2.sh y ejecútalo en una terminal: bash josm-sentinel2.sh TU_ID

El script le pregunta a Copernicus qué capas existen en tu configuración y añade solo esas, con los nombres que tienen allí. Las capas extra (NDWI, NDBI, NIR) solo aparecen si las creaste. Usa imágenes de los últimos 3 meses (hasta 30 % de nubes, primero la escena menos nublada) y hace una copia de preferences.xml antes de modificarlo. Si lo vuelves a ejecutar, actualiza las fechas sin duplicar las capas. Son archivos de texto: puedes abrirlos en un editor para revisarlos antes.

Qué hace cada parámetro

Parámetro Qué hace
LAYERS=COLOR_INFRARED Qué composición mostrar. Cámbialo por el ID de otra capa para tener otra visualización
TIME=2026-08-01/2026-11-14 Rango de fechas de las imágenes usadas. Ajústalo al período que quieras
MAXCC=30 Descarta escenas con más del 30 % de nubes
PRIORITY=leastCC Arma el mosaico priorizando las escenas con menos nubes

Si JOSM ignora TIME, MAXCC o PRIORITY: pasa cuando eliges la capa de la lista (Obtener capas), porque JOSM genera su propia URL y elimina los parámetros extra. La opción más robusta es configurarlos en la propia capa, en el Configuration Utility: Time range (usa Relative, p. ej. últimos 3 meses, para que la imagen se mantenga actualizada), Cloud coverage y Mosaic order (Least cloud coverage).

Consejo: crea dos entradas con fechas distintas, una en la estación seca y otra en la de lluvias. En zonas semiáridas esto cambia por completo lo que se ve, sobre todo embalses y ríos intermitentes.

Problemas comunes

Síntoma Causa probable Solución
Teselas con error solo con zoom alejado El servicio rechaza áreas muy grandes Acércate. Es normal
Layer XXX not found El ID de la capa no coincide con la configuración Revisa la columna Id del Configuration Utility. Mayúsculas, _ y - importan
B8 is not defined o Failed to evaluate script El script de la capa está en el formato antiguo Sustituye el script (ver los ejemplos en la sección extra)
Imagen desplazada o error de coordenadas JOSM en proyección WGS84 (EPSG:4326) Usa la proyección por defecto Mercator (EPSG:3857)
Imagen vacía No hay escenas con menos de MAXCC % de nubes en el período Amplía el rango de TIME o sube MAXCC

Para ver el error exacto, haz clic derecho sobre una tesela con error → Mostrar información de la tesela (Show tile info).

Licencia

Los datos Sentinel son abiertos (licencia Copernicus) y se pueden usar para mapear en OSM. Añade al conjunto de cambios algo como source=Copernicus Sentinel-2.


Extra: capas adicionales

Además de las capas de la plantilla, creé algunas que ayudan mucho. Para añadirlas, ve al Configuration Utility → New Layer, escribe un nombre (se convierte en el ID), elige Source: Sentinel-2 L2A, haz clic en el lápiz de Data processing, pega el script y guarda.

NDWI: agua

Resalta los cuerpos de agua en azul. Ideal para embalses, lagunas y ríos.

//VERSION=3
// NDWI (McFeeters): (B03 - B08) / (B03 + B08)
function setup() {
  return {
    input: ["B03", "B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndwi = (s.B03 - s.B08) / (s.B03 + s.B08);
  let c = colorBlend(ndwi,
    [-0.8, -0.3, 0.0, 0.2, 0.5],
    [[0.0, 0.5, 0.0], [0.6, 0.8, 0.4], [0.95, 0.95, 0.85], [0.3, 0.6, 1.0], [0.0, 0.0, 0.6]]);
  return [...c, s.dataMask];
}

NDBI: áreas construidas

Resalta superficies construidas y suelo desnudo en amarillo/rojo. En zonas semiáridas el suelo seco también sale alto, así que úsalo junto con el falso color.

//VERSION=3
// NDBI: (B11 - B08) / (B11 + B08)
function setup() {
  return {
    input: ["B08", "B11", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndbi = (s.B11 - s.B08) / (s.B11 + s.B08);
  let c = colorBlend(ndbi,
    [-0.5, -0.1, 0.0, 0.1, 0.3],
    [[0.0, 0.3, 0.8], [0.2, 0.7, 0.3], [0.9, 0.9, 0.6], [0.95, 0.6, 0.2], [0.8, 0.1, 0.1]]);
  return [...c, s.dataMask];
}

NIR en escala de grises: carreteras y orillas

Solo la banda B08 (infrarrojo cercano, 10 m). La vegetación se ve clara y el agua y el asfalto oscuros. Simple y nítido para trazar carreteras y orillas de ríos y embalses. Sugerencia de la comunidad, ¡gracias!

//VERSION=3
// NIR grayscale (B08)
function setup() {
  return {
    input: ["B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let v = 2.5 * s.B08;
  return [v, v, v, s.dataMask];
}

False color (urban): script corregido

Si la capa False color (urban) da el error B8 is not defined, sustituye su script por este:

//VERSION=3
// False color (urban): B12, B11, B04
function setup() {
  return {
    input: ["B12", "B11", "B04", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(sample) {
  return [2.5 * sample.B12, 2.5 * sample.B11, 2.5 * sample.B04, sample.dataMask];
}

Qué capa usar para cada tipo de mapeo

Para cambiar de capa en JOSM, solo cambia LAYERS= en la URL. Vale la pena crear una entrada por cada capa que uses a menudo.

Capa (nombre en la plantilla) LAYERS= Bandas Mejor para
Color Infrared (vegetation), el “falso color” COLOR_INFRARED B8, B4, B3 Carreteras asfaltadas (oscuras sobre la vegetación roja), límites de vegetación, cultivos, bosques de ribera
Natural color (true color) TRUE_COLOR B4, B3, B2 Vista general, confirmar qué es cada elemento, suelo desnudo, zonas urbanas
False color (urban) COLOR_INFRARED__URBAN_ B12, B11, B4 Zonas urbanas y construidas. Ayuda a distinguir asfalto de caminos de tierra
Vegetation Index - NDVI VEGETATION_INDEX (B8−B4)/(B8+B4) landuse=farmland, natural=wood/scrub, deforestación, pivotes de riego
NDWI (extra) NDWI (B3−B8)/(B3+B8) natural=water: embalses, lagunas, ríos anchos, zonas inundables
NDBI (extra) NDBI (B11−B8)/(B11+B8) landuse=residential/industrial, expansión urbana, nuevas urbanizaciones
NIR en escala de grises (extra) NIR B8 Trazar carreteras, orillas y límites de vegetación con el máximo contraste
Moisture Index MOISTURE_INDEX (B8A−B11)/(B8A+B11) Humedales (natural=wetland), llanuras inundables, vegetación regada o seca
SWIR SWIR B12, B8A, B4 Áreas quemadas, suelo desnudo, minería, agua (muy oscura)
Agriculture AGRICULTURE B11, B8, B2 Parcelas agrícolas, distinguir cultivos y pastizales
Geology GEOLOGY B12, B4, B2 Afloramientos rocosos, canteras, natural=bare_rock
Atmospheric penetration ATMOSPHERIC_PENETRATION B12, B11, B8A Días con bruma o humo, cuando el color natural se ve mal
Bathymetric BATHYMETRIC B4, B3, B1 Costa, arrecifes, bancos de arena en aguas poco profundas. Usa B1 (60 m), así que es más borrosa: evítala para trazados precisos

Mi combinación favorita: falso color para carreteras y vegetación, NDWI para el agua y color natural para confirmar. Para embalses en zonas semiáridas, compara una imagen de la estación de lluvias con una de la seca y mapea el nivel normal del agua (intermittent=yes si se seca todos los años).

¡Feliz mapeo!

Esta entrada también está disponible en portugués, inglés y francés.


Sentinel-2 en fausses couleurs dans JOSM, gratuitement, via Copernicus

Si vous cartographiez des zones rurales, vous connaissez le problème : l’imagerie Bing ou Esri est ancienne, nuageuse, ou ne permet tout simplement pas de savoir si une route est goudronnée ou en terre. Sentinel-2 règle une bonne partie de ce problème. C’est une imagerie satellite gratuite, mise à jour tous les quelques jours, avec une résolution de 10 m et des bandes infrarouges invisibles à l’

Si vous cartographiez des zones rurales, vous connaissez le problème : l’imagerie Bing ou Esri est ancienne, nuageuse, ou ne permet tout simplement pas de savoir si une route est goudronnée ou en terre. Sentinel-2 règle une bonne partie de ce problème. C’est une imagerie satellite gratuite, mise à jour tous les quelques jours, avec une résolution de 10 m et des bandes infrarouges invisibles à l’œil nu.

Dans la composition fausses couleurs (bandes B8, B4 et B3), la végétation devient rouge et l’asphalte apparaît sombre et bien contrasté. Les routes goudronnées qui traversent la brousse ou les cultures ressortent très nettement.

Sentinel-2 en fausses couleurs dans JOSM : la route goudronnée apparaît comme une ligne sombre et nette, la végétation en rouge

Sentinel-2 en fausses couleurs dans JOSM, zone rurale du Ceará, Brésil. Contient des données Copernicus Sentinel modifiées (2026). Image : Wikimedia Commons, CC BY-SA 4.0.

Ce tutoriel montre comment ajouter cette couche à JOSM avec le service gratuit Copernicus Data Space Ecosystem de l’Union européenne.

Limite importante : 10 m par pixel suffit pour les routes principales, les grandes pistes, l’eau, la végétation, l’occupation du sol et les zones brûlées. Cela ne suffit pas pour les bâtiments ni pour les rues étroites en ville.


1. Créez un compte Copernicus Data Space

  1. Allez sur https://dataspace.copernicus.eu et cliquez sur Login → Register.
  2. Remplissez le formulaire et confirmez votre e-mail.

Le compte est gratuit et inclut un quota mensuel de traitement, suffisant pour cartographier normalement dans JOSM.


2. Créez une configuration et récupérez votre ID

JOSM n’accède pas directement au Copernicus Browser. Il utilise un service WMS que vous configurez une seule fois.

  1. Allez sur https://shapps.dataspace.copernicus.eu/dashboard/ avec le même compte.
  2. Dans le menu latéral, ouvrez Configuration Utility.
  3. Cliquez sur New configuration.
  4. Donnez-lui un nom (ex. : JOSM) et, dans Create configuration based on, choisissez Simple Sentinel-2 L2A template.
  5. Cliquez sur Create configuration.

N’utilisez pas les autres modèles Sentinel-2. CC Europe ne couvre que l’Europe et la 120 m Mosaic est trop grossière. « L2A » signifie une image avec correction atmosphérique.

La configuration contient déjà plusieurs couches prêtes à l’emploi. Dans le panneau de gauche, sous Service endpoints, se trouve l’ID de la configuration, un code du type xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Copiez cet ID, il va dans l’URL de JOSM.

Attention aux noms : la couche « False color » du Copernicus Browser s’appelle Color Infrared (vegetation) dans le modèle, avec l’ID COLOR_INFRARED. La couche False color (urban) est une autre composition (B12, B11, B4). Vérifiez toujours l’ID exact dans la colonne Id de votre configuration.


3. Ajoutez la couche à JOSM

  1. Dans JOSM, ouvrez Édition → Préférences (F12) → onglet Imagerie.
  2. En bas, cliquez sur + WMS.
  3. Collez l’URL ci-dessous en remplaçant VOTRE_ID par l’ID copié à l’étape précédente :

    https://sh.dataspace.copernicus.eu/ogc/wms/VOTRE_ID?SERVICE=WMS&REQUEST=GetMap&VERSION=1.3.0&LAYERS=COLOR_INFRARED&FORMAT=image/png&TRANSPARENT=TRUE&STYLES=&CRS={proj}&BBOX={bbox}&WIDTH={width}&HEIGHT={height}&TIME=2026-08-01/2026-11-14&MAXCC=30&PRIORITY=leastCC
    
  4. Si JOSM propose de récupérer les couches, cochez l’option pour définir manuellement l’URL WMS générée (Set generated WMS URL manually) et collez la même URL dans le champ de l’URL WMS.
  5. Donnez-lui un nom, par exemple Sentinel-2 Fausses couleurs, et validez.
  6. Activez la couche depuis le menu Imagerie.

Raccourci : toutes les couches d’un coup

Si vous ne voulez pas construire les URL une par une, j’ai écrit un script qui ajoute toutes les couches de votre configuration au menu Imagerie de JOSM : josm-sentinel2 sur GitHub. Fermez JOSM avant de le lancer.

  • Windows : téléchargez josm-sentinel2.bat (Download ZIP ou Raw), double-cliquez dessus et collez votre ID. Windows peut afficher un avertissement SmartScreen, car il a été téléchargé.
  • macOS et Linux : téléchargez josm-sentinel2.sh et lancez-le dans un terminal : bash josm-sentinel2.sh VOTRE_ID

Le script demande à Copernicus quelles couches existent dans votre configuration et n’ajoute que celles-ci, avec leurs noms. Les couches bonus (NDWI, NDBI, NIR) n’apparaissent que si vous les avez créées. Il utilise les images des 3 derniers mois (30 % de nuages maximum, scène la moins nuageuse d’abord) et sauvegarde preferences.xml avant de le modifier. Relancez-le plus tard pour mettre à jour les dates sans dupliquer les couches. Ce sont de simples fichiers texte : vous pouvez les ouvrir dans un éditeur pour les vérifier avant.

Ce que fait chaque paramètre

Paramètre Rôle
LAYERS=COLOR_INFRARED La composition à afficher. Remplacez-la par l’ID d’une autre couche pour changer de visualisation
TIME=2026-08-01/2026-11-14 Période des images utilisées. Ajustez selon vos besoins
MAXCC=30 Écarte les scènes avec plus de 30 % de nuages
PRIORITY=leastCC Construit la mosaïque en privilégiant les scènes les moins nuageuses

Si JOSM ignore TIME, MAXCC ou PRIORITY : cela arrive quand la couche est choisie dans la liste (récupération des couches), car JOSM construit sa propre URL et supprime les paramètres supplémentaires. L’option la plus robuste est de les régler sur la couche elle-même dans le Configuration Utility : Time range (choisissez Relative, par ex. les 3 derniers mois, pour garder une image à jour), Cloud coverage et Mosaic order (Least cloud coverage).

Astuce : créez deux entrées avec des dates différentes, une en saison sèche et une en saison des pluies. En zone semi-aride, cela change complètement ce que l’on voit, surtout pour les retenues d’eau et les cours d’eau intermittents.

Problèmes courants

Symptôme Cause probable Solution
Tuiles en erreur seulement en zoom éloigné Le service refuse les zones trop grandes Zoomez. C’est normal
Layer XXX not found L’ID de la couche ne correspond pas à la configuration Vérifiez la colonne Id du Configuration Utility. Majuscules, _ et - comptent
B8 is not defined ou Failed to evaluate script Le script de la couche est dans l’ancien format Remplacez le script (voir les exemples dans la section bonus)
Image décalée ou erreur de coordonnées JOSM en projection WGS84 (EPSG:4326) Utilisez la projection par défaut Mercator (EPSG:3857)
Image vide Aucune scène sous MAXCC % de nuages sur la période Élargissez TIME ou augmentez MAXCC

Pour voir l’erreur exacte, faites un clic droit sur une tuile en erreur → Afficher les informations de la tuile (Show tile info).

Licence

Les données Sentinel sont ouvertes (licence Copernicus) et peuvent être utilisées pour cartographier dans OSM. Ajoutez par exemple source=Copernicus Sentinel-2 à votre groupe de modifications.


Bonus : couches supplémentaires

En plus des couches du modèle, j’en ai créé quelques-unes qui aident beaucoup. Pour en ajouter une, allez dans le Configuration Utility → New Layer, saisissez un nom (il devient l’ID), choisissez Source : Sentinel-2 L2A, cliquez sur le crayon de Data processing, collez le script et enregistrez.

NDWI : l’eau

Met en évidence les plans d’eau en bleu. Idéal pour les retenues, étangs et rivières.

//VERSION=3
// NDWI (McFeeters): (B03 - B08) / (B03 + B08)
function setup() {
  return {
    input: ["B03", "B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndwi = (s.B03 - s.B08) / (s.B03 + s.B08);
  let c = colorBlend(ndwi,
    [-0.8, -0.3, 0.0, 0.2, 0.5],
    [[0.0, 0.5, 0.0], [0.6, 0.8, 0.4], [0.95, 0.95, 0.85], [0.3, 0.6, 1.0], [0.0, 0.0, 0.6]]);
  return [...c, s.dataMask];
}

NDBI : zones bâties

Met en évidence les surfaces bâties et le sol nu en jaune/rouge. En zone semi-aride, le sol sec ressort aussi, donc utilisez-le avec les fausses couleurs.

//VERSION=3
// NDBI: (B11 - B08) / (B11 + B08)
function setup() {
  return {
    input: ["B08", "B11", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndbi = (s.B11 - s.B08) / (s.B11 + s.B08);
  let c = colorBlend(ndbi,
    [-0.5, -0.1, 0.0, 0.1, 0.3],
    [[0.0, 0.3, 0.8], [0.2, 0.7, 0.3], [0.9, 0.9, 0.6], [0.95, 0.6, 0.2], [0.8, 0.1, 0.1]]);
  return [...c, s.dataMask];
}

Proche infrarouge en niveaux de gris : routes et berges

Uniquement la bande B08 (proche infrarouge, 10 m). La végétation est claire, l’eau et l’asphalte sont sombres. Simple et net pour tracer les routes et les berges des rivières et retenues. Suggestion de la communauté, merci !

//VERSION=3
// NIR grayscale (B08)
function setup() {
  return {
    input: ["B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let v = 2.5 * s.B08;
  return [v, v, v, s.dataMask];
}

False color (urban) : script corrigé

Si la couche False color (urban) renvoie l’erreur B8 is not defined, remplacez son script par celui-ci :

//VERSION=3
// False color (urban): B12, B11, B04
function setup() {
  return {
    input: ["B12", "B11", "B04", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(sample) {
  return [2.5 * sample.B12, 2.5 * sample.B11, 2.5 * sample.B04, sample.dataMask];
}

Quelle couche pour quel type de cartographie

Pour changer de couche dans JOSM, modifiez simplement LAYERS= dans l’URL. Il vaut la peine de créer une entrée par couche que vous utilisez souvent.

Couche (nom dans le modèle) LAYERS= Bandes Idéale pour
Color Infrared (vegetation), les « fausses couleurs » COLOR_INFRARED B8, B4, B3 Routes goudronnées (sombres sur la végétation rouge), limites de végétation, cultures, ripisylves
Natural color (true color) TRUE_COLOR B4, B3, B2 Vue d’ensemble, identifier chaque élément, sol nu, zones urbaines
False color (urban) COLOR_INFRARED__URBAN_ B12, B11, B4 Zones urbaines et bâties. Aide à distinguer asphalte et pistes en terre
Vegetation Index - NDVI VEGETATION_INDEX (B8−B4)/(B8+B4) landuse=farmland, natural=wood/scrub, déforestation, pivots d’irrigation
NDWI (bonus) NDWI (B3−B8)/(B3+B8) natural=water : retenues, étangs, grandes rivières, zones inondables
NDBI (bonus) NDBI (B11−B8)/(B11+B8) landuse=residential/industrial, étalement urbain, nouveaux lotissements
Proche infrarouge en niveaux de gris (bonus) NIR B8 Tracer routes, berges et limites de végétation avec un contraste maximal
Moisture Index MOISTURE_INDEX (B8A−B11)/(B8A+B11) Zones humides (natural=wetland), plaines inondables, végétation irriguée ou sèche
SWIR SWIR B12, B8A, B4 Zones brûlées, sol nu, mines, eau (très sombre)
Agriculture AGRICULTURE B11, B8, B2 Parcelles agricoles, distinguer cultures et pâturages
Geology GEOLOGY B12, B4, B2 Affleurements rocheux, carrières, natural=bare_rock
Atmospheric penetration ATMOSPHERIC_PENETRATION B12, B11, B8A Jours de brume ou de fumée, quand les couleurs naturelles sont mauvaises
Bathymetric BATHYMETRIC B4, B3, B1 Littoral, récifs, bancs de sable en eau peu profonde. Utilise B1 (60 m), donc plus flou : à éviter pour un tracé précis

Ma combinaison préférée : fausses couleurs pour les routes et la végétation, NDWI pour l’eau et couleurs naturelles pour vérifier. Pour les retenues en zone semi-aride, comparez une image de saison des pluies avec une de saison sèche et cartographiez le niveau d’eau normal (intermittent=yes si elle s’assèche chaque année).

Bonne cartographie !

Cet article existe aussi en portugais et en anglais.


Sentinel-2 false color in JOSM, for free, via Copernicus

If you map rural areas, you know the problem: Bing or Esri imagery is old, cloudy, or simply doesn’t show whether a road is paved or dirt. Sentinel-2 solves a good part of that. It is free satellite imagery, refreshed every few days, with 10 m resolution and infrared bands the human eye can’t see.

In the false color composite (bands B8, B4 and B3), vegetation turns red and asphalt turns

If you map rural areas, you know the problem: Bing or Esri imagery is old, cloudy, or simply doesn’t show whether a road is paved or dirt. Sentinel-2 solves a good part of that. It is free satellite imagery, refreshed every few days, with 10 m resolution and infrared bands the human eye can’t see.

In the false color composite (bands B8, B4 and B3), vegetation turns red and asphalt turns dark and high-contrast. Paved roads crossing scrubland or farmland really stand out.

Sentinel-2 false color in JOSM: the paved road shows up as a dark, sharp line and vegetation is red

Sentinel-2 false color in JOSM, rural Ceará, Brazil. Contains modified Copernicus Sentinel data (2026). Image: Wikimedia Commons, CC BY-SA 4.0.

This tutorial shows how to add this layer to JOSM using the free Copernicus Data Space Ecosystem service from the European Union.

Important limitation: 10 m per pixel works for highways, wide rural roads, water, vegetation, land use and burned areas. It does not work for buildings or narrow urban streets.


1. Create a Copernicus Data Space account

  1. Go to https://dataspace.copernicus.eu and click Login → Register.
  2. Fill in the form and confirm your email.

The account is free and comes with a monthly processing quota, which is enough for normal mapping in JOSM.


2. Create a configuration and get your ID

JOSM doesn’t talk to the Copernicus Browser directly. It uses a WMS service that you set up once.

  1. Go to https://shapps.dataspace.copernicus.eu/dashboard/ with the same account.
  2. In the side menu, open Configuration Utility.
  3. Click New configuration.
  4. Give it a name (e.g. JOSM) and, under Create configuration based on, choose Simple Sentinel-2 L2A template.
  5. Click Create configuration.

Don’t use the other Sentinel-2 templates. CC Europe only covers Europe and the 120 m Mosaic is too coarse. “L2A” means atmospherically corrected imagery.

The configuration comes with several ready-made layers. In the left panel, under Service endpoints, you’ll find the configuration ID, a code like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Copy this ID, because it goes into the JOSM URL.

Watch the names: the “False color” layer in the Copernicus Browser is called Color Infrared (vegetation) in the template, with ID COLOR_INFRARED. The False color (urban) layer is a different composite (B12, B11, B4). Always check the exact ID in the Id column of your configuration.


3. Add the layer to JOSM

  1. In JOSM, open Edit → Preferences (F12) → Imagery tab.
  2. At the bottom, click + WMS.
  3. Paste the URL below, replacing YOUR_ID with the ID you copied in the previous step:

    https://sh.dataspace.copernicus.eu/ogc/wms/YOUR_ID?SERVICE=WMS&REQUEST=GetMap&VERSION=1.3.0&LAYERS=COLOR_INFRARED&FORMAT=image/png&TRANSPARENT=TRUE&STYLES=&CRS={proj}&BBOX={bbox}&WIDTH={width}&HEIGHT={height}&TIME=2026-08-01/2026-11-14&MAXCC=30&PRIORITY=leastCC
    
  4. If JOSM asks to fetch the layers, tick “Set generated WMS URL manually” and paste the same URL into the WMS URL field.
  5. Give it a name, for example Sentinel-2 False Color, and confirm.
  6. Turn the layer on from the Imagery menu.

Shortcut: all layers at once

If you’d rather not build the URLs one by one, I wrote a script that adds every layer of your configuration to the JOSM Imagery menu: josm-sentinel2 on GitHub. Close JOSM before running it.

  • Windows: download josm-sentinel2.bat (Download ZIP or Raw), double-click it and paste your ID. Windows may show a SmartScreen warning because it was downloaded.
  • macOS and Linux: download josm-sentinel2.sh and run it in a terminal: bash josm-sentinel2.sh YOUR_ID

The script asks Copernicus which layers exist in your configuration and adds only those, with the names they have there. The bonus layers (NDWI, NDBI, NIR) only show up if you created them. It uses imagery from the last 3 months (up to 30% clouds, least cloudy scene first) and backs up preferences.xml before changing it. Run it again later to refresh the dates without duplicating layers. They’re plain text files, so feel free to open them in an editor and check them first.

What each parameter does

Parameter What it does
LAYERS=COLOR_INFRARED Which composite to show. Replace it with another layer ID for a different view
TIME=2026-08-01/2026-11-14 Date range of the images used. Adjust to the period you want
MAXCC=30 Discards scenes with more than 30% cloud cover
PRIORITY=leastCC Builds the mosaic favouring the least cloudy scenes

If JOSM ignores TIME, MAXCC or PRIORITY: this happens when you pick the layer from the list (Get layers), because JOSM builds its own URL and drops extra parameters. A more robust option is to set them on the layer itself in the Configuration Utility: Time range (use Relative, e.g. last 3 months, so the imagery stays current), Cloud coverage and Mosaic order (Least cloud coverage).

Tip: create two entries with different dates, one in the dry season and one in the wet season. In semi-arid regions this completely changes what you see, especially reservoirs and intermittent rivers.

Common problems

Symptom Likely cause Fix
Tile errors only when zoomed out The service refuses very large areas Zoom in. This is normal
Layer XXX not found The layer ID doesn’t match the configuration Check the Id column in the Configuration Utility. Case, _ and - matter
B8 is not defined or Failed to evaluate script The layer script uses the old format Replace the script (see the examples in the bonus section)
Shifted image or coordinate errors JOSM is in WGS84 projection (EPSG:4326) Use the default Mercator (EPSG:3857) projection
Empty image No scene below MAXCC% cloud cover in the period Widen the TIME range or raise MAXCC

To see the exact error, right-click a failed tile → Show tile info.

License

Sentinel data is open (Copernicus license) and can be used for mapping in OSM. Add something like source=Copernicus Sentinel-2 to your changeset.


Bonus: extra layers

Besides the template layers, I created a few that help a lot with mapping. To add one, go to the Configuration Utility → New Layer, enter a name (it becomes the ID), choose Source: Sentinel-2 L2A, click the pencil next to Data processing, paste the script and save.

NDWI: water

Highlights water bodies in blue. Great for reservoirs, ponds and rivers.

//VERSION=3
// NDWI (McFeeters): (B03 - B08) / (B03 + B08)
function setup() {
  return {
    input: ["B03", "B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndwi = (s.B03 - s.B08) / (s.B03 + s.B08);
  let c = colorBlend(ndwi,
    [-0.8, -0.3, 0.0, 0.2, 0.5],
    [[0.0, 0.5, 0.0], [0.6, 0.8, 0.4], [0.95, 0.95, 0.85], [0.3, 0.6, 1.0], [0.0, 0.0, 0.6]]);
  return [...c, s.dataMask];
}

NDBI: built-up areas

Highlights built-up surfaces and bare soil in yellow/red. In semi-arid regions dry soil also scores high, so use it together with false color.

//VERSION=3
// NDBI: (B11 - B08) / (B11 + B08)
function setup() {
  return {
    input: ["B08", "B11", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndbi = (s.B11 - s.B08) / (s.B11 + s.B08);
  let c = colorBlend(ndbi,
    [-0.5, -0.1, 0.0, 0.1, 0.3],
    [[0.0, 0.3, 0.8], [0.2, 0.7, 0.3], [0.9, 0.9, 0.6], [0.95, 0.6, 0.2], [0.8, 0.1, 0.1]]);
  return [...c, s.dataMask];
}

NIR grayscale: roads and shorelines

Just band B08 (near infrared, 10 m). Vegetation is bright, while water and asphalt are dark. Simple and sharp for tracing roads and the edges of rivers and reservoirs. Suggested by the community, thanks!

//VERSION=3
// NIR grayscale (B08)
function setup() {
  return {
    input: ["B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let v = 2.5 * s.B08;
  return [v, v, v, s.dataMask];
}

False color (urban): fixed script

If the False color (urban) layer fails with B8 is not defined, replace its script with this one:

//VERSION=3
// False color (urban): B12, B11, B04
function setup() {
  return {
    input: ["B12", "B11", "B04", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(sample) {
  return [2.5 * sample.B12, 2.5 * sample.B11, 2.5 * sample.B04, sample.dataMask];
}

Which layer to use for each kind of mapping

To switch layers in JOSM, just change LAYERS= in the URL. It’s worth creating one entry for each layer you use often.

Layer (template name) LAYERS= Bands Best for
Color Infrared (vegetation), the “false color” COLOR_INFRARED B8, B4, B3 Paved roads (dark against red vegetation), vegetation edges, crops, riparian forest
Natural color (true color) TRUE_COLOR B4, B3, B2 General overview, checking what each feature is, bare soil, urban areas
False color (urban) COLOR_INFRARED__URBAN_ B12, B11, B4 Urban and built-up areas. Helps tell asphalt from dirt roads
Vegetation Index - NDVI VEGETATION_INDEX (B8−B4)/(B8+B4) landuse=farmland, natural=wood/scrub, deforestation, centre-pivot irrigation
NDWI (bonus) NDWI (B3−B8)/(B3+B8) natural=water: reservoirs, ponds, wide rivers, floodplains
NDBI (bonus) NDBI (B11−B8)/(B11+B8) landuse=residential/industrial, urban sprawl, new subdivisions
NIR grayscale (bonus) NIR B8 Tracing roads, shorelines and vegetation edges with maximum contrast
Moisture Index MOISTURE_INDEX (B8A−B11)/(B8A+B11) Wetlands (natural=wetland), floodplains, irrigated vs. dry vegetation
SWIR SWIR B12, B8A, B4 Burned areas, bare soil, mining, water (very dark)
Agriculture AGRICULTURE B11, B8, B2 Field boundaries, telling crops from pasture
Geology GEOLOGY B12, B4, B2 Rock outcrops, quarries, natural=bare_rock
Atmospheric penetration ATMOSPHERIC_PENETRATION B12, B11, B8A Hazy or smoky days, when natural color looks bad
Bathymetric BATHYMETRIC B4, B3, B1 Coastline, reefs, sandbanks in shallow water. Uses B1 (60 m), so it is blurrier: avoid it for precise tracing

My favourite combo: false color for roads and vegetation, NDWI for water and natural color to double-check. For reservoirs in semi-arid regions, compare a wet-season image with a dry-season one and map the normal water level (intermittent=yes when it dries up every year).

Happy mapping!

This entry is also available in Portuguese.


Sentinel-2 em falsa cor no JOSM, de graça, pelo Copernicus

Quem mapeia no interior do Brasil conhece o problema: a imagem do Bing ou da Esri é antiga, cheia de nuvem ou simplesmente não mostra se aquela estrada é asfaltada ou de terra. O Sentinel-2 resolve boa parte disso. É uma imagem de satélite gratuita, atualizada a cada poucos dias, com 10 m de resolução e com bandas de infravermelho que o olho não vê.

Na composição falsa cor (bandas B8, B4

Quem mapeia no interior do Brasil conhece o problema: a imagem do Bing ou da Esri é antiga, cheia de nuvem ou simplesmente não mostra se aquela estrada é asfaltada ou de terra. O Sentinel-2 resolve boa parte disso. É uma imagem de satélite gratuita, atualizada a cada poucos dias, com 10 m de resolução e com bandas de infravermelho que o olho não vê.

Na composição falsa cor (bandas B8, B4 e B3), a vegetação fica vermelha e o asfalto fica escuro e bem contrastado. Rodovias pavimentadas cortando a caatinga ou a lavoura ficam muito evidentes.

Sentinel-2 em falsa cor no JOSM: a rodovia asfaltada aparece como uma linha escura e nítida, e a vegetação em vermelho

Sentinel-2 em falsa cor no JOSM, no interior do Ceará. Contém dados Copernicus Sentinel modificados (2026). Imagem: Wikimedia Commons, CC BY-SA 4.0.

Neste tutorial mostro como colocar essa camada no JOSM usando o serviço gratuito do Copernicus Data Space Ecosystem, da União Europeia.

Limitação importante: 10 m por pixel serve para rodovias, estradas vicinais largas, água, vegetação, uso do solo e áreas queimadas. Não serve para prédios nem para ruas estreitas dentro da cidade.


1. Crie uma conta no Copernicus Data Space

  1. Acesse https://dataspace.copernicus.eu e clique em Login → Register.
  2. Preencha o cadastro e confirme o e-mail.

A conta é gratuita e dá direito a uma cota mensal de processamento, que é suficiente para mapear normalmente no JOSM.


2. Crie a configuração e pegue o seu ID

O JOSM não acessa o Copernicus Browser diretamente. Ele acessa um serviço WMS que você configura uma única vez.

  1. Entre em https://shapps.dataspace.copernicus.eu/dashboard/ com a mesma conta.
  2. No menu lateral, abra Configuration Utility.
  3. Clique em New configuration.
  4. Dê um nome (ex.: JOSM) e, em Create configuration based on, escolha Simple Sentinel-2 L2A template.
  5. Clique em Create configuration.

Não use os outros templates de Sentinel-2. O CC Europe cobre só a Europa e o 120 m Mosaic tem resolução baixa demais. “L2A” significa imagem com correção atmosférica.

A configuração já vem com várias camadas prontas. No painel da esquerda, em Service endpoints, aparece o ID da configuração, um código no formato xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Copie esse ID, porque ele vai na URL do JOSM.

Atenção ao nome: a “False color” do Copernicus Browser aparece no template como Color Infrared (vegetation), com ID COLOR_INFRARED. A camada False color (urban) é outra composição (B12, B11, B4). Confira sempre o ID exato na coluna Id da sua configuração.


3. Adicione a camada ao JOSM

  1. No JOSM, abra Editar → Preferências (F12) → aba Imagens.
  2. Na parte de baixo, clique em + WMS.
  3. Cole a URL abaixo, trocando SEU_ID pelo ID copiado no passo anterior:

    https://sh.dataspace.copernicus.eu/ogc/wms/SEU_ID?SERVICE=WMS&REQUEST=GetMap&VERSION=1.3.0&LAYERS=COLOR_INFRARED&FORMAT=image/png&TRANSPARENT=TRUE&STYLES=&CRS={proj}&BBOX={bbox}&WIDTH={width}&HEIGHT={height}&TIME=2026-08-01/2026-11-14&MAXCC=30&PRIORITY=leastCC
    
  4. Se o JOSM pedir para buscar as camadas, marque “Definir URL WMS gerada manualmente” e cole a mesma URL no campo da URL WMS.
  5. Dê um nome, por exemplo Sentinel-2 Falsa Cor, e confirme.
  6. Ative a camada pelo menu Imagens.

Atalho: todas as camadas de uma vez

Se preferir não montar URL por URL, fiz um script que adiciona todas as camadas da sua configuração ao menu Imagens do JOSM: josm-sentinel2 no GitHub. Feche o JOSM antes de rodar.

  • Windows: baixe o josm-sentinel2.bat (botão Download ZIP ou Raw), dê dois cliques e cole o seu ID. O Windows pode mostrar um aviso do SmartScreen por ser um arquivo baixado.
  • macOS e Linux: baixe o josm-sentinel2.sh e rode no terminal: bash josm-sentinel2.sh SEU_ID

O script pergunta ao Copernicus quais camadas existem na sua configuração e adiciona só essas, com os nomes que estão lá. As camadas do bônus (NDWI, NDBI, NIR) só aparecem se você as tiver criado. Ele usa as imagens dos últimos 3 meses (até 30% de nuvens, cena menos nublada primeiro) e faz backup do preferences.xml antes de mexer. Rodando de novo, atualiza as datas sem duplicar as camadas. São arquivos de texto: abra num editor para conferir antes de rodar, se quiser.

O que significa cada parâmetro

Parâmetro O que faz
LAYERS=COLOR_INFRARED Qual composição mostrar. Troque pelo ID de outra camada para ter outra visualização
TIME=2026-08-01/2026-11-14 Intervalo de datas das imagens usadas. Ajuste para o período que quiser
MAXCC=30 Descarta cenas com mais de 30% de nuvens
PRIORITY=leastCC Monta o mosaico priorizando as cenas com menos nuvens

Se o JOSM ignorar TIME, MAXCC ou PRIORITY: isso acontece quando a camada é escolhida na lista (Obter camadas), porque o JOSM monta a própria URL e descarta os parâmetros extras. A alternativa mais robusta é configurar isso na própria camada, no Configuration Utility: Time range (use Relative, por exemplo últimos 3 meses, para a imagem não ficar desatualizada), Cloud coverage e Mosaic order (Least cloud coverage).

Dica: crie duas entradas com datas diferentes, uma na estação seca e outra na chuvosa. No semiárido isso muda completamente o que aparece, principalmente açudes e rios intermitentes.

Problemas comuns

Sintoma Causa provável Solução
Tiles com erro só com zoom afastado O serviço recusa áreas muito grandes Aproxime o mapa. É normal
Layer XXX not found O ID da camada não bate com a configuração Confira na coluna Id do Configuration Utility. Maiúsculas, _ e - fazem diferença
B8 is not defined ou Failed to evaluate script O script da camada está no formato antigo Substitua o script (veja os exemplos no bônus)
Imagem deslocada ou com erro de coordenadas JOSM em projeção WGS84 (EPSG:4326) Use a projeção padrão Mercator (EPSG:3857)
Imagem vazia Não há cena com menos de MAXCC% de nuvens no período Aumente o intervalo de TIME ou o valor de MAXCC

Para ver o erro exato, clique com o botão direito sobre um tile com erro → Mostrar informações do tile.

Licença

Os dados Sentinel são abertos (licença Copernicus) e podem ser usados para mapear no OSM. Coloque no changeset algo como source=Copernicus Sentinel-2.


Bônus: camadas extras

Além das camadas do template, criei algumas que ajudam bastante no mapeamento. Para adicionar, vá ao Configuration Utility → New Layer, dê o nome (que vira o ID), escolha Source: Sentinel-2 L2A, clique no lápis de Data processing, cole o script e salve.

NDWI: água

Realça corpos d’água em azul. É ótimo para açudes, lagoas e rios.

//VERSION=3
// NDWI (McFeeters): (B03 - B08) / (B03 + B08)
function setup() {
  return {
    input: ["B03", "B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndwi = (s.B03 - s.B08) / (s.B03 + s.B08);
  let c = colorBlend(ndwi,
    [-0.8, -0.3, 0.0, 0.2, 0.5],
    [[0.0, 0.5, 0.0], [0.6, 0.8, 0.4], [0.95, 0.95, 0.85], [0.3, 0.6, 1.0], [0.0, 0.0, 0.6]]);
  return [...c, s.dataMask];
}

NDBI: área construída

Realça superfícies construídas e solo exposto em amarelo/vermelho. No semiárido, o solo seco também sai alto, então use junto com a falsa cor.

//VERSION=3
// NDBI: (B11 - B08) / (B11 + B08)
function setup() {
  return {
    input: ["B08", "B11", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let ndbi = (s.B11 - s.B08) / (s.B11 + s.B08);
  let c = colorBlend(ndbi,
    [-0.5, -0.1, 0.0, 0.1, 0.3],
    [[0.0, 0.3, 0.8], [0.2, 0.7, 0.3], [0.9, 0.9, 0.6], [0.95, 0.6, 0.2], [0.8, 0.1, 0.1]]);
  return [...c, s.dataMask];
}

NIR em tons de cinza: estradas e margens

Só a banda B08 (infravermelho próximo, 10 m). A vegetação fica clara, e a água e o asfalto ficam escuros. Simples e nítido para traçar estradas e margens de rios e açudes. Sugestão da comunidade, obrigado!

//VERSION=3
// NIR grayscale (B08)
function setup() {
  return {
    input: ["B08", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(s) {
  let v = 2.5 * s.B08;
  return [v, v, v, s.dataMask];
}

False color (urban): script corrigido

Se a camada False color (urban) der erro B8 is not defined, substitua o script por este:

//VERSION=3
// False color (urban): B12, B11, B04
function setup() {
  return {
    input: ["B12", "B11", "B04", "dataMask"],
    output: { bands: 4 }
  };
}

function evaluatePixel(sample) {
  return [2.5 * sample.B12, 2.5 * sample.B11, 2.5 * sample.B04, sample.dataMask];
}

Qual camada usar para cada tipo de mapeamento

Para trocar de camada no JOSM, mude só o LAYERS= na URL. Vale criar uma entrada para cada camada que você usar com frequência.

Camada (nome no template) LAYERS= Bandas Melhor para
Color Infrared (vegetation), a “falsa cor” COLOR_INFRARED B8, B4, B3 Estradas asfaltadas (escuras contra a vegetação vermelha), limites de vegetação, lavouras, matas ciliares
Natural color (true color) TRUE_COLOR B4, B3, B2 Visão geral, conferir o que é cada feição, solo exposto, áreas urbanas
False color (urban) COLOR_INFRARED__URBAN_ B12, B11, B4 Áreas urbanas e construídas. Ajuda a separar asfalto de estrada de terra
Vegetation Index - NDVI VEGETATION_INDEX (B8−B4)/(B8+B4) landuse=farmland, natural=wood/scrub, desmatamento, pivôs de irrigação
NDWI (bônus) NDWI (B3−B8)/(B3+B8) natural=water: açudes, lagoas, rios largos, áreas alagáveis
NDBI (bônus) NDBI (B11−B8)/(B11+B8) landuse=residential/industrial, expansão urbana, novos loteamentos
NIR em tons de cinza (bônus) NIR B8 Traçar estradas, margens de água e limites de vegetação com contraste máximo
Moisture Index MOISTURE_INDEX (B8A−B11)/(B8A+B11) Áreas úmidas (natural=wetland), várzeas, vegetação irrigada x seca
SWIR SWIR B12, B8A, B4 Áreas queimadas, solo exposto, mineração, água (fica bem escura)
Agriculture AGRICULTURE B11, B8, B2 Talhões agrícolas, diferenciar culturas e pastagens
Geology GEOLOGY B12, B4, B2 Afloramentos rochosos, pedreiras, natural=bare_rock
Atmospheric penetration ATMOSPHERIC_PENETRATION B12, B11, B8A Dias com névoa ou fumaça, quando a cor natural fica ruim
Bathymetric BATHYMETRIC B4, B3, B1 Litoral, recifes, bancos de areia em água rasa. Usa a B1 (60 m), então fica mais borrada: evite para traçado preciso

Minha combinação preferida: falsa cor para estradas e vegetação, NDWI para água e cor natural para conferir. Para açudes no semiárido, compare uma imagem da estação chuvosa com uma da seca e mapeie o nível normal da água (intermittent=yes quando secar todo ano).

Bom mapeamento!

Thursday, 27. October 2022

Florian Lohoff

josm plbuildings for Northrhine-Westfalia

For a long time building imports in Northrhine-Westfalia or NRW was a hassle. The only source would be a WMS server and some people wrote software to convert the WMS tiles back to some useful vector informations and merge into the josm dataset. This solution was pretty fragile and my impression is that its basically unmaintained, although it still works for me.

For a long time i was look

For a long time building imports in Northrhine-Westfalia or NRW was a hassle. The only source would be a WMS server and some people wrote software to convert the WMS tiles back to some useful vector informations and merge into the josm dataset. This solution was pretty fragile and my impression is that its basically unmaintained, although it still works for me.

For a long time i was looking for a solution to use something like generic WFS in JOSM with a rule based merging of tags and or geometries (Which geometries to use nodes from, snap distance etc). Nothing like this popped up in the last 10 years.

So i had a look yesterday and found the plbuildings plugin which just needs the right server component to serve OSM XML files.

So i quickly hacked a server component to server the NRW Open Data Shape dataset.

When you install the plbuildings plugin into josm, and change the URL to:

plbuildings.server_url=https://osm.zz.de/plbuildingsnrw/v1/

You will be able to import building outlines from the Hausumringe NRW dataset. I am not that happy with the amount of nodes this dataset contains, or the usability with the plbuildings plugin, but its a start.

Also this will most like break horribly if you have real multipolygon buildings e.g. with a hole in the middle. This is not yet implemented at least on the server side as it would require to serve back a relation. I have no idea whether the plbuildings plugin supports this.


OpenStreetMap User's Diaries

Emplacement erroné du sommet du Rocher de la Tête Noire (1688)

En se fiant aux courbes de niveaux entourant le sommet virtuel du Rocher de la Tête Noire (1688, Valais, Suisse) sur la carte OpenStreetMap on peut constater que le point (noeud ?) du sommet est mal placé, et qu’il devrait se trouver à environ 170 m plus loin au nord-est, à l’intérieur du cercle formé par la courbe 1680, seule zone 1680-1690 s’apparentant à un mont ou un sommet ; c’est d’ailleur

En se fiant aux courbes de niveaux entourant le sommet virtuel du Rocher de la Tête Noire (1688, Valais, Suisse) sur la carte OpenStreetMap on peut constater que le point (noeud ?) du sommet est mal placé, et qu’il devrait se trouver à environ 170 m plus loin au nord-est, à l’intérieur du cercle formé par la courbe 1680, seule zone 1680-1690 s’apparentant à un mont ou un sommet ; c’est d’ailleurs ce que confirme Swisstopo, la carte la plus fiable en Suisse.