How complete are addresses in OpenStreetMap in Belgium? After several status these previous years (see September 22, May 23, May 24, November 24 for Wallonia and April 2025 for all Belgium, here is an update of the situation.

The aim of this small article is to assess the completeness of addresses in Belgium for OSM, compared to official data. Basically we count the address points in OSM and in official data by municipalities. We don’t check the address quality here, we know there can be errors in OSM data, as well as in official data.

How I proceeded

Using QGIS, I gathered OSM addresses and official ones. OSM data is imported in a PostgreSQL database using ´osm2pgsql´ based on a pbf file for Belgium from the 20th of October. Official data is coming from BEST address, that gathers Belgian addresses for the 3 regions of the country.

Addresses in OSM can be mapped on buildings (most of the cases), hence on a way, or on a node. I consider only objects with the “addr:housenumber” tag. First, I made a single layer of addresses points from OSM data by merging the centroids of buildings with this tag and the points with this tag, by excluding the places where these two layers overlaps (typically points with an address inside a building where there is already an address). The method is far from perfect: I don’t consider relations, I miss some way objects with addresses but without the building tag (typically some schools), and probably a lot of other edge cases due to the “joyeux bordel” of the OSM data model. Finally I removed duplicate located at the same place.

Official data considers several address points for each building unit, or box number. It means that there are often several points at the same place, especially in cities, accounting for each box number. Since the mapping of box number is often not so used in OSM, I removed all duplicated address located at the same location. This reduces the number of official address from 7,033,422 to 4,578,368.

Then I simply count the number of OSM and official address by Belgian municipalities and compare the two.

The method and the QGIS project file is now saved in github.

The result in maps

In Belgium, I counted 4,098,458 addresses in OSM compared to 4,578,368 in official data: a ratio of 89.5 %. It was 87.6 % in the last analysis in April 2025.

But! There are actually a lot of official addresses that are already available but which match no buildings in reality: these are provisioned addresses for future buildings. It is not about a few addresses. In my municipality, about 400 addresses over ~4000 are just provisioned: they do not correspond to buildings already built at the moment. The completeness rate of many places could thus be 10% higher!

Here is the map of the completeness by municipalities

Here is a map with circles showing the number of missing addresses by municipalities. The largest missing parts are in big cities: Antwerpen, Gent, Tournai, Namur, … Brussels region looks however good, and Charleroi improved a lot since the last analysis.

Municipalities where the completeness rate is the lowest are:

1. Opwijk
2. Maarkedal
3. Vleteren
4. Mont-de-l’Enclus
5. Celles
6. Berlare
7. Ronse
8. Estaimpuis
9. Huldenberg
10. Zwevegem

Where are the missing addresses and why?

I had a look at some places where OSM is missing addresses compared to official data. It happens in 3 kinds of situations:

1) In the municipalities with the lowest completion rate, addresses are missing simply because no contributions were made in these areas: no “manual” adding of addresses nor import of buildings with addresses. Sometimes, the area was actually mapped for a long time in OSM but with buildings without addresses.

2) There are a lot of missing addresses in the largest cities: Antwerpen, Gent, Namur, Tournai, … Mapping buildings and addresses is always more complex in cities as compared to mapping small villages. Major reaffectation of land to residential areas (typically from industrial land to residential area) occurs a lot in large cities and we can find a lot of missing addresses in these areas.

3) Lastly, even in well-mapped places, there can be missing addresses simply because there are new buildings, either scattered in the streets or gathered in new districts, and the local mapper did not add these new addresses yet.

So, we have a completeness rate of about 90% in OpenStreetMap. Given the fact that some official addresses are provisioned, we are not so far from the completion, at least in terms of number of addresses. We know that OSM is sometimes more up-to-date compared to official data, but still there are some places where addresses are just missing.

How to improve the address coverage in OSM in Belgium?

The community did already a great job, but there are still some places to improve!

If you want to contribute to addresses and buildings in Belgium, you can of course add “by hand” some new buildings and addresses in your neighborhood, or even check existing ones.

But actually, a lot of buildings and addresses in Belgium were imported using the “buildings import tool”, which is almost necessary if you want to add thousands of addresses where it is still missing.

This tool was just revamped: the new version is available at https://new.buildings.osm.be/. Basically, the tool helps to detect where buildings are missing and allows to copy-paste the buildings in JOSM. It takes some times to get used to it, but after a few manipulations, you’ll be ready to import and conflate hundreds of buildings at once.

Please ask for some help for any question about using this tool: there is a discussion page here. There are also more information on this wiki page, and you can tell other OSM contributors where you are working using this map.

Hi everyone. I’d like to share a small project built on OpenStreetMap data: The Church Atlas (https://thechurchatlas.com/?src=osm-diary), a free, ad-free map of more than 3,000 churches with an interface in 18 languages. How it uses OSM: churches are imported city by city from OSM (amenity=place_of_worship with religion=christian), using name and name:xx, denomination, addr:* and wikidata. Wikidata and Wikipedia are then used for summaries, photos and, where OSM has none, street addresses (Wikidata provided addresses for about 600 churches). Every map view and church page credits “© OpenStreetMap contributors” with links to the copyright page and the ODbL. What I learned about church tagging along the way: • Many churches, especially small chapels on the Greek islands, only have a name in the local script and no name:en, so they are hard to show in other languages. • Many chapels share identical names in the same municipality, which makes them hard to tell apart without a locality. • Some objects carry only addr:housenumber without addr:street, which is not usable as an address on its own. • Some churches have no denomination tag. I’m not a professional programmer and built the site with the help of an AI assistant, so I’d especially value advice from experienced mappers: are there tagging conventions I should follow more closely, or common mistakes in how I read the data? If you spot wrong or missing churches, you can tell me on the site or here. Thanks for all the mapping that makes this possible!

Native Mappers is taking its first step towards building a community of student volunteers, geographers and mapping enthusiasts passionate about OpenStreetMap, cartography, GIS, remote sensing and community-led mapping.

The first meeting focuses on introducing our vision, exploring open mapping, identifying volunteer interests, and planning future training sessions, field mapping activities and collaborative projects.

Our mission is to connect local knowledge with open geographic data and inspire young people to map their surroundings for a better-connected world.

🌐 Website: https://www.nativemappers.github.io
📸 Instagram: https://www.instagram.com/nativemappers/
💼 LinkedIn: https://www.linkedin.com/in/native-mappers-b5603643b/
📘 Facebook: https://www.facebook.com/profile.php?id=61593913542834
💻 GitHub: https://github.com/NativeMapper
𝕏 X: https://x.com/NativeMappers

Join us in learning, mapping and contributing to the global open mapping community!

NativeMappers #OpenStreetMap #CommunityMapping #GIS #RemoteSensing #Cartography #YouthMappers

Hallo zusammen,

hinter diesem Konto steht Rücksitzhelden, eine kleine, kostenlose App für Familien auf langen Autofahrten. Sie zeigt Ausflugsziele und familienfreundliche Restaurants direkt an der Route, jeweils mit dem Umweg in Minuten. Gemacht wird sie von Martin Faust aus Berlin.

Für die Restaurants nutzen wir OpenStreetMap-Daten (© OpenStreetMap-Mitwirkende, ODbL). Dabei fällt uns immer wieder etwas auf, und oft melden sich Inhaber direkt bei uns, wenn sich ein Name geändert hat oder die Öffnungszeiten nicht mehr stimmen. Diese Korrekturen wollen wir nicht nur bei uns eintragen, sondern auch an OSM zurückgeben.

So arbeiten wir:

• Nur einzelne Korrekturen von Hand, keine automatisierten oder Massenänderungen. Jede Änderung prüft und gibt ein Mensch frei.
• Ein Changeset pro Objekt, immer mit Kommentar und Quelle.
• Quellen: die Website oder das Impressum des Betriebs, Auskünfte der Inhaber, eigene Ortskenntnis. Niemals Google Maps oder andere Quellen mit unpassender Lizenz.
• Im Zweifel eine Notiz statt einer Änderung, zum Beispiel wenn ein Betrieb geschlossen haben soll, wir es aber nicht sicher wissen.

Wenn euch an einer unserer Änderungen etwas auffällt, schreibt gern einen Kommentar zum Changeset, eine Nachricht an dieses Konto oder eine Mail an hallo@ruecksitzhelden.de. Wir antworten und korrigieren.

Danke an alle, die OSM möglich machen. Ohne eure Arbeit gäbe es die App so nicht.

Martin

English summary: This account belongs to Rücksitzhelden (ruecksitzhelden.de), a small free app for families on long car trips in Europe that uses OSM data for restaurants. We fix what restaurant owners tell us or what their own websites state, one object per changeset, by hand and with a human review, never from Google Maps or other incompatible sources. Questions or concerns: comment on the changeset, message this account, or write to hallo@ruecksitzhelden.de.

I want to install shareit to windows

15/10/2026-21/10/2026

Mapping

• Mateusz Konieczny has proposed bot edits that would remove wall=wall from barrier=wall objects (and nowhere else) and do the same for fitness_station=yes and fitness_station=fitness_station on leisure=fitness_station, crossing=yes on highway=crossing, bollard=yes on barrier=bollard objects.

• Requests for comments have been made for the following proposals:

• Tykayn, aka Baptiste Lemoine, proposes phasing out amenity=hospital in favour of healthcare=hospital. Voting on this is planned to take place from 5 to 19 November.
• HuggeK, PizzaTreeIsland and FairwayMapper want to use type=sport, along with golf=course and golf=tee_markers, to map golf courses with multiple courses and tee-dependent values.

Mapping campaigns

• The Ballerup Municipality announced five new MapRoulette challenges covering all five Danish regions, with nearly 90,000 tasks to help improve OpenStreetMap.

Community

• Four ministries of the Government of Québec have granted explicit authorisation to incorporate their geographical data into OpenStreetMap. The OSM Contributors wiki page contains a link to the authorisations. It should be noted that the Ministry of Natural Resources and Forests limits their authorisation to the dataset explicitly mentioned. Québec contributors subsequently started a discussion on the OSM Community forum to plan the steps for integrating these significant additions of data into OpenStreetMap: reviewing administrative boundaries, integrating address points and buildings, and harmonising street names.

• FooBar99 explained how aerial imagery can be used while offline mapping in JOSM. To do this, he uses the Python tool MapTilesDownloader, which downloads tiles at any zoom level.

• OpenCage interviewed Sofia Pahaoja, creator of Touch Mapper, in the latest of their OpenStreetMap interview series. Touch Mapper uses OpenStreetMap data and 3D printing to create tactile maps for visually impaired people.

OpenStreetMap Foundation

• The OpenStreetMap Foundation announced the election of Craig Allan (26.7%), Gregory Marler (26.4%), Héctor Ochoa Ortiz (25.7%), and Maurizio Napolitano (21.2%) to its board. All four candidates reached the required threshold in the first round and there were 1,656 voters in this election, with 595 ballots cast, of which 580 were valid.

• Craig Allan presented the 2026 Chairperson’s report at the OpenStreetMap Foundation Annual General Meeting, as chair of the OSMF Board. Several other reports and documents were also presented at the meeting, including the 2026 Treasurer’s report by Roland Olbricht, the 2026 Personnel Committee’s report and the minutes of the 2025 Annual General Meeting.

• The OpenStreetMap Ops Team reported that several PHP-based secondary OpenStreetMap services were temporarily offline due to a critical PHP security vulnerability.

Local chapter news

• From 2 to 4 October 2026, FOSSGIS hosted ► the FOSSGIS-OSM Community Meeting at the Linuxhotel in Essen, attended by 25 active members. Topics included association work, a Mapnik-style replica of OpenSeaMap for map printing using print.get-map.org, and an exchange of experiences regarding the Panoramax instance. The results are documented on the wiki.

Events

• Stefan Keller is inviting you to a webinar on enterprise data integration with Apache Hop on 27 October 2026 from 11:00 to 12:00 CET. It is online and free of charge. The webinar will cover the latest version, the current status of the GIS plugins, and two case studies from Glue Software Engineering AG.

• KonGeoS, the conference for geodesy students from the German speaking region, took place at Mainz University of Applied Sciences from 15 to 17 October 2026. At the exhibitors’ forum, FOSSGIS members provided ► information about open-source GIS, OpenStreetMap, and the association.

• Katja Haferkorn reported ► on the Smart Country Convention in Berlin, where FOSSGIS e.V. was represented at the lat/lon GmbH stand in the Open Source Park.

Education

• The Spatial Workflow team have assessed OpenStreetMap data completeness in Washington, DC (US), by comparing OSM’s road network with the Census Bureau’s TIGER roads, analysing building and road growth curves using full OSM history data via the ohsome API, and measuring the completeness of key attributes.

Maps

• The web app atm.gr lists ATMs across Greece on a map and in a searchable list, using OSM amenity=atm data combined with data from the banks and refreshed weekly. Attributes missing in OSM are shown as unknown, which indicates to local mappers where data can be improved.

• The Institute of Geography at the Autonomous University of Mexico maintains a web map of geosites, based on OpenStreetMap and Leaflet. Knowledge of geohistory is essential for promoting its appreciation and fostering its conservation. In this regard, the identification, documentation, and dissemination of geosites help bring the Earth sciences closer to different sectors of society and contribute to a greater understanding of the land and the natural processes that shaped it.

• At efimereuonta-nosokomeia.gr there is an independent free service that shows Greece’s hospitals on a map and in a list, including telephone numbers, directions and details of their Accident and Emergency departments. The map is based on OpenStreetMap, and the list works even without an internet connection. No registration is required, and a separate page shows which hospitals are on call today. For emergencies, the home page provides direct links to the numbers 166 (EKAB) and 112.

• MapQuest has added a Halloween-themed Surveillance layer to their Android and iOS applications based on OSM man_made=surveillance data.

• OsmAnd has updated its terrain maps and contour lines for the United States, Canada, and Mexico, using high-resolution national elevation data from the USGS, NRCan, and INEGI. The new data has about a 10 m resolution in the mainland US and about 30 m in Alaska and most of Canada and Mexico, so smaller ridges and steeper cliffs are now visible.

OSM in action

• Jan Kryšpín has launched North Up Daily, a daily map puzzle in which you have to reorient 16 rotated map tiles so that roads and rivers line up correctly, and then guess the location. The game is free to play and requires no account. If you want more, you can practise as much as you like in practice mode or compete on the leaderboard. The map data is sourced from OpenStreetMap.

Software

• Geocracia, a Brazilian news portal, released its AI prompt (beta version) but there is no OpenStreetMap attribution, even after contacting the developer about this problem.

• In episode 313 of the Freakshow podcast, Tim Pritlove introduced ► Kugelblitz, a 3D globe browser ► for macOS that uses various data sources, including Sentinel-2 Cloudless, NASA Blue Marble, Earth at Night, Natural Earth, Mapterhorn, and OpenStreetMap.

• Ratafuel is a free, open-source Android app that helps you find the cheapest fuel nearby in France. It combines open data on fuel prices with OpenStreetMap data on petrol stations. You can filter stations by fuel type, search for them in a selected town, and open a route in a sat-nav app. Ratafuel contains no adverts or trackers; access to your location is optional.

• Stadia Maps explained that a recent update pays closer attention to land cover processing and presentation in the Alidade Bright, Outdoors, and Stamen Terrain map styles.

• Gigazine explained how to use Vespucci, a free, full-featured mobile app for editing OpenStreetMap data.

Programming

• ^[1] Adam Lucke has developed FreeNauticalChart.net, an open-sourced and open-data project that aims to provide free nautical charts.

• Sarah Hoffmann reported that OpenStreetMap has not yet decided whether or not to participate in GSoC 2027. Students are advised not to get involved in projects before the participation announcement in March 2027, when OpenStreetMap’s participation will be confirmed.

Releases

• Simon Legner has released Maplair 4.0.0, an open-source JavaScript library for interactive maps, forked from Leaflet. It integrates features that previously required plugins or workarounds in Leaflet applications, including map rotation, fullscreen mode, search, heatmaps, a minimap, and legends.

• Rphyrin released version 26.10.16 of whathappened.here, a social check-in and review application built on OpenStreetMap. This update added shareable permalinks for user and location pages.

• Tobias Zwick has released StreetComplete version 64.0, which is the first stable iOS version of this editor. It may take some time for the app to become available in the App Store.

Did you know that …

• Daniel Schep has presented OSM Kids! at the SotM 2026 Lightning Talks. The talk was previously given at Mapping USA 2026 (we reported earlier).

OSM in the media

• Jakub Waller’s Papamap was featured on German Televison channel NDR.

• Chase DiBenedetto, of Mashable, explained how commuters can avoid Flock cameras using MapQuest, a navigation app launched in 1996. Its recently introduced ‘Surveillance Layer’ allows users to locate nearby Flock cameras and other surveillance systems. According to MapQuest’s terms, the data comes from OpenStreetMap contributors.

Other “geo” things

• The Regional Court of Frankfurt am Main has ruled , in a judgment that is not yet final , that Google is prohibited from publishing 3D images of a residential property. German case law on the matter is inconsistent, as the Regional Court of Itzehoe reached a different decision in a similar case in 2020.

• Before dominating the oceans with its fleets, Portugal legally built ► its right to navigate them, conquer them, and exclude its rivals. From the pontifical legitimacy of the Portuguese monarchy to the bulls of the 15th century and the Treaty of Tordesillas, the political and legal foundations of the mare clausum transformed the ocean into a space of sovereignty and overseas expansion.

• In his newsletter, Mapas Milhaud, Miguel García Álvarez presented ► twelve browser-based geography games. These included WorldGuessr (guessing locations using Street View), TimeGuessr (estimating the location and year a photo was taken), Worldle (recognising countries from their silhouettes) and Travle (naming countries as a chain of connections). His personal favourite is GeoGrid, in which you fill in a 3×3 grid.

Upcoming Events

Country	Where	Venue	What	When
🇮🇳	Ernakulam	Edapally, Kochi	Kochi Mapping Party 2026	2026-10-24 - 2026-10-25
🇮🇹	Pordenone	Consorzio Universitario Pordenone	Linux Day a Pordenone	2026-10-24
🇮🇹	Bologna	Liceo Copernico di Bologna	Linux Day 2026 a Bologna	2026-10-24
🇮🇹	Parma	Officine On/Off Parma	Linux Day 2026 Parma	2026-10-24
🇫🇷		Inclu K’fé	Cartopartie à Orx	2026-10-24
🇮🇹		Biblioteca comunale Alda Merini	Linux Day Casorate Sempione 2026	2026-10-24
🇩🇪	Berlin	Wikimedia e.V. Tempelhofer Ufer 23-24,10963 Berlin	OSM Hackweekend Berlin-Brandenburg 10/2026	2026-10-24 - 2026-10-25
🇸🇪	Uppsala	Datorföreningen Update	Mapping meetup in Uppsala	2026-10-25
🇮🇳	Bengaluru	Olive Street Food Cafe, 7th Cross Road, BTM Layout	OSM Bangalore Mapping Party	2026-10-25
🇮🇳	Noida	Noida	OSM Delhi NCR Mapping Party No.33 (Noida)	2026-10-25
			a11y-Score: ein OSM-Barrierefreiheitswerkzeug	2026-10-26
			CartONG : Mapathons en ligne 2026-2027	2026-10-26
🇮🇹	Milano		Formazione Wikimedia Italia - OpenStreetMap: tasking manager	2026-10-26
🇩🇪	Heidelberg	DEZERNAT#16	Rhein-Neckar OSM Treffen	2026-10-26
🇩🇪	Stadtgebiet Bremen	Online und im Hackerspace Bremen	Bremer Mappertreffen	2026-10-26
🇫🇷	Saint-Étienne	Zoomacom	Rencontre Saint-Étienne et sud Loire	2026-10-26
🇲🇽	Ciudad de México	Antiguo Colegio de San Ildefonso	State of the Map Latam 2026	2026-10-27 - 2026-10-29
			Pravidelný Missing Maps CZ-SK online Mapathon	2026-10-27
🇪🇸	Madrid	Online	Mappy Hour OSM España	2026-10-27
🇺🇸	San Jose	Online	South Bay Map Night	2026-10-27
🇦🇹	Wien	Schlupfwinkel (Kleine Neugasse 10, 1040 Wien)	80. Wiener OSM-Stammtisch	2026-10-27
🇬🇧	Derby	The Brunswick, Railway Terrace, Derby	East Midlands pub meet-up	2026-10-27
🇫🇷		La Fabrique des possibles	Réunion du groupe local de Nancy	2026-10-28
🇩🇪	Düsseldorf	Online bei https://meet.jit.si/OSM-DUS-2026	Düsseldorfer OpenStreetMap-Treffen (online)	2026-10-28
🇩🇪	Würzburg	FabLab Würzburg	Würzburger OSM-Treffen	2026-10-28
🇨🇭	Rapperswil-Jona	OST RJ Gebäude 6, Rapperswil	20. Mapathon & Mapping Party Rapperswil 2026	2026-10-30
🇮🇹	Pesaro	Biblioteca-Archivio “Vittorio Bobbato”	Linux Day Pesaro	2026-10-31
🇮🇳	नई दिल्ली	Jitsi Meet (online)	OSM India - Monthly Online Mapathon	2026-11-01
🇩🇪	Hannover	Kuriosum	Stammtisch	2026-11-02
🇨🇭	Bern	Provisorium46	Berner OpenStreetMap-Znacht	2026-11-03
			Missing Maps London Mapathon Beginner Friendly (with Training) (Online) [eng]	2026-11-03
🇩🇪	Stuttgart	Forum 3 Café	Stuttgarter OpenStreetMap-Treffen	2026-11-04
🇫🇷		Bar Le Schmilblik	Rencontre mensuelle des contributeurs Paris sud	2026-11-05
🇫🇷	Angers	L’Arrière Train, 3 rue de Frémur, Angers	Angers Rencontre mensuelle OpenStreetMap	2026-11-06
🇦🇹	Salzburg	HTL Itzling	Maker Days Salzburg	2026-11-07
🇮🇹		Angera	Mapathon @ Angera	2026-11-07
🇩🇰	København	Cafe Bevar’s	OSMmapperCPH	2026-11-08
			CartONG : Mapathons en ligne 2026-2027	2026-11-09
🇹🇼	臺北市	MozSpace Taipei	OpenStreetMap x Wikidata Taipei #94	2026-11-09

This weeklyOSM was produced by MarcoR, MatthiasMatthias, Raquel Dezidério Souto, Strubbl, Andrew Davidson, barefootstache, derFred.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

테스트용

Accept “contribution” someone said about adding more details to existing OSM but one thing it could not be more simplify as like Google map or Waze on direction from one to another. Certainly, some direction is wrong or shown with unknown name is questionable yet no idea of how to make correction? Anyone can suggest a way to change it? Keep it up with exploring. We discuss further…

ร้านดีกว่านีไม่มีอีกแล้ว

ร้านดีกว่านีไม่มีอีกแล้ว

StravaTracer — новый плагин для JOSM: щёлкните по тропе на тепловой карте Strava, и он нарисует недостающую линию.

Что он делает

• идёт по центру следа на тепловой карте, а не по его краю;
• подстраивается под популярность тропы, поэтому и малопосещаемые, и популярные тропы работают с одними и теми же настройками;
• перескакивает через прерывистые участки малопосещаемых троп и догружает тайлы, если тропа продолжается;
• не трогает то, что уже нанесено на карту, и соединяет концы новой линии с существующими;
• создаёт одну линию для выбранной тропы; ответвления можно добавлять по одному.

Всё это одна команда: Ctrl+Z отменяет её.

Как пользоваться

1. Установите stravatracer в JOSM: Настройки → Модули (JOSM 19613 или новее).
2. Откройте слой тепловой карты Strava. Проще всего это сделать с помощью расширения для браузера JOSM Strava Heatmap: оно само настраивает URL и cookies.
3. Выберите режим Strava trace на левой панели инструментов и щёлкните по тропе.

🎬 Видео с демонстрацией

Всегда проверяйте

Тепловая карта показывает, где ходят люди, но не то, существует ли там настоящая дорога и какого она типа. Сверяйте результат со снимками, ставьте правильные теги (по умолчанию highway=path) и отправляйте только то, в чём уверены.

Код, документация и сообщения об ошибках: https://github.com/erickdeoliveiraleal/josm-strava-tracer. Буду рад отзывам!

Плагин основан на идее и алгоритме osm-strava.

StravaTracer est un nouveau greffon JOSM : cliquez sur un sentier de la carte de chaleur Strava et il dessine la voie manquante.

Ce qu’il fait

• il suit le centre de la trace de la carte de chaleur, pas son bord ;
• il s’adapte à la fréquentation du sentier : les sentiers peu et très fréquentés fonctionnent avec les mêmes réglages ;
• il franchit les parties discontinues des sentiers peu fréquentés et télécharge d’autres tuiles quand le sentier continue ;
• il ignore ce qui est déjà cartographié et raccorde les extrémités de la nouvelle voie aux voies existantes ;
• il crée une seule voie pour le sentier cliqué ; les embranchements peuvent être cliqués un par un.

Tout est une seule commande : Ctrl+Z l’annule.

Comment l’utiliser

1. Installez stravatracer dans JOSM : Préférences → Greffons (JOSM 19613 ou plus récent).
2. Ouvrez la couche de la carte de chaleur Strava. Le plus simple est l’extension de navigateur JOSM Strava Heatmap, qui configure l’URL et les cookies pour vous.
3. Choisissez le mode Strava trace dans la barre d’outils de gauche et cliquez sur un sentier.

🎬 Vidéo de démonstration

Vérifiez toujours

La carte de chaleur montre où les gens passent, pas s’il existe une vraie voie ni de quel type. Vérifiez le résultat avec l’imagerie, mettez les bons attributs (highway=path par défaut) et n’envoyez que ce dont vous êtes sûr.

Code, documentation et rapports de bugs : https://github.com/erickdeoliveiraleal/josm-strava-tracer. Les retours sont les bienvenus !

Le greffon s’appuie sur l’idée et l’algorithme d’osm-strava.

StravaTracer es un nuevo plugin para JOSM: haz clic sobre un sendero del mapa de calor de Strava y dibuja la vía que falta.

Qué hace

• sigue el centro del trazo del mapa de calor, no su borde;
• se adapta a la popularidad del sendero, así que los senderos poco y muy usados funcionan con el mismo ajuste;
• atraviesa los tramos entrecortados de los senderos poco usados y descarga más teselas cuando el sendero continúa;
• ignora lo que ya está mapeado y conecta los extremos de la vía nueva con las vías existentes;
• crea una sola vía para el sendero en el que hiciste clic; los ramales se pueden trazar uno a uno.

Todo es un único comando: Ctrl+Z lo deshace.

Cómo usarlo

1. Instala stravatracer en JOSM: Preferencias → Complementos (JOSM 19613 o posterior).
2. Abre la capa del mapa de calor de Strava. La forma más fácil es la extensión de navegador JOSM Strava Heatmap, que configura la URL y las cookies por ti.
3. Activa el modo Strava trace en la barra de herramientas de la izquierda y haz clic sobre un sendero.

🎬 Vídeo de demostración

Revisa siempre

El mapa de calor muestra por dónde pasa la gente, no si existe una vía real ni de qué tipo es. Comprueba el resultado con las imágenes, pon las etiquetas correctas (highway=path por defecto) y sube solo lo que tengas claro.

Código, documentación y reportes de errores: https://github.com/erickdeoliveiraleal/josm-strava-tracer. ¡Las sugerencias son bienvenidas!

El plugin se basa en la idea y el algoritmo de osm-strava.

O StravaTracer é um novo plugin do JOSM: clique numa trilha do heatmap do Strava e ele desenha a via que falta.

O que ele faz

• segue o centro do traço do heatmap, não a borda;
• se adapta à popularidade da trilha, então trilhas pouco usadas e muito usadas funcionam com o mesmo ajuste;
• atravessa os trechos picotados das trilhas pouco usadas e baixa mais tiles quando a trilha continua;
• ignora o que já está mapeado e liga as pontas da via nova às vias existentes;
• cria uma via só para a trilha clicada; os ramos podem ser clicados um a um.

Tudo é um único comando: Ctrl+Z desfaz.

Como usar

1. Instale o stravatracer no JOSM: Preferências → Plugins (JOSM 19613 ou mais novo).
2. Abra a camada do heatmap do Strava. O jeito mais fácil é a extensão de navegador JOSM Strava Heatmap, que configura a URL e os cookies para você.
3. Ative o modo Strava trace na barra de ferramentas da esquerda e clique numa trilha.

🎬 Vídeo de demonstração

Revise sempre

O heatmap mostra por onde as pessoas passam, não se ali existe uma via de verdade, nem o tipo dela. Confira o resultado com as imagens, coloque as tags certas (highway=path por padrão) e só envie o que você tiver certeza.

Código, documentação e relatos de erros: https://github.com/erickdeoliveiraleal/josm-strava-tracer. Sugestões são bem-vindas!

O plugin é baseado na ideia e no algoritmo do osm-strava.

StravaTracer is a new JOSM plugin: click on a trail of the Strava heatmap and it draws the missing way for you.

What it does

• follows the centre line of the heatmap trace, not its edge;
• adapts to the popularity of the trail, so rarely and heavily used trails work with the same settings;
• crosses the broken parts of rarely used trails and downloads more tiles when the trail goes on;
• ignores what is already mapped and connects the ends of the new way to the existing ways;
• creates a single way for the clicked trail; branches can be clicked one by one.

Everything is one command: Ctrl+Z undoes it.

How to use it

1. Install stravatracer in JOSM: Preferences → Plugins (JOSM 19613 or newer).
2. Open the Strava heatmap layer. The easiest way is the JOSM Strava Heatmap browser extension, which sets the URL and the cookies for you.
3. Select the Strava trace mode in the left toolbar and click on a trail.

🎬 Demo video

Please review

The heatmap shows where people go, not whether there is a real way there, nor its type. Check the result with the imagery, set the right tags (highway=path by default) and only upload what you are confident about.

Code, documentation and bug reports: https://github.com/erickdeoliveiraleal/josm-strava-tracer. Feedback is welcome!

The plugin is based on the idea and the algorithm of osm-strava.

Disclaimer: Do not try this at home!

There is an ongoing DRC Ebola campaign where mappers are asked to update residential areas. All newly published projects follow the same pattern. There are a lot of small tasks to be mapped. The tasks are so small that no new residential areas need to be mapped in them. Only the existing mapping needs to be updated (move or delete buildings based on the imagery required by the project). Often the task area is completely empty.

Since the deployment of the v5.4.1 release and the panel rearrangement, completing a task takes more clicks than in the previous version. Even if you’re an experienced mapper who read the instructions before you started, the Instructions tab still opens first, so you have to switch to the Completion tab and scroll past the additional instructions to submit the task. Considering the small tasks in the campaign, the time it takes to submit a single task is more than half of the total time spent on mapping.

This is where laziness kicks in. And so does the Tasking Manager API.

The goal? Find patterns and use whatever means to speed up the process.

Prerequisites that must be met:

1. No other mappers are active on the project. This matters because you work within the area defined by the project’s task grid without locking the tasks.
2. You upload regularly to prevent conflicts (a mapper who locks a task in the Tasking Manager always takes priority over any changes you made there without locking it).

Validators may be suspicious when so many tasks are marked as mapped within seconds of each other. This diary documents the process and explains why these tasks met all the requirements to be marked as mapped.

The technical workflow in JOSM:

1. Download the project’s task grid (using the TM API). Each task boundary has its ID and status.
2. Using the search function, find the right number of small unmapped tasks with the query taskStatus=READY waylength:-300 (only the unmapped tasks with a perimeter under 300 meters).
3. In the Tags/Memberships window, right-click the <X different> value of the taskId key and copy the list of values into a text editor for later.
4. Use Download along to download all OSM data for the selected tasks as a new layer.
5. Now add the task boundaries to the TODO list.
6. Inspect the tasks one by one and mark each one as done in the TODO list.
7. Upload the data to the OSM server (don’t forget to fill in the project’s changeset comment).

The Python script (outside JOSM):

1. Use the project ID and the saved taskId list as input.
2. A small script iterates over the taskId list and calls the TM API to lock each task and mark it as mapped (two API calls per task).
3. If the script fails to lock a task, it skips it and moves on to the next one.

That completes the first iteration, and you can start over. The project’s task grid needs to be downloaded again to get the updated task statuses. Change the search query from waylength:-300 to waylength:-620. The rest of the steps remain the same. Don’t forget to update the taskId list for the script. The third iteration uses waylength:-950.

The result

After three iterations, 70% of the project was mapped and I saved roughly 5,000 mouse clicks and a great deal of time. At the time of writing, I had already used this workflow on five projects and mapped over 4,500 tasks. I didn’t encounter any merge conflicts.

Notes

I found that, for me, the sweet spot is around 200–400 tasks per batch. You can tweak the waylength value in the search query (all tasks smaller than…) to achieve the right number of tasks in the selection. The biggest slowdown was the OpenAerialMap imagery used in the Ebola campaign because its tiles load quite slowly.

When I only deleted features in a task, I just moved to the next task and uploaded the data every 100 tasks. If another mapper who locked the task had already deleted the same object, JOSM showed a warning that it no longer existed on the server, and the upload continued. If I added any features to a task, I uploaded the data immediately so my changes were already on the server in case someone else locked the task.

Conclusion

On every project, I stopped once all tasks matching waylength:-950 were done. Larger tasks take longer to update, so bypassing the Tasking Manager brings little benefit, and I suggest returning to the regular workflow with task locking.

Právě vznikla tištěná turistická mapa Prahy, na základě aktuálních dat OpenStreetMap. Je určená lidem, kteří do Prahy přijeli na pár dnů a chtějí se rychle zorientovat v tom nejzajímavějším, co Praha nabízí.

Mapový podklad je záměrně jednoduchý. Obsahuje síť ulic a jen nezbytné množství dalších informací. Díky tomu zůstává přehledný a dává prostor tomu dalšímu. Přibližně stovce zajímavých míst, která jsou na mapě vyznačena pomocí malých ilustrací a popisků. Vedle známých historických památek jsou tu i ty méně známé, moderní stavby, veřejné umění nebo technické zajímavosti.

Asi vás napadne, proč ještě dnes tisknout mapu, když máme telefony i encyklopedie v kapse. Odpověď je jednoduchá. Nejde o náhradu digitálních map. Ty používáme všichni. Papírová mapa jen nabízí jiný pohled na totéž.

Rozložená ukazuje celé historické město najednou. Vidím vzdálenosti mezi místy, představím si kudy se vydám na první pohled - a nechám oči chvíli bloudit po ulicích. Je to trochu pomalejší způsob, jak se zorientovat. A právě v tom je kouzlo map, na které už tak trochu zapomínáme. Na ostrém slunci zůstává čitelná, nepotřebuje baterii a můžete si do ní poznačit tužkou místo, které vás zaujalo. Po návratu domů se mapa promění ve vzpomínku na navštívená místa. Na zadní straně jsou stručné informace o nejvýznamnějších pražských památkách v devíti světových jazycích. Je to základní přehled bez nutnosti je hledat.

Trochu se chlubím. Graficky jsem ji připravil, vyzkoušel si, jak na každém milimetru, na každém odstínu záleží. Vydali jsme ji ve vydavatelství, v kterém se turistickým publikacím už nějakou dobu věnujeme. Je tu vidět síla čerstvých mapových dat, za nimiž stojí komunita a tak trochu i moje znalost rodného města. Míst je hodně, ale vybrat z nich sbírku vzpomínek které mám v srdci, na to už databázový dotaz nestačí. Chtěl jsem ukázat Prahu jako rozmanité a přitom ne zas tak veliké město. Nejen jako ukazovač tras od startu do cíle.

Pokud vám během návštěvy Prahy mapka pomůže jen jednou, splnila účel. A možná se tak připomene, že pomalý analogový svět ještě neřekl poslední slovo. S pomocí nových zkušeností je později můžeme propojit s budoucností.

A new printed tourist map of Prague has just been published, built directly on up-to-date OpenStreetMap data. It is designed for visitors who arrive in the capital of the Czech Republic for a few days and want a quick, clear orientation to the very best the city has to offer.

In static cartography, the base map is intentionally kept minimal. It features the street network alongside only the essential geographic elements. This clean background leaves ample room for what matters most: roughly one hundred curated points of interest, brought to life with small custom illustrations and brief labels. Beside iconic historical landmarks, the map highlights lesser-known sights, modern architecture, public art, and unique engineering points of interest.

You might wonder why anyone would print a physical map today, when we all carry navigation apps and encyclopedias in our pockets. The answer is simple: it isn’t meant to replace digital tools. We all use those daily. A paper map simply offers a different perspective on the same space.

Unfolded, it presents the entire historic city at a single glance. You can feel the true distances between places, plot out a walk visually, or simply let your eyes wander across the streets. It invites a slightly slower pace of orientation—a classic form of spatial magic we sometimes forget in the digital age. It stays perfectly legible in bright sunlight, requires no battery, and lets you mark your favorite spots with a pencil. Long after you return home, it turns into a tangible keepsake of your journey. On the back, concise overviews of Prague’s major sights are provided in nine languages, offering quick context without needing to search online.

To be a bit personal: I had the privilege of working on the graphic design and cartographic preparation for this project, testing firsthand how much every single millimeter and color nuance matters in print. It was published by our team, where we’ve been crafting travel publications for years. The finished map really showcases the strength of fresh, community-driven OSM data combined with a lifetime of personal knowledge of my hometown.

While database queries can easily return thousands of locations, filtering them down to a meaningful collection of memories requires a human touch. I wanted to show Prague as a rich, diverse, yet walkable city—not just calculate the fastest route from point A to point B.

If this map helps you navigate or discover something new during your visit, even just once, it has fulfilled its purpose. And perhaps it serves as a gentle reminder that the slow, tactile world still has plenty to offer—especially when powered by open data and brought forward into the future.

After integrating OpenStreetMap data into my own application, I noticed inaccurate or missing business information, so I started correcting it directly on OSM.

Транспортная компания «Возовоз» сократила сроки грузоперевозок в Пятигорск из нескольких крупных городов России. Обновлённые условия позволяют быстрее доставлять коммерческие и частные отправления, планировать поставки и оптимизировать логистику между регионами.

Новые сроки доставки в Пятигорск

Теперь доставка сборных грузов в Пятигорск занимает:

• Москва — Пятигорск: от 3 до 5 дней;
• Санкт-Петербург — Пятигорск: от 4 до 6 дней;
• Ростов-на-Дону — Пятигорск: от 1 до 3 дней.

Сокращение сроков особенно актуально для компаний, которым важно своевременно пополнять складские запасы, отправлять товары покупателям и поддерживать регулярные поставки. Частные клиенты также могут быстрее пересылать мебель, технику, личные вещи и другие разрешённые к перевозке грузы.

Перевозка сборных грузов по России

«Возовоз» специализируется на автомобильных грузоперевозках, в том числе на доставке сборных грузов LTL. Отправления нескольких клиентов объединяются в одной перевозке, поэтому для доставки небольшой или средней партии не требуется заказывать отдельный автомобиль целиком. Такой формат подходит для товаров, оборудования, комплектующих и других коммерческих грузов.

В зависимости от задачи можно оформить межтерминальную перевозку или заказать доставку от двери до двери. Стоимость грузоперевозки рассчитывается с учётом маршрута, веса и габаритов отправления, а также выбранных дополнительных услуг.

Рассчитайте стоимость перевозки

Чтобы узнать стоимость и срок доставки в Пятигорск, воспользуйтесь онлайн-калькулятором и рассчитайте доставку. Укажите город отправления, параметры груза и подходящий формат доставки — система поможет рассчитать стоимость перевозки и спланировать отправку.

Сокращённые сроки на направлениях из Москвы, Санкт-Петербурга и Ростова-на-Дону делают грузовую доставку в Пятигорск удобнее.

양도소득세 너무 많이 나와요..

We had an awesome, hop-py time with the UPRI YouthMappers! The other day, I had an opportunity to facilitate a mobile-first workshop where we got hands-on with Vespucci, swapped mapping tips, and learned to read topographic maps for clues about where watercourses might be. We also tackled tagging questions and talked about ways to join our #ChasingWaterways campaign.

Icebreaker participants launching themselves forward. Can you guess how this exercise is relevant to our theme?

Kudos to our hosts

A big thank-you to Feye and the lovely UPRI OSM mapping team—Erika, Raf, Steph, and Ureil—for hosting and organizing the day. I’m glad to finally tie faces to familiar, waterway-chasing usernames. It was also great to meet both current YouthMappers and a bunch of hopeful new applicants.

Everyone already knew their way around iD/Rapid, and the more experienced mappers were using JOSM, so we skipped the beginner stuff and dipped our toes into Vespucci. sometime ### Mapping from your pocket

Vespucci was a great fit for the day: it’s made just for Android, but gives mappers an option for editing on the go, and has powerful tools for more complex tasks. It can also handle MapRoulette tasks, though a recent security incident temporarily took the MapRoulette API offline. That meant awkwardly switching apps, which could get tedious when you’re on a roll.

We spent the morning exploring the app basics – plus some of the more advanced features, answering questions, and sharing ways to use of other resources alongside aerial imagery to spot waterways and check flow directions.

One of the tools we had fun with was visualizing waterways with #WaterwayMapOrg, and how all rivers flow to the sea. Or not.

Some questions—like whether Vespucci can “square” buildings or draw round shapes—also got us talking about the little editor features we all get attached to.

After a hearty lunch, it was time for a mini mapa-thon! We worked on #TulayTuloy, a beginner-friendly bridge-mapping project and a fun side quest to our bigger waterway campaign. Bridges are important structures—and useful landmarks right over the water.

How far can you jump?

We were curious about the familiar OSM rule of thumb that a stream is something an active, able-bodied person can jump across. Our project guidelines use 2 meters as the cutoff, so we put it to the test.

Most jumps landed around 1.3 meters, and the longest was 1.8 meters. No one cleared 2 meters—and there were a few laughs when people realized just how wide that is!

Afterwards, I heard somebody made a pun #TalonTalon, after the #TulayTuloy hashtag.

My favorite part of the day was exploring DEMs, contour lines and hill shading. Topographic maps can be especially useful when imagery is cloudy or unavailable, and participants were amazed that they can spot features they’d missed before once they knew what and where to look.

After all that hopping, we dove into waterway mapping, where we discovered the limitations of using small screens, explored and tried workarounds, and still managed to complete tasks, giving everyone a chance to polish their new Vespucci editing skills.

Want to try to map a waterway near you? Find a #ChasingWaterways task and give it a try!

Hop-py folks, happily posing for a group-fie.

We’ve already penciled a date for another mapa-thon next month, and we’d be very happy to see you join us, whether you map with Vespucci, or the more usual suspects: iD/RapiD or JOSM.

We’ll post a message as soon as we nail down the details. Watch for announcements in the local communities’ channels.

P.S. I’m pleased to share that many of the issues we faced with the Maproulette mobile interface has been addressed in the upcoming version 4, hopefully, that means we’d have a smoother workflow for Vespucci users in the next mapa-thon.

Ludell is a small township in Rawlins County, Kansas. I’ve mapped every building, road, the stream that goes through it.

1. OBSTACLE osm.wiki/Key:obstacle Celem tego znacznika jest oznaczanie przeszkód, które nie wynikają z właściwości drogi (nawierzchni, materiału, szerokości itp.), lecz z jej otoczenia lub właściwości lokalnych; podobnie oznacza miejsca, w których droga (najczęściej drogi wodne) napotyka przeszkody środowiskowe. Ten znacznik może być używany w aplikacjach nawigacyjnych do omijania obszarów lub wykorzystywania części drogi o niższym priorytecie podczas obliczania tras, podobnie jak w przypadku progów zwalniających, przepraw promowych lub dróg nieutwardzonych, ale może być również używany na ścieżkach przeznaczonych dla pojazdów.

Tego klucza używa również zespół Humanitarian OSM .

1. overgrown=*- Oznacza, że ​​dany obiekt, zwykle autostrada, jest porośnięty roślinnością.