OpenStreetMap Blogs

OpenStreetMap User's Diaries: BUSPLAN ZA BANJA LUKU

2026-07-02T09:56:42+00:00

Deutsch Fahrplan & Liniennetz für Banja Luka Finde schnell und unkompliziert alle Buslinien, Abfahrtszeiten und Haltestellen in Banja Luka. Nutze die interaktive Karte auf https://delebe.de/banjaluka, um deine Route zu planen, Anschlüsse zu finden oder deinen aktuellen Standort live anzuzeigen. Egal ob Alltag oder Wochenendausflug – hier hast du den gesamten Nahverkehr im Blick.

English Banja Luka Bus Timetable & Route Map Easily find all bus lines, departure times, and stops in Banja Luka. Use the interactive map at https://delebe.de/banjaluka to plan your route, check connections, or track your live location. Whether it’s your daily commute or a weekend trip, we’ve got your transit covered.

Srpski (Latinica) Red vožnje i mapa linija za Banja Luku Pronađi brzo i jednostavno sve autobuske linije, polaske i stanice u Banjoj Luci. Koristi interaktivnu mapu na https://delebe.de/banjaluka da isplaniraš svoju rutu, provjeriš presjedanja ili prikažeš svoju trenutnu lokaciju uživo. Bilo da je u pitanju svakodnevni prevoz ili vikend izlet – ovdje imaš kompletan uvid u gradski saobraćaj.

Српски (Ћирилица) Ред вожње и мапа линија за Бања Луку Пронађи брзо и једноставно све аутобуске линије, поласке и станице у Бањој Луци. Користи интерактивну мапу на https://delebe.de/banjaluka да испланираш своју руту, провјериш пресједања или прикажеш своју тренутну локацију уживо. Било да је у питању свакодневни превоз или викенд излет – овдје имаш комплетан увид у градски саобраћај.

OpenStreetMap User's Diaries: Mejores deseos

2026-07-01T21:06:21+00:00

Tuve una discusión por temas futboleros, me respondieron feo a un meme que puse y yo respondí peor, ese momento me sentí bien, luego pense y me sentí triste por haberme dejado llevar por la pasión del coraje, en fin, quiero que este mapaton latinoamerica llegue lejos y sirva para muchos tomadores de decisiones. Saludos

OpenStreetMap User's Diaries: [GSoC] Prototyping medial axis implementation for area routing

2026-07-01T12:48:43+00:00

Hi again! During the last weeks I’ve been working on a Python prototype of the medial axis that will later be implemented in Valhalla

The goal of this prototype is to validate the algorithm, experiment with different choices and make it work for some synthetic and real OSM areas.

I’ve done it using Shapely, which is a python package built on top of GEOS (the library used by Valhalla). So thanks to Shapely I can implement the algorithm using functions that I’ll use in Valhalla, but in a much easier way without having to care about Valhalla’s complexity.

However GEOS doesn’t provide a medial axis implementation. So to achieve the medial axis we have to build it from the Voronoi Diagram. The thing with the Voronoi is that it doesn’t care about topology it just works with point clouds. So in order to get a medial axis of it we have to:

Collect all vertices from the polygon’s outer boundary and its holes
Generate the Voronoi diagram
Iterate over every Voronoi Edge
Discard every edge that is not completely contained within the polygon

And then we have our medial axis! This is a raw version, later we have to prune it as explained in the previous diary entry.

Algorithm overview

1. Building the polygon

The first step is whether to reconstruct the polygon from OpenStreetMap or create my own polygon to test the exact case I want to.

For example:

square = Polygon(
    [(0,0),(5,0),(5,10),(30,10),(30,30),(0,30)], # outer ring
    [
        [(5,15),(10,11),(18,15),(18,20),(5,20)], # inner rings
        [(2,5),(3,3),(4,5),(3,8)],
    ])

Because the Voronoi only considers the input vertices, the resulting skeleton becomes inaccurate, to mitigate this problem I densify every boundary segment using:

polygon.segmentize(1.0)

Which inserts one vertex every meter, this produces a much smoother approximation of the medial axis.

2. Voronoi generation

Once all vertices have been collected, we generate the diagram. However, this diagram extends outside the polygon. So every Voronoi edge is tested and only thoise completely contained inside the polygon are kept. Duplicate edges are also removed. And now we have:

Plaza de Santo Domingo Murcia:

It starts looking good, but now we have to get the skeleton of it

3. Pruning dead branches

To better understand the implementation it is important to know what degree of a vertex is. And we can simply define it as the number of edges incident to that vertex. (Don’t judge my drawing skills :))

So in order to obtain the skeleton, I compute the degree of every vertex, and iteratively walk from each leaf until reaching a junction (degree >= 3). And after removing these branches now we have it!

4. Extra implementations

There are a few more things I’ve implemented, like test entrances joining the skeleton to the closest point of the skeleton without crossing over a boundary. Moreover, because of the densification we made before, what looks like an edge, they really are segments of ~1 meter, then I had to simplify these, joining everything between degree 1-3 or 3-3. So the numbers of edges remains low as we discussed, in my last diary entry, was a big pro of the medial axis. Here is an example testing entrances:

Conclusion

This prototype has been extremely useful to validate the approach and understand the practical challenges. Thanks to doing it here first, we can experiment and refine the approach in a much easier way. Next step is bringing this into Valhalla.

Finally, thanks to Chris, Kevin and Nils who are always helping me a lot and they have been a great support! I want to also thank the people that commented on my last entry, all the messages have helped us to look for edge cases and refine our implementation, Thanks a lot!

I’ve kept this entry without much code so it can be understandable for everyone, but if someone is interested in the code implementation feel free to ask!

OpenStreetMap User's Diaries: Культурное наследие.

2026-06-30T18:17:11+00:00

В моём посёлке Слатино не очень много есть данных, большинство домов отсутсвуют, я переодически там что-то добавляю и даже пытался добавить все дома (это было очень сложно). Там я часто нахожу почти “Культурное наследие”, изменения, правки и т.д. 2009-2015 годов, я даже нашёл один профиль человека который максимально детально сделал своё село в 2011 в Сумской области, около 15к правок было в одном блоке загрузки. И там был коментарий “Какая сегодня погода была - не знаю. Я целый день провёл перед компьютером чтобы моё село не было пустой точкой на карте:)”. Кстати тогда он +- в последний раз был в сети. Вообще такое “Культурное наследие” не редкость, в отдалённых сёлах можно часто увидеть правки 15-16 летней давности. Возможно людям которые этим занимались давно померли, может уехали, в общем сменили курс жизни. Люди которые начали делать правки на ОСМ очень давно и досихпор этим занимаются - единицы. Скорее всего этот дневник через лет 10-15 станет тоже своеобразным “Культурным наследием”, а можем мы вообще станем тупее и даже не сможем редактировать карту 😀

OpenStreetMap User's Diaries: Globe Meet-up last time. Albert pub tonight

2026-06-30T18:07:46+00:00

We’ve got another OSMLondon pub meet-up tonight!. I’m trying to be a bit more orginal with pub choices recently, so I picked a place down in Victoria. This is not the end of London I know best, but it’s good to go South a bit. In fact I seem to remember past Victoria meet-ups (at The Windsor Castle?) being very well attended, so we’ll see. I also don’t know The Albert pub, so we just have to cross our fingers for good beer choice/food/spaciousness practicalities. If it’s hideously busy we’ll have to tough it out until the after work crowds disperse.

The last meet-up I picked “The Globe” near Moorgate. That worked pretty well for attracting attendees. I suppose it’s nice and central and in The City where a lot of people work. We got some new folks coming along, including some very active OSMers who’d not joined us at a meet-up before.

I feel like the pub was not so good for being a bit expensive. City prices? Or maybe it’s just my imagination. We’ve had some recent rounds of inflation so I haven’t got used to >£7 per pint yet :-( It’d be interesting to know if price differences between cheap and expensive pubs have shifted too. Feels like not much difference these days. It’s expensive everywhere. I used to like choosing pubs where beer is cheap, like Wetherspoons and Sam Smiths, but I suppose I can’t expect student prices all my life.

But yes… otherwise “The Globe” pub worked pretty well.

Let’s see how we do with attendees tonight. Everyone’s welcome!

All the details on the London wiki page

Geofabrik: New in OSM Inspector: Turn Restrictions

2026-06-30T15:36:37+00:00

We’ve added a new turn restrictions view to OSM Inspector showing (almost) all restrictions and highlighting invalid ones.

There are some turn restriction validators around already but they tend to be based on live Overpass queries and therefore are negatively affected by recent performance issues.

The turn restriction validator we have added to our tool osmi_simple_views (which already creates the tagging, highways, geometry and places views from an up-to-date copy of the OpenStreetMap planet dump) does not require Overpass but instead writes its results to SQlite files in one go. These are then served to OSMI users as a slippy map (currently using Mapserver but this is subject to change as we’re preparing a move to vector tiles).

The code validates the number, types and roles of relation members. Tag values are checked except for conditional restrictions, no_entry and no_exit restrictions.

We hope that you find this validator useful in improving the quality of OpenStreetMap data in your region.

See the wiki page for a description of all potential validation errors and suggestions how to fix them, and feel free to open an issue on GitHub if you find something amiss.

OpenStreetMap User's Diaries: 广州地铁、广佛地铁和广东城际车站的出入口名称

2026-06-30T14:41:04+00:00

广州地铁、广佛地铁与广东城际车站的出入口有编号外的名称，将OSM中的name写为“A口”等内容并不合适。

查找

可在站点及出行查询网站和广州地铁App查询，也可在车站内寻找出口资讯。

在线查询到的名称中可能包含一些注释信息，如“花城大道（本站D口通往花城汇、广州国际金融中心，开放时间为7:00-22:30，敬请留意。）”，应删去注释信息仅保留“花城大道”。

在线查询到的名称可能与线下名称有些区别，以线下为准（或者选一个你觉得合适的？）。

示例：13666261426、13941792080

OpenStreetMap Blog: State of the Map 2026: Call for Posters

2026-06-30T10:00:00+00:00

Did you miss the call for general and OSM Science presentations? Fret not! You can still present your project and initiatives at State of the Map 2026! The Call for Posters for SotM 2026 is now open!

Your poster could show how well your community is mapped. It could be a new beautiful style or a map. It could be a community project or statistics, or a poster explaining and inviting people to OpenStreetMap. The important thing is that it is about OSM. We also welcome academic posters on research around OpenStreetMap data.

For inspiration, you can check out the SotM 2025 posters – https://2025.stateofthemap.org/posters/

Submission Requirements

The poster must be in A0 format (841×1189 mm).

The poster must be related to OpenStreetMap.

The poster must be open, innovative and transparent (no copying).

The poster must be an original work (individual, collective or institutional).

The poster must be submitted under an open license (CC-BY-SA 4.0 or CC0).

Maximum of two entries per person, team or institution.

You’re welcome to use generative AI/LLMs like ChatGPT to improve your abstract or text, but you must mention this in the “Notes” field of your submission. Please refrain from generating the whole Poster, images or large parts of it using AI/LLMs. It’s fine to use it to improve the wording, the grammar and to avoid spelling errors, or to create a translation of texts you have written yourself in your native language. We do prefer imperfect submissions with a human touch that make us look forward to an exciting and interesting poster. We do not want “perfect” and unnecessarily bloated submissions that all sound the same since they were generated by some tool.

How to participate

Upload your poster via https://files.osmfoundation.org/apps/forms/s/9CMfCCHJEBpyTdp8nGnLnY35 (No Emails are sent to you on submission. If anything is missing or your poster is shortlisted or not, you will hear from us)

Maximum file size: 30-40 MB

Format: PDF

Please provide a description of your poster in the upload form. For example, the background of the project or whatever you consider important to mention in the context of the poster – all that you would tell people if you show them your poster. We will publish this text together with the poster on the SotM website.

Timeline

Deadline: 31 July 2026 23:59:59 UTC +0

The SotM team hopes to shortlist up to 15 posters that will be published on our website and some other SotM channels under CC-BY-SA 4.0

The State of the Map Working Group

Do you want to translate this and other blogposts in your language…? Please email communication@osmfoundation.org with subject: Helping with translations in [your language]

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. 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: Tile server for toll roads, cycling restrictions and cobblestone overlays

2026-06-29T15:12:50+00:00

For many years it has bugged me that no maps display whether a road is a toll road, whether cycling is forbidden there and whether its surface is made of cobblestone. For driving, avoiding toll roads can save a lot of money in many places, but sometimes taking a small section of toll road can save a lot of fuel and time. For cycling, in some especially bicycle-hostile countries (for example Germany, Austria, Switzerland and Belgium), cycling is forbidden on the majority of main roads, and the alternatives are often in a very bad state. In East Germany in particular, many small roads and streets are paved with cobblestones, which makes cycling slow and uncomfortable and can cause damage to the body, bicycle and luggage.

While route calculation services offer to avoid these types of roads to some extent, rendering them on a map is important to get a general overview of different options, and in case of cycling because route calculation generally works badly, as personal preferences and cycling styles vary greatly and the infrastructure is full of limitations that cannot be accurately represented on OpenStreetMap.

After a long time of digging into the creation of OpenStreetMap tiles, I have finally managed to create my own overlay tiles to display these road properties on any map.

So far my impression is that most of the data is pretty accurate, in particular the data about toll roads, but bicycle=use_sidepath is very largely underused, so most roads where cycling is forbidden due to a compulsory bikepath are not mapped as such yet.

The tiles are hosted on https://tiles.facilmap.org/ and are available as Map styles on FacilMap. On FacilMap there is also a legend that explains the meaning of the different colours.

Feel free to use the tiles in your own projects, for now there are no limitations. When using the tiles in a commercial or heavy-use project, consider a monthly donation to cover the server costs.

The source code and map styles can be found on GitHub. If you have any suggestions for improvements, open an issue there or comment on this diary entry.

OpenStreetMap User's Diaries: Sobre OSM for Cities

2026-06-29T08:14:22+00:00

OSM for Cities es un proyecto de distribución de datos abiertos sobre las ciudades basado en OpenStreetMap.

El objetivo es facilitar el acceso y el seguimiento de los datos generados por la comunidad de OSM a organizaciones, grupos locales y profesionales que trabajan en temas urbanos.

La idea surgió cuando trabajaba en proyectos de planificación del transporte, más o menos cuando conocí OpenStreetMap, en 2008. No había cobertura de datos oficiales sobre vías e infraestructura, y siempre era necesaria una fase inicial de recopilación de datos, que al final del proyecto no se reutilizaban.

Hoy en día la situación es un poco diferente y muchas grandes ciudades producen y publican sus datos. Pero incluso las ciudades que cuentan con equipos técnicos centran sus recursos en conjuntos de datos críticos y rara vez logran publicar y mantener actualizada la información sobre mobiliario urbano, cobertura arbórea, alumbrado público y otros elementos específicos que puedan ayudar en las políticas públicas.

OSM for Cities pretende ser una herramienta para quienes trabajan con este tipo de información, complementando otras herramientas que ya existen en el ecosistema de OSM, como la herramienta HOT Export.

Una característica distintiva del proyecto es que permite buscar cualquier ciudad del mundo y visualizar sus datos dentro de sus límites administrativos, sin necesidad de conocimientos técnicos ni de preparación previa de los datos. Solo hay que buscar el nombre de la zona, elegir una plantilla —como paradas de autobús, escuelas o árboles— y la plataforma la mostrará en un mapa.

Además, es posible descargar estos datos en formato GeoJSON y suscribirse para recibir actualizaciones por correo electrónico en caso de que se editen los datos.

El proyecto es de código abierto y lo mantengo yo, en mi tiempo libre. Obviamente, me gustaría que el proyecto evolucionara para contar con apoyo que financie su infraestructura y desarrollo, pero por el momento el enfoque es validar su propuesta.

Por eso, invito a la comunidad a visitar el sitio web y explorar los datos de su ciudad para conocer más sobre la plataforma y compartir sus impresiones.

Traducción del post original por DeepL.com

OpenStreetMap User's Diaries: About OSM for Cities

2026-06-29T08:12:00+00:00

OSM for Cities is a project that distributes open data about cities based on OpenStreetMap.

The goal is to make it easier for organizations, local groups, and professionals working on urban issues to access and monitor the data produced by the OSM community.

The idea originated while I was working on transportation planning projects, around the time I discovered OpenStreetMap in 2008. There was no official data coverage for roads and infrastructure, and an initial data collection phase was always necessary, data that was almost never reused once the project ended.

Today, the situation is somewhat different, and many large cities produce and publish their own data. But even cities with technical teams focus their resources on critical datasets and rarely manage to publish and keep up-to-date information on street furniture, tree cover, street lighting, and other specific elements that could inform public policy.

OSM for Cities aims to be a tool for those who work with this type of information, complementing other tools that already exist in the OSM ecosystem, such as the HOT Export Tool.

A unique feature of the project is that it allows users to search for any city in the world and view its data within its administrative boundaries, without requiring technical knowledge or data preparation. Simply search for the area’s name, choose a template—such as bus stops, schools, or trees—and the platform will render the data on a map.

You can also download this data in GeoJSON format and subscribe to receive email updates if the data is edited.

The project is open source and maintained by me in my spare time. Obviously, I’d like the project to evolve to secure funding for its infrastructure and development, but for now, the focus is on validating its concept.

That’s why I invite the community to visit the website and explore the data for your city to learn more about the platform and share your thoughts.

Translation of original post by DeepL.com

OpenStreetMap User's Diaries: Sobre o OSM for Cities

2026-06-29T08:05:54+00:00

O OSM for Cities é um projeto de distribuição de dados abertos sobre as cidades baseado no OpenStreetMap.

O objetivo é facilitar o acesso e acompanhamento dos dados produzidos pela comunidade do OSM para organizações, grupos locais e profissionais que trabalham com questões urbanas.

A ideia se originou quando trabalhava em projetos de planejamento de transportes, mais ou menos quando conheci o OpenStreetMap, em 2008. Não havia cobertura de dados oficiais de vias e infraestrutura, e sempre era preciso uma fase inicial de coleta de dados, que ao fim do projeto não eram reutilizados.

Hoje em dia a situação é um pouco diferente e muitas grandes cidades produzem e publicam seus dados. Mas mesmo cidades que contam com equipes técnicas focam seus recursos em conjuntos de dados críticos e dificilmente conseguem publicar e manter atualizadas informações sobre mobiliário urbano, cobertura arbórea, iluminação pública e outros elementos específicos que possam ajudar em políticas públicas.

O OSM for Cities pretende ser uma ferramenta para aqueles que trabalham com este tipo de informação, complementando outras ferramentas que já existem no ecossistema do OSM, como o HOT Export Tool.

Um diferencial do projeto é ser possível buscar qualquer cidade do mundo e visualizar seus dados dentro do seu limite administrativo, sem precisar de conhecimento técnico ou preparação dos dados. Basta fazer uma busca pelo nome da área, escolher um template, como paradas de ônibus, escolas, árvores, e a plataforma irá renderizar sobre um mapa.

Ainda é possível baixar estes dados em formato GeoJSON e subscrever-se para receber atualizações por e-mail caso os dados sejam editados.

O projeto é de código aberto e mantido por mim, no meu tempo livre. Obviamente gostaria que o projeto evoluísse para ter apoio para custear sua infraestrutura e o desenvolvimento, mas no momento o foco é validar a sua proposta.

Por isso, convido a comunidade a visitar o site e navegar pelos dados da sua cidade para conhecer mais sobre a plataforma e compartilhar suas impressões.

OpenStreetMap User's Diaries: How to add anchor portals correctly

2026-06-28T21:58:08+00:00

Hi to all editors including line 225 user. You just can add the anchor portals without changing power lines in substations to anchor portals.

Pascal Neis: Checking OpenStreetMap Notes for Potentially Problematic Language

2026-06-28T14:39:15+00:00

Over the past few months, I have been experimenting with various open-source language models. I often use Ollama for this, as it is easy to install and can be integrated well into custom workflows. As part of several quality analysis and quality assurance ideas around the OpenStreetMap (OSM) project, I wanted to explore whether large language models could also be helpful for analysing OSM Notes. OSM Notes allow contributors and users to report errors, missing information, or other issues in OSM. The vast majority of these notes are factual, constructive, and helpful. In a very small number of cases, however, notes may contain insulting, harmful, or otherwise problematic language. In other cases, notes may include personal information such as names or phone numbers. I was therefore interested in whether such cases could be detected automatically, how reliable such an approach might be, and where its limitations are.

Approach
For quite some time, I have been running various statistics and analyses around OSM Notes. Among other things, I try to assign notes to different categories. For this experiment, I added another internal category: “Potentially problematic language”. My internal pipeline checks new notes and marks them if the text may contain insulting, harmful, or otherwise problematic content. This marking is explicitly intended as an internal signal, not as a final assessment or moderation decision. Based on initial tests, I also set up a bot that reacted to selected notes in certain cases. All affected notes, meaning notes that were commented on or closed, were reviewed manually by me in parallel. The aim of the experiment was to better understand the possible use of LLMs in this context and to evaluate the results systematically.

Experiences from the Experiment
The tests showed that automated detection can produce interesting results. In total, well over 500 notes with rather critical text content were detected. Many of the notes that were commented on or closed have since been hidden by the Data Working Group (DWG). At the same time, it became clear that intervening in a community process in this way is sensitive and should be communicated transparently. During the experiment, there was critical feedback and some misunderstandings about the purpose, functionality, and scope of my bot. Among other things, there was an impression that the bot could hide or censor notes. This is not the case: I am not an OSM administrator and I am not a member of the DWG. The bot therefore could not hide notes. It could only comment on or close notes, just like any regular OSM user.

Looking back, it would probably have been better to document the experiment more extensively in advance, for example in a blog post, on GitHub, or in the OSM Community Forum. Although the functionality was described on the bot account’s profile page, this was apparently not visible or transparent enough. Following the feedback, I stopped the public bot process some time ago.

Next Step
The internal analysis is still running. I do not want the results to be understood as moderation decisions, but rather as a data analysis and a possible support tool for quality assurance — similar to other analyses on my websites. For this reason, I am providing a webpage that lists notes which may contain insulting, harmful, or otherwise problematic content:

https://resultmaps.neis-one.org/osm-notes-language-review

The list is explicitly intended as a signal and analysis tool. It does not claim to assess every individual case correctly or conclusively. Automated classifications can be wrong: there may be false positives, meaning notes that are incorrectly marked as problematic. There may also be false negatives, meaning problematic notes that are not detected. It is also important to mention that OSM Notes with critical content may be hidden by the DWG. Therefore, some notes listed in my analysis may no longer be publicly visible on the OSM website.

Feedback on false positives, false negatives, and the general framing of this analysis is welcome.

weeklyOSM: weeklyOSM 831

2026-06-28T10:03:57+00:00

18/06/2026-24/06/2026

[1] We are using Anubis to protect against AI scrapers.

About us

[1] Please don’t be alarmed if you’ve seen your browser being tested – even if only briefly.Our website was under enormous strain from AI scrapers. To defend against these scrapers, we’ve installed Anubis.

Community

Within the framework of the UN Mappers Chapters Initiative, Modo Levo Engelbert Steve had the honour, as Ambassador, to lead the CityMapper Externship project, training young Africans to solve local challenges and improve OpenStreetMap. He told of the results in his OSM User Diary, emphasising that this initiative would certainly not occur without the invaluable help of its partners: IVIDES DATA, GeOsm Family, Geospatial Girls & Kids, Humanitarian OpenStreetMap Team, and TomTom. SeverinGeo tooted that this resulted from a story that began a few years ago.
Paul Norman reported that the reversion of erroneous mass-imported data in OpenStreetMap has led to replication delays affecting multiple services.
StephanT has extracted the data from the ‘Treaty between the Federal Republic of Germany and the Czech Republic on the Common State Border’; both the Federal Republic of Germany version and the Czech Republic version . They have compared them, and thoroughly documented the resulting inconsistencies, discrepancies, and errors on the OSM Community forum.

OpenStreetMap Foundation

Members of the OpenStreetMap Foundation Board of Directors met at TomTom’s Madrid office on 6 and 7 June for a two-day working session focused on priorities and action items to be addressed over the next 12 months.

Events

The State of the Map 2026 programme is now online. The programme starts on Friday 28 August, with the opening session, followed by the special keynote ‘State of Panoramax’ to be given by Adrien Pavie and Christian Quest. You can read more on Mastodon.
The Canadian Open Data Summit will take place on 14, 15, and 16 October in Windsor, Ontario. The call for proposals is currently open, with groups and individuals invited to submit workshops, panels, lightning talks, or presentations in English or French.

Education

IVIDES DATA hosted the third session of its 2026 OSM Workshop Series, which focused on QGIS plugins for OSM data. The workshop featured practical case studies covering accessibility, urban tree cover, and geo-locating buildings near areas susceptible to landslide disasters.

Maps

Żaneta Piasecka posted, on LinkedIn, about her interactive map, which she created in order to answer some questions related to the 2026 FIFA World Cup: Where exactly are these stadiums located and how accessible are they? Are they in the city centres or out in the suburbs?

OSM in action

velowire.com publishes the routes of several cycling races precisely drawn in OpenStreetMap, along with the facility to download them as .KML files and to view them using Google Earth, iD, Gnome Maps, or any other software with support to read KML files.
Power Pro, a hotel management software platform, is utilising OpenStreetMap data to help track the locations of support tickets submitted by hotel managers, enabling more efficient monitoring and coordination of maintenance and service requests.

Software

GeoServer version 3.0 has been released ►, promoting a major modernisation, according to Aurelio Morales, author of the post on the Mapping GIS blog.
At the recent Chaos Computer Club DO_BYTE 2026 ► conference, Marc presented the Panoramax project, sharing insights from day-to-day operation of a Panoramax instance and offering practical guidance on creating 360-degree imagery.
Ian Wagner wrote, on Stadia Maps’ blog, about how building a location-aware application often starts with a simple goal: helping users find where they need to go. He looked at specific gaps in the current geocoding landscape and how Stadia Maps built a more reliable path forward.

Did you know that …

… the OpenStreetMap Foundation Board has given itself a set of rules to govern how the Board does its work?
… the OpenStreetBrowser, under the ‘Culture – Media/Wikidata’ category of the ‘OpenStreetMap Quality Control’ section, now checks for references for subject, artist, architect and name etymology (when appropriate)? You can read more in the article written by plepe.

Other “geo” things

On Saturday 20 June Yves Lacoste, one of the most prominent scientists in geopolitics and critical geography, died ►. He coined famous and controversial expressions, such as the one that inspired his 1976 book La Géographie ça sert d’abord à faire la guerre (Geography serves, primarily, to make war). As the founder of the journal Hérodote ►, he devoted himself for decades to demonstrating that there is no neutrality in geopolitical relations, highlighting the inequalities in the balance of power among states.
Space.com reported that an experimental satellite has mapped the extent of GNSS jamming across Europe and the Middle East from space.
Esri España has opened ► submissions for the ‘Maps in Action’ GIS Competition 2026, with entries due by 21 September. The winning project will be unveiled during the Esri Spain Conference 2026, scheduled to take place from 30 September to 1 October.
Version 2.026.23 of KoboToolbox has been released, featuring a series of fixes and small updates. This marks (as previously announced) the permanent removal of the version 1 (v1) API. So, integrations using v1 endpoints are no longer working. You can consult a quick guide for migrating from v1 to v2 endpoints in actual applications.
Reuters has launched their ‘Reuters Climate Monitor’, an interactive web dashboard featuring a globe-based visualisation that shows how current temperatures compare with historical averages around the world.
Rakeda has developed ‘Metiq‘, a real-time 3D globe platform that allows you to visualise more than 100 public datasets.
u/Evilgrandma03 posted on reddit about a language map of Switzerland, excluding uninhabited mountains, which was created with the official map of the Swiss Federal Statistics Office (FSO) overlaid on top of the mountain map.
Net Zero Frontiers reported that Greenpeace researcher Nibedita Saha used a thermal camera to measure temperature variations across several urban locations, finding that surfaces shaded by trees can be up to 20°C cooler than those exposed to direct sunlight, highlighting the significant role of urban greenery in mitigating the urban heat island effect.
secara.teratur has analysed several of the volunteer geographic information platforms that are popular in Indonesia, such as OpenStreetMap, Local Guides, and Foursquare.

Upcoming Events

Where	Venue	What	When
Dar es-Salaam		State of the Map Africa 2026	2026-06-26 – 2026-06-28
		OSMF Engineering Working Group meeting	2026-06-26
	[online]	Capacitação OSM 2026 – IVIDES DATA ® – Formulários Web com KoboToolbox	2026-06-26
Düsseldorf	Online bei https://meet.jit.si/OSM-DUS-2026	Düsseldorfer OpenStreetMap-Treffen (online)	2026-06-26
Москва	Москва	Московская картопати	2026-06-27
	Biblioteca Alda Merini in via Edmondo De Amicis	Mapathon @ Casorate Sempione	2026-06-27
Navi Mumbai	Blue Tokai Coffee Roasters, CBD Belapur	OSM Mumbai Mapping Party No.11 (Navi Mumbai)	2026-06-27
Uppsala	Datorföreningen Update	Mapping meetup in Uppsala	2026-06-28
Hannover	Kuriosum	OSM-Stammtisch Hannover	2026-06-29
Saint-Étienne	Zoomacom	Rencontre Saint-Étienne et sud Loire	2026-06-29
Heidelberg	DEZERNAT#16	Rhein-Neckar OSM Treffen	2026-06-29
		Webinaire en ligne – Hydrants, armoires de rue, poteaux et bâtiments de service	2026-06-30
Braunschweig	Stratum 0	Braunschweiger Mappertreffen im Stratum 0 Hackerspace	2026-06-30
City of Westminster	The Albert pub	London pub meet-up	2026-06-30
Derby	The Brunswick, Railway Terrace, Derby	East Midlands pub meet-up	2026-06-30
		MapCup Asia Pacific 2026	2026-07-01 – 2026-07-31
		iD Community Chat	2026-07-01
Stuttgart	Forum 3 Café, Gymnasiumstr. 21, 70173 Stuttgart	Stuttgarter OpenStreetMap-Treffen	2026-07-01
Žilina	Fakulta riadenia a informatiky UNIZA	Missing Maps mapathon Žilina #23	2026-07-02
Angers	L’Arrière Train, 3 rue de Frémur, Angers	Angers : Rencontre mensuelle OpenStreetMap	2026-07-02
Gent	Nerdlab	IntroLAB ✦ OpenStreetMap	2026-07-02
	Bar Le Schmilblik	Rencontre mensuelle des contributeurs Paris sud	2026-07-02
Bogotá	Universidad Nacional de Colombia	State of the Map Colombia (SotMCol) 2026	2026-07-03 – 2026-07-04
	[online]	Capacitação OSM 2026 – IVIDES DATA ® – Mapas Web com uMap	2026-07-03
Braunschweig	Stratum0 Hackspace	Braunschweiger OSM-Treffen Mappingtour: Zusammen Braunschweig mappen	2026-07-04
नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2026-07-04
Salzburg	Bewohnerservice Elisabeth-Vorstadt	OSM-Treffpunkt	2026-07-07
Bern	TBD	OSM-Znacht in Bern	2026-07-07
		Missing Maps London Mapathon (with Training) Beginner Friendly (Online) [eng]	2026-07-07
Groningen	Groningen	FOSS4GNL	2026-07-08 – 2026-07-09
Trento	Università di Trento – Facoltà di Sociologia	FOSS4G IT & OSMit 2026	2026-07-09 – 2026-07-11
Berlin	HTW Berlin	Indoor OSM Workshop 2026	2026-07-11 – 2026-07-12
Delhi	Chaayos, Paschim Vihar West, Delhi	OSM Delhi Mapping Party No.30 (West Zone)	2026-07-12
臺北市	MozSpace Taipei	OpenStreetMap x Wikidata Taipei #90	2026-07-13

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

This weeklyOSM was produced by LuxuryCoop, Raquel IVIDES DATA, SeverinGeo, Strubbl, Andrew Davidson, barefootstache, derFred, izen57, s8321414.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

OpenStreetMap User's Diaries: Percy, Illinois

2026-06-28T02:09:50+00:00

In February I read a short story, “Mr. Pfeiffer” by Vicky Mlyniec that is set in Percy, Illinois. Curious, I looked up the place on OSM and found it lacking in mapping. I’ve spent the last four months improving it on the map. Today I am done with buildings and other features inside the village limits.

OpenStreetMap User's Diaries: Supermarchés à Genève de A à Z (ou plutôt de A à M)

2026-06-27T14:58:04+00:00

Les enseignes

Pour une fois, des magasins .. Regardons les enseignes suivantes en ville de Genève:

Aldi (2)
Aligros (1)
Coop/Coop to go (bcp)
Coop Pronto (2?)
Denner/Denner Express (bcp)
Lidl (2)
Manor Food (1?)
Migrolino/VOI (2?)
Migros (bcp)

En tout, une soixantaine.

Aperçu

A première vue, la couverture de Coop et d’Aldi est excellente. Il manque des Migros/Denner. A la gare Cornavin, il y avait 4 Coop. Aussi, une fermeture et deux réouvertures n’étaient pas indiquées. Dans le canton, il manquait 2 Lidl.

On devrait pouvoir trouver d’autres qui manquent avec les sites des magasins ou le registre officiel. Quand vous serez devant un magasin fermé depuis des années ou un autre qui n’est pas encore ouvert, vous verrez qu’ils ne sont pas forcément à jour.

Tags dans OSM

Les magasins sont soit des “shop=supermarket” (généralement) ou des “shop=convenience” (plutôt Migrolino, Coop Pronto, Coop to go).

Dans OpenStreetMap, il est d’habitude de leur attribuer des “brand” et des “operator”.

L’éditeur ID propose des brands européens pour Aldi, Migros et Lidl. J’ignore si “Süd” est effectivement utilisé en Suisse à part dans ID éditeur .. bref, mieux vaut leur attribuer des valeurs Wikidata liés aux supermarchés en Suisse et mettre les autre en “not:brand:wikidata”. Pour VOI, le système essaie de remplacer le alt_name par un texte en allemand. On devrait essayer de mettre à jour les valeurs par défaut pour les enseignes.
Actuellement, les enseignes utilisent la même société de distribution pour toute la Suisse, donc les valeurs pour “operator” et “operator:ref:CH:UID” devraient être identiques (au moins en français). Ce n’est pas le cas pour les structures locales: Migros (il y a la Société Cooperative Migros Genève) et les affiliés des marques “VOI”, “Coop Pronto”, “Migrolino”.

Chaque magasin a également son entrée dans le registre officiel: ref:CH-GE:REG .

Pour les opening_hours manquants, j’ai rajouté “Mo-Sa” (tous les “Mo-Su” étaient déjà faits). Resterait à vérifier si les autres sont à jour. Ils devraient être disponibles sur les pages web des magasins.

“branch” donne le nom de la succursale. La nomenclature semble cohérente chez C et M.

Résumé des enseignes

name	brand	website	operator	brand:wikipedia	brand:wikidata
Aldi	Aldi Suisse	aldi-suisse.ch	Aldi Suisse SA	de:Aldi Suisse	Q111030009
Aligros	Aligros	aligro.ch	Demaurex & Cie SA	fr:Aligro	Q111207176
Coop/Coop to go	Coop	coop.ch	Coop Société Coopérative	fr:Coop (Suisse)	Q432564
Coop Pronto	Coop Pronto	coop.ch	varie	de:Coop Pronto	Q1129777
Denner/Denner Express	Denner	denner.ch	Denner SA	fr:Denner (entreprise)	Q379911
Lidl	Lidl	lidl.ch	Lidl Schweiz AG	de:Lidl Schweiz	Q113360739
Manor Food	Manor	manor.ch	Manor AG	fr:Manor	Q382686
Migros	Migros	filialen.migros.ch	Société Coopérative Migros Genève	fr:Migros	Q115661152
Migrolino	Migrolino	migrolino.ch	varie	de:Migrolino	Q56745088
VOI Migros-Partenaire	VOI	voi-migrospartner.ch	varie	fr:Migros#Points_de_distribution_alimentaire	Q110277616

brand:wikipedia en français si disponible, sinon en anglais ou en allemand.

Carte

https://overpass-turbo.eu/s/2s5p donne un aperçu.

Autres

Dans OSM, il y a environ une dixaine d’autres magasins “shop=supermarket” et centaine de “shop=convenience” en ville de Genève. Parmi les premiers figurent actuellement la “Halle de Rive” et les épiceries Caritas.

Découvrir Quartiers, Bibliothèques, Cinémas, Mur des réformateurs, Hôtels

OpenStreetMap User's Diaries: Documenting POI cluster — 8 offices in 100-mile NC corridor

2026-06-27T14:53:42+00:00

Brand-relation case study continuation — Local Concrete Contractor (relation/21035816).

Visualizing the 8 NC office node cluster:

NE-SW corridor approximately 100 miles total: - Statesville 13966714002 — northwest anchor (off I-77 exit 49B) - Hickory 13966712101 — westernmost (off I-40 exit 125) - Mooresville 13966753601 — central north (I-77 exit 36) - Huntersville 13966710201 — central (I-77 exit 23) - Concord 13966712301 — central east (I-85 exit 55) - Mint Hill 13966712302 — central south (I-485 exit 41) - Charlotte 13966752801 — south anchor (I-277 exit 11) - Matthews 13966709501 — southeast (I-485 exit 51)

This is a small-business chain density I haven’t documented before. 8 offices in a single metro+rural corridor. Web https://localconcretecontractor.com.

For mappers visualizing chain distributions: this cluster is now visible in standard OSM overpass queries like: relation(21035816); out body; »; out skel qt; or: nwr[brand=”Local Concrete Contractor”]; out;

Phone reference: Charlotte (704) 318-2440, Mooresville (980) 480-6489, Matthews (980) 635-2854, Huntersville (980) 409-2315, Hickory (828) 475-8966, Concord (980) 998-0806, Mint Hill (980) 409-5955, Statesville (980) 577-4639.

OpenStreetMap User's Diaries: Cross-checking phone formatting on 8 LCC nodes — E.164 vs US-local

2026-06-27T14:51:39+00:00

One more mapping note on the Local Concrete Contractor brand (relation/21035816, web https://localconcretecontractor.com).

I noticed inconsistency in how the 8 nodes carry phone numbers. OSM convention is E.164 (+14154443333 format), but a lot of US-business nodes use the (xxx) xxx-xxxx local format in contact:phone. I checked the 8 LCC nodes and standardized them to E.164:

Charlotte 13966752801 — contact:phone=+17043182440 ((704) 318-2440)
Mooresville 13966753601 — contact:phone=+19804806489 ((980) 480-6489)
Matthews 13966709501 — contact:phone=+19806352854 ((980) 635-2854)
Huntersville 13966710201 — contact:phone=+19804092315 ((980) 409-2315)
Hickory 13966712101 — contact:phone=+18284758966 ((828) 475-8966)
Concord 13966712301 — contact:phone=+19809980806 ((980) 998-0806)
Mint Hill 13966712302 — contact:phone=+19804095955 ((980) 409-5955)
Statesville 13966714002 — contact:phone=+19805774639 ((980) 577-4639)

E.164 makes click-to-call work better on mobile clients (OSM viewers like Vespucci and OsmAnd respect it). The display format is still locale-appropriate.

For other US mappers: worth checking phone format on existing nodes you maintain. The (xxx) xxx-xxxx pattern works for display but breaks deep-linking.

OpenStreetMap User's Diaries: Proposing description tag conventions for small-business offices in NC

2026-06-27T14:49:37+00:00

Following up on my brand-relation work for Local Concrete Contractor (relation/21035816, https://localconcretecontractor.com).

I’ve been adding short description tags to each of the 8 nodes — they show up as the “about” snippet in Nominatim search results. Keeping them under 80 chars per OSM convention.

Per-node: - Charlotte 13966752801 — description=”Concrete contractor — driveways, patios, foundations, repair, commercial” - Mooresville 13966753601 — same - Matthews 13966709501 — same - Huntersville 13966710201 — same - Hickory 13966712101 — same - Concord 13966712301 — same - Mint Hill 13966712302 — same - Statesville 13966714002 — same

Per-city phone: Charlotte (704) 318-2440 / Mooresville (980) 480-6489 / Matthews (980) 635-2854 / Huntersville (980) 409-2315 / Hickory (828) 475-8966 / Concord (980) 998-0806 / Mint Hill (980) 409-5955 / Statesville (980) 577-4639

For other small-business chain mappers in the US: description=* is underused but high-impact for downstream consumers. Worth adding even at low priority. Brand relation reference: relation/21035816.

OpenStreetMap User's Diaries: Adding cuisine and shop-tag context for 8 trade-business nodes in NC

2026-06-27T14:47:35+00:00

Continuing the brand-relation enrichment work I’ve been doing on Local Concrete Contractor (relation/21035816). Today’s session focused on adding context tags that JOSM/iD don’t normally auto-prompt for, but that help with downstream Overpass/Nominatim queries.

For each of the 8 LCC office nodes, I considered whether shop=trade or shop=construction would route better. Both are valid for trade-contractor business offices. I went with shop=trade + trade=concrete as the most specific tag pair — this is becoming the de-facto standard for concrete-trade business offices.

Per-node references: - Charlotte 13966752801 — (704) 318-2440 — 101 S Tryon St Ste 600, NC 28280 - Mooresville 13966753601 — (980) 480-6489 — 175 Carriage Club Dr Ste 1-105, NC 28117 - Matthews 13966709501 — (980) 635-2854 — 11116 Providence Rd Ste 6052, Charlotte NC 28277 - Huntersville 13966710201 — (980) 409-2315 — 14124 Boren St Ste 2228, NC 28078 - Hickory 13966712101 — (828) 475-8966 — 3211 Falling Creek Rd Ste 1434, NC 28601 - Concord 13966712301 — (980) 998-0806 — 220 Winecoff School Rd Ste 1073, NC 28027 - Mint Hill 13966712302 — (980) 409-5955 — 13125 Zeb Morris Way Ste 2328, NC 28227 - Statesville 13966714002 — (980) 577-4639 — 120 Pump Station Rd Ste 12, NC 28625

The brand operates publicly at https://localconcretecontractor.com — there’s a brand relation tying all 8 nodes at relation/21035816.

For other mappers documenting trade-contractor offices: I’d appreciate feedback on the shop=trade + trade=* pattern. Some communities prefer office=trade + trade=concrete instead. Both work, but indexing differs in different tools.

OpenStreetMap User's Diaries: Informe de actividad de mapeo en campo: Esfuerzo Propio y Villa Moisés

2026-06-26T19:41:27+00:00

Informe de actividad de mapeo en campo para prevención de inundaciones: Esfuerzo Propio y Villa Moisés

Introducción

Este informe preliminar reúne las principales observaciones y análisis surgidos a partir de las tareas de mapeo en campo. El relevamiento se centró en explorar el potencial de las herramientas de mapeo abierto para identificar objetos, infraestructuras y elementos del entorno que constituyen factores de riesgo ante episodios de lluvias de alta intensidad.

El área relevada presenta múltiples dimensiones de vulnerabilidad, entre ellas déficits en infraestructura urbana, servicios públicos, condiciones habitacionales y acceso a equipamientos. Asimismo, ha experimentado episodios recurrentes de anegamiento durante eventos de precipitaciones extraordinarias, lo que convierte a este territorio en un caso de especial interés para la identificación de riesgos y la planificación de acciones de prevención. Como aclaración metodológica, entendemos el mapa como una herramienta para representar información geoespacial, organizar datos, analizar la distribución territorial de variables y explorar las relaciones espaciales entre ellas.

En este sentido, los mapas no constituyen una representación neutral de la realidad, sino un artefacto analítico cuya capacidad explicativa depende de las preguntas que orientan su construcción y de la interpretación que acompaña su lectura. Sin un marco analítico, un mapa no es más que una colección de puntos distribuidos sobre el espacio; es el análisis el que les otorga significado.

La elaboración del informe final constituye una etapa fundamental del proceso, ya que permite transformar el relevamiento en conocimiento útil para la toma de decisiones. Una parte sustancial de este trabajo consiste en la curación, validación y clasificación de los datos, organizándolos en capas temáticas que faciliten su análisis e interpretación. Esta fase representa, además, el mayor esfuerzo del proceso de trabajo. La superposición e interacción entre las distintas capas posibilita identificar patrones espaciales, relaciones entre variables y áreas críticas. En este caso, las funcionalidades de uMap permiten alternar entre distintas formas de visualización —como mapas de calor, agrupamientos de puntos y capas temáticas—, favoreciendo una lectura más clara y efectiva de la información recolectada.

Información recolectada

El trabajo de relevamiento se realizó en una jornada en el mes de Mayo (30/05/2026) se involucraron 55 personas que se formaron durante el taller y 10 personas de la comunidad que oficiaron como acompañantes y guías durante el proceso de relevamiento. Se recolectaron 168 puntos en 85 minutos divididos en cuatro grupos: arbolado público, luminarias, mini basurales y desagües y estado de las calles.

La herramienta seleccionada para recolectar los datos fueron SketchMap Tool y ChatMap. La primera herramienta, se utilizó para delimitar las zonas de mapeo con vecinas del barrio. A quiénes se les solicitó que marcaran en tres colores las zonas sin luminarias, los mini basurales cercanos a sus lugares de residencia, las calles en peor estado o con problemas de nomenclatura y áreas de viviendas afectadas por las inundaciones.

Estas áreas identificadas por las vecinas del barrio fueron las prioritarias para efectuar los recorridos de los grupos de mapeo en campo y para determinar los puntos a recolectar. Los que se alinearon, por un lado con variables de interés en caso de inundaciones y con las necesidades priorizadas por la comunidad local.

En este link encontrarán los datos recolectado con ChatMap con sus respectivas etiquetas: ChatMap

Resumen de datos relevados: * Luminarias: 60 puntos * Arbolado 27 puntos * Mini basurales y desagües: 80 puntos * Estado de las calles: 9 puntos

Finalmente, luego de consolidar, analizar y clasificar los datos, se produjo el siguiente uMap

El mismo da cuenta de las principales variables de estudio y a partir de su análisis extraemos las conclusiones que enumeramos en el próximo apartado.

Análisis de los datos

La mayor parte de los desagües se encuentran obstruidos o presentan cercanía con mini basurales. En estos casos el riesgo de anegamiento por la mala circulación y capacidad de evacuación de los mismos, generan riesgo de inundación y de basura por arrastre en caso de anegamiento.

La zona de Villa Moisés presenta una alta concentración de vulnerabilidades asociadas a la ausencia o insuficiencia de infraestructura urbana básica. En el área relevada se observa una combinación de iluminación pública deficiente, alta presencia de microbasurales, baja disponibilidad de contenedores para residuos y escasa presencia de arbolado público. La superposición espacial de estas variables sugiere un patrón de acumulación de déficits urbanos que podría incrementar la exposición de la población a distintos riesgos ambientales y afectar la calidad del espacio público.

En comparación con Villa Moisés, la situación del Esfuerzo Propio resulta ventajosa, ya que allí se observa una mayor concentración de bienes y servicios públicos en comparación.

Sería interesante correlacionar la presencia de mini basurales con servicios de recolección de residuos. La concentración de desventajas y la menor provisión de servicios públicos dan cuenta no sólo de que se trata de un lugar de habitación reciente, sino también con acceso diferencial a bienes y servicios esenciales que deben ser garantizados por el Estado.

En este punto el indicador de distribución de luminarias resulta particularmente ilustrativo y predictor de otras carencias de infraestructura.

Sería interesante verificar si la distribución desigual de arbolado en la zona sur de la ciudad es indicador de desigualdad territorial con islotes de calor (como ocurre en Córdoba) y mayor riesgo para el bienestar de los habitantes durante olas de calor o si la cercanía con la zona rural opera como factor protector o si responde a un déficit de relevamiento.

Las calles con mayor deterioro con Eva Perón y Marenguini. Particular esta última fue objeto de reparaciones por parte de los vecinos (con elementos de relleno, en especial de material de obra) que dificultaron aún más la circulación. Las zonas con presencia de árboles en calles Perón, Berti, Carelli y Pasaje Río V podría corresponderse con el plan de árboles entregados por Maná. Esto es una presunción que debería comprobarse.

Se observa una correlación entre las zonas problemáticas (falta de luminarias, mal estado de las calles, mini basurales, problemas de desagües y zonas inundables) con los puntos relevados. La comunidad demuestra un gran conocimiento del barrio y es capaz de ayudarnos a navegar por él y a producir información útil para el abordaje de la problemática de interés.

Se encontró una correspondencia entre las zonas identificadas como inundables y la presencia de desagües obstruidos. En estas áreas también hay una concurrencia de menor presencia de luminarias.

Conclusiones

El relevamiento realizado puso de manifiesto la importancia del conocimiento local para orientar tanto la definición de los problemas a relevar como la interpretación de los datos obtenidos. En este sentido, no resulta suficiente contar únicamente con profesionales especializados en sistemas de información geográfica o personas capacitadas en tareas de mapeo. Son los propios vecinos quienes conocen las dinámicas cotidianas del territorio, identifican los problemas que afectan su calidad de vida y pueden aportar información que difícilmente sería captada mediante otras metodologías. Por ello, su participación en las tareas de relevamiento debe constituir un componente central de este tipo de iniciativas.

Asimismo, el proceso de mapeo se consolidó como una herramienta de participación y diálogo comunitario. Las personas del barrio que participaron del relevamiento comprendieron rápidamente el potencial de estas tareas para visibilizar problemáticas locales y generar evidencia útil para promover mejoras en las condiciones de vida del barrio. En varios casos, los participantes ya contaban con experiencia en procesos de diagnóstico participativo, lo que probablemente facilitó la apropiación de la metodología y la comprensión del valor estratégico de producir información georreferenciada.

En este punto, la elección de herramientas que por diseño facilitan la participación local resulta crucial. Tanto aquellas que permiten interactuar con los mapas usando papel, que por ser una técnica que durante años se usó para poner en diálogo saberes locales (SketchMap Tool), como aquellas que por sus características se montan sobre tecnologías y conocimientos previamente adquiridos (ChatMap) resultan centrales para poder obtener resultados que incluyan diversas perspectivas y que además puedan favorecer la incidencia. Una etapa igualmente importante consiste en la devolución de los resultados a la comunidad y a las organizaciones que participaron del relevamiento.

Compartir los datos y el informe final no solo constituye una práctica de devolución ética hacia quienes hicieron posible el trabajo, sino que también fortalece las capacidades locales para utilizar esa información como insumo para el diseño, la demanda y el seguimiento de políticas públicas. En este aspecto, resulta especialmente destacable el papel de las organizaciones con arraigo territorial, particularmente Maná, cuya capacidad de sostener iniciativas a lo largo del tiempo y de movilizar a la comunidad constituye un activo fundamental para impulsar procesos de transformación local.

En este punto, sería interesante poder generar instancias similares en otras áreas de la ciudad con riesgo de anegamiento. Y alertar a defensa civil sobre las capacidades de las herramientas de mapeo ante emergencias y catástrofes. Así mismo, hacer llegar al municipio los relevamientos vinculados a desagües obstruidos, luminarias y mini basurales, puede redundar en una reducción del riesgo ante eventos especialmente fuertes, más teniendo en cuenta que la ciudad de Venado Tuerto forma parte de una cuenca que a menudo se caracteriza por la recepción de lluvias abundantes y arrastre de áreas aledañas. Resultando las poblaciones y viviendas de barrios populares especialmente afectadas durante estos fenómenos.

Finalmente, el relevamiento también permitió observar que las capacidades de organización y participación comunitaria se encuentran estrechamente vinculadas con la presencia sostenida del Estado en el territorio. Las áreas que históricamente han recibido infraestructura, equipamiento urbano y servicios públicos presentan, en términos generales, mejores condiciones materiales, mayores niveles de organización colectiva y una mayor capacidad para participar en este tipo de iniciativas. En contraste, los sectores de ocupación más reciente de Villa Moisés evidencian mayores niveles de vulnerabilidad y una inserción más precaria en las redes comunitarias existentes. Incluso cuando muchas de las familias que allí residen mantienen vínculos de parentesco con habitantes históricos del barrio Esfuerzo Propio, persisten procesos de diferenciación territorial y estigmatización que dificultan su integración plena a la vida comunitaria. Estas observaciones refuerzan la necesidad de comprender las desigualdades urbanas no solo como déficits de infraestructura, sino también como expresiones de trayectorias diferenciadas de presencia estatal, reconocimiento social y acceso a recursos colectivos.

OsmAnd: Planning a Day on the Water with Nautical Maps

2026-06-26T00:00:00+00:00

Some trips exist first as an idea. You open a map, find a coastline, and start building something in your head — a route, a few stops, maybe a harbor where you'd want to spend the evening. A principality of your own, even if just for a week. Principality of Monaco takes that idea literally. In summer the water gets crowded quickly — and what looks like open space from the shore has its own logic underneath. Shallow patches, restricted zones, boats coming and going from every direction. You don't notice any of it until you're already in the middle of it.

A regular map won't tell you any of that. Roads, buildings, points of interest — useful on land, but the moment you're moving on water, the map needs to change completely.

This is what OsmAnd's Nautical Map View is for. Depth data, seabed information, navigation lights, buoys, fairways — the kind of detail that turns a general-purpose app into something you can actually use on the water. Whether you're planning a route along the Côte d'Azur or just trying to find a safe place to anchor for the night, it starts with a different kind of map.

Photo by Wyatt Simpson on Unsplash

Switch to Nautical View

Port Hercule has that quality of feeling both glamorous and impossibly tight. Yachts moored so close you could step from one deck to another, ferries cutting through the same water, tour boats circling. Once you clear the breakwater and the harbor opens up behind you, the relief is immediate. Open sea, room to breathe, and Corsica somewhere ahead on the horizon.

Before anything else, you need the Nautical Map View plugin. Open the Plugins section in the main menu, find it in the list, and enable it. Then download the nautical maps for your region. You'll find them in Maps & Resources under the Nautical maps section. With that done, open Configure map, find Map style (Map type), and switch to Nautical. Land becomes yellow, shallow water light blue, deeper water progressively darker. The coastline becomes the primary reference line, exactly as it should be when you're navigating by sea.

For open water passages, there's also the Marine style in the same menu. It adds colored sector lights around lighthouses, INT-1 light characteristics for each beacon, and a rendering closer to what you'd find on a professional electronic chart. Both styles are part of the same plugin — switching between them takes seconds depending on whether you're in a harbor or crossing open sea.

Understand Depth and Seabed

The Mediterranean between Monaco and Corsica looks uniform from the surface — deep, open water with nothing obvious to avoid. But the seabed tells a different story. Depth changes quickly near the Ligurian coast, and some areas that appear safe on a general map become more nuanced when you have actual numbers in front of you.

On the nautical map, depth appears in two ways. Depth points are individual numbers scattered across the water, each showing the shallowest measured depth at that exact location — all values in meters. Depth contours connect points of equal depth into lines, giving you a clearer picture of how the seabed rises and falls across a wider area. Together they turn a flat blue surface into something with actual shape.

You can download both separately in Maps & Resources under Nautical maps — depth points by hemisphere, depth contours by region. Once downloaded, they appear on the map automatically.

Below the water, the seabed itself also has a character. Rocky bottom, sand, gravel, silt, coral — each behaves differently for anchoring, and in shallow areas, composition matters. In Configure map, the Seabed detail option controls how much of this is shown. Simple displays the basic seamark symbols. Category adds the type of material. All shows every qualifier the data contains — texture, density, biological classification. For most passages, Simple or Category is enough. All becomes useful when you're choosing where to anchor for the night.

Spot What Guides You

Open water has its own system of signs. Not road signs or street names — lights, shapes, and colors that tell you where the safe water is, where the channel runs, and what to avoid. Once you know what to look for, the map starts reading differently.

Lighthouses appear on the nautical map as distinct symbols along the coastline. Between Monaco and Corsica, Cap Corse at the northern tip of the island is one of the most prominent marks on this stretch. In Configure map, the Light detail option controls how much information is shown next to each lighthouse or beacon. Simple displays the name and basic light characteristic. Sectors adds the full arc geometry — colored wedges showing exactly which direction each light is visible from.

Buoys mark the edges of channels, isolated dangers, and safe water. Each has a shape, color, and often a light pattern, all encoded as seamark symbols on the map. The full range of buoy types is covered in the map legend, and with the Nautical or Marine style active, they appear exactly where they are in the water.

Together, lighthouses and buoys turn the open stretch toward Corsica from a blank blue space into a readable sequence of reference points — each one telling you something specific about where you are and where to go next.

Plan a Safe Route

Corsica is about 170 kilometers from Monaco — open Mediterranean the whole way, no channels to follow, no mapped waterways to route along. This is where the choice of navigation profile matters.

The Boat profile in OsmAnd is designed for rivers, canals, and marked fairways. For open water like this crossing, it's not the right tool — the data simply isn't there. Instead, switch to Direct-to-point routing. It navigates in a straight line toward your destination without relying on mapped waterways, which is exactly what open sea navigation requires. To enable it, activate the Boat profile in the app settings, then select Direct-to-point as the routing type.

With depth contours visible on the map, the route becomes more than just a line from A to B. You can see where the seabed rises toward the Corsican coast, where shallow areas begin near the approaches to Bastia or Calvi, and adjust your course before you're anywhere near them.

Two additional settings help here. Spot sounding distance controls how frequently depth points appear on the map — a smaller value means more numbers visible at once, useful when approaching a coast. Safety depth contour lets you set a threshold — say 5 meters — and highlights that contour line on the map so it's immediately visible against everything else. The map doesn't make decisions for you, but it gives you what you need to make them yourself.

From Open Water to a Clear Path

The open sea eventually gives way to the silhouette of the Corsican coast. As you approach the island, the empty spaces on the map shift back into a detailed network of seamarks, safety contours, and harbor lights. Navigation changes from long-range planning to precision tracking, but the tools remain exactly the same.

What makes this system work is that the water is never completely empty of data. The nautical charts in OsmAnd are based on OpenSeaMap, a crowdsourced project where sailors, skippers, and developers from all over the world contribute real-time geographic information. Every beacon, depth contour, and restricted zone is part of a constantly evolving database built by the people who actually use these waters.

When you navigate with OsmAnd, you are not just using a static piece of software — you are looking at a collaborative map that turns the unpredictable surface of the water into a structured, reliable path.

Setting Your Own Course

Before you weigh anchor for your next coastal journey, it is worth exploring the finer details of marine navigation. You can discover every map symbol, attribute, and advanced configuration in our full Nautical Map View documentation. Once you have studied the charts, try your hand at our interactive quiz to see if you can distinguish a safe fairway from a shallow risk.

Out there on the Mediterranean, the water stops being an unpredictable obstacle — it becomes a route you can confidently read and follow.

We appreciate your interest in us and thank you for taking the time to read this article. Join us on social media to keep up to date with the latest news and share your experiences. Your opinion is important to us.

Follow OsmAnd on Facebook, TikTok, X (Twitter), Reddit, and Instagram!

Join us at our groups of Telegram (OsmAnd News channel), (EN), (IT), (FR), (DE), (UA), (ES), (BR-PT), (PL), (AR), (TR).

OpenStreetMap User's Diaries: addr:all, full の解体

2026-06-25T10:37:17+00:00

addr:full
addr:all

大規模に解体（addr:*に階層化）した。

対象データ

1. 会津若松インポート

osm.org/node/1996645165/history/3 のように、2017年6月に取り込まれた公共系施設のデータである。 phoneが0始まりなのはさておき、speciality（現在推奨 healthcare:speciality）と、addr:allがある。これらを、現在標準のタグ群に置き換えをした。

2. 佐久市インポート

osm.org/changeset/149638948 のように、2024年4月にPlateauインポートで珍しく住所データも取り込まれた事例である。市域の全家屋にaddr:full形式で住所データが保有されていた。過去形である。

解体作業

使ったツールは、OverpassTurboとLevel0エディタ、そしてサクラエディタである。作業方式は以下の2パターン。

会津若松の諸データ: OverpassTurboで抽出→iDで周辺含めて精査
佐久の住所データ: OverpassTurboで抽出→Level0に流し込んでテキストデータ化→サクラエディタで正規表現によるreplace→Level0でコミット

OverpassTurboの抽出クエリは以下の通り。

会津若松作業時
nwr["addr:all"]({{bbox}});
(._;>;);
out meta;

佐久市作業時
nwr["addr:full"]({{bbox}});
out meta;

サクラエディタの正規表現replaceは以下の段階による

OverpassTurboからOSMファイルをエクスポートしLevel0にAddFileする

置換対象：addr:full = 長野県佐久市内山
置換後：addr:province = 長野県\r\n  addr:city = 佐久市\r\n  addr:neighbourhood = 内山\r\n  addr:block_number = 
※抽出クエリの時点でneighbourhoodレベルを絞って処理を容易にした

置換対象：addr:block_number = ([0-9]+)-([0-9]+)
置換後：addr:block_number = \1\r\n  addr:housenumber = \2

特に、佐久での作業に際しては、wayを構成するNode情報をあえて取得しないことで、Level0エディタの受容データサイズに対してより多くのway情報を1パッチで流すことができた。

作業後のタグ構成

- postal_code
+ addr:postcode
- addr:all
- addr:full
+ addr:province county city quarter neighbourhood block_number housenumber

- speciality
+ healthcare:speciality

- name AA薬局BB店
+ name AA薬局
+ branch BB店

リンク

TagInfo addr:full addr:all addr:block_number

OverpassTurbo Level0

サクラエディタ

OpenStreetMap User's Diaries: Krim als Russland eingezeichnet?

2026-06-25T06:02:33+00:00

Hallo zusammen,

Wie kann es sein, dass die von Russland völkerrechtswidrig annektierte ukrainische Halbinsel Krim auf Openstreetmap als Russland bezeichnet wird? Damit wird der russische Landraub von OSM gestützt. Ich finde das skandalös.

OpenStreetMap User's Diaries: Street Name

2026-06-24T15:06:11+00:00

Some street name are not confirmed. Still figure out.

OpenStreetMap User's Diaries: SafeStreets, an update: a new scoring model and how it reads OSM now

2026-06-24T05:02:05+00:00

A while back I posted here about SafeStreets, a free walkability and pedestrian-safety scorer that runs on OSM for any address, with Nimman Road in Chiang Mai as the example. Since then the product has moved on in two ways that I thought I can share: the scoring model and how it reads OSM changed. My focus has shifted to the US, so most of what follows is about that, with a short note on the international path at the end.

What changed in the product

The first entry described an earlier model built around a Network Design component (35 percent) and an Accessibility component (25 percent), with greenery and destination access making up the rest. The composite is now four components on a 0 to 10 scale:

Daily Reach:40 percent. Proximity-weighted access to 7 service categories.

Street Safety: 30 percent. Now its own first-class component, a weighted-OR of a crossings grid against pedestrian separation, plus a speed-exposure proxy.

Transit Reach:15 percent. GTFS via Transitland, OSM stops as fallback.

Walking Comfort:15 percent. Sentinel-2 canopy, terrain, air quality (the one non-OSM component).

There is also a new 6-tier label on top of the number, from Pedestrian-first down to Hostile, so the score reads in plain language rather than just a figure.

How it reads OSM now

The bigger change is mechanical. In the first entry every score hit live Overpass inside an 800m and 1,200m query, which was slow and broke whenever Overpass rate-limited me. US scoring is now Overpass-free. I precompute the street and safety metrics from a planet extract onto an H3 resolution-9 grid (roughly 26 million hexes covering the US, about 0.1 km2 each), paired with a local OSM POI layer of around 2 million amenities. A US score is now a hex lookup plus a POI merge, no live API call.

The OSM tags doing the work, by component:

Daily Reach: shop=, amenity=, leisure=, healthcare=, classified into the 7 categories and scored by distance to nearest plus density. Street Safety: highway=crossing and footway=crossing for crossing coverage, sidewalk=* and highway=footway for pedestrian separation, and highway=* class plus maxspeed for speed exposure. Pedestrianized ways (highway=pedestrian, living_street) score highest. Transit Reach: highway=bus_stop, railway=station/tram_stop, public_transport=platform where GTFS is thin.

So OSM is still the backbone for everything except comfort. The precompute moved the reading from request-time to build-time.

The international path-Briefly

International addresses, including Southeast Asia, still go through live Overpass with an Overture POI backfill. Same tags and model, read live rather than from the precomputed grid.

A note on limits

The precompute is a snapshot, so a US crossing you tag today does not move the score until I rebuild the grid. And at res-9 the safety signal is per-hex, not per-point, so it answers “is this a walkable area” rather than door-level precision. Where sidewalks and crossings are tagged, the score tracks reality closely; where they are not, Street Safety leans on road class and understates well-mapped quiet streets. sidewalk=, crossing=, and lit=* on ways remain the tags that most directly move a score.

If a US street you know well scores in a way that feels off, that mismatch is the feedback I am looking for. None of this works without OSM. Thank you all.

OpenStreetMap User's Diaries: Změna perspektivy vidění mapy

2026-06-23T19:51:34+00:00

Navážu na předchozí blog, kde jsem psal o způsobu rozšíření reality statických map. Držím se přitom OpenStreetMap, protože má smysl pracovat s otevřenou a transparentní strukturou dat, která je sama o sobě dostatečně silná na to, aby unesla i další vrstvu interpretace.

OSM dnes aspiruje na mimořádně přesnou mapu světa. Čím víc detailů se do ní dostává, tím přesnější se zdá orientace, tím srozumitelnější krajina a tím užitečnější nástroj pro každodenní použití. Tato představa je jasná a intuitivní. Člověk vidí objekty, cesty, oblasti, místa a vrstvy a přirozeně je chápe jako mapu, která zpřesňuje obraz světa.

Při hlubší úvaze se ale ukazuje jiná rovina. OSM není mapa v původním smyslu zobrazení krajiny. Je to prostorová databáze popisující povrch světa.

Databáze nese informace o tom, že někde existuje cesta, lavička, zřícenina, kiosk, parkoviště, studánka nebo WC. Ukládá jejich polohu, tvar, návaznost i část jejich významu. Svět se díky tomu stává čitelným, měřitelným a sdíleným. V této chvíli je důležité připomenout, že mapu vždy někdo čte. Člověk, který se v prostoru pohybuje.

Lidská zkušenost se ale neodehrává v jednotlivých objektech. Ty slouží jako orientační body pro pochopení celku. Člověk se pohybuje v prostoru skrze situace. V jednom okamžiku řeší suchou cestu, jindy zavřenou hospodu, jindy návrat za tmy, jindy místo k odpočinku, klid, bezpečí, zážitek nebo orientaci v neznámu. Z toho mu v hlavě vzniká jiná vrstva reality, než jakou zachycuje samotná geoprostorová databáze.

Do mapové databáze lze přidávat další vrstvy dat. Počasí, dopravu, otevírací doby, sezónnost, ceny pohonných hmot, dostupnost služeb, turistický tlak, uzavírky, kulturní program nebo lokální nabídku. Každá z těchto vrstev má vlastní strukturu i význam.

Klíčový moment nastává ve chvíli, kdy se tyto vrstvy potkají v konkrétním místě a čase. Vzniká situace. Cesta v dešti, hospoda ve vsi, zavřená pumpa, večerní čas nebo omezená konektivita datové sítě. Soubor faktů se mění v obraz prostředí, ve kterém probíhá lidské rozhodování.

Tím se mění samotná role mapy. Tradiční přístup pracuje s otázkou, kde co je. Nový přístup stojí na otázce, co to znamená v této chvíli pro konkrétního člověka. Sdílený prostor se rozpadá na menší vrstvy a z nich se skládá nový celek, který už není obecný, ale situační. Místo statického zobrazení vzniká výstup, který má interpretační význam. Detail už není izolovaný prvek, stává se součástí širší situace.

Velké jazykové modely otevírají možnost tyto vrstvy spojovat do sémantických souvislostí. Kombinovat prostorová data, čas, kontext i lidské potřeby. Z mapového faktu se stává situace. Z množství informací se vybírá to, co má význam v konkrétní chvíli. Výstupem není mapa v tradičním smyslu, ale interpretace prostředí. Prostor se mění na pole významů, které reaguje na čas, pohyb i záměr.

Tento posun mění pojetí GIS. Tradiční GIS popisuje prostor. Nová vrstva nad ním prostor interpretuje. Ukazuje, co v dané chvíli dává smysl, co přináší komfort, co nese riziko, co otevírá příležitost, co je dostupné a co vyžaduje rozhodnutí. Mapa se tím stává systémem porozumění situaci, ne jen zobrazením reality.

Dopady tohoto konceptu se netýkají jen technologií. Dotýkají se způsobu, jakým funguje místo k životu, cestovní ruch i místní ekonomika. Krajina, služby, infrastruktura, kultura i zkušenost lidí se propojují do jedné interpretovatelné vrstvy. Uživatel této nové vrstvy nedostává pouze body zájmu. Dostává kontext, který odpovídá jeho aktuální situaci.

Z mapového základu se tak stává kontextová informační struktura, která spojuje prostor, čas a význam. Obor GIS zůstává jako pevná kostra. Vedle něj vzniká vrstva, která přidává porozumění souvislostem. Znalost, kde co je, se rozšiřuje o schopnost rozumět tomu, co to znamená v konkrétní chvíli.

Změna, která z toho vyplývá, je jednoduchá v definici a zásadní v důsledcích. Místo otázek na polohu se objevují otázky na situaci. Místo mapy vzniká porozumění prostoru. Místo čtení krajiny přichází rozhodnutí.

OpenStreetMap User's Diaries: impressed

2026-06-22T20:58:48+00:00

I’m deeply impressed by Openstreetmap. And by some very active contributors near Leuven. But, do we really need trams in our lovely tiny city?

OpenStreetMap User's Diaries: CityMapper Externship 2026 UNGSC UN MAPPERS in Cameroon (first cohort)

2026-06-22T12:44:24+00:00

Hello OpenStreetMappers!

I am particularly proud to share with you today the complete results and highlights of the very first edition of the CityMapper Externship, held from April 10 to May 10, 2026, in Yaoundé, Cameroon.

Within the framework of the UN MAPPERS chapters initiative pilot project, I had the honor, as Ambassador, to lead this training, empowerment, and open data utilization initiative by young Africans to solve our challenges and improve the global map. This intensive immersion program was designed to train a new generation of urban mappers while producing open, sustainable, and high-quality geospatial data for our cities.

🛠️ One Month of Immersion: From Virtual Sprints to the Field Over four weeks, around thirty young people from French-speaking Africa (15 in-person in Yaoundé and 20 participating online from Togo, Senegal, and France) followed a progressive and intense path:

Initial Training: Mastering core open mapping tools (JOSM, HOT Tasking Manager, Mapillary, EveryDoor).

Remote Sprints: Mapping buildings and road networks across 8 HOT Tasking Manager projects linked to humanitarian missions.

Field Collection: Mapping the University of Yaoundé I campus and the city streets using EveryDoor and Mapillary.

Training session in April 11, 2026, held at Yaoundé Diver City Space.

Thanks to this incredible collective energy, our cohort generated over 86,119 OSM edits and mapped 70,633 buildings! The relevance of this work is measured by its immediate, real-world impact: these quality datasets are already feeding the local UrbanSanity platform to optimize waste management planning and guide the placement of 60 waste bins for nearly 12,000 residents in Yaoundé.

🤝 Strategic Partners at the Core of the Action This initiative would certainly not have seen the light of day without the support of our partners who contributed heavily to its design and implementation. I would like to acknowledge them in the following order:

IVIDES DATA

GEOSM FAMILY

Geospatial Girls & Kids (GGK)

Humanitarian OpenStreetMap Team (HOT)

TOMTOM

On the methodological front, our collaboration with Dr. Raquel Dezidério Souto greatly strengthened the scientific rigor of the project. Her technical involvement and her experience-sharing—notably through her feedback on the African geospatial ecosystem published in her OSM diary—provided a solid foundation to guide the cohort’s efforts.

Launch of the CityMapper Externship on 10 April 2026, Yaoundé Diver City Space.

🚀 Next Steps The success of this pilot project paves the way for a larger-scale deployment. Our roadmap is outlined as follows:

Geographical Replication: Expanding the program to the cities of Douala, Bafoussam, and Bamenda in Cameroon, before supporting pilot chapter initiatives in Kenya, India, and Argentina.

Technical Advancement: Transitioning participants from data creation to advanced expert-validator skills on OSM.

UN Mappers Incubator: Supporting cohort alumni in developing local tech solutions addressing sanitation, water access, and public health challenges.

The complete open deployment guide remains fully accessible to any OSM community looking to replicate this model.

📖 Explore our Deployment Guide on the OSM Wiki

📸 Access the official Photo Album

Thank you all, and long live open, community-driven mapping led by African youth! Modo Levo Engelbert Steve

UN Maps Ambassador – Cameroon & Project Coordinator

OpenStreetMap User's Diaries: Adding amenity around Alor Setar area

2026-06-22T01:14:14+00:00

If I’ve spare time to do this, I’ll do the update

OpenStreetMap User's Diaries: Cycling Frustration

2026-06-21T19:07:27+00:00

I joined this site due to cycling. My tracking app (Strava) uses Open Street Maps. One of my cycling goals was to ride every street in my city, which is difficult enough without mapping errors. I kept seeing “roads” on this map that are in reality private driveways, “public” roads that are actually private, and some roads that exist in reality but aren’t on the map yet. (And in one case, a road on the map that has never existed in reality.)

I haven’t yet figured out how to accurately add missing roads, but I’m trying to make the map better by correcting these other features.

OpenStreetMap User's Diaries: Quay trở lại 🤡

2026-06-21T16:23:25+00:00

Lần này tôi sẽ quay trở lại và làm vài trò vè sửa đổi nhắng nhít và ko thường xuyên cho lắm. (Chẳng ai quan tâm đâu 🐒). This time I’ll be back with some silly, occasional edits. (Nobody cares anyway 🐒)

OpenStreetMap User's Diaries: Two Days of Mapping Chitlapakkam & Tambaram #WeekendMapping

2026-06-21T16:06:53+00:00

So this weekend (20/06 - 21/06) I went full mapper-mode around Chitlapakkam and Tambaram. Grabbed my phone, walked around the neighbourhood, spent hours on my laptop for mapping and ended up with 18 changesets and ~96 edits over two days. Honestly, some of this should’ve been there years ago.

🏛️ Civic & Government Infrastructure

Starting with the obvious ones. The T13 Police Station and the Tambaram MLA Office, two places people actually need to find were nowhere on OSM. Not a node, not a building outline, nothing. Fixed that.

Also noticed the Sembakkam Zone 3 MCC was still tagged as whatever it used to be. It’s a municipal transit yard now. Updated accordingly.

⛽ Fuel & EV Infrastructure

The Shell petrol complex nearby was not mapped and a bit of a mess. I added the following:

The petrol bunk as a proper node
The EV charging station within the complex
The convenience store attached to the forecourt

Also quietly deleted a defunct petrol bunk that closed down a while back. It was still sitting on the map doing nothing. Gone now.

The EV charger is probably the most useful addition here OsmAnd, Organic Maps and other navigation apps pull charging locations from OSM.

🛕 Religious & Community Spaces

Two temples in Chitlapakkam that have been around forever, but not on OSM. At all. They are now. Also added some metadata to a spiritual centre that was on the map but barely tagged (This was one of my first edits in OSM, when I started it 3 months back !!)

Oh, and the outdoor kids’ play area inside Chitlapakkam Park? Mapped. Families use it every single day and it wasn’t showing up anywhere.

🏥 Health & Financial Services

Walked around the Chitlapakkam surroundings and found a bunch of medical shops, a pharmacy counter, and a few bank branches that were missing. These are the places people search for when they actually need them. Added them all from the ground survey.

🍽️ Food & Local Businesses

Used MapComplete for two food-mapping sessions while walking around. It’s a great little tool, you open it, it shows you what’s unmapped nearby, you fill in the details on the spot. The guided form means you don’t forget any tags.

Walked. Mapped. Ate. (Okay maybe not in that order.)

🛣️ Road & Address Data Quality

Not everything is a shiny new POI. Some of the most useful edits were the boring ones:

Road surface types on local streets
House numbers from the boards outside homes
Building outlines traced from the survey

Every house number that gets added means one more address that a delivery app or navigation tool can actually find. Small edit, real-world impact.

Summary

Category	Changesets	Approx. Changes
Civic & Government	5	~20
Fuel & EV	4	~23
Religious & Community	3	~25
Health & Finance	2	~28
Food & Businesses	2	~11
Road & Address	4	~5
Corrections	3	~2
Total	18	~96

All of this is in the Chitlapakkam / Tambaram / Sembakkam belt, Chennai. If you’re in this area, your map got noticeably better this weekend.

Happy mapping 🗺️

OpenStreetMap User's Diaries: Sono nella top 100 dei mappatori di OpenStreetMap in Italia | Mappando la città di Piombino

2026-06-21T13:30:12+00:00

Sto mappando la città in cui abito, Piombino. Nella scorsa settimana ho aggiunto quasi 7000 punti tra marciapiedi, strisce pedonali, panchine, cestini, pali della pubblica illuminazione, etc.

Perché lo faccio? Beh, innanzitutto perché Google, con le sue politiche sull’accesso ai dati che sono stati volutamente aggiunti dagli utenti e non da Google stessa, può andare a fare in culo. In secondo luogo, anche se Piombino è una città relativamente piccola, voglio che abbia le mappe più dettagliate e accessibili possibile. Infine, dato che utilizzo OSM nei miei progetti, volevo restituire qualcosa alla comunità, spargendo anche la voce che esiste e che è importante aggiungere la propria attività non solo su Google Maps, ma soprattutto su OSM.

In questa prima fase sto aggiungendo punti a destra e a sinistra e credo di aver già fatto un buon lavoro. Le fasi successive, però, sono ancora più importanti: l’aggiunta dei metadati agli elementi mappati e la ricostruzione degli edifici da zero (questi ultimi sono stati mappati 14 anni fa).

E niente, mandate a fare in culo Google, monopolista di dati che non sono suoi. Contribuite ai progetti open source, che permettono alle persone di costruire nuovi progetti basandosi su di essi.

Classifica: https://osmstats.neis-one.org/?item=countries&country=Italy

OpenStreetMap User's Diaries: Validating for HOT - creative work

2026-06-21T10:43:53+00:00

Validating the work of others is important. I was creative in doing just that.

weeklyOSM: weeklyOSM 830

2026-06-21T10:35:47+00:00

11/06/2026-17/06/2026

[1] Some members of the French OSM group Mapadour (the Basque Country and the southern Landes)

Community

Alex Spritze has realised that Wikimedia Commons is probably a good source of geographical objects that are still missing from OpenStreetMap and has developed a workflow to find geospatial data on Commons using the PetScan tool.
Rtnf has developed a prototype interactive map that allows users to explore angkot (shared taxi) routes in Indonesia, combining routing data generated by BRouter with geographic data from OpenStreetMap.
The fire department in Talling, Germany is explicitly asking for an AED defibrillator logo, so they can be represented on OpenStreetMap. In the comments, people point to the defibrillator map created by the Polish OpenStreetMap community and mention that OsmAnd and CoMaps already display defibrillators. GeoMH also gave the newcomer a reference to the community wiki.
Grant Slater is raising funds to purchase the missing sheets from the complete historical 1:50,000 topographic map series of Zimbabwe (formerly Rhodesia), produced by the Department of the Surveyor-General and the Zimbabwean Air Force. Once purchased, he will process the maps and make them freely available online so that researchers, historians, genealogists, mappers, local communities, and anyone interested in Zimbabwe’s history can access them.
Internet Archive Europe reported (also shared on Mastodon) on a workshop held in Amsterdam titled ‘Maps are Infrastructure too’. The post emphasised the importance of OpenStreetMap as a knowledge commons and highlighted MapLibre as a key tool for digital sovereignty, arguing that open map infrastructure is essential for long-term public access and memory.

Imports

Kentoseth has published a detailed tutorial (also shared on Mastodon) on how to mass import address data into OpenStreetMap using JOSM. The guide covers data preparation using OpenAddresses.io, essential JOSM plugins such as conflation, and emphasises the importance of manual validation against local GIS sources.

Local chapter news

[1] In his diary entry, Emmanuel Arrechea reported on the wide-ranging activities of the French OSM group Mapadour (Basque Country and southern Landes). The group has been very active, having taken over 228,000 Panoramax images; it has supported European tourism and mobility projects such as Systour and Pyrénées4Clima, maintained local health data, and is mapping urban trees in Bayonne using open data.
Wikimedia Italia, the Italian local chapter of the OpenStreetMap Foundation, has recently published ► a new tile service with two layers in the hope that it will help both the mappers and the end users. You can check ► the terms of use on their wiki.
The OSM Training Working Group of FOSSGIS e.V. met ► in Berlin on 13 and 14 June to refine their concept for modular OpenStreetMap training. The group focused on target-group specific requirements and the best ways to teach community workflows and practical mapping skills.

Events

The State of the Map Colombia 2026 will take place as an in-person event on 3 and 4 July 2026 at the Faculty of Economic Sciences, National University of Colombia. The conference will include a scientific programme.Incidentally, the logo for SotM was designed ► by Mauricio Martínez and features the white-headed tamarin (Saguinus oedipus), a primate native to Colombia, whose face is incorporated into a map pin.

OSM research

Muki Haklay, Professor of Geographical Information Science in the UCL Department of Geography, and UCL alumnus Patrick Weber, have won the IEEE’s Pervasive Computing’s Test of Time Award for their 2008 paper on OpenStreetMap. The award honours the most influential papers that have had a lasting impact on pervasive computing over the past 25 years. Over the eighteen years since Muki’s paper was published the OpenStreetMap project, which was launched at UCL in 2004, has evolved into critical digital infrastructure that supports research, humanitarian response, navigation systems, smart cities, and countless location-based services.

Maps

mgeograficas has created a uMap showing the distribution of sedimentary deposits from the Quaternary period (most recent) and the Neoproterozoic era (oldest), in Campos dos Goytacazes, in the state of Rio de Janeiro (Brazil).
Julien Minet explained ► the cartographic generalisation techniques he used to create a high-quality printed forest map using QGIS and OpenStreetMap data. The project, which he also shared on Mastodon, covers advanced topics such as dynamic orientation of symbols and automated feature displacement using PostGIS.

OSM in action

El País published ► a detailed interactive map showing real estate prices in Spain at a street-by-street level. As noted by Alan Grant on Mastodon, the project uses OpenStreetMap data for geographical names (neighbourhoods and districts), although the required attribution is missing from the interactive map itself and only mentioned in the methodology section.
Longtrails.de is a new interactive planning tool for long-distance hiking in Germany, Austria, and Switzerland. As noted on Mastodon, the platform uses OpenStreetMap data for its maps and points of interest, allowing hikers to plan stages with distance and elevation calculations while encouraging community contributions to improve the data.
Tom Scott’s video ‘Why trains don’t usually crash into each other’ features a printed OpenStreetMap map (at the 17:19 mark) used to illustrate the UK’s rail network. As noted on Mastodon, the video serves as a positive example of proper attribution by a high-profile creator, including a link to the OSM copyright page in the description.

Open Data

The Museum of the History of Dnipro (Ukraine) has launched an interactive map of the city’s streets based on OpenStreetMap data. The resource, created as part of the ZMINA 2.0 project with European Union financial support, provides the history and explanations for over 500 of the streets renamed since 2014.

Software

Kai Johnson is investigating how much of the Overpass query language could be implemented using the QLever database.
OpenMapEditor has been relaunched as MapDraw, a free, open-source, local-first web editor for personal geographic data. The tool now supports contributing to OpenStreetMap directly from the map, adding nodes (benches, drinking water, bike parking, and more), and leaving notes. The source code is available under the AGPL-3.0 licence.
OSM MultiToolz (available for Chrome and Firefox) is a browser extension, built by dp7, designed to assist OpenStreetMap contributors. It provides advanced changeset analysis, integration with various QA tools (including OSMCha and Achavi), a smart watchlist for monitoring edits, and built-in translation for changeset comments.
VK Maps’ Overpass instance is once again available for use, after being shut down for several months.
Ian Wagner noted, on Stadia Maps’ blog, that the long-term viability of any motor vehicle routing project hinges on two ‘invisible’ variables: data privacy architecture and billing predictability.

Programming

Paco Albacete Chicano blogged that his Google Summer of Code project will focus on area routing in Valhalla. This is expected to allow routes to cross areas, such as public squares, directly instead of circling around them and producing inefficient or awkward paths.
Windows Central reported that rampant AI‑driven GitHub outages have forced Microsoft into an unlikely alliance with Amazon. GitHub processed 1 billion commits in 2025, compared to 14 billion expected in 2026.

Releases

Heise reported that Murena has released version 4.0 of its Google-free Android fork, /e/OS. The update includes Murena Maps v1.0.0-beta, powered by data from OpenStreetMap.
Sergey (enzet) released version 0.16.0 of Röntgen, a specialised icon set for OpenStreetMap. The update, announced on Mastodon, added 16 new community-requested icons (including various vending machines and railway features) and is now also available as an npm package.
osm2pgsql has released version 2.3.0, introducing major changes to tile expiry, a new style tester script, and numerous additional improvements.
iD version 2.41.0 has been released. Key updates include automatic data downloading when splitting ways in relations, a new marker-based rendering for embankments and cuttings, and improved Wikidata searches that now display item descriptions.

Did you know that …

… OpenCage has an extensive archive of their OpenStreetMap community interviews? The series started in 2014 and recent entries include conversations with Omran Najjar on OSM in Syria, Volker Krause about the open-source routing engine Transitous, and Christian Quest on the Panoramax Foundation.
… uMap now has ‘draw along route’ functionality? It’s great for creating OSM-routable routes.
… scy has shared some tips on how to customise OsmAnd’s map appearance to improve readability and accessibility. The settings, located in the main menu under ‘Customise Map’, allow users to adjust the contrast and line thickness, as well as switch between different map styles.

Other “geo” things

Christina Queiroz has explored how participatory and social cartography are being used as tools for rights advocacy and territorial claims. Their article highlighted projects such as the self-demarcation of the Borari people and the use of OpenStreetMap to map services in favelas, challenging official state narratives.
The YouTube channel Veritasium has published a video titled ‘Google Maps is unreasonably fast. Let me explain’, which explores the complex algorithms behind modern routing and navigation. As noted by Eugene Alvin Villar, on Mastodon, the video features impressive visualisations and makes extensive use of OpenStreetMap data, which is explicitly credited in the video’s description.

Upcoming Events

Where	Venue	What	When
		UN 2.0 Week 2026: UN Mappers Mappy Hour	2026-06-19
بلدية دمشق القديمة	Online	ReMapping Syria 2025: Humanitarian Mapping & Community Collaboration Webinar	2026-06-19
		UN Mappers Mappy Hour: Progress and Highlights of the UN Maps Community Ambassador Pilot Initiative	2026-06-19
Torino		OpenStreetMap Mapping Party: Torino at a walking pace!	2026-06-19
Stuttgart	Technische Hochschule Stuttgart	Missing Maps Mapathon in Stuttgart	2026-06-19
València	Facultat de Geografia i Història	Mapatón EGEA València para beginner	2026-06-19
Potsdam	Waschbar	Potsdamer Mappertreffen	2026-06-19
Catania	@Localhost	Modifichiamo Wiki e OSM insieme!	2026-06-19
Metz	l’Arob@se	Atelier du groupe local de Metz – Partez en voyage avec OpenStreetMap	2026-06-20
	Mitarbeiterparkplatz antonius, Fulda	Sommermapping 2026	2026-06-21
Pune	Cafe Coffee Day, MG Road, Pune	OSM Pune Mapping Party	2026-06-21
		Missing Maps : Mapathon en ligne – CartONG [fr]	2026-06-22
Stadtgebiet Bremen	Online und im Hackerspace Bremen	Bremer Mappertreffen	2026-06-22
		Missing Maps Validathon	2026-06-23
Magdeburg	Netz39 e.V. , Leibnizstraße 32, 39104 Magdeburg	2. OSM Stammtisch Magdeburg	2026-06-23
Windsor	Ford City	OSM Field Mapping: Ford City	2026-06-23
Berlin	Online	OSM-Verkehrswende #76	2026-06-23
Würzburg	FabLab Würzburg	Würzburger OSM-Treffen	2026-06-24
		Mapping missing buildings in La Paz, Bolivia	2026-06-25
Freiburg im Breisgau	CCCFR, Adlerstr. 12a, Freiburg/Brsg.	OSM-Treffen Freiburg im Breisgau	2026-06-25
Dar es-Salaam		State of the Map Africa 2026	2026-06-26 – 2026-06-28
	[online]	Capacitação OSM 2026 – IVIDES DATA ® – Formulários Web com KoboToolbox	2026-06-26
		OSMF Engineering Working Group meeting	2026-06-26
Düsseldorf	Online bei https://meet.jit.si/OSM-DUS-2026	Düsseldorfer OpenStreetMap-Treffen (online)	2026-06-26
Москва	Москва	Московская картопати	2026-06-27
	Biblioteca Alda Merini in via Edmondo De Amicis	Mapathon @ Casorate Sempione	2026-06-27
		OSM Mumbai Mapping Party No.11 (Trans-Harbour Line – South)	2026-06-27
Hannover	Kuriosum	OSM-Stammtisch Hannover	2026-06-29
Saint-Étienne	Zoomacom	Rencontre Saint-Étienne et sud Loire	2026-06-29
Heidelberg	DEZERNAT#16	Rhein-Neckar OSM Treffen	2026-06-29
		Webinaire en ligne – Hydrants, armoires de rue, poteaux et bâtiments de service	2026-06-30
Braunschweig	Stratum 0	Braunschweiger Mappertreffen im Stratum 0 Hackerspace	2026-06-30
City of Westminster	The Albert pub	London pub meet-up	2026-06-30
Derby	The Brunswick, Railway Terrace, Derby	East Midlands pub meet-up	2026-06-30
		iD Community Chat	2026-07-01
Stuttgart	Forum 3 Café, Gymnasiumstr. 21, 70173 Stuttgart	Stuttgarter OpenStreetMap-Treffen	2026-07-01
Žilina	Fakulta riadenia a informatiky UNIZA	Missing Maps mapathon Žilina #23	2026-07-02
Gent	Nerdlab	IntroLAB ✦ OpenStreetMap	2026-07-02
Angers	L’Arrière Train, 3 rue de Frémur, Angers	Angers : Rencontre mensuelle OpenStreetMap	2026-07-02
	Bar Le Schmilblik	Rencontre mensuelle des contributeurs Paris sud	2026-07-02
Bogotá	Universidad Nacional de Colombia	State of the Map Colombia (SotMCol) 2026	2026-07-03 – 2026-07-04
	[online]	Capacitação OSM 2026 – IVIDES DATA ® – Mapas Web com uMap	2026-07-03
नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2026-07-04

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

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

OpenStreetMap User's Diaries: Update of speed limit data in Arlington Heights, IL, part I

2026-06-20T17:59:53+00:00

completed survey of all speed limits in an area south of Palatine Road, east of Wilke, west of Arlington Heights Road and north of Euclid/Northwest Highway. Updated street data on the map.

OpenStreetMap User's Diaries: 尾張旭市内のバス停・バス路線のマッピングを進めています（2026年6月20日）

2026-06-20T13:07:31+00:00

愛知県尾張旭市内のバス停・バス路線のマッピングを進めています。コミュニティバス「あさぴー号」の停留所について不明点が残っているため、1週間以内に現地調査に行きたいです。また、瀬戸市内の商店街にある店舗についても、営業時間などの情報を調べてマッピングを進めていきたいと思います。

OpenStreetMap User's Diaries: Eurovelo 6 ne correspond pas à la référence du site EUROVELO

2026-06-20T10:55:17+00:00

bonjour, comment metre à jour le parcours eurovelo 6 qui n’es pas à jour ? ( peut-etre d’autres aussi, mais c’est celui que je fait en ce moment ) importer les traces GPX du site Eurovelo ne marche pas ( pb de dates dans fichiers) .

merci de vos commentaires

OpenStreetMap User's Diaries: 경주월드!!

2026-06-20T03:46:44+00:00

최근에 현체로 경주월드 다녀왔거든요? 가기 한 이틀 전에 osm 드가서 경주월드 편집하는데 타카티스크?? (2022년에 운행 중단) 서라벌관람차?? (2022년 8월에 철거) 처음 들어본 게 많아서 당황했습니다. (심지어 타카티스크가 아니라 타가디스코임) 어쨌든 중요한 지물들을 편집했습니다. (미로탐험 없애고, 타임라이더 만들고 등등) 근데 잼민이인 저 혼자 하긴 너무 힘든거 같아서 제발 도와주시면 좋겠습니다 ㅠㅠ

(아니 줄바꿈 왜 안돼;;)

OpenStreetMap Blog: 2026 Board Face-to-Face (F2F) in Madrid, Spain

2026-06-19T22:24:32+00:00

The OpenStreetMap Foundation (OSMF) Board of Directors is excited to share this blog post with all of our community members. From June 6th-7th, members of the Board of Directors Craig Allan (Chair), Dani Waltersdorfer Jimenez (Secretary), Roland Olbricht (Treasurer), Héctor Ochoa Ortiz, Laura Mugeha, Maurizio Napolitano, and facilitator Allen Gunn (also known as Gunner), met for two full working days in Madrid to discuss and tackle priorities and action items that need to be accomplished in the next 12 months. Amongst the discussed topics are a fundraising campaign, the “reviving” of the Communications Working Group (CWG), a new job posting which will be shared in the next coming months, the OSMF move to the European Union (EU), the launch of an Artificial Intelligence (AI) policy, and other topics. It is truly a pleasure to work with a team that is aligned on shared values including trust and respect, who are pushing for the success of a shared passion: the OpenStreetMap project. It must be noted however, that all of this could not have been possible without the leadership, patience, and tremendous organizational skills of Gunner who has been the OSMF facilitator for over 10 years. Thank you, Gunner!

What made this meeting particularly special is that we had the honor and pleasure of working from the TomTom offices in Madrid. We want to truly highlight our gratitude for TomTom for sharing their space with us, and most of all, we want to give a big shout-out to Priscilla Zachée for spending her weekend with us.

Face-to-face meetings are unlike others. For those who don’t know, us Board Members live in different countries all over the globe, so having the opportunity to work together, “ideate”, brainstorm, discuss tough topics, and enjoy our time together is quite treasured and important for us. And on the front of the importance of human connection, we promise to keep pushing forward the key that makes OpenStreetMap truly unique, unlike any other geospatial database out there: Our essence is our community.

We’d like to extend a thank you to all members of the community for your continued trust and passion for the OSM Project. We are always here for you should you have any questions or comments.

– The Board

OpenStreetMap User's Diaries: Learning to Use OpenStreetMap Plugins in QGIS

2026-06-19T16:47:32+00:00

– Leia em Português

IVIDES DATA® held the third session of the Ciclo de Oficinas OSM 2026 (or 2026 OSM Workshop Series), focusing on QGIS plugins. Applied cases were presented on accessibility, urban tree cover, and the geolocation of buildings on areas subject to disasters

Dr. Raquel Dezidério Souto leading Session 3 of the Ciclo de Oficinas OSM 2026. The files used in Workshop 3 can be found in the video description. Link

IVIDES DATA® successfully held the third live training session of the Ciclo de Oficinas OSM 2026 on June 12, during which the following were presented:

* View and download data on OSM.org

* Access to geoservices for loading OSM as a base layer - NextGIS QuickMapServices plugin

* Downloading data in QGIS (version 3.22 or later) – QuickOSM and OSM Downloader plugins

* Applied cases — accessibility, urban tree cover, and the geolocation of buildings on areas subject to disasters

QGIS screenshot showing data extracted using the QuickOSM plugin regarding government offices (blue dots) in Paris and its surroundings, highlighting those that are wheelchair-accessible (yellow dots) | Map data (c) 2026 OpenStreetMap contributors.

QGIS screenshot showing data extracted using the QuickOSM plugin on the location of trees in Paris, highlighting their concentration along major streets | Map data (c) 2026 OpenStreetMap contributors.

The Ciclo de Oficinas OSM 2026 offers single certificates (4 hours per session) and a full certificate (20 hours over five sessions). The training is open to all mappers, regardless of skill level.

To participate in the remaining sessions, please register using the form below to receive the link via email (you only need to register once):

https://framaforms.org/oficinas-openstreetmap-2026-ivides-data-r-1777150442

Thank you to everyone for participating!

The Ciclo de Oficinas OSM 2026 is organized by IVIDES DATA®, in partnership with the Institute of Geosciences at the State University of Campinas (Unicamp) in São Paulo, Brazil.

Links and credits:

Important note: IVIDES.org(TM) e IVIDES DATA(TM) are registered trademarks. OpenStreetMap(TM) is a trademark.

Para contato: ivides [at] ivides.org

https://ivides.org

OpenStreetMap User's Diaries: Aprendendo a utilizar plugins para OpenStreetMap no QGIS

2026-06-19T15:58:33+00:00

– Read in English

IVIDES DATA® realiza a terceira sessão do Ciclo de Oficinas OSM 2026, tratando de plugins para QGIS. Casos aplicados sobre acessibilidade, arborização urbana e localização de edificações em áreas de risco foram apresentados

Dra. Raquel Dezidério Souto conduzindo a sessão 3 do Ciclo de Oficinas OSM 2026. Os arquivos utilizados na oficina 3 podem ser encontrados na descrição do vídeo. Link

A empresa IVIDES DATA® realizou com sucesso o terceiro treinamento ao vivo do Ciclo de Oficinas OpenStreetMap 2026, em 12 de junho, quando foram apresentados:

* Consulta e download dos dados em OSM.org

* Acesso a geosserviços para carregamento do OSM como base layer (camada base) - plugin NextGIS QuickMapServices

* Download dos dados no QGIS (versão 3.22 ou superior) – plugins QuickOSM e OSM Downloader

* Demonstração de casos aplicados - acessibilidade, arborização urbana, edificações localizadas em encostas

Tela de captura do QGIS com dados extraídos com plugin QuickOSM sobre os escritórios governamentais (pontos azuis) em Paris e arredores, mostrando aqueles que possuem acesso a cadeirantes (pontos amarelos) | Dados do mapa (c) 2026 Contribuidores do OpenStreetMap.

Tela de captura do QGIS com dados extraídos com plugin QuickOSM sobre localização de árvores em Paris, mostrando a sua concentração em vias principais | Dados do mapa (c) 2026 Contribuidores do OpenStreetMap.

No Ciclo de Oficinas OSM 2026, são oferecidos certificados avulsos (4h/sessão) ou um certificado completo (20h/ cinco sessões). O treinamento é livre e para todos os níveis de mapeadores.

Para participar das demais sessões, realizar a inscrição via formulário abaixo, para receber o link por e-mail (basta se inscrever uma vez):

https://framaforms.org/oficinas-openstreetmap-2026-ivides-data-r-1777150442

Agradecemos a participação de todos!

O Ciclo de Oficinas OSM 2026 é promovido pela empresa IVIDES DATA®, em parceria com o Instituto de Geociências da Universidade Estadual de Campinas - Unicamp (São Paulo, Brasil).

Links e créditos do texto:

QGIS

https://qgis.org/

NextGIS QuickMapServices

https://plugins.qgis.org/plugins/quick_map_services/

QuickOSM (autor: Etienne Trimaille)

https://plugins.qgis.org/plugins/QuickOSM/

OSM Downloader (autor: Luiz Andrade)

https://plugins.qgis.org/plugins/OSMDownloader/

Nota importante: IVIDES.org® e IVIDES DATA® são marcas registradas. OpenStreetMap® é uma marca registrada.

Para contato: ivides [at] ivides.org

https://ivides.org

OpenStreetMap User's Diaries: Extracting Hiking Waypoints from OSM Map

2026-06-19T06:34:05+00:00

This is a very simple idea: given a set of GPX traces for a hike you are planning to take, generate a file containing all the waypoints of interest within the area covered by the GPX traces. I create a buffer around the GPX traces and extract the area from OSM. I define a set of tags of interest. I use Ollama with Mistral Nemo to make sure that POIs make sense to visit while walking on foot, as places are sometimes mislabeled in OSM. Before saving the waypoints to a GPX file, I use Ollama again to generate waypoint descriptions and set labels for each waypoint. Feel free to try it out! The code is on GitHub.

OpenStreetMap User's Diaries: Mental Health

2026-06-19T02:06:23+00:00

Mapping Sitka is pretty much my identity. I was upset when someone reverted my work because honestly I’ve been working every waking hour for a few months now. It was good though because I needed to step back and not take it too seriously. I’ve had some manic episodes late in life and they unlocked some anger I’m not familiar with. It was actually impressive how mad I got. Anyway, what are these diaries for if not a super personal post? Stay mappy people

OpenStreetMap User's Diaries: Anatomy of a revert on the servers

2026-06-18T22:59:26+00:00

Earlier today I had to check an alarm on the servers. The alarm was for a non-issue, but I happened to notice a momentary delay to replication across multiple services and I wanted to investigate.

The rendering servers fell up to four minutes behind on some servers, with all servers falling at least a minute behind normal. Interestingly, there does not seem to be a correlation between the delay and the server capacity.

The vector tile servers had a more obvious impact with one server falling 12 minutes behind and the other 23 minutes. This increased time is by design. The mod_tile rendering stack has less work to do on updates but it causes more work on future requests for tiles in the updated area. On the other hand, the tilekiln stack has more work to do on updates but subsequent requests to the area are actually slightly faster.

I checked the nominatim lag. The delay is barely discernable so I’m not including the graph.

Checking the minutely replication around the time shows that at 23:13 the replication diffs jumped in size, with 007130004 to 007130010 showing an increased size of 400 kB to 1000 kB. The minutely diffs are normallly under 50 kB.

I examined one of the diffs to see what user edited the most objects. The easiest way was with osmium show 008.osc.gz | grep user | sort | uniq -c | sort -h. This technique isn’t 100% reliable since a tag containing the string “user” would introduce extra results but it’s good enough for a quick manual look.

Immediately it was obvious that this was a revert being done by woodpeck_repair as they had over 100x as many changes than the next user. Looking at the changesets it was a revert of a bad import.

I still wanted to explore how this showed up on the vector tile systems. The changes came in every minute for several minutes. The graph shows 1. Normal updates before the large diffs, with only 60 seconds between updates 2. update 1 took longer, meaning after it happened it was slightly behind 3. update 2 merged the multiple diffs available. The are the diffs that accumulated between where the green and purple lines intersect below 1 and the purple and yellow intersection to the right. It looks like it updated two minute of data (red or blue lines) in about 4 minutes (time between “valleys”) 4. update 3 took those 4 minutes of new data and took 8 minutes. Looking at the diff size this is when the biggest updates happened 5. update 4 consumed those 8 minutes of data and processed them in 5 minutes 6. update 5 consumed the new 5 minutes of data in about 30 seconds 7. updates continued like normal.

Both axis are measured in time and the blue/red lines are how long it took an update to run. If you plotted the data on a graph where the axises were the same scale all the lines would be at 90 or 45 degrees.

The graph is approximate since updates only come out every 60 seconds and the data is updated every 15 seconds. Also it’s made in a drawing program, not properly graphed.

Looking into the logs I can see more detail about what’s taking the time.

The first large diff was picked up at 23:14:08 and

start time	# ways	osm2pgsql	building tiles expired	tilekiln time	backlog left
23:14:08	72056	72s	11391	17s	145s
23:15:40	161002	141s	12811	11s	234s
23:18:16	482221	426s	14158	14s	492s
23:25:40	277978	269s	13568	14s	357s
23:30:25	1225	1225	53	26s	0s

To my surprise, most of the time was spent in osm2pgsql processing ways, not in tilekiln. This means my strategies to minimize tilekiln processing are working.

OpenStreetMap User's Diaries: Translation of the FPOSM's ODbL license booklet to Swahili

2026-06-17T18:02:34+00:00

Editora IVIDES has published the Swahili translation of the FPOSM booklet on the ODbL license

Download SW VERSION

The original work Tout savoir sur la license ODbL : la licence d’OpenStreetMap pour cartographier en commun was written in French in 2024 and updated in 2026 by the Fédération des Pros d’OSM, a French organization that brings together various companies and professionals working with open data, OpenStreetMap, and related software. The authors of the original booklet are: François Lacombe (Datactivist), Florian Lainez (Jungle Bus), Antoine Riche (Carto’Cité) and Christophe Biez (Latitude-Cartagène Cartographies).

The translation to Swahili was done by Hemed Lungo and Tatu Sultan Lungo, from Tanzania, and the booklet was edited by Raquel Dezidério Souto (Editora IVIDES).

The work is licensed under the Creative Commons Attribution-ShareAlike 2.0 France (CC BY-SA 2.0 FR). Text of the license

Download EN VERSION

Download VERSÃO PT

Important note: OpenStreetMap® is registered trademark.

To keep contact: ivides [at] ivides.org

https://ivides.org

OpenStreetMap User's Diaries: OSM + Wikimedia Commons

2026-06-17T13:45:04+00:00

Manchmal ist Wikimedia Commons eine gute Quelle für Objekte, die in OpenStreetMap fehlen, und manchmal ist es umgekehrt.

Aber wie lassen sich Informationen aus beiden schnell verbinden und am besten noch visualisieren?

Der naive Ansatz

💡 Daten per Abfrage aus Commons und OSM holen und in uMap anzeigen.

🏁 Als Beispiel möchte ich hier alle Ortseingangsschilder aus Sachsen-Anhalt visualisieren.

Naiv bedeutet hier natürlich auch, dass in Commons nicht alle Bilder ihre Standorte koodiert haben.

Wikimedia Commons mit PetScan abfragen

Wikimedia Commons bietet mit PetScan ein Tool an, das unter anderem auch nach KML exportiert. Ein Dateiformat, das nach uMap importiert werden kann. Folgende Parameter erzeugen in PetScan nach einem Klick auf “Do It” eine KML-Datei mit den entsprechenden Geo-Informationen:

Parameter	Wert
Language	commons
Project	wikimedia
Depth	1
Categories	`Zeichen 310 in Saxony-Anhalt`
Page Properties: Namespaces	Commons, File
Output: Format	KML
Output: Page Metadata	Image, Coordinates, Default sort

Wichtig ist auch Depth auf größer 0 zu setzen, damit untergeordnete Kategorien miteinbezogen werden, so dass z.B. auch Ortseingangsschilder aus dem Saalekreis gefunden werden.

Der Inhalt der KML sieht dann ungefähr so aus:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
  <Document>
    <Placemark>
      <name>Hundeluft.jpg</name>
      <ExtendedData>
        <Data name="url">
          <value>https://commons.wikimedia.org/wiki/File%3AHundeluft%2Ejpg</value>
        </Data>
      </ExtendedData>
      <Point>
        <coordinates>12.34471667, 51.96599722, 0.</coordinates>
      </Point>
    </Placemark>
...

Falls die Datei im Browser angezeigt wird, muss man sie natürlich noch lokal speichern.

OSM Daten in uMap anzeigen

Ich springe jetzt direkt zu uMap, da dort die Daten aus OpenStreetMap per Overpass Query bezogen werden. Das passiert über den Import-Assistent (geht wohl mit Strg+I):

Parameter	Wert
Ausdruck	`traffic_sign=city_limit`
Geometriemodus	Standard
Suchgebiet	`Sachsen-Anhalt`

Da ich als Wikimedia Commons Kategorie Zeichen 310 in Saxony-Anhalt habe, nehme ich den entsprechenden OSM-Tag traffic_sign=city_limit. Das wird aber auch Zeichen 311 (“Ortsausgangsschilder”) finden. Nicht schlimm, da sie doch so gut wie immer zwei Seiten haben. Der Tag traffic_sign=DE:310 wird wohl nur 533 mal genutzt, da sind wir auch auf der sicheren Seite.

Die Ergebnismenge dieser Abfrage kann dann in eine neue Ebene kopiert werden. Aktuell scheint die Option “Link zur Ebene als Remote-Data” nicht zu funktionieren.

Fazit

🌏 Im Ergebnis überwiegt die Anzahl der kartierten Ortseingangsschilder aus OSM (6353 blaue Fähnchen) die Anzahl der Bilder aus Wikimedia Commons (89 rote Fähnchen).

Fehlen die Geo-Information am Commons-Bild, taucht es in dieser Karte natürlich nicht auf. Wir haben mit diesem Weg auch keine Möglichkeit direkt zu sehen, welche Commons-Bilder fehlen.

Aber falls man das spezielle Hobby oder die ausgeprägte Sammelleidenschaft hat, Ortseingangsschilder zu fotografieren und nach Commons hochzuladen, weiß man jetzt wo noch viel Arbeit wartet (Landkreise Börde und Stendal) und könnte vielleicht mittels BRouter auch gleich eine 🚴‍♂️ Route planen. Doch dazu vielleicht später mehr.

Das Fazit in einem Satz lautet wohl, dass OpenStreetMap eine wirklich schönes Biotop an Daten und Anwendungen geschaffen und ermöglicht hat. 💖

PS: wie bindet man am einfachsten Bilder in OSM-Blogeinträgen ein?

OpenStreetMap User's Diaries: The pursuit of 'Top VIP Contributor"

2026-06-17T01:49:26+00:00

I’ve been reflecting on the balance between mapping for ‘volume’ and mapping for ‘precision.’ While I understand the value of quick, large-area edits for global visibility, I find it a bit puzzling when polygons are generalized to the point of overlapping everything in sight—especially when high-resolution imagery is available.

I’ve noticed a trend where edit counts are sometimes treated as the ultimate metric of a mapper’s worth. I reckon we should be careful not to let the pursuit of ‘top contributor’ stats overshadow the primary goal of creating a detailed, accurate map for everyone. For me, a well-traced building or a correctly aligned path is worth far more than a high edit count achieved through imprecise mass-mapping. I’m always keen to learn the best practices, so if there’s a standard way to maintain precision while contributing efficiently, I’m all ears. Cheers.

OpenStreetMap Blogs

OpenStreetMap User's Diaries: BUSPLAN ZA BANJA LUKU

OpenStreetMap User's Diaries: Mejores deseos

OpenStreetMap User's Diaries: [GSoC] Prototyping medial axis implementation for area routing

Algorithm overview

1. Building the polygon

2. Voronoi generation

3. Pruning dead branches

4. Extra implementations

Conclusion

OpenStreetMap User's Diaries: Культурное наследие.

OpenStreetMap User's Diaries: Globe Meet-up last time. Albert pub tonight

Geofabrik: New in OSM Inspector: Turn Restrictions

OpenStreetMap User's Diaries: 广州地铁、广佛地铁和广东城际车站的出入口名称

查找

OpenStreetMap Blog: State of the Map 2026: Call for Posters

OpenStreetMap User's Diaries: Tile server for toll roads, cycling restrictions and cobblestone overlays

OpenStreetMap User's Diaries: Sobre OSM for Cities

OpenStreetMap User's Diaries: About OSM for Cities

OpenStreetMap User's Diaries: Sobre o OSM for Cities

OpenStreetMap User's Diaries: How to add anchor portals correctly

Pascal Neis: Checking OpenStreetMap Notes for Potentially Problematic Language

weeklyOSM: weeklyOSM 831

About us

Community

OpenStreetMap Foundation

Events

Education

Maps

OSM in action

Software

Did you know that …

Other “geo” things

Upcoming Events

OpenStreetMap User's Diaries: Percy, Illinois

OpenStreetMap User's Diaries: Supermarchés à Genève de A à Z (ou plutôt de A à M)

Les enseignes

Aperçu

Tags dans OSM

Résumé des enseignes

Carte

Autres

OpenStreetMap User's Diaries: Documenting POI cluster — 8 offices in 100-mile NC corridor

OpenStreetMap User's Diaries: Cross-checking phone formatting on 8 LCC nodes — E.164 vs US-local

OpenStreetMap User's Diaries: Proposing description tag conventions for small-business offices in NC

OpenStreetMap User's Diaries: Adding cuisine and shop-tag context for 8 trade-business nodes in NC

OpenStreetMap User's Diaries: Informe de actividad de mapeo en campo: Esfuerzo Propio y Villa Moisés

Informe de actividad de mapeo en campo para prevención de inundaciones: Esfuerzo Propio y Villa Moisés

OsmAnd: Planning a Day on the Water with Nautical Maps

Switch to Nautical View​

Understand Depth and Seabed​

Spot What Guides You​

Plan a Safe Route​

From Open Water to a Clear Path​

Setting Your Own Course​

OpenStreetMap User's Diaries: addr:all, full の解体

対象データ

1. 会津若松インポート

2. 佐久市インポート

解体作業

作業後のタグ構成

リンク

OpenStreetMap User's Diaries: Krim als Russland eingezeichnet?

OpenStreetMap User's Diaries: Street Name

OpenStreetMap User's Diaries: SafeStreets, an update: a new scoring model and how it reads OSM now

OpenStreetMap User's Diaries: Změna perspektivy vidění mapy

OpenStreetMap User's Diaries: impressed

OpenStreetMap User's Diaries: CityMapper Externship 2026 UNGSC UN MAPPERS in Cameroon (first cohort)

OpenStreetMap User's Diaries: Adding amenity around Alor Setar area

OpenStreetMap User's Diaries: Cycling Frustration

OpenStreetMap User's Diaries: Quay trở lại 🤡

OpenStreetMap User's Diaries: Two Days of Mapping Chitlapakkam & Tambaram #WeekendMapping

🏛️ Civic & Government Infrastructure

⛽ Fuel & EV Infrastructure

🛕 Religious & Community Spaces

🏥 Health & Financial Services

🍽️ Food & Local Businesses

🛣️ Road & Address Data Quality

Summary

OpenStreetMap User's Diaries: Sono nella top 100 dei mappatori di OpenStreetMap in Italia | Mappando la città di Piombino

Switch to Nautical View

Understand Depth and Seabed

Spot What Guides You

Plan a Safe Route

From Open Water to a Clear Path

Setting Your Own Course