Esse foi meu primeiro projeto de importação semi-automatizada. Na maioria das vezes prefiro usar o MapRoulette para poder conferir os dados e corrigir se necessário. Isso acaba dando um pouco mais de trabalho mas isso é melhor para dados mais complexos como escolas, postos da policia, clínicas e outros dados.

Como estou sempre procurando novas bases de dados que possam ser usadas para melhorar o OSM acabei encontrando o GeoDourados, que é uma base bastante rica de dados sobre a cidade de Dourados, alem de contar com ortofotos de alta resolução.

Mandei um e-mail para os responsáveis pedindo permissão para usar os dados no OSM e, apesar de ter enviado mais de 10 e-mails para cidades diferentes, a única que respondeu foi Dourados. Por isso gostaria de agradecer ao Departamento de Geoprocessamento de Dourados, em especial ao Ênio Alencar, por ter dado suporte com esse projeto.

De todos os dados possíveis para utilização no OSM, decidimos começar pelas árvores, visto que além de ser um dado útil, seria mais simples de importar inicialmente. Não há duvida da importância das árvores para o ambiente das cidades, além de promover conforto nos dias mais solarizados também servem para absorver os ruídos produzidos nas grandes cidades.

Caso queira saber mais sobre arborização e o OSM na ultima terça feira houve um webinar sobre o OSM e arborização urbana para comemorar o dia da árvore link

O trabalho de importação só foi possível com a ajuda do Matheus Gomes que teve todo o trabalho administrativo, pedindo permissão da comunidade, escrevendo na Wiki e preparando os dados para serem importados. Sem ajuda sua ajuda não saberia nem por onde começar, obrigado!

Com os dados já prontos e com autorização, tive que começar a limpar áreas de conflito que já tinham árvores mapeadas. Usei o overpass turbo para baixar esses dados e comparei com os dados que seriam importados.

Em destaque árvores que já haviam sido mapeadas antes na cidade de Dourados.

Após remover as árvores (do arquivo original) que poderiam dar conflitos com as já existentes no OSM.

E esse foi o resultado de antes e depois da nossa importação:

Como resultado final, podemos destacar não somente a importação e atualização de mais de 94.000 árvores no OSM, como também a permissão para utilizar vários outros dados do GeoDourados. Com isso, já inserimos as ortofotos de Dourados tanto no iD quanto no JOSM, por exemplo. Também fortalecemos os laços com mais uma prefeitura brasileira.

Por fim, os próximos passos envolvem analisar e ver a melhor maneira possível de inserir os outros dados possíveis, como endereços e edificações.

{Insert standard apology about poor english from non-native speaker here}

So, I've found this beautiful thing, the OSM, I'm feeling so inspired and motivated - finally a platform where I can make contribution and fixes knowing that my efforts will not be in vain!

I'm currently living in Gyumri, Armenia, and maps here... have issues. On Google Maps, seems that building were autogenerated from satellite images - there are obvious errors, missing buildings, nonexistent buildings, buildings with weird geometry, buildings that are crossing roads or each other, roads that in reality are footpaths, footpaths that are ending abruptly (because they are partly hidden by trees on satellite image) - you name it. Addresses are absent on 90% of buildings. In my city, all you can do in Google Maps - 'add missing place' or 'add missing address' ('fix road' option in my area is not available), by filling some form and hope that it will be accepted by somebody someday. But where should I add address if the building itself is not present on the map!?

At least Google is accepting edits related to places (working hours, changed location etc.) pretty fast usually. In case of Yandex Maps that is not the case. Those were my favorite maps (especially UI-wise) before... before I've tried to start contributing and fix errors about ogranizations I visit. Seems that in vast majority of edits you will receive seemingly automatic "Unfortunately we were unable to confirm" letter. "We need more information to confirm the edit. Please contact support." What? Why? Oh well... After writing to support, they usually do add edits without any additional questions. - "Why did you reject same edits in the first place? That is looking almost automatical. Are you defending from bots that way? What did I do wrong and how can I do edits 'the right way' in the future to avoid bothering you and wasting time of support specialists?" - "Sorry, we do not disclose details of our verification processes. Please be understanding.". That's demotivating. If I'm adding a photo of some shop that have none of them - it can wait for a 'verification' for a month or more. I'm still waiting! Photos usually greatly help me to navigate in new places...

After that, OSM feels like a breathe of fresh air, like a knight on a white horse (haha, sorry) that should free me from that corporate bureaucracy and finally allow me to do useful stuff for free! (lol)

Though that's a pity that by making changes on OSM I cannot enhance my experience with sites and services that rely on other maps (for some food delivery services you cannot even pick your location if your house's address is not on a map - and you're lucky if it allowes to type in any address without validation). I really hope that more and more businesses will rely on OSM's data in the future.
And, though I'm annoyed by Yandex & Google - honestly, currently I do not see real alternatives when I use maps to search for some organization or just find a nice place to have a lunch - I really rely on photos, ratings, user's feedbacks and a flexible search by name and organization type... (at least, I used that on a daily basis when I was living in a big city, where most organizations are on map and data is usually relevant). In that sense, OSM is clearly deeply map-centric, businesses are not in its focus, I understand that. I can recommend it to my friends to search for an address, not for 'fish restaurant'.
Of course, there are apps like 'Maps.me', that do use OSM data and seem more average-user-friendly, but in my place they are not so popular, almost unknown, so quality and comleteness of data that should be added by users suffers, comparing to mainstream map services. I haven't tried to add data using mapbox UI yet myself, that's for the nearest future =) But looks nice already! I wonder if they do some 'validation' and how long it is...

As I opened Gyumri map after completing OSM's marvelous crash course, I've noticed bunch of inconsistencies in my district - and, while clarifying buildings geometry, naively shifted those buildings 'to match the image'. Only after some time I noticed that you can choose between different background image sources. With different shift relative to data layer. Stupid me... but what is the right way? Quite quickly I found the answer on the wiki (Error Categories). In Gyumri, GPS data is... scarce. And I have no car. I checked different parts of the city (which is more or less flat as I know) trying to find offsets what make existing paths lay on roads as nicely as possible. For Bing imagery that appeared to be ~2.8, 4.2. Buildings still seemed off, but now I was modifying them with some amount of confidence - clearly, buildings were marked without gps data before, seemingly created using Esri-Clarity images without any shift. To double-check myself, today I switched to Esri, hid data layer, shifted Esri images to GPS tracks and then enabled data layer again to see buildings that I modified earlier. Well... not bad, I think, but not great either, with at least 2 meters shift. Sigh... But what if I shift Esri layer now, to match my moved buildings? I suppose, gps tracks will be looking misplaced then? No! They are still 'somewhat on roads', and that magic gives me anxiety. After all, seems that there are just not enough gps data to be sure. And now, after clarifying buildings and roads locations for a half of district (that turned out to be almost meditative process), I'm not sure even that what I do is right. Yes, at least it is closer to gps data than it was previously, but do I need to make those changes if in the future somebody may be using more complete gps data that may give other offsets? Or somebody decides to edit map of Gyumri now and finds different offsets because of scarcity of current gps data. In both cases it will be like re-doing the same work again. I don't know now if I should revert my own changes. After all, I did not make map less precise, and in case of geometry, it is definitely an upgrade. But.... that offsets stuff... ugh. Maybe I'm just missing something in my approach. I'm a newbie, after all. At least I will record gps tracks when using taxi now =)

I love it

依據高雄市政府觀光局2022.06.27發布政府開放資料 其中包含壽山國家自然公園轄管山區及高雄觀音山範圍之通訊標示 https://khh.travel/zh-tw/event/news/4565 總計61處，經比對有1處坐標有問題(已經向高雄市觀光局詢問) 其餘多數壽山國家自然公園內多是補充電信業者資訊(之前已建置遠傳和台哥大，這次多新增中華電信和亞太電信) 至於高雄觀音山為本次新增項目。

台灣政府最早由林務局羅東林區管理處與電信業者合作測試及設置通訊牌誌，並請RUDY協助匯入OSM中，隨後經累積林務局各林區管理處、玉山國家公園、雪霸國家公園、壽山國家自然公園管理處、新北市政府相關單位建置之通訊資料已達1300處，台灣登山迷途案件占山域救援案件近5成，本次增加可以補充相關電信業者，讓民眾知道哪裡可以通報，提升台灣民眾登山安全。

Hey ihr Lieben,

ich hätte gerne eine abfrage die mir die wasserwanderrastplätze in Brandenburg anzeigt.

Ich bin sehr neu in diesem Forum und nicht besonders technikaffin. Wenn mir jemand zeigen könnte, wie die abfrage aussieht, wäre ich sehr dankbar.

Un projet occupe une poignée de contributeurs OSM en Belgique: l’import des batiments, c’est-à-dire compléter tous les batiments à partir des données officielles et ajouter la référence de ces données officielles aux batiments existants.

Depuis des contacts initiés fin 2021 avec le service public de Wallonie (SPW), cet import est également disponible pour la Wallonie, sur base des données du PICC: la base de référence pour les batiments en Wallonie.

Cet article expose brièvement la méthodologie suivie et des premiers résultats sur 3 sections administratives de la commune de Neufchâteau, principalement en repérant des nouveaux batiments et des batiments détruits.

Quid des batiments en Belgique?

À ma connaissance, il n’y a pas eu d’état des lieux récents de la complétude des batiments en Belgique. D’une manière générale, la majorité des batiments ont été cartographiés, souvent à la main, sur base d’images aériennes (ou du fond de plan du PICC en Wallonie). Les contributeurs trouvent en cherchant un peu des communes où il manque davantage de batiments que d’autres, ou bien des endroits où les batiments devant avoir une adresse n’en ont pas. On pourrait faire une analyse plus détaillée par commune pour estimer le taux de complétude des batiments.

Quoiqu’il en soit, voici une carte de l’état d’avancement de l’import: http://umap.openstreetmap.fr/fr/map/building-import-status_714473#8/49.792/5.823; Attention, comme dit plus tôt, une majorité de batiments ayant déjà été cartographiés par le passé, cette carte ne renseigne que sur l’import récent des batiments ainsi que l’ajout des références officielles.

Comment ça marche?

L’import se fait à partir d’un outil web, disponible sur https://buildings.osm.be/, en combinaison avec le programme JOSM. La page décrivant l’import est ici. Les instructions détaillées sont là. Je ne vais pas rentrer dans les détails du fonctionnement ici. Si vous êtes intéressés à importer des batiments, lisez ces pages et/ou contactez la communauté en Belgique, en particulier la “room element” (endroit de “chat”) dédiée à cet import.

Buts de l’import

Les buts de cet import sont multiples: d’abord remplir la carte de batiments existants, ensuite et surtout, avoir une base d’adresses à jour dans OpenStreetMap et enfin, avoir dans les batiments OSM la référence des batiments du PICC.

Ce dernier but a un intérêt pour la mise à jour future des batiments: quand le PICC évolue, on veut pouvoir rapidement déterminer si un batiment a déjà été importé dans le passé, et la meilleure façon de le faire est d’avoir son numéro de référence du PICC dans une étiquette OSM.

En outre, en faisant l’import, on peut détecter des différences entre le PICC et OSM qui vont pouvoir être remontées aux gestionnaires du PICC. Ces différences sont:

• des nouveaux batiments;
• des batiments ont été détruits;
• des batiments ont été modifiés.

La section “Dealing with errors in the source data” indique que faire dans ces cas.

Import des batiments à Neufchâteau

Un import des batiements a été réalisé sur une grosse partie de la commune de Neufchâteau: à savoir les sections de Neufchateau (ville), Longlier et Hamipré. Au total, 5883 batiments ont été importés avec l’outil buildings.osm.be et JOSM. Cela concerne des batiments avec adresses (maisons, appartements, batiments commerciaux) mais aussi des abris de jardins, des batiments agricoles, etc.

En faisant cet import, j’ai pu comparer le PICC et OSM, ainsi que les dernières images aériennes disponibles (printemps 2021). Le résultat:

• 76 nouveaux batiments, avec “source:geometry:ref=missing” (lien overpass): des nouveaux batiments, souvent avec un tag “building=construction” ou bien “start_date=20xx”, ou encore un tag “fixme=housenumber”, quand le numéro du batiment est inconnu.

• 17 batiments détruits, avec la clé “razed:building” ou “demolished:building” (lien overpass)

• un ou l’autre batiment modifié, pour lesquels j’ai omis de mettre l’étiquette “source:geometry=outdated”, mais qui était très peu nombreux.

La suite

Suite à des contacts avec le SPW, nous avons une liste de communes où le PICC a été mis à jour récemment. C’est sur ces communes qu’on peut concentrer l’effort. Toutefois, le plupart de ces communes ont déjà beaucoup de batiments dans OSM, et il est clair que réaliser un import de batiments du PICC là où des batiments OSM existent déjà prend beaucoup plus de temps que d’importer des batiments dans une zone vierge. La liste de ces communes, classées par le nombre d’adresses déjà existantes est:

Si vous êtes intéressé·e·s à réaliser des imports sur ces communes ou d’autres endroits, lisez la documentation, contactez la communauté et bonne cartographie!

The OSMF is pleased to financially support the en.osm.town OpenStreetMap Mastodon (or “Mapstodon”) service.

The OpenStreetMap Foundation has had a Free & Open Source Software Policy, and a committement to open communication channels. We exist to support the OpenStreetMap project.

Mastodon (aka “The Fediverse”) is a distributed social media network, based on the ActivityPub internet standard. It’s been featured on the New York Times, Vice and Wired. Think of Twitter, but based on open internet protocols, and allowing each community to define its own rules and build its own local community. The Fediverse has a reputation of being nicer and more respectiful than some of the more combative social media spaces.

The en.osm.town Mastodon Mapstodon instance was set up in July 2018 and has been steadily used by hundreds of OSMers over the years. Since the start, we’ve been using the excellent service from Masto.host to host this little corner of the fediverse. Some of the Mapstodon users have been spreading flyers at in person State of the Map conferences. Since this little community has been constantly active and helping each other, the OSMF decided to step up and help support this, and fund it directly.

Our own FOSS Policy Special Committee, and Communication Working Group had recommended this action.

The server was founded & administred by @amapanda@en.osm.town, with moderation from others. (Although Amanda is on the OSMF Board, this is separate from the Board). While the OSMF is funding this project, there will be no change to the moderation & administration of the server. The OSMF “supports, but does not control” OpenStreetMap.

If you want an easy way to mirror your posts to Mastodon, you can use a “Cross Poster” like the Mastodon-Twitter Crossposter or Moa.party. Many OpenStreetMap twitter accounts have set up cross posters, such as State of the Map, twitter @sotm is @sotm@en.osm.town, or the main OpenStreetMap Twitter account (@openstreetmap) is @openstreetmap@en.osm.town

So, sign up, get your pineapple, start tooting and boosting, and have fun!

• Create a mastodon account on the instance
• Follow @openstreetmap@en.osm.town, or @sotm@en.osm.town for our global State of the Map conference.
• See what’s happening on en.osm.town right now (The “Public Timeline”)
• Check out the #OpenStreetMap hashtag on the global fediverse
• Read more about Mastodon on the OpenStreetMap wiki
• Get a Mastodon mobile app
• A more detailed Guide to Mastodon
• Get an OpenStreetMap Mastodon flyer
• Previously on blog.osm.org

The OpenStreetMap Foundation is a not-for-profit organisation, formed to support the OpenStreetMap Project. It is dedicated to encouraging the growth, development and distribution of free geospatial data for anyone to use and share. The OpenStreetMap Foundation owns and maintains the infrastructure of the OpenStreetMap project, is financially supported by membership fees and donations, and organises the annual, international State of the Map conference. Our volunteer Working Groups and small core staff work to support the OpenStreetMap project. Join the OpenStreetMap Foundation for just £15 a year or for free if you are an active OpenStreetMap contributor.

Le premier journal

Dès aujourd'hui je vais écrire des journaux dans le fonctionnement lors de faire du vélo.

Denpasar

Who am I?

Hi, everyone!

Since this is a diary, I’ll try to keep it that way.

I am from Nepal & a Software Engineering undergraduate student at CODE University in Berlin, Germany since 2019.

That makes me a non-EU international student. Like most students in technology, I also work part-time at a startup, hypcloud, for experience and other perks.

I like the process of creating a tech product, particularly ideation sessions, user stories & figuring out tech problems.

Why GSoC?

There were a few students who completed GSoC at our university and organized a session sharing their experiences. That made me curious. I found OpenStreetMap(OSM) from the list of organizations, mapped my home, and liked the product.

You can find my application here

What am I building?

Geo-referenced image viewer

User story

• An OSM user takes photos of different restaurants, supermarkets, and other cafes from his/her phone on a given day

• The user now wants to update the opening and closing hours of one of the restaurants with help of the photos he/she took some time ago

• By dragging and dropping (or importing) those photos in the iD editor, the user wants to see all the photos on the OSM & fill out the business hours (opening and closing) side-by-side

A pictorial representation of the user story can be found here

How to reach out to me?

Github or

mukesh.jaiswal@code.berlin

Con oggi, 26 giugno 2022, è stato completato da parte mi il lavoro di rifacimento delle relazioni delle seguenti reti urbane autobus del Friuli Venezia Giulia: urbana Monfalcone, urbana Lignano, urbana Grado

MONFALCONE (aggregato Ronchi e Staranzano)

• LS (linea storica)
• LP (linea Panzano)
• CC (circolare centro)
• CA (circolare Aris)
• CS (circolare Staranzano)
• CL (circolare Lisert)
• RD (circolare Ronchi destra)
• RS (circolare Ronchi sinistra)
• SC (linea diretta Stazione-Cantieri)
• 28P (servizio integrativo Via Bagni park - Cantieri)

LIGNANO SABBIADORO (annesse fraz. Pineta e Riviera)

• A1 (linea Darsena Vecchia - Viale Adriatico)
• A2 (linea Darsena Vecchia - Parco Zoo)
• BN (linea notturna ByNight)
• M1 (linea Mercato - Viale Adriatico)
• M2 (linea Mercato - Darsena Vecchia)

GRADO(annesse fraz. Pineta e Valle Cavarera)

• 37 (circolare urbana)

TRIESTE

Aggiunta diramazioni linea G51 per la Wartsila e per Piazza Oberdan, nonchè la correzione dei tratti e delle fermate mancanti della tratta per l’Aeroporto di Ronchi. Aggiunta in data odierna anche la linea 20 express per Muggia.

Oltre alle relazioni sono state create (ove mancanti) le fermate ed i vari spezzoni per permettere l’inserimento del percorso; inoltre ho aggiornato le etichette nelle fermate con tag e valori obsoleti.

• Alessandro Carmeli

I tried opengeofiction, but it is closed, make you wait and stuff, how do i make my own openstreetmap like thing on a chromebook?

14/06/2022-20/06/2022

Breaking news

• The next OSMF Board meeting will take place on Thursday 30 June 2022, at 13:00 UTC via the OSMF video room (which opens about 20 minutes before the meeting). The draft agenda is available on the wiki. The topics to be covered are:
  • Treasurer’s report
  • Updated membership prerequisites plan
  • Consider directing the OWG to cut access off due to attribution or other
    legal policy reasons, if flagged by the LWG
  • OSM Carto
  • OSM account creation API
  • Advisory Board – monthly update
  • Presentation by Mapbox Workers Union
  • Guest comments or questions.

Mapping

• ViriatoLusitano has updated > his very detailed and richly illustrated guide describing how to integrate data from the National Institute of Statistics (INE) into OSM, with names and georeferenced boundaries of different urban agglomerations.
• Anne-Karoline Distel made a short report on her mapping trip to North Wales.
• At this year’s SotM France conference, Stéphane Péneau gave an overview of street-level imagery, from hardware choice to file management.
• Requests have been made for comments on the following proposals:
  • school=entrance to deprecate the use of the tag school=entrance.
  • exit=* to deprecate entrance=exit, entrance=emergency, and entrance=entrance in favour of clearer tags.
  • Emergency access and exits to address issues with the current tagging of these items.
  • aeroway=stopway for mapping the area beyond the runway that has a full-strength pavement able to support aircraft, which can be used for deceleration in the event of a rejected take-off.
  • runway=displaced_threshold for mapping the part of a runway which can be used for take-off, but not landing.
  • school:for=* a tag for schools to indicate what kinds of facilities are available for special needs students.
  • information=qr_code for tagging a QR code that provides information about a location of interest to tourists.
• Voting on the pitch:net=* proposal, for indicating if a net is available at a sports pitch, is open until Saturday 2 July.
• Voting on the following proposals has closed:
  • aeroway=aircraft_crossing to mark a point where the flow of traffic is impacted by crossing aircraft, was approved with 14 votes for, 0 votes against and 0 abstentions.
  • substation=* to improve tagging of power substations and transformers mixing on the same node, was approved with 11 votes for, 1 vote against and 0 abstentions.

Community

• In the 133rd episode of the Geomob Podcast, Muki Haklay, Professor of Geoinformatics at UCL, an early adopter of combining geography with computer science and one of the earliest supporters of OpenStreetMap, is the guest. There is a discussion about extreme Citizen Science.
• Nathalie Sidibé > , from OSM Mali, is now involved in another community: Wikipedia! Her commitment to the Malian community, to open source data and of course to OSM has already been featured in several profiles. Now there is her full biography > and an initiative of the ‘Les sans pagEs‘ > women geographers project.

Imports

• Daniel Capilla provided > an update about the import of Iberdrola charging stations for electric vehicles in Malaga, which is now complete. The data is available under an open licence from the Municipality of Malaga (Spain). He maintains a corresponding wiki page for the documentation and coordination of open data imports.

Events

• YouthMappers UMSA, a recently opened chapter of YouthMappers in Bolivia, tweeted about their first OpenStreetMap training activity on 22 June.
• Videos of the presentations at the SofM-Fr 2022 conference are now available online. A session listing for the conference, which was held 10 to 12 June in Nantes, is available > on their website.

Education

• Anne-Karoline Distel explained in a new video how to add running trails to OpenStreetMap.
• Astrid Günther explained, in a tutorial, how she created vector tiles for a small area of Earth and hosts them herself.

OSM research

• Youjin Choe, a PhD student in Geomatics at the University of Melbourne, Australia, is looking for your advice on a potential focus group study on the design of the OSM changeset discussion interface. Her research topic is on the user conflict management process in online geospatial data communities (which has mixed components of GIS, HCI, and organisational management).

Maps

• Hub and spoke is a map that shows the 10 nearest airports to a given position.
• CipherBliss published a thematic map of places to eat based on OpenStreetMap, ‘Melting Pot‘ > .

Open Data

• [1] Osmose is now using open data to compare against OpenStreetMap data to find any missing roads or power lines in OSM. At present comparisons are made for power lines in France and highways in Spain.

Software

• The first version of ‘Organic Maps’, a free and open source mobility map app for Android and iOS, was released > last June (2021). After more than 100,000 installations and one year of intensive development work, the results and plans for the future are presented.

Programming

• The new OSM app OSM Go! is looking for translators and developers.

Releases

• Version 17.1 of the Android OSM editor Vespucci has been released.
• With version StreetComplete v45.0-alpha1 Tobias Zwick introduced the new overlays functionality.

Did you know …

• … that there are apps out there helping you find windy roads? Curvature, Calimoto and Kurviger are just some examples.
• … the MapCSS style for special highlighting of bicycle infrastructure in JOSM?
• … HistOSM.org, which renders historical features exclusively?
• … the Japanese local chapter of OSMF, OSMFJ, maintains a tile server and also offers a vector tile download service (via user smellman)? More details are on the wiki > .

OSM in the media

• OpenStreetMap featured > (see video ) ) in an overview of a wide range of modern mapping technologies in a segment on the France24 news channel. The OSM examples were: participative mapping in Africa (3m17s); and, Grab’s use of OSM in South-East Asia (4m10s), which allows them, unlike other map providers, to take into account the reality of Asia with rainy seasons and a lot of narrow roads. Other topics include Apple’s 3-D visualisation of Las Vegas, 360 degree image capture, indoor mapping and geoblocking.

Other “geo” things

• Matthew Maganga wrote, in ArchDaily, about the inequalities created through modern mapping methods and especially Google StreetView.
• Google Earth blogged about how they process Copernicus Sentinel-2 satellite images daily to create a current and historical land cover data set.
• Saman Bemel Benrud, an early Mapbox employee, looked back at the 12 years he worked at the company and describes how it changed over time – leading to a failed attempt to found a union, which was part of the reason he left the company last year.
• Canada and Denmark had a decades long land dispute, called the Whisky War, over an uninhabited Arctic island between Nunavut and Greenland. Following an agreement to divide control of Hans Island / Tartupaluk / ᑕᕐᑐᐸᓗᒃ, Canada now has a land border with a second country after the United States. Note that Canada also shares a maritime border with a second European country (France) near Newfoundland (second because Greenland is a constituent country of the Kingdom of Denmark).

Upcoming Events

Where	What	Online	When	Country
Arlon	EPN d’Arlon – Atelier ouvert OpenStreetMap – Contribution		2022-06-28
Hlavní město Praha	MSF Missing Maps CZ Mapathon 2022 #2	Prague, KPMG office (Florenc)		2022-06-28
City of New York	A Synesthete’s Atlas (Brooklyn, NY)		2022-06-29
Roma	Incontro dei mappatori romani e laziali		2022-06-29
	[Online] OpenStreetMap Foundation board of Directors – public videomeeting		2022-06-30
Washington	A Synesthete’s Atlas (Washington, DC)		2022-07-01
Essen	17. OSM-FOSSGIS-Communitytreffen		2022-07-01 – 2022-07-03
	OSM Africa July Mapathon: Map Liberia		2022-07-01
	OSMF Engineering Working Group meeting		2022-07-04
臺北市	OpenStreetMap x Wikidata Taipei #42		2022-07-04
San Jose	South Bay Map Night	✓	2022-07-06
London	Missing Maps London Mapathon		2022-07-05
Berlin	OSM-Verkehrswende #37 (Online)	✓	2022-07-05
Salt Lake City	OSM Utah Monthly Meetup		2022-07-07
Fremantle	Social Mapping Sunday: Fremantle		2022-07-10
München	Münchner OSM-Treffen		2022-07-12
20095	Hamburger Mappertreffen		2022-07-12
Landau an der Isar	Virtuelles Niederbayern-Treffen	✓	2022-07-12
Salt Lake City	OSM Utah Monthly Meetup		2022-07-14

Note:
If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by Lejun, Nordpfeil, PierZen, SK53, SeverinGeo, Strubbl, Supaplex, TheSwavu, YoViajo, derFred.

(original post in English)

Selon les régions considérées, la pratique habituelle du ski nordique est différente. Si en Europe de l’ouest, dans la grande majorité des cas on peut s’attendre à ce qu’une piste de ski de fond soit préparée avec un plan lisse pour le skating et au moins un paire de rails pour le style classique, ce n’est pas le cas partout dans le monde.

Dans certaines régions, la préparation des pistes est plus légère, et la pratique du ski de fond majoritaire est plutôt celle du « ski de randonnée nordique » avec des skis larges.

Sur OpenStreetMap, pour différencier ces pratiques très différentes, on utilise le tag piste:grooming .

Mais aujourd’hui (25.06.2022), pour 24 % des pistes de ski fond, soit tout de même 22’303 km, impossible de savoir quels skis prendre.

Alors cet été, à défaut de sortir la dameuse du hanger, à vos souris pour renseigner les pistes que vous connaissez !

Sur Opensnowmap.org, ces pistes sont signalées par des pointillées à partir du niveau zoom 12, et d’un skieur un peu perdu à partir du zoom 15.

Pour trouver ces pistes ou piste:grooming n’est renseigné ni sur les way, ni sur une relation, vous pouvez utiliser cette requête Overpass : https://overpass-turbo.eu/s/1jEl.

Petit rappel des définitions sur le wiki OSM :

• piste:grooming=classic - Deux rails sont préparés pour le style classique ou alternatif.

• piste:grooming=classic;skating - Plan lisse pour le skating et au moins une paire de rails pour le classique.

• piste:grooming=skating - Uniquement un plan lisse pour le skating (ou style libre).

• piste:grooming=scooter - Piste pour le classique damée par une moto-neige, la piste est moins tassée et à une seule voie.

• piste:grooming=backcountry - Piste non préparée mais balisée pour la randonnée nordique, ce sont les skieurs qui font la trace.

Depending on the area, the default nordic skiing practice differs a lot. While in western Europe one can expect a wide area for skating plus tracks for classic style skiing, this is not the case everywhere in the world.

In some regions, the piste preparation is much lighter and the majority of pistes are just signposted crosscountry ski routes for crosscountry touring with extra-large skis.

On OpenStreetMap, we use the tag piste:grooming  to describe accurately the various practices.

Yet today (25.06.2022), there is no way to know what kind of gear is well-suited to run 24 % of the nordic skiing pistes already mapped, that is 22’303 km.

This summer, no need to get the snowcat out of its shed, just take your mouse to update the tags on pistes you know !

On Opensnowmap.org, these pistes appears with a dashed pattern from zoom 12, and display a perplexed skier from zoom 15 onward.

You can also find pistes where the piste:grooming tag is no set on a way nor a relation from this overpass query : https://overpass-turbo.eu/s/1jEl

[out:json][timeout:90];
way["piste:type"="nordic"][!"piste:grooming"]({{bbox}}) -> .nogroomingway;
rel(bw.nogroomingway)["piste:type"="nordic"]["piste:grooming"] -> .groomingrel;
way(r.groomingrel) -> .groomingway;
(.nogroomingway; - .groomingway;);
out geom;

Here is a reminder of the wiki’s definition:

piste:grooming=classic  Two rails for classic style nordic.

piste:grooming=classic;skating  Wide piste for skating and at least one set of classic rails.

piste:grooming=skating  Wide piste for skating (or ‘free’) style nordic.

piste:grooming=scooter  Classic style groomed by a smaller snowmobile, which means that the piste is often much looser and single lane.

piste:grooming=backcountry  Un-prepared itinerary for cross-country skiing, tracks are made manually by skiers.

Postcodes are a curious thing. Not every country in the world has them. But where they do, postcodes tend to play an important role for locating areas. If you are in a country with postcodes, you likely know your home postcode by heart and will be regularly asked for it. And because you have to remember it, it makes sense to also use it when searching for places. It’s much shorter and more precise than a full address. Time to take stock of postcodes in OpenStreetMap to see how useful they are for geocoding.

How Nominatim uses postcodes

Nominatim uses postcodes in two different ways. First of all, it needs to make postcodes searchable. That means having a database of all existing postcodes for every country together with its approximate location. Second, it wants to be able to present a postcode for every result, even if the found place doesn’t have a postcode mapped. That means inferring the postcode from the surrounding objects.

Postcodes in OSM

Postcodes can be mainly found in two forms in OSM: as part of an address or as a self-contained postcode area.

Postcode areas are multipolygons with a boundary=postal_code tag. They are a rare occurrence as the map below shows. Only France, Germany and Hungary have a full coverage with postcode areas. Belgium still has coverage for a good part of the country. The coverage in other countries is so patchy that it is fair to assume that the data is not up-to-date.

So what about the rest of the world? There is still a lot of postcode information found in the form of addresses.

Postcodes in addresses are tagged with addr:postcode and give us the most accurate information about the postcode for a single spot on the map. There are approximately 84 million postcode tags in the world and Taginfo shows that they are neatly distributed over the planet.

In fact, they are dense enough that it is possible to infer a postcode for most inhabited places on the planet, simply by looking up the closest addr:postcode tag. The question is: how reliable are the postcodes mapped in OSM?

The quality of postcodes

To get an estimate of the quality of postcodes we can start with a simple check: has the postcode the format that we would expect for the country. Luckily, Wikipedia has a handy list of postcode formats in the world, a perfect starting point for a quality check of OSM. It turns out that postcodes are fairly regular. Most countries opt for a simple 4, 5 or 6-digit number. A handful of countries adds the letters A-Z and optional spaces to the list but that is it. The record for the longest postcodes are held by Iran and Ghana with a length of 10 characters. You won’t be surprised to hear that both countries have a very high rate of formatting errors in OSM postcodes.

To check the OSM data, we just have to turn the Wikipedia list into something machine-readable and have the computer compare it with the OSM data. You can see the result of this analysis displayed below.

Countries in green have less than 1% of postcodes with an error. Yellow means that less than 10% of the postcodes are wrong. Countries in red have more than 10% errors. Countries that don’t have postcodes have been left white. To be fair, most of the red countries have introduced postcodes very recently and therefore postcode coverage in general is very low at the moment. The quality is bound to improve once postcode usage picks up in general. The clear winners in the statistics are Iceland, Danmark and Liechtenstein. Despite a very dense coverage with postcodes, not a single error could be found.

Fun fact: there is a common kind of error with the addr:postcode tag that is found in many countries: the tag contains the telephone area code instead of the postcode. The age of the letter in writing is clearly coming to an end.

Overall only 0.14% of postcodes are wrongly formatted. That is quite encouraging although it still doesn’t really tell us how many postcodes are wrong. A postcode might be well formatted but still have typos in them. Finding such postcodes is much harder. However, we can get an estimate about the number of errors by looking at Germany and France. For both countries we have postcode areas and we can check the postcodes of address points against them. For Germany, there are about 0.1% postcodes that do not match their area, for France 0.7% postcodes are wrong. This is significantly more than there are wrongly formatted postcodes but still so little that it is fair to say that postcode data in OSM is quite reliable.

QA for postcodes

Do you want to have a look at the typical errors and maybe even fix some of them? The Nominatim QA site now includes a view that shows postcodes which do not comply with their country’s official format:

Postcode filtering for Nominatim

The overall goal for doing the analysis in the first place was to see how postcode handling can be improved in Nominatim. It turns out that filtering suspicious postcodes is a very easy thing to do because postcode formats are so very well regulated and are used quite consistently in OSM.

Starting with the next version, Nominatim comes with a sanitizer for postcodes. It filters out all the postcodes that do not comply with the official format of the country. It will still show you wrongly mapped postcodes for the object where you mapped them. But it will no longer use postcodes that “look wrong” to infer the postcode on neighbouring objects or allow you to search for them.

In the long term, it would be nice to do more detailed consistency checks on the postcodes. Postcodes are usually not assigned randomly but are grouped by area. In France, for example, the first two numbers are always the same as the department number. Hints like these could be helpful to find more mapping errors. This, however, requires more sophisticated methods than a simple regular expression check and is something for another blog post.

mes coordonnées

*46.89229369426986 *4.676101134753768

1. 2.

Modisi

Be careful with when working with Microsofts automatically identified buildings in RapID. Microsoft is apparently using its misaligned imagery therefore buildings are misaligned.

Check geometry with correctly aligned imagery before uploading.

Here is an example of two microsoft buildings (marked with arrows):

31.05.2022 I have published an open letter to the members of the OSMF foundation board regarding the problems I believe the community is facing in creating the main style of OpenStreetMap. The heated discussion that took place around this topic surprised me a lot. I didn’t think that so many involved editors from different parts of the world share my concerns.

On 06.06.2022 at the Engineering Working Group meeting this topic was raised, there is a note about this in the meeting record:

Follow up on osm-carto frustration

Brandon notes that the OWG have an outstanding issue on their public >tracker related to possible technology alternatives to OSM Carto. Unfortunately, >discussion is cut short as the scheduled meeting time is about to end.

As for me it is a bit of a pity.

30.06.2022 13:00 UTC At the meeting of the Board of Directors the mysterious topic of OSM Carto will be discussed. I am already looking forward to my participation in this event. Will you also take part in it? Here is the link for those who are interested:

(https://osmvideo.cloud68.co/user/ror-nt7-6tu)

I hope that this time I will not be disappointed and the board will find a solution to this problem, or at least start a consultation among the community. Which will contribute to the democratisation of the process of creating our flagship style

It’s once again time for an edition of our interview series with OpenStreetMap communities around the world. Today we hear from Martijn van Exel all about OpenStreetMap in Utah.

1. Who are you and what do you do? What got you into OpenStreetMap?

My name is Martijn van Exel and I’ve been involved in OSM for a pretty long time. In fact, I just celebrated my 15th OSM editing anniversary! I made my first edit at a mapping party in Amsterdam, where I lived at the time. I don’t remember how I learned about the mapping party, probably some open source usenet group. I do remember thinking: “of course, this makes so much sense - a free and open map that everyone can contribute to!” The tools were rudimentary back then, we had no aerial imagery to trace from, so it was basically just walking and biking the streets of Amsterdam and taking notes. We had to cover every street multiple times to get enough data to reliably map the streets; the handheld GPS units we had were not that great, and the urban canyon effect is real.

I started helping organize more mapping events and helped write a grant proposal that got us money to further build the community and purchase handheld GPS units we would loan. A real light bulb moment for me was attending the State of the Map 2008 in Limerick. Seeing people from all over caring so much about this project was amazing. I helped organize State of the Map 2009 in Amsterdam, where we first saw real interest in OSM from businesses. From then on, I have basically been involved in OSM non-stop.

2. What would you say is the current state of OSM and the OSM community in Utah?

The OSM community in Utah is strong, but also a bit disconnected. We have many active mappers, but many of them just do their thing, mapping solo in their spare time. There’s a fair amount of communication online, but I have not met most active mappers in person. In part that is because Utah is large, about the size of Romania, and for the most part sparsely populated. Even the Salt Lake City metro area is large enough that it’s hard to get people to get together just because of the travel times involved.

3. What are the unique challenges and pleasures of OpenStreetMap in Utah? What things should the rest of the world be aware of?

Outdoor recreation is huge here: mountain biking, hiking, skiing camping, off-roading, fishing.. Whenever I go on a camping trip I download offline OSM maps on the Gaia GPS app, and I also check OSM in the area where I’m headed. More often than not I will find that another local mapper has updated trails, natural features, access restrictions—all the stuff that is important for an outdoors adventure that you often won’t find on any other map. Many people from out of state and abroad come to Utah to visit National Parks such as Arches, Zion and Bryce Canyon. If you are planning a visit to one of these places or any of the other awesome places of natural beauty here, be sure to bring OSM maps, and help improve them while you’re here! Be sure to bring an app that supports offline maps: even in some of the National Parks, there is no cell service available.

4. What is the best way to get involved? Is there a regular meet-up? A mailing list? Where does the community meet online?

I have been organizing monthly meetups off and on since 2011, when I moved here. Currently they happen on the first Wednesday of the month. I announce them on Meetup and on OSMCal. I try to reach out to new and active mappers via OSM messages to get more people to join. Those who attend appreciate the sense of community that the meetups bring. The University of Utah is home to a YouthMappers chapter, but I haven’t been in touch with them. Online, we have a Slack channel #local-utah on the OpenStreetMap US Slack. If you’re not a member of this Slack, you can invite yourself here.

5. What steps could the global OpenStreetMap community take to help support OSM in Utah and the western US in general?

I would love it if it were easier to get in touch with local mappers. I built a tool, Meet Your Mappers, that helps a little bit by listing the most active mappers in your area. I am looking forward to seeing Microcosms, an extension to the OSM web site that lets you create mapper groups, become part of osm.org. If you haven’t heard about it, check out his presentation at SOTM US earlier this year.

At the national level, OpenStreetMap US has been doing an absolutely amazing job growing the OSM community nationwide. They host regular online Mappy Hours, support local groups with advice and Meetup membership costs, and organize bigger events that really create a sense of community. During COVID, we had the online Mapping USA events, and last spring our part of the United States was lucky to host the first in-person SOTM US since 2019 in Tucson, Arizona. The local team as well as OSM US did a great job making this event fun and successful.

6. This year OSM celebrates its 18th birthday, so we are well into the “teenager” stage of the project. But what will it look like when it “grows up”? Where do you think the project will be in 10 years time, both globally and in Utah specifically?

10 years is a long time to look ahead. I would argue that OSM is not quite in teenager territory yet. Perhaps more in the “Wonder Years” stage. OSM is only starting to come to terms with the fact that we’re a major player in the maps space now. The rapid growth and adoption of OSM has caused some growing pains. We haven’t really learned what it means to be a truly global and diverse community yet. We haven’t fully embraced the opportunities that growing use of and contributions to OSM data by large organizations can bring. We must face these challenges, and in 10 years we surely will have, but it will require strong vision and leadership.

Meanwhile here in Utah, we will just keep working on the map and collaborating with local and state GIS agencies to improve OSM and make it more useful. Recently, I collaborated with the Utah state GIS agency to publish an OSM-based places dataset that complements the State’s own GIS data. It is already used by 911 services to find people in emergencies more quickly. This is the kind of stuff that keeps me want to work on OSM. More than anything though, it’s the people. I have made many friends in this community. I hope to see them all this summer in Firenze at SOTM!

Thank you, Martijn - for your efforts to grow OpenStreetMap in Utah and worldwide. I also had the pleasure of attending SotM in Limerick many years ago, and it got me very motivated about OpenStreetMap. How far we’ve come since then! Thanks for the insights into the OSM Utah scene and keep up the great work.

Happy mapping,

Ed

Please let us know if your community would like to be part of our interview series here on our blog. If you are or know of someone we should interview, please get in touch, we’re always looking to promote people doing interesting things with open geo data.