OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

I have created a tag, diet:excipient_free=* , which is about finding clean supplements, i.e., without harmful ingredients that can make us infertile, inflamed, obese or even epileptic.

For example, whenever we look for magnesium (bis)glycinate, we want one thing, but many so-called “magnesium” supplements come with a lot more ingredients that might reduce the price, or enhance the appearance, but of course, at a cost; to hurt and make us need another supplement to compensate with the side effects. (Maybe they should rename those “magnesium” supplements to corn syrup supplements instead.)

Almost if not all of those ingredients fall into one category, excipients. Let’s use diet:excipient_free=* on pharmacies and nutrition supplement stores to promote a healthier future without dyes, fillers, flavorants, preservatives and other inactive ingredients that can cost us our health.

🌳 Percebendo que havia poucas informações no OpenStreetMap sobre o Parque Evaldo Cruz, em Campina Grande - PB, iniciei há uns meses o micromapeamento da área motivado pela reforma que ocorreu no local, por ser uma área verde que frequento cotidianamente e ser parte do Parque do Povo, onde acontece o Maior São João do Mundo.

Folha de Handroanthus impetiginosus Identificação em campo de Handroanthus impetiginosus (Ipê-roxo-de-bola)

📚 Sou pesquisador da área ambiental então sempre tento mostrar o potencial que o mapeamento para o OpenStreetMap possui. Os resultados abaixo são relacionados às árvores mapeadas e identificadas no local do parque, um trabalho que iniciei faz mais de seis meses e está quase 100% pronto. Quem quiser acompanhar esses e outros mapeamentos, costumo divulgá-los no Instagram - OMapaPB.

See full entry

Location: Centro, Campina Grande, Região Geográfica Imediata de Campina Grande, Região Metropolitana de Campina Grande, Região Geográfica Intermediária de Campina Grande, Paraíba, Brasil
Posted by SimonPoole on 4 March 2026 in English. Last updated on 6 March 2026.

OpenStreetMap old timers know about the infamous 2009 TIGER import of road data in the US that continues giving to this day. Our story has none of the, maybe deliberate, shenanigans (see the TIGER improvement project) that went on back then in the US, but there are clearly some similarities in the lessons that should be learnt.

Back in July of 2011 the Swiss community undertook a big effort to import municipality boundaries from swisstopo (the marketing name of the federal Swiss GIS department) (see osm.wiki/Switzerland/swissBOUNDARIES3D). Being an OSM n00b at the time with just a bit over a year editing experience I didn’t really do anything useful for the import proper, but I did organise the explicit permission needed from swisstopo as this was many years before their data would become available for use on open terms for us in September 2021. With a couple of technical hiccups along the way that are not really documented, we finally managed to complete the work by early August.

Fast forward to today: I’ve been going on for a few years now that we really need a quality assurance process so that we can discover and track differences between swisstopos data and what is in OSM. We knew and fully expected that there would be differences, because:

  • at the time of the import we simplified the boundaries quite significantly because of the resource constraints of the computer hardware available to us,
  • over the last 14 years we independently followed the mergers and other changes of the municipalities (see osm.wiki/Switzerland/2026_Municipality_Mergers), and didn’t expect this to improve the accuracy of the boundaries, and we knew that now and then there would be associated minor geometry changes that we wouldn’t be able to track,
  • and then just general decay due to glueing and accidental modifications.

Thanks to work by our community member habi inspired by earlier work by Branko Kokanović from Serbia, we have now have daily QA data and boy, we were wrong.

See full entry

Привет сообществу OpenStreetMap!

Не знаю, будет кто-то читать эту запись или нет, но попробовать написать в дневник — очень интересный опыт. Нигде не слышал, что здесь есть такой функционал, а раз имеется 😊 — нужно пользоваться.

В этой записи я хотел бы поделиться своим первым опытом. По сути, этот текст будет «водой» и не принесет много полезной информации.

Как я стал мапером

Однажды мне потребовалось найти адрес в моем поселке, но каково же было мое удивление, когда выяснилось, что никаких адресов нет (по крайней мере, точных). Мало того, отсутствовали и ключевые объекты инфраструктуры.

Недолго думая, я начал искать информацию о том, как редактируют карты, и наткнулся на «Народную карту» Яндекса. Какое-то время я вносил правки там: добавил и исправил достаточно много объектов. Процесс показался, как ни странно, очень интересным и «залипательным» — так у меня появилось хобби в картографии.

Знакомство с OSM

О проекте OSM я знаю относительно давно, но особого внимания ему не уделял. Как я сейчас понимаю — очень зря! Такого классного редактора, как iD, я еще не видел. Инструменты настолько простые, что ты не работаешь ими, а получаешь наслаждение, если так можно выразиться.

Про документацию я вообще молчу! Она бесподобна. Снимаю шляпу перед людьми, которые переводили её на русский язык. С ней очень удобно работать: один клик — и ты уже читаешь именно то, что тебе надо, а не тонну неструктурированной и разбросанной информации.

Итоги

Как проходит одобрение правок и когда они появятся на основной карте — я пока не знаю, да на данном этапе это и не важно. Надеюсь, что быстро.

В общем, очень жалею, что раньше не редактировал здесь и не уделял проекту внимания. Проект классный, документация — моё почтение, инструменты на высоте!

Всем спасибо за внимание, всем пока!

Posted by aleesteele on 3 March 2026 in English. Last updated on 6 March 2026.

3 March 2026: Writing this at a Missing Maps “London” remote meeting, realizing that I’d never written a OSM diary about the research I did within the ecosystem. I’m so late! But I’d love to still write this down. This placeholder is cross-linked with my blog.

From October 2020 to June 2021, I conducted ethnographic research within the (humanitarian) OpenStreetMap universe, trying to understand how communities, crises, and corporations came together on OSM. My thesis was ultimately about how humanitarian technologies like open source maps are used and created in response to crisis, and the convoluted mix of humanitarian values, corporate interests, and international networks that intersect on the OpenStreetMap platform.

The project and community is incredibly complex, a confluence of humanitarian actors, technology workers, and crowdsourced labor. My initial questions focused on why people contribute to open-source platforms like OSM (and Wikipedia for that matter), but they later evolved into what role humanitarian mapping plays within the wider ecosystem of geospatial and mapping technologies it is a part of.

Increasingly, as this was just before the wave of new AI technologies, I found that OSM data was being used in order to train AI systems like those used for road detection, etc.

While the written work is in the process of publication (eventually!), there are a number of public videos that share some of my public-facing findings on the subject.

Crisis Maps, Community, and Corporations (an Anthropologist’s perspective)

This talk shares my initial findings from this period, drawing from interviews and studies of political economy, science and technology studies, and humanitarianism. Social science methods might help us to better understand this changing period of OSM and HOT history, as it heads into the future.

Mapping crises, communities and capitalism on OpenStreetMap: situating humanitarian mapping in the (open source) mapping supply chain

See full entry

Posted by jwheare on 3 March 2026 in English.

I started a new wiki talk page discussion on the conflicting/controversial usage of the wetland=tidalflat tag regarding implied and explicit surface types:

Also posted a comment on positive related changes being worked on by the carto team:

Every map tells a story. Some stories are drawn with roads and buildings. Others are written through people, voices, and lived experiences. This is the story of how mapping became a bridge between climate vulnerability and community resilience in the heart of Dhaka. Under the Climate Resilience Fellowship, proudly supported by OpenMappingHub Asia Pacific, our Team 8 embarked on a journey called “Healthy Homes, Safer Futures.” Our goal was simple yet powerful: to strengthen climate awareness and resilience among vulnerable communities living in Dhaka’s urban informal settlements.

Where It All Began

In early May, all ten fellowship teams gathered in Dhaka, sharing ideas and aspirations for climate action. We were two coordinators: Mohammad Azharul Islam — Oceanographer and GIS Analyst at the Center for Geoservice and Research Ahsan Habib Saimon — Capacity Building Officer at Christian Commission for Development in Bangladesh Together, they envisioned a project that would connect data, digital tools, and grassroots knowledge to create safer living environments.

See full entry

Location: Duaripara, Pallabi, Dhaka, Dhaka Metropolitan, Dhaka District, Dhaka Division, Bangladesh

Nimman Road, Chiang Mai(Thailand) is a well-mapped, high-traffic corridor. It scores a B on network density: good intersection frequency, reasonable block lengths. But it scores near zero on crossing coverage because there are no highway=crossing nodes tagged within the 800m analysis radius. The street has physical crossings. They’re just invisible to any tool that relies on OSM, which is most tools.

That’s what SafeStreets shows: not just a score, but which data gap is causing it.

Nimman Road, Chiang Mai — SafeStreets walkability analysis showing 4.6/10 Car-dependent score with Street Grid 2.8, Tree Canopy 5.5, Destinations 7.2

What SafeStreets is?

A free tool that scores the walkability and pedestrian safety of any street address globally(graded out of 10). No account required, 190+ countries. OSM is the backbone, and the only data source that works everywhere.

How OSM powers it, three functions?

See full entry

Location: Chiang Mai City Municipality, Fa Ham, Mueang Chiang Mai District, Chiang Mai Province, Thailand

Portal North Bridge construction and study documents

https://archive.org/details/@isstatenisland/lists/7/portal-bridge-documents?sort=date

I gathered and uploaded documents relating to the Portal Bridge capacity enhancement project and its replacement, Portal North Bridge. The documents (except the Amtrak bulletins) come from NJDEP’s DocMiner. The Amtrak bulletins were retrieved by FOIA request. It appears the FEIS disappeared off the web many years ago.

The original plans intended to build a 3-track fixed span to the north. The documents from 2019 and later depict the currently chosen plan, the two-track fixed structure to the north. The south structure is not funded.

https://archive.org/details/portal-bridge-project-feis-final-4f-october-2008 Portal Bridge Capacity Enhancement Project - Final Environmental Impact Statement and Final Section 4(f) Evaluation, October 2008

https://archive.org/details/portal-bridge-project-feis-final-4f-appendix-vol1-october-2008 Portal Bridge Capacity Enhancement Project - Final Environmental Impact Statement and Final Section 4(f) Evaluation, October 2008: Appendix Volume 1

https://archive.org/details/portal-bridge-project-feis-final-4f-appendix-vol2-october-2008 Portal Bridge Capacity Enhancement Project - Final Environmental Impact Statement and Final Section 4(f) Evaluation, October 2008: Appendix Volume 2

https://archive.org/details/portal-bridge-project-relocation-study-january-2010 Portal Bridge Capacity Enhancement Project - Relocation Feasibility Study, January 2010

https://archive.org/details/portal-bridge-project-gc02-construction-plan-sheets-2019 Portal Bridge Capacity Enhancement GC.02 Contract - Construction Plan Sheets, August 15th 2019

https://archive.org/details/portal-bridge-project-environmental-impact-sheets-2020-2025 Portal Bridge Capacity Enhancement Project - Environmental Impact Sheets, January 2020 with November 2025 modifications

See full entry

Location: Kearny, Hudson County, New Jersey, 07032, United States

Como corrigir o nome de uma rua na aplicação CNEFE

Corrigir um nome de rua usando a aplicação CNEFE – Logradouro é um processo simples e direto, integrando os dados oficiais do Instituto Brasileiro de Geografia e Estatística com o mapa colaborativo do OpenStreetMap.

Veja o passo a passo:

1️⃣ Escolha a área no mapa Acesse a aplicação e navegue pelo mapa até a cidade ou bairro desejado. Você pode usar o zoom e arrastar o mapa para localizar a região onde deseja verificar os nomes das ruas.

2️⃣ Use o filtro “Rua” No painel de filtros, selecione a opção Rua. Isso fará com que a aplicação mostre apenas os logradouros classificados como ruas, facilitando a identificação de divergências entre o CNEFE e o OSM.

3️⃣ Escolha o editor A aplicação permite abrir a edição diretamente em um editor do OSM. Você pode escolher, por exemplo:

Editor iD (no navegador) JOSM (editor avançado para desktop)

Selecione o editor com o qual você já trabalha.

See full entry

Location: Niquelândia, Região Geográfica Imediata de Uruaçu - Niquelândia, Região Geográfica Intermediária de Porangatu-Uruaçu, Goiás, Região Centro-Oeste, 76420-000, Brasil

多言語表記のタグ付けを考える(パート2: 編集合戦編)

2026-02-01に’さくらインターネット Blooming Camp’で行われた「マッパーズサミット2026」での発表内容の「編集合戦編」です

パート1: OSMの基礎知識編

この記事は「基礎知識編」の続編です

必ず「基礎知識編」を見てから「編集合戦編」へ進んでください

パート2: 編集合戦編

ここからは、OSM編集で実際に起きた「編集合戦」について説明します。

パート1を見ていない方は、パート1: OSMの基礎知識編 を先に見ください

p21

事件は「渋谷スクランブル交差点」で起きました
- ウェイ: 渋谷駅前交差点 (1335178864) “バージョン #6” 2025-07-30

この交差点は英語圏では “Shibuya scramble crossing”として世界的に認知されており、インバウンド観光客の目的地ともなっています
- 渋谷スクランブル交差点

訪日客が”Shibuya scramble crossing”を目的地にした場合、数多ある渋谷周辺の’交差点’の中からどうやって”Shibuya scramble crossing” だと確信することができるでしょうか?
交差点にある「案内標識」の「国際表記名=Sybuya Sta.」がOSMに入力されていれば,日本語を解さない人でも「Sybuya Sta.」と表記された場所が「Shibuya scramble crossing」だと確信することができます

See full entry

Posted by SirfHaru on 24 February 2026 in English.

OK. Last year I wrote a short guide on mapping Indian addresses but I lost it in my tiny pursuit to delete myself. Today I suddenly came across the fact that the guide was actually used by mappers and, hence, as a result I am now writing this post to become a replacement for that old guide. Since this is a new one, I don’t want to just rehash the old stuff and instead this time I am going to take a simple problem and show how I would solve it from scratch.

A1, Tower 2, Sector 11, RK Puram, South West District, Delhi, India

A problem very similar to this one came up in OSM India’s XMPP channel today. So, how does one go about mapping this address?

As it’s usually the case we can ignore the district, state, and country part as they are all very well mapped in India. This leaves us with everything upto RK Puram.

If you are thinking that something as big as RK Puram should surely be already on the map then you are wrong; In my “career” I have actually seen larger areas without any nodes for them. So we will in fact check if it’s already on the map and, guess what, it actually is already mapped as a suburb, so that’s one less step for us! I should mention that in OSM there are three “neighbourhood” levels below the district: quarter, suburb, and neighbourhood in decreasing order of size. In most cases suburb and neighbourhood should be enough for you, but it is important to be aware of quarter for special situations.

Now let’s check for Sector 11. As of writing this, Sector 11 isn’t on the map. So I will put a neighbourhood node at the approximate centre of Sector 11. (Remember that neighbourhood is smaller than suburb.) We are making good progress.

See full entry

Location: Sector 12, Ramakrishna Puram, Vasant Vihar Tehsil, New Delhi, Delhi, India