OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

Desde o início deste ano, mais ou menos, no mês de Janeiro/2022, venho tentando na medida do possível atualizar dados inerentes à realidade das construções, seja ela de natureza jurídica ou de natureza, digamos que tenha certo vínculo “strictu sensu” por meio de normas à coisas abstratas, ou seja, “sem vida”, como por exemplo, corpos d’água, postes, pontos de ônibus, trem, bicicletário e dentre outros….O além disso, pode ser denotado e especificado no campos e subcampos, como também a sua descrição resumida e notas de observação. *Detalhe: Todo Mapeador/Analista de Geoprocessamento Profissional deve assumir um compromisso sério perante à sociedade contemporânea a sua assinatura ou o seu legado/rastro mais ou menos verídico da situação do território no qual foi concebido, criado, recriado e moldado pelas ações humanas e, inclusive da ações naturais ao longo de centenas e/ou talvez milhares de anos…

Posted by bo_hot on 4 February 2022 in English.

Hi all,

To better get the word out about what hot_tech is up to, each month I’m going to sit down and reflect and share the fruits of our labour so people can see what we’re working on, who’s working on it and how you can get involved. I’m sure these will evolve over time, so consider this a starting point.

Tldr;

  • Welcome to Kristen (android engineer), Leen (senior product manager) and Petya (tech collective facilitator); three new members joining us at hot_tech this month.

  • hot_tech has a new vision ‘just tech to connect people and places’ There’s a lot of ‘new’ this year for hot_tech, including new vision, new direction, new projects.

  • Kathmandu Living Labs are officially our first ever ‘collective’ partners. And will be the new official Tasking Manager maintainers.

You can read the full blog and details on the hot_tech blog here >.

Hope you’ve all had a nice warm up to the new year!

Kindness,

Bo

Location: Naz, Esserts-Salève, Monnetier-Mornex, Saint-Julien-en-Genevois, Upper Savoy, Auvergne-Rhône-Alpes, Metropolitan France, 74560, France
Posted by eternaltyro on 2 February 2022 in English. Last updated on 5 February 2022.

Background and context 🗺️

I’ve been using JOSM to map missing public transport routes in Chennai. It’s a project I’ve been doing for personal reasons which I intend to elaborate in another post and I began with iD only to find later that the order of the route segments matter and iD doesn’t make it easy to do reorder segments.

So I started using JOSM with a helper plugin I found. This has made my workflow much easier and faster. One small annoyance though is that I could only download a small section of a fairly large city to edit the map in JOSM. I discovered I could download larger areas if I carefully picked specific ways or nodes since the limitation (to downloading data) is the total size of data that OSM can return.

So I went and searched the web for examples of OverpassQL and their explanations, learned what I could about how the QL works in the time I had and strung together a quick and dirty query that downloads ONLY roads and bus stops within the bounding-box (that I get to easily draw in JOSM).

This probably could be improved for concision. This is the OverpassQL I use to download roads and existing relations in order for me to map bus routes using JOSM’s overpass-based data import dialogue window.


[out:xml][timeout:90][bbox:{{bbox}}];
(
  wr["highway"="primary"];
  wr["highway"="primary_link"];
  wr["highway"="secondary"];
  wr["highway"="secondary_link"];
  wr["highway"="tertiary"];
  wr["highway"="tertiary_link"];
  wr["highway"="trunk"];
  wr["highway"="trunk_link"];
  node["highway"="bus_stop"];
  node["bus"="yes"];
  node["public_transport"="platform"];
  node["public_transport"="stop_position"];
);
(._;>;);
out meta;

This has some nice conveniences for me:

See full entry

Location: Ward 60, Zone 5 Royapuram, Chennai, Tamil Nadu, 600009, India
Posted by Romeo Ronald on 1 February 2022 in English.

Mapping in a conflict Zone

In a war-torn and post conflict environment like South Sudan, the approach for mapping can be way different, basing on the fact that South Sudan’s war was based on a tribal line, it is again more difficult to perform a more inclusive program like mapping, but as for us at OSM South Sudan looked at this as an opportunity more than a challenge, so we began more basic training with basic tools like the ID editor and concept mapping.

See full entry

Location: Hai Soura, Juba City, Juba, Central Equatoria, South Sudan

Nach gut 2 Monaten ist der Kartenausschnitt Leipzig Wahren zu 90% durchdetailiert. Einzelne Ortspunkte folgen noch.

Es wurden mehrere Gartenanlagen angelegt und mit Gartennummern versehen. Die Uferbereiche der Flüsse durchgebildet und jede Menge Grundstückseinfriedungen ergänzt. Ebenso wurden die Wohngebiete nach Häuserblock aufgeteilt und neu gezogen (Grenze Bordstein). Beim Campingplatz Wahren wurden die im Wald befindlichen Ferienhütten ergänzt. Diese fehlten komplett.

Ergänzungen die noch fehlen: 1. Auensee (Grünflächen und Bäume) 2. Wohngebäude Pittlerstraße (Fotos fertig - Einarbeitung folgt) 3. Gewerbe Pittlerstraße

Location: Wahren, Nordwest, Leipzig, Sachsen, 04159, Deutschland

Uzice is a town in the Zlatibor district, in the Republic of Serbia. According to the 2011 census report, there were 52,646 inhabitants.

It lies on the banks of the river Djetinje. The medieval ruins of the then very important city have been preserved. Uzice was the seat of the Partisan army in the fall of 1941. In 1946, the name was changed to Tito’s Uzice in honor of Josip Broz Tito, and the old name was returned in 1992.

Uzice is a major center of the metal and machinery industry and fruit growing. Administrative center of the municipality of the same name and Zlatibor district.

Just look at the difference, how it looks now & how it did look before the change was made to a map:


View Larger Map

See full entry

W minionym tygodniu udało się pozyskać patronat honorowy dla naszego projektu ze strony czołowych specjalistów medycyny w Polsce. Na liście lekarzy, którzy obdarzyli nas swoim zaufaniem znajdują się:

  • prof. dr hab. Jerzy Robert Ładny - Konsultant Krajowy w dziedzinie medycyny ratunkowej
  • dr n. med Wiktor Kuliczkowski - Konsultant wojewódzki ds. kardiologii (dolnośląskie)
  • prof. dr hab. n. med. Andrzej Wysokiński - Konsultant wojewódzki ds. kardiologii (lubelskie)
  • dr hab. n. med. Łukasz Balwicki - Konsultant wojewódzki ds. zdrowia publicznego (pomorskie)
  • prof. dr hab. n. med. Marianna Janion - Konsultant wojewódzki ds. kardiologii (świętokrzyskie)

Jednocześnie przebudowaliśmy i rozbudowaliśmy stronę projektu. Wyszukiwanie oraz import danych jest teraz ułatwione. Lokalizacje AED są dostępne do pobrania w formacie csv, xls oraz GeoJson bezpośrednio z poziomu strony. Obecnie mamy zlokalizowanych ponad 1500 urządzeń (stan na 30.01.2022) Cały czas spływają do nas dane z samorządów więc ta ilość będzie się jeszcze zwiększać.

W przyszłym tygodniu będziemy kontynuować akcję mailową, roześlemy zapytania do pozostałych województw, na liście zostały nam jeszcze trzy. Plan na najbliższy tydzień to dalsza optymalizacja strony oraz praca nad włączeniem danych pozyskanych od jednostek samorządu. Mam nadzieję, że do końca lutego uda się zakończyć ten etap.

Pozyskując stopniowo dane będziemy także rozbudowywać stronę wiki poświęconą AED, zgodnie z informacjami pozyskanymi w ramach projektu z uwzględnieniem przykładów tagowania wypracowanymi podczas pracy.

Obecnie w skład zespołu zajmującego się projektem poza mną wchodzą następujący edytorzy:

See full entry

EXEMPLO DE CONSULTA OVERPASS / EXEMPLO DE CONSULTA OVERPASS

Consulta de VILAS

[out:json][timeout:25]; // fetch area “Recife” to search in {{geocodeArea:Pernambuco}}->.searchArea; // gather results ( // query part for: “amenity=place_of_worship” node“place”=”village”; way“placeplace”=”village”; relation“place”=”village”; ); // print results out body; >; out skel qt;

Consulta de Abreviação de Nomes de Ruas.

/*

Pesquisa de abreviacoes no OSM. Gera pontos geograficos no mapa.

*/

[out:json][timeout:900];

{{geocodeArea:Pernambuco}}->.searchArea;

(

// Enderecos

way[highway]“name”~”^Av\.”,i;

way[highway]“name”~”^Al\.”,i;

way[highway]“name”~”^R\.”,i;

way[highway]“name”~”Tr\.”,i;

way[highway]“name”~”Tv\.”,i;

way[highway]“name”~”Tra\.”,i;

way[highway]“name”~”Trav\.”,i;

way[highway]“name”~”Pç\.”,i;

way[highway]“name”~”Pça\.”,i;

way[highway]“name”~”Estr\.”,i;

way[highway]“name”~”Serv\.”,i;

way[highway]“name”~”Jd\.”,i;

way[highway]“name”~”Lot\.”,i;

way[highway]“name”~”Bal\.”,i;

way[highway]“name”~”Mun\.”,i;

way[highway]“name”~”Pte\.”,i;

way[highway]“name”~”Rod\.”,i;

// Profissoes

way[highway]“name”~”Dr\.”,i;

way[highway]“name”~”Dra\.”,i;

way[highway]“name”~”Prof\.”,i;

way[highway]“name”~”Profa\.”,i;

way[highway]“name”~”Eng.\.”,i;

way[highway]“name”~”Arq.\.”,i;

way[highway]“name”~”Jorn.\.”,i;

way[highway]“name”~”Med.\.”,i;

// Religiosos

way[highway]“name”~”Pe\.”,i;

way[highway]“name”~”Con\.”,i;

way[highway]“name”~”Ma\.”,i;

way[highway]“name”~”Rev\.”,i;

way[highway]“name”~”Mons\.”,i;

way[highway]“name”~”St\.”,i;

way[highway]“name”~”Sto\.”,i;

way[highway]“name”~”Sta\.”,i;

// Militares

way[highway]“name”~”Mal\.”,i;

way[highway]“name”~”Gen\.”,i;

way[highway]“name”~”Gal\.”,i;

way[highway]“name”~”Cel\.”,i;

way[highway]“name”~”Alm\.”,i;

way[highway]“name”~”Cap\.”,i;

way[highway]“name”~”Capt\.”,i;

way[highway]“name”~”Comte\.”,i;

way[highway]“name”~”Com\.”,i;

way[highway]“name”~”Col\.”,i;

way[highway]“name”~”Cel\.”,i;

See full entry

Location: -8.122, -34.954

Table placard.

This morning was our first (ever?!) OpenStreetMap meetup in Perth, Western Australia. Six of us turned up at the Goods Shed cafe (near the railway station) for introductions, coffee, and a general figuring-out of a plan. Then we headed off in small groups around the local area, mapping footpaths, shops, businesses, trees, drinking fountains, and everything else we could find.

See full entry

Location: Claremont, Town of Claremont, Western Australia, 6010, Australia
Posted by Mateusz Konieczny on 30 January 2022 in English. Last updated on 6 November 2022.

I have seen on tagging mailing list and some other places claims that deprecated tagging schemes continuing to be used are a critical issue.

I also have seen claims that having two tags with the same meaning is a critical issue that cause very big problems.


In my experience as mapper, someone working on OSM editors, someone working with OSM data:

Deprecated tagging schemes continuing to be used are not a big problem or a serious issue.

There are some tags that should be never used ( class:bicycle=* is a good example of something that is pure waste of time, see for example https://github.com/streetcomplete/StreetComplete/issues/2210#issuecomment-726974964 ).

But pointless tags can be completely ignored if they are truly bad ideas.

Note that popular tag which is not fundamentally bad idea and someone wishes to get rid of them is just regular duplicated tag for basically all purposes.


Duplicated tags with the same meaning.

For data consumer it is not a big issue. It is a bit annoying, but as long as new tags do not keep appearing then simple alias solves approximately all the problems.

It can be described as a problem but is definitely not in top 10 issues for data consumer. Maybe not even in top 50.

And is basically eliminated by decent documentation, if one exists at OSM Wiki.

For implementing it in editor - it depends on an exact case and definitely can be annoying.

But the worst part is case when group A demands to deprecate one tag, and group B demands to deprecate tag B. Or when one group accuses someone of being destructive because they followed documentation/consensus that documented some tag as deprecated/not deprecated and situation suddenly changed and another group appeared.

Overall this is quite ironic: people wishing to deprecate, rename, change tags often argue to be doing it to help data consumers.

See full entry

Posted by happy5214 on 30 January 2022 in English. Last updated on 9 February 2022.

Summary

For my first diary post, I’ll go into the ongoing dispute in the highway class tagging in one of my focus areas, the south-central San Joaquin Valley, particularly regarding rural four-lane roads in Fresno and Tulare counties.

Background

Traditionally, highway=trunk is used in the US for expressways and controlled-access roads with fewer than 4 lanes, though tagging standards vary from place to place. highway=primary is the typical tag in California for state routes, while highway=secondary is usually used for signed county routes, of which Tulare County has many.

In urban areas, the California OSM Wiki page also recommends using highway=secondary for roads with 4 lanes and highway=primary for roads with 6+ lanes.

The issue

When the rural 4-lane roads were remapped to reflect their divided 4-lane status (with the exception of Mooney Boulevard/CA 63, this was largely done by me), I generally tagged them as secondaries, with the rationale that they were clearly more important than the standard county roads (which I was generally tagging as tertiaries at the time). Since then, many of them had been upgraded to trunks by a single editor, which led to a pair of reversions when I tried to downgrade them again.

The current state

After a recent changeset, most of the non-state route four-lane rural roads (except for Golden State Highway and Mountain View Avenue) are now tagged as primaries. The Mountain View trunk tagging continues into Tulare County as Avenue 416, then turns south on Road 80 toward CA 198. The entire route of CA 65 in Tulare County (except for the freeway segment in Porterville) is also tagged as a trunk, even the 2-lane portions. The remaining four-lane rural roads in Tulare County are either primaries or secondaries.

My (originally) suggested solution

My (original) preference is to classify highways using a combination of importance and construction. With that said, here’s what I would do here.

See full entry

Location: Tulare County, California, United States

APRENDA A MAPEAR O mapeamento no OpenStreetMap é um esforço em equipe, crescendo continuamente devido a uma comunidade de centenas de milhares de colaboradores globais dedicados. Todos podem participar deste mapa aberto do mundo, é preciso de pessoas responsáveis, abertas a aprender e mostrar amor pelos detalhes.

Você pode começar sua jornada agora. Você não precisa pedir permissão antes de adicionar ou modificar dados existentes. Se você acredita que pode melhorar algo, faça-o. Mas lembre-se sempre, com grandes poderes vem grandes responsabilidades.

LEARN TO MAP. Mapping in OpenStreetMap is a team effort, continually growing due to a community of hundreds of thousands of dedicated global contributors. Everyone can participate in this open world map, it takes responsible people, open to learning and showing love for details.

You can start your journey now. You don’t need to ask permission before adding or modifying existing data. If you believe you can improve something, do it. But always remember, with great power comes great responsibility.

link to Learn to Map in OSM https://tasks.hotosm.org/learn

Atenciosamente,

Raphaelmirc Recife/PE.

Turbo Overpass Query

Site with Examples of Overpass Turbo Queries.

Consulta Overpass Turbo

[out:json][timeout:25]; ( way“highway”=”motorway”; way“highway”=”trunk”; way“highway”=”primary”; way“highway”=”secondary”; way“highway”=”tertiary”; ); out body; >; out skel qt;

Pesquisa de abreviacoes no OSM. Gera pontos geograficos no mapa.

Search for abbreviations in OSM. Generates geographic points on the map.

/* Pesquisa de abreviacoes no OSM. Gera pontos geograficos no mapa. */ [out:json][timeout:900]; {{geocodeArea:Pernambuco}}->.searchArea; ( // Enderecos way[highway]“name”~”^Av\.”,i; way[highway]“name”~”^Al\.”,i; way[highway]“name”~”^R\.”,i; way[highway]“name”~”Tr\.”,i; way[highway]“name”~”Tv\.”,i; way[highway]“name”~”Tra\.”,i; way[highway]“name”~”Trav\.”,i; way[highway]“name”~”Pç\.”,i; way[highway]“name”~”Pça\.”,i; way[highway]“name”~”Estr\.”,i; way[highway]“name”~”Serv\.”,i; way[highway]“name”~”Jd\.”,i; way[highway]“name”~”Lot\.”,i; way[highway]“name”~”Bal\.”,i; way[highway]“name”~”Mun\.”,i; way[highway]“name”~”Pte\.”,i; way[highway]“name”~”Rod\.”,i;

// Profissoes way[highway]“name”~”Dr\.”,i; way[highway]“name”~”Dra\.”,i; way[highway]“name”~”Prof\.”,i; way[highway]“name”~”Profa\.”,i; way[highway]“name”~”Eng.\.”,i; way[highway]“name”~”Arq.\.”,i; way[highway]“name”~”Jorn.\.”,i; way[highway]“name”~”Med.\.”,i;

// Religiosos way[highway]“name”~”Pe\.”,i; way[highway]“name”~”Con\.”,i; way[highway]“name”~”Ma\.”,i; way[highway]“name”~”Rev\.”,i; way[highway]“name”~”Mons\.”,i; way[highway]“name”~”St\.”,i; way[highway]“name”~”Sto\.”,i; way[highway]“name”~”Sta\.”,i;

See full entry

Location: Cohab, 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

Tarefas disponiveis no Maproulette para Padronização Internacional de Numeros de Telefones no Brasil / Tasks available in Maproulette for International Standardization of Telephone Numbers in Brazil.

alguns estados brasileiros ainda precisa de atualização dos dados telefonicos que estão mapeados no OSM e por isso venho aqui disponibilizar os link´s das tarefas no maproulette para quem puder fazer essa atualização e deixar os numeros telefonicos no padrão internacional.

exemplo de numero telefonico no brasil.

+55 DDD Numero de Telefone

+55 11 123456789

dá espaço para o DDD e o primeiro numero caso seja o 9.

+55 11 9 9123.4567 Link das Tarefas no Maproulette por estados!

Cidade Ceará - Brasil.

Cidade Piauí - Brasil.

Cidade Paraiba- Brasil.

Cidade Bahia - Brasil.

Cidade Maranhão - Brasil.

some Brazilian states still need to update the telephone data that are mapped in OSM and that’s why I come here to provide the links of the tasks in maproulette for those who can do this update and leave the telephone numbers in the international standard.

phone number example in brazil.

+55 Area Code Telephone Number

+55 11 123456789

gives space for the area code and the first number if it is 9.

+55 11 9 9123.4567

Link to Tasks on Maproulette by states!

Cidade Ceará - Brasil.

Cidade Piauí - Brasil.

Cidade Paraiba- Brasil.

Cidade Bahia - Brasil.

Cidade Maranhão - Brasil.

Raphaelmirc Recife/PE. www.umbraosm.com.br UMBRAOSM - União dos Mapeadores Brasileiro do Openstreetmap

Location: Cohab, 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
Posted by Cristoffs on 26 January 2022 in Polish (Polski). Last updated on 11 February 2022.

Klawisz F12 lub wybranie z paska skrótów ikony otwiera okno konfiguracji programu. Warto poświęcić chwilę na dostosowanie zachowania programu tak, by łatwiej było edytować. Na początku polecam włączyć tryb ekspercki JOSM-a, da nam to możliwość dostosowania aplikacji do naszych preferencji oraz włączy kilka niezbędnych funkcji, w tym możliwość zablokowania wysyłania zmian na serwer wybranej warstwy, co będzie pomocne, jeśli chcemy poćwiczyć na „sucho”.

W tym miejscu omawiam wyłacznie najważniejsze i najbardziej przydatne moim zdaniem ustawienia, ten krótki przewodnik nie wyczerpuje możliwości programu, a jedynie ma za zadanie ułatwić edycję dla wszytkich, którzy zaczynają swoją przygodę z JOSM.

Serwer OSM - Autoryzacja konto

Przed dokonaniem pierwszych edycji na mapie koniecznie trzeba autoryzować JOSM, tak by można było zapisać naszą pracę na serwerze OpenStreetMap. Okno OSM Server pozwala nam na konfigurację połączenia z serwerem. Autorzy programu rekomendują korzystanie z protokołu OAuth w celu dokonania uwierzytelnienia. Po jednorazowym podaniu hasła, w celu uzyskania klucza dostępu, proces będzie dokonywany automatycznie przy każdorazowym uruchomieniu programu.

Odwzorowanie kartograficzne

W celu prawidłowej kalibracji podkładu warto sprawdzić, w jakim układzie będziemy pracować. Dla Polski domyślnym odwzorowaniem jest PUWG o kodzie: EPSG:2180, jego stosowanie pozwala na poprawną kalibrację podkładów udostępnianych przez Główny Urząd Geodezji i Kartografii.

Style rysownia

Grupa ustawień pozwalających zmienić sposób , w jaki JOSM wyświetla dane w oknie edycji, w tym wypadku wiele zalezy od preferencji użytkownika oraz obiektów, na jakich się skupia. Dla mnie sprawdzają się następujące:

  • Kaart Style - Styl opracowany przez zespół edytorów Kaart-a wizualizujący atrybuty przez zastosowanie wielu kolorów. Dostępny na GitHubie pod adresem: https://github.com/KaartGroup/Kaart-Styles
  • fixme and note - Obiekty oznaczone fixme lub note są bardziej widoczne

See full entry