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.

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.

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.

… See full entry

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

サクラエディタ

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.

Some street name are not confirmed. Still figure out.

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

What changed in the product

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

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

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

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

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

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

How it reads OSM now

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

The OSM tags doing the work, by component:

… See full entry

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

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

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

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

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

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

… See full entry

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

Hello OpenStreetMappers!

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

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

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

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

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

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

… See full entry

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

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

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

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

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

🏛️ Civic & Government Infrastructure

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

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

⛽ Fuel & EV Infrastructure

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

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

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

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

🛕 Religious & Community Spaces

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

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

🏥 Health & Financial Services

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

🍽️ Food & Local Businesses

… See full entry

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

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

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

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

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

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

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

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

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

merci de vos commentaires

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

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