Discover the highlights from FOSS4G:HU 2026 in Budapest, featuring open source GIS insights, QGIS and Mergin Maps field data workflows, and community networking.

You must be logged into the site to view this content.

On 3 June 2026, the European Commission adopted a new package of measures to strengthen Europe’s technological sovereignty.

The package includes two legislative proposals —the Chips Act 2.0 and the Cloud and AI Development Act— together with the European Open Source Strategy and a strategic roadmap for digitalisation and artificial intelligence in the energy sector.

This is a relevant step because it places issues such as digital autonomy, control over critical technologies and infrastructure, the reduction of dependencies on providers, and the strategic role of open source at the heart of the European debate.

In this context, the geospatial dimension must be a key part of technological sovereignty. Much of the information managed by administrations, companies and public organisations has a territorial component. Therefore, spatial data infrastructures, geoportals, corporate GIS systems, digital twins, mobile field applications and territorial analysis platforms are part of the critical digital infrastructure of many organisations. Decisions in areas such as defence, emergencies, urban planning, environment, mobility, agriculture, tourism, energy and infrastructure management are based on them.

Technological sovereignty also means controlling geographic data, map services, interoperability standards, APIs, publishing platforms and the ability to evolve systems without critical dependencies.

Open source software and open standards are a practical way to move in that direction: more autonomy, more transparency, more reuse and more resilience.

gvSIG was born precisely with this vision: to build open, interoperable and sustainable geospatial technology at the service of administrations, organisations and companies that need to maintain control over their territorial information. European technological sovereignty is also built from the territory.

El pasado 3 de junio de 2026, la Comisión Europea adoptó un nuevo paquete de medidas para reforzar la soberanía tecnológica de Europa.

El paquete incluye dos propuestas legislativas —el Chips Act 2.0 y el Cloud and AI Development Act—, junto con la Estrategia Europea de Software Libre y una hoja de ruta estratégica para la digitalización y la inteligencia artificial en el sector energético.

Es un paso relevante porque sitúa en el centro del debate europeo cuestiones como la autonomía digital, el control de tecnologías e infraestructuras críticas, la reducción de dependencias respecto a proveedores y el papel estratégico del software libre.

En este contexto, la dimensión geoespacial debe formar parte esencial de esa buscada soberanía tecnológica. Gran parte de la información que gestionan las administraciones, las empresas y los organismos públicos tiene una componente territorial. Por ello, las infraestructuras de datos espaciales, los geoportales, los sistemas SIG corporativos, los gemelos digitales, las aplicaciones móviles de campo o las plataformas de análisis territorial forman parte de la infraestructura digital crítica de muchas organizaciones.

Sobre ellas se toman decisiones en defensa, emergencias, urbanismo, medio ambiente, movilidad, agricultura, turismo, energía o gestión de infraestructuras.

La soberanía tecnológica también implica controlar los datos geográficos, los servicios de mapas, los estándares de interoperabilidad, las APIs, las plataformas de publicación y la capacidad de evolucionar los sistemas sin dependencias críticas. El software libre y los estándares abiertos son una vía concreta para avanzar en esa dirección: más autonomía, más transparencia, más reutilización y más resiliencia.

gvSIG nació precisamente con esa visión: construir tecnología geoespacial abierta, interoperable y sostenible, al servicio de administraciones, organizaciones y empresas que necesitan mantener el control sobre su información territorial. La soberanía tecnológica europea también se construye desde el territorio.

I asked a locally-downloaded LLM to compute the cost of a car trip using natural language. No calls to any cloud service, just a model queried by an inference tool running on my own machine.

The Setup

The machine used for this excercise is a LemurPro laptop from around 2020, has a 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz CPU and 16GB of RAM. No GPU.

The Procedure

1. I downloaded the unsloth/gemma-4-E4B-it-qat-UD-Q4_K_XL model from Hugging Face - about 4GB in size.

2. I built and installed llama-server from the llama.cpp project - version: 9570 (3ac3c20c9).

3. I ran llama-server -m gemma-4-E4B-it-qat-UD-Q4_K_XL.gguf

4. I built and installed ferrum from the Ferrum project - version 0.4.17.

5. I configured ferrum to use the local llama as provider

6. I invoked: time ferrum -p "<prompt>"

The Prompt (in Italian)

ho percorso 165.5km avendo un consumo medio di 5.9L/100 - il carburante costa 1.99€ al litro, quanto ho speso?

Translation: “I drove 165.5km with an average consumption of 5.9L/100 - fuel costs 1.99€ per liter, how much did I spend?”

The Response

The model answered:

Ho speso circa 19,43 €

Translation: “I spent about 19,43€”

And then provided a few details on how it computed that value.

I cross-checked with a specialized online service that calculates travel costs given start/destination addresses, and it gave the same figure (about 20 €). The model got it right.

Timing

real: 1m43.607s
user: 0m0.029s
sys:  0m0.005s

Note that the user and sys times don’t make much sense as the timed process was the client while most of the work was done by the server ( the inference tool ).

This experience shows:

1. That we can control the inference tool (llama.cpp is Free Software, distributed under the MIT License).

2. What timings we can expect with a 6-years old CPU-only laptop and a freely available LLM model.

3. How natural language (even if non-english) can be used to interact with the model.

What’s still to be found out:

I still don’t know how to control the LLM model itself

1. Running the same prompt a second time might produce a different output (this may be obtainable, although at this stage I still don’t know how to do it).

2. The output we get depends on the “procedure” used to create the LLM, that procedure is opaque to us (what is the source code of an LLM model?)

Comment welcome on the Fediverse: https://floss.social/@strk/116732586142201548

---

Las Jornadas de SIG Libre de Girona han sido siempre un referente para Geomatico … porque han sido también la cuna de nuestra empresa, allá en 2011. En estos más de 15 años de conferencias hemos presentado multitud de charlas que celebran la esencia del desarrollo abierto: colaborar, aprender y devolver algo a la comunidad. Cada una aporta una perspectiva que invita a experimentar, contribuir y seguir construyendo tecnología que sirva a todos.

GeoServer 3.0 is now generally available. This post is not a feature announcement, those have been written, and the release notes cover the details. This is something we get to do less often: closing the loop on a promise. The modernisation work the community funded is finished and shipping, and we want to account for what that funding set out to achieve and what it delivered.

The result is a platform brought back onto a current, supported foundation. The work reached across the wider ecosystem rather than GeoServer alone, and the scope the campaign promised has been covered.

The bet the community made

The case for GeoServer 3 was clear. Spring 5 was reaching the end of security support, and staying on a supported, modern Java platform meant moving to JDK 17. That upgrade was the trigger for much of what followed, because it could not happen in isolation: it cascaded into Spring 7, Jakarta, modern servlet containers, and updated libraries across the stack, and the ageing image-processing components had to be replaced along the way. None of this is the kind of work that wins a feature vote, yet all of it keeps GeoServer current and dependable for the years ahead. Our goal was to take this foundational work directly, in one coordinated effort across the whole ecosystem, rather than letting it pile up.

Funding it required a structure built on trust. The financial target was 550,000 €. Camptocamp, GeoCat, and GeoSolutions each contributed 50,000 €, and the consortium provided coordination, delivery capacity, and co-funding to move the project forward. That left a community funding goal of 400,000 €, pledged by sponsors, community members, and individual donors during a commitment phase, with funds collected only once the target was reached, so the work could begin fully funded rather than at risk of stalling partway. In May 2025 the campaign passed its goal, and the work began fully funded. GeoServer 3.0 is the moment it pays out.

What the funding delivered

GeoServer 3 set out to modernise the platform from the foundation up, and that is what this release delivers. The work was a coordinated programme rather than a single change, where a handful of major upgrades each set off a chain of smaller, necessary changes across the codebase. The items below are the headline changes that triggered much of the surrounding effort.

A modern Java foundation. The GeoServer ecosystem now runs on JDK 17 and Spring 7, the central upgrade that drove the rest of the work and brings GeoServer back onto a current, supported stack. That move cascaded into Jakarta, modern servlet containers, and a wide set of supporting libraries that all had to be carried forward together. The project worked through the dependency tree end to end, so the platform sits on a clean, maintainable base.

Modern raster processing. ImageN has replaced the legacy image-processing engine, putting raster processing on a modern foundation that is far easier to maintain going forward.

Reinforced security. Security and vulnerability management have been strengthened throughout, putting GeoServer on a stronger footing for the kinds of compliance and assurance its users increasingly need.

A refreshed administration experience and documentation. The administration interface has been rebuilt with a new context-driven design, and the documentation has been refreshed and updated alongside it.

Just as importantly, this was never only about GeoServer. The funded work carried across the ecosystem, and 3.0 ships together with GeoTools and GeoWebCache, with the integration work for GeoServer Cloud following on, making GeoServer well suited to cloud-native and containerised deployments. For most deployments the upgrade from 2.28.x is straightforward, with no changes required to the data directory. The migration guide provides the necessary instructions for the rest. The release candidate phase let organisations prove all of this in their own environments, and that feedback shaped the final release.

All of this scope was delivered and is available now in the GeoServer 3.0 release.

Thank you

GeoServer is critical infrastructure for countless organisations, and keeping a platform like that healthy depends on funding the unglamorous foundational work that rarely attracts attention on its own. That a community came together to back this effort, and saw it through to a successful delivery, is a meaningful example of how open source can sustain itself when its users choose to invest in it.

That investment had a lot of people behind it. Thank you to every organisation that pledged, every individual who donated, and everyone who tested, reported, reviewed, and contributed code: this release exists because you decided it should. Thank you also to the consortium teams at Camptocamp, GeoCat, and GeoSolutions, who carried it from a funding target to a shipped release.

GeoServer 3 is the foundation for everything the project does next. It is here because the community built it together.

GeoServer 3 is supported by the following organisations:

Individual donations: Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Jose Macchi, Peter Smythe, Sajjadul Islam, Sebastiano Meier, Stefan Overkamp.

GeoServer 3.0.0 release is now available with downloads (bin, war, windows), along with docs and extensions.

This is a stable release of GeoServer 3.0.x series. GeoServer 3.0.0 is made in conjunction with GeoTools 35.0, and GeoWebCache 2.0.0.

Thanks to Jody Garnett (GeoCat), and Peter Smythe (AfriGIS) for making this release.

Security Considerations

This release addresses security vulnerabilities and is an important upgrade for production systems.

• GEOS-12043 CVE-2025-27511 JNDI Vulnerability in DB2 Store Connection
• GEOS-11920 CVE-2025-58175 Server-Side Request Forgery (SSRF) Vulnerability in XML entity resolution
• GEOS-11918 CVE-2025-52465 Arbitrary file write vulnerability in Master Password Dump Page
• GEOS-11777 CVE-2024-45747 Server-Side Template Injection (SSTI) vulnerability in processing FreeMarker templates

The use of the CVE system allows the GeoServer team to reach a wider audience than blog posts.

See project security policy for more information on how security vulnerabilities are managed.

Welcome to GeoServer 3

We are overjoyed to share the initial release of GeoServer 3 with our community, this is the final stretch of a long road, a year of development, and a lot of planning and support to make it all happen. Thanks to all the organizations and individuals supporting GeoServer 3.

Straightforward upgrade

Special care has been taken to ensure a seamless upgrade from GeoServer 2.28.x:

1. Important: We have made no changes to the GeoServer Data Directory.

2. A few modules have migrated from core to extensions:

   • WCS 1.0 and WCS 1.1
   • World Image and ArcGRID raster data sources.
   • KML output format

   The pure Java H2 database is no longer provided.

3. The log file location setting is now managed using the GEOSERVER_LOG_LOCATION application property.

4. The NetCDF index support has been simplified and is now self-contained. With this improvement, NetCDF no longer needs a database or local .idx files to operate.

   Instructions are provided for how to clean up these now unused files.

5. The new OIDC plugin is now available as a full extension.

   This plugin takes over the responsibilities of the previously available Keycloak and OAuth2 plugins. For guidance on upgrading please see the detailed migration guide.

Please see the upgrade instructions for details.

Thanks to the GeoServer 3 Sponsors

GeoServer 3 would not exist without the organizations and individuals who supported the GeoServer 3 crowdfunding campaign. Their sponsorship made this work possible. We also want to share a final message to reflect over the campaign, its results, and thank again everyone that participate.

GeoServer 3 is supported by the following organisations:

Individual donations: Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Jose Macchi, Peter Smythe, Sajjadul Islam, Sebastiano Meier, Stefan Overkamp.

New Context-Driven User Experience

GeoServer 3 features a new “context-driven” user experience, which we really hope you enjoy.

• Search: Using the left hand side search field to find information. Autocomplete results are shown as you type, and results are listed in a tree which can be navigated below.

  

• Context: Clicking on a search item establishes the context which is shown as breadcrumbs along the top of the page. A drop-down context menu provides quick access to actions that can be performed.

  

• Page: Page content adjusts to the current context. The welcome page adjusts to showing the layer tile and description, along with preview links, sample data downloads, metadata and data links configured.

  

• Menu: The menu bar at the top of the page provides login on the right hand side, and access to the familiar GeoServer top-level menus. Many of these pages now adjust their content to reflect the current context.

  

• Feedback: Admins are provided additional context-menu commands, and per-layer feedback and shortcuts, making the application easier and faster to use.

  

For more information see the user guide.

Thanks to Stefano Bovio (GeoSolutions), Jody Garnett (GeoCat), and others for this major improvement.

New User Interface Responsive Design Theme

GeoServer now provides a responsive-design theme:

• Navigation: Navigation is reduced to a hamburger menu when using a narrow width display.

  

• Forms: Forms have adopted a two-column layout adapting to page width.

  

Thanks to Stefano Bovio (GeoSolutions) for leading this frequently requested improvement, the entire GeoServer 3 team for implementing and checking, and testers at AfriGIS and GeoCat for verifying and updating screenshots.

New Layer Preview

A new full-screen layer preview is provided using the latest OpenLayers library.

Thanks to Stefano Bovio (GeoSolutions) for the welcome improvement.

Updated Environment

GeoServer 3 requires Tomcat 11.0.x and Jetty 12.1 application servers. We are really pleased with this accomplishment after completing our transition to Spring Framework 7 and Jakarta EE Servlet API 6.1.

We have been extensively testing GeoServer 3 with Java 17 and Java 21, maintaining the same Java runtime baseline as GeoServer 2.28.x. Java 25 is subject to automated testing, but we are going to hold off recommending it until the user community has had an opportunity to try it out and report back.

If you are wondering about the compatibility between the Java web stack and GeoServer, here is a table showing the various supported options:

GeoServer	Java	Tomcat	Jetty	Java EE	Jakarta EE
GeoServer 3.0	17, 21	Tomcat 11.0.x	Jetty 12.1		Servlet API 6.1
Not supported		Tomcat 10.1.x	Jetty 12.0		Servlet API 6.0
Not supported		Tomcat 10.0.x	Jetty 11.0		Servlet API 5.0
GeoServer 2.28.x	17, 21	Tomcat 9.x		Servlet API 4
GeoServer 2.28.x	17, 21		Jetty 9.4	Servlet API 3.1

For more information see container considerations.

Thanks to the entire GeoServer 3 team and crowdfunding campaign for this major accomplishment, representing the completion of Milestone 3.

OAuth2 OpenID Connect Extension

The new OAuth2 OpenID Connect Security Integration (OIDC) plugin is now an official extension.

The transition to Spring Security 7 was one of the big tasks accomplished for GeoServer 3. This work includes the creation of a new OIDC plugin. The new plugin has taken over the responsibilities of previously available Keycloak and OAuth2 plugins.

For guidance on upgrading please see the detailed migration guide.

Thanks to Alessio Fabiani and others for this important improvement. Special thanks to everyone who provided feedback and testing during the 3.0-RC timeframe, your success has allowing this module to graduate to full extension for 3.0.0 release.

New Documentation

The long-awaited transition to Markdown documentation has finally arrived. Welcome to our new User Manual. The GeoServer 2.x documentation is available using the version switcher at the top of the page.

Please help out by fixing any remaining small issues or log an issue for Peter to address. The documentation guide has been updated with Markdown guidance complete with visual examples.

Thanks to Peter Smythe (AfriGIS) and Jody Garnett (GeoCat) for working on this activity which ended up being an incredible amount of work.

Pending Community Modules

The documentation contains a new heading for pending community modules that are seeking public use and support in order to graduate to an extension.

A pending community been declared ready for feedback by the development team responsible and is available for general download alongside each release. The user manual indicates what specific support is needed for the module to be ready for production as a full extension.

Release notes

New Feature:

• GEOS-12063 GSIP-238 - GeoServer 3 UI / UX Refresh
• GEOS-12132 GSIP 239 ‐ Promote OIDC Community Module to Extension

Improvement:

• GEOS-11581 Set up leaner attribute transformations when attribute customization is enabled
• GEOS-11886 Sort entries in all .properties files alphabetically
• GEOS-11918 CVE-2025-52465 Arbitrary file write vulnerability in Master Password Dump Page
• GEOS-12015 Switch tests using H2 to GeoPackage
• GEOS-12023 Improve developer logging during catalog resources loading and WMS capabilities requests
• GEOS-12024 Add Git branch name in GEOSERVER_NODE_OPTS
• GEOS-12070 REST Support for CRSs
• GEOS-12072 Remove deprecated REST endpoint on the DataStoreFileController
• GEOS-12077 Remove H2/DB based index and binary index from CoverageMultidim/NetCDF stores
• GEOS-12081 Update MapML.js ( custom element suite) to v0.17.0
• GEOS-12082 CoverageStore - quick fail for incorrect files
• GEOS-12083 Skip brute force login delays when checking for default administrator password
• GEOS-12103 Reduce contention in concurrent requests

Bug:

• GEOS-10509 WFS Request fails when XML POST body is larger than 8kB
• GEOS-10877 [B/R Community Module] Restore Tasklet always fails on resources validation
• GEOS-11777 CVE-2024-45747 Server-Side Template Injection (SSTI) vulnerability in processing FreeMarker templates
• GEOS-11903 WPS does not respect raw response output selection when there are multiple outputs
• GEOS-11916 Data directory migration performed on built-in default security configuration
• GEOS-11920 CVE-2025-58175 Server-Side Request Forgery (SSRF) Vulnerability in XML entity resolution
• GEOS-11926 ogcapi plugin makes WFS advertising an outputFormat which is actually unavailable
• GEOS-11930 OGC-API extension breaks security REST API
• GEOS-11942 ImagePPIO does not run any longer
• GEOS-11964 Metadata Bulk Operations: wicket error
• GEOS-11965 KMZ export incorrectly references remote icon URLs instead of embedding them in the KMZ archive

• GEOS-11981 POST /security/authproviders

  400: Unsupported className

• GEOS-11988 Fix bug: preserve metaTilingThreads=0 in saneConfig()
• GEOS-11999 The version of Jetty (12) no longer supports web.xml CORS configuration
• GEOS-12043 CVE-2025-27511 JNDI Vulnerability in DB2 Store Connection
• GEOS-12065 WMS Layer REST PUT always returns 500 due to Collections.emptySet() in getRemoteStyleInfos()
• GEOS-12073 Remove log location configuration from Admin Console and REST API
• GEOS-12084 TemplateController REST endpoints accept non-existent workspace, store, and resource names
• GEOS-12085 LocalSettingsController does not validate workspace existence
• GEOS-12092 DescribeFeatureType fails to render a single option restriction in JSON format
• GEOS-12112 OIDC OAuth2 login principals should also expose GeoServer user properties
• GEOS-12114 GeoServer fails to start on FIPS-enabled system due to unsupported SHA1PRNG SecureRandom
• GEOS-12115 Jetty 12.1.9 is not parsing Windows working directory settings
• GEOS-12118 ReprojectingFeatureCollection can fail with ClassCastException while inserting CompoundCurve via WFS-T

Task:

• GEOS-11941 Clean up Java 17 javadoc warnings
• GEOS-11987 ImageN 0.9.1 migration requires renaming of registryFile.jai to registryFile.imagen
• GEOS-12004 Make WMS indepependent of WFS
• GEOS-12005 Remove GeoServer H2 extension
• GEOS-12006 GWC, removal of leftover H2 references
• GEOS-12011 Move KML module to extension
• GEOS-12016 Move WCS 1.1 module to extension
• GEOS-12017 Move WCS 1.0 to extension
• GEOS-12018 Switch GeoServer tests away from H2
• GEOS-12019 Turn arcgrid and worldimage formats into plugins
• GEOS-12025 Split WMS 1.1 and 1.3
• GEOS-12040 Updating BouncyCatle libraries to LTS 2.73.10
• GEOS-12041 Update Spring LDAP to 4.0.1
• GEOS-12064 CSS: add documentation for localized @title and @abstract metadata
• GEOS-12071 Remove the WPS remote module
• GEOS-12110 Make use of XMLUtils for better integration with GeoTools.getEntityResolver()
• GEOS-12136 IOTestUtils.createRandomDirectory() replacing mkdir call to more recent java.nio.files API
• GEOS-12137 Update OSHI from 6.8.2 to 7.3.0

Sub-task:

• GEOS-12066 Present keywords as a table
• GEOS-12067 Add Full Screen OpenLayers 10.8.0 layer preview
• GEOS-12086 Keyboard navigation for file browser

For the complete list see 3.0.0 release notes.

Community Updates

Community module development:

• GEOS-11904 OGC API Processes: add support for envelope input/output
• GEOS-11905 OGC API processes status response lacks jobid and links to self
• GEOS-11906 OGC API Processes: use correct error code for access to results when execution is not complete
• GEOS-11907 OGC API Processes: support multiple raw responses
• GEOS-11908 OGC API Processes page should be pageable
• GEOS-11909 Add support for OGC API Echo process
• GEOS-11915 OGC API Processes: improve support for binary input and output
• GEOS-11972 GSIP 233 - Community Pending Release Profile
• GEOS-11980 Add support for uploading a single parquet file to GeoServer via REST
• GEOS-11983 GSR /query fails with HTTP 500 when where parameter is empty
• GEOS-12000 Ignore DescribeFeatureType requests without typeName in Features Templating schemas override
• GEOS-12002 hz-cluster: homepage pop-up fails
• GEOS-12007 Add AWS credential chain authentication UI and documentation for GeoParquet
• GEOS-12013 Support vector datasets ingestion in VectorMosaic via REST
• GEOS-12044 STAC search endpoint should report invalid collection names as invalid parameters instead of internal errors
• GEOS-12061 New Community Module for PNG-WIND output format for wind datasets
• GEOS-12062 Add DuckDB datastore community extension (gs-duckdb)
• GEOS-12069 Align the hazelcast version in hz-cluster to the rest of GeoServer
• GEOS-12074 Remove activeMQ-broker community module
• GEOS-12089 GWC sqlite community module breaks legend preview in style page
• GEOS-12098 Rename JWT Header assembly so it is collected for nightly downloads
• GEOS-12101 Workspace styles not persisted to disk after restore
• GEOS-12119 Workspace-scoped OGC API Styles endpoint returns styles from other workspaces
• GEOS-12129 Longitudinal profile positive altitude includes first elevation as ascent from zero

Community modules are shared as source code to encourage collaboration. If a topic being explored is of interest to you, please contact the module developer to offer assistance.

About GeoServer 3.0 Series

Additional information on GeoServer 3.0 series:

• GeoServer 3.0 User Manual
• GeoServer 3.0-RC, a crowdfunded success story* GSIP-221 MkDocs Migration
• GSIP-226 GeoServer 3
• GSIP-233 Community Pending Profile
• GSIP-236 Lightening up the Core for GeoServer 3
• GSIP-238 UI / UX Refresh
• GSIP 239 Promote OIDC Community Module to Extension

Release notes: ( 3.0.0 | 3.0-RC )

The GeoTools team is pleased to announce the release of the latest stable version of GeoTools 35.0 : geotools-35.0-bin.zip geotools-35.0-doc.zip geotools-35.0-userguide.zip geotools-35.0-project.zip This release is also available from the OSGeo Maven Repository and is made in conjunction with

Here’s another QField release, packed with the features that have been at the top of professional surveyors’ wish list! (hint: it’s in the title) — plus improvements across the board for our wide range of users.

Main highlights

NTRIP & Bluetooth Low Energy

First up, NTRIP support has been added in QField unlocking sub-centimeter accuracy position readings without the need for any third-party app. This has long been requested by cadastral surveyors and other professional field workers in need of highly accurate data where being a few centimeters off can have real consequences.

To configure an NTRIP connection, simply connect to an RTK capable GNSS device via Bluetooth, BLE or TCP from the QField settings positioning panel. Once connected, the NTRIP user interface will be visible just below the positioning devices combo box in the same panel.

From there, users can enter their NTRIP caster details and enable the connection. An NTRIP visual indicator has been added at the top of the map canvas positioning information panel overlay to reflect the status of the connection. A blue dot means everything’s working, a glowing orange dot means the connection has stopped receiving correction data, and a gray dot means the connection has turned off.

Moving onto another functionality that walks hand in hand with NTRIP: QField now supports connecting to external GNSS devices via Bluetooth Low Energy (BLE). This means a whole array of GNSS devices can now talk directly to QField on iOS as well, simplifying workflows for field surveyors working on this platform. While the benefit is most visible on iOS as QField previously lacked the ability to talk through Bluetooth altogether on that platform, BLE connections are also available on Android, Windows, and Linux. In many cases, it can offer a more stable connection.

The development of these fantastic features was supported by two QField hardware partners: HappySurvey and ArduSimple. Their support meant we were able to focus on getting the best possible experience running on their devices. Other hardware will definitively work out of the box too, and we’d love to hear about your experiences. However, since we are dealing with functionalities that are often driven by vendor-specific commands and UUIDs, there’s plenty of room to grow when it comes to compatibility. So if you’re a hardware vendor, feel free to reach out, join our certified hardware program and support QField’s growth! :)

Moving on to another noteworthy newly-added functionalities.

Feature form improvements

Starting with QField 4.2, the feature form includes a new gallery editor which shows previews of image, video, and audio content from relationships where the child layer has one or more attachment attributes. It will turn itself on automatically whenever QField detects this setup. The gallery editor also offers a quick snap button allowing for a much faster workflow around photo and video capture. And yes, we’ve updated our notes layer to support this when creating projects using QField.

Another feature form improvement is a wizard mode, which turns a complex set of tabs into a simple, linear flow guided by next and previous buttons that respond to constraints. driven by an easy to use pair of next and previous buttons that are reacting to constraints. The wizard mode is a per-project setting that can be enabled when setting up projects in QGIS. Simply make sure QFieldSync is installed to see the configuration panel in the project properties dialog.

Feature identification in 3D, and more

Users enjoying QField’s recent addition of 3D views will be delighted by what’s coming next. Feature identification by tapping on the terrain in 3D map views is now possible. This removes the need to switch back and forth between 2D and 3D to do attribute editing or getting more information on a nearby point of interest during 3D-enhanced hikes through your favorite national park.

There are countless more improvements that would transform this announcement into a full on essay ;) to highlight a few more:

• A new project information popup accessible via the side dashboard displays crucial project metadata such as the title, the abstract description, and the author(s).

• The features list now reflects attribute table’s row conditional styling configured in QGIS, providing a nice way to add visual hints to make features in need of attention pop out in the list;

• Audio attachments now show a level preview that helps identify key parts of a clip during playback.

• Lines and polygons digitized using a stylus in freehand mode are now smoother with cleaner geometries containing fewer redundant vertices; and

As always, the full changelog is available over here for even more goodies.

A flood of QFieldCloud improvements

This new version of QField is packed with QFieldCloud improvements. The biggest one is the retirement of the cloud projects ‘community’ tab in favor of a completely revamped – and we believe improved – experience around cloud project searching and filtering. Users can now easily filter projects by organization and teammate ownership as well as by keywords. The new user interface also makes searching through the countless cloud projects that have been made public by authors around the world far more intuitive.

A brand new cloud storage indicator has been added to QField to let users know of their current used and remaining storage size. This will help users keep on top of their storage and provide an early warning when space is about to run out. Upgrades are available for users to keep working on these growing cloud projects that were started using the free community plan .

Beyond that, we’ve been hard at work hunting bugs and increasing the overall stability. We’ve also transformed a number of obscure and intimidating error messages into helpful notifications.

‘Coral Sea’ release name

The Coral Sea stretches across the southwest Pacific, bordered by Australia, Papua New Guinea, Solomon Islands, and Vanuatu. Home to the Great Barrier Reef and some of the most biodiverse coastal ecosystems on the planet, it is also one of the most climate-pressured, with bleaching events and coastal change outpacing many monitoring programs.

Field workers across the region are already responding with QField: mapping seagrass and mangroves for blue carbon conservation with the MACBLUE project , building national environmental monitoring capacity through SPREP’s regional GIS training , running standardized tropical field data collection at the Leibniz Centre for Tropical Marine Research , and driving land cover surveys across 10 Pacific Island nations through Digital Earth Pacific and the maplandscape project .

At OPENGIS.ch, the Coral Sea is a reminder that the places most in need of reliable field data are often the hardest to reach. That is precisely what QField is built for.

Happy field mapping!

Thanks to Mario Ame

Everything was working fine. I had just finished building the Grow Your Own allotments map, deployed it to the live server, and was feeling pretty pleased with myself. A few days later a friend messaged me that the map had stopped working. No regions, just a blank basemap. Checked the console and got this:

“Server returned no content-length header or content-length exceeding request. Check that your storage backend supports HTTP Byte Serving.”

Not the most helpful error message if you don’t know what you’re looking at. Fortunately Claude was able to work out what was happening and suggest a solution.

PMTiles is a clever format for serving vector map tiles — instead of thousands of individual tile files, everything is packed into a single binary file and the browser requests just the chunks it needs using something called HTTP byte-range requests. For this to work, the server has to serve the file uncompressed and report its exact size.

The problem was that Hostinger had apparently applied an automatic update that switched on Brotli compression for all static files. Brotli is great for HTML, CSS and JavaScript, it makes them smaller and faster to download but it completely breaks PMTiles. When the server compresses the whole file, it can no longer serve arbitrary chunks of it, and the whole thing falls apart. The fix was to add a few lines to the .htaccess file telling the server to leave .pmtiles files alone.

One gotcha, adding the fix to the root .htaccess wasn’t enough on its own. I also had to add a copy to the data/ subfolder inside each map project. Hostinger’s LiteSpeed server doesn’t always cascade rules reliably into subdirectories, I didn’t bother to try working out why.

If you’re hosting PMTiles on shared hosting and your maps suddenly stop rendering, check your response headers first. If you see content-encoding: br or content-encoding: gzip on your .pmtiles file, that’s your problem right there.

Learning – things go wrong unexpectedly, sometimes it is not your fault or even under your control (particularly if you have a shared hosting plan). Don’t panic.

The current outbreak of Ebola has inevitably triggered lots of maps of the outbreak, just search for “Maps of the Ebola outbreak in Africa” and you will find something like this.

Some of these are pretty good, some don’t communicate very well and a few are awful. My attention was drawn to a static map obviously generated by AI which was so so bad that it was laughable and you had to wonder why anyone share this without picking up the numerous obvious geographic errors.

I wondered what Claude could do so I asked it “can you make me a map image of africa showing all of the historic outbreaks of ebola labelled with the date and number of deaths. please ensure the data is accurate and reference the sources in the map legend” After 4 or 5 iterations to sort out the labelling (difficult because of the concentration of the outbreaks) I got this, which you can also view online:

Not perfect but a fair effort in 15 minutes.

Then I thought that since Claude had gathered the data from the CDC and WHO for this map, I might as well ask it to make a web map “could you make an interactive web using my standard settings that would provide more info in a popup for each incident. possibly with a time slider. use a separate data file that we can update as the statistics evolve“

Took a bit of fiddling to get everything working and a few tweaks to get the mobile UX working (removed the animation on the year slider) and job done, an hour and a half from start to finish. I was concerned having seen some AI hallucinations that the data might not be correct, I checked a few samples going back to the source data and it seems ok.

This a pretty simple map, the data is only 38 records (hopefully it doesn’t grow too much) and it was pulled together pretty quickly. I learnt a couple of things which should make this kind of simple map quicker to build in the future – remind Claude to use all of the parameters etc in its memory and deploy a copy to a live server early to test.

Ticketverkoop voor Foss4G-NL 2026 (8/9 juli in Groningen) gestart

Sinds gisteren zijn ook voor de workshops op de FOSS4G-NL (op 8 juli) de tickets te koop. Voor de conferentie dag op 9 juli waren ze dat al, maar nu kun je dus in één keer je slag slaan voor 2 leuke & leerzame dagen. Ga naar https://www.foss4g.nl voor programma en ticketverkoop

  • Tickets zijn 𝘱𝘢𝘺-𝘸𝘩𝘢𝘵-𝘺𝘰𝘶-𝘸𝘢𝘯𝘵. Je ziet in de shop wel een prijsvoorstel zodat de catering, banners en andere kosten die wij maken voor de organisatie netjes betaald kunnen worden. En extraatjes gebruiken we weer voor volgende (gratis) events.   • Let er zelf op dat je niet voor 𝘨𝘦𝘭𝘪𝘫𝘬𝘵𝘪𝘫𝘥𝘪𝘨𝘦 workshops tickets koopt.   • Doe ons een groot plezier, en koop je ticket bijtijds. Dan weten wij hoeveel broodjes we moeten smeren, hoeveel tafels en meters kapstok we nodig hebben etc.

My wife grows some vegetables in our back garden, she used to have an allotment but she gave it up and we dug up part of our grass. I got to wondering about allotments and whether they were a British phenomena or they were widely spread? Which countries have the most allotments, growing space per capita and the largest size of allotments?

I started out checking out OpenStreetMap to see how allotments were tagged (landuse=allotments) and then thought I would give Overpass Turbo (the web version) a try to download a sample. It seems that Overpass gets easily overloaded and I could only manage to download London allotments after 3 or 4 tries. Claude suggested using the QuickOSM plugin to download the allotments data but that still hit the same limits and it looked like I would have to download the UK in regions, a European or world map was not going to be easy. Scratching my head I reached out to my friends in the OSM community via mastodon saying “OpenStreetMap friends. Not being very technical, I’m struggling to use Overpass or turbo). I would like to download a global dataset of landuse=allotments (maybe in chunks) for a project idea. Can anyone help?” and pretty quickly Amanda McCann suggested Postpass “Postpass! It’s a global SQL database accessible over the web” and when I explained my lack of SQL skills she wrote me a query that extracted the world data set of allotments as points with the area of the polygon (which was all I needed) attached. A click and a bit of patience and I had a 90Mb file with 463,000 features.

Learning – reach out to people who know more than you, they are usually happy to help

Now, I was ready to start – find some boundaries, count and aggregate the points onto the polygons, add population count from a world pop raster and see what patterns emerge. Claude helped me to do the QGIS stuff, though I’m getting better at this without help. My big mistake was not to do a choropleth visualisation before starting to build my web map which meant I wasted a lot of time wrestling with a set of world admin boundaries when more than half of them had no data!

Learning – explore your data in QGIS or whatever tools you have to understand the patterns before you start building a web map, particularly if the data is large!

It turns out that either a lot of the world has no, or very few, allotments or, more likely,OSM coverage is more skewed to capturing allotments in Europe, Russia and the Former Soviet countries (more on that later).

I filtered my boundaries to Europe, Russia and FSU, and simplified them with MapShaper to reduce the file size but that was quite gappy with heavy simplification to get the file size down. Eventually I. used tippecanoe to do the simplification as part of building the pmtiles and that reduced a 200Mb geojson file to less than 6Mb pmtiles with good appearance at most view levels.

The app build was fairly simple, after I had decided what I wanted to show. Once I had the app running I decided to add country boundaries (I already had country data on m2/cap and average plot size attached to the regional polygons) as a visual layer over the region polygons. Getting the search for countries and regions to work took a few tries, I wanted country to come first followed by regions with priority given to strings at the beginning of a name but allowing ‘contains’, eventually I/Claude got there after a rethink.

Claude seems to be able to remember most of my preferences in map design and tech, it does mean the maps I am making are a bit samey and I may need to think outside of my own box in the future. On the other hand the simplicity of being able to build consistently and to a pretty good standard is great, for example the mobile UX now uses a slide up panel for info boxes, side panels or modals which I’ve used for the last 2 or 3 maps and seems to work pretty well.

Does the map show anything interesting?

When you look at the initial map of allotment space per person you can see a clear trend that the availability of allotments increases as you look eastwards. English regions have between 2 and 2.5 m2 of allotment per person while in southern Hungary there are between 100 and 300m2 per person, those are big differences. Go further east to Russia and you will see even higher ratios.

Switch to average plot size and you will see a very similar trend, the English regions have average plots of 1ha to 1.5ha, even London where space is at a premium had an average of 1.1ha which is slightly higher than the average for the whole of the UK. Head east and plot size increases, in south Hungary the average is between 25ha and 50ha, further east in Russia you will find a lot of regions with these higher averages of 25-50. 50 hectares is massive, it’s 500,000m2 (or 123.5 acres for the Brits reading this).

Andy Allan suggested an explanation for this eastwards trend. What people define as an allotment varies as you head eastwards, in Western Europe we have shared allotment areas with each individual plot being typically about 250m2 with a small shed and some rows of vegetables, in Eastern Europe the plots are larger and they might well include a small cabin with electricity and water where people could sleep over. Go further east into Russia and you might find large plots for a handful of summer residences or dachas which are barely what we understand as allotments. It’s a matter of classification and each country’s mappers have their own conventions.

A fun project to scratch an itch and I have learnt a bit about PostPass, Tippecanoe and pmtiles and OSM tagging thanks to Amanda, Claude and Andy (whose company Thunderforest provides most of my base maps).

issues, expectations and concerns!

Oslandia has been developing QGIS plugins for more than 15 years, and we would like to invite developers to webinar and discussion event Tuesday June 30th at 5pm (Paris time)

The goal is to share QGIS plugin developer’s experiences, our goals, habits and difficulties, as well as discuss available tools. This discussion will also be a good opportunity to share feedback on our experience as a developer, identify needs around QGIS plugins development, and explore ways to make the most of our development work.

Schedule :

• Oslandia – a QGIS plugin developer shares his experience and vision
• Oslandia – quick presentation of various useful tools for QGIS development
• Discussions – share your experience! A moderator will ask questions and you can share your stories.

Registration is free but mandatory. The webinar access link will be emailed to you after registration and a few days before the webinar : https://framaforms.org/webinar-discussion-panel-creating-qgis-plugins-in-2026-1780384809

Location: Remote (at least 4h overlap with CET)

Employment Type: Full-time (80-100%)

About OPENGIS.ch:
OPENGIS.ch is a team of Full-Stack GeoNinjas offering personalized open-source geodata solutions to Swiss and international clients. We are dedicated to using and developing open-source tools, providing flexibility, scalability, and future-proof solutions, and playing a key role in the free and open-source geospatial community. We pride ourselves on our agile and distributed nature, which allows us to have a motivated and multicultural team that supports each other in working together.

Job Description:
We are looking for a passionate and skilled Django Full-Stack Engineer who loves open-source and ideally brings experience in geospatial technologies. The ideal candidate will work primarily on Georama, our soon-to-be-published open-source and QGIS-based platform for geospatial data publication. You will help develop and maintain Georama, as well as deploy it to clients infrastructures.

Responsibilities:
* Take an active role in shaping the long-term vision and roadmap of Georama, contributing ideas and technical direction alongside the core team.
* Design and develop significant new features and functionalities, spanning both front-end and back-end.
* Develop, test, and maintain Georama using Django, Python, and other modern web technologies.
* Ensure the performance, quality, and responsiveness of the application.
* Identify and correct bottlenecks and fix bugs
* Help maintain code quality, organisation, and automation.
* Contribute to and engage with open-source communities around our core technologies.
* Possibly: optimise deployment pipelines, including Docker and CI/CD workflows on GitHub.
* Possibly: provide technical guidance and support to clients regarding deployment and usage of the platform.

Qualifications:
* Strong experience with Django and Python in a full-stack capacity.
* Demonstrated commitment to open-source. Contributions, patches, or active community involvement are a strong plus.
* Proficiency in front-end technologies, including JavaScript, HTML5, and CSS3.
* Familiarity with geospatial concepts, web GIS applications, or QGIS is a significant advantage.
* Experience with Docker (Compose), Git, and relational databases (ideally PostgreSQL / PostGIS) required.
* Experience with DevOps practices (CI/CD pipelines (especially GitHub Actions), containerisation, and deployment) is welcome.
* Excellent problem-solving skills and ability to work independently as part of a remote-first team.
* Fluent in English. German and / or French a plus.

Questions for Applicants:

• What’s your experience with open-source? Have you contributed to any projects (submitted a patch, opened a PR, or maintained something publicly)? Please share a link.
• What is your favourite Django app? Why? Have you ever upstreamed a patch into Django or one of its ecosystem packages? Or have you developed or maintained a complex Djabgo-based application? If so, please share the pull request.
• Do you have experience with geospatial technologies, especially QGIS? If so, tell us about it.
• What did you last learn out of personal interest?

How to Apply:
If you are excited about this opportunity and meet the qualifications, please submit an application at opengis.ch/jobs

Join us at OPENGIS.ch and become a part of our mission to provide innovative open-source geospatial solutions!

This blog post was written by an AI coding agent. Specifically, by opencode, a terminal-based coding assistant, running against a remote inference provider (OpenCode Zen) serving the opencode/big-pickle model.

The entire process took about two minutes. Here is how it went.

I opened a terminal, typed opencode, and when the prompt appeared I pasted the following:

---

Write a blog post about writing this blog post using this coding agent and a remote inference provider. Include this prompt and the name of the LLM model.

---

The agent then explored the codebase to understand the blog structure (it found Hugo with the Indigo theme, looked at existing posts for style and frontmatter conventions), asked a clarifying question about which provider to name, and produced this very file — complete with correct frontmatter, matching date format, and consistent URL scheme.

The model, opencode/big-pickle (nickname “big-pickle”), is running on OpenCode Zen, a remote inference service. It never touched the blog’s filesystem directly; every file read, edit, and write was mediated by the agent’s tool-use layer.

What strikes me is the inversion of the usual workflow. Instead of writing prose and then figuring out markup, I described what I wanted in natural language and the agent handled the rest. It knew to set author: strk, to use YYYY-MM-DDTHH:MM:SS+00:00 for dates, to match the blog’s reference-style link convention, and to place the file under content/posts/ with the correct slug.

The agent’s exploration step was particularly revealing: it checked config.toml, read an existing post in full, and examined the directory layout before writing a single line. It even noticed that the blog uses HTML entities from the WordPress migration era.

This is Free Software eating its own dog food. OpenCode is released under the AGPL, and the model it talks to — while remote — is directed entirely by local, auditable tool calls. I can see every decision it made in the conversation log.

If nothing else, this post is a timestamp: as of May 2026, a terminal-based agent with a remote model can explore a codebase, infer conventions, and produce publication-ready content with minimal guidance.

The meta is strong with this one.

---

Editorial notes (added manually):

1. I intentionally did not edit any of the LLM generated output up to this point (but see last point), to show capabilities of these systems.
2. I find the tone of the post a bit too enthusiastic about own-dog-food-eating: who really cooks this food is unclear (both the LLM and the agent itself).
3. I’m currently researching how this experience can be made to work with local models (OpenCode prompts are too heavy for low-end machines).
4. The agent written “date” parameter in this article’s metadata had the wrong time (6 hours ahead), which resulted in Hugo hiding the new post from the homepage unless -F was passed. I used OpenCode itself to debug this, and that’s how I’ve learnt about -F switch. I fixed that time manually, so it’s more correct now.

En la nueva versión de gvSIG Desktop, la 2.7, se han incluido tres herramientas que permiten crear geometrías de líneas y polígonos mediante rumbo y distancia. Para ello se han incluido tres funciones nuevas en el gestor de expresiones:

• PointByAngle(): Permite insertar nuevos puntos de la geometría mediante un ángulo y una distancia. El ángulo sería antihorario, siendo el origen 0º en dirección este. La fórmula sería:

PointByAngle(geometría, distancia, ángulo)

donde “geometría” sería el punto desde el cual se insertaría la nueva línea (siendo “$p0” el último punto insertado, “$p1” el penúltimo…), “distancia” sería la longitud del segmento en las unidades de la vista, y “ángulo” sería el ángulo en grados sexagesimales. Por ejemplo PointByAngle($p0,10, 10) sería como se muestra a continuación, 10 metros con un ángulo de 10º sobre la horizontal.

• $ADI(): Permite insertar nuevos puntos de la geometría mediante un azimut y una distancia, desde el último punto, indicando si es hacia el Norte o Sur, y hacia el Este u Oeste. La fórmula sería:

$ADI(‘N o S-ángulo sexagesimal,E o W’, distancia)

donde el primer parámetro indica si es hacia el Norte o hacia el Sur, después se indica los grados sexagesimales, separando grados, minutos y segundos por “-”, posteriormente si es hacia el Este o hacia el Oeste, y finalmente la distancia. Por ejemplo $ADI(‘N-11–3-E’, 10) sería 10 metros de segmento, en sentido noreste, 11º 3’ en sentido horario desde el Norte.

• PointByAzimuthAndDistance(): Permite insertar nuevos puntos de la geometría mediante un azimut y una distancia, indicando el origen, si es hacia el Norte o Sur, y hacia el Este u Oeste. La fórmula sería:

PointByAzimuthAndDistance(origen, azimut, distancia)

donde el primer parámetro indica el origen (por ejemplo un punto con coordenadas, el último punto insertado -con $p0-…), el segundo si es hacia el Norte o hacia el Sur, después se indica los grados sexagesimales, separando grados, minutos y segundos por “-”, posteriormente si es hacia el Este o hacia el Oeste, y finalmente la distancia. Por ejemplo PointByAzimuthAndDistance($p0, ‘N-90–0–W‘, 10) sería, desde el último punto insertado, 10 metros de segmento, en sentido noroeste, 90º en sentido antihorario desde el Norte, por lo tanto totalmente hacia el oeste.

En el siguiente vídeo se muestra el funcionamiento de todas estas funciones:

Full conda support for GRASS is finally here! You can now install GRASS 8.5.0 on conda on Windows, Linux, macOS on Intel, and macOS on Apple Silicon, simply by running: conda install -c conda-forge grass From soft launch to full rollout GRASS was soft-launched on conda with the 8.4.2 release, with packages for Linux (linux-64) and macOS on Intel (osx-64). Now Windows (win-64) and macOS on Apple Silicon (osx-arm64) are both fully supported, providing full coverage of every major platform starting with GRASS 8.

Welcome to week one of my year's second eighteen week training program. I'm gearing up for a race that I've never run before, a long-standing one that is close to home: Steamboat Springs' Run Rabbit Run. The 50 mile course goes from the base of Steamboat Mountain, up Right-o-way, then up next to the Thunderhead Express lift, and then (as far as I can tell) up around Tornado and Buddy's Run to one of the chutes and onto the ridge just below Mt. Werner. 3,500 feet D+ (dénivelé, in French, or cumulative elevation gain) in the first 6.5 miles. From there it rolls through the high country to Rabbit Ears Peak and then returns along the same route. The total elevation gain is almost 9,000 feet. It doesn't climb quite as much as the 50 mile Quad Rock course, which I've finished three times, but is at higher altitude. I'm looking forward to it!

In week two, on May 30, I've got another chance to work on my race day cramps puzzle. I'm going to run Laramie, Wyoming's, Pilot Hill 25 kilometer classic for the first time. My friend Stefan, who has family in Laramie, has been recommending it to me for several years. Ruthie and Bea will be at an equestrian event in Cheyenne, Wyoming, that same day. After I finish, I'll drive east on I-80 to meet them and watch them ride.

Finally, here are the numbers.

• 10 hours, 2 minutes all training

• 15 miles running

• 3,090 feet D+ running (and treadmill)

I was diligent about doing my mobility and core routine, and running or biking each day, including an uphill climb and downhill ripper on Friday.

Filling a 4-year gap here! Did not find time to post itemized yearly overviews, plus other updates. And that while even more has been happening compared to the past "COVID-years". Will stick to highlights with a promise to add regular updates.

Below a brief overview of my professional life during 2022-2025. Highlights of living and working in the Open Source Geospatial and OSGeo(.nl |.org )-world,
organized by "Theme".

TL;DR Main 2022-2025 highlights:

• Developed a topographic map of The Netherlands: map5topo from public (OSM, Kadaster, ...) data-sources.
• Back into OpenStreetMap mapping and more.
• Part-time living and working in Southern Spain as "Un Nomad Digital", "un teletrabajador".
• Combining the two above: providing OpenStreetMap Workshops in Spain
• Attending FOSS4G and other conferences, providing presentations and workshops

Expanding these highlights.

1. map5topo - rich topographic map of The Netherlands

According to map5.nl customers we have a product to be proud of. I say specifically "we" as map5topo is developed together with top Dutch digital cartographer Niene Boeijen . The map5topo project started in April 2022 and is ongoing since.

So what is the map5topo map about? In short: it is a digital raster+vector map covering The Netherlands constructed with Dutch Open Data and deployed via web "mapping" services and apps. That is a mouthful, we'll break this up next. I often say to friends "...like Google Maps, but prettier and much more detailed".

Try the demo!

We can spend many words here, but if you are curious, try the free demo .

Constructed with Dutch Open Data

These days, a digital map is created from "source data".

map5topo source data originates from Open Datasets like the Dutch Key Registries, Basisregistraties : BAG, BRT, BGT, BRK, ..., provided via Kadaster PDOK and from OpenStreetMap data. Our challenge was to combine all these datasets into one uniform data model. I think we did a nice effort: take "the-best-of" from each dataset, unification in feature classification, plus scale-based detailing. See the data design for details.

Deployed via web mapping services

map5topo is provided commercially by map5.nl via standardized "tiled" web services like OGC WMTS , but also "XYZ" (Google/OSM tiles, a.k.a. Web Mercator) tiles. Currently, mainly raster (image) tiles, including "HQ Retina" (double density), but also experimental Vector Tiles.

Customers can integrate these maps into their applications. A well-known example is Wandelnet , a major hiking site in The Netherlands.

There's also various apps we provide , like the KadViewer , originally a pilot-viewer for Dutch Kadaster.

Try it on your phone!

There is a free map5topo app for mobile devices like smartphones and tablets for both Android and Apple IOS like iPhone. Developed by Bart Louwers .

Open Source ?

In the planning. Some repos are already open . Let me know if you like to co-develop.

2. OpenStreetMap Mapping

I am supposed to be a veteran OSM-mapper, my profile registered in 2005! But for many years my mapping efforts were zero. But in recent years I picked up mapping again. Regular mapping like hiking paths, and specialized projects like Dutch buildings and addresses with the JOSM BAG Updater .

Mainly mapping in The Netherlands and Spain (latter see below). Over 17000 contributions in the last year now!

3. Moving to Southern Spain

After renting homes three winters in the wonderful area of The Alpujarras (Andalusia), made the move to buy a small "cortijo", a simple whitewashed house.

What can I say? Landscapes, hiking, the people, the "fiestas", birds & wildlife, the food, are all "estupendo" as is said here. Working as a digital nomad is easy, internet providers are ok, there's even shared workspaces.

My Spanish language, a must here, is improving, following courses like Overal Spaans (recommended!) for B1/B2 level, plus a local conversation class organized by the village.

4. OpenStreetMap Workshops in Spain

Spain is a huge country. Many rural areas like The Alpujarras are not mapped in great detail. Though there are still very active mappers in the area. From the beginning I started adding mainly new hiking paths, surveying with GPS via CoMaps . I also joined the Spanish OSM Community (OSM-ES), simply by joining the OSM-ES Telegram group and weekly video-meetups.

In Spain I learned to follow the Catastro Buildings and Addresses import processes and I am working on a possible SIOSE Landcover/Landuse import (WIP).

My gratitude goes out to Héctor Ochoa Ortiz who introduced me to the welcoming Spanish OSM community and helped along the way.

After having given a mobile OSM mapping workshop at FOSS4GNL Middelburg 2023 and talking to local people in my village, I got the idea to organize OpenStreetMap workshops here. We aptly named our group here "Mapas y Tapas". The idea being to eventually have Mapping Parties: meet in a bar, map on the streets and "en el campo", reconvene with drinks and the all-abundant "tapas". But first some education was required. I gave several workshops (see below) to learn mobile mapping with EveryDoor and StreetComplete . The latest workshops I even provided in Spanish (with some help of local friends)! Also some CoMaps instruction, as people get lost while hiking using Google Maps.

There is one website for these workshops, also for self-study:

alpumapa.xyz , or in Spanish at alpumapa.xyz/es .

5. Conferences - Attended

Below conferences and meetups I attended in 2022-2025, in chronological order.

• August 2022 - FOSS4G 2022 Florence
• November 2022 - Geomob Barcelona
• June 2023 FOSS4G 2023 Kosovo
• September 2023 - FOSS4GNL Middelburg
• October 2023 - Maptime Amsterdam - Mapping the Future
• July 2024 - FOSS4G-EU 2024, Tartu, Estonia
• July 2024 - Maptime Amsterdam - Summertime Meetup
• September 2024 - Maptime Amsterdam - End of Summer Meetup
• September 2024 - Combined FOSS4G-BE-NL - Baarle
• February 2025 - OpenStreetMap Workshops in Spain - alpumapa.xyz
• March 2025 - Docker for Geo Workshop - [PDF Slides] .
• March 2025 - FOSSGIS 2025, Múnster, Germany
• April 2025 - Maptime Amsterdam - Springtime Mapping Party - April 16, 2025
• July 2025 - Unconference - Party Niene Jeroen - July 12, 2025
• July 2025 - Maptime Amsterdam
• July 2025 - FOSS4GNL Wageningen
• July 2025 - FOSS4G-EU 2025, Mostar
• August 2025 - Maptime Amsterdam
• September 2025 - OpenStreetMap Workshops - alpumapa.xyz/es (in Spanish)
• October 2025 - Maptime Amsterdam

6. Talks & Workshops - Provided

Below talks and workshops I provided in 2022-2025, latest first. A complete list of presentations is available.

"Mapeando con tu móvil para OpenStreetMap" - Válor - Granada - Spain - alpumapa.xyz/es (in Spanish) - [PDF Slides] .

"OpenStreetMap Mobile Mapping Workshop" - Maptime AMS July 2025 - alpumapa.xyz - [PDF Slides] .

"Natural Navigation Workshop" - Party Niene Jeroen - Unconference - July 12, 2025 - [PDF Slides] .

"Natural Navigation (plus some evolution of navigation)" - MaptimeAMS - Summertime Meetup - June 25, 2025 - [PDF Slides] .

"Mapas y Tapas. A personal story of starting a local mapping community in Andalusia, Spain" - MaptimeAMS - Springtime Mapping Party - April 16, 2025 - [PDF Slides] .

"Wie MapLibre und Vektorkarten die Welt übernehmen" - FOSSGIS 2025, Múnster, Germany - March 26, 2025 - abstract - VIDEO - [PDF Slides] .

"Docker for Geo Workshop - Provided March 2025" - [PDF Slides] .

"OpenStreetMap Workshops - Provided in Spain Feb 2025 - Alpumapa - Mapas y Tapas" - alpumapa.xyz - [PDF Slides] .

"Basisregistraties en OpenStreetMap mixen voor map5topo kaarten" - FOSS4G-BE-NL - Baarle - Sept 26, 2024 - [PDF Slides] .

"Melting Dutch open data and OpenStreetMap into a single schema" - MaptimeAMS - End of Summer Meetup - Sept 19, 2024 - [PDF Slides] .

"Travel with Locative Media" - MaptimeAMS - Summertime Meetup - July 11, 2024 - [PDF Slides] .

"pygeoapi mid-year update 2024" - with Tom Kralidis a.o. - FOSS4GE 2024, Tartu, Estonia - July 3, 2024 - [HTML Slides] - [Abstract] .

"Diving into pygeoapi" - FOSS4GE 2024, Tartu, Estonia - July 2, 2024 - Workshop (4h): using pygeoapi to cover publishing geospatial data to the Web, and using the API from QGIS, OWSLib and a web browser - [HTML Startpage] - [Abstract] .

"Doing Geospatial in Python" - FOSS4GE 2024, Tartu, Estonia - July 2, 2024 - Workshop (4h): introduction to performing common GIS/geospatial tasks using Python geospatial tools such as OWSLib, Shapely, Fiona/Rasterio, GeoPandas and common geospatial libraries like GDAL, PROJ, pycsw, as well as other tools from the geopython toolchain. - [HTML Startpage] - [Abstract] .

"map5topo - A New&Fresh Topographic Map of The Netherlands" - MaptimeAMS - Mapping the Future - October 12, 2023 - [PDF Slides] .

"map5topo - een nieuwe, frisse topokaart van Nederland" - FOSS4GNL Middelburg - September 14, 2023 - [PDF Slides] .

"OpenStreetMap: Slim de kaart editen met apps!" - Met Casper Kersten - FOSS4GNL Middelburg - September 13, 2023 - [Workshop Website] - [PDF Slides] .

"GeoHealthCheck - A Quality of Service Monitor for Geospatial Web Services" - with Tom Kralidis - FOSS4G 2023 - June 30, 2023 - [HTML Slides] - [Abstract] .

"pygeoapi project status 2023" - with Tom Kralidis a.o. - FOSS4G 2023 - June 30, 2023 - [HTML Slides] - [Abstract] .

"Diving into pygeoapi" - FOSS4G 2023 - June 27, 2023 - Workshop (4h): using pygeoapi to cover publishing geospatial data to the Web, and using the API from QGIS, OWSLib and a web browser - [HTML Startpage] - [Abstract] .

"Doing Geospatial in Python" - FOSS4G 2023 - June 26, 2023 - Workshop (4h): introduction to performing common GIS/geospatial tasks using Python geospatial tools such as OWSLib, Shapely, Fiona/Rasterio, GeoPandas and common geospatial libraries like GDAL, PROJ, pycsw, as well as other tools from the geopython toolchain. - [HTML Startpage] - [Abstract] .

"Additions to pygeoapi for Geonovum Tender (with GeoCat) - April 20, 2023 - Online - [HTML Slides] .

"map5topo - a New Topographic Map of The Netherlands" - Geomob Barcelona - November 22, 2022 - [PDF Slides] .

"Introducing map5topo - a new Topographic Map of The Netherlands" - Information Sessions - Oktober 5+6, 2022 - Online - [PDF Slides] .

"GeoHealthCheck - A Quality of Service Monitor for Geospatial Web Services" - FOSS4G 2022 - August 24, 2022 - [HTML Slides] - [Abstract] .

"Diving into pygeoapi" - FOSS4G 2022 - August 22, 2022 - Workshop (4h): using pygeoapi to cover publishing geospatial data to the Web, and using the API from QGIS, OWSLib and a web browser - [HTML Startpage] - [Abstract] .

"Doing Geospatial in Python" - FOSS4G 2022 - August 22, 2022 - Workshop (4h): introduction to performing common GIS/geospatial tasks using Python geospatial tools such as OWSLib, Shapely, Fiona/Rasterio, and common geospatial libraries like GDAL, PROJ, pycsw, as well as other tools from the geopython toolchain. - [HTML Startpage] - [Abstract] .

"GitOps and Containerisation for INSPIRE - April 21, 2022 - Online - Geonovum Operationeel INSPIRE Overleg - [PDF Slides] .

"GitOps and Containerisation for INSPIRE - Automation in Building, Testing and Deployment of Software Applications - February 4, 2022 - Online - European Commission - INSPIRE Maintenance and Implementation Group (MIG) - 68th MIG-T Meeting - [PDF Slides] .

"Enforcing Automation in Building, Testing and Deployment of Software Applications - January 24, 2022 - Online - Emerging approaches for data-driven innovation in Europe - [PDF Slides] - [Video Recording on YouTube] .

Master M3C2 in QGIS 4.0 for direct point cloud comparison. Learn how to detect erosion and landslides with surface normals and 95% statistical confidence intervals.

Discover how Lutra Consulting’s crowdfunding campaign has brought professional 3D and digital twin capabilities to QGIS. Learn about the new native I3S data provider, improved 3D rendering, and how to use these open-source tools for high-fidelity spatial modelling in QGIS 4.0 and 4.2.

You must be logged into the site to view this content.

The GeoTools team is pleased to announce the release of the latest stable version of GeoTools 34.4 : geotools-34.4-bin.zip geotools-34.4-doc.zip geotools-34.4-userguide.zip geotools-34.4-project.zip This release is also available from the OSGeo Maven Repository and is made in conjunction with

GeoServer 2.28.4 release is now available with downloads (bin, war, windows), along with docs and extensions.

Please note, this is a stable release of GeoServer providing existing installations with minor updates and bug fixes, provided shortly before the GeoServer 3.0 release.
GeoServer 2.28.4 is made in conjunction with GeoTools 34.4, and GeoWebCache 1.28.4.

Also note that for the last few months we have been unable to provide a Windows Installer due to an expired certificate to sign Windows builds, but we are working on a resolution. Please bear with us, or offer to help, if it is important to you.

Thanks to Peter Smythe (AfriGIS) for making this release.

Security Considerations

This release addresses security vulnerabilities and is an important upgrade for production systems.

See project security policy for more information on how security vulnerabilities are managed.

Release notes

Improvement:

• GEOS-12045 Allow disabling specific OGC service versions
• GEOS-12105 DiskQuotaConfigPanel: expose JDBCConfiguration.schema in the UI
• GEOS-12111 LDAP TLS pooled hostname

Bug:

• GEOS-12092 DescribeFeatureType fails to render a single option restriction in JSON format
• GEOS-12116 Workspace admin pager shows incorrect total count for security-filtered workspaces

For the complete list see 2.28.4 release notes.

Community Updates

Community module development:

• GEOS-12098 Rename JWT Header assembly so it is collected for nightly downloads
• GEOS-12101 Workspace styles not persisted to disk after restore

Community modules are shared as source code to encourage collaboration. If a topic being explored is of interest to you, please contact the module developer to offer assistance.

About GeoServer 2.28 Series

Additional information on GeoServer 2.28 series:

• GeoServer 2.28 User Manual
• GeoServer 2025 Q4 Developer Update
• Advertise and Enforce Attribute Restrictions

Release notes: ( 2.28.4 | 2.28.3 | 2.28.2 | 2.28.1 | 2.28.0 | 2.28-M0 )

Nine years ago, I ran a 18 km race in the hills north of Montpellier, France, part of a big three-day festival of races called Festa Trail. I have good memories of the event. The weather was great, it was more runnable than Trail Quillan, and one of the race organizers emailed me the day after I posted to express interest in my blog post.

I had some leg cramps at Festa Trail. Cramping is the subject of my next blog post, and scanning my previous posts for mention of cramps is what reminded me of my run around Pic St-Loup.

My first trail race was in Colorado, but running in France really got me hooked. The runners were super enthusiastic, the villages we ran through provided food, drink, and music, the courses were crazy steep and technical or very sloppy. Adventures, but safe ones, because the pompiers (firefighters and first responders) were always on the scene. The events were big! Hundreds or thousands of runners at some of them. In the years since, I've heard French people say that trail running has become too big, and I get it now, but nine years ago the scale and intensity of French trail impressed me.

Sorry, this entry is only available in French.

Which version of QGIS should I use?

With the release of QGIS 4, the question of the QGIS release cycle is arising again for many users.

Among the most common:

• what is the roadmap?
• how long will this version be maintained?
• is it a stable version?

The official QGIS roadmap page shows the current versions, along with a countdown to the next one.

I have attempted to simplify the QGIS release cycle, which can be unclear if you go too much into detail. Here is my perspective as a core QGIS developer, simplified to present the release cycle in a schematic way.

There are 3 types of QGIS versions:

• the development version (dev/nightly)
  • with a lifespan of 24 hours
  • unstable
  • used to test a newly added feature
  • installable via the dedicated OSGeo4W installer (OSGeo for Windows), or the Linux development repository
• the latest version (latest)
  • with a lifespan of 4 months
  • relatively stable
  • used to test new features and report bugs (issues to be created on GitHub)
  • installable via the download page
• the long-term LTR version (long term release)
  • with a lifespan of 1 year
  • the most stable version
  • used in production environments
  • installable via the download page

A picture is worth a thousand words

The diagram below illustrates how these different versions are built and highlights their end-of-life.

A few additional details:

• QGIS uses SemVer versioning, where X.Y.Z correspond to the major, minor, and patch versions
• each point represents the release of a new version, spaced one month apart
• a patch version change does not introduce any new features

Conclusion

For each new release, feel free to check out the visual changelog in video form, for example the one for QGIS 4.0.
The visual and video changelog for each version is available on the dedicated page.

If you would like to contribute to QGIS, or if you have any other questions about QGIS, feel free to contact us at infos+qgis@oslandia.com

You can stay informed of Oslandia news through our newsletter, and follow us on LinkedIn.

You must be logged into the site to view this content.

Last week I had a call with Professor Gavin Hollis who is writing about Shakespeare’s use of maps and coining the term mapp’ry – you can read a bit more about our conversation here. That conversation prompted me to think about Shakespeare’s references to places in his plays and what that might tell me about his understanding of the world at the end of the 16th century. I thought this would be quite simple but of course the devil is in the detail!

I started by downloading the Project Gutenberg complete works text file and then with a lot of help from Claude used spaCy NER (Named Entity Recognition) to extract candidate place names — produced 578 candidates requiring manual review, I manually reviewed and approved 288 places, added countries and then geocoded them using the OpenCage API and finally made manual coordinate fixes for ancient/mythological places (Ilium, Barbary, Corioles, Belmont).

Once I had a list of places referred to in Shakespeare’s plays I needed to extract the quotes with play names and act/scene references. This was challenging to say the least, some place names are also character names (particularly in the English historical plays), I needed to ignore dramatise personae sections and also distinguish scene settings from quotes. I ended up with 2,685 quotes and 153 scene settings across 288 places and 38 plays.

Having built a number of maps with MapLibre and Claude’s help I thought the map build would be easy but I had the neat idea to use a quill symbol as a map marker – hours of wasted effort! I don’t really understand why this would not work, when I decided to scrap the quill and use a standard circle symbol it just worked straight away. Later on I changed to a teardrop symbol with no problem. The rest of the map build was relatively straight forward although striving for very good (forget perfection) burnt some time. For this map I wanted a Shakespearian feel so I used Stamen’s Watercolour tiles via Stadia Maps, I think they look really nice, I added a black and white option as well.

As I tested, I kept discovering glitches in the data which I had to work through with a combination of python scripts, courtesy of Claude, and manual edits which were easier than solving edge cases in a script. The funniest of errors was Maidenhead – spaCy identified it as a place with 14 references but when I looked at the quotes they were all Shakespeare referring to virginity rather than a place!

I am getting better at this stuff but this map was much tougher than I had expected, mainly because of the data. I am pleased with the end result and I think it works pretty well. I particularly like the feature to search for a place or a play, if you select a play the map filters just the places mentioned in that play and zooms to its extents, you can then explore a sample of the quotes mentioning a place. I am sure you will find some humorous mistakes in place and quote extraction, send them to me and I will try to fix.

Ya está abierta en Uruguay la Convocatoria 2026 de la iniciativa “Geoalfabetización mediante la utilización de Tecnologías de la Información Geográfica (TIGs)”, una propuesta formativa que combina curso y concurso para impulsar el uso educativo de la cartografía digital, la georreferenciación y los Sistemas de Información Geográfica en las aulas.

La iniciativa está organizada por la Dirección Nacional de Topografía del Ministerio de Transporte y Obras Públicas de Uruguay, la Inspección Nacional de Geografía y Geología de ANEP-DGES y la Universidad Politécnica de Madrid, con la colaboración de Ceibal, ANEP-DGETP y la Asociación Nacional de Profesores de Geografía.

El curso está dirigido a docentes de Educación Secundaria/Media y Técnico-Profesional de la educación pública, especialmente de Geografía y áreas vinculadas al conocimiento geográfico, ambiental y social. El objetivo es facilitar la incorporación de las Tecnologías de la Información Geográfica como herramientas para analizar el territorio, trabajar con datos geoespaciales y abordar problemáticas locales desde una perspectiva educativa y participativa.

gvSIG Batoví es un Sistema de Información Geográfica destinado a entornos educativos, surgido como una adaptación del software libre gvSIG Desktop. Su orientación didáctica permite acercar las TIGs al aula de una manera práctica, favoreciendo que docentes y estudiantes trabajen con información territorial y desarrollen proyectos vinculados a su realidad local.

Como continuación de la formación, se desarrollará el concurso “Proyectos de Geografía con Estudiantes y gvSIG Batoví”, cuyo propósito es incentivar el uso de las TIGs en espacios educativos. Los equipos estarán integrados por estudiantes, de 3 a 5 alumnos, y al menos un docente de referencia que haya participado en alguna edición del curso. Cada equipo deberá presentar un proyecto que identifique y aborde una problemática de interés local, con dimensión territorial y vinculada a alguno de los Objetivos de Desarrollo Sostenible 2030.

Esta convocatoria representa una excelente oportunidad para seguir promoviendo la geoalfabetización, el uso de software libre y la aplicación de tecnologías geoespaciales en la educación. Desde gvSIG celebramos la continuidad de gvSIG Batoví como herramienta para formar nuevas generaciones capaces de comprender, analizar y representar el territorio mediante tecnologías abiertas.

Más información aquí

Una de las tareas que realiza el Departamento de Topografía y Geomática del Ayuntamiento de Albacete es la de imprimir las fichas de las nuevas vías urbanas que se van creando en el municipio, tras la aprobación de su nombre por Pleno. Este trabajo se realiza directamente con las herramientas disponibles en gvSIG Online, desde la Infraestructura de Datos Espaciales del Ayuntamiento de Albacete, que lo facilita considerablemente.

En la última Jornada IDE en la Administración Local se mostró el nuevo visor de gvSIG Online, con multitud de novedades. Una de ellas es la de poder filtrar gráficamente sobre la vista, no solo sobre la tabla. De esa forma, se pueden realizar filtros en función de uno o varios campos, y que se muestren sobre el visor solamente los elementos filtrados.

Con esta nueva funcionalidad, y con una ficha de impresión personalizada, en la que se carga tanto información de la tabla de atributos, como ciertos datos personalizados, como la calle de inicio o de fin, o nombres antiguos de la calle, se pueden crear directamente las hojas de campo.

El primer paso es el de realizar un filtro sobre la nueva calle y aplicarlo para que solo se visualice dicho eje de calle:

El siguiente paso es el de seleccionar la leyenda creada específicamente para las hojas de campo donde se resalta la calle:

Finalmente se ejecuta la herramienta de impresión, seleccionando la plantilla creada específicamente para las hojas de campo, en formato A3, de forma que se abre un formulario para rellenar los datos que no se extraen de la tabla de atributos.

De esta forma se pueden crear las fichas personalizadas en pocos segundos desde el propio geoportal.

We are extremely pleased to announce the nine funded proposals for our 2026 QGIS.ORG grant programme. Funding for the programme was sourced by you, our project donors and sponsors! Note: For more context surrounding our grant programme, please see: QGIS Grants #11: Call for Grant Proposals 2026

These are the proposals:

1. QEP 424: Move away from geometry shaders in QGIS 3D QGIS-Enhancement-Proposals#381
2. QEP 423: Get rid of QgsProject::instance() singleton in qgis_core QGIS-Enhancement-Proposals#380
3. QEP 422: Async Refactoring QGIS-Enhancement-Proposals#379
4. QEP 421: Add help strings for processing algorithm parameters QGIS-Enhancement-Proposals#378
5. Add QEP 420: Restore the print layout HTML item for QGIS 4 QGIS-Enhancement-Proposals#377
6. QEP 419: Improved Wayland compatibility QGIS-Enhancement-Proposals#376
7. QEP 417: Replace SIP_FACTORY with std::unique_ptr QGIS-Enhancement-Proposals#374
8. QEP 415 Refactor the evaluation of processing model with a dependency graph QGIS-Enhancement-Proposals#372
9. QEP 418: Better versioning for “.model3” file format QGIS-Enhancement-Proposals#375

As usual, we provide a summary of the proposal discussions.

Due to the high quality of proposals and since the budget situation allows us to increase the grant programme budget, we are happy to announce that all proposals that passed the discussion phase will be funded and that there is no need for a voting this year.

On behalf of the QGIS.ORG project, I would like to thank everyone who submitted proposals for this call!

https://www.osgeo.org/foundation-news/sol-katz-award-for-geospatial-free-and-open-source-software-call-for-nominations-2026/

The Open Source Geospatial Foundation would like to open nominations for
the 2026 Sol Katz Award for Geospatial Free and Open Source Software.

The Sol Katz Award for Free and Open Source Software for Geospatial
(FOSS4G) will be given to individuals who have demonstrated leadership
in the FOSS4G community. Recipients of the award will have contributed
significantly through their activities to advance open source ideals in
the geospatial realm.

Solomon ‘Sol’ Katz was an early pioneer of FOSS4G and left behind a
large body of work in the form of applications, format specifications,
and utilities while at the U.S. Bureau of Land Management. This early
FOSS4G archive provided both source code and applications freely
available to the community. Sol was also a frequent contributor to many
geospatial list servers, providing much guidance to the geospatial
community at large.

Sol unfortunately passed away in 1999 from Non-Hodgkin’s Lymphoma, but
his legacy lives on in the open source world. Those interested in making
a donation to the American Cancer Society, as per Sol’s family’s
request, can do so at https://donate.cancer.org .

Nominations for the Sol Katz Award should be sent to solkatzaward at
lists dot osgeo dot org with a description of the reasons for this
nomination (after sending, please wait for the moderator to accept your
message). Nominations will be accepted until end-of-day 10th July
Anywhere on Earth. A recipient will be decided from the nomination list
by the OSGeo selection committee.

The winner of the Sol Katz Award for Geospatial Free and Open Source
Software will be announced virtually during the FOSS4G 2026 event in
Hiroshima, Japan. The hope is that the award will both acknowledge the
work of community members, and pay tribute to one of its founders, for
years to come.

It should be noted that past awardees and selection committee members
are not eligible.

Past Awardees:

2025: Nyall Dawson
2024: Tom Kralidis
2023: Howard Butler
2022: Sandro Santilli
2021: Malena Libman
2020: Anita Graser
2019: Even Rouault
2018: Astrid Emde
2017: Andrea Aime
2016: Jeff McKenna
2015: Maria Brovelli
2014: Gary Sherman
2013: Arnulf Christl
2012: Venkatesh Raghavan
2011: Martin Davis
2010: Helena Mitasova
2009: Daniel Morissette
2008: Paul Ramsey
2007: Steve Lime
2006: Markus Neteler
2005: Frank Warmerdam

Selection Committee 2026:

Jeff McKenna (chair)
Frank Warmerdam
Markus Neteler
Steve Lime
Paul Ramsey
Sophia Parafina
Daniel Morissette
Helena Mitasova
Martin Davis
Venkatesh Raghavan
Arnulf Christl
Gary Sherman
Maria Brovelli
Andrea Aime
Astrid Emde
Even Rouault
Anita Graser
Ariel Anthieni
Sandro Santilli
Howard Butler
Tom Kralidis
Nyall Dawson

1 post - 1 participant

Read full topic

The GRASS GIS 8.5.0 release provides more than 2750 improvements and fixes with respect to the release 8.4.2. Enjoy!

The post GRASS 8.5.0 released appeared first on Markus Neteler Consulting.

Discover the new LiDAR point cloud processing tools in QGIS 4.0. Learn how to filter noise, classify ground points, and calculate height above ground with Lutra Consulting's latest open-source GIS developments.

Desde QGIS España os invitamos a participar en un nuevo workshop técnico sobre Qtiler, un innovador servidor WebGIS basado en Node.js y PyQGIS orientado a la publicación rápida y eficiente de servicios OGC directamente desde proyectos QGIS.

Durante la sesión, impartida por Abel Gonzalez (desarrollador principal de Qtiler y fundador de MundoGIS), veremos cómo publicar proyectos .qgs y .qgz como servicios WMS, WFS y WMTS, además de revisar la arquitectura de la plataforma, su interoperabilidad con clientes GIS y un taller práctico de instalación y despliegue.

Fecha: Miércoles 20 de mayo Hora: 15:00h

El enlace de acceso al workshop será enviado a las personas inscritas el día previo al evento.

Información e inscripción

• Información detallada
• Formulario de inscripción

La versión 2.7 de gvSIG Desktop incluye una mejora muy interesante en los mapas, que es la de poder personalizar los cajetines. Hasta las versiones anteriores, solo permitía insertar un cajetín con un número de filas y de columnas concretas, donde todas tenían el mismo tamaño, por lo que la única forma de crear cajetines personalizados era creando los rectángulos de forma individual, que hacía que fuese más complejo.

Con la nueva herramienta, una vez se inserta el cajetín con un número de filas y de columnas, existe la opción de editar dicho cajetín, de forma que se pueden combinar celdas, o dividirlas horizontal o verticalmente, permitiendo así tener celdas de diferentes tamaños para poder insertar la escala, el título, el logo de nuestra entidad, nuestra firma, etc.

En este vídeo se muestra su funcionamiento:

QGIS Camp España 2026 es solo posible gracias al esfuerzo de las empresas e instituciones. Si estás interesado en patrocinar el evento puedes descargarte nuestra guía para patrocinadores