OpenStreetMap Blogs Last Update:

Fehlende Smootness-Daten brouter könnte profitieren!

Wie soll brouter gute Rennrad-Tracks finden, wenn in OSM smoothness kaum gepflegt wird? Ein kleines Tool TagCoverage, welche ich geschrieben habe, zeigt, dass smoothness wenig gepflegt wird. In NRW sind gerade 8,6 % der erfassten Ways dafür dokumentiert! Natürlich gibt es Ausnahmen, in Köln gibt es deutlich höhere Werte, im Ortsteil Blumenberg sind es sogar 88,4 %! Berlin ist mit im Schnitt 37,3 % auch deutlich besser.

Abhilfe

Aber hier kann was getan werden, ich arbeite an einer App ACCoGPS, die georeferenzierte Vibrationsdaten per Handy am Fahrradlenker aufnimmt und diese über ein Backend aufbereitet und daraus saubere Smoothness-Daten ermittelt.

Beide Tools stelle ich am 16.9. beim OSM-Stammtisch in Köln kurz vor.

14 hours ago

I am happy to announce that we, the OpenStreetMap Carto maintainers, have prepared a new release of the OpenStreetMap Carto stylesheet (the default stylesheet on the OSM website). Once changes are deployed on openstreetmap.org it will take a couple of days before all tiles show the new rendering.

This is a minor release, but it still contains quite a lot of high impact changes to the map. We are also introducing a number of new design techniques in the style like scale dependent de-duplication of features and abbreviation of long labeling strings.

Under the hood we have added quite a few performance improvements, that we hope will ease resource requirement for style users and free resources for both mappers to add more data and for us to further improve the design of the map.

Here are some details on the visible changes this release brings to the style.

Motorway junction improvements

Density of highway=motorway_junction labels has been too high in some areas, leading to junction labels often blocking other labels (in particaular highway shields) while not being too useful themselves. We have made two changes in that regard:

• moving the starting zoom level for the labels up by one (ref starting z12 instead of z11, name starting z14 instead of z13).
• de-duplicating junctions with the same ref/name at the lower zoom levels.

The latter is important for motorway junctions because they are often mapped in pairs for both directions of the motorway. This previously often led to two identical labels and avoiding that helps a lot in reducing label density without removing substantial information. We also de-duplicate suffixes on ref (like 42a, 42b)

♦ ♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5204

github.com/openstreetmap-carto/openstreetmap-carto/pull/5227

Thanks to contributor leijurv for implementing these changes.

Unification of the fill colour for power plants etc. with the fill colour for industrial landuses for zoom levels 10-12

This fixes the error of the fill color for power=generator and similar tags not being unified with all the other builtup landuses at lower zoom levels.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5193

Thanks to contributor olafkryus for implementing this change.

Remove golf=pin rendering on polygons

We had previously displayed symbols for golf=pin on both nodes and polygons while mapper consensus is clearly that it is only used on nodes. This is changed now.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5214

Thanks to contributor dch0ph for implementing this change.

Remove highway=bus_guideway oneway arrow offset

We had rendered oneway arrows on highway=bus_guideway with an offset next to the line for a long time, but it was noticed that this leads to confusion in case of several closeby roads. We therefore changed this to centered oneway arrows.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5226

Thanks to contributor dch0ph for implementing this change.

Rework waterway lines

One of the biggest changes of this release is reworking of the waterway line rendering.

This includes, in particular:

• substantially narrowing the line signature of waterway=canal, which we had shown much stronger - like waterway=river - before, which does not reflect mapper consensus on the use of the tag though. This had led to mappers feeling discouraged to use waterway=canal on smaller artificial waterways. We have now adjusted this to a much more moderate line width.
• fixing errors and inconsistencies in bridge/tunnel rendering in some cases.
• reducing the halo of small waterways at high zoom levels, which had previously led to an inbalance between darker and brighter backgrounds.
• starting minor waterways earlier (at z12) in a subtle way to better communicate the drainage structure and provide better feedback on waterway mapping on a coarse scale.

♦ ♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5201

Thanks to contributor dch0ph for implementing this change.

Render waterway=fish_pass and tidy waterway bridge/tunnel code

waterway=fish_pass has been established as tagging for structures at weirs or dams that are meant to facilitate fish passing by the barrier during migration. We have now added support for rendering those and at the same time re-organized rendering of waterway tunnels and bridges a bit. That leads to us no more rendering waterways that are tagged both bridge=yes and tunnel=yes - which is not really meaningful tagging anyway and which had broken rendering before.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5240

Thanks to contributor leijurv for implementing this change.

Merge bridge and waterway-bridge layers

OSM-Carto has the most sophisticated and most accurate framework of layered roads rendering of all OSM based map styles in production use - yet there are various aspects in which our rendering is not properly reflecting the mapping in OSM. One of them is waterway bridges (like aqueducts) - which we have so far not correctly layered with the roads. The waterway bridges were always rendered above all road bridges, even if the layer tagging indicated othewise.

We have now integrated the waterway bridges into the road bridges layer and render them in correct order.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5251

Thanks to contributor dch0ph for implementing this change.

Improvements of waterway=dam and other water barriers

A number of improvements were made to the rendering of waterway barriers, in particular dams.

waterway=dam is used to map dams in the sense of contructed barriers to contain a standing body of water (usually called a reservoir). This is not to be confused with man_made=dyke, which is a barrier to prevent flooding during seasonal or weather related higher water levels.

These can be and are mapped with either nodes, linear ways or polygons.

OSM-Carto has rendered waterway=dam for a long time, but we have had various issues with the rendering that needed work. Some of them have been addressed now.

First the appearance of dams at the first zoom levels (z13-z15) was often considered heavy, especially for smaller dams. We tuned the rendering parameters to address that - and also the high zoom level design to better show that linear way and polygon design are representations of the same feature class.

Then we removed rendering of name labels on the outline of waterway=weir mapped with polygons. We had stopped rendering polygons tagged waterway=weir because that is not consensus mapping, but the label rendering was remaining as a stray label. This is now fixed. Also we changed the drawing order to provide better feedback on overlapping waterway barriers by rendering linear ways above polygons.

As you can see there are still some issues not yet addressed - like the stray labels for dams mapped with nodes at the lower zoom levels and the offset of dam polygon labels.

♦ ♦ ♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5241

github.com/openstreetmap-carto/openstreetmap-carto/pull/5264

Thanks to contributor dch0ph and leijurv for implementing these changes.

Remove rendering of name of amenity=charging_station

Like for many other points of interest we had - so far - rendered amenity=charging_station with a name label. But charging stations rarely have a proper name so the name tag on these is mostly abused as a label tag - not in line with the consensus among mappers about name tagging. Hence we decided to remove those labels. This also opens space for better differentiating charging stations in the future in a meaningful way - like indicating the vehicle types supported, plug standards, payment methods etc.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5238

Thanks to contributor GA-Kevin-Codes for implementing this change.

Add rendering of man_made=ceremonial_gate

Some time ago mappers have discussed the idea to unify tagging of different types of ceremonial gates (common in east and southeast Asia) to a single primary tag and thereby making it easier for mappers to tag these (without requiring up-front knowledge of the specific type) and for data users to interpret them.

We have now added basic support for rendering these.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5236

Thanks to contributor daishu0000 for implementing this change.

Delay minor accommodation text label

So far we have started showing symbols and labels of tourism accommodations (like hotels) all at the same zoom level (z17). With this change we now delay the name labels of the minor accommodations (tourism=guest_house and tourism=chalet) until z18.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5262

Thanks to contributors dch0ph for implementing this change.

Shorten multi-component flat and housenumber lists

There are addresses mapped containing long lists in addr:housenumber or addr:flats, which led to very long labels in OSM-Carto. We now addressed this problem by abbreviating long lists in such tags with an ellipsis.

We deliberately did not try to fully parse the content of these tags and label them in an abbreviated and normalized form since there are no firmly established conventions for the form of these tags when containing more than a single number.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5272

Thanks to contributors dch0ph for implementing this change.

Hide fake admin boundary segments on the 180 degree meridian

In OpenStreetMap we ought to map things in geographic coordinates, but unfortunately mappers often tend to map in equirectangular projection (which essentially means treating geographic coordinates as cartesian coordinates). And many data users also rely on them doing so.

This leads - among other things - to mappers creating fake geometries at the 180 degree meridian to formally close geometries in equirectangular projection (while, ironically, breaking them in geographic coordinates).

We in OSM-Carto have been in an unfortunate position since we - like many others - rely on software that expects data in equirectangular projection and is unable to process data in geographic coordinates. So we essentially are unable to support mappers in mapping things in geographic coordinates. So far we have displayed data as is - including the fake closures at the 180 degree meridian. We have now changed that for the administrative boundaries by explicitly removing those parts of the boundary directly on the 180 degree meridian. This works only because there are no actual administrative boundaries direcly on the 180 degree meridian of course.

There are still other issues related to the problem of the software we use only dealing with equirectangular projection and not being able to properly implement the periodic boundary conditions of the Mercator projection in longitude direction. We would like to do better in that regard, but have only limited options to do so.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5294

Thanks to contributor leijurv for implementing this change.

Rework railway=crossing rendering (starting zoom level, prioritization)

So far we have rendered railway=level_crossing/railway=crossing in a very simple fashion, starting with a small symbol at z14/z15 and switching to a larger symbol at z16. The symbol also had very low priority, meaning it was often hidden by road labels despite there being space for the road label to not block the crossing.

We now changed that by making the starting zoom level depend on the type of crossing railway. Also we indicate if a crossing is mapped not on a railway track by using a different symbol.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5285

Thanks to contributors dch0ph for implementing this change.

Lighten design and increase starting zoom level for minor service=* variants of some railways

We have also reviewed and re-designed the zoom level progression of minor service=* variants (service=spur/siding/yard) of some railways. railway=light_rail yards, in particular, were very heavy in appearance at the medium zoom levels and there were various inconsistencies in the zoom level progressions in general.

♦

github.com/openstreetmap-carto/openstreetmap-carto/pull/5290

Thanks to contributor leijurv for implementing this change.

Other changes

This release also includes various other, non-visible changes. For a full list of commits, see

github.com/openstreetmap-carto/openstreetmap-carto/compare/v6.0.0…v6.1.0

Note for deployments: This release updates all of the SQL scripts that you need to run on the rendering database before using the style (indexes.sql, functions.sql and common-values.sql). See INSTALL.md for details.

Thanks

The OSM-Carto maintainers thank all contributors - including those who contributed changes not visible in the map that are not listed above. Particular thanks go to the new contributors:

olafkryus, daishu0000, Harvester57, wangi

I want, in particular, to thank Nakaner (geofabrik) and leijurv for work on efficiency improvements of the style.

Thanks also go to Mapnik developers for addressing various issues and implementing improvements of particular interest for OSM-Carto.

As always, we welcome any bug reports at

github.com/openstreetmap-carto/openstreetmap-carto/issues

23 hours ago

For ages, I’ve been wanting to tell my stories around a specific place in OSM. Not specifically a “review” of a business, but simply a personal anecdote about me and that particular place.

Years ago, I received my first invitation to give a talk about OSM. On that occasion, I proposed this project: “What if we create a platform where people can share their personal stories around a specific place?”

But I was probably just an “idea guy” back then.

My programming skills weren’t developed enough to build the platform all by myself, and I had no idea how to get funding to pay for a hosting service anyway. So I shelved the idea for a long time.

Fast-forward to 2026, I eventually thought to myself: maybe it’s finally the right time to revisit that old dream.

So I built this.

♦

First, you log in using your OSM account.

♦

I want this platform to be somewhat of an extension of OSM Diary.

Here, you can not only write an “OSM Diary” entry associated with your OSM account, but also link it to a specific place. Every story is tied to a particular location. If a place is significant enough that many people have posted their stories about it, you can see all the other stories associated with that place.

Then, you have three ways to choose a place. You can search for it using the “Search places with Photon” feature. You can manually zoom in on the map and pick a location. Or you can use the GPS button to automatically zoom to your current location.

Then, pick a location and write your story.

♦

♦

♦

♦

♦

♦

Try it here : bisikbekasi.rf.gd/o/

Source code : github.com/altilunium/altilunium.github.io/blob/main/util/ivebeen_here/index.php

2 days ago

Online-Konsultation für einen weiterentwickelten Rahmen für Open Data

Die Bundesregierung plant, den strategischen Rahmen für Open Data weiterzuentwickeln. Das Bundesministerium für Digitalisierung und Staatsmodernisierung lädt daher die Open-Data-Community, Stakeholder und die interessierte Öffentlichkeit zu einer Online-Konsultation ein.
Ziel dieser Konsultation ist es, Vorschläge und Anregungen für einen weiterentwickelten Rahmen als „Fahrplan für Open Data“ zu sammeln. Die Bundesregierung strebt die Verabschiedung und Veröffentlichung für Anfang 2027 an.

Mitglieder aus dem FOSSGIS e.V. haben anhand der Leitfragen die wichtigsten Aspekte, Themen und Handlungsfelder zusammengetragen, woraus eine Stellungnahme entstanden ist, die fristgemäß eingereicht wird.

Danke an alle, die unterstützt haben.

Hier ist die komplette Stellungnahme zum Nachlesen und Herunterladen als PDF.

2 days ago

Wrapping up GSoC 2026: Making closures.osm.ch production ready

This summer I had the chance to spend my second Google Summer of Code working with the OpenStreetMap Foundation, this time on closures.osm.ch, a community platform for reporting temporary road closures in real time so that routing engines can actually route around them.

closures.osm.ch started life during GSoC 2025 as a solid prototype: a FastAPI backend, a Next.js frontend, OpenLR location referencing, and a first attempt at routing integration with Valhalla. My job this summer was to take it from “working prototype” to something closer to a real production service.

The routing problem

The biggest issue going in was architectural. The frontend was fetching closures, pulling out raw coordinates, and handing them to the public Valhalla instance as exclude_locations. It worked, sort of, but it had a hard 49-point cap, ignored one-way closures entirely, and duplicated business logic between two different frontend components. None of that scales.

Before writing any code, I actually went and discussed the right approach with the Valhalla maintainers themselves in a public GitHub discussion. That conversation confirmed the long-term correct architecture is Valhalla’s live traffic tile infrastructure rather than anything at the exclude_locations level. That’s a bigger undertaking than fits in one summer, so the plan became a two-stage one: build a solid stepping-stone now, leave the graph-level integration properly documented for later.

That stepping stone is what shipped: a self-hosted Valhalla instance, and a new backend endpoint that buffers closure geometries with Shapely and passes them to Valhalla as exclude_polygons instead. The frontend got a lot simpler as a result, it just asks for a route now and gets one back with closures already avoided, no more duplicated logic living in the browser.

OpenLR, for real this time

Somewhat embarrassingly, the OpenLR codes the platform was generating weren’t actually spec-compliant OpenLR, they used a custom marker byte that no standard decoder could read. That’s now fixed, with encoding going through Valhalla’s map-matching, so closures.osm.ch’s location references should now interoperate with other OSM-based navigation tooling that speaks real OpenLR.

Vector tiles

Active closures are now served as MVT vector tiles straight out of PostGIS with ST_AsMVT, so the map layer updates live instead of requiring a page reload. Small feature, but it makes the map feel a lot more alive.

What’s left

Government data ingestion is the piece I didn’t get to finish. The plan was CIFS and DATEX II importers so the platform could ingest authoritative closure data from municipal agencies directly, but partway through the summer that scope shifted: OST offered to push pre-processed Swiss ASTRA data to us directly instead of us having to parse it ourselves, which changes the shape of that work. I’ve made a start on it, but it’s genuinely not done, and I’ll be continuing on it after GSoC officially wraps up. UI internationalisation is also still untouched, it’s documented as deferred work for now.

Thanks

Huge thanks to my mentors Simon Poole and David Haberthür for the guidance this summer, and for trusting me to make real architectural calls on a project that real people depend on. Also thanks to the Valhalla maintainers for taking the time to talk through the routing architecture with a stranger on the internet before I’d written a line of code.

If you want the full technical rundown with links to every PR, I’ve written that up separately in the project’s final report.

Development on closures.osm.ch continues, I’m not stopping here.

3 days ago

I sincerely apologize for my lack of reading the guide for this website when I shouldn’t use map 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.

:/

(UPDATE: This has been edited 2 times now.)

4 days ago

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!

4 days ago

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

4 days ago

27/08/2026-02/09/2026

♦

[1] Group photo from SotM 2026 in Paris | © SotM 2026 Paris | map data © by OpenStreetMap Contributors.

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.

5 days ago

Created account, Labor Day Weekend

5 days ago

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í! 😃🐧

6 days ago

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”?>

6 days ago

When OpenStreetMap put a slippy map on its front page on its front page in 2005 it used a Mercator map. This made excellent sense at the time: true north was at the top everywhere, angles were good (spherical Mercator less so than geoidal Mercator) and the raster tiles at then in use could be scrolled without spending computational power on changing their shape. Other maps at the time made the same decision for the same reasons.

Twenty years on desktop and even mobile processors can render vector tiles with consummate ease, keeping the labels in the right shape while they do so. The need to keep tiles the same shape has evaporated and many maps can be spun to put whichever direction the user wants at the top. But the disadvantages of Mercator remain: at small scales Canada and Greenland are exaggerated in size compared to Africa. At large scales this is more subtle, each zoom level maps Helsinki at a linear scale twice as large as Bogota with four times the area and shifting a zoom level doesn’t mix well with map styles that use the level to show differing amounts of detail. There is more than a further zoom level of difference between Helsinki and Longyearbyen. The widest used scheme for tile URLs leaves a hole 1000km across around each pole; this was tolerated because the is no land in the Arctic hole and, as any Australian will tell you, the southern hemisphere doesn’t count.

Many vector tiles, however, are still based on Mercator leaving the different scale at each zoom level depending on latitude in place along with the holes at the poles. This made the transition from raster to vector tiles easier but is less relevant now apart from holdouts like the OSM-Carto layer. An alternative tiling scheme is how OSM stores its coordinates: latitude and longitude. A large scale map of a small area could simply use the coordinates directly scaled by the cosine of the latitude and the scale will stay the same as the map pans north and south. A small scale map could use the Equal Earth projection favoured in a United Nations vote, another equal-area projection or one that isn’t such as an orthographic globe view — or even Mercator.

These opinions are my own.

16 hours ago

recent hdyc.neis-one.org feature update is really something else. it forces you to read “that thing”. sometimes i accidentally read something that makes my blood boil.

alright, instead of replying there, i’m gonna reply to it here instead.

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

place=town: An important urban centre that is larger than a village, smaller than a city, and not a suburb. Towns normally have a good range of shops and facilities which are used by people from nearby villages.

place=village: A smaller distinct settlement, smaller than a town, with few facilities available, with people travelling to nearby towns to access these.

place=hamlet: An isolated settlement.

i can confirm by myself that “that place” is not isolated.

meanwhile, administrative borders should be mapped as ways/relations properly. for a node, just stick with this global consensus definition as stated on the wiki page.

but where can we get that administrative border data?

someone in “that Telegram” group claimed to own all the copyright to this country’s administrative data, even though it is clearly already licensed as open data on “that site”.

i’m not a lawyer, so i don’t know the legality of manually tracing that border from an official source. this is why i hate mapping from official sources. i’d rather stick to local knowledge and direct surveys.

and… that’s it, pretty much.

a day ago

Alright. Day two. As I finally have some free time to write this one.

At 2:27 pm, I went to the Martinique room, planning to attend the “OSM Science” opening talk.

♦

At 2:37 pm, I saw a slide showcasing the QR codes for each OSM Science output, starting from 2019 to 2025 (including the IJGI special issue).

♦

I went back and forth, decoding all those QR code links one by one, and posted them on my Mastodon.

• zenodo.org/records/3405431 (2019 - Heidelberg)
• zenodo.org/records/3928675 (2020 - Cape Town (x) - Online)
• zenodo.org/records/5116434 (2021 - Online)
• zenodo.org/records/7004791 (2022 - Firenze)
• zenodo.org/records/10443403 (2023 - Antwerp)
• zenodo.org/records/17370615 (2024 - Nairobi)
• zenodo.org/records/21009418 (2025 - Manila)
• zenodo.org/communities/osmscience2026/records?q=&l=list&p=1&s=10 (2026 - Paris)
• www.mdpi.com/journal/ijgi/special_issues/OpenStreetMap

The Q&A session started at 2:51 pm, and finally ended at 2:58 pm.

♦

After that, I stayed in the Martinique room. The researchers who had submitted their publications to OSM Science started presenting their work, one by one, in quick succession, around five minutes each.

Around 3:02 pm, I had to close the stream for a little while because I had something to do.

I came back at 3:38 pm, still in the Martinique room. The OSM Science paper presentations were still ongoing, and finally ended around 3:44 pm.

Then, it was coffee break (10:44 am Paris time). The programme said it would resume at 11:15 Paris time.

I closed the stream, killed some time by editing WeeklyOSM, then came back at 4:12 pm, this time in the Corse room.

The talk had not started yet. It finally began at 4:15 pm.

The topic was very interesting: how to make your GNSS (a.k.a. “GPS”) reach centimeter-level accuracy.

♦

Turns out, you need special hardware and a special “network to distribute GNSS correction streams”.

♦

♦

♦

♦

♦

♦

♦ The talk ended at 4:43 pm.

At 4:44 pm, I went back to the Martinique room. The next talk started at around 4:50 pm, this time about visualizing lanes in road networks. Really interesting.

♦

When I edit WeeklyOSM, I sometimes come across several contributors who are working on this exact same problem: how to properly visualize lanes in the OSM road network.

And this problem is really complex. Sometimes, for example, you need to account for the width of each road’s geometry, which can even vary along a particular segment.

♦

♦

♦

♦

♦

♦

♦

The talk ended at 5:18 pm.

At 5:22 pm, I went to the Corse room. This time, the talk was about the “Fédération des pros d’OpenStreetMap” (FPOSM).

From the talk description, it is “a French non-profit organization that unites companies and professionals whose services and tools are built on OpenStreetMap, and who are committed to keeping OpenStreetMap a healthy digital commons”.

I discussed this talk quite a lot in the internal HOT chat group while watching the stream online, especially the possibility of starting a similar organization ourselves.

At 5:48 pm, I had to close the stream again because I had something to do.

At first, I planned to rejoin at around 8 pm, but then I got an urgent invitation from my neighbor to attend an event. So I tried to watch the stream on my mobile phone while traveling outside, around 8 pm, in the Guadeloupe room.

It was one of the talks that I really wanted to watch. It was about OpenStreetMap’s “core software” projects, explained by the key people behind those projects themselves.

Unfortunately, I failed to watch the rest of the talk, since the neighbor’s event was starting soon. So I had to close the stream and move on.

Thankfully, as I am writing this OSM diary right now (September 9th, while the second day was August 29th), the full recording of that talk is already available on the SOTM 2026 website, hosted by OSM France’s PeerTube instance.

Well, I think I want to watch the video in full first before continuing this OSM diary…

2 days ago

September 6–12 September 8

• Fixed David Lane and Country Brook Lane.
• Modified Rickly Street; added note that signage by the Street Department is incorrect. Correct spelling is Rickly Street, not Rickley Street. (Contacted city and should be fixed soon with new work order)
• Added a driveway and multiple road names (Buckeye Alley, Cherry Alley, Hickory Alley, Elm Alley, Maple Alley, Ash Alley, Walnut Street, Cypress Alley, and the rest of Beech Alley).
• Added info to (now closed) Hannah J Ashton Middle School.
• Added Unzinger Ditch and name of Dysar Run.

2 days ago

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.

4 days ago

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

4 days ago

in-browser editor

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

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

1. United States
2. Kentucky

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

37 Degrees North & -85 Degrees West

4 days ago

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.

5 days ago

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

5 days ago

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

6 days ago

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

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

6 days ago

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

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

7 days ago