Welcome to Planet OSGeo

November 17, 2026

Dear Reader,

On Thursday 19 November 2026, MassGIS, the Commonwealth of Massachusetts' Bureau of Geographic Information, celebrates its 40th anniversary with an open house in Boston. Remarks start at 10:00 from the EOTSS Secretary, followed by reflections from three former MassGIS directors on how the agency and its work have evolved. The event is open to all, and the details are on the MassGIS event page. We cannot be there in person, so we are marking the occasion here. Congratulations to the whole MassGIS team and to EOTSS.

Happy 40th, MassGIS. Four decades of Massachusetts geographic data, more than twenty years on GeoServer.

Forty years of authoritative data

MassGIS is the official state agency responsible for collecting, storing and sharing geographic data for Massachusetts. Established in 1986, MassGIS originally operated within the Commonwealth's environmental secretariat and is now part of the Executive Office of Technology Services and Security (EOTSS). Its mandate goes beyond data: it coordinates GIS activity across the Commonwealth and sets the standards that keep statewide data consistent and usable. The data is created and curated by the MassGIS team, and it is hosted on databases and servers run by several parts of EOTSS. It is a joint effort, and this anniversary belongs to all of them.

Most people meet MassGIS through its applications. MassMapper, launched in November 2021 to replace the long-serving OLIVER viewer, is the flagship interactive map. The MassGIS Data Hub publishes the same authoritative layers as downloads, services and APIs. MuniMapper gives cities and towns without their own application a customised version of MassMapper. The users are municipalities, regional planning agencies, surveyors, engineers, real estate professionals, researchers and the general public.

Twenty years on GeoServer

MassGIS put its first GeoServer into production in November 2005, with version 1.5.0. More than twenty years and numerous upgrades later, GeoServer remains a key component of MassGIS's web mapping infrastructure. It serves hundreds of statewide layers, from parcels and addresses to wetlands, land use and aerial imagery, through OGC-compliant WMS and WFS services. Those services feed MassMapper, but also the desktop and web GIS tools that cities, regional agencies and consultants use every day.

MassGIS is now working on its next upgrade to GeoServer 3, following the agency's implementation schedule. This ongoing investment in maintenance and modernization helps support the long-term reliability and sustainability of the platform.

The current platform runs clustered GeoServer deployments integrated with PostGIS and Leaflet, alongside proprietary tools, in what MassGIS describes as a fully hybridised web mapping platform. A few numbers from MassGIS, for January to September 2026:

 
  • Over 800 datasets published with dynamic SLD styling.
  • More than 3,800 MassMapper launches per business day.
  • Over 200,000 GeoServer requests per business day.
MassMapper showing the Boston area, courtesy of MassGIS

MassMapper, the interactive map of the Commonwealth, courtesy of MassGIS.

Why this matters beyond Massachusetts

Twenty years is a long time in software. Over that period MassGIS has moved across several generations of GeoServer, moved to the cloud, swapped out its front end, and kept the same services running for the people who depend on them. That continuity is the point. Open standards mean a layer published once can be consumed directly in ArcGIS, QGIS or a web browser, without local copies of the data to maintain. An open platform means the state controls its own infrastructure, with no licence tied to the number of layers or users. And because upgrades are part of normal operations, the platform keeps pace with new releases instead of falling behind.

For regional and local GIS managers the benefit is practical: reliable access to authoritative data, direct interoperability with their own tools, and less infrastructure to run themselves. For other states and agencies it is a working example of what open source geospatial looks like at statewide scale, in production, over decades.

Our part

MassGIS develops and maintains MassMapper, its flagship interactive mapping application, with support from Schneider Geospatial. GeoSolutions supports MassGIS through an enterprise support and subscription agreement for GeoServer. Our role is to keep the platform stable and current: optimisation, performance tuning, security guidance and best practices, straight from the people who develop GeoServer. It is the kind of long, quiet partnership we like best, where the software simply keeps working.

Read the case study

The full story of how MassGIS uses GeoServer to power MassMapper is in our case study, available as a two-page PDF on the MassGIS portfolio page. If you run statewide or municipal data services and want to talk about GeoServer in production, our Enterprise Support Services, Professional Training Services and Subscription Services are the place to start, or just contact us.

Happy 40th, MassGIS. Here's to the next twenty years on GeoServer.

The GeoSolutions team, GeoSolutions

by simone giannecchini at November 17, 2026 02:37 PM

November 16, 2026

This post is part of a series on Georama. You will learn more in the upcoming posts.

Have you ever wished you could publish your QGIS project directly to the web, be it as WMS, as OGC API – Features, or within a full-fledged WebGIS? Then Georama is made for you!


What is Georama?

Georama is an open, interoperable platform, built on Django, for any geospatial data publication workflow, from complex enterprise workflows down to anyone sharing their first dataset. Georama is your bridge between powerful desktop GIS and scalable, standards-based web publishing.

Under the hood, Georama connects four components, each focused on one job:

  • QGIS as the data integration and styling engine
  • Django as the application and permission layer
  • pygeoapi and QSL as the standards-based service backends
  • GeoGirafe as the WebGIS frontend

Georama is open source, dual-licensed under AGPL 3.0 (or later) and an OPENGIS.ch commercial licence.

At the time of writing, the current stable version of Georama is 26.2.

Thanks a lot to the Web Team for all the hard work in the past few months! 


From QGIS to a WebGIS

You can publish your QGIS project to the web in just 4 steps:

  1. Create your QGIS project (ideally with QGIS 3.44) and copy it to the server where your Georama instance is running
    Style your project in QGIS
    Style your project in QGIS
  2. Integrate your project in Georama
    Integrate your project in Georama
  3. Publish your integrated project as a WebGIS theme

    Publish your project as a WebGIS theme
  4. Set the permissions accordingly (or set to public if you want to share your WebGIS with the rest of the world)

    Define access rights to individual users and groups

And there you have it!


Of course, you can also publish your individual layers as WMS and / or OGCAPI Features. We’ll cover that in a later blog post.


 What can I find in Georama?

  • Publish your QGIS projects to the web in just a few clicks, keeping the styling, properties and basic metadata you defined in QGIS
  • Built on OGC standards: WMS 1.3.0 and OGC API – Features
  • Publish directly into a WebGIS, leveraging the power of the GeoGirafe client and community. Georama is one of GeoGirafe’s officially supported backends
  • Native OIDC support: we have tested extensively with Keycloak, Microsoft Entra ID and Amazon Cognito, but any OIDC-compliant service should work nicely
  • Fine-grained access rights, down to the attribute level
  • Metadata management for your layers and datasets
  • Multilingual user interface: currently English, French, German and Italian
  • API-first: automate everything, without using the graphical user interface! A future blog post will guide you through the Georama API
  • Multi-tenant: one Georama instance can host several tenants, each with its own projects, users and permissions. For example, a city running georama.city.ch can give each of its departments its own tenant, such as departmentA.georama.city.ch and departmentB.georama.city.ch. A future blog post will guide you through multi-tenancy in Georama.

Try it yourself on the sandbox

The best way to discover Georama is to try it. Head to sandbox.georama.io and log in with one of these accounts:

  • Simple user: sandbox_user // youCanTestGeorama
  • Admin user: sandbox_admin // youCanTestGeorama

On the sandbox, you cannot push your own QGIS projects, but we have prepared a few projects for you to play with: integrate them, publish them, assign permissions, and see the result in the WebGIS or, if you publish layers as WMS or OGCAPI – Features, directly in QGIS. We’d love to hear what you think!

Want to go further?

  • Browse the source code on GitHub
  • Install and deploy your own instance with the help of the documentation

What’s next?

We have a lot of ideas and plans that will unfold in the coming months, among them:

by Stéphane Henriod at November 16, 2026 03:32 PM

Prezado leitor,

Quer aprender a implantar e gerenciar uma Infraestrutura de Dados Espaciais (IDE) e publicar seus dados geográficos na web?

Estão abertas as inscrições para a nova turma do Curso de GeoNode 5.1 da Geocursos!

Com uma abordagem prática, você aprenderá a utilizar o GeoNode para organizar, publicar, compartilhar e gerenciar dados geoespaciais, integrando diferentes ferramentas e tecnologias.

🚀 O que você vai aprender?

✅ Instalação e configuração do GeoNode 5.1
✅ Gerenciamento e publicação de dados geoespaciais
✅ Servidores de mapas e padrões OGC (WMS e WFS)
✅ Criação de mapas, dashboards, geostories e fluxos de trabalho geoespaciais
✅ Integração entre GeoNode e QGIS
✅ Aplicações práticas para implantação de IDEs

📅 Quando?
01, 02, 03, 08, 09 e 10 de dezembro de 2026.

🕖 Horário: 19h às 22h (Brasília)
💻 Modalidade: EAD ao vivo
⏱ Carga horária: 18 horas (6 aulas)
🎥 Gravações disponíveis por 12 meses
🎓 Certificado de participação
👨‍🏫 Instrutor: Fernando Quadro

📢 Inscrições até 30/11/2026!

As vagas são limitadas!

🔗 Garanta sua vaga:
https://geocursos.com.br/geonode

💡 Transforme seus conhecimentos em GIS e dê o próximo passo na publicação e gestão de dados geoespaciais na web!

by Fernando Quadro at November 16, 2026 02:33 PM

I am pleased to announce the release of MapGuide Open Source 4.0.1-Test

The reason this is a 4.0.1-Test instead of just 4.0.1 is because the volume of changes since 4.0 is such that I wasn't comfortable with going straight to a 4.0.1 release. I needed a -Test release and several weeks of breathing space to collect any issue reports and be able to act on them to make sure we didn't miss anything important.

Before we continue, I want to make this declarative statement crystal clear in no uncertain terms:

This release was (un-repentantly and un-apologetically) made with AI assistance from DeepSeek. I have made no secrets about my AI usage in the lead-up to this release. If the fact that my usage of AI offends your sensibilities and makes MapGuide "AI slop" in your eyes, then I wish you all the best in looking for an alternative GIS web mapping server. I'm not going to expend any efforts to convince you to stay. It is because of AI assistance that I am able to make this release *now* instead of probably ... a year from now if I were to apply regular human effort to implement the volume of changes in this release.

With that statement out of the way, here's what's new in this release. It's a big list, so strap in!

MapGuide changes

  • Updated bundled Apache, Tomcat and PHP (mitigated against php2shell)
    • Apache httpd 2.4.71
    • Tomcat 9.0.123
    • PHP 8.3.36
  • Windows installer migrated to Wix 6.x. If you encounter installer issues, let us know on the mapguide-users mailing list ASAP.
  • New experimental OpenAPI spec + swagger UI for the mapagent. The mapagent is not a RESTful interface, which presented some interesting challenges describing the API surface with OpenAPI, but we've made it work for the most part!
  • New experimental Linux support for MapGuide Portable
    • The OSGeo.MapGuide.Portable nuget package can now be used to build apps for both Windows and Linux. The viewer nuget packages built on top of this are still Windows-only.
  • Ubuntu installer script now optionally lets you install msttcorefonts
  • Linux installer scripts now auto-probe and auto-configure known font directories in serverconfig.ini
  • MultiGeometry/GeometryCollection instances now render and select properly
  • Massive memory leak sweep from ASAN-instrumented test runs
  • Massive hardening sweep to address potential buffer overflows and input validation gaps
  • Fix MgNullPropertyValueException when selecting features and attribute data contains NULL values
  • Fix web tier init failures leaving the process permanently broken and improper web tier teardown
    • Should improve stability if using IIS and reduce the need to force app pool recycling
  • Fix MgDrawingService.EnumerateLayers() API not working on Linux
  • Fix leaking byte arrays when passed to MgByteReader.Read() for Java and PHP
  • Fix incorrect distance measurement on coordinate systems like Web Mercator
  • Fix MgNamedCollection potentially holding stale refs
  • Fix incorrect arc calculations
  • Fix name element duplication for KML elements
  • Fix excess KML placemark elements when Advanced Stylization is enabled
  • Fix correctness of "batch sorted block" feature join algorithm
  • Fix Advanced Stylization area symbolization clipping not applying
  • Fix cases where negative render times could be reported by performance report
  • Fix assorted incorrect mapagent behavior
  • Fix striped raster rendering in some cases
  • Improve error message quality when its localized form cannot be retrieved
  • Improve robust CPU perf counter reading on Linux
  • Document log properties in serverconfig.ini
  • Improved BerkeleyDB error message quality (some were previously masked as "bad memory allocation")
  • Improve handling of bigger selections and properly escape id values with single-quotes

FDO changes

Core/General
  • Massive memory leak sweep across core and various providers. Debug runs of FDO core + provider test suites now produce 0 leaks on both Linux and Windows.
  • Massive hardening sweep to address potential buffer overflows and input validation gaps
  • GenericRdbms: The FDO_TRACE_FILE facility is now available for Linux
  • GenericRdbms: Fix various reported capabilities vs reality mismatches
  • GenericRdbms: Harden against queries referencing non-existent classes and properties
  • Use the safer mkstemp API for temp file name generation
  • Honor indentation settings when writing feature schemas to XML
  • Fix XmlFeatureSerializer not honoring XML flags
  • Fix properties with NULL values not included in XML output
  • Improve handling of large chains of OR conditions
  • GenericRdbms: Each FDO provider is now is own deb package on Ubuntu instead of all being bundled under a monolithic fdo-rdbms package.
SDF
  • Fix incorrect NOT IN behavior when NULL values are involved
  • Gracefully handle unknown ordering fields in extended select command
SHP
  • Fix GetSpatialContexts crash when schema cache is invalidated
SQLite
  • Fix filtering on numbers with more than 5 decimal places
  • Fix filtering on dates returning wrong results
  • A "Default" spatial context is now returned if the data store has no coordinate system metadata
  • Properly fix thread-safety on both Windows and Linux when building internal metadata.
    • The deadlock on Linux (reason for original fix being rolled back) was due to using a non-recursive pthread mutex.
OGR
  • Re-architect provider internals for better stability when consumed from a .net client FDO application
  • MultiGeometry/GeometryCollection instances are now read by the provider properly
  • Fix "Invalid index: -1" errors from missing properties
GDAL
  • Prevent blank horizontal stripes when up-sampling rasters
  • We try to include the underlying GDAL error message in more places where exceptions are thrown
  • Update configuration doc XML schema to cover missing elements
King Oracle
  • Fix issue reading negative int64 values
  • CLOBs are now read properly on Linux
  • Unicode strings now insert properly on Linux
SQL Server Spatial
  • The SQL Server Spatial FDO provider is now available for Linux
    • You will need to install the Microsoft ODBC Driver for SQL Server. The ubuntu installer package will install this for you automatically
  • New experimental environment variable (FDO_SQS_PERF) that improves provider performance in various areas
    • Set =1 to opt-in
  • Provider now prefers Microsoft ODBC driver 17/18 before falling back to SQL Server Native Client.
  • Fix poor error message when inserting a row into a table without a primary key
  • Fix spatial contexts with dots in its name not being destroyable
  • Fix query with explicit property list losing all geometry types on its query result geometry property
  • Queries against geography columns apply polygon vertex ordering fixes if required
PostgreSQL
  • Curve geometries now auto-linearized for versions of PostGIS that do not natively accept curve geometries in their spatial operators
  • Now uses proper bind variables for geometry values, eliminating the ugly wkb->hex->wkb roundtrip in SQL query generation
  • Fix failing queries that involve coalesced geometry expressions
MySQL
  • Fix incorrectly reported column types
  • Fix column aliasing in joined queries
ODBC
  • New experimental Linux support for the ODBC FDO provider
    • Previously, we built the provider but did not vet any supported behavior
    • Vetted ODBC drivers for Linux (based on test suites)
      • mdb-tools
      • ODBC Driver for SQL Server
    • Your mileage may vary for any other drivers
WMS
  • Fix "no data" value reported by provider

Download Links

Trac has been on the fritz lately, so the release notes which has the download links have been mirrored to my mapguide-fdo-docs repo on GitHub.

4.0.1-Test release notes on GitHub

by Jackie Ng (noreply@blogger.com) at November 16, 2026 08:48 AM

November 15, 2026

As I am doing my final spot checks on a MapGuide Open Source 4.0.1-Test release, I am lamenting that MapGuide Maestro was still windows-only and even though a multi-platform rewrite is in my plans, that is in the distant future. Meaning that to spot-check functionality on an MGOS Linux installation, I'd have to either:

  1. Make raw HTTP requests to its mapagent (painstaking)
  2. Spin up a Windows VM to run Maestro that connects out to the mapagent on that MGOS Linux installation (less painstaking, but still painful)
But then I thought a bit harder. Thanks to the efforts of Lord Gaben, gaming is now viable on Linux. Most windows games that don't use invasive kernel anti-cheats "just work" now out-of-the-box on Linux. It's part of the reason I was comfortable jumping ship from Windows 10 when it went EOL last year.

But I have been viewing this strictly from a gaming context, maybe we can apply that same logic to windows apps in general?

I go and download the latest zip release of MapGuide Maestro from GitHub, extracted the contents to some folder.

Then I open a terminal in that folder and ran: 

wine Maestro.exe

And ... it just works!





This is on Fedora 44, my daily driver OS and one of the major Linux distros!

Does Maestro under Wine operate flawlessly? Not sure. YMMV. Does this invalidate the need for a multi-platform rewrite of Maestro? Not exactly, that plan is still in place. But this discovery is a nice stop-gap measure to tide the Linux users over until then!

So if your Linux distro can run Steam, it can probably run Maestro as well!

by Jackie Ng (noreply@blogger.com) at November 15, 2026 03:16 PM

November 13, 2026

November 12, 2026

Some places are more than a dot on a map. For OPENGIS.ch, Laax is one of them.

Laax is home to OPENGIS.ch, and it is where QField was born. So when it came time for this year’s Hackfest, there was really only one place to go. In October 2026, our ninjas travelled from across Switzerland and around the world back to the mountains where it all began. And this time, we didn’t come alone.


Closing a circle ➰

This year Laax also welcomed the QGIS User Conference and the 29th QGIS Contributor Meeting, organised by OPENGIS.ch and the Swiss QGIS user group. For the QField team, the symbolism was hard to miss.

QField exists because of QGIS. Every map, every form and every symbol a field worker sees on their phone is designed in QGIS and drawn by the QGIS rendering engine. QField is what happens when a community spends two decades building a world-class desktop GIS in the open, and then someone asks, “what if we took this outside?” Welcoming that community to the very village where OPENGIS.ch and QField started felt like closing a circle.

Marco, QField’s creator, captured it in the title of his conference talk: “QField, From Laax with 💚”. He told the story of a project that left these mountains and found its way to fieldwork sites on every continent. He also shared where it is heading next, with on-the-fly project creation, COGO tools, NTRIP support for RTK accuracy and 3D data collection.

At the outdoor QField workshop, participants collected real data in the Alpine landscape, syncing it through QFieldCloud as they went. Other ninjas spent the onboarding day helping new contributors take their first steps into the QGIS codebase, or working on different projects for OPENGIS.ch. Many stayed on through the Contributor Meeting to work on QGIS itself. We don’t just build on QGIS. We help build it, and this week we got to do it side by side with the people who make it possible.


More than software 🥷

People sometimes describe open source as a licence, or a way of distributing code. For us it has always been something bigger. It is our reason for being.

Look around the room when the OPENGIS.ch ninjas get together and you see what we mean. There are developers, designers, consultants, project managers, administrators and support specialists. They come from different countries, speak different languages and bring very different backgrounds. On any given day, they work on different things: a new QField feature, a QFieldCloud improvement, a fix deep in QGIS, the development of GEORAMA by a fast-growing web team, the preparation of our upcoming courses, or a tailored solution for a client with a tough problem to solve. Not to mention Team 42, who keep things running behind the scenes.

And they all share a stubborn belief that the best tools are built in the open, and that hard problems get solved faster when everyone can see the work and pitch in.


All of us are better than any one of us.

That belief shapes how OPENGIS.ch works every day. We are a distributed team spread across many time zones, and most of our collaboration happens the open-source way: in public repositories, in issue threads and in code reviews. That works remarkably well. But a week together in Laax is a reminder that the real foundation of open source is people, and the trust between people who choose to build something together.

A hackfest in the mountains was bound to produce a few stories. Our CEO flew down the mountain instead of taking the gondola. 🪂 Our lead QField developer celebrated his birthday with all the ninjas singing around a raclette in a mountain chalet. 🧀 And some squatted and climbed their way to the perfect portraits for our website, because dedication to the shot is a team sport. 🏋📷


Out in the field 🗺

Fittingly for a team that builds tools for fieldwork, we spent a lot of the week outdoors. Our users work on muddy trails, steep slopes and remote plateaus, so it does us good to get our own boots dirty now and then.

The October weather was on our side. Groups rode the cable car above Flims and hiked across the Segnes plateau, a broad golden plain beneath a jagged wall of limestone peaks, with waterfalls pouring off the cliffs. Others wandered forest paths down to the turquoise Caumasee, or looked out over the Rhine Gorge from a viewing platform high above the river. It is hard to walk through country like that without wondering how you would map it. Once a field person, always a field person.

Back in the village, the lobby of the Riders Hotel became our co-working space for the week. 🧑‍💻 It was a happy mix of laptops, coffee and the kind of quick conversations that are so much easier in person. A question that might take a day of back and forth over chat gets settled in ten minutes at a shared table. We also set aside time to talk about how we work together and where we want to go next, filling a few walls with sticky notes along the way. When heads needed clearing, the football table saw some fiercely competitive matches.


Long tables, warm evenings 👥🕯🍽🥷🪩💬

If one image sums up the week, it is a long table full of people.

We walked through the forest together to Tegia Larnags, a wooden mountain restaurant, for an evening with the whole OPENGIS.ch crew. There was good food, plenty of laughter, a few surprises, and a dance floor that stayed busy late into the night. Some of us had worked together online for months, or even years, without ever sharing a meal. Those conversations, about QField, about life, about the next big problem to tackle together, are where a team really grows.

Some of the best moments were unplanned: a BBQ under a clear mountain sky, a busy bar on a cold night, and a team photo in matching OPENGIS.ch hoodies. For those who stayed on into the weekend, the village celebrated the return of the cattle from the high summer pastures with a traditional festival. It was a lovely reminder that Laax is a real mountain community, and that we are lucky to call it home.


Why it matters

Hackfest is how we stay a team, and a stronger team makes better things. The trust, energy and ideas from a week like this flow straight back into our work. They show up in QField and QFieldCloud, in the projects we deliver for our clients, and in the code we contribute to QGIS.

In the end, the people who benefit most are the ones using what we build, out in the field, every day. What is good for our team is good for our users, and good for the open-source community we are proud to be part of.

This year it meant even more. We came back to the place where QField was born, with the whole OPENGIS.ch team together in one place. We left with full notebooks, tired legs, new friendships and a renewed sense of why we do this. It is about people from all over the world working together in the open to build tools that anyone, anywhere, can use to map what matters to them.



Thank you 💚🫂

A huge thank you to everyone who made this week possible. Thank you to Anna for organising travel, accommodation and every detail in between, including warm clothes for the ninjas arriving from warmer climates. Thank you to the Swiss QGIS user group and everyone behind the QGIS User Conference and Contributor Meeting for bringing the community to our home. And thank you to the Rocks Resort and the Riders Hotel for being such great hosts.

From Laax, with 💚.
See you at the next Hackfest! 🥷

by Anja Ottiger at November 12, 2026 10:14 AM

November 11, 2026

Dear Reader,

We are back from Barcelona, where Smart City Expo World Congress 2026 took place from 3 to 5 November 2026 at Fira Barcelona Gran Via. This year's theme was "Urban Solutions, Real Impact", and it set the tone for three intense days.

GeoSolutions was there as an exhibitor in the Italian Pavilion (Hall 2, Stand C161). We spent the event meeting clients, partners and many new organisations we had never met before. In this post we share what we heard from them, and what we think it means for the cities planning their next geospatial platform.

What we saw in Barcelona

Municipalities and companies from all over the world came to Barcelona to show what they are building. Three topics came up in almost every conversation at our stand:

Climate resilience - flood risk, heat islands and extreme weather are no longer future scenarios. Cities need to understand where they are exposed and act before the next event. Sustainable mobility - transport networks, traffic and public space are being redesigned around data, often in real time. City planning - urban development, housing and infrastructure decisions are increasingly tested on data before they reach the ground.

What these projects share is their foundation. Behind almost every solution there is a geospatial platform that collects data from many sources, keeps it consistent and turns it into decisions. The "smart city" label is fading. What cities want now is to be resilient, and location data is how they get there.

Digital twins: from showcase to strategy

Digital twins were described again and again as the next frontier for cities. A few years ago, a digital twin was often a striking 3D model shown at events. In Barcelona, the conversation had clearly moved on.

Cities still use their twins to understand their current status: buildings, networks, environment and services, all in one place. But the real value is what comes next. A digital twin is the base for models that explore different future scenarios: what happens to a neighbourhood during a flood, how a new mobility plan changes traffic, which areas suffer most in a heatwave.

With climate change, testing those scenarios before acting has become essential, not optional. It lets cities plan with evidence, compare options and explain their choices to citizens.

The open source shift is real

The most encouraging part of the event was the people we met. Many of the organisations that stopped by were new to us, and many of them had already moved away from proprietary GIS, or never adopted it. Some started directly on open source. Others run hybrid architectures, where open source components work side by side with commercial products.

In many cases, GeoServer, MapStore and GeoNode were already part of their stack, running in production. We heard this from them directly, and it is the best confirmation of the work we do every day.

Behind many of these choices there was one recurring theme: digital sovereignty. Public administrations increasingly want to decide where their data lives, who can access it and which technologies they depend on. Open source, built on open standards, lets them keep that control instead of handing it to a single vendor.

At our stand we showed concrete examples built on these three products, from geoportals that publish and share data to applications for exploring urban data in 2D and 3D. Open source isn't the alternative anymore. For many cities, it is the standard.

Our view: why the foundation matters

A digital twin is only as good as the platform underneath it. If cities want to simulate their future, they need to own the base those simulations run on. From our experience, a city-ready geospatial platform needs four things:

Open standards. Data published through OGC standards can be reused by any tool, today and in ten years. It does not stay locked in one vendor's format. Control over data and costs. Open source removes per-user and per-server licences. Cities can scale their platform as their needs grow, and invest the budget in their own projects. Room to grow. A platform built on open, modular components can add new data sources, sensors and models without starting over. Today's geoportal becomes tomorrow's digital twin. Professional support. Open source in production still needs expertise. Long-term maintenance, security updates and fast answers when something breaks are what make it a safe choice for public administrations.

The cities we met in Barcelona are not choosing open source just because it is free. They choose it because it gives them independence, and that independence matters even more when the stakes are as high as climate adaptation.

See you next year, Barcelona

A big thank you to everyone who visited our stand, and to those who welcomed us at theirs. The conversations we started in Barcelona continue now, and we look forward to the next edition.

If your organisation is building a geoportal or a digital twin on open source, or is thinking about moving away from proprietary GIS, we can help you design, deploy and scale it:

  Contact us to learn more, the GeoSolutions team
320x100_eng

by Enrico Usai at November 11, 2026 02:30 PM

Making FAIR research infrastructures usable

What Do Geoinformation Technology Users Really Need?

Guest post by Sadra Matmir1 | TU Dortmund University / Bochum University of Applied Sciences (Hochschule Bochum)

Sadra Matmir's Master's Thesis

The Challenge: Making FAIR Research Infrastructure Useful in Practice

Open Science and FAIR principles have made significant progress in improving access to scientific data and computational research. However, an important challenge remains:

Making research outputs FAIR and providing them through research infrastructures does not necessarily mean that potential users will adopt the technologies that make them available.

Geoinformation Technologies (GITs) can provide powerful analytical capabilities, but their adoption in planning and environmental practice depends on much more than technical performance. Usability, perceived benefits, organizational requirements, and users’ technical skills all play important roles. This raises a central question:

How can we better understand the gap between GIT developers’ perspectives and the needs of planning practitioners?

I explored this challenge in my master’s thesis “Evaluating technology adoption by planners using a data-to-knowledge package for flood risk management” in spatial planning at TU-Dortmund University, building on interdisciplinary collaboration within the EU-funded AquaINFRA project. In cooperation with researchers and developers from Hochschule Bochum, Aalborg University, and 52°North, we developed the Elbe Data-to-Knowledge Package (D2KP), building on existing research on dasymetric population mapping by Ida Maria Bonnevie and colleagues2. A quick information for those who haven’t heard about the Data-to-Knowledge Package: The main objective of the D2KP is to enhance the reusability of computational research outputs by enabling users to seamlessly trace the process from raw data to analysis and knowledge generation. It contains everything that is needed to reproduce the analysis plus additional products that make reuse and interaction with the analysis easier. Further details can be found in a previous blog post.

Following the D2KP development guideline3 prepared by Markus Konkol at 52°North, we transformed Ida Maria Bonnevie’s original R-based research scripts into a modular and reproducible workflow for the German part of the Elbe River basin. The process involved restructuring the analytical code into reusable functions, preparing a Docker-based computational environment, and collaborating with the AquaINFRA development team to integrate the components into the AquaINFRA Interaction Platform (AIP) and Virtual Research Environment (VRE).

The resulting Elbe D2KP connects FAIR datasets, analytical code, and reproducible workflows. As part of my research, we demonstrated its practical application by combining the population distribution outputs generated by the Elbe workflow with HQ100 flood hazard zones. This analysis was conducted using the QGIS tool integrated into the Galaxy-based VRE, allowing users to explore the potential application of these outputs in flood risk management. During the demonstration, participants tested the Elbe D2KP and explored its results through the AIP and VRE. The entire process was carried out through a standard web browser, without requiring users to install any additional software (Figure 1).

Elbe D2KPFigure1: Overlay of Elbe D2KP workflow outputs with HQ100 flood hazard zones using the QGIS tool integrated into the AquaINFRA Virtual Research Environment (VRE). The map displays two vector layers: the subbasin population density layer generated by the Elbe D2KP workflow and the HQ100 flood hazard layer for Brandenburg.

However, the main objective of my research went beyond technical implementation. It focused on a broader question: How do different stakeholder groups perceive the adoption of geoinformation technologies ?

To investigate this, I applied Fuzzy Cognitive Mapping (FCM), a participatory, semi-quantitative method used to represent how people understand complex systems. Participants identify factors influencing the adoption of GIT, connect them through cause-and-effect relationships, and assign positive or negative weights indicating the perceived direction and strength of these relationships. The resulting cognitive maps allow different stakeholder perspectives to be visualized and compared. We used the online MentalModeler platform to collaboratively develop and visualise Fuzzy Cognitive Maps (FCMs) and conduct scenario simulations exploring how the introduction of the Elbe D2KP might influence technology adoption from practitioners’ perspectives.

The assessment was conducted through two stages of workshops. First, during the AquaINFRA partner meeting in Oslo in December 2025, developers, researchers, and project managers worked in eight groups to identify factors influencing the adoption of GIT and construct their FCMs. One of the well-connected FCM maps developed by AquaINFRA partners is presented in Figure 2.

Figure 2 . A well-connected Fuzzy Cognitive Map (FCM) developed by AquaINFRA partners during the workshop in Oslo, Norway.

In the second stage, workshops and guided sessions were conducted with planning practitioners from Stadt Bochum and Emschergenossenschaft4 in Germany in January 2026. Participants developed cognitive maps representing their perspectives on GIT adoption and were introduced to the Elbe D2KP through its analytical workflow and practical flood risk management application. Figure 3 presents the FCM developed during the Emschergenossenschaft session.

FCMsFigure 3: Fuzzy Cognitive Map (FCM) developed with water management practitioners from Emschergenossenschaft during the workshop in Germany.

Following this introduction and testing the Elbe D2KP, FCM scenario simulations were conducted to explore how the perceived introduction of the D2KP might influence different adoption-related factors within the practitioners’ cognitive maps. This approach allowed us to compare the perspectives of the AquaINFRA team and potential users while investigating the perceived benefits and challenges associated with adopting the D2KP concept by planning practitioners.

What Did We Learn?

The findings revealed an interesting difference between the perspectives of GIT developers and practitioners. While both groups recognized factors such as cost, usability, and perceived benefits, they understood their relationships differently. AquaINFRA partners generally described adoption through interconnected technical and organizational factors, whereas practitioners focused more directly on usability, integration, and benefits for their daily work.

Interestingly, substantial differences were also observed among the AquaINFRA partners themselves. Although they were directly involved in developing and implementing the AquaINFRA infrastructure, their FCMs revealed different understandings of GIT adoption. Even when participants identified similar influencing factors, they often perceived the relationships between these factors differently. This highlights that involvement in developing a GIT does not necessarily lead to a shared understanding of its adoption.

Scenario simulations introducing the Elbe D2KP into the practitioners’ cognitive maps suggested positive changes in perceived benefits and ease of integration. However, both models also indicated challenges related to user-friendliness. These results represent stakeholder perceptions and modelled scenarios rather than measured technology performance, but they highlight an important potential trade-off between analytical capabilities and accessibility.

The Takeaway: FAIR-based GIT Needs User Perspectives

This research highlights two important lessons for developing and adopting new GITs.

First, technology adoption is shaped not only by individual factors, such as usability, cost, and perceived benefits, but also by how these factors interact. Using Fuzzy Cognitive Mapping (FCM), we identified both shared concerns and differences in how stakeholders understand the relationships between them. This revealed patterns of agreement and fragmentation that might otherwise remain hidden, even among people directly involved in developing the same research infrastructure.

Second, successful adoption requires bridging the gap between developers’ perspectives and practitioners’ needs. While developers often focus on technical infrastructure and system functionality, practitioners place greater emphasis on practical benefits, usability, and integration into their existing workflows. Our findings highlight the importance of understanding these different perspectives and aligning them throughout the technology development process.

The experience within AquaINFRA demonstrates that technical quality, reproducibility, and FAIR compliance alone are not sufficient to ensure successful adoption. Equally important are clear communication of how technologies work, accessible training materials, and continuous engagement with potential users.

Ultimately, making research infrastructure FAIR is an essential step toward reusability, but turning reusable research into technology that people can confidently adopt requires a shared understanding between developers and practitioners.

 

 

References

1 Sadra Matmir is a research associate at Bochum University of Applied Sciences (Hochschule Bochum), working on the EU-funded AquaINFRA project, focusing on reproducible geospatial workflows, Open Educational Resources (OERs), and technology adoption. He holds master’s degrees in Geoinformation Science from the University of Twente in the Netherlands and Spatial Planning from TU Dortmund University in Germany.

2 Bonnevie, I. M., Hansen, H. S. and Schrøder, L. (2024): Dasymetric Algorithms Using Land Cover to Estimate Human Population at Smaller Spatial Scales. ISPRS International Journal of Geo-Information, 13(12), p. 427. https://doi.org/10.3390/ijgi13120427

3 Konkol, M. (2024): User Guide: Creating a Data-to-Knowledge Package. Zenodo. https://doi.org/10.5281/zenodo.15772477

4 The Emschergenossenschaft is a public water management association responsible for the Emscher River Basin in Germany’s Ruhr region. Founded in 1899, it focuses on wastewater management, flood protection, river restoration, and sustainable water resource management.

by sadramatmir at November 11, 2026 07:30 AM

November 10, 2026

Dear all,

The CRO is pleased to announce the list of new OSGeo Charter Members.

  • Dirk Stenger from Germany
  • Jin Igarashi from Japan
  • Matthias Mhor from Germany
  • Luiza Marques Fonseca dos Santos from Brasil
  • Berit Mohr from Germany
  • Dominik Weckmüller from Germany
  • Jonathan Beliën from Belgium
  • Roel Huybrechts from Belgium
  • David García from Uruguay
  • Ignacio Talavera from Uruguay
  • Yasuto Furukawa from Japan
  • Alen Mangafić from Slovenia
  • Kilian Paenen from Belgium
  • Kaue de Moraes Vestena from Brasil
  • Corey T. White from United States of America
  • Hinako Iseki from Japan
  • Colin Mazengarb from Australia [0]
  • Alexander Kmoch from Germany
  • Salvatore Fiandaca from Italy
  • Patrícia Iribarrem from The Netherlands
  • Adam Stewart from Germany
  • Isaac Ullah from United States of America
  • Charlotte Flasse from Belgium
  • Denilson de Jesus from Brasil

You may visit the nominations page [1] to learn more about the candidates.

This year there were 24 valid nominations and all were accepted. 260 charter
members cast their vote, with each nominee attaining more than 130 votes. The
OSGeo Foundation now counts 491 active Charter Members [2].

The board approved the new members days ago [3].

Warm regards,

Luís de Sousa
(Your 2026 OSGeo CRO [4])

[0] Pending
[1] https://wiki.osgeo.org/wiki/New_Member_Nominations_2026
[2] https://www.osgeo.org/about/charter-members/
[3] https://www.loomio.com/d/UNcQTlOw/motion-to-approve-the-new-charter-members
[4] https://wiki.osgeo.org/wiki/Chief_Returning_Officer

1 post - 1 participant

Read full topic

by OSGeo_News at November 10, 2026 10:20 AM

FOSS4G North America 2026 in Sacramento, GeoSolutions sponsored break

Dear Reader,

We are back from FOSS4G North America 2026, held in Sacramento, California, from November 2 to 4, 2026, and we want to share what we presented and what we saw.

GeoSolutions was there with Simone Giannecchini and Andrea Aime for the whole conference, at our table in the exhibit area and in the session rooms for our four talks in the Technical track. GeoSolutions supported the event as a Bronze sponsor and also sponsored the Tuesday afternoon break.

Below you will find the slides of all four talks, embedded directly from Google Slides, plus a short video with a live demo of the AI tools we presented.

AI-dministering GeoServer and MapStore

An early look at the Model Context Protocol (MCP) servers we are building for GeoServer and MapStore. They let today's AI assistants help with real administration tasks, such as publishing layers, tuning caches and diagnosing issues, with guardrails to keep production deployments safe.

Andrea also recorded a demo that shows the MCP servers at work on a live GeoServer and MapStore setup.

State of GeoServer

New features, community updates and recent developments of GeoServer, for expert users, developers and anyone curious about what GeoServer can do for them.

GeoServer VS GeoServer: fight!

GeoServer benchmarked against itself. Each experiment measures the real performance cost of a common operator decision: data formats, security, logging, CRS handling, JVM settings and scaling.

Precision farming with GeoServer: lessons learned and future directions

Ten years of experience ingesting, managing and disseminating drone, Earth observation and agricultural machinery data at scale for the precision farming industry, with GeoServer deployed in the cloud.

What we saw in Sacramento

AI agents for GIS work were one of the main threads of the conference. A good example was the talk by Dara O'beirne and Silas Toms, Geospatial AI Agents in Practice: Sacramento Open Data and Hermes, where the open source Hermes agent framework orchestrates QGIS, GDAL, PostGIS and web mapping tools to automate the creation and management of web GIS outputs, with human approval before anything gets published. It is the same direction we are taking with our MCP servers for GeoServer and MapStore: let the agent take care of the repetitive work, and keep people in control of what goes into production.

Cloud native formats were the other big thread. Zarr, GeoParquet and Cloud Optimized GeoTIFF (COG) keep maturing and are becoming the standard way to store and share large raster and vector datasets on object storage, while DuckDB is turning into a go-to tool to query them directly, with no database server in between. GeoServer is already part of this picture, with community modules for COG, GeoParquet and DuckDB, and this is an area we are following closely.

A big thank you to the FOSS4G North America 2026 organizers and volunteers for a great conference, and to everybody who attended our talks or stopped by our table for a chat. We look forward to seeing you again at FOSS4G North America next year!

As always, call on us, the core code developers and experts on:

  • GeoServer, the leading open source server to publish geospatial data at scale.
  • MapStore, our modular open source WebGIS product to create and publish geospatial data as maps, dashboards and geo stories.
  • GeoNode, the open source GIS platform to create a complete and interoperable spatial data infrastructure.

If you are interested in learning more about how we can help you achieve your needs with MapStore, GeoServer, GeoNode and GeoNetwork through our Enterprise Support Services, Professional Training Services and Subscription Services please contact us!

The GeoSolutions team,

320x100_eng

by simone giannecchini at November 10, 2026 08:47 AM

November 07, 2026

November 04, 2026

On October 19, 2026 the GeoServer project announced three releases: 3.0.2, 2.28.6 and 2.27.7. For most deployments these are maintenance and security updates. For organizations that must run their geospatial infrastructure under formal cryptographic requirements, 3.0.2 carries something more: a new FIPS community module, developed by GeoSolutions, that lets GeoServer run on top of a FIPS 140-3 validated cryptographic module. In this post we look at what the module enables, the engineering behind it, and what teams should plan before adopting it.

What FIPS compatibility enables

FIPS 140-3 is the United States government standard for cryptographic modules, and a hard requirement in many federal, defense and regulated environments. Software running in those environments is expected to perform all cryptographic operations inside a validated module, operating in its approved mode.

The new FIPS community module makes that possible for GeoServer. It replaces the standard Bouncy Castle library with the FIPS-validated Bouncy Castle build (bc-fips 2.1.2 as the cryptographic provider, bcpkix-fips 2.1.10 for certificates and CMS), registers it ahead of the default Java providers, and runs it in approved-only mode, where requests for non-approved algorithms fail instead of silently falling back. Configuration and user passwords are stored with AES-GCM, the keystore moves to the BCFKS format, and a new FIPS tab under Server Status shows the cryptographic setup at a glance: crypto module state, approved-only mode, operating system FIPS mode, provider position and the algorithms GeoServer needs. The same information is exposed in the module status returned by the REST resource /rest/about/status.json, which is convenient when several instances have to be checked.

The FIPS tab under Server Status in GeoServer 3.0.2, showing the cryptographic module state, approved-only mode and provider position

The FIPS status page in GeoServer 3.0.2. Image from the GeoServer 3.0.2 release announcement, CC BY.

One distinction matters when evaluating this. FIPS validation applies to the cryptographic module and its conditions of use, not to the products that integrate it. As the NIST CMVP FAQ makes clear, embedding a validated module does not make the embedding product validated. The module gives GeoServer a concrete, reviewable path to FIPS compatibility; compliance of the overall deployment remains something each organization establishes through its own configuration and accreditation process.

The engineering behind it

Making a large Java application work under approved-only cryptography is not a matter of swapping a library. GeoSolutions developed the module together with the core changes and the build-level testing needed to support it. The work, led by Andrea Aime and visible in the public pull requests on the GeoServer repository (#9855 for the main branch and #9880 for the 3.0.x backport, both merged on August 27, 2026), covers three areas:

  • Changes across the GeoServer core to make encryption pluggable and compatible with different algorithm sets, including the move from DES to AES for URL parameter encryption and a keystore named after its format.
  • The module itself, which installs the validated provider through a new core extension point, reports what it found, and adds the status tab, together with the AES-GCM password encoder and master password provider that the core now offers next to the existing ones.
  • The machinery to build and test under FIPS constraints: a Maven profile that builds GeoServer against the FIPS provider across the whole tree and fails if any dependency pulls the regular library back in, a second profile that makes a normal development machine behave like a FIPS one, and scripts for a virtual machine where the real thing is checked.

That last point deserves a word. The module is compiled and tested inside a Rocky Linux 9 virtual machine with FIPS mode enabled. A container is not enough: FIPS mode is a property of the kernel, and a container uses the kernel of its host. On the VM the build runs with FIPS mode active and executes the tests of every module, then the CITE suite (the OGC conformance tests) runs with the kernel, the system crypto policy and the Red Hat Java runtime all in FIPS mode. This is where modules using non-approved algorithms show up. Rocky Linux is a rebuild of RHEL and is fine for testing; organizations that need to pass an accreditation should run on a validated distribution.

Andrea Aime, who led the work, puts it this way: "Making GeoServer run under approved-only cryptography was less about the module and more about the core: encryption had to become pluggable, the tests had to stop assuming a particular set of algorithms, and we needed a build that fails the moment a dependency pulls non-FIPS cryptography back in. The FIPS virtual machine is what catches that; a container cannot, because FIPS mode is a property of the kernel."

Three layers to review for a GeoServer FIPS deployment: the GeoServer FIPS module, the Bouncy Castle FIPS provider, and the Linux and Java configuration

A GeoServer FIPS deployment: the module, the validated provider, and the operating environment. Deployment configuration and validation remain the responsibility of the organization.

The work was commissioned by a leading public safety and security technology company with formal FIPS requirements, which deployed the module in their development and staging environments and ran their own test suite against it before the public release. The result went upstream as a community module rather than staying a private fork, which is the approach we take whenever a customer requirement is of general interest: the customer gets a maintained feature, and every GeoServer user gets the option.

The release announcement also credits GeoSolutions engineers for release testing and the OGC API Maps work by Andrea Aime, and for the GeoFence integration for GeoServer 3 by Emanuele Tajariol. The releases themselves are a community achievement, with contributions and release duties shared with GeoCat, Camptocamp and the other organizations listed in the announcement.

What teams need to plan

The documented path for running GeoServer under FIPS is on Linux, with the operating system and the Java runtime properly configured and the module operating in approved-only mode. Three points deserve attention.

First, a FIPS instance requires a new data directory. An existing data directory cannot be opened in place, because password encoding and keystore format change, and there is no migration tool yet. Unencrypted configuration such as layers, styles and service settings can be carried over, while the security configuration is rebuilt. Second, the module does not configure the operating system: enabling FIPS mode at the OS level is a separate step, and the FIPS status page tells you whether it is active. Third, this is a community module: it is not part of the 3.0.2 extension downloads and is distributed through the GeoServer community builds, so plan the deployment with that in mind, and review extensions and external integrations, since anything performing cryptography outside the validated provider needs to be checked against your requirements.

Maintaining GeoServer in production

Work like this is one example of what it takes to keep GeoServer dependable in demanding environments: changes in the core, upstream maintenance, testing infrastructure, and the follow-through across releases. It is the same engineering that backs our day-to-day support work, from diagnosing production incidents to planning upgrades across versions. Our thanks go to everyone in the GeoServer community who contributed to these releases.

If you are interested in learning more about how we can help you achieve your needs with GeoServer, MapStore, GeoNode and GeoNetwork through our Enterprise Support Services, Professional Training Services and Subscription Services please contact us!

The GeoSolutions team

320x100_eng

by simone giannecchini at November 04, 2026 06:42 PM

Empowering Conservation Through Open Technologies with 52°North and PEOPLE-ECCO

PEOPLE ECCO projectEmpowering Conservation Through Open Technologies with 52°North and PEOPLE-ECCO

The Challenge

Non-Governmental Organizations (NGOs) are key actors in the conservation and restoration of ecosystems worldwide. However, practice-oriented conservation groups face a major hurdle: evaluating the real-world impact of their management activities over large geographic areas. Traditional monitoring methods rely on labor-intensive on-the-ground surveys, which are difficult to sustain at scale. While satellite Earth Observation (EO) data, such as Copernicus Sentinel-2, offer wide-scale coverage and long-term time series, using them effectively requires complex domain knowledge, spatial data handling, and specialized data processing skills.

This week’s challenge is:

How can we build an accessible, cloud-native web platform that transforms complex satellite Earth Observation data into intuitive environmental indicators and actionable metrics for non-technical conservation experts?

The Stakeholders and Co-Design

To bridge the gap between space infrastructure and ground-level species conservation, the European Space Agency (ESA) funded the PEOPLE-ECCO (Enhancing Ecosystems Conservation through Earth Observation Solutions, Capacity Development and Co-design) project under its EO4Society program. Led by the University of Twente (ITC), the consortium brings together technical and domain partners – 52°North, Hatfield Consultants, and DHI Consulting – alongside six key NGO “Early Adopters” across four continents:

  • African Parks: Monitoring protected areas across multiple African nations.
  • Bulgarian Society for the Protection of Birds (BSPB): Preserving critical bird habitats and grassland ecosystems in Bulgaria.
  • IUCN Vietnam: Protecting forest and wetland ecosystems.
  • Lebanon Reforestation Initiative: Restoring forested landscapes and building community resilience in Lebanon.
  • Prince Edward Island Watershed Alliance (Canada): Tracking watershed health and cold-temperate aquatic ecosystems.
  • Reef Check Malaysia: Conserving high-biodiversity coral reefs, seagrass beds, and coastal marine habitats.
PEOPLE ECCOFigure 1: Early Adopters and their regions

Through hands-on Living Labs (such as at BioSpace25 conference) and targeted regional co-design workshops (e.g., in Kuala Lumpur and Plovdiv), these non-technical stakeholders worked directly alongside the technical developers to co-design the system requirements, refine workflows, and shape the user interfaces.

The Technical Architecture

As the software architecture and platform engineering lead, 52°North designed, implemented and deployed the technical foundation.

PEOPLE ECCO PlatformFigure 2: High-level architecture of the PEOPLE-ECCO platform

We also developed the open-source PEOPLE-ECCO Platform to address the needs of GIS professionals, domain specialists, and public stakeholders:

  • Central API (ecco-api): Designed as a RESTful API, ecco-api serves as the primary backbone of the system. It enforces access permissions, handles OpenID Connect (OIDC) authentication via Keycloak, manages conservation sites configurations (area of interest, applicable algorithms), while handling algorithm execution and result retrieval.
  • Hybrid Processing Engine: Heavy satellite processingEO data processing – such as the discovery and retrieval of Sentinel-2 data, cloud masking, band sub-setting, spatial resampling and calculating spectral indices (e.g., NDVI, SAVI, NBR) – is offloaded directly to the openEO Platform within the Copernicus Data Space Ecosystem (CDSE). The Prefect workflow engine, Garage S3 storage and PostgreSQL/PostGIS databases enable seamless custom statistical analyses and post-processing. The engine tracks asynchronous batch jobs, automates credentials management for the CDSE using dedicated service accounts (so users do not need to manage these on their own) and provides outputs and results via standardized SpatioTemporal Asset Catalogs (STAC).
  • Web User Interface (ecco-web): Built with the Open Pioneer Trails framework, This browser-based web application enables non-technical users to run pre-defined, parameterizable PEOPLE-ECCO solutions. They can visually explore time series, inspect Cloud Optimized GeoTIFFs, monitor execution progress and download indicator datasets (see figure 3).
  • Standardized Integration and FAIR Execution: Custom models from consortium partners are packaged as Docker containers (ecco-algorithm-base) using Common Workflow Language (CWL) and OGC Earth Observation Application Packages (EOAP). Outputs are served via standardized SpatioTemporal Asset Catalogs (STAC), adhering to ESA APEx guidelines for long-term sustainability.
PEOPLE-ECCO PlatformFigure 3: User Interface of the PEOPLE-ECCO platform

Today’s Take Away

The PEOPLE-ECCO project demonstrates how open source software, cloud-native standards and collaborative co-design can enable the power of satellite data for ecosystem conservation. By combining openEO cloud processing, dockerized CWL workflows and an intuitive web platform, the PEOPLE-ECCO project has provided NGOs with a modern and scalable toolset to support monitoring, restoration and conservation of ecosystems. All platform components, algorithms, and demonstration outputs developed under PEOPLE-ECCO are open-source and freely accessible to the broader community.

Explore, use, and build upon these contributions directly!

by Matthes Rieke at November 04, 2026 07:30 AM

November 02, 2026

As part of our Security project for QGIS initiative, we identified a work package titled “Improve Memory Safety.”

Having worked on this topic over the last few months, here is a summary of the issues involved and what has been accomplished so far.

It’s not an easy thing to present this topic. I’ll try not to dive into too much technical details to focus instead on the broader objectives and implications.

Once upon a time, in the United States…

In November 2022, the NSA published a report on software security, in which it stated:

Microsoft and Google have each stated that software memory safety issues are behind around 70 percent of their vulnerabilities. Poor memory management can lead to technical issues as well, such as incorrect program results, degradation of the program’s performance over time, and program crashes.

In other words: 70% of software vulnerabilities stem from memory management issues.

NSA recommends that organizations use memory safe languages ​​when possible and bolster protection through code-hardening defenses such as compiler options, tool options, and operating system configurations.

The NSA recommends using “Memory Safe Languages” (MSLs) or “hardening” the code. QGIS consists of approximately 1.5 million lines of C++ code, a language not “memory safe” by default. I am therefore opting for the “harden the code” approach, rather than a rewrite which, I have to admit, would have had the “advantage” of keeping me employed until retirement.

What’s the problem?

C++ is not a “memory-safe” language by default, as it does not require the explicit management of the lifecycle of the memory segments it uses.

 

That sentence didn’t make any sense to you, don’t worry, it won’t hinder your understanding of what follows.

C++ developers are expected to be careful: they must ensure they don’t forget to deallocate memory that was previously allocated, while also avoiding deallocating the same memory multiple times, errors that can lead respectively to memory bloat or program crashes.

These memory management issues can be exploited by malicious actors to inject code into a program, potentially allowing them to steal passwords or gain unauthorized access.

 

A malicious actor

Work performed

Fortunately, C++ offers control structures known as smart pointers, which help manage the memory lifecycle. Using them helps prevent memory leaks and crashes, while also limiting the attack surface.

QGIS currently makes limited use of these. The goal, therefore, is to expand their adoption throughout the codebase and prevent the addition of any new code that fails to utilize them.

To achieve this, I developed a program that rewrites the code to incorporate smart pointers, followed by an extensive review process to ensure no new errors were introduced.

A QGIS contributor in the middle of reviewing a pull request

Why not use AI?

Nowadays, it’s hard to discuss any software engineering topic without bringing up AI (at least we don’t hear about blockchain anymore!), so I feel compelled to answer the question: “Could AI have been used for this task?”—or, to use the terminology favored by “tech-bros,” could it have been “AI-powered”?

The answer is YES. But also NO. For one thing, the QGIS project is still determining its policy regarding AI; for the time being, a moratorium is in place that prohibits its use within the QGIS core.

Furthermore, it would have required a more thorough review. My migration program is deterministic—when it makes a mistake, it always does so in the same way. The same cannot easily be said for a probabilistic machine.

So, does this mean we’re now “memory safe”?

Not quite. We’ve reached a significant milestone, but there’s still more to do. This work will continue over the coming months.

In parallel, I’ve also begun a related project, supported by a QGIS.org grant. The goal is to replace SIP_FACTORY annotations with unique pointers. Explaining the technical details of this, however, would likely scare off the few readers who have made it this far!

This initiative is part of a broader effort, as we believe that all security-related issues must be addressed simultaneously and with equal rigor. After all, what’s the point of installing a reinforced front door if you leave the garage door wide open?

To be continued…

We are committed to a process of continuous improvement—both for the QGIS codebase itself and for the workflows surrounding how the software is contributed to and distributed. It is worth noting that this initiative is not just about security; it also helps to reduce software crashes and memory footprint.

It requires financial support. If you would like to contribute, or if you have any other questions regarding QGIS, please do not hesitate to contact us at mailto:infos+qgis@oslandia.com.

You can stay informed by subscribing to our newsletter and following us on LinkedIn.

by Julien Cabieces at November 02, 2026 11:38 AM

October 31, 2026

Soon after I posted my One Hundred Famous Views of Edo Map, Keir Clarke posted about another map of Japanese woodblock prints on his Maps Mania blog, well worth a read if you want to learn a bit about Japanese landscape art in the 19th C. It turns out that there are a lot more than Hiroshige’s One Hundred (which are actually 119) and someone had made a map of 297 of these prints across 5 series which had lost its base map and had a couple of other glitches. Keir threw down a challenge “Perhaps Steven could take a sneak peek at the map’s JavaScript, which contains the coordinates of all the woodblock prints featured, and use them to expand the scope of his own map.” “How difficult could that be?”, I thought.

I searched Wikipedia and found articles on each of the other series and I used the Ukiyo-e map to get the locations (thanks to whoever made that) and Claude checked every one against Wikipedia and Wikidata. 12 were clearly wrong (e.g. the Naruto Whirlpools sat in Tokyo Bay), so we fixed those. Accuracy is moderate, which is all it needs to be.

While building this expanded version Claude suggested adding a couple of quite neat features that I probably wouldn’t have thought of:

  • The Tōkaidō road is drawn station to station
  • The sightlines from each of Hokusai’s viewpoints to Fuji’s summit are drawn and an exaggerated Mount Fuji is inserted
  • Each series has the option to step through all the cards in that series
  • Each image has a shareable link and can be expanded to full size
  • I added a couple of new features – wherever possible the clusters unpack in one click and selecting a series zooms to the limits of that series

Known issues: some viewpoints are disputed or only placed at the town or province shown, and only 107 of the 178 new prints have a Wikipedia “About” text.

I thought this would be really easy after making the first map, but adding 4 more series turned out to add a bit of complexity and needed more thought and input from me rather than sitting back and letting Claude do it all.

I like the way the clusters are represented and wandering the Tokaido route is neat. I think it has worked out very well and is probably an improvement on the original map that prompted this afternoon’s fun.

<p>The post Ukiyo-e “Pictures of the Floating World” first appeared on KnowWhere.</p>

by Steven at October 31, 2026 05:20 PM

October 30, 2026

From raster to histogram

Visualisation is a key part of any analysis. It is useful not only at the end, when presenting the results, but also throughout the analysis itself. A quick plot can help you interpret intermediate results and decide what to do next.

R and Python offer excellent tools for creating visualisations. When working in GRASS, however, I do not always want to export or reshape the data, or have to remember, or look up, the code needed to create a simple figure. Sometimes, I just want to create a plot directly from within GRASS. At the same time, it should offer enough options to fine-tune the result for online or print publication.

At some point, I realised that it was sometimes easier to spend a little time creating an addon for exactly that purpose. Over time, this has resulted in a series of addons for creating different types of visualisations, including bar plots, line plots, and scatterplots.

The latest addition is r.histogram, which creates histograms based on raster values. GRASS actually already provides two modules for creating histograms. This new addon, however, offers more options for fine-tuning their appearance by taking advantage of Matplotlib’s powerful plotting capabilities. Below are a few examples from the manual page.

Examples

The examples below use the data from the Raleigh, North Carolina sample dataset.

The first example draw a histogram of the elevation raster, setting the plot dimensions and DPI.

g.region raster=elevation
r.histogram map=elevation plot_dimensions=5,4 \
  dpi=100 output=r_histogram_01.png

To change the appearance of the plot, you can tweak individual elements, but also apply a matplotlib style. Below, the ggplot style is used.

r.histogram map=elevation plot_dimensions=5,4 \
  dpi=100 frequency=percent style=ggplot \
  output=r_histogram_02.png

For a bit more colorfull result, we can draw the histogram with each bar colored based on the corresponding elevation raster color table. And we can express the frequencies as percentages.

r.histogram -c map=elevation plot_dimensions=5,4 \
  dpi=100 frequency=percent style=_mpl-gallery \
  output=r_histogram_03.png

And one last example, let’s draw a horizontal histogram with a grid, a reduced relative bar width, and a dark background:

r.histogram -hc map=elevation plot_dimensions=5,4 \
  dpi=100  rwidth=0.9 style=dark_background \
  x_label="Number of cells" y_label="Elevation (m)" \
  output=r_histogram_04.png

The addon lets you modify more elements of the plot, including plot title, x- and y-axis labels, fontsize, border line width, relative bar width, transparent background, and colors of the bars and bar borders. And you can create your own Matplotlib styles and apply them to the plot.

by Paulo van Breugel at October 30, 2026 11:00 PM

The PostGIS Team is pleased to release PostGIS 3.7.0! Best Served with PostgreSQL 19 RC 1 , GEOS 3.15.0 , postgis_tiger_geocoder 2025.2 , and address_standardizer.

This version requires GEOS 3.10+, PostgreSQL 14-19, Proj 6.1+, and libgmp. To take advantage of all postgis extension features, GEOS 3.15+ is needed. To take advantage of all postgis_sfcgal extension features SFCGAL 2.3+ is needed. Python 3 is a new requirement to build the documentation images. Visual examples in the docs are off by default. To build docs with them, configure with --with-visual-examples and make sure you have a running PostgreSQL instance; they are then generated automatically when building the docs (or explicitly with make -C regress visual-examples).

This release contains fixes since 3.7.0rc3 release.

3.7.0

This release is a major release, it includes bug fixes since PostGIS 3.6.4 and new features.

by Regina Obe at October 30, 2026 12:00 AM