OpenStreetMap Blogs Last Update:

Androidアプリ「OSM郵便マップ」をリリースしました

OpenStreetMapのデータを利用した、日本郵便向けの地図アプリです。 登録されているPOIの可視化に加え、煩雑な収集時刻の入力を補助する画面など、編集向けの機能も搭載しています。

Wiki: osm.wiki/JA:OSM郵便マップ

GPS距離判定で現地入力を強いていますが、実装検証はエミュレータではなく現地に足を運んで試してました

これから

• ゆうゆう窓口の営業時間対応
• ゆうちょ銀行ATMの表示 辺りを実装しようと考えています

8月最初の月曜日

近隣を所管する田富郵便局の平日1便の収集ルートと時間が変わるようで、サーベイした1週間後には平日収集時刻が変わることが判明しています。巡回しなきゃ…。

a day ago

在 2026 年 7 月初，Wikidata 台灣與 OpenStreetMap 台灣社群一同在嘉義高鐵站集合，架設好車頂相機，在目標區嘉義縣海線一帶鄉鎮的廟宇以及其聚落，也一邊開車一邊記錄沿途的街景。

從嘉義高鐵站旁的糖鐵車站出發，兵分多路前往嘉義縣沿海太保市、朴子市、東石鄉; 義竹鄉、布袋鎮與鹿草鄉，記錄當地欠缺的地圖圖資與照片。在車上奔馬記錄沿途街景，然後到了廟宇則下車記錄內外觀與攃拜主神。中午大家在湖口飯吃休息用中餐，而傍晚則在鹿草安溪中寮城隍廟集合，觀察廟會活動，為第一天的踏查畫下句點。

第二天的工作坊則是下午進行，在嘉義市區的活動場所台灣圖書室進行，介紹 OpenStreetMap、Wikidata 與維基導遊。

在台灣，維基與開放街圖常面臨上網人口少的地方，比較沒有人願意參與貢獻的窘境。藉由兩個社群活躍成員去台灣各地在地人低度參與的地方去記錄地方地圖圖資以及在地廟宇，補足缺少的資訊。而藉影像補捉工具的協助，如手機相機拍廟宇的外觀與內景，架在車上的 360 相機或相機記錄沿途街景，則讓我們的貢獻延伸至兩天的踏查與工作坊之後，繼續各自在電腦前面整理資料與繪製當地的地圖圖資。

在 OpenStreetMap 的發源地英國，常有一間接一間酒吧接力飲酒聊天談論社群的事情，也順便將沿途的商家記錄下來。在台灣的街景踏查團，則是一間一間的廟宇接連進行踏查，除了記錄，也順便進行 OpenStreetMap 圖資的更新。在台灣，廟宇常是當地聚落的中心點，許多公共事務在廟宇協調與分配，大型的廟宇甚至也會吸引商販前來擺攤做生意。

感謝台灣維基媒體協會與地圖公司 TomTom 的協助，提供舉辦活動所需要的資源。

a day ago

試機1

3 days ago

Bonjour, Je travaille à l’exploitation des routes départementales au Conseil Départemental des Côtes d’Armor. Afin de mener à bien nos missions, nous utilisons des application informatique dont la carto est basée sur OSM. Nous constatons de nombreuses erreur d’affectation de route. En effet de nombreux déclassement de route de route départementale vers route communale n’apparaissent pas. Nos données carto sont en open data et utilisés par l’iGN qui met donc ses cartes à jour régulièrement. Comment faire pour les cartes OSM soient le plus à jour possible. Merci

3 days ago

Querying OpenStreetMap Data with the Overpass Turbo Wizard

If you’re new to OpenStreetMap (OSM), writing Overpass queries from scratch can seem intimidating. Fortunately, Overpass Turbo provides a built-in Wizard that generates queries automatically based on simple search phrases. This makes it easy to retrieve geographic data without learning the full Overpass Query Language (Overpass QL).

What is the Overpass Turbo Wizard?

The Wizard is a feature in Overpass Turbo that converts plain-language search terms into valid Overpass queries. Instead of manually writing code, you can describe the data you want and let the Wizard generate the query for you.

For example, if you want to find schools in the current map area, you can simply enter:

text amenity=school

The Wizard will create the corresponding Overpass query automatically.

How to Use the Wizard

1. Open Overpass Turbo.
2. Zoom the map to your area of interest.
3. Click Wizard in the toolbar.
4. Enter a search expression such as:

amenity=hospital

or

shop=supermarket

1. Click Build and Run Query.
2. The matching features will appear on the map.

The generated query can also be viewed and edited if needed.

Example

Suppose you want to locate restaurants in the visible map area. Enter:

amenity=restaurant

The Wizard generates an Overpass query and displays all matching restaurants from OpenStreetMap within the current map view.

Exporting the Results

After the query runs successfully, you can export the results for use in GIS software or other applications.

1. Click Export.

2. Choose a format such as:

   • GeoJSON for web mapping and GIS tools.
   • KML for Google Earth.
   • GPX for GPS applications.
   • Raw OSM Data for OpenStreetMap-based workflows.
3. Save the file to your computer.

GeoJSON is the most commonly used format because it works well with tools like QGIS, Leaflet, and Mapbox.

Conclusion

The Overpass Turbo Wizard is the easiest way to query OpenStreetMap data without learning complex query syntax. By entering simple tag-based expressions such as amenity=school or shop=supermarket, you can quickly retrieve map features and export them in formats suitable for analysis, visualization, and GIS projects. For beginners, the Wizard provides a fast and practical introduction to the power of OpenStreetMap data extraction.

Note

• If a query fails because it exceeds the execution time limit, increase the timeout value (in seconds) in the generated query and rerun it.
• If you are unfamiliar with OpenStreetMap (OSM) tags, refer to the following resources to explore available tags and their usage:
  • OSM Taginfo
  • Tagfinder

3 days ago

I’ve been mapping out every building I can that is visible from satellite imagery and Bing Streetside throughout Mount Pleasant. I’m currently focused on finishing up the neighborhoods and businesses that are on Chuck Dawley and Coleman Blvd, and I have almost finished filling in that large area made up from those major arteries.

I really wish I could use Charleston County’s GIS viewer for addresses and building shapes (especially for newer buildings, since people keep moving here ):< ), but of course the county puts all of their GIS data under copyright. That would be fine, but I tried contacting the GIS office to see if I could get permission to use their data, specifically their address data, but they never even responded. There are a few other ways that I could “request” address data but I don’t know if those requests would even be useful for mapping purposes. Best thing to do is to go to these neighborhoods myself and mark down any addresses that I couldn’t have gathered from Streetside. I’m not sure how I will do that without looking like a creep stopping at people’s houses and marking their address down. Guess I’ll have to grow a pair and do it anyway!

I do wish Bing Streetside had better image quality. The best images are from 8 years ago, and some houses have been demolished and replaced in that time according to Esri imagery (the most up to date imagery here, probably around only a year off). There are some spots with 2020 imagery but it just looks so awful. Even with the higher quality 2014 imagery you can barely make out small details like addresses at all. It really makes you appreciate what Google Street View provides, but we can’t use that at all. No wonder Bing Streetside completely shut down.

I enjoy seeing others update the Charleston area with me. There’s a mapper named “mas” who has been doing really good work with certain areas like I’On and other places scattered around town. I bet they are actually going to these places and writing stuff down as their stuff is more detailed than mine, while I’m merely going off of satellite.

At some point I’ll go out and do some address scavenging myself. Guess I’ll find a place to park and take a nice walk throughout some of these neighborhoods. Wish gas prices weren’t as expensive as they are… If anyone has any tips for doing something like this please let me know!

3 days ago

Hi! For the last few years I’ve been building a service that exports OSM data into formats that live outside the GIS world: CorelDRAW (CDR), AutoCAD (DWG/DXF), SVG for illustrators, STL for 3D printing. It turns out the most grateful audience for OSM data isn’t cartographers at all: it’s signage designers who need a neighbourhood map as curves, civil engineers who need a DWG base plan, laser-engraving makers cutting city maps from DXF.

The main pain I had to solve was keeping LAYERS: roads, buildings and water should arrive in CorelDRAW as separate editable layers, not as one pile of curves. Every export is assembled from the same thematic groups OSM itself thinks in — roads, buildings, water, greenery, land use, POIs — and each group becomes a named layer of the target application: you can hide, recolour or delete it in one move instead of picking objects one by one. Street labels live on their own layer too — a signage designer usually wants them, a laser engraver almost never does.

The second pain is the boundary. A rectangle around a city inevitably drags in pieces of neighbouring areas, and cleaning them up by hand is painful. So exports can be clipped strictly to an administrative boundary: pick a city or district from the catalog (about 2.9 million admin areas across 179 countries) and every layer is trimmed to the outline, with cut polygons properly closed along the border.

The service: osm2cdr.com. All data © OpenStreetMap contributors, ODbL — attribution is embedded in every export. I’d love feedback from the community: what’s missing, and what feels un-OSM-ish?

3 days ago

Moin.

Zum Einen, um sie für mich selbst zu speichern, zum Anderen, weil sie vielleicht noch nicht jedem bekannt sind, ein paar hilfreiche URIs:

Copernicus Browser

Copernicus Browser der ESA, bietet verschiedene Arten von Luftaufnahmen, neben dem sichtbaren Licht auch nahes und fernes Infrarot, Ultraviolett sowie spezielle Ansichten für z.B. die Landwortschaft, Luftverschmutzung, Überschwemmungen und Dürren, Geologie, Gewässer, Schnee und Gletscher oder urbanes und die Möglichkeit, durch verschiedene Aufnahmezeitpunkt zurück zu blättern.

World Imagery Wayback Machine

World Imagery Wayback Machine, bietet die Möglichkeit, Satellitenaufnahmen in Halbjahres- bis Jahresschritten rückwärts zu blättern, ähnlich der entsprechenden Funktion in Google Earth Pro.

Waldinfo NRW

Waldinfo.nrw, bietet speziell für NRW verschiedene, spezialisierte Kartenebenen, z.B. Landbedeckung (Cop4ALL), Baumartenklassifikation (Sentinel2), Vegetations- und Gebäudehöhen (nDOM), Forstliche Standortkarten, Vogel- und Naturschutzgebiete, Freizeitkataster und Wanderwege, forstliche Rettungspunkte, etc.

YoHours

YoHours, Visualisierung von Öffnungszeitenangaben in der OSM-Syntax. Nützlich, um Öffnungszeitenangaben vor der Eintragung in OSM zu testen, speziell, wenn sich diese durch Abweichungen in einem bestimmten Datumsfenster komplex gestalten.

ELWAS NRW

ELWAS-web NRW, verschiedene hydrologische Karten für NRW, z.B. Fließgewässer- und Seekennzahlen, Hochwassergefahrenkarten, Verzeichnis der Gewässerpegel und Grundwassermessstellen.

RIO - Oberbergischer Kreis

RIO OBK, Sonderkarten des Oberbergischen Kreises, z.B. Historische Karten und Luftbilder, Freizeitkarten, Klima- und Starkregenkarten.

INSPIRE WMS NRW

INSPIRE NW Gewässernetz, Fließgewässerkarte NRW auf der Basis von ATKIS-Basis-DLM (Grundgenauigkeit ATKIS +/-3m), monatlich aktualisiert.

Digitaler Zwilling

GeoPortal NRW, Digitaler Zwilling, NRW in 3D-Luftaufnahmen. Über die Haupseite des GeoPortal NRW, auch weitere Spezialkarten, z.B. Liegenschaftskataster, Bebauungs- und Bauleitpläne, Lärmkarten und unterschiedliche Höhenlinienkarten zu Orten in NRW.

TBC

4 days ago

♦

🗺 NOVA FERRAMENTA CNEFE 2022 IBGE PARA O OPENSTREETMAP 🚀

A maior atualização da ferramenta de logradouros chegou!

O sistema que verifica nomes de logradouros a partir dos dados do CNEFE 2022 foi completamente reformulado com base no feedback da comunidade! 🔄 O QUE MUDOU? MÃO DUPLA!

Antes: Apenas corrigíamos o OSM com base no CNEFE

Agora: Compatibilização mútua entre as duas bases!

✅ Se o OSM estiver errado → Corrige no mapa (JOSM/iD) ✅ Se o CNEFE estiver desatualizado → Corrige na ferramenta

“Preparando o terreno para a futura importação em lote dos endereços!”

🎯 NOVIDADES IMPERDÍVEIS

🔐 Login via OSM - Autenticação obrigatória (adeus bots!) 📦 Edição em Lote - Resolva vários logradouros de uma vez (use com cautela!) 🔗 Integração Overpass-Turbo - Verifique fontes no OSM rapidamente 📋 Cópia Automática - Nome corrigido já vai pro Ctrl+V! 🏷 Alternador Via x Lugar - Para praças, vilas e casos especiais 📊 Histórico de Colaboração - Veja quem já ajudou na sua área

📈 Filtros e Estatísticas - Acompanhe seu progresso! 👇 PASSO A PASSO NOVO PAINEL

1. Leia o nome do logradouro no CNEFE (já corrigido com dicionário)
2. Abra no iD ou JOSM e edite a geometria
3. Digite o nome EXATO que ficou na tag name= no OSM
4. Clique em “Salvar Checagem” e pronto!

⚠️ ATENÇÃO: Maiúscula ≠ Minúscula | Acento faz diferença! 🤔 PARA QUEM É?

✅ Iniciantes que não editam OSM diretamente ✅ Mapeadores experientes no JOSM ✅ TODOS que querem contribuir com endereços precisos! 📚 RECURSOS PARA VOCÊ

📖 Manual Completo: cnefe.mapaslivre.com.br/tutoriais/pdf/logradouros_manual.pdf

🎥 Vídeo Tutorial: youtu.be/8LFIy04d78k 💬 Grupo no Telegram: t.me/grupoumbraosm 🔗 Acesse Agora: cnefe.mapaslivre.com.br

Vamos construir juntos a base para a importação de endereços! 🏠📍

OpenStreetMap #CNEFE #IBGE #MapeamentoColaborativo #DadosAbertos #OSM #Geotecnologias #MapeamentoUrbano #ImportaçãoDeDados 4 days ago

16/07/2026-22/07/2026

♦

[1] Navigation app focused on showing the exact location of building entrances and apartment number ranges | © Oleksandr Nazarenko | map data © by OpenStreetMap Contributors.

Mapping campaigns

• Ranjeet Jadhav, of Mid-Day, reported that Jaipur-based long-distance hiker Manav Singh Shekhawat has mapped more than 2,000 km of trekking trails in the Sahyadri Mountains on OpenStreetMap after walking nearly 3,500 km across the range.

Community

• In the latest OpenCage’s OpenStreetMap interview series, Matt Whilden spoke about his journey as an OSM mapper, his work supporting the community through the OpenStreetMap US Board, and his passion for creative mapping.
• Jikke Meyer plans ♦ to map football stadiums on OpenStreetMap, starting from Botswana in Africa.
• Volker Krause joined an in-person workshop at HTW Berlin to discuss topics related to mapping indoor spaces in OpenStreetMap.

Local chapter news

• OSM Malaga tooted ♦ that the Ruedas Redondas association, a cycling users’ association in Malaga, has added a bicycle parking map ♦►♦ to its website based on OpenStreetMap data. As they explained on their website, it is the ‘most complete and up-to-date’ bicycle parking map of the city, thanks to the collaborative work of the local OSM community.

Maps

• Nicolas Seriot has developed Cartopolis, a web app that renders OpenStreetMap data in a map style reminiscent of the late 1990s.
• HeiGIT presented a custom openrouteservice instance for disaster response in Venezuela, combining OpenStreetMap with real-time road-blockage data from HDX to dynamically route humanitarian vehicles around damaged or impassable infrastructure.
• Jaz Michaelking developed Fediverse Near Me, a web map based on OSM that visualises a curated selection of well-moderated social web providers that are open for registration and serve specific countries, regions, or cities.
• Alessandro Lorenzi has created OpenStreetPhoto, an interactive map that displays all the photos linked to a feature in the OpenStreetMap database. It is currently only available for Italy.
• Using the world’s restaurant data from OpenStreetMap, Vladimir Terentyev has developed a world map of dish names on restaurant signs, attempting to answer the research question: ‘Where does plov end and biryani begin, and who really draws these limits’?

OSM in action

• Stefan Keller presented two web mapping applications built on OpenStreetMap and open government data. VivaMap ♦ combines OSM POIs and buildings with official datasets to let users build customised quality-of-life indicators for Swiss neighbourhoods, while UrbanistMap lets communities collaboratively geolocate and visualise urban development projects worldwide. UrbanistMap is well suited to encouraging mappers with local knowledge to update the data in OSM.

Software

• [1] Oleksandr Nazarenko has built ♦ Pidyizdy, a navigation ♦ app focused on showing the exact location of building entrances and apartment number ranges. It is designed for couriers, taxi drivers, and utility service workers, so they don’t have to wander around apartment yards searching ♦ for the entrance.
• Pavel Gavrilov tried darkonus’ recently released JOSM plugin, FilletTools (we reported earlier). The plugin allows users to round the corners of lines and polygons, as well as convert freehand strokes into smooth ways. Pavel praised FilletTools, noting that new JOSM plugins rarely have such a strong case for becoming a standard tool in many users’ workflows.
• AnyFinder, originally released as a freemium app in 2019 for iPhone and iPad, is now available as a free browser-based application for finding, adding and editing OpenStreetMap places from phones, tablets, or desktop computers. AnyFinder uses Overpass and Postpass as its backend query engines. The app’s catalogue currently contains 286 place categories in 66 groups, from restaurants and shops to public services and natural features.Categories define what kind of place to search for, while 128 filters refine results by properties such as wheelchair access, cuisine, fuel type, or available facilities. The current dataset covers 47 structured features and 435 OSM tags. Changes to places can be submitted directly to OpenStreetMap through the app using an OpenStreetMap account.
• Tina and Eugene introduced OsmAnd’s measuring tools, including Distance by Tap, Ruler, Radius Ruler, and Target Line.
• Tina and Eugene reported also that OsmAnd has discontinued ‘merged’ maps, which were large country- or region-level files assembled from smaller regional maps. Users who have one of these maps installed will no longer receive updates for it.
• David Larlet reported that uMap has received a grant through the NGI0 Commons Fund to integrate vector tiles into uMap. The current work is focused on vector tile customisation, allowing users to modify the map style, such as removing buildings or changing road colours, so the basemap can better fit the purpose of their map.
• Stadia Maps explained that moving from a geocoding prototype to a production-level application often reveals a frustrating reality: ‘standard’ industry pricing is rarely as simple as it looks. Most caching solutions charge steep premiums (often 6–8x normal query cost) to store results, and some impose strict rules limiting caching to single-user sessions only.
• OSM user SmallCat has published josm-account-manager, a plugin that lets you manage multiple account profiles and different endpoints in JOSM. It is available for installation from JOSM‘s plugin source.
• Koharachan announced ♦, in her OSM User Diary, a fork of iD she is working on, and described its special features that ease mapping. She said that this editor introduces ♦ some AI assistance.
• Fedilab developed PawFed, a collaborative map for animal welfare. Mention @PawFed from your Mastodon account with relevant hashtags and a location, and your report will appear on the map. Shelters, veterinary clinics, lost or found animals, food donations, and other information that can help animals are displayed on the map.
• Venetis Charalampidis reported on the progress of the closures.osm.ch Google Summer of Code 2026 project, noting that one of its goals, adding a Valhalla-powered routing endpoint that genuinely avoids closed roads, has now been completed.

Programming

• Marcos Dione has developed a map showing the sizes of city blocks in Marseille by processing the street network data from OpenStreetMap.
• The Austrian-German OSM tile hoster Maptoolkit has launched a free vector tile server that permits commercial use. The cartography features rather opinionated cartography, with a focus on tourism and outdoor, including outdoor-specific styles (Hiking, Cycling, Winter), global hill-shading, contour lines, water depths, 3D terrain, and a maximum data zoom of 15 globally. It is hosted in the EU and privacy-friendly: No API key, login, or cookies. Fully compliant with the General Data Protection Regulation (GDPR). This service supports custom style sheets, including a new, beginner-friendly map editor at mapmaker.maptoolkit.org. It includes AI-ready documentation. You’ll also find an interesting comparison with OpenFreeMap, Protomaps, Versatiles, and OpenMapTiles on the page.

Releases

• uMap version 3.8.0a4 was released on 18 July 2026.

Did you know that …

• … Observing the City has made ‘Where is Downtown’? This is a web app that lets users draw what they consider to be the ‘downtown’ of a given city and compares their definition with everyone else’s.

OSM in the media

• The online magazine Konvert featured articles on volunteer projects such as Wikipedia, OpenStreetMap, iNaturalist, Project Gutenberg, and Stack Overflow, and spoke ♦►♦ to some of the participants of these projects.

Other “geo” things

• clement_igonet revealed on OSM US’s Slack that he had built a small MapLibre application that shows a time-slider over European administrative boundaries, where the polygons come from an API that models them with valid periods (from sources as INSEE COG, IGN Admin Express and Eurostat GISCO, all open data, no OSM data involved for now). The demo is available. You can watch a short video. The API in the background is api.confinia.io and the source is available on GitHub.
• The NOAA Office for Coastal Management runs four major programmes, one of which is the Digital Coast. In this context, the Sea Level Calculator has been launched, which estimates scenarios for changes in mean sea level, showing the sections of the coastline that would be affected (in monitoring regions). To assist researchers and other users, a series of short videos has been made available.
• HeiGIT has launched a new newsletter, Point of Interest. The first issue focuses on the latest evolution of openrouteservice, its newest developments for humanitarian (and other) uses, and where HeiGIT is heading next.

Upcoming Events Country Where Venue What When MapCup Asia Pacific 2026 ♦ 2026-07-01 – 2026-07-31 ♦ Hotel Sadanand, Crawford Market OSM Mumbai Mapping Party No.12 (Masjid Bunder) ♦ 2026-07-26 ♦ Online Racha Mapping Party ♦ 2026-07-27 – 2026-08-02 ♦ Braunschweig Stratum 0 Braunschweiger Mappertreffen im Stratum 0 Hackerspace ♦ 2026-07-28 ♦ Kiel Mango’s, Kiel Kieler Mapper*innentreffen ♦ 2026-07-28 ♦ Berlin Online OSM-Verkehrswende #77 ♦ 2026-07-28 ♦ Mannheim RaumZeitLabor, Mannheim Rhein-Neckar OSM Treffen ♦ 2026-07-29 ♦ Düsseldorf Online bei meet.jit.si/OSM-DUS-2026 Düsseldorfer OpenStreetMap-Treffen (online) ♦ 2026-07-29 UN Mappers Community Discussion: Community Chapters Initiative ♦ 2026-07-31 ♦ Hannover Endhaltestelle Roderbruch der Stadtbahnlinie 4 Mapping Party ♦ 2026-07-31 ♦ Thiruvananthapuram Kazhakoottam Market bus stop Mapping Party at Kazhakoottam ♦ 2026-08-01 ♦ Uppsala Datorföreningen Update Kartträff i Uppsala. Tema Cykelinfrastruktur ♦ 2026-08-02 ♦ Salzburg Bewohnerservice Elisabeth-Vorstadt OSM-Treffpunkt ♦ 2026-08-04 Missing Maps London Mapathon (with Training) Beginner Friendly (Online) [eng] ♦ 2026-08-04 iD Community Chat ♦ 2026-08-05 ♦ Stuttgart Biergarten Tschechen & Söhne Stuttgarter OpenStreetMap-Treffen ♦ 2026-08-05 ♦ Angers L’Arrière Train, 3 rue de Frémur, Angers Angers Rencontre mensuelle OpenStreetMap ♦ 2026-08-06 ♦ Bar Le Schmilblik Rencontre mensuelle des contributeurs Paris sud ♦ 2026-08-06 ♦ København Cafe Bevar’s OSMmapperCPH ♦ 2026-08-09 ♦ New Delhi North Delhi OSM Delhi Mapping Party No.31 (North Zone) ♦ 2026-08-09 ♦ 臺北市 MozSpace Taipei OpenStreetMap x Wikidata Taipei #91 ♦ 2026-08-10

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 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.

5 days ago

Seit ein paar Wochen versuche ich, möglichst viele offene OSM-Notes um Dingolfing abzuarbeiten. Es macht mir echt Spaß. In meiner Freizeit mache ich seit letztem eigentlich nur zwei Sachen: mappen und Survey machen.

Wo ich angefangen habe, war in Dingolfing fast alles rot (von den Notes her). Jetzt ist die Hälfte (oder vielleicht sogar mehr als das) grün.

Mein Ziel danach ist es, einige Osmose-Fehler zu beheben und dann den ganzen Prozess bei Landshut zu wiederholen.

6 days ago

Ho pubblicato su uMap una mappa interattiva che raccoglie i punti vendita delle principali catene di fast food presenti in Italia.

Al momento la mappa include:

• McDonald’s
• KFC
• Burger King
• Starbucks
• La Piadineria
• Roadhouse
• Alice Pizza
• Billy Tacos
• Old Wild West
• Five Guys

Tutti i dati sono stati raccolti direttamente dai siti ufficiali delle rispettive catene, con l’obiettivo di offrire una panoramica il più possibile completa e aggiornata della loro distribuzione sul territorio italiano.

Link alla mappa: umap.openstreetmap.fr/it/map/fast-food-chains-in-italy_1437687

7 days ago

According to the Alaska Department of Fish and Game, there are over three million lakes in Alaska with a surface area larger than five acres!

Currently, in OpenStreetMap, there are roughly two hundred and forty two thousand elements in Alaska tagged with natural=water, which is a generic tag for an area filled with water.

So, I have decided to embark on mapping natural areas filled with water!

I use the USGS elevation data for alignment, as it seems to have the best alignment to where things actually are on the ground. The USGS imagery is sometimes aligned with the elevation data, but sometimes is not, so the Mapbox and ESRI Clarity imagery is instrumental in areas where it is more accurate to the elevation data.

The National Map Topographic is extremely useful for some lakes, for those where it matches the elevation data well. Often though, it does not match the elevation data.

I posted about this in the OpenStreetMap Slack, and have received help from Watmildon, who has been very kind and extremely helpful! He is helping with the technical aspects of this, and has brought the 3DHP program to my attention, a hydrology program from USGS that is based on elevation data and thus much more accurate than the older NHP data. He is helping to setup a website where one can view the differences between OpenStreetMap, NHP, and the 3DHP, and eventually I hope to be able to overlay the 3DHP data onto an OpenStreetMap editor so I can use it to assist the mapping.

Thanks for reading and happy mapping!

Sources:

www.adfg.alaska.gov/index.cfm?adfg=rivers.main

taginfo.geofabrik.de/north-america:us:alaska/search?q=natural%3Dwater

www.usgs.gov/3dhp

a day ago

Test

a day ago

Bonjour, Je travaille à l’exploitation des routes départementales au Conseil Départemental des Côtes d’Armor. Afin de mener à bien nos missions, nous utilisons des application informatique dont la carto est basée sur OSM. Nous constatons de nombreuses erreur d’affectation de route. En effet de nombreux déclassement de route de route départementale vers route communale n’apparaissent pas. Nos données carto sont en open data et utilisés par l’iGN qui met donc ses cartes à jour régulièrement. Comment faire pour les cartes OSM soient le plus à jour possible. Merci

3 days ago

One day, in a certain neighborhood, there was a heated discussion about naming an unnamed road.

At first, the discussion was about deciding what name they should choose for the road.

But can you guess the final consensus of that discussion?

They preferred not to be mapped.

The status quo was good enough, they said. The road looked like a maze, with little or no clue on how to properly navigate it. They argued that if they named the unnamed road, it would give “outsiders” a clue on how to navigate it, which was “bad” for the internal security of the people who lived there.

This made me think about the ethical grounds of conducting large-scale mapathon campaigns remotely.

We generally work under the assumption that “the more mapped places, the better.” But what if the locals don’t consent to being mapped?

What if they prefer not to be mapped?

3 days ago

Pola Keyword SEO Spam Judi Online di Indonesia

Hasil pengamatan menunjukkan bahwa changeset SEO spam judi online di OpenStreetMap memiliki pola yang relatif konsisten. Brand umumnya menggunakan akhiran “88”, sedangkan komentar changeset berisi kumpulan kata kunci promosi yang diulang untuk kepentingan optimasi mesin pencari (SEO), bukan untuk mendeskripsikan perubahan data OpenStreetMap.

Observations indicate that SEO spam changesets related to online gambling in OpenStreetMap follow a relatively consistent pattern. Brand names commonly use the “88” suffix, while changeset comments consist of collections of promotional keywords repeated for search engine optimization (SEO) purposes rather than describing the actual OpenStreetMap data edits.

Keywords are ordered by descending frequency

Very High / Dominant Frequency

–88 (brand suffix)
slot
gacor
judi
casino
terpercaya
terbaik

High Frequency

login
daftar
link alternatif
RTP
maxwin
jackpot
bonus
deposit
withdraw
mahjong
zeus
Pragmatic Play
PG Soft
togel
toto
–77 (suffix)
–99 (suffix)
–138 (suffix)
–168 (suffix)
–188 (suffix)
–303 (suffix)
–777 (suffix)

Moderate Frequency

pola
cashback
free spin
scatter
wild
multiplier
cuan
menang
sabung ayam
SV388
poker
domino
QQ
Habanero
Joker
Spadegaming
Microgaming
Playtech

Unique Study: Trojan Horse Spam

Pada teknik ini, komentar changeset tampak sepenuhnya normal dan tidak mengandung kata kunci yang berkaitan dengan perjudian. Sebaliknya, konten spam disembunyikan di dalam tag objek OSM, sehingga deteksi yang hanya mengandalkan kata kunci pada komentar changeset menjadi kurang efektif.

In this technique, the changeset comment appears completely legitimate and contains no gambling-related keywords. Instead, the spam is concealed within the OSM object’s tags, making keyword-based changeset detection less effective.

Contoh / Example:

Changeset Comment Created a restaurant Tags addr:city=Medan, addr:housename=TOKO CUAN****88, addr:housenumber=28, addr:postcode=20112, addr:province=Sumatera Utara, addr:street=Jalan Candi Borobudur, amenity=restaurant, building=yes, contact:instagram=heylink.me/cuan****88top/, cuisine=coffee_shop, diet:halal=yes, name=TOKO CUAN****88, opening_hours=sunrise-sunset, website=cuan****88.top Modus Operandi Analysis

1. Komentar Changeset Bersifat Umum: Komentar changeset menggunakan deskripsi yang sederhana dan umum (misalnya, “Added cafe”), sehingga edit tersebut tampak seperti perubahan rutin tanpa memunculkan indikasi yang berkaitan dengan perjudian.

2. POI Tampak Sah: Objek OSM diisi dengan tag-tag yang lazim digunakan pada tempat usaha, seperti alamat lengkap, amenity, dan jam operasional, sehingga menyerupai bisnis lokal yang valid.

3. Brand Disisipkan pada Tag Objek: Alih-alih menempatkan konten promosi pada komentar changeset, pelaku menyisipkan nama brand judi ke dalam tag seperti name dan addr:housename, serta menambahkan tautan eksternal melalui website dan contact:instagram.

4. Sulit Dideteksi: Karena komentar changeset tidak mengandung kata kunci yang mencurigakan, mekanisme deteksi yang hanya mengandalkan analisis komentar kemungkinan tidak akan menandai edit tersebut. Indikasi spam baru terlihat setelah dilakukan pemeriksaan terhadap tag objek dan tautan eksternal yang terkait dengan POI.

1. Generic Changeset Comment: The changeset comment uses a simple, ordinary description (e.g., “Added cafe”), making the edit appear routine and avoiding any obvious gambling-related terms.

2. Legitimate-looking POI: The object is populated with common business tags, including a complete address, amenity, and opening hours, so it blends in with genuine local businesses.

3. Brand Embedded in Object Tags: Instead of placing promotional content in the changeset comment, the spammer inserts the gambling brand into tags such as name and addr:housename, while adding external links through website and contact:instagram.

4. Difficult to Detect: With no suspicious keywords in the changeset comment, comment-based filters are unlikely to flag the edit. The spam only becomes apparent after examining the object tags and the external links associated with the POI.

3 days ago

♦

Note that this is an update of a previous diary entry. This version uses updated Overpass software from a fork.

Many people have noticed that publicly available Overpass servers have been suffering from overuse (a typical “tragedy of the commons”). OSM usage policies generally contain the line “OpenStreetMap (OSM) data is free for everyone to use. Our tile servers are not”. Unfortunately, there have been problems with overuse of the public Overpass servers, despite the usage policy. “Just blocking cloud providers” isn’t an option, because (see here - use the translate button below) lots of different sorts of IP addresses, including residential proxy addresses, are the problem.

People who want to use e.g. Overpass Turbo do have the option to point it at a different Overpass API instance. If you’re using Overpass Turbo and you get an error due to unavailability, likely that is because the Overpass API that it is using is overwhelmed. There are other public Overpass API instances, but they may be complete (in terms of geography, or history) or up to date.

At this point, if you’re one of the people who created the problem you’ll likely just spin up more instances to retry after timeouts and make the problem worse. Most people reading this are I hope not in that category. There are commercial Overpass API providers - more details for the example in that table can be found here.

Other people (including me) might wonder whether it’s possible (without too much work) to set up an Overpass API server that just covers one or two countries. To keep it simple, let’s restrict myself to Britain and Ireland 2.3GB in OSM, and let’s not worry about Attic Data (used for “queries about what was in OSM in the past”) or metadata.

Let’s just try and do regular Overpass queries such as you might start from this taginfo page, like this. I’ll also only target the Overpass API, and will use “settings” in an Overpass Turbo instance to point to my Overpass API server. I do want to apply updates as OSM data is changed.

I’m interested in creating a server covering the UK and Ireland. In terms of size, have a look at how much bigger or smaller your area of interest is than the 2.3GB of Britain and Ireland below and use that to judge what size server you might need.

Documentation

At this point it’s perhaps worth mentioning that the documentation around Overpass has historically been … (and I’m channelling my inner Sir Humphrey here) “challenging”.

There’s the OSM wiki which talks about “Debian 6.0 (squeeze) or Debian 7.0 (wheezy)”, the latter of which went EOL in May 2018. There is also an HTML file on overpass-api.de. That is … (engages Sir Humphrey mode again) not entirely accurate, in that it says to run something that doesn’t exist if you’ve cloned the github repository.

One of the best documents by far is external and is by ZeLonewolf, which starts off by saying “I found the existing guides to be lacking”. It then says “This is a combination of various other guides, the official docs, Kai Johnson’s diary entry…” (which is the other “best document”) “… and suggestions from @mmd on Slack. This guide is intended to demonstrate how to configure a server dedicated to only running overpass”. Kai’s diary entry from 2023 is definitely worth reading (sample quote there “Running an Overpass server is not for the faint of heart. The software is really finicky and not easy to maintain. You need to have some good experience with Linux system administration and the will and patience to deal with things that don’t work the way they’re supposed to”).

Also, this github issue (and things linked from it) summarises some of the issues that I had on the way to getting my test servers set up.

Since Kai’s diary entry in 2023 his instructions have grown into a full followable README in github; I’ll link to that below.

Where what I’m doing below differs from what the other guides say I’ll try and say why I am doing it differently. Usually it’s because my requirements are different (e.g. an overpass server for a small area rather than everywhere, on a VSP rather than a piece of tin or a Docker container, or because I need limited functionality).

Server

For my use case, we’ll need a server that is publicly accessible on the internet to do this. I’m already a customer of Hetzner, so initially I created a test server there. Other providers are available, and may make more sense depending where you are in the world and how much you want to pay. For testing, spinning up something at one of the hyperscalers might make financial sense, but I suspect not long-term. I went with a CX43 with 160GB of SSD disk space, 16GB RAM and a rather large amount of bandwidth. This turned out to be about the right size for Britain and Ireland. I went with Debian 13 and public ipv4 and ipv6 addresses. I don’t know if Overpass releases need a particular architecture, but went with “x86” rather than “ARM” just in case. I actually moved to a different VM configuration, but these instructions have been tested and do work.

If you’re needs are different you don’t have to use a cloud server for this. and Kai’s diary entry has a lot of information about physical server sourcing and setup.

Sizing was alas largely guesswork and trial and error - while I’m sure that the commercial providers know chapter and verse on this, there isn’t a lot written down about “sizing based on extract size” that isn’t “how long is a piece of string”. I found that loading even North Yorkshire (just 56MB in OSM) created a nodes file in the database area of 23GB, so that sets the minimum server size, even for very small test extracts.

The speed of the disk used needs to be able to apply updates in less time than the updates are of. If it takes 2 hours to apply 1 hour of updates, your server will never catch up. In practice I didn’t find this to be an issue with the servers at Hetzer and the relatively small extracts (updated daily) that I was working with.

Initial server setup

In what follows I’ll use youruseraccount, yourserver and yourdomain in place of the actual values I used.

I already have some ssh keys stored at Hetzner, so when buying the server, I chose a new name in the format “yourserver.yourdomain” and added my ssh keys. I have yourdomain registered at a DNS provider, and I added the IPV4 and IPV6 addresses there. I can now ssh in as root to “yourserver.yourdomain”, and run the usual:

ssl -l root yourserver.yourdomain
apt update
apt upgrade

and bounce the server and log back in again.

The next job is to create a non-root account for regular use and add it to the “sudo” group:

useradd -m  youruseraccount
usermod -aG sudo youruseraccount
chsh -s /bin/bash youruseraccount

I’ll create a new password in my password manager for youruseraccount on this server (obviously I used my account name rather than actually youruseraccount, but you get the idea…). Next, set the new account password to the newly chosen password

passwd youruseraccount

and check I can login to the new server as youruseraccount with that password, and become root:

ssh -l youruseraccount yourserver.yourdomain
sudo -i 
exit

Install some initial software:

sudo apt install emacs-nox screen git tar unzip wget bzip2 net-tools curl apache2 wget g++ make expat libexpat1-dev zlib1g-dev libtool autoconf automake locate osmium-tool

That list includes both software prerequisites (apache2) and things that will be really useful (screen). It also includes emacs as a text editor; you can use your preferred one instead wherever emacs is mentioned below.

To use screen you just type screen and then press return. You can manually detach from it by using ^a^d and later reattach by using “screen -r”. If there are multiple screens you can attach to you’ll see something like this:

There are several suitable screens on:
    95207.pts-2.h23 (02/15/2026 09:20:20 AM)        (Detached)
    95200.pts-2.h23 (02/15/2026 09:19:57 AM)        (Detached)
    1633.pts-2.h23  (02/14/2026 12:37:50 PM)        (Attached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and you can choose which one to reconnect to by typing in (say) “95207” and pressing “tab”. To force a reconnection to a screen that something else is attached to, use “screen -d -r”.

In many cases below I’ll say “(in screen)” - this just means it’s a good idea to run these commands from somewhere that you can detach from and reattach to. It doesn’t mean you need to create a new screen every time.

The ssh keys that I had stored have been added for root by Hetzner, but I also want to add them to my new account too:

sudo -i
sudo -u youruseraccount -i
ssh-keygen -t rsa
(either use existing password for ssh passphrase, or create and store a new one)
exit

cp /root/.ssh/authorized_keys /home/youruseraccount/.ssh/
emacs /home/youruseraccount/.ssh

… and in there change the ownership of the files to youruseraccount.

Next, check that you can ssh in to yourserver.yourdomain without a password. Next disable regular password access. We don’t want people to be able to brute force password access to a server on the internet, so we can just turn this off.

sudo emacs /etc/ssh/sshd_config

Find the line that says

# To disable tunneled clear text passwords, change to "no" here!

and uncomment and change the next two lines to say

PasswordAuthentication no
PermitEmptyPasswords no

save the file and then

sudo /etc/init.d/ssh restart

and then try and login (from the shell on that machine will work as a test)

ssh 127.0.0.1

It should say Permission denied (publickey).

Setting up a certificate is the next priority. Everything on the internet these days pretty much assumes https access, so let’s do that before even thinking about overpass. I’ll use acme.sh for that. Other providers and tooling are available and you can use them if you prefer. Login as your non-root account and then:

sudo -i
cd
wget -O -  get.acme.sh | sh -s email=youremailaddress
exit
sudo -i
/etc/init.d/apache2 stop
acme.sh --standalone --issue -d yourserver.yourdomain -w /home/www/html  --server letsencrypt

the last lines of the output you get should be like

-----END CERTIFICATE-----
[Sat Feb 14 12:51:45 AM UTC 2026] Your cert is in: /root/.acme.sh/yourserver.yourdomain_ecc/yourserver.yourdomain.cer
[Sat Feb 14 12:51:45 AM UTC 2026] Your cert key is in: /root/.acme.sh/yourserver.yourdomain_ecc/yourserver.yourdomain.key
[Sat Feb 14 12:51:45 AM UTC 2026] The intermediate CA cert is in: /root/.acme.sh/yourserver.yourdomain_ecc/ca.cer
[Sat Feb 14 12:51:45 AM UTC 2026] And the full-chain cert is in: /root/.acme.sh/yourserver.yourdomain_ecc/fullchain.cer

Next do

sudo a2ensite default-ssl
sudo a2enmod ssl
sudo systemctl reload apache2

and then edit the default site config

sudo emacs /etc/apache2/sites-enabled/default-ssl.conf

Replace the SSL references with the correct ones.

SSLCertificateFile      /root/.acme.sh/yourserver.yourdomain_ecc/fullchain.cer
SSLCertificateKeyFile   /root/.acme.sh/yourserver.yourdomain_ecc/yourserver.yourdomain.key

Restart apache

sudo systemctl restart apache2

and browse to yourserver.yourdomain to make sure that the certificate is working. You’ll need to arrange for that certificate to be renewed every couple of months, but let’s concentrate on overpass for now.

That is it for the initial server setup, so now would be a good time for a server snapshot or other sort of backup.

Which Overpass software to install

It’s confusing, but there are several forks of Overpass. The original one (I think) is here; last updated 2 years ago. There’s also this one, also last updated 2 years ago - see here for positive comments about the speed of meta queries vs the original. There is also this, last updated at the time of writing last week. The main branch there has numerous enhancements, including .pbf support; we’ll use that.

The Readme is excellent and contains much more information than this summary diary entry.

Setting up the user for Overpass

For this part, we’re going to follow parts of ZeLoneWolf’s guide. I’ve reproduced that mostly as written below, although some of the software already was installed earlier.

sudo su

mkdir -p /opt/op
groupadd op
usermod -a -G op youruseraccount
useradd -d /opt/op -g op -G sudo -m -s /bin/bash op
chown -R op:op /opt/op
apt-get update
apt-get install g++ make expat libexpat1-dev zlib1g-dev apache2 liblz4-dev curl git
a2enmod cgid
a2enmod ext_filter
a2enmod headers

exit

The username that we created above is “op”. We won’t use a password for that but will just use

sudo -u op -i

when we need to change to it from our normal user account.

Configuring Apache

We already have Apache set up with a default HTTPS website that says “It works!”. We’ll use some of what’s in ZeLoneWolf’s Guide but we DON’T want to completely replace our config with that one. Instead we’ll selectively copy in some sections. Edit the file as is:

sudo emacs /etc/apache2/sites-available/default-ssl.conf

Note that we are using https with the defaults and the filename is different to the example.

Find this line:

DocumentRoot /var/www/html

and after it insert this section:

# Overpass API (CGI backend)                                                                          
ScriptAlias /api/ /opt/op/cgi-bin/

<Directory "/opt/op/cgi-bin/">
        AllowOverride None
        Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
        Require all granted

        # CORS for Overpass Turbo                                                                     
        Header always set Access-Control-Allow-Origin "*"
        Header always set Access-Control-Allow-Methods "GET, POST, OPTIONS"
        Header always set Access-Control-Allow-Headers "Content-Type"
</Directory>

# Compression (for API responses)                                                                     
ExtFilterDefine gzip mode=output cmd=/bin/gzip

# Logging                                                                                             
ErrorLog /var/log/apache2/error.log
LogLevel warn
CustomLog /var/log/apache2/access.log combined

# Long-running Overpass queries                                                                       
TimeOut 300

I then deleted a bunch of lines, all comments of functional duplicates of what we had just added, down to but not including:

#   SSL Engine Switch:                                                                                

Save and restart apache:

sudo /etc/init.d/apache2 restart

and check that you can still browse to “yourserver.yourdomain”. It won’t look any different as the default website has not been changed; we’ll test the “cgi-bin” parts later.

Compile and Install Overpass

As our local user:

mkdir ~/src
cd ~/src
git clone github.com/b1tw153/Overpass-API
cd Overpass-API
git branch

Note that main (the updated version) is the default branch

cd ~/src/Overpass-API/src/
autoreconf -i
./configure CXXFLAGS="-O2" --prefix=/opt/op --enable-lz4

The next bit might take a while, so you might want to run it from within screen in case of disconnection:

time sudo make install

(that’ll take a few minutes)

sudo -u op -i
mkdir db
mkdir diff
exit
sudo cp -pr ~/src/Overpass-API/src/rules/ /opt/op/db/

Those two directories above created are for the database and minutely diff files. Logfiles are written to the user directory or in the database directory with this version. In operation, the biggest by far will be “db” - we’ll expect 2.3GB of .pbf extract to create a database of initially 20GB or so. We’ll talk more about this later.

Loading OSM Data

In the fork of Overpass that we are using, this process for initialising the Database from an extract is documented here. See also Initialize the Database from a Clone and Initialize the Database from a Planet File for other options.

Based on the example script there, we’ll load the initial data like this, from the “op” user:

EXTRACT_FILE_URL=download.geofabrik.de/europe/britain-and-ireland-latest.osm.pbf   # URL of the extract file to import                                                                                               
OVERPASS_DIFF_URL=download.geofabrik.de/europe/britain-and-ireland-updates/        # URL of the chosen replication source associated with the extract file                                                                 
OVERPASS_BIN_DIR=/opt/op/bin/                                                              # path to the bin directory in your Overpass installation                      
OVERPASS_DB_DIR=/opt/op/db/                                                                # path to your Overpass database directory                                      
OVERPASS_DIFF_DIR=/opt/op/diff/                                                            # path to the directory that will be used to store diff files                 
OVERPASS_META_MODE=no # yes|no|attic - include meta data, base data only, or attic data                        
nohup "$OVERPASS_BIN_DIR/import_osm_data.sh" \
  --db-dir="$OVERPASS_DB_DIR" \
  --diff-dir="$OVERPASS_DIFF_DIR" \
  --diff-url="$OVERPASS_DIFF_URL" \
  --data-source="$EXTRACT_FILE_URL" \
  --meta="$OVERPASS_META_MODE" &

I created an example shell script in /opt/op/bin/ to do this in case it needs to be run more than once. When run, it writes all output to nohup.out; in order to see the current progress you can run:

tail -f nohup.out

On a test server with fast SSD disk the process took a couple of hours or so for me; at the end you should see lines something like:

compute_geometry: Node 13537323062 used in relation 20194148 not found.
Flushing to database ....... done.
Update complete.
2026-07-23 21:22:09: Database import complete
2026-07-23 21:22:09: Finding replicate_id for download.geofabrik.de/europe/britain-and-ireland-updates/ ...
WARNING: Failed to download download.geofabrik.de/europe/britain-and-ireland-updates/000/002/428.state.txt
WARNING: Failed to download download.geofabrik.de/europe/britain-and-ireland-updates/000/003/641.state.txt
WARNING: Failed to download download.geofabrik.de/europe/britain-and-ireland-updates/000/004/248.state.txt
WARNING: Failed to download download.geofabrik.de/europe/britain-and-ireland-updates/000/004/551.state.txt
WARNING: Failed to download download.geofabrik.de/europe/britain-and-ireland-updates/000/004/703.state.txt
2026-07-23 21:22:11: REPLICATE_ID=4854
2026-07-23 21:22:11: Database ready

Those warnings at data load don’t indicate an actual problem. There will always be “X used in Y not found” messages when loading extracts, and the first state file on Geofabrik’s server is currently actually 727; I’ve no idea why the software tries to download earlier versions here.

Note that with this version of Overpass we didn’t need to download a .pbf file and convert it into .bz2 format - we just loaded the .pbf directly. We also didn’t need to manually edit several of the scripts needed to run overpass since those parameters were set by the load script above and/or will be set by the start script we’ll come to in the next section.

Also note that on slow disk this process will take MUCH longer - perhaps unfeasibly so.

After an initial data load of Britain and Ireland, the “db” directory was 16GB in size. That’s with compression, and is a factor of 3 or 4 better than without compression. It’s still much bigger than the initial .pbf, which was 2.4GB.

It is a good idea to do some sort of snapshot or backup at this stage.

log file management

There’s a section in ZeLoneWolf’s guide that covers this.

This version of Overpass doesn’t have an explicit log directory; logs are written to nohup.out or in the database directory. These will eventually grow large and will eventually need a log rotation mechanism to be set up, but let’s gloss over that for now and see Overpass actually running first! For more on logfiles, read the Readme here,

Maintenance

I have deliberately not set this up yet as I don’t want to automatically do anything at e.g. reboot; rather I’d like to control it manually so that I can watch that it does what it is supposed to. This section of the readme has more details.

Start overpass

If this isn’t the first time you’ve started overpass you may want to take a backup copy of the previous “diff” directory.

In the fork of Overpass that we are using, this process for running Overpass is documented here.

Based on the example script there, we’ll run overpass like this from the “op” user:

OVERPASS_BIN_DIR=/opt/op/bin/                                                                      # path to the bin directory in your Overpass installation
export OVERPASS_REPLICATE_ID=auto                                                                  # use the replicate_id file from the database directory
export OVERPASS_DB_DIR=/opt/op/db/                                                                 # path to your Overpass database directory
export OVERPASS_DIFF_DIR=/opt/op/diff/                                                             # path to the directory that will be used to store diff files
export OVERPASS_DIFF_URL=download.geofabrik.de/europe/britain-and-ireland-updates/         # URL of the replication source that matches the database
export OVERPASS_UPDATE_FREQUENCY=86357                                                             # update interval in seconds (should match replication source)
export OVERPASS_META_MODE=no                                                                       # yes|no|attic - include meta data, base data only, or attic data (should match existing database or import)
export OVERPASS_AREAS=yes                                                                          # yes|no - create or skip derived area data
nohup "$OVERPASS_BIN_DIR/run_osm3s.sh" &

I created an example shell script in /opt/op/bin/ to do this in case it needs to be run more than once. When run, it writes all output to nohup.out; in order to see the current progress you can run:

tail -f nohup.out

When started, in there you should see lines something like:

tail nohup.out 
2026-07-27 21:50:33: Started areas dispatcher  (PID 1218)
2026-07-27 21:50:33: Starting apply_osc_to_db.sh
2026-07-27 21:50:34: Started apply_osc_to_db.sh (PID 1224)
2026-07-27 21:50:34: Starting fetch_osc.sh
2026-07-27 21:50:35: Started fetch_osc.sh (PID 1270)
2026-07-27 21:50:35: Starting rules_loop.sh
2026-07-27 21:50:36: Started rules_loop.sh (PID 1333)
2026-07-27 21:50:36: Skipping backup.sh startup (set OVERPASS_BACKUP_* environment variables to enable backup)
2026-07-27 21:50:36: Checking startup ...
2026-07-27 21:50:36: Startup complete

In the directories below “diff”, you should see that it has downloaded daily diffs for any days since your extract, for example:

ls -alt diff/000/004/
total 6452
drwxrwxr-x 2 op op    4096 Jul 27 22:50 .
-rw-rw-r-- 1 op op 3561802 Jul 27 22:50 859.osc.gz
-rw-rw-r-- 1 op op     113 Jul 27 22:50 859.state.txt
-rw-rw-r-- 1 op op 2996912 Jul 27 22:50 858.osc.gz
-rw-rw-r-- 1 op op     113 Jul 27 21:52 858.state.txt
-rw-rw-r-- 1 op op     113 Jul 27 21:52 857.state.txt
-rw-rw-r-- 1 op op     113 Jul 27 21:52 856.state.txt
-rw-rw-r-- 1 op op     113 Jul 27 21:52 854.state.txt
-rw-rw-r-- 1 op op     113 Jul 27 21:52 849.state.txt
-rw-rw-r-- 1 op op     113 Jul 27 21:52 840.state.txt
-rw-rw-r-- 1 op op     113 Jul 27 21:52 821.state.txt
-rw-rw-r-- 1 op op     113 Jul 27 21:52 783.state.txt
drwxrwxr-x 5 op op    4096 Jul 27 21:52 ..

Testing standalone

At the command line type:

bin/osm3s_query

Paste in this:

<query type="nwr"><bbox-query n="51.96" s="51.86" w="-3.31" e="-3.22"/><has-kv k="amenity" v="pub"/></query><print/>

Press return. Press ^d. A selection of data will be returned.

Testing from Overpass Turbo

In a web browser, browse to overpass-turbo.eu/s/2kEW .

Click “settings”. Change “server” from “overpass-api.de/api/” to “yourserver.yourdomain/api/”. Click “run”. You should not get an error, and should get a couple of nodes and 4 ways returned. At the top right of the Overpass Turbo window you can click “Map” and “Data”. Among the things that “Data” shows are the “Overpass API” version (at the time of writing “0.7.62.11 87bfad18”) and the “timestamp_osm_base”. With an extract downloaded from Geofabrik, that will always be “around 8pm yesterday”. The new update appears in the early hours of the morning, based on the previous day’s updates to 8pm. If the data is more than a day old the results at the bottom right of the “map” screen show in yellow, not white.

For the avoidance of doubt - if you browse to “yourserver.yourdomain/” you’ll get some sort of “It works!” page. If you browse to “yourserver.yourdomain/api/” you’ll actually get an error - it’s designed to be accessed (see the CORS settings above) by Overpass Turbo, not a regular browser.

It’s also worth testing that the area generation has worked. This is done automatically behind the scenes by the new Overpass scripts; it’ll take a little while to complete. A simple example of an area query is here.

Shutting down Overpass

The maintenance section above also mentions it, but for completeness you shut down this version of overpass by sending a regular SIGTERM to the run_osm3s.sh process.

$ ps -ef | grep osm3s
op          1145       1  0 22:50 ?        00:00:00 bash /opt/op/bin//run_osm3s.sh
op          1668    1657  0 23:17 pts/1    00:00:00 grep osm3s
$ 
$ kill 1145
$ 
$ ps -ef | grep osm3s
op          1712    1657  0 23:17 pts/1    00:00:00 grep osm3s
$ 

This will leave behind some sleeping processes:

$ ps -ef | grep sleep
op          1362       1  0 22:50 ?        00:00:00 sleep 86400
op          1430       1  0 22:50 ?        00:00:00 sleep 2444
op          1643       1  0 23:08 ?        00:00:00 sleep 81726
op          1648       1  0 23:08 ?        00:00:00 sleep 85305
op          1717    1657  0 23:18 pts/1    00:00:00 grep sleep
$ 

It won’t cause any problems to leave them, but you could also send a regular “kill” signal to each of those just to tidy up.

Now what?

Shutting everything down and taking a snapshot of the server is a good idea at this point. The long-term cost of snapshots is small (€0.20 per month or so). The cost of leaving a server of this specification running 24x7 isn’t that large - around €10, perhaps a couple of beers or a couple of fancy coffees.

You might also want to think about setting up an Overpass server that does include metadata and attic data - but you’re probably better off with a dedicated server for that, and better off following one of the other guides linked above.

3 days ago

Привет! Я несколько лет делаю сервис, который выгружает данные OSM в форматы, живущие за пределами ГИС-мира: CorelDRAW (CDR), AutoCAD (DWG/DXF), SVG для иллюстраторов, STL для 3D-печати. Оказалось, самая благодарная аудитория данных OSM — вовсе не картографы: это дизайнеры вывесок, которым нужна карта района в кривых; проектировщики, которым нужна подложка в DWG; мастера лазерной гравировки, режущие карты городов по DXF.

Главная боль, которую пришлось решать, — сохранить СЛОИ: чтобы дороги, здания и вода приезжали в CorelDRAW отдельными редактируемыми слоями, а не одной свалкой кривых.

Устроено это так: каждый экспорт собирается из тех же тематических групп, которыми думает сам OSM, — дороги, здания, вода, растительность, землепользование, точки интереса. Внутри файла каждая группа становится отдельным именованным слоем целевой программы: слой можно скрыть, перекрасить или удалить одним движением, не выбирая объекты поштучно. Подписи улиц тоже живут отдельным слоем — дизайнеру вывески они обычно нужны, мастеру гравировки почти никогда.

Вторая боль — граница. Прямоугольник вокруг города неизбежно захватывает куски соседних районов, и вычищать их вручную мучительно. Поэтому экспорт умеет резаться строго по административной границе: выбираешь город или район из каталога (в нём около 2,9 млн административных единиц по 179 странам) — и все слои аккуратно обрезаются по контуру, а разрезанные полигоны корректно замыкаются на границе.

Сервис: osm2cdr.ru (мир: osm2cdr.com). Данные © участники OpenStreetMap, ODbL — атрибуция вшита в каждый экспорт. Буду рад обратной связи от сообщества: чего не хватает, что сделано не по-OSM-овски?

3 days ago

♦

NEW IBGE CNEFE 2022 TOOL FOR OPENSTREETMAP 🚀

The biggest update to the street name tool has arrived!

The system that verifies street names using CNEFE 2022 data has been completely redesigned based on community feedback! 🔄 WHAT’S CHANGED? TWO-WAY SYNC!

Before: We only corrected OSM based on CNEFE Now: Mutual alignment between both datasets!

✅ If OSM is wrong → Fix it on the map (JOSM/iD) ✅ If CNEFE is outdated → Fix it in the tool

“Paving the way for the future batch import of addresses!”

🎯 UNMISSABLE NEW FEATURES

🔐 OSM Login - Authentication required (goodbye bots!) 📦 Batch Editing - Resolve multiple streets at once (use with caution!) 🔗 Overpass-Turbo Integration - Quickly check sources in OSM 📋 Auto-Copy - Corrected name is ready to paste (Ctrl+V)! 🏷 Street vs. Place Switcher - For squares, villages, and special cases 📊 Collaboration History - See who has helped in your area

📈 Filters and Statistics - Track your progress! 👇 NEW DASHBOARD STEP-BY-STEP

1. Read the street name from CNEFE (already corrected via dictionary)
2. Open in iD or JOSM and edit the geometry
3. Type the EXACT name used in the OSM name= tag
4. Click “Save Check” and you’re done!

⚠️ ATTENTION: Uppercase ≠ Lowercase | Accents matter! 🤔 WHO IS THIS FOR?

✅ Beginners who don’t edit OSM directly ✅ Experienced JOSM mappers ✅ EVERYONE who wants to contribute accurate addresses! 📚 RESOURCES FOR YOU

📖 Comprehensive Manual:

cnefe.mapaslivre.com.br/tutoriais/pdf/logradouros_manual.pdf

🎥 Video Tutorial: youtu.be/8LFIy04d78k

💬 Telegram Group: t.me/grupoumbraosm

🔗 Access Now: cnefe.mapaslivre.com.br

Let’s build the foundation for the address import together! 🏠📍

OpenStreetMap #CNEFE #IBGE #CollaborativeMapping #OpenData #OSM #Geotechnologies #UrbanMapping #DataImport 4 days ago

RETEX : Questions existentielles sur ma rencontre avec panoramax

à suivre peut-être :

• entrée de journal (à venir) : Cartographier mon village
• entrée de journal (à venir) : Simple model 3D dans OSM

Je rappelle que ces entrées de journal ne sont ni des pages de WIKI, ni des conseils d’expert … . Ce sont juste des comptes-rendus d’expérience vécue ou des questionnements en cours mis ici pour servir à toute personne intéressée.

A l’origine : mon trekking urbain recyclage

(voir entrée de journal trekking urbain)
Lorsqu’il est apparu, en juin 2025, que j’allais passer devant les 1600 (que je pensais alors être 284) points d’apport de mon territoire, un contributeur m’a demandé de penser à tous les photographier et de verser les photos dans Panoramax, ce que j’ai accepté aussitôt.

Et me voilà parti avec mon smartphone à la main pour photographier chaque point d’apport (en fait une photo par conteneur et une photo pour le point d’apport constitué par le groupe de conteneurs). J’ai aussi à l’occasion pris des photos de quelques points notables (notamment des oeuvres de street art croisées au bord des chemins).

Comme je répondais à une demande sans avoir vraiment réfléchi à l’objectif, je ne me suis posé que peu de questions. J’ai rapidement compris qu’il y avait plusieurs instances de Panoramax avec un répertoire commun (références coordonnées entre les instances) et ai choisi l’instance OpenStreetMap simplement parceque je répondais à une demande OSM et visais principalement à mettre l’attribut panoramax=xxxxx sur mes conteneurs.

Rapidement une question : pourquoi ces photos?

Au bout de 800 photos versées (j’ai peut-être l’esprit un peu lent), je me suis interrogé sur l’intérêt de ces versements. J’y voyais deux objectifs possibles :

• mettre à disposition des photos de terrain pour permettre à d’autres contributeurs de cartographier eux-mêmes à partir de ces photos les éléments qui les intéressent, sans nécessirement avoir à se déplacer. Mais cet objectif me paraissait plutôt faible car d’une part le cartographe, c’était moi et d’autre part je pensais avoir tiré des photos toutes les informations pertinentes pour la base OSM. Il faut comprendre qu’il s’agissait de photos plates (pas 360 degrés) centrées et zoomées sur les conteneurs et ne fournissant que très peu d’informations d’environnement utiles pour d’autres sujets. Je me disais que après mon usage, les photos n’avaient que peu d’intérêt pour les autres. Dès lors, pourquoi les publier et ne pas simplement les consulter localement (sur mon PC) pour mes sessions de cartographie
• mettre à disposition des photos pour faire connaître les paysages (cartographions nos territoires, autres usages non pressentis par moi ?, marketing touristique ?). Mais là, je me suis rapidement rendu compte que les photos de points d’apport volontaires n’étaient pas très “marketing” : beaucoup de conteneurs sales, beaucoup de conteneurs débordants, beaucoup d’incivilités de riverains déposant des déchets au sol à côté des conteneurs eux-mêmes, … .

Lorsque j’ai essayé de partager ces interrogations sur le forum, j’ai essentiellement eu comme réponse : “toutes ces raisons sont valables, et tu fais comme tu le sens …”. Je sentais que ce travail était inutile et j’aurais volontiers arrêté si je ne m’étais pas engagé auprès du contributeur initial.

J’ai donc fini mon trekking urbain avec publication dans panoramax de toutes les photos, mais sans grande conviction.

Mais plus tard …

Un peu plus tard, deux événements m’ont considérablement fait changer d’avis :

• un contributeur, sur le forum France, a demandé de l’aide pour configurer le code couleur des points d’apport volontaire de sa commune. Il m’a été facile de l’aider (simple erreur de syntaxe sur son utilisation des codes) mais je me suis alors rendu compte que je ne m’étais jamais soucié de configurer les codes couleur des 1600 points d’apport que j’avais cartographiés. Cela ne m’était tout simplement pas venu à l’esprit. J’ai alors réalisé que si quelqu’un s’intéressait à cet attribut, il pouvait aisément le faire plus tard sur mes 1600 POI simplement en allant analyser les photos Panoramax !
• Quelques semaines plus tard, une étudiante en première année de Master dans le domaine de la Gestion des déchets qui réalise un projet de mémoire sur l’inclusion des personnes en situation de handicap dans le domaine du tri de déchets me contacte pour m’interroger sur l’exploitation qu’elle peut faire des données OSM. Là encore, je réalise que, bien que je me sois efforcé de mettre l’attribut wheelchair sur chacun des conteneurs cartographiés, les photos Panoramax apportent une vision beaucoup plus précise pour cette étudiante.

Donc, ne jamais préjuger des besoins que les autres (contributeurs OSM ou non) auront plus tard ! Et comme les images Panoramax bénéficient d’une licence permettant leur réutilisation la plus large, l’idée de verser à Panoramax les images terrain a repris pour moi tout son sens.

Cartographier ma commune : vers le 360 et le RTK

Après mon trekking urbain recyclage, je me suis intéressé à l’enrichissement de la cartographie de ma commune :

• tous les commerces mis à jour et complétés,
• toutes les chaussées et les sentiers
• tous les trottoirs, avec leur revêtemen, leur largeur, leurs traversées de chaussées
• les équipements urbains (poubelles, hydrants, lampadaires, caméras,etc.)

Premier constat : le besoin d’images 360 degrés

Mon souhait a tout de suite été de partager ce projet avec plusieurs contributeurs opérant dans la zone et, pour ce faire, de verser cette fois des séquences panoramax complètes sur lesquelles chacun pourrait s’appuyer pour cartographier les sujets qui l’intéresse.
Je me suis rapidement rendu compte que les images “plates” (mono directionnelles) étaient peu efficaces dans ce but, voire plutôt frustrantes. Il me semble que l’on a besoin dans ce cas de pouvoir orienter la vue dans toutes les directions pour rechercher les objets visés, pour pouvoir aussi observer un objet sous plusieurs angles … .

J’ai donc choisi de verser des séquences d’images à 360 degrés et ai vraiment apprécié ce mode pour cette utilisation, même si on perd de la précision (usage d’une Gopro Max), ce qui est parfois perturbant pour lire les affichages (horaires de commerçants, par exemple).

Même avec un objectif ciblé (par exemple les conteneurs de points d’apport volontaire), j’ai regretté à postériori de ne pas avoir pris des images 360 qui auraient permis une meilleure appréhension de l’environnement. Par exemple, l’accès PMR à un point d’apport nécessite parfois d’avoir une bonne vision des bords du soubassement supportant les conteneurs.

J’ai même pensé à un moment que les images monodirectionnelles n’avaient pas d’intérêt. Avec un peu de recul toutefois (pas beaucoup, je le reconnais), il me semble qu’il y a plusieurs cas où elles se défendent bien :

• elles sont souvent plus faciles à prendre. En voiture, par exemple, elles ne nécessitent pas d’installation sur le toit. Même à pied, elles sont plus naturelles sans équipement supplémentaire.
• elles sont efficaces dans la cartographie de la signalisation routière : placées dans le sens du déplacement, elles captent la vision de la route qu’a le conducteur. Elles permettent ainsi une bonne vision des panneaux et indications de signalisation routière. En revanche, en mode plus exploratoire (images à pied ou même à vélo), elles me semblent moins appropriées.

Deuxième constat : le RTK (positionnement centimétrique)

Aucun de mes versements en 2025 sur Panoramax d’images de points d’apport volontaire n’a de positionnement centimétrique. Cela ne m’avait pas gêné pour les conteneurs à ordure car je les positionnais dans OSM non pas à partir des géolocalisations des photos, mais plus par rapport aux autres repères de la rue (croisements, marques sur la chaussée visibles sur les images aériennes, visibilité directe du conteneur sur l’imagerie aérienne,…). Comme mon objectif était plutôt d’accéder aux images via le lien panoramax= dans OSM, l’éventuel positionnement approximatif dans Panoramax ne m’avait pas du tout perturbé. Je ne me suis rendu compte que plus tard (par exemple via la simple exploration dans Panoramax) des perturbations que cela pouvait générer. J’ai regretté par la suite de ne pas avoir retouché les positions et axes de ces photos avant leur versement à Panoramax.

En revanche, quand j’ai commencé à envisager de recouvrir ma commune de séquences Panoramax permettant ensuite une cartographie la plus précise possible, je me suis rendu compte que les écarts de 5 mètres étaient très perturbants. Ils permettaient par exemple difficilement d’utiliser des visions croisées. De même, des images géolocalisées à 5m près signifient en général des traces GPX de la même randonnée avec une précision trop faible pour les posionnements de sentiers, voire même de trottoirs.
Lorsque j’ai commencé à regarder ce qui existait déjà sur Panoramax concernant ma commune, j’ai trouvé par exemple au milieu du jardin de la mairie des images prises par la fenêtre d’un train positionnées à 56 m de la voie ferrée ! Donc peu exploitables pour positionner correctement un lampadaire, par exemple.

J’ai donc décidé de positionner les images versées dans Panoramax au centimètre (dans la pratique, on est plus proche de 10-20 cm que du centimètre). Et donc rover RTK pour une trace centimétrique et alignement des images avant publication sur cette trace avec les magnifiques outils JOSM. Je recommande à cette occasion pour les francophones la superbe série de tutoriels vidéo de Stéphane Peneau disponible ici sur le forum OSM France

Quelques certitudes (pour l’instant)

Il me semble aujourd’hui que :

• Alimenter Panoramax en images libres de droit est fondamental. Pour parodier un adage célèbre : “verse tes images. Même si tu ne sais pas à quoi elles vont servir, il y aura toujours quelqu’un qui en tirera un usage intéressant !”. Bien sûr, pour moi, le premier usage est l’aide aux contributions cartographiques à OSM. Mais ce nest probablement qu’une petite partie des usages effectifs.
• Privilégier au maximum les images 360 degrés. Elles permettent une perception complète de l’environnement de l’image. Il est très frustrant de ne pas pivoir modifier l’angle d’observtion sur une image monodirectionnelle. Mon sentiment (qui, comme toujours, n’engage que moi) est que les séquences d’images monodirectionnelles devraient être limitées à l’observation des signalisations routières. Les images monodirectionnelles isolées (non en séquence) ont aussi un sens, bien sûr, pour la recherche d’une grande précision sur un objet précis.
• Toujours essayer de repositionner (par traitement logiciel) ses images au mieux avant de les verser. Idéalement, bien sûr, en les calant sur un GPX RTK.
• Il y a plusieurs instances (voir ici une liste) et elles se partagent le catalogue de références, ce qui permet de pouvoir mettre dans OSM l’attribut panoramax=xxx sans avoir à se soucier de l’instance. Choisissez celle que vous voulez (en fonction de votre jugement de la qualité de service et des contraintes de versement éventuellement imposées), par exemple bien sûr l’instance OSM-FR).

Et de nombreuses incompréhensions ou interrogations à creuser Explorer les instances

Je dois avouer que je ne comprends pas bien quelles images chaque instance fournit en mode exploration. Par défaut, il semble que ce ne soient que ses propres images, ce qui est bien sûr un problème lorsqu’on explore les images, soit pour trouver une image utile pour la cartographie, soit pour planifier un trajet de collecte d’images en visant principalement des zones non pourvues.
Par défaut, l’instance Panoramax OSM-HR par exemple ne fournit que ses images.
Mais par défaut, l’instance Panoramax OSM-FR fournit ses images, mais aussi le Maroc, le Royaume-Uni, l’Amérique du Nord, mais pas les images françaises de l’instance IGN !

Pour toute exploration ayant besoin de toutes les images, un conseil qui marche :

• Ouvrez le menu déroulant “Filtres” et choisissez en haut de ce menu “Monde entier”
• Ou bien, utilisez ce site fédérateur

J’ai mis du temps à comprendre cela. Par bonheur, aucune instance n’avait hébergé d’images sur ma commune avant que je ne comprenne cette caractéristique.. Mes versements n’ont donc pas été redondants.

Organiser / découper les séquences

Par habitude (sur mes six mois de versements :) ), je ne coupe pas mes séquences. Je les recadre (via JOSM), les nettoie (suppression des images inutiles par exemple lors des pauses pour nettoyer les objectifs ou pour redresser un choc contre une branche) et les verse telles quelles, sans les découper.
Avec le recul, je nuis pas sûr que ce soit la meilleure option :

• les utilisateurs qui lancent le suivi de la séquence suivent le chemin que je me suis choisi, qui ne présente pas toujours de l’intérêt pour eux (par exemple, quand je quadrille un quartier ou un parc). Dans le cas de séquences à pied, à part s’il s’agit d’un sentier de randonnée, je ne suis pas certain que ce soit un problème.
• je pense cependant que ce choix m’obligera, si je veux mettre à jour une séquence plus tard, à rejouer la même séquence exactement.
• J’hésite donc à découper les séquences en segments de carrefour à carrefour. Cela n’est pas un grand problème pour moi (un peu plus de travail de versement) mais je crains en revanche que cela ne complique l’usage de l’exploration pour quelqu’un qui cherche à balayer une rue complète.

Organiser la maintenance des images

J’ai consacré le dernier trimestre 2025 à la cartographie des points d’apport volontaire de mon intercommunalité et au versement des 2000 photos (monodirectionnelles, précision GNSS Smartphone de base) puis le premier semestre 2026 au versement de tous les sentiers et trottoirs de ma commune (16000 photos 360 avec positionnement RTK).
Je constate aujourd’hui que certaines de ces photos mériteraient d’être rafraichies (qualité de la météo, changements urbains, etc), ce qui me pose plein de questions (sans décision / réponse pour l’instant) :

• Si je remplace une photo référencée dans OSM, il faut mettre à jour OSM. A priori OK
• Si je remplace une séquence référencée dans le champ “source” d’un changeset, comment faire? Une réponse est de ne pas remplacer mais de créer une nouvelle séquence sans supprimer l’ancienne. La référence source du changeset reste ainsi parfaitement correcte : c’est la séquence qui a été utilisée…
• mais si je ne remplace pas une séquence mais me contente d’en rajouter une nouvelle sur le même trajet, cela ne risque-t-il pas de saturer l’exploration des images (sans parler de l’usage un peu abusif de l’espace disque de l’instance) ?
• Si je remplace des images par des nouvelles mais que je ne souhaite pas faire exactement le même chemin, comment procéder ? (sauf à découper les séquences en segments carrefour - carrefour).
• Je pense qu’il existe des options d’exploration pour prendre les images / séquences récentes au détriment des anciennes mais je n’ai pas étudié cet aspect.
• Quelle fréquence pour renouveler les images ? (je pense que annuel serait cool)

Taguer les photos

Il y a clairement un travail important mené par plusieurs contributeurs pour mettre en place des outils d’analyse des images et d’alimentation d’une base de données d’attributs de parties de photos, soit via les outils d’analyse, soit manuellement et explicitement par les contributeurs.

C’est un travail que je ne maîtrise pas du tout, que je n’effectue donc pas, mais qui m’interroge :

• Je pensais au début que Panoramax était simplement un outil d’OSM et j’ai mis quelques mois à comprendre que Panoramax avait une vie à part avec des usages nombreux hors OSM. Ce tagging des images concerne donc à la fois des intérêts OSM et des intérêts extra-OSM et donc l’apprentissage de ces centres d’intérêt et peut-être de nouvelles familles d’attributs.
• Quand j’analyse une photo pour cartographier OSM, j’identifie des objets que j’envisage de cartographier (lampadaires, hydrants, commerces, mobilier de propreté urbaine, …) et je détermine les attributs ad hoc avant de les cartographier dans OSM. Je me dis que si je dois faire le même travail pour les taguer également sur la photo, je fais clairement double travail, ce qui ne me tente pas trop sans comprendre le but et l’usage. Par ailleurs, un objet tagué sur une photo devrait aussi l’être sur deux ou trois des photos voisines dans la séquence (sans parler de la séquence sur le trottoir de l’autre côté de la rue). Cela fait beaucoup … .
• Il y a peut-être une façon de taguer un objet simplement en indiquant son Id OSM (je ne sais pas). Ce serait plus simple mais poserait plusieurs autres problèmes (par exemple la non pérennité des Ids OSM au fur et à mesure des mises à jour de la cartographie)
• Il y a clairement un intérêt à la reconnaissance automatique en visant ensuite l’alimentaton d’un outil Osmose pour signaler des objets manquants dans OSM. Je ne pense pas que cela existe encore. Cet objectif pose alors le problème de l’apprentissage des outils d’analyse et mon refus [actuel] de consacrer du temps au tagging des images me culpabilise : ce tagging pourrait avoir pour but d’apprendre la bonne reconnaissance aux outils d’analyse.

Pour résumer : bravo et merci à tous les bénévoles impliqués dans ces travaux. Mais je ne comprends pas suffisamment bien pour l’instant pour m’investir la dedans.

Financer les instances Panoramax

Attention, point de vue personnel et discutable. Merci de ne pas enflammer les commentaires de cette entrée de journal sur ce point

Je comprends que les instances aient besoin de ressources (serveurs, espace disque) et j’ai vu récemment une discussion sur un appel aux dons pour l’instance OSM-FR. Au cours de celle-ci, quelqu’un a émis l’idée de faire payer les contributeurs qui déposent des volumes importants de photos (la logique étant que l’espace disque est bien sûr lié au volume déposé).

J’ai du mal à comprendre cette idée. A titre personnel, je stocke toutes les images que je verse sur mon PC pour les images d’usage courant et sur mon compte cloud (européen :) ) pour l’ensemble.
Je ne verse donc pas sur Panoramax pour stocker mes photos mais pour les mettre à disposition de la communauté. Et plus j’en verse, plus je pense rendre service, à qualité appropriée, bien sûr (comme d’habitude, ceci n’engage que moi; il s’agit d’un article de journal personnel qui fait état de mes expériences et compréhensions du monde OSM et de son environnement).

Si des financements sont à chercher, il me paraitrait logique de viser :

• les fonds prévus pour le financement des startups d’état (FAST ?)
• les principaux utilisateurs bénéficiant des images (même si elles sont bien sûr grand public)

Dans le cas de l’instance OSM-FR, il me semble peut-être un peu abusif de demander des financements à l’IGN, mais il me paraitrait raisonnable de faire financer par OpenStreetMap France (pour laquelle des appels aux dons ou des recherches de sponsors me semblent défendables).

J’ai conscience d’une certaine incohérence dans ma position : je ne comprends pas (et n’y réponds pas) un appel aux dons auprès des contributeurs Panoramax mais je comprends (et y réponds via par exemple les adhésions) un appel aux dons auprès des contributeurs OpenStreetMap. Cette incohérence vient peut-être de mon sentiment (réducteur probablement) que c’est OpenStreetMap qui est l’utilisateur principal de l’instance Panoramax OSM-FR.

Ces entrées RETEX (retour d’expérience) dans mon journal font état de mes choix de débutant, mes hésitations, mes découvertes, mes questions. Ces textes n’engagent que moi et ne sont pas des entrées de WIKI. Plusieurs de ces choix ont été évoqués sur le forum France, mais pas tous. Je reste bien sûr ouvert à tout commentaire et n’ai aucunement la prétention de donner ici des recommandations.

5 days ago

Ajout du parcours de “Mâcon Disc Golf - Parcours P.A.P.A.” à Mâcon (71)

Par ici : osm.org/node/14041516470

♦ ♦ ♦ ♦ ♦

Photos trouvées ici : udisc.com/courses/macon-disc-golf-parcours-p-a-p-a-nX1m/photos

5 days ago

More details – community.openstreetmap.org/t/should-diary-entries-move-to-community-openstreetmap-org/145754

6 days ago

I have been mapping on OpenStreetMap for a little over 11 months now. However, OpenStreetMap is not where my love for mapping started. 7 months beforehand, I started editing Google Maps. Every time I had a minute of free time, whether at my computer or on my phone while going to school, I would trace roads all around the world. I completely stopped doing anything else for fun other than fixing and creating roads.

However, this craze of mine ended on August 12th, 2025. I found out that more than 50% of my edits were being rejected by Google when I knew that all of them were OBJECTIVELY correct. I decided that I was done with Google Maps, but I needed something new to fill the hole that mapping had in my heart. That’s when I discovered OpenStreetMap 15 minutes later. I knew I had heard that name somewhere, so I decided to check it out.

Before I even completed the tutorial, I was hooked. While before I could only map walking paths, now I could map literally anything I want. Even the concept of mapping buildings was something I had to get adjusted to due to how small the number of things I could map on Google Maps was. I spent the rest of my day figuring out the mapping capabilities of the iD editor. The next day, I spent the entire day mapping and seeing what others had already mapped (spoiler alert: a lot).

My love for mapping on OpenStreetMap has never really ended; If anything, it has grown. I went out of my way to drive from Virginia all the way to Madison, Wisconsin for State of the Map 2026. Now, I have accumulated nearly 3,000 changesets and a little under 200,000 contributions to the map. I have made so many edits in Virginia to the point where I run into features I’ve edited nearly every day. I edit in school, on the car ride to school, while procrastinating homework, while having nothing else to do at home, and everything in between. I’ve recently even seen the iD editor haunt (bless) my dreams. My mind can’t go more than 5 minutes without thinking about mapping.

I’m not writing this to ask for help or anything, I just wanted to share everything on my mind and if at least one person reads this then I’m happy.

8 days ago