В моём посёлке Слатино не очень много есть данных, большинство домов отсутсвуют, я переодически там что-то добавляю и даже пытался добавить все дома (это было очень сложно). Там я часто нахожу почти “Культурное наследие”, изменения, правки и т.д. 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.

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