hello! this is a basic draft to work on a possible import of static elevator/escalator data from the MTA largely to support potential work to show live availability data in Transitous. this will be set up as a MapRoulette challenge - naturally verifying the MTA data will be quite important so it’d be best not to do this as a ‘blind’ import

there’s a good chance this gets converted into a wiki page later but for now it’ll be planned here :-)

• Equipment Code -> ref

Wie trage ich Toiletten eigentlich korrekt ein?

Eine Toilette hat 2 Eingangstüren. Hinter der eine Kabinen und Stehurinale nur für Männer. Hinter der anderen eine Toilette für Frauen, Rollstuhlfahrer und non-binäre Menschen.

Eine Behindertentoilette benötigt einen Eurokey. (oder nicht)

Eine Toilette ist für FLINTA*.

Eine Toilette ist Unisex.

Es gibt ein Stehurinal.

Es gibt ein Hockurinal.

(Die Toilette auf dem Invalidenplatz in Berlin hat beides hinter zwei Türen und eine Sitztoilette hinter der dritten Tür).

Es gibt eine freiwillige Gebühr.

Ein Stehurinal hat keine Tür, ist 24 Stunden “offen”. Hat einen “Labyrinth”-Eingang

Ein Stehurinal hat kein Dach.

Eine Toilette ist Teil von “Die nette Toilette” und der Öffentlichkeit kostenlos zugänglich.

Eine Toilette ist selbstreinigend und während der Reinigung unzugänglich.

Nach 20 Minuten erfolgt die Zwangsöffnung.

Es gibt einen Veto-Schalter für 10 weitere Minuten.

Es gibt in Bodennähe einen Notrufknopf.

Es gibt mehrere Notrufknöpfe.

Es gib in Bodennähe ein umlaufendes Seil an dem gezogen werden kann, um den Notrufknopf zu betätigen.

Der Notrufknopf ist dauerhaft außer Funktion.

Die Tür öffnet sich automatisch, aber nur halb. Für die volle Öffnung muss der Öffner ein zweites mal gedrückt werden.

Eine Toilette ist seit Monaten defekt und abgesperrt.

Eine Treppe in einer Fußgängerzone führt zur Toilettenanlage herab, diese wurde aber vor Jahren dekommisioniert und die Treppe ist nur noch dekoratives Stadtmöbel.

Sanifair Gutscheine sind erhältlich.

Nur bestimmte Zahlungsmittel sind möglich.

Ein Münzwechselautomat steht oben an der Treppe zur Toilette.

Die Toilette ist nur per Treppe zugänglich.

Es gibt einen Aufzug.

Es gibt kein Fenster.

Es gibt Milchglasfenster.

Es gibt Fenster mit Panoramaaussicht über die ganze Stadt (Intercity Hotel Hannover, Casino-Etage, ganz oben).

Tonight’s London pub meet-up is at the Blue Posts. An old favourite!

Last time I said I was going to be adventurous with pub choices, and we went to The Albert in Victoria. I’m sorry I didn’t bother writing down any notes about interesting OpenStreetMap discussions from the evening. Rest assured many interesting OpenStreetMap discussions were discussed. My diary entry last time was just about pub choices, and this one will be no different!

Actually I do remember there was a lot of conversation about delivering election leaflets, since we had at least three different people in attendance who do a lot of campaigning, and using OpenStreetMap for that. It’s quite a nice use of OSM since you can boost the addressing coverage in the area of interest, and then use it, and then fix issues while using it, in a nice localised virtuous circle, and the use involves visiting every address, so perfect for filling in any map gaps.

So this was a new pub, and it worked pretty well. I decided to follow a theory I had, that pubs can be less overcrowded and more pleasant when they are further away from tube stations. The Albert pub was about half way between Victoria and Westminster tubes. Not sure it really worked in terms of avoiding the crowds, but it was spacious enough upstairs. There was a very big screen showing the wimbledon which we had to try not be distracted by.

I described this “further away from tube stations” theory to Matt Amos, and he crunched the numbers, rendered the maps, and dedicated a entire geomob talk investigating the “Watering Holes of inaccessibility” concept, including comparing OSMLondon pub choices over the past 18 years to conclude that we do indeed tend to go to pubs which are relatively far from tube stations!

… See full entry

aqui está o vídeo mostrando como usar a plataforma de Mapeamento Colaborativo de Bairros com dados derivados do CNEFE / IBGE 2022 no Openstreetmap usando o Editor JOSM.

Link do Vídeo: https://youtu.be/AUJiTgzaXqY

---

PASSO A PASSO:

🗺️ Mapeamento Colaborativo de Bairros no Openstreetmap usando a ferramenta de Mapeamento com dados derivadas dos dados do CNEFE / IBGE 2022.

Contribua para melhorar o mapa da sua cidade

A plataforma derivada dos dados do CNEFE / IBGE 2022. — Mapeamento Colaborativo de Bairros** permite que a comunidade participe do mapeamento e ajude a organizar informações importantes sobre os bairros das cidades brasileiras.

Você pode escolher uma cidade, selecionar uma área para mapear e utilizar o JOSM (Java OpenStreetMap Editor) para adicionar as informações ao OpenStreetMap.

🌐 Acesse a plataforma:

https://cnefe.mapaslivre.com.br/bairros.php

---

🚀 Como começar a mapear

1️⃣ Acesse a plataforma derivada dos dados do CNEFE / IBGE 2022.

… See full entry

This is just a reminder for myself on what to focus on to improve OSM-based navigation

This is the link to the blog post that goes in-depth on how CoMaps and OsmAnd take penalties into account when deciding how long a route will take and which route is the best/most efficient.

• Traffic Lights (Create a controlled junction and add necessary time penalties)
• Highway tags (Create uncontrolled junctions and add necessary time penalties)(Ex: Stop signs, yield signs, unmarked crossings, marked crossings)
• Traffic Calming features (From Least to Highest impact: rumble_strip, island, cushion, chicane, choker, table, bump, hump) Make sure they have a direction=* tag to mark the correct way affected.
• Pedestrian Crossings
• Barriers such as gates

Remember to add the direction=* tag to most of these!

El pasado 10 de agosto de 2026, Colombia fue golpeada por un fuerte sismo en la zona occidental de Colombia, en el departamento de Chocó.

Las afectaciones se dieron en muchos lugares de Colombia, donde las ciudades de Pereira, Cali y Chocó tuvieron muchas afectaciones, como edificios colapsados.

Debido a que monté un canal de WhatsApp para ChatMap muy temprano el mismo día del temblo, se han podido recoger muchos datos en terreno de las afectaciones. Igualmente, con el apoyo de la empresa Rumbo Digital pudimos una aplicación para funcionamiento offline y recolección masiva de reportes en terreno con fotos.

Todo ese proyecto de recolección de datos en terreno quedó documentado en https://d.osm.lat/palmar, y gracias a la Comunidad OpenStreetMap Colombia, como también el apoyo de HOTOSM y UN mappers, se pudo curar el contenido y tener un mapa que permite identificar las afectaciones graves.

Igualmente, gracias a la empresa FlyNorth, se han podido obtener ortofotos aéreas de zonas afectadas, con lo que estamos actualizando osm.

Este es el mapa con todos los datos que tenemos: https://umap.openstreetmap.fr/en/map/activaciones-de-mapeo-en-osm-por-terremoto-en-el-p_1450567

Aquí, una consolidación de todas las construcciones colapsadas, las cuales ya se mapearon o se deben actualizar en OpenStreetMap como demolished. Se tiene la dirección, el elemento en osm (o el más cercano), una visualización en Google StreetView y las fotos de los reportes.

Quibdó

• Calle 18 carrera 12 - osm.org/way/1176493359 - https://maps.app.goo.gl/s47hQjLXmjj5XB5TA - https://chatmap.hotosm.org/api/v1/media/6ef13ad2-9511-4f1a-885c-f247b4eca6e7.jpg

• Calle 18 carrera 18 - osm.org/way/1176507306 - https://maps.app.goo.gl/35P8kZuB1CJsJwvXA - https://maps.app.goo.gl/9ixkrXwoMGTqMF8y5 - https://chatmap.hotosm.org/api/v1/media/736ea2bf-4459-4406-81ba-ceabddaf3836.jpg - https://pub-978c45c8dccb4879aec4296407762b3b.r2.dev/2026/08/c8d24449-d525-43e3-a4f2-193bb9a0ffba.jpg

… See full entry

I build Tisseur de Voies, a site that computes loops where you ride one way and take the train back. Heritage railways fit that model well, because many of them carry bikes for free in a dedicated van, where regular regional trains count them. Trying to use them, I found the same situation almost everywhere: the tracks are in OSM, the service line is not. A data consumer sees a railway, with no way to tell that a train runs on it, where it stops, or who operates it. So I started adding them, one line at a time.

What I have contributed so far:

• Le Mastrou, Ardèche, 10 August (changeset 187233238): two route=train relations, one per direction, plus their route_master.
• Velay Express, Haute-Loire, 12 August (changeset 187362618): the same, with bicycle=limited on both directions.
• Chemin de Fer de la Baie de Somme, 19 September (changeset 189261499). Here two relations already existed, but as route=railway, with from and to swapped with respect to the geometry. I retagged them route=train, named them after the operator’s own routes, and filled in operator.
• Le Grand Large, the same day (changeset 189262951), the creation behind my first question.

1. One journey sold end to end, but two trains and a 200 m walk

The Chemin de Fer de la Baie de Somme sells three journeys on its metre-gauge network: « Entre Terre et Prés-Salés » between Le Crotoy and Saint-Valery, « Les Bas-Champs » between Saint-Valery and Cayeux-sur-Mer, and « Le Grand Large », Le Crotoy to Cayeux in 1 h 35. The third one combines the other two, and the change happens at Saint-Valery between two stations two hundred metres apart, on foot.

I mapped it as a third route=train relation. Its ways form a continuous chain from end to end, since the track does link the two Saint-Valery stations (I added the sixty metres that were missing along the quay), and yet no single train runs the whole thing. That is what bothers me, and I would rather raise it than let someone find it.

… See full entry

Je construis Tisseur de Voies, un site qui calcule des boucles où l’on part à vélo et où l’on rentre en train. Les lignes touristiques m’intéressent pour une raison simple : beaucoup embarquent les vélos gratuitement, dans un fourgon prévu pour ça, là où le TER les compte. En cherchant à les exploiter, j’ai trouvé la même situation presque partout. Les rails sont dans OSM, la ligne de service n’y est pas. Un consommateur de données voit une voie ferrée, sans savoir qu’un train circule dessus, ni où il s’arrête, ni qui l’exploite. J’ai donc commencé à les ajouter, une ligne à la fois.

Ce que j’ai contribué jusqu’ici :

• Le Mastrou, en Ardèche, le 10 août (changeset 187233238) : deux relations route=train, une par sens, et leur route_master.
• Velay Express, en Haute-Loire, le 12 août (changeset 187362618) : le même geste, avec bicycle=limited sur les deux sens.
• Chemin de Fer de la Baie de Somme, le 19 septembre (changeset 189261499). Là, deux relations existaient déjà, mais en route=railway, avec des from et to inversés par rapport à la géométrie. Je les ai passées en route=train, renommées avec les noms que l’exploitant donne à ses parcours, et j’ai renseigné operator.
• Le Grand Large, le même jour (changeset 189262951), la création qui pose ma première question.

1. Un parcours vendu de bout en bout, mais deux trains et 200 mètres à pied

Le Chemin de Fer de la Baie de Somme vend trois parcours sur son réseau métrique : « Entre Terre et Prés-Salés » entre Le Crotoy et Saint-Valery, « Les Bas-Champs » entre Saint-Valery et Cayeux-sur-Mer, et « Le Grand Large » qui relie Le Crotoy à Cayeux en 1 h 35. Ce troisième parcours cumule les deux autres, et le changement se fait à Saint-Valery entre deux gares distantes de deux cents mètres, que l’on franchit à pied.

… See full entry

For fall of 2026, I’ve recently resumed contributing and have transitioned from focusing on Paola, KS to Lawrence, KS. This is a move I hope to also make in real life in early 2027; until then it will mostly be working off of Esri aerial imagery and mapillary street level photos.

Once moved I’ll be able to survey things properly, and in the medium term after that the hope is also to start to capture 360 camera imagery by bicycle. I don’t have one due to price and the fact that I couldn’t justify one when mapping Paola.

Things that have caught my interest:

• Adding parking downtown
• Seeing if I like micro mapping things like land use. (will probably do this as a palette cleanser between working on other groupings of tasks)
• Adding crossing ways to the bike paths instead of just nodes
• Finding bicycle parking and repair stands
• Searching for cycleways

Observation on bike routes

The bike route signage situation on the ground is a bit unclear. In some areas the mapillary coverage is good enough to start to tackle that now. In lower traffic areas it will probably be necessary to be in the area to handle properly. Bicycle route relations exist for the area, but seem to have been done by several people and don’t have a coherent style. Making them consistent will likely be a long term project that will require actually having the local network already in my head.

Searching for cycleways via Aerial Imagery

Using the Esri imagery, which seems to date from 2024, I’ve found several streets where cycleways were tagged, and a few areas where tagging needed to be removed.

W 21st bike boulevard

bicycle_road and cyclestreet both exist, I’m unsure if they should be used or not.

To be mapped:

• Sharrows (Done)
• Bike Lanes (Done)
• Streetside parking boxes
• Chicanes (Done by jake_penguins prior)
• Turn lanes
• lane markings (Done)

Searched Areas

Completion Log

… See full entry

Every single driveway and sidewalk connection on every road beginning with A has been done. 17 of… 602. AGH.

Fucking diaries? Hell yeah. Anyways, I wanna clean my town up. Driveways and sidewalks are woefully unmapped… I have little idea what I’m doing on a styleguide level. Stared at the wiki, learned a little bit of Overpass to pull up a list of every road in town, and now I’m just alphabetically working through it all…

Una de las opciones que probé fue la actualización de ubicación, e muy precisa

New here, but excited to help. I’ve been using StreetComplete on my commute to help get some things updated and cleaned up here in Vermont

Moc prosím: když někdo mění názvy nějakého objektu, přeneste starý název do old_name. Ať už je to jméno budovy, ulice nebo zastávky MHD.

Je úplně úžasné, když existuje místo, které plní i funkci “historického překladače”. Když mluvíte se starousedlíkem, který vás posílá na Tesco u tramvaje “Zahrádky”, ale v ostatních mapách nic takového není, protože zastávka byla přejmenována na “Třebovice, OC”. Nebo když starousedlíci mluví o “Bachnerovi”, protože “Prior Horník” se vždy tak nějak pletl s “Prior Úderník” o dvě ulice vedle a s “Prior Hutník” o tři ulice a náměstí vedle. Dneska je tam “Bang Bang” a kdo ví, co to bude za rok.

Zejména na budově Sokolská 1, Ostrava je vidět význam této položky, když 80-letý řekne “Ander” nebo “ASO”, 50-letý něco jako “Starý Prior u Masarykáče, chvilku to bylo taky Laso”, 30-letý “stará VZP” a pro mladší je to prostě “ten barák jak se tam čeká na zastávce Sýkorák, dole se střídají různé sekáče s hadrama a je tam dost nachcáno”. A ano, všechny ty názvy jsou živé.

Najít stránku, kde je toto vše zdokumentováno, zabralo docela dost času a pro neznalé by byl problém si ji zase naopak spojit s konkrétními souřadnicemi… to je obecně podivný neduh různých historických stránek o architektuře, že neuvádějí souřadnice. A OSM má díky old_name unikátní vlastnost historii a souřadnice propojit.

He verificado la vía Guayas 129 en Puerto Engabao, Punta de Piedra. Confirmo su recorrido y coordenadas. Todo coincide con lo que se ve en el terreno.

Impetus

Many routers, such as OSRM,¹ set penalties for barriers like traffic lights or at-grade crossings, to estimate time lost at these points. For intersections with traffic lights, the standard procedure is to put a tag of highway=traffic_light at the intersecting node. For divided highway intersections, common practice is to tag each intersecting node also.

This quickly adds up to excess penalty for the simple router.² On a cross-traffic turn (left turns in the United States), this will lead the router to count three penalties per intersection. But, time spent at these intersections is not near three times the normal intersection, especially considering a cross-traffic turn often has first priority and protected access along divided highways.

The more-detailed method of tagging removes the unnecessary penalties. Instead of tagging highway=traffic_light at every intersection, a node is placed at every stop line to the intersection.

… See full entry

I run cyclists.com, a library of cycling routes. Every route page tries to answer what a rider wants to know before setting off: how much of it is on busy roads, whether it is paved, where the water and cafés are. Nearly all of those answers come from OpenStreetMap, so I wanted to explain how we use the data and pass back a few things we found in it.

What we measure along a route

We don’t use Overpass. A few hundred routes would be unfair load on a public instance, so everything runs against local Geofabrik extracts. For each route line we sample a point every 100 m, take the nearest way within 80 m and read its tags:

• Road class: highway=* grouped into cycle path, quiet street, minor road, main road (primary/secondary), major road (trunk) and motorway.
• Cycle provision: highway=cycleway, any cycleway*=* tag that isn’t no, or bicycle_road=yes.
• “Main roads without a cycle lane”: km on primary, secondary, trunk or motorway ways with none of the above.
• Fast roads: km where maxspeed is 80 km/h or more (mph converted).
• Surface: surface=* first; then tracktype; then the road class (a primary road with no surface tag counts as paved, a track as unpaved). Anything else is shown as “no data” rather than guessed.
• Services: cafés, bakeries, shops, drinking water, toilets, bike shops and railway stations within a few hundred metres of the line, placed by km along the route, plus the longest stretch with none.

Where a sample point is more than 80 m from any way, it counts as unmapped. We say so on the page instead of filling the gap.

A typical result, for a loop in the Hajar mountains above Fujairah: “Most of it (42.6 km) is on main roads without a cycle lane, 16.4 km where the limit is 80 km/h or more. The first 30 km has no café, shop or water.” And for the Deeside Way out of Aberdeen: “62% is on cycle paths or roads with a cycle lane. 52% is mapped as paved and 47% as gravel or unpaved.”

Elevation comes from the Copernicus DEM, not from OSM or from the GPS.

… See full entry

I run cyclists.com, a library of cycling routes. Every route page tries to answer what a rider wants to know before setting off: how much of it is on busy roads, whether it is paved, where the water and cafés are. Nearly all of those answers come from OpenStreetMap, so I wanted to explain how we use the data and pass back a few things we found in it.

What we measure along a route

We don’t use Overpass. A few hundred routes would be unfair load on a public instance, so everything runs against local Geofabrik extracts. For each route line we sample a point every 100 m, take the nearest way within 80 m and read its tags:

• Road class: highway=* grouped into cycle path, quiet street, minor road, main road (primary/secondary), major road (trunk) and motorway.
• Cycle provision: highway=cycleway, any cycleway*=* tag that isn’t no, or bicycle_road=yes.
• “Main roads without a cycle lane”: km on primary, secondary, trunk or motorway ways with none of the above.
• Fast roads: km where maxspeed is 80 km/h or more (mph converted).
• Surface: surface=* first; then tracktype; then the road class (a primary road with no surface tag counts as paved, a track as unpaved). Anything else is shown as “no data” rather than guessed.
• Services: cafés, bakeries, shops, drinking water, toilets, bike shops and railway stations within a few hundred metres of the line, placed by km along the route, plus the longest stretch with none.

Where a sample point is more than 80 m from any way, it counts as unmapped. We say so on the page instead of filling the gap.

A typical result, for a loop in the Hajar mountains (Fujairah Loop via Fayyad and Minazif): “Most of it (42.6 km) is on main roads without a cycle lane, 16.4 km where the limit is 80 km/h or more. The first 30 km has no café, shop or water.” And for the Deeside Way out of Aberdeen: “62% is on cycle paths or roads with a cycle lane. 52% is mapped as paved and 47% as gravel or unpaved.”

… See full entry

---

Also Vater kenne ich das Problem: Wo ist die nächste Wickelmöglichkeit? Welcher Spielplatz hat eine Schaukel? Welches Café hat eine Spielecke? Darum habe ich kinderfreundlicheorte.de gebaut – eine Karte familienfreundlicher Orte, komplett basierend auf OpenStreetMap-Daten.

Stand heute:

• Deutschland: 149.182 Orte
• Österreich: 13.482, Schweiz: 16.096, Liechtenstein: 95, Luxemburg: 1.538, Südtirol: 1.208

Die Pipeline fasst Spielplatzgeräte (Schaukeln, Rutschen, Wippen) mit ihrem Spielplatz zusammen, indiziert u.a. changing_table, kids_area, highchair und Besucher können Ausstattung über „Ausstattung melden” nachtragen – geprüfte Meldungen wandern per OSM-API zurück in die Datenbank.

Meine Bitte an die Community: Wenn ihr mappt, tragt changing_table, kids_area oder Spielplatzgeräte ein, wo ihr sie seht. Ich hab selbst damit angefangen. Kleine Tags, große Wirkung für Eltern!

Hinweis: Die Seite ist derzeit nur auf Deutsch und deckt nur deutschsprachige Regionen ab (DE, AT, CH, LI, LU, Südtirol).

Kegiatan saya mengikuti latihan Muslim Calisthenics Jakarta pertama kali dalam sekali :-D

Minggu, 14 Juni 2026

… See full entry