Nothing in OpenStreetMap goes stale faster than opening_hours. A business moves its closing day from Monday to Tuesday, edits one line on its website, and the map still shows last year’s answer. You find out when you are standing in front of a locked door.

So Fulda has had a small watchman running for a few weeks now: 559 business websites in the town and its district, each checked every three days, and not the whole page but exactly the block that carries the hours. If one character in there changes, a message goes out.

The interesting part is not the machinery behind it, it is how little you need in order to join in. Two interfaces are enough, and you probably have both open already: GitHub for adding a page, Matrix for reading what comes back.

Adding a business: one issue, one number, one click

If you know a page whose opening hours are worth watching, you open an issue from the template Watch vorschlagen. Three fields: the page, the name of the business, its OSM id.

A bot takes over from there. It fetches the page, looks for the text blocks that could be opening hours, and posts them into the issue, numbered. Not as code, not as XPath, but as the text it would capture:

1)  Montag - Freitag 09:00 - 18:00 Uhr / Samstag 09:00 - 13:00 Uhr
2)  Termine nach Vereinbarung, Telefon 0661 ...
3)  Bürozeiten der Hausverwaltung: Mo, Mi 10 - 12 Uhr

You answer with /pick X. The bot writes the file, pushes the branch and comments a link that opens the pull request with the title already filled in. One click, done.

No fork, no installation, no API key, no XPath. What the bot deliberately does not do for you is the reading: which of those three blocks really carries the hours of this business, rather than the landlord’s office hours, an appointment window or a running clock. That is the actual decision in this project, and it stays with a human.

The bot also knows when to say no. A page that is already watched gets named together with the file that covers it. A page that was looked at once and found unusable comes back with the reason and the date, instead of a proposal that the checks would reject anyway.

The alert arrives in Matrix

When a page reports in, it lands in a room shared with other mappers: #osm-fulda-openinghours:matrix.org. This is how the message arrived on 4 September, real and uncut:

Öffnungszeiten geändert: Klosterladen Abtei Fulda
Webseite: https://www.abtei-fulda.de/stadtkloster/klosterladen/
OpenStreetMap: https://www.openstreetmap.org/node/5511605749

+ Dienstag, 8. September, geöffnet: 13 – 16 Uhr

Zu tun: Zeiten in OSM prüfen, dann check_date:opening_hours setzen.
Zeigt der Diff keine Öffnungszeiten, ist es ein Fehlalarm: OSM bleibt unberührt, der Filter
muss nachgezogen werden.
Wie Fehlalarme entstehen
Fehlalarm melden

Title, page, OSM object, the line that changed, the job to do. The link to the object turns the alert into one click instead of a search through the map, and the last two lines are links whose addresses stay out of the way of the text. The message is German because the people acting on it map in Fulda.

False alarms happen, which is why the way to report one sits in the message itself. A filter that captures the hours today can hit the news box after a site relaunch. Then the diff shows no hours, OSM stays untouched, and the filter gets redrawn: another issue form, again without a fork.

To read along you need nothing but a Matrix account. No subscription, no flood of email: across roughly 560 watched pages that is a handful of messages a week, if that, plus a short report early on Mondays listing the watches whose capture no longer holds hours.

Why the chain ends at Matrix and not at OSM

Writing the new hours straight into OpenStreetMap would be technically easy. It would also be wrong.

A website can be wrong. A change can be a holiday notice that is gone again next week. A sign on the door beats the website in case of doubt. And a bad watch is noise, while a bad tag is somebody else’s data. So the automation stops at the message: the monitor points at something you would otherwise miss, and a person takes it from there, someone who can go and look if it comes to that.

What does not work

Honestly: not every page is usable. Chains publish their branch hours behind a postcode search, and a diff on the corporate page says nothing about the shop in town. Opening hours photographed as a sign are an image, not text. Some sites block every automated fetch. And more often than you would expect, a website simply never states its hours.

Those cases are not dropped quietly. Each one is recorded with a reason and a date to look again. A business that only has a social media page today may have its own next year.

This works one size smaller. And one size larger

It actually started one size smaller. The OSM user GeoMH had decided for himself to run changedetection on his own computer, to keep important infrastructure in his district up to date, pharmacies above all. Working that way took him across the district boundary into our corner of the map, which is how the contact came about, and his approach became the idea of building the concept out further. Everything described here is an extension of his version, not a replacement for it.

Fulda runs it permanently on a server because several people read along there. That is not a requirement. The core is changedetection.io, a container you start on your own machine whenever you have time for map work: it checks the pages you gave it, shows what changed since last time, and can be switched off again afterwards. One evening a month is enough for a small town.

Matrix and GitHub are interchangeable too, they are simply the most convenient choice here:

• Without Matrix. changedetection sends its notifications through the usual channels, email, ntfy, Telegram, whatever you actually read. We put a small relay in front of it because matrix.org hands out short-lived access tokens. Working alone you need no notification at all: the list of changed pages inside the app is the work list.
• Without GitHub. A watch is a small file. If you map for yourself, you keep those files locally. GitHub buys three things that only start to matter once more than one person joins in: a review before anything goes live, an automatic check on every proposal, and a way in for people who do not want to touch a repository.

There is just as much room upwards. The area sits in each entry’s category tag (fulda-bakery), so several places can live in one instance without mixing, and weekday and time-format detection is a small file of its own that takes further languages. Whether that becomes 60 watches for one district or a few thousand for a whole region changes nothing about the structure, only the question of who reads the alerts.

Rebuilding it

Everything is open, GPL-3.0. The craft is documented separately and in English, so another town can start from it: how to find the hours block on a page, how to tell that the filter caught the wrong one, and why a watch is a file rather than a form. What you need in order to contribute is written in German, because whoever adds a watch here is reading German opening hours anyway.

If you know a business in Fulda whose hours in OSM are out of date: the issue form is open, and the bot answers faster than any maintainer.

https://github.com/osm-fulda/oeffnungszeiten

In OpenStreetMap veraltet nichts so schnell wie opening_hours. Ein Betrieb schiebt den Ruhetag von Montag auf Dienstag, ändert eine Zeile auf seiner Website, und in der Karte steht weiter der alte Stand. Auffallen tut das erst, wenn jemand vor einer verschlossenen Tür steht.

Für Fulda läuft deshalb seit ein paar Wochen ein kleiner Wächter: 559 Websites von Betrieben in Stadt und Landkreis, jede alle drei Tage geprüft, und zwar nicht die ganze Seite, sondern genau der Block, in dem die Zeiten stehen. Ändert sich dort ein Zeichen, gibt es eine Nachricht.

Das Interessante daran ist weniger die Technik dahinter, sondern wie wenig man braucht, um mitzumachen. Zwei Oberflächen reichen, und beide hat man vermutlich schon offen: GitHub zum Hinzufügen, Matrix zum Mitlesen.

Einen Betrieb hinzufügen: ein Issue, eine Zahl, ein Klick

Wer eine Seite kennt, deren Öffnungszeiten beobachtet werden sollten, öffnet ein Issue über die Vorlage Watch vorschlagen. Drei Angaben: die Seite, der Name des Betriebs, seine OSM-Id.

Danach übernimmt ein Bot. Er holt die Seite, sucht die Textblöcke, die nach Öffnungszeiten aussehen, und kommentiert sie durchnummeriert im Issue. Nicht als Code, nicht als XPath, sondern als den Text, den er einfangen würde:

1)  Montag - Freitag 09:00 - 18:00 Uhr / Samstag 09:00 - 13:00 Uhr
2)  Termine nach Vereinbarung, Telefon 0661 ...
3)  Bürozeiten der Hausverwaltung: Mo, Mi 10 - 12 Uhr

Man antwortet mit /pick X. Der Bot schreibt die Datei, schiebt den Branch und kommentiert einen Link, der den Pull Request mit ausgefülltem Titel öffnet. Ein Klick, fertig.

Kein Fork, keine Installation, kein API-Schlüssel, keine XPath-Kenntnisse. Was der Bot bewusst nicht abnimmt, ist das Lesen: welcher der drei Blöcke oben wirklich die Öffnungszeiten dieses Betriebs trägt und nicht die Bürozeiten des Vermieters, ein Terminfenster oder eine mitlaufende Uhr. Das ist die eigentliche Entscheidung im Projekt, und sie bleibt beim Menschen.

Der Bot weiß auch, wann er absagt: Seiten, die schon beobachtet werden, nennt er samt der Datei, die sie abdeckt. Seiten, die schon einmal geprüft und für untauglich befunden wurden, weist er mit Grund und Datum zurück, statt einen Vorschlag zu bauen, den die Prüfung ohnehin kassiert.

Der Alarm kommt in Matrix an

Meldet sich eine Seite, landet das in einem Zimmer, das mit anderen Mappern geteilt wird: #osm-fulda-openinghours:matrix.org. So kam die Meldung am 4. September an, echt und ungekürzt:

Öffnungszeiten geändert: Klosterladen Abtei Fulda
Webseite: https://www.abtei-fulda.de/stadtkloster/klosterladen/
OpenStreetMap: https://www.openstreetmap.org/node/5511605749

+ Dienstag, 8. September, geöffnet: 13 – 16 Uhr

Zu tun: Zeiten in OSM prüfen, dann check_date:opening_hours setzen.
Zeigt der Diff keine Öffnungszeiten, ist es ein Fehlalarm: OSM bleibt unberührt, der Filter
muss nachgezogen werden.
Wie Fehlalarme entstehen
Fehlalarm melden

Titel, Seite, OSM-Objekt, die geänderte Zeile, Auftrag. Der Link auf das Objekt macht aus der Meldung einen Klick statt einer Suche in der Karte; die zwei letzten Zeilen sind Links, ihre Adressen stehen im Text nicht im Weg.

Fehlalarme gibt es, deshalb steht der Meldeweg gleich in der Nachricht. Ein Filter, der heute die Zeiten einfängt, kann nach einem Relaunch der Website plötzlich die Neuigkeiten-Box treffen. Dann zeigt der Diff keine Zeiten, OSM bleibt unberührt, und der Filter wird nachgezogen: wieder ein Issue-Formular, wieder ohne Fork.

Wer mitlesen will, braucht nur einen Matrix-Account. Kein Abo, keine E-Mail-Flut: Bei rund 560 beobachteten Seiten sind das ein paar Nachrichten pro Woche, wenn überhaupt. Dazu montags früh ein kurzer Bericht, welche Watches ihre Zeiten nicht mehr sauber einfangen.

Warum die Kette bei Matrix endet und nicht bei OSM

Es wäre technisch machbar, die neue Zeit direkt in OpenStreetMap zu schreiben. Aber das wäre falsch.

Eine Website kann irren. Eine Änderung kann ein Feiertagshinweis sein, der nächste Woche wieder verschwindet. Ein Schild an der Tür schlägt im Zweifel die Website. Und ein falscher Watch ist Lärm, ein falscher Tag sind fremde Daten. Deshalb endet die Automatik bei der Nachricht: Der Monitor zeigt auf etwas, das man sonst übersieht, den Rest macht ein Mensch, der auch zur Not mal hinfahren könnte.

Was nicht funktioniert

Ehrlicherweise: nicht jede Seite taugt etwas. Ketten veröffentlichen ihre Filialzeiten hinter einer Postleitzahlensuche, ein Diff auf der Konzernseite sagt nichts über den Laden in der Stadt. Öffnungszeiten als abfotografiertes Schild sind ein Bild, kein Text. Manche Seiten blocken jeden automatischen Abruf. Und überraschend oft nennt eine Website ihre Zeiten schlicht gar nicht.

Diese Fälle werden nicht stillschweigend verworfen, sondern mit Begründung und Wiedervorlagedatum festgehalten. Ein Betrieb, der heute nur eine Social-Media-Seite hat, kann nächstes Jahr eine eigene haben.

Das geht auch eine Nummer kleiner. Und eine Nummer größer

Angefangen hat es sogar eine Nummer kleiner. Der OSM-Nutzer GeoMH hatte für sich entschieden, changedetection auf dem eigenen Rechner laufen zu lassen, um wichtige Infrastruktur in seinem Landkreis aktuell zu halten, allen voran Apotheken. Dabei ist er über die Kreisgrenze in unsere Ecke geraten, so kam der Kontakt zustande, und aus seinem Vorgehen wurde die Idee, das Konzept weiter auszubauen. Alles, was hier steht, ist ein Ausbau seiner Fassung, nicht der Ersatz dafür.

Fulda betreibt das dauerhaft auf einem Server, weil dort mehrere Leute mitlesen. Nötig ist das nicht. Der Kern ist changedetection.io, ein Container, den man auf dem eigenen Rechner startet, wenn man Zeit für Kartenarbeit hat: Er prüft die hinterlegten Seiten, zeigt, was sich seit dem letzten Mal geändert hat, und darf danach wieder aus sein. Ein Abend im Monat reicht für eine Kleinstadt.

Auch Matrix und GitHub sind austauschbar, sie sind hier nur die bequemste Wahl:

• Ohne Matrix. changedetection schickt seine Meldungen über gängige Kanäle, E-Mail, ntfy, Telegram, was man eben liest. Bei uns steht ein kleines Relais davor, weil matrix.org kurzlebige Zugangstoken ausgibt. Wer allein arbeitet, braucht überhaupt keine Benachrichtigung: Dann ist die Liste der geänderten Seiten im Programm selbst die Arbeitsliste.
• Ohne GitHub. Ein Watch ist eine kleine Datei. Wer für sich mappt, hält die Dateien einfach lokal. GitHub kauft drei Dinge dazu, die erst zählen, wenn mehr als eine Person mitmacht: ein Review vor dem Scharfschalten, eine automatische Prüfung jedes Vorschlags und den Weg für Leute, die kein Repository anfassen wollen.

Nach oben ist genauso offen. Das Gebiet steckt im Kategorie-Tag jedes Eintrags (fulda-bakery), also können mehrere Orte in derselben Instanz liegen, ohne sich zu vermischen, und die Erkennung von Wochentagen und Zeitformaten ist eine eigene kleine Datei, die weitere Sprachen aufnimmt. Ob daraus 60 Watches für einen Landkreis werden oder ein paar tausend für ein Bundesland, ändert am Aufbau nichts, nur an der Frage, wer die Alarme liest.

Nachbauen

Alles liegt offen, GPL-3.0. Das Handwerk steht in eigenen Dokumenten und auf Englisch, damit eine andere Stadt damit anfangen kann: wie man den Zeitenblock einer Seite findet, woran man merkt, dass der Filter den falschen erwischt hat, und warum ein Watch eine Datei ist und kein Formular. Was zum Mitmachen nötig ist, steht auf Deutsch.

Wer in Fulda einen Betrieb kennt, dessen Zeiten in OSM veraltet sind: Das Issue-Formular liegt offen, und der Bot antwortet schneller als jeder Maintainer.

https://github.com/osm-fulda/oeffnungszeiten

Sou um usuário novo, e desde que comecei a editar locais que conheço, acabei não lendo a guia de direitos de autor, onde indica-se que sites como Google não deverão ser usados para preencher informações. Acabei cometendo esse erro, e peço minhas sinceiras desculpas pelos erros que cometi. A partir de agora, estarei usando os sites oficiais do município e os sites oficiais das instituições e prédios que irei adicionar, junto com fotos aéreas e, se eu puder, visitarei esses lugares.

I sincerely apologize for my lack of reading the guide for this website when I shouldn’t use sites related to Google. I’m lazy at first when I tried to use the site for the first time. Especially for mapping broadcast stations, and missing barangays for like 9 months now.

:/

hola esta app me servira para hacer seguimiento a un celular?

In 2026, the question is no longer really:

“Can OpenStreetMap truly be used professionally?”

State of the Map 2026 in Paris once again showed that this question has largely been settled.

OSM now serves as the foundation for national reference datasets, is influencing European standardisation work on cycling infrastructure, supports research into data quality, and is part of an increasingly structured professional ecosystem.

Around it, other digital commons are also emerging, such as Panoramax.

At the same time, some talks reminded us of something essential: behind tags, ontologies and data pipelines, a map remains a representation of the world — and therefore the result of choices.

A few reflections, with a cycling-data bias, after three days at #SOTM2026 at Géodata Paris 👇

(french version here)

State of the Map Paris 2026: OpenStreetMap is scaling up

For the first time, the global State of the Map conference took place in France, from August 28 to 30, 2026, in Champs-sur-Marne, near Paris.

The location itself felt quite symbolic. The international OpenStreetMap community gathered at Cité Descartes, including at Géodata Paris, IGN’s school, alongside École nationale des ponts et chaussées and Université Gustave Eiffel.

For three days, contributors, researchers, public authorities, institutions, associations and companies met in a place dedicated to education, research and new uses of geographic data.

This connection between OSM, academia, research, public institutions and professional geodata users actually sums up quite well what I took away from this edition.

A few days after SOTM 2026, one impression stands out:

OpenStreetMap is scaling up.

Of course, OSM has long ceased to be merely “a collaborative map” sitting on the margins of large private or governmental mapping platforms.

But this year’s conference showed particularly clearly how deeply the project is now embedded in professional applications, research, public policy and even standardisation work.

And it was particularly interesting to see this evolution taking place at IGN.

IGN was not only one of the event’s partners. Several topics discussed during the conference — including Panoramax, digital commons and the relationship between institutional datasets and OpenStreetMap — also illustrate a deeper evolution in the relationship between the French institutional geographic ecosystem and OSM.

A few years ago, IGN and OpenStreetMap could easily have been portrayed as two separate, perhaps even competing, worlds. I have quite vivid memories of this opposition from when I studied here myself.

SOTM 2026 told a rather different story:

one of complementarity, commons and collaboration.

Among the many talks, a few topics particularly caught my attention.

OSM is starting to inspire cycling standards

The presentation “How OSM inspires CEN standards for cycling infrastructure”, by Tu-Tho Thai, sent a strong signal.

As part of European work on the digital description of cycling infrastructure, the Cyclinfra project is examining OpenStreetMap tags and mapping practices.

OSM is therefore no longer simply adapting itself to institutional standards.

It is also starting to inspire them.

France’s Base Nationale des Aménagements Cyclables (BNAC) — the National Cycling Infrastructure Database — follows a similar approach: using OSM as a source, transforming the data into a national data schema, and enabling public authorities to improve the shared OSM dataset in return.

For cycling, this convergence between OSM, national datasets and European standards is particularly promising.

It is also very close to what we have been promoting within the Geodata team at Geovelo.

When mapping a pothole becomes political

The discussions around “The democratic stakes of mapmaking”, with Ksenia Ermoshina, Christian Quest and Françoise Bahoken among others, were a useful reminder of something that is often overlooked:

Mapping is a political act.

A simple example illustrates this well.

Mapping potholes or problems in public space may seem trivial. But making those issues visible also makes it possible to assess public policies and helps residents organise or advocate for improvements.

Choosing what we represent, what we describe, and what we leave invisible is already a decision.

Technical choices in a database or a map are therefore never entirely neutral.

Panoramax: a new geographic common

Panoramax was also highly visible throughout the conference — starting right from the opening session.

That was particularly satisfying for us at Geovelo, as we helped fund the first viewer back in 2021, when the project was still called GeoVisio.

Panoramax provides a free, open and federated alternative for sharing street-level imagery.

Its value is not only in the photographs themselves.

Its architecture is equally important: multiple organisations can host their own imagery while remaining connected through a common federation.

Like OpenStreetMap, Panoramax demonstrates that it is possible to build an open, decentralised geographic infrastructure that does not depend on a single provider.

The French Federation of OSM Professionals is helping structure the ecosystem

The French Federation of OpenStreetMap Professionals, of which Geovelo is a member, was also very visible during the event: through its booth, talks, discussions with participants and an OpenStreetMap TV studio.

This reflects another important evolution.

Over the past few years, a genuine professional ecosystem has been developing around OpenStreetMap.

The Federation brings together companies and professionals working in mobility, accessibility, energy, urban planning, tourism, GIS tools, data quality and other fields.

Its purpose is not simply to represent businesses using OSM.

It also builds bridges with public authorities, explains the ODbL licence, documents professional uses of OSM and advocates for the commons-based model.

We also followed several more technical and applied-research topics.

Making OSM easier to use

Jake Low’s presentation “Sourdough and Layercake” addressed another major challenge: OpenStreetMap’s complexity.

Sourdough provides vector tiles that remain close to the logic of OSM tags.

Layercake transforms OSM data into thematic layers, including in GeoParquet format.

The objective is straightforward: allow more people to work with OSM data in tools such as QGIS, DuckDB or notebooks without first having to master the full complexity of PBF files, relations and tagging conventions.

Making OSM easier to access without losing the connection to the original data is probably one of the major challenges facing the ecosystem.

Understanding changes in OpenStreetMap

The work presented by Camille Bernard and Pedro Pinheiro focused on detecting and semantically annotating changes in OpenStreetMap.

Their research was presented as:

Bernard, C., Pinheiro, P., & Viry, M. (2026). Detection and Semantic Annotation of Changes in OpenStreetMap Data. OSM Science 2026 at State of the Map 2026.

Detecting that an object has changed is relatively easy.

Understanding why it changed is much harder.

Imagine that a cycleway suddenly appears in OSM.

Was the infrastructure actually just built?

Was it already present on the ground but had never been mapped?

Was it simply a tagging correction?

Or a geometry improvement?

Being able to distinguish between these situations is essential when analysing how a territory evolves.

This is something we will be following closely.

Comparing the number of kilometres of cycleways in OSM between two dates is not enough. We need to distinguish changes in the real world from changes in how the real world is represented in OSM.

OSM is no longer just a map

Although, to be fair, it probably never was.

All these examples tell a similar story:

• Panoramax is building a new commons around street-level imagery.
• Sourdough and Layercake are making OSM data easier to use.
• The Federation of OSM Professionals is helping structure an economic ecosystem while building bridges with public institutions.
• Research is helping us better understand how OSM data evolves.
• European cycling standards are beginning to learn from OpenStreetMap.
• Discussions about mapping remind us that technical choices can also have democratic consequences.

The question is therefore no longer really whether OpenStreetMap can be used professionally or institutionally.

That has already been answered.

The more interesting questions are now:

• How do we industrialise without closing things down?

• How do we standardise without oversimplifying?

• How do we professionalise without taking ownership away from the community?

That is what I will remember from State of the Map 2026 in Paris.

OpenStreetMap is no longer simply a map that we improve feature by feature.

It is an infrastructure and a digital common around which tools, companies, standards, research and public policies are now being built.

Geovelo at SOTM 2026

We also contributed two presentations during the conference:

• Geovelo & cycling infrastructure, a discussion in the SOTM TV studio, in French.
• “How OpenStreetMap became the backbone of France’s National Cycling Database”, presenting the history of the BNAC and making the case for the relationship between institutional cycling data and OpenStreetMap.

A busy State of the Map, and plenty of ideas to bring home.

See you at the next one!

in-browser editor

##JOSM ###Potlatch ####Merkaartor

History Export ***GPS Traces **User Diaries ***Communities **Copyright **Help ****Donate *******About

1. United States
2. Kentucky

[kramdown](https://kramdown.gettalong.org/quickref.html

37 Degrees North & -85 Degrees West

Das Vernetzungstreffen des FOSSGIS e.V. hat am 02.09.2026 mit 25 Teilnehmenden in der Netzwerkwelt stattgefunden. Die Idee ist, das gegenseitige Kennenlernen und gemeinsamer Austausch zu Anliegen und Themen. Menschen im Umfeld des FOSSGIS-Vereins erhalten Gelegenheit Kontaktpunkte zu finden. Viele Teilnehmende waren schon beim letzten Mal dabei und kannten sich in der Benutzung der Netzwerkwelt aus.

Eindrücke vom Treffen, Start im FOSSGISeV-Raum

Spannende Themen im Austausch

Zu Beginn trafen sich alle Teilnehmenden im Raum FOSSGIS e.V. für einen gemeinsamen Einstieg und um den Ablauf der Veranstaltung miteinander zu teilen. Vier Räume waren thematisch vorgeplant.

Die Idee der Vernetzung im Bereich Blaulicht/BOS/Gefahrenabwehr wurde von Jana Thomas und Mirco Schindler weiter vorangetrieben. Es wurden konkrete Schritte bsprochen, um eine Arbeitsgruppe im FOSSGIS e.V. zu gründen. Die Gruppe hat schon eine eigne Mailingliste sowie erste Ideen für den Namen und was erreicht werden möchte.
Auf der SOTM 2026, die Ande August in Paris stattgefunden hat, gab es einen Vortrag passend zum Thema, “Emergency Services using OpenStreetMap in Germany”.

Der diesjährige Geodaten-Hackathon (#hack4GDI_DE) findet vom 13. - 14.11.2026 an der Hochschule Mainz statt. Die Challenge 2 zum Thema Flächenentsiegelung & Schwammstadt wird von Emmanuel Tobey gestaltet. Um den Einstieg zu erleichtern, nutzte Emmanuel das Vernetzungstreffen. Die Gruppe formulierte eine Wikianleitung für einen FOSS-Einstieg beim Hackathon und tauschte sich zum Umsetzungskonzeot aus. Details & Anmeldung zum Geodaten-Hackathon sind auf den Webseiten der GDI-DE zu finden.

Das Thema KI und heterogene Geodaten treibt nicht nur Johannes Lauer um. In der Gruppe geht es um die Frage, kann KI bei heterogenen Geodatenbeständen helfen? Welche Tools gibt es? Welche Use Cases haben sie Teilnehmenden? Als Usecases wurden Softwareentwicklung, Landoberflächenklassifikation oder der Support für non-GIS-Experts und weitere besprochen. Vor- und Nachteile von KI-Nutzung waren Thema, beispielsweise haben die Repo-Betreiber Codeberg e.V. eine Entscheidung zum Schutz der FLOSS-Commons vor LLMs getroffen und hier aufgeschrieben, die CivicDataLab Community hat ein selbst gehostetes KI-Tool auf den Weg gebracht. Das Thema wird beim nächsten Vernetzungstreffen fortgesetzt.

Im Themenraum Praxisbeispiel QGIS-(Analyse-)Werkzeuge stellte Anja Eisert das Sichtbarkeitsanalysetool Visibility Analysis vor. Im Anschluss tauschten sich die Teilnehmenden allgemein zu QGIS-Tools und PlugIns sowie über Weiterbildungsmöglichkeiten und Jobperspektiven aus.

Das Treffen in der Netzwerkwelt hat auf Basis von Workadventure stattgefunden. In der Netzwerkwelt ist die Interaktion von Teilnehmenden möglich, man ist mit einem Avatar unterwegs, gibt sich beim Eintreten einen Namen. Trifft man eine andere Person, öffnet sich ein Videochat, eine Unterhaltung ist bis maximal 4 Teilnehmende möglich. Die Räume (Inselchen) sind Videokonferenzräume, man tritt einem Jitsi-Videochat bei, dort fanden die Austauschrunden statt. Vielen Dank an Stella fürs Bauen der Netzwerkwelt und danke den FOSSGIS e.V. für die Unterstützung des Treffens mit den Entgelt an die Betreiber der Plattform.

Abschluss und Feedback

Abschluss und Feedback

Die Rückmeldungen waren durchweg positiv, die Teilnehmenden kommen wieder und wollen sich weiter über verschiedene Themen austauschen.

Das nächste Vernetzungstreffen am 09.12.2026 wird wieder ab 17:30 Uhr in der Netzwerkwelt starten, um entspanntes Ankommen, ersten Austausch und einen gemeinsamen Beginn um 18 Uhr zu gewährleisten.

Folgende Themen wurden gewünscht und werden voraussichtlich angeboten:

• Fortsetzung Vernetzung BOS/Gefahrenabwehr (Jana + Mirco)
• Beispiele aus der Praxis: QGIS, QGIS Layertool, ArCGIS2QGIS (Anja E., Christian S.)
• Fortsetzung Raumes zu KI und Geodaten, da die Entwicklung so schnell geht, dass regelmäßiger Austausch sinnvoll erscheint (Johannes L.)
• Konzepte studentischer Vernetzung (David.stud)

Wer Interesse hat einen Raum anzubieten, meldet sich bitte vorab bei Katja oder per mail an socialmedia@fossgis.de.

Infos aus dem Verein

Die Aktivitäten des Vereins sind im FOSSGIS-Vereins-Kalender zu finden.

Vom 9.-13-03.2027 findet die FOSSGIS-Konferenz 2027 in Heidelberg statt. Erste Infos sind auf der Konferenzhomepage veröffentlicht, Beitragseinreichungen sind im Rahmen des Call for Participation vom 01.10. bis 01.11.2026 und die Anmeldung ist ab Januar 2027 möglich.

JETZT OSM-Förderer werden und die digitale Souveränität stärken!: https://openstreetmap.de/foerderer/

Das aktuelle Projekt: OSM-Schulungen, gefördert durch die DSEE (transform_D) läuft noch bis Ende 2027. Die Idee ist Schulungsmodule mit Inhalten zu entwickeln. Eine Arbeitsgruppe begleitet den Entwicklungsprozess inhaltlich, erste Schulungen werden zu Beginn 2027 stattfinden. Für die Organisation der Schulungen in der Koordinierungsstelle des FOSSGIS e.V. kommt ab 01.10.2026 eine neue Kollegin.

Das wichtigste zuletzt: Der FOSSGIS-Verein sucht einen Schatzmeister, die Position ist derzeit bis zur nächsten Mitgliederversammlung mit Wahl komissarisch zu besetzen.

Manchmal zoome ich in einen zufälligen Bereich hinein, sehe, dass ein Bereich komplett ungemappt ist, und verbringe dann die nächste Stunde damit, jedes kleine Detail zu erfassen, das ich sehen kann. OpenStreetMap bearbeiten macht süchtig.

27/08/2026-02/09/2026

Mapping campaigns

• Hiki introduced the Deutsche Bahn Metadata Cleanup project, an effort to improve the quality of OpenStreetMap data around German railway stations.
• Denmark’s OpenStreetMap community has made mapping accessible parking spaces its September 2026 project, encouraging contributors to survey and add missing spaces nationwide to improve the country’s free accessibility data.

Community

• Bigbug21 blogged on the current state of defibrillator mapping in OpenStreetMap, concluding that much has been achieved, but there is still plenty of work to be done.
• While attending State of the Map 2026, Juminet noticed a decline in the influence of big tech companies within OpenStreetMap, suggesting a shift back toward the volunteer contributions that formed the heart of the project in its early days. This contrasted with his experience at State of the Map 2018, when major technology companies were investing heavily in OpenStreetMap mapping.
• Anne-Karoline Distel showed how to map disused fish weirs on OpenStreetMap.
• Rawaz has mapped population data from Iraq’s 2024 census onto OSM administrative boundaries, covering admin levels 2 through 6.
• rphyrin praised Stylus Labs Maps after SotM 2026 as the best mobile OpenStreetMap vector map app they have tried.
• rphyrin plans to share his experiences from attending the global State of the Map 2026 online. He is still writing about the first day, with the remaining days a work in progress.
• Vishal Kumar shared several insights on the role of AI in mapping, from State of the Map US 2026, held 11 to 13 June.

Local chapter news

• OpenStreetMap US has published its August 2026 monthly newsletter, featuring the OSM US team heading to Paris for State of the Map 2026, an upcoming September Mappy Hour in collaboration with Foursquare, and the announcement of its newest Charter Project, OldInsuranceMaps.

Events

• [1] Volker Krause wrote about his attendance at SotM 2026 in Paris.
• A 360° version of the SotM2026 group photo is now online on Panoramax!
• The official PeerTube channel of State of the Map 2026 can be found here.
• Muki Haklay has shared his impressions of attending State of the Map 2026 in Paris. Muki, Professor of Geographical Information Science at the UCL Department of Geography, won the IEEE Pervasive Computing’s Test of Time Award for his 2008 paper on OpenStreetMap.

Education

• Lucy Kago reported, as a UN Mappers’ ambassador, that UN Mappers Kenya has completed its first ever Youth Climate Mapping Externship, a seven-week virtual programme designed to equip young Kenyans with real geospatial tools and apply them to climate challenges in Nairobi. Nineteen university students participated in the programme. The initiative had the support of IVIDES DATA (as a full sponsor), GeoMind Solutions and Geospatial Developers (as technical partners), and Community Mappers Kibera (as community partner). You can see the results on the UN Mappers’ blog.

Humanitarian OSM

• HOTOSM interviewed the CoMaps team about how the app was used to help rescuers after the earthquakes in Venezuela.

Maps

• Cody Blatt has created DepthScout, a depth-mapping platform designed to aid fishing, which uses shoreline data from OpenStreetMap.
• Map4 has released a free trial version, limited to 50 queries per day, of their US telecom fibre intelligence dashboard, built on top of OpenStreetMap basemap data.
• The Plataforma latinoamericana y del caribe por la justicia climática (Latin American and Caribbean platform for climate justice) maintains ► a uMap for mapping ‘false solutions’ to the climate crisis, those which claim to advance the protection of the planet and its inhabitants through approaches that include deception, technical shortcomings, so-called technological innovation, and rhetoric but which perpetuate consumption and the hoarding of wealth as we know it. The initiative is a collaboration ► of organisations from 15 Latin American countries.

OSM in action

• The California Ocean and Coastal Monitoring Inventory is an interactive dashboard of ocean and coastal monitoring programmes operating within 12 nautical miles of the California coast, using basemap data from OpenStreetMap.

Open Data

• The Leibniz Supercomputing Centre tooted that it is making its archive of Landsat data accessible ►, with support from the Technical University of Munich and the German Aerospace Centre.

Software

• Ashuttl has made linecast, a free open-source collection of terminal apps for weather, radar, sunshine, moon data, tides, and maps that uses public data sources including OpenStreetMap-derived vector data.
• Inspired by a recent Mapterhorn talk at State of the Map 2026, rphyrin has developed a web app that accepts coordinates pasted from JOSM and displays an interactive 3D terrain visualisation. The app can help JOSM users better understand the three-dimensional geographic context of the area they are currently mapping.

Programming

• Developer NameError has built Draw.city, a US geography game where players draw circles on a map to estimate populations and explore census demographics and OpenStreetMap points of interest.
• rphyrin has experimented with Sourdough to build a mobile-friendly vector map that treats roads uniformly and prioritises displaying as many mapped points of interest as possible, especially at high zoom levels.
• An agentic bot (Claude Code) ‘explained’ ‘its’ approach to filling in Belgium’s national secondary road route relations on OpenStreetMap in an OSM Diary entry. The community’s response to the edits can be judged from the posts in the OSM Community forum thread.

Did you know that …

• … a curated collection of all European E-roads, an international network of major roads connecting countries across Europe, is mapped in OSM?

Other “geo” things

• Natsuhei Eno, a Senior Policy Officer at the Tokyo Foundation, published an article on the Foundation’s blog discussing what supports regional information infrastructure. Featuring Associate Professor Yasuyuki Matsumoto , of Setsunan University, who researches civic activities using OpenStreetMap and Wikipedia (such as Wikipedia Town and mapping parties), the article highlighted the importance of citizens participating not merely as recipients but as contributors to local information.
• Ryan Christoffel reported that Apple Maps is now showing advertisements to their customers; they will appear both as suggested places in the map and in the search result list with a little blue ‘ad’ text next to them.
• Kaio Bárbara has developed climateBR, a software package that provides tools for downloading, processing, and analysing historical meteorological data from Brazil’s National Institute of Meteorology.
• Science Daily reported that NASA has successfully tested a system that allows satellites to navigate without GNSS by using other spacecraft and debris as landmarks in orbit.
• Neha Arora and Aboudy Kreidieh, of Google Research, reported that coordinating a small fraction of navigation routes in Google Maps can measurably improve driving speeds and reduce emissions across an entire city.

Upcoming Events

Country	Where	Venue	What	When
	नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2026-09-05
	大阪市	中崎町ホール Nakazakicho HALL, Salon de AmanTo天人 (Osaka)	State of the Map Asia 2026	2026-09-06 – 2026-09-07
	臺北市	MozSpace Taipei	OpenStreetMap x Wikidata Taipei #92	2026-09-07
	Madrid	Online	Mappy Hour OSM España	2026-09-08
	Braunschweig	Stratum 0	Braunschweiger Mappertreffen im Stratum 0 Hackerspace	2026-09-08
	Hamburg	Voraussichtlich: “Variable”, Karolinenstraße 23	Hamburger Mappertreffen	2026-09-08
		temporärhaus	OSM-Stammtisch Ulm/Neu-Ulm	2026-09-08
	Tours	Étape 84	Rencontre locale de Touraine	2026-09-09
	Berlin	Kastanienallee 7-9, 10435 Berlin	219. OSM-Stammtisch Berlin-Brandenburg	2026-09-10
	München	WikiMUC	Münchner OSM-Treffen	2026-09-10
	Bochum	Das Labor, Alleestraße 50, Bochum	OSM-Treffen Bochum	2026-09-10
	Zürich		191. OSM-Stammtisch Zürich	2026-09-11
	København	Cafe Bevar’s	OSMmapperCPH	2026-09-13
	Delhi	Too Mikki Tapas, South Extension	OSM Delhi Mapping Party No.32 (South Extension)	2026-09-13
	Greater London	1 Cabot Square, 7th Floor, Canary Wharf E14 4QJ	EAW Volunteering Event	2026-09-14
			CartONG : Mapathons en ligne 2026-2027	2026-09-14
			Missing Maps London Mid-Month for Advanced Mappers (no training provided) (Online) [eng]	2026-09-15
	San Francisco	Near BART 24th St. Mission station	Bay Area WikiSalon	2026-09-15
	Lyon	Tubà	Réunion du groupe local de Lyon	2026-09-15
	San Jose	Online	South Bay Map Night	2026-09-15
	Chemnitz	Kaffeesatz, Chemnitz	OSM-Stammtisch Chemnitz	2026-09-15
	Bonn	Dotty’s	204. OSM-Stammtisch Bonn	2026-09-15
	Stainach-Pürgg	Online	22. Österreichischer OSM-Stammtisch (online)	2026-09-15
		Online	Lüneburger Mappertreffen (online)	2026-09-15
	St. Gallen	Rosenbergstrasse 59, 9000 St.Gallen	Map The Climate! Ein Mapathon	2026-09-16
	Köln	Lokal K, Hackländer Straße 2, Köln-Ehrenfeld	OSM Stammtisch Köln	2026-09-16
	Nantes		COntrib’atelier	2026-09-16
		MJC de vienne	Réunion du groupe local de Vienne	2026-09-16
	Kiel	Kieler Innovations- und Technologiezentrum	OSM auf der Kielux 2026	2026-09-18 – 2026-09-19

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 MarcoR, MatthiasMatthias, Raquel Dezidério Souto, Strubbl, Andrew Davidson, barefootstache, derFred, mcliquid.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

So, during my career, I discovered OpenStreetMap. While editing, I used Google Maps and Street View, and I shouldn’t have read the guide, which is not allowed on this site, especially when adding missing barangays.

Whoops. :/

Created account, Labor Day Weekend

good things compared to yesterday: no rain!!

bad things: nearly 30°C outside and So. Many. Bees. okay it wasn’t as many as i make it sound like but i am admittedly afraid of bees. not a great time

ANYWAY. i went and finished the side of thames street that i started yesterday, then did the other half on the way home. so im pretty sure ive accounted for almost everything on that street now! so i guess next on the list is the side streets. hopefully we get some days that are nice and cool so i dont suffer doing this haha

El Grupo de Usuarios de GNU/Linux de La Laguna celebrará un aniversario más y estaré participando con una conferencia y un taller de OpenStreetMap.

Se efectuará en la Universidad Tecnológica de Torreón el 25 de septiembre desde las 9:00 horas con conferencias y talleres.

La Conferencia

En la conferencia OpenStreetMap: Datos abiertos y más se enseñará al público asistente qué es OpenStreetMap (OSM), qué son los datos abiertos y cómo y por qué usar ambos ya sea en nuestros trabajos, en nuestra comunidad y, principalmente, en nuestra vida diaria.

El Taller de mapeo

En el taller Mapeando mi entorno se enseñará al público asistente a usar OpenStreetMap (OSM) para que puedan agregar a un mapa libre elementos que pueden enriquecer el mapa para todos quienes lo usamos.

Espero que todas las personas que conozcan y les interese el Software Libre nos puedan acompañar el 25 de septiembre desde las 9:00 horas.

Recuerden: 😃🐧 ¡La entrada es Libre, solo tienen que registarse aquí! 😃🐧

最近大阪市鶴見区内をマッピングしていますが、大体の建物の造形が実際と違ったり更地になってたり。近々修正などを始めるかな〜とか思ってのんびりしていますが、先に登録できそうな表示版だったり店舗などが全く進んでいなかったりと時間とやる気不足気味のためある程度の網羅はまだまだ先になりそうかもしれません。

そして関係ないですが最近鼻水が止まりません。ティッシュが足りない…。 もう一つどうでもいいことですが どうやってもこれ開くとGPUプロセスが飛ぶのですが…開ける方いませんか?

Hi everyone! I have been trying to edit some locations but the changeset size is exceeded (cause i forgot to upload after moving to the other country). I have no idea which nodes are from Portugal and which from Italy. Can someone help?

Thank you so much in advance

<?xml version=”1.0” encoding=”UTF-8”?>

قمت بإضافة مساهمات أحياء سكنيه جديده في منطقتي قمت بإضافة مساهمات أماكن عباده كنائس ومساجد في منطقتي قمت بتنظيف مساهمات بالفعل هي ليست موجوده والبعض منها غير موجود ومكرر وليس له أي أساس في وجوده ويضلل مستخدمين الخريطه،لذالك قمت بتنظيف الخريطه منها

انتظر بفارغ الصبر مزامنة مابس مي مع osm لان مابس مي من البرامج الأكثر استخدام في منطقتي بالعلم اني استخدم اورجانيك وكومباس ايضاً لأني أحب الخريطه اشكر الجميع اتمنى الخير لكل المجتمع في osm

بيت

got out of the house for a bit today and got started adding/removing some businesses on thames street south, and adding info like hours and contacts to ones that were already there. headed home when it started raining but i feel like i got a pretty good amount done for one walk.

i only really focused on one side of the street to start, i was gonna do the other side on the way home but due to the rain ive just left it for another time. here’s to better weather this week 💜💜

Обеспечение загородного участка автономным водоснабжением — первоочередная задача для любого землевладельца. Традиционно для решения этой проблемы применяется крупногабаритная буровая техника на базе грузовых автомобилей (ЗиЛ, УРАЛ, КамАЗ). Однако на практике буровые бригады часто сталкиваются с объективными препятствиями: плотная застройка, наличие ухоженных газонов, проложенные подземные коммуникации, узкие ворота или линии электропередач, исключающие возможность подъезда и разворота тяжелых машин.

В таких условиях оптимальным выходом становится использование малогабаритных буровых установок (МГБУ). Они позволяют проводить работы в стесненных условиях без ущерба для окружающего ландшафта. При этом гидрогеологические условия Александровского района Владимирской области отличаются крайней неоднородностью и сложностью разреза. Из-за этого применение малых технических средств возможно далеко не везде. Перед началом работ важно детально изучить специфику местных грунтов и водоносных слоев.

Важное примечание: Все приведенные ниже цифровые показатели глубин залегания водоносных горизонтов носят ориентировочный и обобщенный характер. Для получения точной информации и составления достоверного прогноза необходимо консультироваться со специалистами по каждому конкретному адресу.

Полезные ссылки про бурение на воду малыми установками:

• Большой обзор про бурение скважин малогабаритными установками на примере установки Гидробур Г1.

• Новые записи в нашем дневнике про бурение водозаборных скважин на проекте ОпенСтритМеп

Виды малогабаритной буровой техники

Современный рынок МГБУ предлагает несколько модификаций оборудования, каждая из которых имеет свои технические ограничения, габариты и область эффективного применения:

Разборные буровые установки

Представляют собой модульные металлические конструкции (переносные рамы), которые собираются непосредственно на точке бурения. Область применения: Бурение неглубоких скважин на песок (включая абиссинские колодцы) в самых труднодоступных местах, подвалах зданий или закрытых павильонах.

Ширина подъездных путей: Специальные пути не требуются. Элементы конструкции переносятся вручную через стандартные калитки шириной от 0,8 метра.

Габариты рабочей площадки: Минимальное пространство составляет около 2х2 метра при высоте потолка/навеса не менее 2,5–3 метров.

Буровые станки малогабаритные на колесном ходу

Компактные установки, смонтированные на базе прицепов для легковых автомобилей или самоходных колесных шасси.

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

Ширина подъездных путей: Для проезда требуется коридор шириной не менее 1,2–1,5 метров.

Габариты рабочей площадки: Для безопасного развертывания мачты и размещения сопутствующего оборудования необходима площадка размером от 3х4 метра.

Буровые малые станки на гусеничном ходу

Самоходные мини-установки на резиновом или металлическом гусеничном ходу, обладающие повышенной проходимостью и мощностью. Область применения: Бурение глубоких эксплуатационных скважин на межпластовые воды (включая известняк) на участках со сложным рельефом или мягким грунтом. Резиновые гусеницы минимизируют повреждение верхнего слоя почвы.

Ширина подъездных путей: Требуется проезд шириной от 1,5 до 1,8 метров. Габариты рабочей площадки: Оптимальная рабочая зона составляет около 4х5 метров с учетом места для бурового раствора и инструмента.

Что еще интересного почитать про подземные воды Владимирской области:

• Выход подземных вод на поверхность через Родник на улице Мира

Гидрогеологические особенности Каринского сельского поселения

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

На данной территории с высокой степенью вероятности можно оборудовать классические фильтровые скважины на песок под погружной насос. Местами встречаются обильные песчаные линзы с высоким уровнем залегания подземных вод, что позволяет обустраивать так называемые абиссинские иглы (забивные колодцы). В этих слоях формируются безнапорные грунтовые воды, доступные для легкого инструмента.

Тем не менее ключевым фактором успеха выступает геоморфология. Необходимо обязательно учитывать абсолютные высоты над уровнем моря. На возвышенностях и водораздельных плато глубина залегания обводненных песков существенно увеличивается, а верхние горизонты могут оказаться сухими или содержать лишь сезонную верховодку. В таких высоких точках вероятность успешного применения легких разборных МГБУ заметно снижается, и может потребоваться переход на более мощную гусеничную технику.

Гидрогеология Следневского сельского поселения

В Следневском сельском поселении гидрогеологическая обстановка усложняется. Хотя здесь также сохраняется принципиальная возможность бурения малогабаритными установками как под погружной насос, так и под абиссинские скважины, общая вероятность стабильного дебита на малых глубинах чуть ниже, чем в Каринском. Основные запасы чистой воды приурочены к межпластовым водоносным горизонтам, перекрытым сверху толщей моренных суглинков. При планировании работ важно учитывать следующие региональные особенности:

• Зависимость от рельефа. Как и в соседних зонах, отметки высот над уровнем моря диктуют глубину залегания стабильных водных пластов. На локальных возвышенностях маломощная техника может не дойти до обводненной породы.

• Каменистые включения. В ряде населенных пунктов поселения разрезы содержат плотные моренные отложения с обилием валунов, крупных камней и галечника. Прохождение таких интервалов легким инструментом МГБУ часто становится технически невозможным из-за заклинивания бурового снаряда. В подобных зонах эффективно отработать способна исключительно крупногабаритная техника с тяжелым ударно-канатным или мощным роторным инструментом.

• Географический градиент. При приближении к границам Ярославской области гидрогеологические условия закономерно ухудшаются: песчаные водоносы истощаются, замещаются глинистыми фракциями, а глубина залегания коренных водоносных пород растет. В связи с этим шансы на успешное применение малых установок при движении на север и северо-восток Следневского поселения стремительно падают.

Гидрогеологические условия Андреевского сельского поселения

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

Верховодка в Андреевском поселении крайне нестабильна и сильно зависит от количества осадков, поэтому ориентироваться на нее при создании долговечного источника водоснабжения нельзя. Грунтовые воды часто характеризуются повышенным содержанием соединений железа и органики из-за близкого залегания юрских глинистых водоупоров.

Шансы пробурить надежную песчаную скважину с помощью МГБУ колеблются от средних до низких в зависимости от конкретной деревни. Использование разборных профильных рам оправдано только на пониженных рельефах и в поймах рек. На средних и высоких геодезических отметках бурение на песок часто превращается в разведочное, не приносящее результата. Для гарантированного получения воды приходится ориентироваться на более глубокие межпластовые воды, залегающие под юрскими глинами (в диапазонах, которые могут достигать 50–75 метров и более). Проходка таких глубин по плотным глинам требует от малогабаритной техники высокого крутящего момента и обязательного использования качественных буровых растворов.

Гидрогеологические особенности в Краснопламенском сельском поселении

Краснопламенское сельское поселение признано наиболее сложным сектором Александровского района с точки зрения автономного водоснабжения. Здесь фиксируются самые низкие шансы на успешную эксплуатацию стандартных малогабаритных буровых установок.

Главная причина кроется в специфике геологического строения:

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

• Сложные, непредсказуемые разрезы. Мощные толщи плотных моренных суглинков чередуются с валунно-галечниковыми интервалами и сухими мелкозернистыми песками, которые склонны к осыпанию и создают эффект «плывуна». Такие условия требуют постоянного крепления ствола скважины обсадными трубами в процессе проходки.

На территории Краснопламенского поселения использование МГБУ невозможно планировать вслепую или на основе усредненных районных карт. Возможность применения малой техники необходимо проверять индивидуально, с точностью до конкретного адреса в населенном пункте. Даже на соседних участках в пределах одной деревни гидрогеологический разрез может кардинально отличаться.

Полезные советы по бурению малой техникой в Александровском районе

Малогабаритные буровые установки — это эффективный и щадящий инструмент для решения задач водоснабжения, незаменимый в условиях плотной застройки Александровского района. Однако сложная гидрогеология региона, обусловленная ледниковым происхождением местных рельефов, накладывает строгие ограничения на их использование. В то время как в Каринском поселении шансы на успех легкой техники весьма велики, в Следневском и Андреевском они требуют учета каменистых включений и высотных отметок, а в Краснопламенском сводятся к минимуму.

Для получения точного прогноза и исключения финансовых потерь на бесперспективную разведку настоятельно рекомендуется перед началом работ проконсультироваться у нескольких независимых буровых бригад. При обращении обязательно указывайте точные географические координаты или адрес участка. Опытные мастера, регулярно работающие в Александровском районе, смогут трезво оценить реальные технологические лимиты своего оборудования, сопоставить их с архивными данными по соседним скважинам и дать четкий, обоснованный прогноз.

Soy nuevo espero pueda mejorar para seguir utilizando de manera adecuada esta app

OsmAnd 5.4 for Android is now available on the Google Play Store. Please update to the latest version to enjoy the new features and improvements.

At this release, we focused on improving the search experience, making it easier to find places and discover objects around a specific location. We also added the ability to attach media files to Favorites and Waypoints, making them more informative and useful for your travels.

🔄 Update Now!

Thanks to all our users for their feedback and suggestions. Your input is invaluable in helping us improve OsmAnd and make it the best navigation app for Android.

What's new​

• Refreshed search UI: sorting, category filters, cleaner look
• Attach photos and media to Favorites
• Favorites: subgroups support and pinnable folders
• New widgets appearance
• Roof shapes for 3D Buildings
• Coordinates: search, map grid, and POI display now support EPSG and Maidenhead locator
• Navigation settings improvements
• Android Auto updates
• Astronomy added solar & lunar eclipses
• AIS improvements
• New spatial search — find places and search around a place
• Others updates and improvements
• Bug fixes.

Refreshed search UI​

We introduced a refreshed Search interface designed to make finding places faster and easier.

You can now quickly choose where to search — around the Map Center or My Location — and select how results should be sorted: by Nearest or Relevance.

It is also easier to narrow down the results by selecting one or multiple POI categories, so you can focus only on the places you are interested in.

The updated interface makes Search more flexible, easier to understand, and faster to use.

History search and filtering​

The Search History menu now gives you more control over what is displayed.

You can filter history by item type and choose one or several categories:

• Tracks
• Locations
• Addresses
• POIs
• Favorites
• Photos
• Destinations

By default, all history items are shown.

You can also sort history by:

• Recent
• Nearest
• Nearest to Map Center

An additional Type filter lets you display:

• All
• Search
• Navigation

The History settings menu also includes an option to back up your history, helping you preserve your previous searches and navigation activity, make back up as file or clear all history.

Attach photos and media to Favorites​

We've made Favorites and Waypoints more informative by allowing you to attach media files directly to them.

Similar to the Audio/Video Notes feature, you can now add photos, videos, and audio notes to a saved Favorite or GPX Waypoint. You can take a new photo, record a video or audio note, or choose existing media from your device.

Attached files are displayed in a new Media section directly in the Favorite or Waypoint context menu, so photos and recordings connected to a place are easy to access when you need them.

This makes Favorites and Waypoints useful not only for saving a location, but also for keeping additional visual or audio information connected to that place.

Subgroups support and pinnable folders for Favorites​

Managing large collections of Favorites is now much easier.

Favorites can now be organized using folders and subfolders, similar to the folder structure already available for Tracks. This allows you to create a clear hierarchy instead of keeping all Favorite groups at the same level.

For example, you can organize places like this:

Netherlands / Amsterdam / Museums

or create even deeper folder structures when needed.

In My Places → Favorites, folders are displayed separately from individual Favorite points. You can create new folders, rename them, and move Favorites between folders and subfolders.

The full folder path is also shown where it is useful, including the Favorite context menu, making it easier to understand where a saved place belongs. For long folder structures, OsmAnd automatically shortens the path while keeping the most important folder names visible.

You can also pin important folders for quicker access to the Favorite groups you use most often.

The new hierarchy is supported when moving and exporting Favorites and works with OsmAnd Cloud synchronization, while preserving the existing file-based Favorites structure.

New widgets appearance​

We introduce new appearance settings for map widgets, giving you more control over how information is displayed on the map.

Instead of configuring widgets only individually, you can now customize the appearance of each widget panel — Left, Right, Top, and Bottom — from a dedicated Appearance screen.

For each panel, you can adjust:

• Widget or row size — Original, Small, Medium, or Large
• Widget icons — keep individual settings, show all, or hide all
• Text and secondary text colors
• Background color — Default, Transparent, or Custom

A live preview shows how the selected settings will look directly while you configure them.

For custom colors, Day and Night modes can be configured separately, helping keep widgets readable with different map styles and lighting conditions.

You can also copy appearance settings from another widget panel or another profile, making it easier to keep a consistent layout across different OsmAnd profiles.

Updated 3D Buildings​

OsmAnd 5.4 brings another major update to 3D Buildings, making cityscapes more detailed and closer to the real-world geometry stored in OpenStreetMap.

Buildings can now display different roof shapes instead of being rendered only as simple flat-topped volumes. When the corresponding roof information is available in OpenStreetMap, OsmAnd uses it to create a more recognizable building silhouette.

Rendering of complex buildings and building parts has also been improved. OsmAnd now handles structures divided into multiple building:part elements more accurately, including cases where only building:levels information is available instead of an explicit height.

We also improved the rendering of buildings created from relations and multipolygons, fixing cases where individual sections or lower parts of complex structures could be missing from the 3D model.

These changes make landmarks and detailed urban areas significantly more realistic when exploring the map in 3D.

To enable the feature, go to:

Menu → Configure map → Topography → 3D buildings

Coordinates EPSG systems​

We expand support for coordinate systems, making the app more useful for professional mapping, field work, surveying, amateur radio, and other activities that rely on specific coordinate formats.

You can now use EPSG coordinate systems and the Maidenhead Locator System across different parts of OsmAnd, including:

• Coordinate Search
• Map Grid
• POI and map context information

In Coordinate Search, you can select recently used formats or browse the full list of available coordinate systems. You can also quickly find the required system by searching for its name or EPSG code.

The Maidenhead Locator System is also supported on Android. It represents locations using a compact combination of letters and numbers and is commonly used by amateur radio operators.

Coordinate formats can be configured separately for each OsmAnd profile. You can choose a Primary coordinate format, add other formats to the list, reorder them, or remove formats you do not need.

Navigation settings improvements​

OsmAnd 5.4 improves navigation in situations where a route crosses regions with outdated or inconsistent offline maps.

Previously, route calculation could be interrupted by several dialogs asking you to update maps or manually continue using the downloaded maps. In some cases, this could even happen during route recalculation while navigation was already active.

Now, OsmAnd can handle these situations more smoothly. If the selected routing method cannot calculate the route correctly, the app can switch to an alternative calculation method and continue navigation without unnecessary interruptions.

You can also control this behaviour manually in:

Navigation settings → Route parameters → Route calculation method

Here, you can choose the preferred routing calculation method depending on your needs.

This makes route calculation more reliable when travelling across map borders or when not all downloaded maps were updated at the same time.

Android Auto updates​

OsmAnd 5.4 brings several improvements to Android Auto, making the search, and navigation experience more convenient on the car display.

More Useful Search Results​

Search results in Android Auto now show more information at a glance.

For POIs, OsmAnd can display opening hours in a compact format, together with distance and address information. This makes it easier to see whether a restaurant, shop, fuel station, or another place is currently open before selecting it as your destination.

Address presentation has also been simplified for nearby POIs, reducing unnecessary information on the limited Android Auto screen.

Improved Navigation Controls​

Navigation controls have also been refined. The X button next to the ETA now correctly stops the active navigation, making it easier to finish a trip directly from the Android Auto interface.

We also fixed interface issues on the arrival screen, including the duplicated Search button that could appear after reaching a destination.

Together, these changes make Android Auto cleaner and easier to use while keeping important map, search, and navigation information accessible on the road.

Astronomy added solar & lunar eclipses​

The Astronomy plugin continues to grow in OsmAnd 5.4 with new tools for exploring solar and lunar eclipses directly on the Star Map.

Solar Eclipses​

You can now explore solar eclipses around the world and see how an eclipse develops over time.

The new Solar Eclipse Explorer shows the eclipse shadow on the map and provides a timeline that you can move through to see how the event changes. Information is calculated for the selected location, making it possible to check whether and how the eclipse will be visible there.

You can also quickly switch between previous and next solar eclipses and explore their paths in different parts of the world.

Lunar Eclipses​

The Star Map now also includes a dedicated Lunar Eclipse Explorer, supporting:

• Penumbral eclipses
• Partial eclipses
• Total eclipses

The eclipse timeline shows the different stages of the event, while the visualization demonstrates how the Moon moves through the Earth's penumbra and umbra.

You can check the current eclipse phase, obscuration, Moon altitude, and where the eclipse is visible. A dedicated visibility layer on the map helps show the regions where the Moon is above the horizon during the event.

Together, these additions turn the Astronomy plugin into a useful tool not only for exploring stars and planets, but also for planning and observing upcoming eclipses.

AIS improvements​

OsmAnd 5.4 brings several improvements to the Vessel Tracker (AIS) plugin, making it easier to configure AIS connections and monitor nearby vessels.

The plugin settings have been reorganized into clearer sections for Connection, Object visibility, and Collision avoidance alarms (CPA).

You can configure AIS data reception using TCP or UDP, with connection information and status displayed directly in the interface.

New Object visibility settings give you more control over outdated AIS targets. You can define when a vessel should be marked as outdated and how long it should remain visible on the map after its signal is lost.

The Collision Avoidance Alarm (CPA) settings have also been redesigned. You can configure:

• Warning time (TCPA) — how far in advance OsmAnd should warn about a potential collision.
• Closest Point of Approach (CPA) — the minimum safe distance between your vessel and another AIS target.

When another vessel is predicted to come too close within the configured time, OsmAnd can highlight it as a potential collision risk.

AIS visibility can also be managed as a dedicated map layer through Configure Map, making it easier to enable or disable vessel information when needed.

New spatial search​

Experimental feature: In OsmAnd 5.4, the new spatial search algorithm is available only when the OsmAnd Development plugin is enabled. This allows us to collect feedback and continue improving the feature before enabling it by default in a future release.

Search in OsmAnd 5.4 has received a major upgrade. A new spatial search algorithm makes it easier to find places and discover objects around a specific location.

Previously, search was largely tied to your current location and the way individual words in a query were interpreted. The new approach takes geographical context into account, making combinations such as a place name + POI, category, street, or address much easier to understand.

For example, you can find a city or another place first and then search for cafés, restaurants, hotels, shops, fuel stations, or other POIs around that location. This is especially useful when planning a trip somewhere else instead of searching only near your current position.

The new search engine also improves how OsmAnd handles more complex queries, including combinations such as "Hotel Berlin", a POI together with a street or city, different street-name formats, translated category names, and other location-based searches.

Under the hood, this is more than an interface update. Our backend team introduced a new search architecture called Spatial Search by Name, designed to provide more relevant results and resolve many limitations of the previous search system. Search by supported POI categories has also been optimized for faster results.

Others updates and improvements​

• More track details in What's Here. Track information now makes it easier to distinguish between tracks on the map, including identifying the folder where a track is stored.

• More icons for profiles. The profile icon selection has been expanded, giving you more options to visually distinguish profiles for activities such as running and other use cases.

• Extended AIDL support for external apps. External apps and plugins can now organize their OsmAnd widgets into groups and use custom widget icons, providing more flexibility for third-party integrations.

• Correct altitude on Android 16. Fixed an issue where OsmAnd could display ellipsoidal altitude instead of altitude above mean sea level (MSL) on Android 16 devices.

Bug fixes​

• Fixed multiple URLs separated by semicolons being displayed and opened as a single link.
• Fixed the Open on map action in Travel Guides.
• Fixed copying widget panels and layouts from another profile.
• Improved performance when opening GPX waypoint descriptions by resolving intermittent UI freezes.
• Fixed widgets disappearing from Analyze on map after returning to OsmAnd from another app.
• Fixed imported multi-segment tracks not appearing immediately after import.
• Corrected incorrectly calculated storage size for Favorites and Favorite folders.
• Fixed synchronization between elevation, road type, surface, and other graphs in route details.
• Improved external sensor widgets by showing the correct disconnected state and resetting values after stopping.
• Fixed a visual gap between the current location marker and the route line during navigation.
• Fixed Favorite folder colors being reset after an app update.
• Fixed deleted Favorites unexpectedly reappearing on the map.
• Fixed outdated 3D Terrain maps not appearing in the Updates list.
• Improved sorting of Favorites by proximity to the selected map area.
• Fixed the location marker being hidden or positioned outside the visible map area in Android split-screen mode.
• Fixed navigation incorrectly ending after switching to another app and returning to OsmAnd.
• Improved navigation stability by fixing a resource leak that could cause crashes during longer trips.
• Improved pinned Favorites folder behavior so folder state is preserved correctly after restarting the app.
• Improved handling of very large tracks to reduce out-of-memory crashes when working with tracks containing hundreds of thousands of points.
• Fixed incorrect 3D track rendering when using Speed as the visualization parameter.

If you have suggestions for improving the Android version of the app, please get in touch with us. We appreciate and welcome your contribution to the further development of OsmAnd.

• Follow:

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

• Join:

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

• Get:  

  

  

When assigning Dakota and Lakota names to map elements, I am mainly drawing on the (often lifelong) work of others; very few of my changes are based on personal local knowledge. I have focused on sources who are either directly part of, or at least worked closely with, authentic Oc̣eti Ṡakowiƞ communities. This is the language of nations that are alive today, and they have things to say! My major sources include:

• My mapping work owes an enormous amount to (and sits in the shadow of) the absolutely incredible Maḳoc̣e Waṡte map by Lakota historian Dakota Wind Goodhouse, who drew on a vast range of sources to populate the names of thousands of places. His blog The First Scout is one of the best public history projects you’ll find anywhere, and you should check it out. Sometimes my research has led me to different conclusions on the precise meaning and pronunciation of some place names, and the largest limitation of his map is the one he tells you about right away (it is a Landscape Map and so rarely discusses towns and cities) but this is still the single largest, most thorough map of Lakota/Dakota place names you will find anywhere until such time as I can somehow map four times as much content as I have.
• For places in or adjacent to southern Minnesota, Paul Durand’s 1994 book “Where the Waters Gather and the Rivers Meet” is a vital source. Durand spent decades researching the names in this book, meeting with elders and communities and keeping meticulous records. Physical copies of this book (which are very rare and expensive now) included a large-scale map of the elements it describes. My copy is an ebook that did not include this map, but the dedicated folks at Wakaƞ Tipi Awaƞyakapi have a full-scale version printed on their wall at their newly opened center in Imniżaska (St Paul) which they were gracious enough to let me view and photograph.
• For places in or near the borders of the 1868 Great Sioux Reservation, a “Map of Lakota Place Names” created by communities of elders in Lower Brule and Rosebud from 2002-2017 has been a valuable resource. A copy should still be findable online at RAMADDA.
• For locations in Manitoba, I owe nearly everything I’ve mapped to the work of Dúzahan Mániwiƞ (Doris Pratt), a brilliant Dakota language teacher from Wípazoka Wakpa who devoted her long life to the restoration of her people’s language. She assembled a vast list of place names in her text “Dakota Iapi Ehdakub”, which she published in the final years of her life and which you can get a copy of for free at the Manitoba First Nations Education Resource Center.
• The New Lakota Dictionary (produced by the Lakota Language Consortium) and its Dakota counterpart the Dakhod Iapi Wic̣oie Wówapi (produced by the Daḳota Iapi Oḳodakic̣iye) have been very helpful for the research task of identifying the meanings and full pronunciation of names from sources that often represent the written language in different ways. These also included a great many place names directly, though I try to defer to the primary sources above (and make use of alt_name) parameters) when they disagree. A mention should also be made of the venerable Riggs dictionary as a reference for any number of words.
• And I am especially grateful to many current and former teachers and fellow-students at the University of Minnesota Dakota Language Program for patiently teaching me enough Dakota to have some understanding of what these sources are saying and how the logic of the language works. If you are trying to build a real understanding of the language from the ground up, I cannot recommend them enough. It won’t be quick or easy, but if you stick to it you’ll come out speaking Dakota.

There are many other “minor” sources that are the origin of one or a few place names, and there are other “major” sources that I have an eye on but am yet to get access to. I’ll edit this Diary post to add the latter if and when that changes.

I contributed by editing yay