About three years ago, I had given a talk to some folks at the Irish Wheelchair Association in Kilkenny about the history of Kilkenny. They wanted me to do that again, but I thought that giving the same talk would be boring and asked whether I could talk about mapping accessibility instead. They were open to the idea, so I did that. I thought it would be a good opportunity to tell them about OpenStreetMap, but also to get some input from them about what else we could map.

In preparation for the talk, I created an “accessibility” preset in StreetComplete with quests all to do with wheelchair and visually impaired mapping, including the surface quest, because I figured that would be important for the routing services for wheelchairs. I surveyed quite a bit in Kilkenny city centre to get an idea of what the situation in town is.

I’ve recorded a video with the same slides I used for the talk which you can watch on YouTube (proof-read English and German subtitles available).

Additional quests for StreetComplete that I came up either by myself or with their help are (They’re also in the video, but it’s handy to have them listed here.):

• Is this ATM wheelchair accessible?
• Is this vending machine accessible?
• Is payment in this shop/ restaurant wheelchair accessible? (They said that sometimes the payment terminals are fixed in place too high up on a counter.)

After the talk, one of the facilitators told me about an upcoming audit walk in Kilkenny (on the 24th of July) to assess accessibility. So I got in contact with them to tell them about wheelmap.org and sent them a link to the video, so they don’t audit things I have already surveyed.

I used two overpass-turbo queries in the talk/ video to show some of the data that can be extracted from OSM:

• shops with the wheelchair key, colour-coded by accessibility (which is similar to wheelmap, but the data can be exported)
• steps and ramps, colour-coded by the ramp key (yes/ no/ separate/ no data)

… See full entry

Die OpenStreetMap Community in Fulda hat in Kooperation mit dem Magrathea Laboratories e.V. - Chaos Computer Club Fulda - eine Panoramax Instanz ins Leben gerufen.

Panoramax ist eine Software für Straßenbilder wie man es von Google oder Apple Maps kennt. Der große Unterschied: Die geschossenen Bilder werden unter CC-BY-SA-4.0 Lizenz veröffentlicht und gehören also keinem Unternehmen. Das Projekt verfolgt die Idee der digitalen Unabhängigkeit und setzt zusätzlich auf eine zukunftsorientierte dezentrale Infrastruktur in der sich Panaromax Server der ganzen Welt in eine sogenannte Förderation begeben um als ein großes Ganzes zu fungieren.

Fulda ist hiermit die erste Stadt in Deutschland, die dieser Föderation mit ihrer Instanz beigetreten ist und es gibt auch schon einiges zum Anschauen:

https://panorama.osm-fulda.de/

Zu sehen gibt es aktuell einige Stadtteile Fuldas und Radwege um Fulda herum.

ℹ️ In den Filtereinstellungen könnt ihr den Rest der Welt miteinblenden lassen.

Aktuell haben wir 34,854 Bilder die 474 km abdecken. Auf Festplatten sind das ~340 GB. Also ca. 0,74 GB pro 1 km Strecke. Unsere Ressourcen sind aktuell zu 34% ausgelastet. Wir bekommen also noch einiges mehr “in den Kasten” bevor wir uns über mehr Finanzierung Gedanken machen müssen.

Zwei Dinge schon mal vorab: Gesichter und Nummernschilder werden natürlich unkenntlich gemacht. Falls trotzdem etwas auffällt, kann dies gemeldet werden und wir werden uns darum kümmern. Häuser werden nicht unkenntlich gemacht, da es dazu keine Gesetzesgrundlage gibt. Die großen Anbieter machen das bisher nur aus Kulanz.

Du hast Fragen, interessante Ideen dazu oder magst mitmachen, dann schau doch einfach mal in unserem Chat oder im Fuldaer OpenStreetMap Wiki vorbei!

ℹ️ Mal 1-2 Stunden investiert und dein Stadtteil/Dorf könnte auch abgelichtet sein.

Motivation

Mal ab von der technischen Finesse und dem Konzept der Dezentralität von Panoramax, hat das Projekt mehrere Ziele:

… See full entry

Увидя contact:website = https://vk.com/... руки открыли Overpass Turbo

Острожно, регулярки!

Ну поехали

искать, что можно перенести в contact:vk:

nwr["contact:website"~"^https://vk\\.com"][!"contact:vk"]

Всегда ли https?

nwr["contact:website"~"^http://vk\\.com"][!"contact:vk"]

Всегда ли http?

nwr["contact:website"~"^vk\\.com"][!"contact:vk"]

Всегда ли в начале?

nwr["contact:website"~"vk\\.com"][!"contact:vk"]

Аккуратно с автозаменой, есть валидные домены оканчивающиеся на vk.com. Затыкается примерно так: "(^|[^a-z])vk\\.com"

Всегда ли .com?

На практике да. Но не в website!

nwr["website"~"vk\\.ru"][!"contact:vk"] — (помним про ложные срабатывания)

Ещё есть .link, но это в принципе можно считать сайтом заведения. Это всё?

Ищем другие доменные зоны

(
   nwr["website"~"(^|[^a-z])vk\\..+/"][!"contact:vk"]; 
)->.a;

(
   nwr.a["website"~"\\.(link|com|de|ru)"];
)->.skip;

(.a; - .skip;);
out geom meta;

Кроме редких vk.cc (сокращатель ссылок) и vk.me (прямые ссылки на фотки) особо ничего.

Это всё?

Отключаем зависимость от регистра

(
   nwr["website"~"(^|[^a-z])vk\\.(com|ru)/",i][!"contact:vk"];
)->.a;

(
   nwr["website"~"(^|[^a-z])vk\\.(com|ru)/"][!"contact:vk"];
)->.skip;

(.a; - .skip;);
out geom meta;

Артефакты прошлого

Фан-факт: OpenStreetMap старше ВКонтакте.

nwr["website"~"vkontakte\\.",i][!"contact:vk"];

Всё?

А теперь всё тоже самое но без [!"contact:vk"]

---

В следующей серии изучим сам contact:vk

📊 First changeset review insights for Andhra Pradesh, India

• 🙋‍♂️ Review Requests: 32% of newcomers requested a review of their first changeset.
• ✨ Technical Quality: 32% of a newcomer’s very first edits are completely free of technical errors.
• ⚠️ Low-Severity Issues: 49% of changesets have low serverity errors like abbreviation issues or duplicate node-way geometries

---

💡 Localized, faster community validation workflows are essential to support mapping talent.

About 450 editors join OpenStreetMap and contribute their first edit everyday based on a study for the year 2023.¹ Despite diverse OSM review tools and processes, there were few studies about OSM new editor data quality at country level.² Very little is known about their contribution quality and persistence at province level. This need was identified in the first ever desk analysis of State of the map for Andhra Pradesh in 2025. Even attempting to statistically analyze is not easy, given the need to query databases with specialized programs. OSM Changeset Analyser(OSMCha) is a very good tool for reviews. Using OSMCha and OSM APIs, I built a small Python Jupyter notebook program with help from Github Copilot. I applied this to understand the new editors contributions for Andhra Pradesh province of India for Q1, 2026. I found that 32% of first edit changesets are of good quality. 49% have low severity issues. Only 3% continue the edit activity in the subsequent 30 days after discussion on their first changesets. This program can be reused easily by modifying OSMCHA’s AOI filter identifier and OSMCHA user token.

Review process using OSMCha

… See full entry

Not at all my work, but a place to record the work of Akash Wadhwani. They have just written a great piece on OpenStreetMap and the work of volunteers to map in support of disaster response.

I recommend you all read it, it’s a great advert for you.

https://sheets.works/data-viz/strangers-draw-maps

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 да испланираш своју руту, провјериш пресједања или прикажеш своју тренутну локацију уживо. Било да је у питању свакодневни превоз или викенд излет – овдје имаш комплетан увид у градски саобраћај.

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

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)],
    ])

… See full entry

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

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.

… See full entry

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

查找

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

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

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

示例：13666261426、13941792080

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.

… See full entry

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.

… See full entry

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

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.

… See full entry

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

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.

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 .

… See full entry

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.

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.