OpenStreetMap Blogs Last Update:

Bugün Başladım Hasan Doğan Civarını Yaptım

osm的小伙伴们大家好，今天我无意中发现了osm可以写日记然后放在自己的首页中。有的小伙伴分析地区编辑完完整度，有的教大家正确使用地图标签。虽然我注册有三年多了但是论辈分还是个小老弟😂，那我就写写我比较擅长的东西，欸要不我就写写有关家乡的一些事好了哈

枞阳县枞阳镇旗山社区邻近枞阳县人民医院、银塘花苑与银塘星城这三个区域中间有一条三级道路，道路有花坛阻拦，两条单行道形式，双向四车道（高峰期两车道因为两边可以停车）

这条道路的命名其实非常迷，枞阳县地图与天地图将其命名为健康路，而枞阳县ZY-02银塘行政区规划文件与地名信息系统将其命名为康居路（商业地图通常采用后者）。这条路到底叫康居路还是健康路？

其实我住的地方离这条路不远，所以经常在傍晚散步时走这条路。根据我的见解以及查阅对应文件的思路，这条路现阶段应该还是命名为康居路为好，至少26年8月之前还是得叫它康居路

26年初，县里开展《城市生命线》安全设备部署工作，在大街小巷安装了监测设备，同时县里也提及同日设立路灯管理所。随即4月份县里的每个路灯都贴上了标签，其中这条路的路灯被贴上康居路标签。这项工作是领先于枞阳县地图的制作的，可以认定当前这条道路仍为康居路

在枞阳县地图中，康居路并未消失而是跑到了旗山小学与中海山水城的区域中间，而它的命名依据是因为附近有个小区名为康居山庄。但是无论是在枞阳县ZY-02银塘行政区规划文件中，还是在旗山社区服务站点地图中，这个不是小区，是银塘村的回迁房，经简单查阅县政府公开文档初步确认区域名为银塘安置地。真正现存的“康居山庄”在妇幼保健院旁边，不过叫康居家园。当然不排除小区未来改名的情况

其次那条路虽然在路灯管理所的标签、附近停车场名称以及路牌中没有给出详细名称，但是在枞阳县ZY-02银塘行政区规划文件中，这条路被命名为安置地路。鉴于规划文件的审图号较枞阳县地图较新，该未分级道路我建议命名为安置地路，而保留原先的康居路命名位置

上次有个过于热心的小伙伴将康居路所在道路标为健康路（与此同时他还把旗山路标为莲城路，而莲城路是天地图的一处过时标记，我有时间在下一次日记里说），希望我的笔记能在我没时间贡献枞阳的时候，给其他人一些有理可循的参考（与此同时我也会夹带一些私货介绍枞阳有什么有意思的地方，比如枞阳中学占据的地方曾经有个自然村叫答咀村，这个村的来历可神奇了，另开一个新坑），望大家多多关照👋

A quick update on where things stand after the first half of the coding period.

In my first post I mentioned three goals for the summer. The first one, adding a Valhalla-powered routing endpoint that genuinely avoids closed roads, is now done.

The platform already had road closure data in the database. What it was missing was any connection between that data and actual routing. The frontend was calling valhalla1.openstreetmap.de directly, with no awareness of the closures sitting in our own database.

I set up a self-hosted Valhalla instance (3.5.1) running in the project’s Docker stack, loaded with Switzerland OSM data. Then I built a backend endpoint, POST /api/v1/routing/closure-aware, that sits in front of Valhalla and does the work the frontend couldn’t do on its own:

1. Fetches currently-active closures from the database that affect the requested transport mode (car, bicycle, or pedestrian)
2. Buffers each closure geometry into an avoidance polygon. LineStrings get a 10m buffer, Points get 15m, Polygons are used as-is. The buffering uses per-centroid UTM reprojection so the radii are true metres anywhere
3. Sends those polygons to Valhalla as exclude_polygons so the route detours around them
4. Returns the trip along with a count of how many closures were excluded

The frontend routing page now calls this endpoint instead of Valhalla directly, so closure avoidance happens server-side automatically.

The self-hosted Valhalla currently covers Switzerland only. For routes outside Switzerland the frontend falls back to the public Valhalla instance without closure avoidance, which is fine for now since the platform is Swiss-focused.

308 tests passing, including integration tests for all three transport modes and a version contract test that checks the Valhalla image is pinned to 3.5.1.

Next up is the sidecar service that feeds active closures into Valhalla’s traffic tile system, the second item from my original list. More on that soon.

The code is on GitHub if you want to follow along.

Hello I’m a former Marine and an American who still believes in The Constitution and the words written in it!!! Stand up!!! Stand together!!

Leia em português

♦ Front cover of the ebook A short guide to create web maps with uMap. Source of image and map data (c) 2026 OpenStreetMap contributors, uMap, and authors.

The preview and download may take a few seconds. Be patient, please.

♦ uMap MAPA-ZCM, with zoomed-in map of Guanabara Bay (Rio de Janeiro, Brazil). Map data (c) 2026 OpenStreetMap contributors, uMap, author.

SOUTO, Raquel Dezidério. A short guide to create web maps with uMap. Rio de Janeiro, Editora IVIDES, 2026. DOI: 10.5281/zenodo.21263723.

This work (ebook) is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0), which means you may share this publication, if provided the reference to the author. This publication is an adaptation of part of the uMap guide, as several new controls and dialog boxes have recently been created.

Important: IVIDES DATA™ is a registered trademark. OpenStreetMap™ is also a trademark.

IVIDES DATA™ is a small business whose primary activity is information technology consulting, headquartered in Rio de Janeiro, Brazil. CNPJ: 56.127.866/0001-12. To contact us regarding this or other matters related to the IVIDES.org™ or its company IVIDES DATA™, please send an email to ivides [at] ivides.org.

♦

♦

♦

It is a very rare moment, when somebody made a new JOSM tool, that must become one of main tools in you palette, like Building Tools or RelToolBox.

Meet Fillet Tools plugin. It will completely replace Fastdraw and partially replace Improve Way.

Silent let’s play demonstration on youtube: www.youtube.com/watch?v=agyY25jVeGM

OSM forum thread

Some important notes for newcomers of this tool:

1) Main buttons for this plugin: Shift-Enter-Alt.

• Enter = finalize drawing (press it instead of last click if you connect end of line to the other way).

• Shift + mouse roller = undo/redo drawed points

• Alt = disable way justification mode. (!)

2) Do not make self overlapping of drawed line. If you press Enter during drawed line overlapping - drawed line totally dissappears instead become new way object on the map. This dissappearing may cause big done work loosing. (!) If you made overlapping, unroll it back using Shift + mouse roller. Overlapped line is gray, not overlapped line is red.

3) If you start and finish new line on the other existing way, FilletTools works in “Part of way redraw mode” (existing lines justification mode). In this mode on pressing Enter all existing way part between start and finish points will be deleted and changed by new drawed line. To skip this mode (for example if you add new multipolygone to the existing one, like scrub to forest), you must press Alt button once at any time during drawing new line. (!)

4) Using mouse roller without pressing Shift zooms your map view. Also, during new line drawing anytime you can use “Download map data in current view” button, so you can draw this line even outside of downloaded area.

An inadvertent typo recently led me to a slightly alarming discovery. Omitting the “r” from www.openstreetmap.org took me to a website that definitely wasn’t OSM, and prompted me to download something quite suspicious-looking. Thankfully I have my browser set to “paranoid” mode so things went no further, but it still felt like a near miss.

Apologies if I’m re-alerting folks to a known issue (a perfunctory web search didn’t turn up anyone else flagging this), and I’m not expert enough to know if there’s any legal and effective way to stop the impostor, but hopefully this is at least a helpful reminder to type carefully and trust your gut if anything smells phishy :)

One hot July evening ten years ago, I found my way to a bar somewhere near the Barbican in London and descended down the stairs into the basement space for the MapSwipe launch party. At the door I was handed my name sticker and asked to fill in the number of square kilometres I had already swiped on the app. I duly filled in my 597 sq km and joined the party.

♦

MapSwipe is an open-source mobile app where you swipe through satellite imagery and help identify features. The app was created as part of the Missing Maps project to help solve a problem we had in the early days. Mappers like myself would be asked to map an area to help a humanitarian project but we would open task after task with very little in it to actually map. So, the simple, but genius, idea behind MapSwipe is what if volunteers could do a first pass through the area and pick out the features that need to be mapped; then this smaller area could be presented to mappers to trace the data and add it to OpenStreetMap.

It is very quick and easy to use MapSwipe to contribute to humanitarian mapping. Download the app and create your account, then choose a project on the front page, do the tutorial, and start swiping away and tapping on the screen every time you spot a feature you’ve been asked to find. However, on the evening of the party we had an unfortunate problem.

♦ The only photo I took all evening.

At the beginning of the party, it was announced that there were prizes for the two people who mapped the most that evening. The idea was to listen to the speeches, mingle with other partygoers, and swipe. The problem was that the Wi-Fi did not work! People struggled to download the app on the night, and you couldn’t really use it in the basement bar.

As a member of the London Missing Maps community I’d heard about the development of this app and before the launch party given the opportunity to download the app and test it out. I had enjoyed testing it out and swiping at home and on my commute and this is why I rocked up to the event with 597 sq km of mapping under my belt. As there was so little mapping to be done at the party the competition rules were changed to the winners being the ones with the most square kilometres mapped – and that is how I ended up with a lovely hand drawn MapSwipe t-shirt as a prize!

♦ Photo by Aga Kreglewska

The t-shirt was sweet, but it did get modified before I wore it next. I chopped of the collar and added some more colour to it by adding blue cloth down the sides. Here I am wearing it at the next mapathon in London in August 2016 (where I was sharing my experience of validating at mapathons).

Over the past ten years 136,000 contributors have made 216 million swipes to map together for humanitarian action using MapSwipe. The project types have increased on the mobile and web app as this small but mighty tool keeps moving forwards. The launch party was on the 19th of July 2016 so next week we can celebrate ten years of this remarkable idea made into an app that continues to make a difference. I’m glad I was there at the launch, and I can’t wait to see what comes next. Happy birthday MapSwipe!

MapSwipe: mapswipe.org

Missing Maps: missingmaps.org/

While field-testing an app I’m building for walking Public Rights of Way (MOROW), I found a real one. Chippenham parish path CHIP108, a legally recorded Byway Open to All Traffic, was mapped in OSM with highway=bridleway, ref=CHIP108, and a free-text note describing its BOAT status, but no designation= and no prow_ref=. Those are the two tags any PRoW-aware tool actually reads, so the path was rendering as an ordinary, unremarkable line. I fixed that one way directly (changeset 185555601), but the obvious next question was whether the same mistake, recording a council’s path reference under the generic ref= tag instead of prow_ref=, is a one-off or systematic.

Before building anything to find out, I went looking for prior art, and found it. Robert Whittaker’s UK PRoW toolkit (osm.mathmos.net/prow/) already does this properly, county by county, comparing OSM against official Definitive Map data and generating per-parish tagging-error reports with real way IDs ready to work through. For Wiltshire alone: 8,354 recorded rights of way, only 58% carrying designation=, only 24% carrying prow_ref=. That’s roughly 4,450 km of Wiltshire’s legal PRoW network without a prow_ref tag, a scale question the tool had already answered, far beyond anything I’d have worked out from scratch.

CHIP108 itself doesn’t appear on either of Wiltshire’s error lists, most likely because the detection starts from ways already carrying some PRoW tag and checks the other; CHIP108 had neither. I’ve asked on Robert’s forum thread (community.openstreetmap.org/t/roberts-openstreetmap- stuff-osm-mathmos-net/112981) whether that’s a known gap or something worth extending for.

Rather than wait indefinitely for a reply, I pulled a small sample, 8 ways from Wiltshire’s live tagging-errors page, and hand-verified each one against Wiltshire Council’s official Open Data Hub PRoW dataset (a genuinely open, OGL3-licensed ArcGIS feature service, distinct from their proprietary interactive map viewer) before touching anything.

Worth sharing because the verification step earned its keep, not just rubber-stamped the list: - One way already had the correct designation tag; the “error” only needed the missing prow_ref. - One reference number turned out to cover both a footpath and a bridleway segment under the same prow_ref. The physical way’s tags (foot/bicycle/horse access) were needed to work out which one it actually was. - Two of the eight sit in a different parish to the one Robert’s tool assigned them, which matches his own documented bounding-box-vs-parish caveat rather than being a bug. - Two candidates couldn’t be confirmed with confidence at all, and are being held back rather than guessed at.

Robert’s own tagging-error pages already warn that some flagged ways aren’t genuine errors. This is what that looks like in practice.

Chasing down Wiltshire’s specific feed led to a broader question: how many of England and Wales’s 161 Rights of Way authorities actually publish their Definitive Map data under an open licence? Robert maintains a thorough catalogue (osm.mathmos.net/prow/open-data/) of exactly this, which I used as the baseline rather than starting fresh.

The numbers are striking. 90.7% of authorities already have some kind of online interactive Rights of Way map for the public, so the underlying data clearly exists digitally in almost every case, but only 32.9% have released it under an open licence for reuse. That’s a two-thirds gap between “we’ve digitised this” and “you can actually use it.”

Searching for live ArcGIS-hosted feature services (the same pattern behind Wiltshire’s feed) against councils Robert’s catalogue currently shows as having no data on record turned up several genuinely new, properly OGL-licensed sources: Durham, North East Lincolnshire, and Redcar and Cleveland among them, plus a much fresher live source for Lincolnshire than the 22-month-old FOI-sourced snapshot currently on file. I’ll be passing these on.

I’ve also started emailing a small pilot batch of councils that already publish an online map but haven’t opened the underlying data, pointing out (with the actual comparable-authority numbers) that the extra step to an open licence is usually small. Early days, but happy to share how it goes and the approach used, if it’s useful to others chasing the same gap elsewhere.

None of the harder parts of this were mine to solve. Robert Whittaker’s tooling and open-data cataloguing did the heavy lifting. This is really just a small addition at the edges: a workflow for hand-verifying a batch of fixes carefully, and a fresh pass at which councils have quietly opened up their data since the catalogue was last checked.

If you maintain, or know someone who maintains, Rights of Way data for a UK council not yet on Robert’s list, get in touch with him, or with me.

Chris

Like much of the web, OSM has been struggling with bots downloading rendered maps, in our case declining to use our planet dumps to get what they want.

I therefore make a suggestion: give suspected scrapers a poisoned version of the map, for instance it could have scrambled POIs, or perhaps roads named after villains. We can then point out the source of the resulting contamination as it goes public.

For a while, the “Dienst Mobilteit van Antwerpen” (Department of Mobility of the Province of Antwerp) wanted to have (libre) streetview imagery, especially of the Belgian “cycle highways” - a type of cycling network in Belgium.

Mapillary and Panoramax are - of course - a part of their solution.

But how to actually take the pictures? It requires someone travelling along all the cycle paths.

This is where the “groendienst” (the department of Parks + greenery) comes in. They are cycling along all the cyclepaths, to make an inventory of all the invasive species. A special cargo bike is equiped with a special camera to scan the greenery and to automatically detect those invasive species.

The Mobility Department then asked to also install a GoPro on this cargo bike. And just like that, for practically no extra cost, they have streetview imagery!

You can see the cargo bike (parked in their parking garage) here

♦

Today marks exactly one year since I started making changes to the map of Korea using openstreetmap.

my projects: 제주시 원도심 * 영흥면 * 거북섬 * 제부도 * 대부동 * 영종도 and 자운대

During this time, I’ve met many talented people, participated in many projects that will benefit people for decades to come, and of course (how could I not?), I’ve also satisfied my ego with athletic achievements. Mapping is a great hobby for people like me who can never get enough of new data. Every day of mapping brings new knowledge, and with it, new emotions.

I’ve heard a lot of opinions this year. That mapping is about freedom. That mapping is about community. That mapping is about the environment in which a person lives. Perhaps all of this, and more, is completely true. But for me personally, mapping is about knowledge, data, and education. It’s like having a sweet tooth and finding a bottomless sea of ​​sugar. It’s like finding a beach where diamonds are scattered right under your feet.

We live in an age of endless wealth. Internet, AI, cartography, food, water, access to politics, access to education, access to entertainment… Without leaving our homes, we can do in a day what took scientists centuries to achieve in the past. More than anything, I can’t understand how, in this abundance, people find time to fight and kill each other. Because I personally am incapable of satiating myself with the wealth that was given to me solely by the era in which I was born.

Fate has given me almost nothing in this life. But even deprived of what little I have, I never cease to feel capable of the impossible. Only because this bottomless sea of ​​possibilities never ends.

I hate route relations. They make editing roads a nightmare, and they’re likely to be out of date. All people need is the list of stops, not the actual roads.

Today, someone mentioned to me that there’s an ongoing “reform” of a certain local tagging scheme.

At first, I really, really, really, really, really didn’t want to get involved at all.

♦

But in the end, I decided to give it a try and skim the proposal anyway.

After that, I wanted to present an argument.

To support that argument, I wanted to introduce this tool that I made several weeks ago.

But then I realized that I probably never made a blog post announcing it at all.

Weird. Usually, I always make a blog post whenever I finish an app.

After double-checking everything, I think it’s safe to say that I never made a blog post about this app.

Alright. Here we go : altilunium.github.io/terjangkau/

♦

♦

Click on any coordinate. It could be your home, your hotel room, a place you want to visit in the future, anything.

The app will query the Overpass API, retrieve all the “important facilities” around that coordinate, then show them to you, sorted by their distance from that coordinate.

Using this, you can quickly grasp “how good a place is.”

Are there any critical facilities nearby? Schools? Police stations? Fire stations? Shops? Restaurants? Other amenities?

If they exist, you can see them at a glance, sorted by distance, so you can prioritize which places you want to visit first.

Or maybe it’s not the place’s fault after all.

Maybe the facilities exist in real life, but they’re still unmapped.

You can also use this app to do a quick survey of an area. Is there something missing that still hasn’t been mapped?

Epilogue :

Turns out, I had already written something about it. But not on my OSM diary or personal blog. Instead, I wrote about it directly in both the GitHub repository and a WeeklyOSM entry.

Epilogue 2 :

Let me just translate my argument into English so the international audience can better understand the context behind this reform.

I once summarized the globally-accepted definitions of the place=* tags (see ATTACHMENT A).

My suggestion is that every decision to classify an administrative or settlement name into a particular place=* category should be both documented and justifiable, especially to OSM data users from outside Indonesia. This helps ensure that our classifications remain consistent with the international conventions behind the OSM tagging system.

It might also be worthwhile to establish a national team of OSM volunteers responsible for classifying place names across Indonesia. The team could maintain a master reference document explaining why one place belongs to a higher place=* category while another belongs to a lower one. We could even define a set of objective minimum criteria that determine when a place should be promoted from one category to another.

For example, the traditional Minangkabau criteria for establishing a nagari require four fundamental customary elements : at least four clans (suku or kaum), a mosque, a customary assembly hall (balai adat), connecting roads (labuah), and a public bathing place (tapian). These criteria are clear, objective, and measurable (population + facilities).

One of the definitions frequently used by OSM when distinguishing place=* categories refers to whether a settlement has “a good range of shops and facilities” or “few facilities available.” I’ve already built an application that can measure this. All that’s left is to define what “a good range” and “few” actually mean in quantitative terms.

ATTACHMENT A

==== place=city + capital=yes  ====
* Render : z6-z10 (circle with a dot)
* '''place=city''' : The largest settlement within a territory, including national, state and provincial capitals, and other major conurbations (an extended urban area, typically consisting of several towns merging with the suburbs of one or more cities).
* '''capital=yes''' : The capital city of the country or administrative division within countries
==== place=city + population=*  ====
* Render : z7-z10 (circle with a dot)
* '''population=*''' : To indicate a rough number of citizens in a given place. The population figure should be a stable number if possible. Typicaly, it includes residents but excludes non-residents who may be visiting the place for business or leisure. Some renderers use this key to show more populated cities more prominently, such as by labeling them with larger text, displaying them at lower zoom levels, or prioritizing them over nearby less populated places. It is recommended to also add the key source:population=* to the same object, having its value the name of the institution that counted the population and the year when the population was counted.
==== place=city  ====
* Render : z6-z14 (circle)
==== place=town ====
* Render : z9-z15 (will stop at z10 if capital=yes)
* '''place=town''' : An important urban centre that is larger than village, smaller than city, and not a suburb. Towns normally have a good range of shops and facilities which are used by the people from nearby villages.
==== place=suburb/village ====
* Render : z12-z16
* '''place=suburb''' : A major area in a town or city, with a distinct and recognized local name and identity. Suburbs may have uncertain boundaries, may overlap with other suburbs, and are often best mapped using a node. 
* '''place=village''' : A smaller distinct settlement, smaller than a town, with few facilities available, with people traveling to nearby towns to access these.
==== place=quarter/hamlet ====
* Quarter render : z14-z16 
* Hamlet render : z14-z17
* '''place=quarter''' : A named part of a bigger settlement where this part is smaller than a suburb and bigger than a neighbourhood. This does not have to be an administrative entity.
* '''place=hamlet''' : An isolated settlement.
==== place=neighbourhood/isolated_dwelling ====
* Render : z15-z19 
* '''place=neighbourhood''' : A named, geographically localised place. 
* '''place=isolated_dwelling''' : The smallest kind of human settlement. The whole settlement must not consist more than two households.
==== place=locality ====
* Render : z16-z19
* '''place=locality''' : A named place that has no population
==== place=square ====
* Render : z16-z19
* '''place=square''' : A town or village square. A (typically) paved open space, generally of architectural significance, surrounded by buildings in a built-up area. The majority of the area of this feature is paved and suitable for open markets, concerts, political rallies and other events that require a solid surface.
==== place=farm/island/islet ====
* '''place=farm''' (z15-z19) : An individually named farm, often including an area where a family of farmers resides.
* '''place=island''' (node:z16-z18, way:z4-z18) : Any piece of land that is completely surrounded by water and isolated from other significant landmasses
* '''place=islet''' (node:z17-z19, way:z11-z19) : Any very small island. Too small to support continuous occupation without shipments from other island.

Ich hatte mit dem Besuch der FOSS4G Europe 2026 Gelegenheit Timișoara in Rumänien kennen zu lernen. Die Region kannte ich bisher nicht.
Es war leicht in dieser Stadt mit fußläufigen Entfernungen eine Unterkunft zu finden, die sich sehr zentral und nahe am zeitgleich stattfindenden Jazzfestival befand. Die Stadtgeschichte lernte ich zwar erst im Rahmen der Exkursion am Samstag, kurz vor der Abreise kennen, doch ich will damit beginnnen.
Timișoara ist eine multikulturelle Stadt im Westen Rumäniens gelegen. Die Geschichte reicht weit über tausend Jahre zurück, die Stadt wurde zwischen den verschiedenen Reichen (Römisches Reich, Residenz ungarischer König, Osmanisches Reich, Türkische Herrschaft, Österreich-Ungarn, … Kommunismus) hin und her gerissen, dies hatte große Auswirkungen auf die Stadtentwicklung, die schon sehr früh (~ 500) begann. Im 11. Jh. urkundlich erwähnt, später immer wieder zerstört, im 13. Jh. Ungarisches Reich, 14 Jh. Zerstörung durch Erdbeben, 15 Jh. von den Osmanen wieder aufgebaut. Unter der Habsburger Herrschaft erfolgte der Umbau zur Festungs- und Garnisonsstadt, im dem große Teile abgerissen und nach Plan aufgebaut wurden. Diese sogenannte Planstadt ist heute die größte Fußgängerzone Europas und ermöglicht eine gute Orientierung in der Stadt. Der Anschluss ans Eisenbahnnetz erfolgte 1857 und 1884 bekam die Stadt eine der ersten elektrischen Straßenbeleuchtungen in Europa.
Timișoara hat viele schöne Gebäude im Gründerzeit- und Jugendstil, die aus der wirtschaftlichen und kulturellen Blüte stammen. Aus diesem Grund wird Timișoara auch “Klein-Wien” genannt. Die Stadt zeichnet sich durch sehr viel Grün und sehr viele Bäume aus. Eine sehr große Grünfläche, der heutige Bürgerpark, ist vorhanden, weil Nicolae Ceaușescu sein Programm zur Systematisierung der Dörfer, welches mit Plänen der Beseitigung von bürgerlichen Wohnstrukturen einher ging, zum Glück, nicht zu Ende bringen konnte. Dieses Programm sollte auf dem Land mehr landwirtschaftliche Nutzfläche und in der Stadt sozialistische Stadtviertel hervorbringen.
Die Revolution, die 1989 das kommunistische Regime in Rumänien stürzte, begann in Timisoara.

♦
Pläne und Reliefdarstellungen Timișoara

Die 3D-Abbildung links stellt ein Relief der osmanischen Befestigungsanlagen dar. Daneben befindet sich ein Bild der berühmtesten Karte aus dem Jahr 1716, Kapitän Francois Perrette zeichnete sie im Zuge des Venezianisch-Österreichischen Türkenkrieges und hatte den Auftrag die Festungsstadt exakt zu vermessen. Im Jahr 1775 entstand die Planzeichnung der Festung Temeswar, als Vorlage für den Umbau in eine moderne Stadt nach europäischen Prinzipien. Anstelle des alten Straßengewirrs wurde ein streng rationales, rechtwinkliges Straßennetz durchgesetzt. Das Relief ganz rechts zeigt ein taktiles Stadtmodell, welches im Zuge der umfassenden Modernisierung und Umwandlung in Fußgängerzonen in den 2010er Jahren im Zentrum der Stadt aufgestellt wurde. Im Jahr 2023 war Timișoara Kulturhauptstadt Europas, das Motto „Shine Your Light!“ („Lass dein Licht leuchten“) ist eine Anspielung darauf, dass die Stadt 1884 die erste in Europa mit elektrischer Straßenbeleuchtung war und 1989 den Ausgangspunkt der Revolution gegen das Ceaușescu-Regime bildete. Dem Titel Kulturhauptstat hat die Stadt mit dem gleichzeitig stattfindenen Festivalul Inimilor und dem JAZZx 2026 Festival alle Ehre gemacht.

♦
Eindrücke von der Stadt, Fotos: Hafi

Die FOSS4G Europe fand mit mehr als 300 Teilnehmenden erfolgreich in Timișoara in Rumänien statt. Das Programm war vielseitig und spannend. Eine FOSS4G Europe gibt es immer dann, wenn auf dem Kontinent Europa keine globale FOSS4G stattfindet.

Insgesamt kann die Überschrift, “the world is changing” über die Veranstaltung gesetzt werden. Angesichts der geopolitischen, technologischen und wirtschaftlichen Veränderungen, mit denen Europa derzeit konfrontiert ist, bot die FOSS4G Europe ein Diskussionsforum, um über Digitale Souveränität, anstehende Aufgaben zur Entwicklung und Anpassung von Open-Source-Software (OSS), der Rolle der OSGeo Foundation als Organisation sowie über zahlreiche OSGeo-Projekte zu diskutieren.

In der Eröffnungsveranstaltung stellten Tom Kralidis, Jeroen Ticheler und Codrina Ilie den aktuellen Status der OSGeo Foundation dar und formulierten das Ziel, die OSGeo zu modernisieren, finanziell stabiler aufzustellen sowie den Sitz in Europa anzusiedeln, um OSGeo für mehr europäische Initiativen zu öffnen. Auch die Mitgliederstruktur soll überdacht werden. Bisher hat die OSGeo Charter Members. Um Charter Member zu werden, muss eine Nominierung durch ein Mitglied erfolgen. Zu diesem Thema fand ein BoF (“Birds of a Feather”, ein informelles Treffen) statt, hier wurden einzelne Aspekte beleuchtet und dokumentiert.

Der Keynote-Vortrag CONTRIBUTING.md for Europe: Time to fork the policy repo?, in welchem Stefanie Lumnitz Beteiligungsmöglichkeiten an EU-Richtlinien vorstellt, eröffnet den Tag für verschiedenen Vorträge zur europäischen Perspektive. Zunächst ging es um die Open Source Strategie der Europäischen Kommission, das darin liegende Potential und auch die sich aus einer Beteiligung ergebenden Herausforderungen. Stefanie Lumnitz zieht einen interessanten Vergleich heran und vergleicht die EU mit dem FOSS4G-Ökosystem, erläutert die Beteiligungsmöglichkeiten für die Community an Richtlinien mitzurbeiten und erläutert die einzigartigen Strukturen der EU.

♦
Möglichkeiten und Aufruf zur Beteiligung an Beiträgen und EU-Richtlinien (Screenshots aus den Vortragsfolien)

♦
Open Source in Europa - Wäre die EU ein Freie OpenSourceSoftware-Projekt, hätte es 27 Betreuer, bei dem niemand einen Push in den Hauptzweig vornehmen kann. (Screenshots aus den Vortragsfolien)

♦
Links: Institutionen der Europäischen Union, rechts: Ablauf für Beiträge zu einer EU-Richtlinie (Screenshots aus den Vortragsfolien)

Im Beitrag Open Source, Digital Sovereignty and Europe’s Geospatial Future sprechen Marco Minghini und Stefanie Lumnitz über eine eine neue geopolitische Phase, in der digitale Technologien als Infrastruktur der Mächte dienen und erläutern die aktuelle politische Dynamik, u.a. der deutsch-französische Dialog, die Wiener Erklärung zur digitalen Souveränität sowie die Entschließung des Europäischen Parlaments zu technologischer Souveränität von digitalen Infrastrukturen. Darüber hinaus weisen sie auf das Risiko des „Sovereign-Washing“ hin, die Prioritätensetzung einzelner Akteure ist nicht immer klar. Der Aufruf geht an die Mitglieder der Community, sich als Expert:in für die Bewertung von Anträgen auf EU-Fördermittel zu engagieren. Dabei ist man als Einzelperson tätig und unterstützt die EU-Dienststellen bei der Umsetzung von EU-Förderungen und Ausschreibungen, die über das Portal verwaltet werden. Die Folien zum Vortrag enthalten weitere interessante Informationen.

♦
Links: Institutionen der Europäischen Union, rechts: Ablauf für Beiträge zu einer EU-Richtlinie (Screenshots aus den Vortragsfolien)

Hans van der Kwast illustriert in seinen Vortrag Open Source for Digital Sovereignty: Business Models, Trustmarks, and Procurement Reform die Diskussion rund um Digitale Souveränität und rechtliche Widersprüche. Er ruft auf Firmen zu gründen. Das Eisbergbild zeigt recht schön, welche Ressourcen gut greifbar und welche eher immaterieller Natur sind, verbunden mit dem Aufruf zum Handeln. “Echte Open-Source-Unternehmen leisten einen Beitrag zur Community!”, indem sie in Benutzerfreundlichkeit und Support investieren, zusammen arbeiten und sich auf die Bedürfnisse des öffentlichen Sektors einlassen. Behörden sind aufgerufen mehr Wert auf Anpassungsfähigkeit, Transparenz und langfristige Kontrolle ihrer IT-Infrastruktur zu legen und die Beschaffungslogik zu überdenken. Der Aufbau von Communities und gemeinsam investierter Infrastruktur kann Open Source Ökosysteme ins Gleichgewicht bringen.

Jeroen Ticheler stellt Nachhaltigkeitsstrategien vor, die OSS-Projekte langfristig gesund halten. Ausgehend davon, dass OSS von allen genutzt und von wenigen finanziert wird, zudem jedoch dem realen Wettbewerb unterliegt, zeigt er welche Geschäftswege helfen bzw. zusammenwirken sollten, um ein OSS-Projekt zu erhalten, sowie erfolgreich und im Wettbewerb beständig zu machen. Hier spielen Beratungs- und Produktorientierung zusammen: Im beratungsorientierten Ansatz steht der Zugang zu Fachwissen im Vordergrund, was durch Schulungen, Support oder integrierten Funktionen bereitgestellt werden kann. Bei der Produktorientierung, geht es um das ausgereifte Produkt, welches paketiert und dokumentiert einen Mehrwert schafft, Sicherheit für Nutzende bedeutet und Investitionen bei den Erstellenden ermöglicht. Letztendlich hat jeder die Wahl mitzuwirken, zu investieren oder zu beschaffen.

Open Source funktioniert nicht nur wegen des offenen Quellcodes, sondern auch weil Zusammenarbeit, Transparenz, Gemeinschaftsvereinbarungen eine langfristige Nachhaltigkeit ermöglichen. Das IGN Frankreich (Institut national de l’information géographique et forestière) hat sich für “OSS by default” entschieden und stellt Open-Source-Werkzeuge vor, die für die Klassifizierung der riesigen Lidar-Datenmengen im Rahmen des nationalen „Lidar HD"-Programms entwickelt wurden und welche Rolle sie spielen. Dazu gehören Projekte wie Myria3D (KI-basierte Klassifizierung), Coclico (Vergleichstool) und Lidro (Verarbeitung von Wasserläufen), die wichtige Open-Source-Bibliotheken (wie PDAL, GDAL, PROJ) nutzen und allesamt auf GitHub unter der Organisation IGNF verfügbar sind, Link zum Vortrag: Boosting QGIS: What France’s Mapping Agency Adds to the Toolbox. Antoine Lavende vom IGN stellt die strategische Bedeutung von Digital Commons für den Aufbau einer nachhaltigen und kollaborativen Zukunft in den Mittelpunkt und ist an mehreren Vorträgen beteiligt, in denen die französiche Kartenagentur ihren Beitrag zum OSS-Ökosystem darstellt.

Das spannende FOSS4G Europe Programm enthielt noch viel mehr sehr interessante Beiträge, um wichtigen Projekten, Ergebnissen und Erkenntnissen Raum zu geben. Die Videoaufgezeichnungen werden nach Aussage der Organisatoren in Kürze veröffentlicht.

Viele OSGeo-Projekte berichten über den Status Quo und aktuelle Entwicklungen.

Iván Sánchez Ortega hat sich Gedanken darüber gemacht, wie viele Koordinatensysteme es in einer Webkarte gibt und dies sehr schön in seinen Folien zum Vortrag illustriert.

Codrina Ilie spricht über das Open Earth Monitor Cyberinfrastructure Projekt, welches dazu dient besser zu verstehen, was Klimawandel für die Gesellschaft bedeutet. Sie stellt ein klares Bild zu Risiken auf, denen der private europäische Sektor aufgrund des Klimawandels ausgsetzt ist.

Ein großes Thema sind KI und LLMs, u.a. betrachtet Florent Gravin wie Open Source AI auf Geoinformation trifft und erläutert Funktionsweisen von GeoLLM und welche Basis und Orchestrierung es braucht. Open-Source-GeoLLM-Tools sind bereits Realität und einsatzbereit mit semantischer Suche und Funktionsaufrufen. Sie lassen jedoch wenig Aussagen zur Datenqualität zu und wie das Modell in der Größe optimierbar ist, bleibt offen. Er hält fest, dass Open Source aufgrund der Datenhoheit unverzichtbar ist und plädiert für offene Modelle, offene Daten und offene Tools, um eine souveräne, fundierte GeoAI zu schaffen, die vertrauenwürdig erscheint, weil die Mensch-Maschine-Interaktion transparent ist.

Die Initiative der QGIS-Trainer traf sich auf der Konferenz. Sie hatten sich auf der letzten FOSS4G Europe 2025 in Mostar verabredet, ein Netzwerk aufzubauen. Die Initiative wurde fortgesetzt und es gab einen Austausch von Ideen zur Zusammenarbeit.

Nach drei Konferenztagen folgten 2 Tage mit zahlreichen Workshops, die sehr gut besucht waren. Am Wochenende fand dann zum Abschluss der Community Sprint statt.

Die nächste globale FOSS4G findet vom 30.08. – 05.09.2026 in Japan in Hiroshima unter dem Motto „Bridging Geospatial Technology and Humanity“ statt.
Im Jahr 2027 wird die globale FOSS4G in Bristol (UK) stattfinden. Die FOSS4G Europe wird erst wieder in 2028 stattfinden. Ein Austragungsort wird noch gesucht.

♦
Gruppenfoto FOSS4G Europe 2026 (Quelle: LinkedIN)

♦

🚀 Conheça a nova plataforma MAPAFEST! 🗺️

O MAPAFEST é uma plataforma de gincanas e torneios de mapeamento colaborativo utilizando o OpenStreetMap (OSM). Agora com uma interface totalmente renovada e novos recursos para a comunidade!

✅ O que você encontra no MAPAFEST

🔐 Login integrado com sua conta do OpenStreetMap

🏆 Criação de gincanas e torneios

👥 Competições entre participantes e equipes

📊 Ranking em tempo real para acompanhar sua pontuação

🗺️ Lista de tarefas para mapear diretamente no OpenStreetMap

🌎 Contribua para melhorar os mapas livres do Brasil e do mundo enquanto participa de desafios e evolui no ranking.

🔗 Acesse agora

🌍 Plataforma: mapafest.mapaslivre.com.br/

📚 Documentação: mapafest.mapaslivre.com.br/v.1/doc/

💚 O MAPAFEST é um projeto desenvolvido com carinho para fortalecer a comunidade OpenStreetMap, incentivando o mapeamento colaborativo, a produção de dados geográficos livres e a integração entre mapeadores.

Mapeando juntos, transformando realidades! 🌎

Read in English

♦ Capa do e-book Mini guia de criação de mapas web com uMap. Fonte da imagem e dos dados do mapa: colaboradores do OpenStreetMap, uMap e autores.

A pré-visualização e o download podem demorar alguns segundos. Por favor, seja paciente.

♦ uMap MAPA-ZCM, com mapa ampliado da Baía de Guanabara (Rio de Janeiro, Brasil). Dados do mapa (c) 2026 colaboradores do OpenStreetMap, uMap, autora.

SOUTO, Raquel Dezidério. Mini guia de criação de mapas web com uMap. Rio de Janeiro, Editora IVIDES, 2026. DOI: 10.5281/zenodo.21195821.

Esta obra está licenciada sob a Creative Commons Atribuição 4.0 Internacional (CC BY 4.0), o que significa que você pode compartilhar esta publicação, desde que faça a referência ao autor (ver “Como citar” acima). Esta publicação é uma adaptação de parte do guia do uMap, uma vez que foram recentemente criados vários novos controles e janelas de diálogo.

Importante: IVIDES DATA® e OpenStreetMap® são marcas registadas.

IVIDES DATA® é uma empresa de pequeno porte (EPP), cuja atividade principal é a consultoria em tecnologia da informação, com sede no Rio de Janeiro (Brasil). CNPJ: 56.127.866/0001-12. Para nos contatar sobre este ou outros assuntos relacionados com o IVIDES.org® ou com a empresa IVIDES DATA®, por gentileza, envie um e-mail para ivides [at] ivides.org.

♦

♦

♦

The current representation of India’s international boundaries on OpenStreetMap is unacceptable.

Jammu & Kashmir, Ladakh, and Arunachal Pradesh are integral parts of India according to the official position of the Republic of India. Displaying a map that does not reflect India’s official boundaries creates confusion for users and undermines the reliability of your platform.

OpenStreetMap must immediately review and correct the representation of India’s boundaries or provide a clear public explanation, supported by its official mapping policy, explaining why the platform displays a different representation.

If OpenStreetMap is unwilling or unable to display India’s official map, it should clearly disclose that its map does not represent the official map of India in relevant jurisdictions. Continuing to present an alternative representation without clear disclosure is misleading to users.

I expect OpenStreetMap to provide:

1. A formal explanation of the current boundary representation.
2. The official mapping policy governing the depiction of India’s international boundaries.
3. The data sources used to determine the current representation.
4. The corrective action OpenStreetMap intends to take, if any.
5. A timeline for addressing this issue or a clear justification for maintaining the current representation.

This issue requires immediate attention. I expect a formal response explaining the current representation, the policy behind it, and the action OpenStreetMap intends to take.

Hello OSM community!

I’m excited to share a project I’ve been working on to map, analyze, and improve the data quality of places of worship across Saudi Arabia.

The website is live here: Saudi Places of Worship Map