Style | StandardCards

OpenStreetMap Blogs

Wednesday, 01. July 2026

OpenStreetMap User's Diaries

Mejores deseos

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

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


[GSoC] Prototyping medial axis implementation for area routing

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 Valh

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:

  1. Collect all vertices from the polygon’s outer boundary and its holes
  2. Generate the Voronoi diagram
  3. Iterate over every Voronoi Edge
  4. 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!

Tuesday, 30. June 2026

OpenStreetMap User's Diaries

Культурное наследие.

В моём посёлке Слатино не очень много есть данных, большинство домов отсутсвуют, я переодически там что-то добавляю и даже пытался добавить все дома (это было очень сложно). Там я часто нахожу почти “Культурное наследие”, изменения, правки и т.д. 2009-2015 годов, я даже нашёл один профиль человека который максимально детально сделал своё село в 2011 в Сумской области, около 15к правок было в одн

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


Globe Meet-up last time. Albert pub tonight

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 cro

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.

photo at the Globe

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

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 […]

OSM Inspector screenshot showing turn restrictions – valid and invalid – in Nancy

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

广州地铁、广佛地铁和广东城际车站的出入口名称

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

查找

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

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

在线查询到的名称可能与线下名称有些区别,以线下为准(或者选一个你觉得合适的?)。

示例:13666261426、13941792080

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

查找

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

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

在线查询到的名称可能与线下名称有些区别,以线下为准(或者选一个你觉得合适的?)。

示例:1366626142613941792080


OpenStreetMap Blog

State of the Map 2026: Call for Posters

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 […]
SotM2018_viewing_posters

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

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

Monday, 29. June 2026

OpenStreetMap User's Diaries

Tile server for toll roads, cycling restrictions and cobblestone overlays

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 Germ

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.


Sobre OSM for Cities

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 cuand

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


About OSM for Cities

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

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


Sobre o OSM for Cities

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 qu

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.

Sunday, 28. June 2026

OpenStreetMap User's Diaries

How to add anchor portals correctly

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

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

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 […]

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

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…

Continue reading →

18/06/2026-24/06/2026

lead picture

[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 developedMetiq‘, 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

Country 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

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.

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.

Saturday, 27. June 2026

OpenStreetMap User's Diaries

Supermarchés à Genève de A à Z (ou plutôt de A à M)

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.

Ape

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


Documenting POI cluster — 8 offices in 100-mile NC corridor

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 —

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.


Cross-checking phone formatting on 8 LCC nodes — E.164 vs US-local

One more mapping note on the Local Concrete Contractor brand (relation/21035816, web 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:

  • Charl

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.


Proposing description tag conventions for small-business offices in NC

Following up on my brand-relation work for Local Concrete Contractor (relation/21035816, 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, pat

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.


Adding cuisine and shop-tag context for 8 trade-business nodes in NC

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

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.

Friday, 26. June 2026

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

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 ento

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.

Fotografía del mapeo en papel realizado con vecinas, foto: Bastian Greshake Tzovaras

SketchMap Tool de Barrio Esfuerzo Propio y Villa Moises

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.

Captura de pantalla de relevamiento realizado con ChatMap, 29/05/2026

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

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.

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.

Monaco harbor

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.

Nautical Map Marine Map

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.

Cap Corse

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.

Direct-to-point routing

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

Thursday, 25. June 2026

OpenStreetMap User's Diaries

addr:all, full の解体

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形式で住所データが保有されていた。過去形である。

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

サクラエディタ


Krim als Russland eingezeichnet?

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.

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.