قانون برای ایجاد کسب و کار در ایران: 1. تگ phone برای تلفن ثابت است و تگ mobile برای تلفن همراه - هرگز از تگ phone برای تلفن همراه استفاده ننمایید 2. تگ website برای دامنه کسب و کارشان است (در صورتی که دامنه ثبت شده باشد) و تگ contact:instagram برای آدرس صفحه (پیج) اینستاگرام. - هرگز ار تگ website برای صفحه اینستاگرام استفاده ننمایید 3. تگ payment:shetab_cards برای کارت‌های ایرانی است و هرگز از تگ‌های payment:visa، payment:mastercard و… استفاده ننمایید چون ویزا، مسترکارت و… در ایران نیستند.

In late-2025, we received a grant through NGI0 Commons Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet program to integrate vector tiles in uMap. This is a huge amount of work considering that a few non-trivial steps are required prior to be able to achieve that goal!

What “vector tiles support” means for uMap? At least, being able to render tiles on the Mapbox vector-tiles format (the de-facto standard), but, and that’s the interesting and hardest part, ideally to be able to customize those tiles: what if I can add a vector tiles style, but remove the buildings or change the road colors, to better fit the purpose of my map?

uMap used to be 100% coupled with Leaflet. In fact, it was initially designed as a storage for Leaflet — the first version of uMap was just a wrapper around Laflet.Storage plugin and django-leaflet-storage backend (well, the really first version was called django-chickpea, but that’s archaeology…).

So, our first need is to decouple from Leaflet, and clearly separate the rendering and the data. This is a work we have already started in the last two years but it was still unfinished (is a software ever finished is left as an exercise for the reader). Then, we want to take advantage of ES6 modules to only load the required JS files and speed up maps’ rendering (especially for read only access!). Finally, we currently rely on a lot of Leaflet plugins which are mostly either outdated and/or unmaintained that we need to port or adapt to the new chosen ecosystem.

Given that context, we are ahead of a long run BUT we already started at a good pace! Follow current PRs if you are curious. Now you may wonder why we choose OpenLayers as a target goal for vector tiles rendering over existing alternatives. Here are some of the reasons:

• Leaflet is lacking vector tiles integration and is less active than before which makes us less confident that this feature eventually lands some day; we investigated adding that support by ourselves, through a plugin, but this is huge, it needs:
  • adding a WebGL renderer, which is basically a lot of math and optimizations
  • adding support for mapbox-vector-tiles specs, which is the hard part, specifically the label placing algorithm
  • and as we developers all know: creating a piece of code is the easy part, maintaining it over the time is the hard one
• We of course tested the scenario where we would keep Leaflet as engine, and only use MapLibre for the vector tiles part (through maplibre-gl-leaflet plugin); that immediately sort of work, but:
  • this is a read only scenario (a uMap user would not be able to customize the tiles)
  • this means adding around 700Ko of JS
• We investigated Gleo, we’ve been able to make it “sort of work” (with leaflet-gleo in the middle), but gleo does not have a label placing algorithm yet, so the hard part remains, and we were afraid of the current bus factor (even if Ivan is an amazing member of the community!)
• We first targeted MapLibre but eventually decided for OpenLayers. Here are the main reasons:
  • OpenLayers allows both object-oriented data model (close to Leaflet’s one) and also a more data-oriented data model (source vs. rendering) which is our final target. This allows a smaller first migration step.
  • OpenLayers is a battery included lib, and in the uMap history we had to fight a lot against plugins maintenance. It includes all the edition parts, which is a bit less mature and more fragmented in MapLibre ecosystem.
  • When uMap was born (more than 10 years ago), OpenLayers was already here, but Leaflet was the CoolKid© in the block which motivated Yohan to choose it. Now we are more mature ourselves (read: old) and are looking for a more stable ecosystem like OpenLayers which will be here and stable for a while too (like uMap!).
  • As a bonus, OpenLayers is already ESM ready (MapLibre is not yet) and we try to use modules as much as possible in uMap to be able to load files only on demand.

As always, that kind of decision is some kind of trade-off for maintainers (and also a bet). Trying to choose the correct balance between maintenance, features, community, activity and such. All this for people ~~not keeping the link to their anonymous map~~ trying to share their best mushrooms places (don’t do that :p).

Given that we only publish a post per year, another important news: we will slowly be moving to codeberg, hopefully before the end of the year.

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.

What I built

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.

Coverage

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.

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.

Bonjour,

J’ai récemment découvert la notion de Bassin de Vie (je vous laisse lire la définition vous-même, wikipédia expliquera mieux que moi), et je me suis dit que les communes centres de ses bassins de vie pourrait être tagger comme “petite ville”, afin d’être au plus proche des réalités locales. Cependant, les données varient entre 2012 et 2022, ainsi je propose de faire une estimation large, et d’inclure les communes centres de ces deux set de données. Disponible sur le site de l’INSEE.

Merci, bonne journée

What Changed​

Previously, some maps were built by merging a set of smaller regional maps into one large file. For example, the full map of Austria was assembled from all of its individual regions; Bavaria (Germany) was assembled from its smaller sub-regions in the same way.

These merged maps are now discontinued. They won't be updated going forward — only the individual regional maps that made them up will continue to receive updates.

If you have a recent version of OsmAnd installed, a warning about this will appear automatically in Maps & Resources → Updates.

Why This Happened​

As OpenStreetMap data grows more detailed, map files get larger over time. Merged maps — combining dozens of regional files into one — eventually became too large to update and use efficiently, affecting app performance and routing speed.

Merging also meant duplication: users downloading a merged map and its individual regions were storing the same data twice. Discontinuing merged maps removes this overlap and keeps map updates faster and more reliable.

This wasn't a sudden decision — OsmAnd has been moving toward smaller, region-based maps for some time, and this change is part of that ongoing transition.

Which Maps Are Affected​

What To Do​

If you have one of the affected maps installed:

• Check Maps & Resources → Updates a warning about your installed maps.
• Delete the discontinued merged map from your device.
• Download the individual regional maps that cover the same area instead.

Going forward, updating by region means smaller downloads and keeps your maps current without needing to re-download a large file each time.

Questions or Issues​

If you have questions about this change or run into issues after switching to regional maps, contact OsmAnd support at support@osmand.net, or visit the Support page for more help options.

09/07/2026-15/07/2026

Mapping

• Voting is open for the following:
  • A proposal to add area-based wall mapping. This proposal focuses on enabling the mapping of walls as areas tagged with indoor=wall + area=yes (indoor mapping).
  • The data centre technical attributes proposal, until Wednesday 22 July. This proposal has its focus on adding attributes for telecom=data_center to describe some technical specifications: total power capacity, IT load, and usable floor area.
• Requests for comments have been called for on these proposals:
  • Deprecating int_name for foreign-language names and exonyms, since the key is used inconsistently for both romanisation and exonyms and does not follow the standard name:<language> pattern.
  • Extending the addr:* namespace with a numbered addr:2:* syntax, to tag multiple addresses directly on the same object, with a mandatory primary address used for rendering and reverse geocoding.

Community

• jellyfish_umbrella, on Mastodon, wondered how to properly tag cashierless services.
• Bluestarfish celebrated MapSwipe’s 10th anniversary by looking back at the MapSwipe launch party, which was held in London on 19 July 2016.
• Chris Debian, currently building an app for walking UK Public Rights of Way, has discovered Robert Whittaker’s UK Public Rights of Way toolkit for helping to fix the tags, and developed a workflow for manually verifying batches of fixes and reviewing which councils have quietly opened their data since the catalogue was last checked.
• Anne-Karoline Distel has published a video demonstrating how OpenStreetMap contributors can use street-level imagery from Bing Streetside, Mapillary, and Panoramax to improve map data. The tutorial focuses on using these imagery sources as references for mapping features that are difficult or impossible to identify from aerial imagery alone, such as shopfront names, traffic signs, road markings, pavements, cycle lanes, house numbers, benches, and other street-level details.
• Einar [no] has written [no] ► a short post about his experience with humanitarian mapping in OpenStreetMap, following the earthquakes in Venezuela in late June.
• Raquel Dezidério Souto reported that IVIDES DATA had just hosted the fifth session of the 2026 OSM Workshop and launched the ebook A short guide to create web maps with uMap.
• Rphyrin accidentally found a mapping sketch that he made around eight years ago during his early days of OpenStreetMap mapping.

OpenStreetMap Foundation

• The OpenStreetMap Foundation has invited everyone designing EU-funded project proposals that involve OpenStreetMap to engage with the foundation early, before submission. OSMF can act as a strategic partner on digital commons and digital sovereignty, bringing experience in open infrastructure governance and community-driven models, but not as a service provider or heavy operational actor. The post also flagged practical points to settle at the design phase, such as licensing compatibility (ODbL vs CC-BY), and how projects can give back to the OSM ecosystem, including financial contributions to the foundation’s sustainability.

Events

• Katja Haferkorn reported ► that FOSS4G Europe 2026 was successfully held in Timișoara, Romania, from 29 June to 5 July. The next global FOSS4G conference will take place in Hiroshima, Japan, from 30 August to 5 September 2026, under the theme ‘Bridging Geospatial Technology and Humanity’. The global FOSS4G conference in 2027 will be hosted in Bristol, United Kingdom.

Maps

• The Castle Map is a map of the world’s castles and fortresses. It displays the locations of more than 2,400 castles, fortresses, and palaces worldwide, using OpenStreetMap vector tiles provided by OpenFreeMap and landmark data from Wikidata.
• Chris Whong released a web version of the NYC Neighbourhoods map. Explore all 300+ neighbourhoods across all five boroughs, zoom in, and learn the geography of the city.
• geoObserver tooted about the ‘OSM-Zeitreise’, or the ‘before/after map‘, on mapki.com, based on Ian Dees’ fork of Amanda McCann’s osm-mapping-party-before-after.
• Alyosha85 has built PlaySG, a free web map made using MapLibre GL that displays every playground in Singapore. The map is automatically refreshed every week by querying the latest OpenStreetMap data through the Overpass API.
• Peter Brodersen has made a route planner that can specifically avoid roads named after men. The data is based on an OpenStreetMap extract for Paris, where every street with the name:etymology:wikidata tag is compared to the corresponding Wikidata item with a specified gender. Streets named after men are marked in the extract, and a custom OSRM routing profile is then created to avoid those roads.
• TrainRouter is an interactive atlas of 767 notable passenger train routes worldwide, rendered on OpenStreetMap-based OpenFreeMap vector tiles. The underlying rail dataset is open and licensed under CC BY 4.0.

OSM in action

• ^[1] UPLB Tools has developed RoomTBA, a web app that helps students at the University of the Philippines Los Baños find classrooms and navigate the campus.
• Radatlas is a free, bilingual (German/English) atlas of Austria’s named cycle routes. Built from OpenStreetMap route geometry and Austria’s digital elevation model, it features interactive MapLibre maps, elevation profiles, and GPX and TCX downloads for each cycling route.

Open Data

• Pieter Vander Vennet explained how the Department of Mobility of the Province of Antwerp collected street-level imagery of Belgium’s cycle highways by mounting a GoPro camera on a cargo bike and uploading the captured images to both Mapillary and Panoramax.
• PizzaTreeIsland published an interactive map that combines street name etymology data from OpenStreetMap with Elo rankings from EloEverything. EloEverything is a project where users compare two concepts at a time, producing rankings for thousands of different things. The source code is available on GitHub.

Software

• Inspired by the RoomTBA campus map, rtnF is offering an HTML script to build a custom, self-hosted, 3D campus map powered by building height data from OpenStreetMap.
• Eugene Alvin Villar reflected on CoMaps’ first anniversary since its 3 July 2025 launch, describing it as a privacy-first, offline navigation app built on OpenStreetMap data with no tracking or advertising. The piece traced CoMaps’ lineage from the original MapsWithMe through Maps.me and Organic Maps, with each fork arising after community concerns over commercialisation and governance. Villar argued that CoMaps’ explicit not-for-profit mission, alongside its open-source licence, shows why the right to fork protects projects from being held hostage by any single company.
• FairwayMapper, renamed from OpenCourseMaps after a nod to the OSMF’s trademark policy, has introduced a free, purpose-built web editor for contributing detailed golf course data to OpenStreetMap. The platform also provides a limited-access Overpass instance for OpenStreetMap contributors. The service was launched on 10 July 2026.
• Diego Camargo announced ► that the GISBR 0.3.2 QGIS plugin can now query the Overpass API, download the roads of a selected municipality, and generate two layers with minimal topology: links (road segments) and nodes (the connections between them). This data can be used for transportation network modelling purposes.
• In the ongoing series featuring open-source projects in the mapping ecosystem, Geocode Earth showcased Protomaps, which can package map data into PMTiles files that can be hosted on ordinary web storage.
• v6.19.0 of the iD tagging schema was released. It has added support for maxweightrating in France, multiple new presets (boundary=protected_area and amenity=traffic_park and 5 more), bug fixes, tweaking of existing fields, new values (for example cuisine=austrian), new icons from Roentgen 0.16.0 and more. As at publication, two further updates have been released, both containing minor changes. The iD tagging schema is now at v.7.0.1.
• Abdullah has created ► a dashboard to visualise the geographic distribution, point density, and coverage gaps of places of worship data in Saudi Arabia.

Programming

• Agasta07 shared a Google Summer of Code midterm report on category support in Nominatim.
• Egor Kotov tooted that backend v.0.4 now uses its own repository with OSRM binaries that are packaged to be self-contained (shipping with all required libraries) and immutable. More details are available.

Releases

• Freemap Europe announced that they have recently merged geotagged Wikimedia Commons photos into the main Photos layer, allowing users to browse more geotagged photos from both Wikimedia Commons and the Freemap community.
• GeoDesk has released GOL Tool 2.3, adding support for exporting query results in OSM-PBF format.

Did you know that …

• … the ShadeMap is a global shadow simulation tool that visualises the shadows cast by mountains, buildings, and trees for any location, date, and time? The platform calculates shadow positions in real time using OpenStreetMap building height data, Mapterhorn global terrain data, and tree canopy data from Meta and the World Resources Institute (2026).

OSM in the media

• Corentin Bechade reported ► on his unsuccessful search for a viable alternative to Google Maps. He spoke with Maël Thomas-Quillévéré, the founder of Cartes.app, who explained why Google’s mapping application has achieved such overwhelming market dominance.

Other “geo” things

• Bathymetrix-AI is an advanced QGIS plugin maintained by Nasef M Aly that offers a research toolkit for deriving high-precision Satellite-Derived Bathymetry (SDB) from corrected multi-spectral satellite imagery (e.g., Sentinel-2 Level-2A). It combines physics-based image processing with modern machine learning to improve bathymetric accuracy, while addressing many of the limitations of traditional SDB methods.
• The World Resources Institute has published a technical note, which describes Trazo, a framework for automatically delineating agricultural field boundaries in South America, from satellite imagery, and scaling these delineations to new geographies. There are five open resources under the CC-BY-4.0 licence, covering the technical foundation through to the 10.9-million-field release for the 2023–2024 planting season. In order to use this dataset, it is necessary to cite the technical note and the Fields of the World, which provides global predictions of agriculture field boundaries for selected years. It is available as an interactive map for Trazo.
• Early map exposure is a global challenge, not just a Kenyan one. Most school systems introduce engaging maps work too late, leaving a majority without vital spatial skills. The Cartography Fun with Maps programme, maintained by GeoMind Solutions, bridges this gap by introducing interactive cartography early. The video ‘What’s your map story?’, available on YouTube, shows some educational resources, such as the book series ‘Mappy Maria’ authored by Catherine Njore from Kenya, and published by Intercen Books. If you wish to acquire these books and support this initiative please contact the author.
• The Guardian reported that Pokémon Go data may have been used to train AI capable of assisting military drones in war zones, following Niantic Spatial’s partnership with Vantor, a company specialising in spatial detection software for drones, including those used by some militaries.
• Caleb Robinson and Isaac Corley have developed Sentinel-2 Paint, a browser app that repaints any satellite image taken by Sentinel-2 as a mosaic of real, geolocated colourful patches of the planet.

Upcoming Events

Country	Where	Venue	What	When
			MapCup Asia Pacific 2026	2026-07-01 – 2026-07-31
	Abidjan	cURAT	MAPATHON TIEBISSOU	2026-07-12 – 2026-07-24
			Mapping missing buildings in La Paz, Bolivia	2026-07-17
			Missing Maps London Mid-Month (Without Training) Advanced Mappers (Online) [eng]	2026-07-21
	Chemnitz	Kaffeesatz, Chemnitz	OSM-Stammtisch Chemnitz	2026-07-21
	Bonn	Dotty’s	202. OSM-Stammtisch Bonn	2026-07-21
	Derby	The Brunswick, Railway Terrace, Derby	East Midlands pub meet-up	2026-07-21
	City of Edinburgh	Guildford Arms, Edinburgh	Edinburgh Meetup	2026-07-21
		Online	Lüneburger Mappertreffen (online)	2026-07-21
			OSMF Engineering Working Group meeting	2026-07-24
		Online	Racha Mapping Party	2026-07-27 – 2026-08-02
	Braunschweig	Stratum 0	Braunschweiger Mappertreffen im Stratum 0 Hackerspace	2026-07-28
	Berlin	Online	OSM-Verkehrswende #77	2026-07-28
	Düsseldorf	Online bei https://meet.jit.si/OSM-DUS-2026	Düsseldorfer OpenStreetMap-Treffen (online)	2026-07-29
	Mannheim	RaumZeitLabor, Mannheim	Rhein-Neckar OSM Treffen	2026-07-29
			UN Mappers Community Discussion: Community Chapters Initiative	2026-07-31
	Hannover	Endhaltestelle Roderbruch der Stadtbahnlinie 4	Mapping Party	2026-07-31
	नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2026-08-01
	Uppsala	Datorföreningen Update	Kartträff i Uppsala. Tema Cykelinfrastruktur	2026-08-02

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.

Found by RouteQA and corrected after 41 minutes. A mapper accidentially connected the B1 around Paderborn with a cycleway.

鹿児島市の建物数集計(2026年7月17日時点)

• ちょっと気が早いが、中間報告。サボってないよってことで

検証用データ

• 基準建物数
  • 国土地理院ベクトルタイル(PBF)
    • 2026年7月1日時点
• 比較対象数(OSM)
  • Geofabrik(PBF)
    • 2026年7月17日時点
• 抽出エリア(行政界)
  • e-statより国勢調査(2020年小地域（町丁・字等）)
• 処理は前回どおり

集計結果

感想

進捗

• 4月集計から約45,000棟増加し、網羅率も51.9%⇒68.8%まで向上した
  • 主に新興住宅地と現地調査で通った道路周辺をできるだけ毎日少しずつ建物を追加した
  • 桜島地域は基準値に到達したので、ひとまず完了とした
  • 中央地域は現在作業中の「田上台」周辺で完了しそう
  • 谷山地域は「清和」「坂之上」「錦江台」の住宅地がまだ残っている
  • 伊敷地域も順調に進んでいる一方、丁目単位で未着手の区域が点在している
    • 作業場所を頻繁に切り替えたため、丁目単位で未着手の区域が点在する結果となった
      • 今後はもう少し計画的に進めたい
  • 郊外地域はまだほとんど手付かず

モチベーション

• わかってはいたもののが、同じ作業の繰り返しで飽きてくることもある
  • 一人で地図を描くのは大変だと痛感する
  • それでも、少しずつ空白が埋まっていく地図を眺めることで、やる気を補充している
  • 自分以外のマッパーも建物を追加してくださってるのを見かけ、やる気が再燃する。本当にありがたい。
• 建物ばかりでは息切れするので、POI追加や現地調査などを織り交ぜながら継続している
• 住宅地より郊外の方が描いてて楽しかったりする

〆

• 正直、思ったより進捗伸びてて驚いた
• 今後の動きとしては先に穴が開いてる住宅地を済ませて、のんびり郊外を進めていきたい
  • 道路・山林の整備も含めて進めていく予定
• 数値管理については、今後はWikiの方へ移行しようかなと思っている

Please refer my March 2025 diary entry as this is changes only.

• Changed the voice recording notes method to a dedicated microphone nearer my face. I launch a script at the same time I start the side cameras. It still saves as date/time stamped 1 minute length files.

• Use a dedicated 2nd WiFi device on the laptop for direct connection (not using in van WAP) to the 225deg side facing camera. This increases the max framerate slightly. The 270deg side camera is still USB connected.

• Procured a cheap 2K dashcam and mounted it rear window. Actually has a GPS position reporting fault, but the clock is okay. Do a lot of local processing to geotag against the UBLOX GPS unit to give 1FPS above 45kph and 3FPS below. Very handy for capturing the back side of speed signs by either swapping views locally or seeing the signs recognised on Mapillary.

• The WiFi/cell router now has two antennas connected (MIMO) which helps the upload rate rate and low signal area performance. Now upload 15-40GBytes for each drive day.

• One of the 20 year old Toshiba laptops had a temp sensor fail such that the cooling fans wouldn’t start. Upgraded both to 10 year old HP Probooks. These reduce processing time approx in half. The extra dashcam included. Still running Debian Linux.

• No longer beacon APRS.

• GPS nav unit now has giveway and stop sign POI’d displayed, so I can add these to the voice notes. I continue to create other special POI’s plus modify the mkgmap process for better end use.

Currently near Injune Qld about to sit still for a while.

Cheers Bob

双击放点，再点，双击结束 * 地震级的编辑体验 欢迎前往 map.osm.asia 体验

BetteriD 和 map.osm.aisa

今天想认真介绍一下 BetteriD，它是 map.osm.asia 默认搭载的编辑器。

BetteriD 是一个基于 OpenStreetMap iD 的改进版编辑器。它的目标不是简单地“换个皮肤”，而是尽可能补齐 iD 长期以来一些影响编辑体验的细节。

我们希望保留 iD 轻量、直接、易上手的特点，同时逐步补充正式版缺失的偏好设置、编辑细节、移动端体验、快捷键兼容，以及一些更加现代化的辅助功能。

简单来说，它是一个更适合长期使用、更贴近实际编辑习惯的 OSM 编辑器分支。

本次更新

这次更新的重点只有一个：让编辑更顺手。

明确区分官方与第三方

首先，编辑器启动时会明确提示当前并非 OpenStreetMap 官方站点。

这样做不是为了制造距离感，而是避免用户误认为自己正在使用官方服务。BetteriD 虽然努力提升编辑体验，但它依然是一个独立项目，不应该与官方站点混淆。

基础体验改进

这一版本修复和优化了不少长期影响使用体验的问题，例如：

• 翻译继承源从开发版调整为正式版，避免不稳定内容进入翻译链。
• Bug 反馈入口不再直接指向本项目。

• 修复和优化多个已知问题，例如：

  • 缩放后元素大小偶尔异常；
  • 对象卡住但地图仍可移动；
  • 缩放与平移状态不同步等。

更符合编辑习惯

我也调整了不少快捷键和地图操作，希望更符合老编辑者的使用习惯。

包括：

• 兼容部分 JOSM 常用快捷键（在不冲突的前提下）。
• 支持按住右键拖动平移地图。
• 持续优化整体交互逻辑。

更好的移动端体验

移动端一直是 iD 的短板，因此 BetteriD 做了一些针对性的优化，例如：

• 减少菜单层级；
• 双击进入绘制；
• 再次双击结束绘制；
• 长按添加节点。

希望让手机编辑不再那么繁琐。

AI 辅助功能

AI 功能目前仍在持续完善，但设计目标始终是用户体验优先。

当某个模型或接口失败时，并不会直接把错误展示给用户，而是会按照预设优先级自动切换备用方案，实现尽可能平滑的回退。

目前涉及的能力包括：

• 网络搜索；
• 标签建议；
• 文本生成等。

同时，偏好设置支持用户自行配置模型优先级，而不是固定使用某一个模型。

正在开发中的实验功能

除了现有功能外，还有一些实验性功能正在推进。

包括：

• 支持导入本地照片作为辅助底图，不上传、不审核、不参与 POI 识别，仅用于本地编辑参考。
• 上传图片后可调用公开接口，在需要时进行图片审核和 POI 识别，与本地照片模式完全独立。
• 根据自然语言描述，由 AI 自动生成 OSM 标签建议。
• 支持叠加两种底图，并可自由调整透明度进行对照。
• 室内编辑增强：选中当前楼层后，自动弱化其它楼层及无关图层。
• WASD 地图移动，默认采用步行模式，并尝试实现更加流畅的飞行模式。

更完善的偏好设置

BetteriD 也在逐步补齐 iD 正式版已有以及缺失的偏好设置。

目前包括：

• 翻译语言数量；
• 智能拆分依据；
• 吸附范围；
• 默认隐藏行政区边界；
• 实验功能总开关；
• 更多可配置选项。

未来仍会继续完善，让更多功能交给用户自由选择，而不是固定写死。

最后

我最喜欢这次更新的一点，并不是增加了多少功能，而是 BetteriD 正在慢慢变成一个真正适合长期使用的工具。

它还不完美，也还有很多地方需要继续打磨，但方向一直没有改变：

让 OpenStreetMap 编辑少一点阻力，多一点顺手。

GitHub：

https://github.com/koharachan/BetteriD/

ps：小声告诉你，实验功能其实已经可以用了哦

Today in our OpenStreetMap (OSM) interview series we are speaking with Matthew Whilden about his journey as an OSM mapper, his work supporting the community through the OpenStreetMap US Board, and his passion for creative mapping. From parks and playgrounds to hidden features discovered through geocoding and aerial imagery, Matthew’s story highlights the curiosity and community spirit that shape OpenStreetMap.

Here is an example of the cathedrals of Germany that we created using Matthew’s XofY tool.

1. Can you introduce yourself and tell us a bit about your OpenStreetMap journey? What first got you hooked on mapping?

I started adding parks and playgrounds when my daughter was born. Both as a simple pastime while she napped, but also a way to explore more things to do with her as she got older. Editing the map is a lovely way to learn more about the world.

2. You’ve mentioned using geocoding to turn lists of addresses into mapping adventures, for example tracking down drive in movie theaters. Can you walk us through your “OSM sleuthing” workflow and share some of your favorite discoveries?

For many years I was obsessed with odd things you can find on aerials (ex: jet sprint boat race lakes). Things that aren’t tricky to find, so long as you know, roughly, where to look. Many oddities will have someone keeping track of them with a list of addresses but for OSM, we can do one better! Geocoding with Nominatim or OpenCage makes for a great start to nailing down the exact locations of these things.

3. As a member of the OpenStreetMap US Board, what are your priorities for supporting the community? What opportunities and challenges do you see for OSM in the United States?

We can get further by all rowing in the same direction. Finding places where we can help sort out the common ground between mappers, app developers, imagery providers, educators, etc., is always a huge win. It’s why I’m so proud of the multitude of working groups we have and the great work we support through those groups.

Fundraising is always top of mind as a board member. I would love to be able to hire a few more technical staff and navigating the ever changing landscape of where memberships and grants are coming from continues to be a challenge.

4. A lot of people assume that mapping is just about adding roads or buildings. What are some of the more unusual or niche projects you’ve worked on, and why do those kinds of contributions matter?

I strongly recommend everyone have at least one really niche tag or type of map data that they are super obsessed over. Preferably something super weird. It’s largely all volunteer work so if we’re not having fun then we’re gonna burn ourselves out! We need more things mapped and ALSO more tools, tutorials, and hype videos to help folks stay engaged.

Here’s some things I’ve been obsessive about to help give folks a sense of what I mean:

A map showing school mascots around the world.

I wrote a long tutorial for a JOSM plugin to help add sidewalk coverage.

I got really into learning about nautical beacon tagging and ended up making a whole website to view blinking lights.

I spent a few hours adding Wikidata tagging so folks could sort out the two different competing restaurants named Taco Time.

5. OpenStreetMap is powered by a global community of volunteers. What advice would you give to someone who wants to move beyond simple edits and start exploring, investigating, and contributing in more creative ways?

Honestly, see what other folks are doing. Join us in the OSM US Slack, the OSM World Discord, on the OSM specific Mastodon server, or any of the million other places mappers are meeting up and sharing ideas, insights, and schemes. I am constantly finding new ways of doing things, new tags, new tools, and inspiration from folks in these spaces.

6. OpenStreetMap recently celebrated its 20th anniversary. Looking ahead, where would you like to see the project and its community 20 years from now?

I’m very lucky to be part of a large and long running community group here at OpenStreetMap US. A huge part of the success is having dedicated and consistent staff that can grow in their roles without having to split time paying their bills with other work. I would love to see more local chapters grow and have support staff for local programs, regional outreach, specific tech needs etc. We have a lot of work to still do and the sky is the limit.

Matthew’s journey shows that mapping is about more than documenting what exists. It is a way to explore, learn, and connect with the world around us. His creative approach reminds us that every mapper can bring something unique to OpenStreetMap, whether through a niche interest or a community project. Thank you, Matthew, for sharing your story and for the energy you bring to the OSM community.

Happy mapping

Danielle

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

Running every morning is just what you do. No discussion — just the street and whatever distance feels right that day. Your running partner lives on Yonge Street. So do you. Same street, different ends — and when he suggested a 7 AM run "somewhere in the middle", it sounded simple enough.

Yonge Street is 56 kilometres long. The longest street in the world, according to Guinness. It starts at Lake Ontario and runs straight north through Toronto until it quietly disappears near Holland Landing. "Somewhere in the middle" turned out to be a question neither of you had actually answered. You were both on Yonge Street — technically neighbours — and had absolutely no idea how far apart you were standing.

A few taps in OsmAnd, and the guessing stopped. Distance by tap, radius circles, a straight line to your meeting point — tools that turn a vague sense of scale into something exact.

Photo by Getty Images on Unsplash

Distance by Tap: Quick Gestures on the Go​

You're three kilometres into the run and there's a park ahead. Is it worth the detour, or is it further than it looks? You don't want to stop, open a route planner, and wait for a calculation. You just want a number. That's exactly what Distance by Tap is for. Enable it in Menu → Configure screen → Other → Distance by tap, and the tool is ready whenever you need it .

Tap anywhere on the map and a straight line appears from your current location to that point, with the distance shown right on the line. Tap somewhere else, and the line moves. It stays on screen as you keep going, giving you a live read on how far something is.

For measuring between any two points — say, from a subway entrance to a coffee shop — place two fingers on the map simultaneously. OsmAnd draws the line between those two points and shows the distance between them, independent of where you are.

If the label is hard to read while moving, go to Menu → Configure screen → Other → Distance by tap → Text size and switch from Normal to Large. The label becomes 1.5× bigger, with extra spacing added between the line and the text. The change applies instantly. No interruptions to the pace.

Ruler: A Permanent Scale on Your Screen​

Distance by Tap answers a specific question: how far is that point? The Ruler answers a different one: what does distance actually look like on this map right now?

It sits at the bottom of the screen as a thin line segment labeled with its real-world length — 100 meters, 500 feet, whatever fits the current zoom level. No setup needed, no widget to add. It's simply there, adapting quietly as you pan and zoom. Closer in, the scale shrinks to show finer distances. Zoomed out over the whole city, it stretches to represent kilometres.

Running along an unfamiliar stretch of Yonge Street, you glance at the map and see a segment marked 200 m. The next intersection looks about two segments away — roughly 400 metres. So, to change the units between metres and feet, go to Menu → Configure profile → General settings → Units & formats → Units of length. The scale updates instantly across the whole map. It's a small thing, permanently useful.

Radius Ruler: Visualizing Spheres of Reach​

Sometimes the question isn't how far a specific point is — it's what's actually reachable from where you're standing.

Enable the widget via Menu → Configure screen → Widgets → Choose a panel → Add widget → Radius ruler, and the map fills with concentric circles centred on your location. Each ring is labeled with its distance — 1 km, 2 km, 3 km and so on. The intervals adjust automatically as you zoom in or out.

On a long run down Yonge Street, this changes how you read the map. Instead of measuring point to point, you can see at once which parks, subway stations, or coffee shops fall within a comfortable distance — and which ones don't.

Tap the widget to cycle through three display modes — Hide, Light, and Dark — depending on what works best against the map underneath. For a wider view of the surrounding area, go to Menu → Configure screen → Other → Display position and switch your location from Center to Bottom — this shifts your position lower on the screen and expands the visible radius above you. You can also tilt the map into 3D view with a two-finger swipe up, which gives the circles depth and makes distances easier to read across the landscape.

Map Markers and Target Line: Tracking Points in Real Time​

You've agreed to meet your running partner at Jaye Robinson Park. You drop a marker on the map — a quick long-tap, then add marker and a flag appears at that point. That's your target.

Enable Arrows on the map and Direction line in Menu → Map markers → Appearance, and the map connects your current location to the marker with a straight line. As you run, the line updates continuously — the distance to the marker counts down, and the bearing shifts as your angle to the target changes. If the marker moves off screen, an arrow takes over and keeps pointing you in the right direction.

The Map markers bar widget at the top of the screen shows the distance and direction to your marker at all times — so even when you're zoomed in and the marker isn't visible, you always know how far you are and which way to go.

Straight Line Routing: Building Complex Measurement Paths​

Today's run has a few more moving parts: starting on Yonge Street, cutting across a park, following a trail that isn't on any road map, finishing somewhere several kilometres away. For that, you need something more structured.

Open Menu → Plan a route and select the Straight line method. A dashed line connects each point you place, and as you build the route, the points list below shows the distance and azimuth for each segment. You're not following roads — you're drawing directly across the map, which makes this tool particularly useful for off-road areas or anywhere the street network doesn't match where you actually want to go.

Add points one by one using the pointer at the centre of the screen, then tap Add point. Move the map to position the next point, add it, and the segment builds. Each entry in the points list shows the cumulative distance and the bearing from the previous point — so at any stage you can see not just the total length of your path, but the exact direction of each leg.

When you're done, the route can be saved as a GPX track — a standalone file you can reopen, share, or use for navigation later. What started as a rough measurement exercise becomes a reusable track.

From Guesstimate to Exact Numbers​

Running 56 kilometres of Yonge Street in one go was never the point. The point was knowing — at any moment, from any spot — exactly how far something is, what falls within reach, and where a route actually leads. Each tool in this article answers a different version of that question.

Before you head out, take a moment to explore the full documentation — you'll find links to each tool throughout this article. Once you're ready, try the interactive quiz below to see how well you can put it all together.

We appreciate your interest in us and thank you for taking the time to read this article. Join us on social media to keep up to date with the latest news and share your experiences. Your opinion is important to us.

Follow OsmAnd on Facebook, TikTok, X (Twitter), Reddit, and Instagram!

Join us at our groups of Telegram (OsmAnd News channel), (EN), (IT), (FR), (DE), (UA), (ES), (BR-PT), (PL), (AR), (TR).

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

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.

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

关于康居路

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

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

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

1. 根据路灯管理局的路灯标签判断

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

2. 根据枞阳县ZY-02银塘行政区规划文件中康居小区存在与否判断

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

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

为啥要写这条路

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

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 : https://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.

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.

What I built

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.

Coverage

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.

Tests

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.

Timișoara

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

FOSS4G Europe fand vom 29. Juni bis 5. Juli 2026 statt

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)

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

🚀 Conheça a nova plataforma MAPAFEST! 🗺️

Discover the new MAPAFEST platform!

🚀 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: https://mapafest.mapaslivre.com.br/

📚 Documentação: https://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! 🌎

Mapafest #OpenStreetMap #OSMBrasil #UmbraOSM #MapeamentoColaborativo #OpenData #DadosAbertos #Gincana #Torneio #MapasLivres

Leia em português

IVIDES DATA™ hosts the fifth session of 2026 OSM Workshop and launches an ebook on creating web maps with uMap

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.

PREVIEW OR DOWNLOAD EBOOK (7.8 MB)

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

Resources for creating web maps with uMap were presented during the fifth session (in portuguese): project creation and configuration, creation of static and dynamic layers, label customization, clustering and heatmaps. This event is part of the 2026 OSM Workshop Series (translation), organized by IVIDES DATA™ in partnership with the Institute of Geosciences at State University of Campinas - Unicamp (São Paulo, Brazil).

The files used in the fifth session can be found in the VIDEO DESCRIPTION

All content is available on the LEARNING PORTAL.

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

HOW TO CITE

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

LEGAL NOTICE

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.

Read in English

IVIDES DATA® realiza a quinta sessão do Ciclo de Oficinas OSM 2026 e lança e-book sobre a criação de mapas na Web com uMap

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.

VISUALIZAR OU REALIZAR O DOWNLOAD DO E-BOOK (7,8 MB)

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

Durante a quinta sessão, foram apresentados os principais recursos para a criação de mapas web com uMap: criação e configuração de projetos, criação de camadas estáticas e dinâmicas, personalização de rótulos, agrupamento (clustering) e mapas de calor (heatmaps). Este evento faz parte do Ciclo de Oficinas OSM 2026, organizado pela IVIDES DATA®, em parceria com o Instituto de Geociências da Universidade Estadual de Campinas - Unicamp (São Paulo, Brasil).

Os arquivos utilizados na quinta sessão podem ser encontrados na DESCRIÇÃO DO VÍDEO

Todo o conteúdo está disponível no PORTAL DO CICLO DE OFICINAS OSM 2026.

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.

COMO CITAR

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.

AVISO LEGAL

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.

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: https://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.