OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

🗺️ Mapa para Todos: Acessibilidade no OpenStreetMap

O OpenStreetMap (OSM) permite mapear o mundo de forma colaborativa — e isso inclui tornar os mapas mais acessíveis para todas as pessoas, inclusive aquelas com mobilidade reduzida, deficiência visual ou necessidades especiais.

Mapear a acessibilidade é uma forma de promover a inclusão, ajudando pessoas a se locomoverem com mais segurança e autonomia.

✅ Como mapear acessibilidade no OSM (resumo de tags)

O que mapearTag principalComplementos úteis Calçadafootway=sidewalkkerb=lowered, width=*,

surface=Faixa de pedestrehighway=crossingcrossing=marked, tactile_paving=yes Rampa de acessoramp=yesincline= (ex: incline=5%) Banheiro acessíveltoilets:wheelchair=yes

Estacionamento acessível amenity=parking + wheelchair=yescapacity:disabled=*Entrada acessívelwheelchair=yes

Pode ser usada em escolas, hospitais, comércios Piso tátiltactile_paving=yes

See full entry

Location: Santo Amaro, Recife, Região Geográfica Imediata do Recife, Região Metropolitana do Recife, Região Geográfica Intermediária do Recife, Pernambuco, Região Nordeste, Brasil

The relationship between municipalities and populated places in the United States is often not obvious, especially in New England due to the naming of their local governments. Naming them towns has blurred the distinction of populated places and municipal governments, when in reality, a clear distinction can be made between the two.

First, let’s look at the things almost everyone should agree with. Nodes tagged with a “place” tag can be referred to as “populated places”, or named concentrations of people. The GNIS definition of a populated place says it best: “Place or area with clustered or scattered buildings and a permanent human population (city, settlement, town, village). A populated place is usually not incorporated and by definition has no legal boundaries. However, a populated place may [correspond with a] “civil” [entity], the legal boundaries of which may or may not coincide with the perceived populated place. Distinct from Census [places] and Civil [entities].” In other words, nodes with a place tag refer to a human settlement, NOT to a municipality. They are the places one might see on a green direction sign while on the road. The exception to this is if the municipal boundary corresponds to the extent of the populated place, which is the norm in most states.

However, in New England, town boundaries are usually formed out of straight lines and rivers, not with the intention of delineating the boundary of a populated place. Therefore, even if a town shares a name with a populated place within its borders, the populated place will not always fill the entire municipality, leaving room for other populated places to fill the rural areas. Some municipalities even lack a populated place with the same name as it. This leads to there being no 1:1 correspondence between municipalities and populated places in New England.

See full entry

🌍 Contribuições da UMBRAOSM para a Agenda 2030 da COP30 no Brasil.

A UMBRAOSM (União dos Mapeadores Brasileiros do OpenStreetMap) atua em diversas frentes que contribuem diretamente para os Objetivos de Desenvolvimento Sustentável (ODS) da ONU. A seguir, destacamos suas principais iniciativas em alinhamento com os ODS 4, 11, 13 e 17:

🎓 ODS 4 – Educação de Qualidade

Criamos tutoriais em vídeo disponíveis gratuitamente no canal oficial da UMBRAOSM no YouTube, facilitando o aprendizado para novos mapeadores de todas as idades.

Realizamos capacitações de novos mapeadores, com foco em educação aberta, colaborativa e digital.

Produzimos e divulgamos materiais didáticos e manuais que orientam sobre o uso das ferramentas de mapeamento colaborativo no OpenStreetMap.

🏙️ ODS 11 – Cidades e Comunidades Sustentáveis

Mapeamos nomes de ruas por todo o Brasil, utilizando dados atualizados do Censo 2022 do IBGE, contribuindo para uma melhor organização urbana.

See full entry

Location: Pirituba, Vitória de Santo Antão, Região Geográfica Imediata de Vitória de Santo Antão, Região Geográfica Intermediária do Recife, Pernambuco, Região Nordeste, 55605-011, Brasil

Sebagai seorang mapper paruh waktu yang paham dengan permainan di dunia OpenStreetMap (ingatkah anda dengan tulisan mimin pada 2018 yang mengritik praktik pembuatan peta ala Humanitarian OpenStreetMap Indonesia (HOT OSM Indonesia)?) dan menekuni dunia dokumentasi sejarah bangunan dan arsitektur melalui blog Setiap Gedung Punya Cerita (SGPC), mimin memandang bahwa dengan fitur yang tersedia, kita bisa memadukan keterbukaan OpenStreetMap dengan informasi yang didapatkan dalam pembuatan blog SGPC.

Jadi bagaimana caranya? Sederhana kalau implementasinya dari sudut pandang SGPC; tidak kalau implementasi di OpenStreetMap.

Pemanfaatan peta OSM di SGPC

Mimin membuat Setiap Gedung Punya Cerita karena banyak faktor, antara lain tidak tereksploitasinya dokumen sejarah dalam bentuk publikasi buku dan majalah sebagai referensi sejarah sebuah bangunan/obyek arsitektur serta memecah dominasi bangunan era Belanda dalam diskursus sejarah perkembangan perkotaan di Indonesia.

Blog ini sudah berjalan sejak 2018, dimana dalam tahap ini sudah ada kurang lebih 800 bangunan yang sejarahnya telah dikompilasi dan dicatat oleh blog ini. Inilah blog single fighter yang sesungguhnya, karena jarang masyarakat kita yang tertarik membuat kontennya sendiri.

Kembali ke topik pembicaraan, pemanfaatan peta OSM di SGPC dibantu dan dimudahkan oleh plugin bernama Leaflet. Leaflet menggunakan peta OSM untuk sumber lokasi datanya. Walau ada kelemahan yaitu orang tidak bisa mencari arah jalan di negara yang sudah kadung dibiasakan dengan peta proprietary semacam Google, setidaknya ini membantu masyarakat dalam mencari lokasi sebuah bangunan, selain melalui cara lama yaitu alamat.

See full entry

I’ve fixed some accidental error introduced in changeset 165092634 by user “Hooptie Bike Lounge”.

Both errors are now fixed in changeset 165210184.

Error #1 : Bowen St

They accidentally moved a node of Bowen St by 100’s of feet.

  • Before their edit the Bowen St node was here

  • their edit accidentally moved the node 100’s of feet to here.

Error #2 : Sidewalk on Boston Ave

They accidentally moved a node 100’s of feet for the sidewalk along the south side of Boston St near Hooptie Lounge.

  • Before their edit the Boston Ave sidewalk node was here

  • their edit accidentally moved the node 100’s of feet to here

Location: Longmont, Boulder County, Colorado, United States
Posted by WARUMICHRADFAHRE on 20 April 2025 in German (Deutsch). Last updated on 21 April 2025.

Heute habe ich eine neue Nomenklatur für meine Fahrten entworfen, sie besteht aus (am Beispiel meiner Fahrt am 20.04.2025):

  1. Letzte zwei Ziffern des laufenden Jahres: 25
  2. Laufender Tag des Jahres: 110
  3. Länderkürzel: DE
  4. Kürzel Bundesland: NW
  5. Startort: Horrem
  6. Hauptrichtung der Fahrt: W
  7. Zielort: Terranova Speedway
  8. Line / Circle: CIR
  9. Bezeichnung der Fahrt: Ballern

Also:

5110 DE NW Horrem W Terranova Speedway CIR Ballern

oder

5110_DE_NW_Horrem_W_Terranova_Speedway_CIR_Ballern

Siehe auch

https://www.openstreetmap.org/user/WARUMICHRADFAHRE/traces/11959979

osm.org/user/WARUMICHRADFAHRE/traces/11959979

Location: Hemmersbach, Horrem, Kerpen, Rhein-Erft-Kreis, Nordrhein-Westfalen, 50169, Deutschland

Hey fellow mappers! 👋🌍

I’m beyond excited to share that the global State of the Map (SOTM) 2025 will be held in Manila, Philippines 🇵🇭 — and preparations are already in motion! For those who are also planning ahead, here are some important links you should definitely bookmark::


🔗 Link Type URL
🌍 Official Website https://2025.stateofthemap.org/
📝 Call for Participation (CfP) https://2025.stateofthemap.org/calls/general/
🧪 OSM Science Track – Call for Abstracts https://2025.stateofthemap.org/calls/osm-science/
💸 Call for Travel Grant https://2025.stateofthemap.org/calls/travel_grants/


🌐 Official SOTM Social Media & Platforms

🌐 Platform Link
🐘 Mastodon https://en.osm.town/@sotm
📺 YouTube https://youtube.com/stateofthemap
📘 Facebook https://facebook.com/stateofthemap
📸 Instagram https://instagram.com/stateofthemap
💼 LinkedIn https://www.linkedin.com/company/stateofthemap/
💬 Telegram Group https://t.me/sotm_international
📝 OSM Wiki Page https://wiki.openstreetmap.org/wiki/State_of_the_Map_2025
📣 Official Blog https://blog.openstreetmap.org
💻 GitHub https://github.com/openstreetmap/stateofthemap-2025
❤️ Support OSM https://support.openstreetmap.org

If you’re thinking of applying, speaking, or volunteering — go for it! The energy, the people, and the purpose behind SOTM are truly unmatched.

Let’s map the future, together. See you in Manila! 🇵🇭


Brazil Singh,
On behalf of the SOTM organizing committee.

It’s difficult to write in all map style languages. A style written in JSON, like MapLibre, has a few extra pain points because JSON is not designed for editing by humans.

Some “common” style languages are

  • CartoCSS
  • Mapnik XML
  • MapCSS
  • MapServer
  • MapLibre GL/Mapbox GL

Some, like CartoCSS, are designed for human editing, while others, like Mapnik XML, serve as a lower-level language. MapLibre GL falls into this category of not being designed for editing by humans. MapLibre GL preprocessors like glug were designed to help with this, but none of them have taken off. Other style projects like openstreetmap-americana have taken a different route. Their developers have written a program in JavaScript that generates the style.

I’m taking a different route. I’m creating a language that uses minimal pre-processing of its input to produce MapLibre GL. I don’t aim to solve every difficulty with MapLibre GL, only the ones that impact me the most. The end result will be a pre-processing language

The biggest problems I encounter when writing MapLibre GL are

  1. No comments

    Comments are essential so other readers understand what’s written

  2. Everything has to be in one file.

    With large styles this is a burden. More than one file makes it easier to edit.

  3. Having to repeat definitions instead of using a variable.

    Something like a color or symbol definition might appear a dozen times in the style. If you want to change it, you need to make sure you got all the occurrences.

  4. Inability to make versions of the style in different colors.

    When you only want to change a few superficial elements of the style, you want to contain those changes to one file.

  5. Not having support for more colorspaces

    I work in perceptual colorspaces like Lch. It’s a lot of converting that the computer should automate.

What issues have you found when writing MapLibre GL styles?