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

Location: Remote, preferably with at least 4h overlap to CEST office hours

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.

Role Description:

We are looking for a DevOps Engineer to design, build, and operate scalable, secure, and reliable infrastructure. You will play a key role in improving automation, system resilience, and deployment workflows, enabling fast and stable delivery of our applications.

Key Responsibilities

Infrastructure & Automation

• Design, build, and maintain infrastructure using Infrastructure as Code (IaC)
• Automate system provisioning, configuration, and deployment processes
• Manage and optimize containerized environments and orchestration
• Develop internal tools and automation

CI/CD & Delivery

• Design, implement, and optimize CI/CD pipelines
• Improve deployment reliability, speed, and rollback capabilities

Systems & Operations

• Administer and maintain Linux (Ubuntu LTS) systems, including patching and hardening
• Support the standardization and deployment of software across diverse environments, including dedicated and on-premises customer hardware
• Implement and enhance monitoring, logging and alerting for all our systems and services

Database & Data Protection

• Manage PostgreSQL databases, including performance tuning and backups
• Implement and regularly test backup and recovery processes to ensure data integrity

Security & Reliability

• Apply security best practices across infrastructure and pipelines
• Proactively identify and resolve reliability and performance issues

Collaboration & Support

• Maintain clear and up-to-date technical documentation
• Collaborate with development and support teams to troubleshoot issues
• Manage tasks effectively and communicate progress and blockers

Requirements

• Proven experience in DevOps, Site Reliability Engineering, or System Administration
• Strong experience with:
  • Python and scripting (e.g., Bash)
  • Docker and containerized environments
  • Infrastructure as Code tools (Terraform / OpenTofu, Ansible)
  • Linux systems (Ubuntu preferred)
  • PostgreSQL database administration
  • Monitoring stack (Prometheus, Grafana, Loki)
  • Git and CI/CD platforms (specifically GitHub Actions)
• Solid understanding of system security, networking, and reliability principles
• Ability to work independently and solve complex technical problems

Perks:

At OPENGIS.ch, we enjoy a variety of perks that make our work experience rewarding. Here’s what we get:

• Flexible Work Hours: We have the freedom to set our own schedules, which helps us better manage our personal and professional lives.
• Remote Work Opportunities: We can work from anywhere, giving us the flexibility to choose our work environment.
• Learning and Development: We are encouraged to grow professionally with access to training programs and workshops.
• Innovative Environment: We thrive in an atmosphere that’s at the forefront of GIS technology, which keeps our work exciting.
• Collaborative Team: We value teamwork and the exchange of ideas, making our workplace dynamic and supportive.

Questions for Applicants:

• What is the most complex process you’ve automated from scratch?
• What is your favorite Ansible module or OpenTofu/Terraform provider? Why? Have you ever contributed to an open-source DevOps tool or infrastructure project? If so, provide a link to the pull request.
• When a critical system goes down, what is the first thing you check and why?
• What did you last learn out of 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!

Ed Parsons kicked-off the conference with a great keynote, talking about how we, as geographers, can make a difference. He got us thinking about what are the real world problems we can solve - a useful reminder that while the research is important, application is important too.

I also really loved his Russian Doll AI explanation - while Generative AI is “the new big thing”, it is all just statistics and many of these terms (Deep Learning, Neural Networks, Machine Learning and Artificial Intelligence) are all part of Data Analytics - which we have been working with in GIS for many many years.

We also heard from the conference chairs, Emma Ferranti and Sarah Greenham about their work with WM Adapt and wider applications in their current research projects.

This was followed by two great presentations from Adam Nudds and Si Chan Lam at the West Midlands Combined Authority (WMCA). Adam is a graduate of Uni of Birmingham, and part of the great links the university has with local government. Si reflected on how his many hundreds of hours playing Sim City 2000 prepared him for a role in Local Government (!)

With Adam, he provided some great food for thought on how we as GIS Researchers can make GIS more accessible and useful to decision makers. Often they want two sentences - but they also want confidence in the research behind those two sentences. PowerBI as a business tool also cropped up a couple of times with the tension of decision makers and non geospatial analysts wanting to use PowerBI, and the GIS experts wanting to use a more full featured GIS. I would say both tools can be useful and it’s worth seeing how we can bridge the two. Si and Adam are trying to make a showcase of GIS tools to show what we can do with GIS for the decision makers in WMCA.

It was also great to hear critical thinking mentioned several times, when using data, particularly IMD. Many many studies use IMD, particularly when they are looking at impacts on people. However, not many critically evaluate their use of it. Fortunately, Emma Ferranti reminded us in her presentation that when they use it, they ask - does it provide enough information and does it identify the people it needs to? Also Luc Wilson reminded us that IMD is often treated like fact, but it isn’t necessarily fact - remember the Ecological Fallacy!

The discussion also went beyond IMD, and Alex Singleton reminded us that while we have to define many aspects to be able to analyse them - he was looking at vulnerability and cash access - the definition of vulnerability is subjective so no one measure captures everything.

Bivariate maps are also now in! They were featured in at least three presentations including Fulvio Lopane and Johara Meyer, who did a great visualisation of picking out just certain groups in her presentation and highlighting them both on the map and in the legend.

The second keynote was a fantastic presentation from Gemma Davis and Claudia Offner from MapAction. MapAction provides mapping for humanitarian emergencies, often sending small teams to provide on the ground support directly after humanitarian emergencies. Gemma and Claudia shared their experiences providing support on the ground, highlighting how important maps are as a common communication tool in this setting. For me, a big highlight was that printed maps are still key - part of their kit is a plotter to create bigger than A3 maps, which form a key part of the planning and operations aspect of any aid response.

While printed maps are key, mobile phones are a massively useful tool too. They also highlighted two key tools they often used. Firstly, KoboToolbox as a geospatial enabled survey app, allowing responders to collect data in the field (without a data connection) and easily upload that data when they have connectivity. They also highlighted the ubiquity of WhatsApp, with local communities using it to coordinate their response. This is great, but it’s hard to integrate this with knowing what is happening where on a map. A new tool, Hot ChatMap, enables anyone to import a WhatsApp (or Telegram, Signal, etc.) chat and create a basic map showing all the locations shared and any related images. This is really helpful to work out what is happening where, and to share that data.

Another aspect I picked up from the conference is the importance of making the application of your work clear. Some presentations did this very very well, making technical aspects and applications clear to those in the audience who are not necessarily experts in that particular field.

While in some years at GISRUK we have been inundated with papers using social media data, this year there was only one - Nurwatik Nurwatik presenting - Incorporating Topology on GPT-Based Geoparsing Model for Finer Geocoding Locations from Social Media Texts. This was a fascinating discussion on using GPT-based technology to improve geoparsing - i.e. understanding how people talk about location in social media text.

Similarly there have been previous years where you could more-or-less follow the whole conference on Twitter - pre Elon Musk of course - but now, the conference only had a few mentions on LinkedIn during the conference - and nothing I could see on Twitter (X), Bluesky or Mastodon. There were a few nice summary posts after the conference, including these ones from Emma Ferranti, Harry Kirby, Lenka Hasova, Ferdous Rababa and many others.

We had a great conference dinner at The Exchange in central Birmingham, a venue owned by the university. There is currently an exhibition called Helios, about the Sun, with a giant model sun hanging from the ceiling - quite a stunning setup. Alongside a variety of public engagement spaces (including one on WM Adapt featuring Emma Ferranti!) The Exchange is also an old bank, and you can tour the vaults downstairs. No gold left unfortunately! But some quite spectacular vault doors:

I was also attending as a judge for the GISRUK & OSGeo:UK GoFundGeo Award, presented a GISRUK presenter who presents a tool or technique that has potential for wide uptake in the open source geospatial (OSGeo) community. We had a great selection of entries, and the final decision was hard. We finally settled on Chenrui Xiao who presented Wheely Easy: Creating a Wheelability Network for Bradford. Thanks to all those on the judging panel who helped me.

GISRUK was a great opportunity to meet GIS academics and researchers, and anyone interested in the developing field of GIS. Next year we will be in Nottingham and I hope to see some of you there.

If you ever want to talk about GIS Training, or whether GIS could be used in your project, I’m always open to a discussion. Please contact me to find out more!

La agrupación formada por ENXEÑERÍA FORESTAL ASEFOR, S.L., FINANCIERA
MADERERA S.A., FORTOP TOPOGRAFÍA S.L.U. y GEOMATICO S. COOP.
GALEGA. ha obtenido apoyo en el marco de la convocatoria NEXOS 2025,
promovida por la Axencia Galega de Innovación, para el desarrollo del proyecto
CUBia: Cubicación inteligente – Investigación avanzada en cubicación
descentralizada con arquitecturas híbridas LiDAR-SLAM / LiDAR-UAV-ALS / IA y
tecnologías disruptoras cuánticas (Quantum Reservoir Computing, QRC) para un
nuevo paradigma en la predicción forestal.

La iniciativa CUBia es un proyecto pionero en Galicia y en el ámbito nacional que
busca transformar progresivamente la forma en que se estiman y gestionan los
recursos forestales a través del uso combinado de tecnologías LiDAR-SLAM y
LiDAR UAV-ALS, inteligencia artificial y enfoques innovadores basados en módulos
experimentales de computación cuántica (QML/QRC).

El objetivo principal es desarrollar y validar un sistema de cubicación forestal
inteligente que permita sustituir el inventario manual tradicional, que supone un
importante esfuerzo en términos de recursos empleados y cuenta con limitaciones
significativas en cuanto a cobertura territorial y precisión, por un sistema digital,
descentralizado y remoto, ligado a la captura de datos mediante sensores
avanzados. Estos datos serán procesados mediante algoritmos de inteligencia
artificial, lo que permitirá llevar a cabo una modelización predictiva que será validada
con datos reales de fábrica.

De esta forma, se busca sentar las bases de un nuevo paradigma en la gestión de
los recursos forestales, mejorando la competitividad del sector maderero a través de
esta nueva generación de inventarios digitales, transferibles y escalables, con
márgenes de error controladas y directamente aplicables a la toma de decisiones, en
un marco de sostenibilidad, economía circular y transparencia en la cadena de valor
forestal.

Durante su ejecución, el proyecto investigará soluciones para la caracterización de
masas forestales comerciales mediante tecnologías LiDAR, desarrollará y validará
modelos predictivos dentro de un sistema de aprendizaje continuo, explorará
enfoques experimentales de computación cuántica e integrará este sistema en una
plataforma de cubicación digital que facilitará el uso, y promoverá la transferencia y
trazabilidad de los resultados.

Subvencionado por la Agencia Gallega de Innovación de la Xunta de Galicia y
cofinanciado por la Unión Europea.

Nº expediente: IN852A 2025/04
Socios: ASEFOR, FINSA, FORTOP, GEOMATICO
Subcontrataciones: Universidad de Vigo, ITG
Colabora: MEDRAR
Fecha de inicio: 01/11/2025
Fecha finalización: 30/09/2028
Presupuesto del proyecto: 1.248.009,60€
Importe de la ayuda: 724.802,08€

I was anticipating a good day at Quad Rock and instead I flopped. I finished in 8:14:46. 186th out of 209 finishers, my poorest place at this race by a big margin. And I'd expected to match, if not exceed, my previous best. What explains this fiasco? My major problem was acute leg muscle cramping, but there were some minor issues as well.

In the week before the race I did my mobility and core routine every day and ran 15-30 minutes per day. I ate and slept normally, which is to say, well. Instead of feeling fresher and fresher, I started to feel stiff and irritated all over. My right Tibalias Anterior and Peroneus Longus, the muscles on the shin and outside of the lower leg, were particularly tight and tender starting on the Thursday before the race and continuing into the eve of the race. I did a small set of 20 second hill sprints on the street around the corner from home on Thursday and felt okay. My shakeout run on Friday afternoon, however, sucked. I never got very comfortable and the strides I attempted were a chore. I was a little dismayed by this, but let that feeling go, figuring that I was likely to feel better on Saturday.

Saturday morning I ran the first mile very easy, then picked up the pace in the second to jump some places before we hit the first single track. In the first half mile of the single track I made about five short bursts to pass slow groups and find people who were running at my target pace. Soon after this, we started uphill and I started to get negative feedback from my legs. Not cramps yet, but a lack of energy, like I'd felt on Friday. I'd felt better on the same climb a week before in my last uphill workout.

I kept a steady enough pace up Towers, and wasn't passed by anyone, but began to go backwards on the first descent. My legs felt tight and fragile. I lost contact with the folks with whom I'd climbed Towers and a few places heading down to the 10-mile mark, Horsetooth Mountain Trailhead.

The next seven miles after the aid station were a complete disaster. I experienced calf cramps that stopped me cold, and shin and foot cramps that made it hard to stand at all. I was passed by 54 runners, about 2 runners per minute, before I reached the Towers aid station. I tried salt. I tried stretching. I had to lie on the dirt at Towers for 15 minutes before I could continue. 3:22 of that was spent listening to "Rock Me Amadeus" on the aid station's sound system, which gave me life and saved my race.

I fumbled my way down Mill Canyon to Arthur's Rock aid station at mile 17, three hours after leaving the Horsetooth aid station. I laid down in the shade to stretch and slowly put myself back together. After 15 minutes, I felt like I could continue, if not quickly. The cramps were fading, but my legs were shot from the involuntary contractions. As if I'd done squats and deadlifts to the point of muscle failure.

During the last seven miles of the race, I caught up with runners who were in their first Quad Rock, or first trail race of this distance, and it was fun to pre-celebrate with them, pump them up, share stories, and remind them that we were going to be finishers, if only because there was nowhere to drop out before the finish. I was feeling a lot better at this point. The last climb up Howard was hard but not the end of the world. I managed a good amount of easy running on the last descent to the finish.

The cramps reminded me of my experience at the Bear 100 in September 2025, except that they hit me sooner at Quad Rock, at 10 miles instead of 17 miles. I've been analyzing my data, memories, and notes to find things about the races that were common or different. And, now that I think about it, it was calf cramps that brought me down at mile 21 at Never Summer 100K in July 2023. I've got a problem with cramping that hasn't been solved by physical therapy or judicious amounts of hard running. It's going to be an interesting problem to work out.

In the end, I did finish, and feel pretty satisfied about that. I haven't crossed a race finish line since July of 2023, almost three years ago. Breaking a streak of three DNFs (2023 Bear 100, 2025 Never Summer 100K, 2025 Bear 100) felt good. The weather was good, the trails were fine. I ran with friends for a while and saw other friends at aid stations. It wasn't all torture. I smiled and laughed quite a bit.

Biggest thanks to Ruthie for driving me and Stefan to the start, taking our drop bags to Horsetooth, and for picking me up at the finish. Thank you, everyone who offered me help on the painful cramping trip. And thanks to Nick and Brad, and all you race volunteers. Everything about this race was top notch, except my legs.

UPDATE 14th May 2026

Thanks to Harry Wood I discovered that 3,000 of the 45,000 pubs in the FHRS dataset had no coordinates and were not showing on my map. Particularly embarrassing was the omission of the Sutton Arms which is a Geomob after event favourite for geobeers. It was relatively simple to rectify this as all but 6 of the missing records had a postcode that could be used to geocode using postcodes.io. Then I had to rerun the count of pubs per constituency, update the pubs per 10k population and rerun the generalisation of the boundaries – easy enough but an hour wasted.

Learning: Even if your dataset is too large to thoroughly inspect, 5 minutes spent scrolling through it, running a couple of sorts and doing some kind of sanity check is time well spent.

---

There has been quite a bit in the news recently about 2 pubs per day closing according to the British Beer and Pub Association. That got me thinking about which areas of the country were best served and where were the dry zones? Nearest Pint, shows pub density per 10,000 population across every parliamentary constituency in Great Britain.

The first challenge was finding a reliable pub dataset. My initial instinct was to use OpenStreetMap, which I expected to have excellent coverage of pubs given the map parties that end up in a pub. I used Overpass Turbo to download (amenity=pub) and found around 19,000 pubs across the UK — a significant undercount. According to the BBPA, there were approximately 45,000 pubs in the UK in 2024, so OSM was capturing fewer than half of them.

The discrepancy makes sense when you think about it. OSM contributors apply a fairly personalised definition of what counts as a pub, whereas the official figure includes working men’s clubs, hotel bars, sports club bars, and other licensed premises that serve alcohol but might not fit the classic pub image. OSM mappers, quite reasonably, tend to tag only what is clearly and obviously a pub.

A much better source turned out to be the Food Standards Agency’s Food Hygiene Rating Service (FHRS), which requires all food and drink premises to register — including pubs, bars and nightclubs. The GetTheData Open Pubs dataset, derived from FHRS, gave me just under 50,000 premises across England, Scotland and Wales, a figure much closer to industry estimates. Northern Ireland was excluded, it operates a separate food hygiene scheme, and the FHRS data doesn’t cover it.

With a fairly good pub locations dataset, the next step was assigning each pub to a parliamentary constituency and calculating density. I used QGIS to get a count of pubs per constituency and calculate the number of pubs per 10,000 people. The boundaries and population figures came from ONS. The one glitch was that the boundary files were very high resolution, I used MapShaper to aggressively thin the boundaries while retaining the topology – super neat tool, much better than trying to do in QGIS processing toolbox.

What the map shows

Traditional pub heartlands in northern England — particularly Yorkshire, County Durham and Lancashire — show the highest densities, with some rural constituencies reaching 15–20 pubs per 10,000 people. Coastal and rural constituencies in the South West also score highly, perhaps reflecting their tourist economies. Liverpool Riveride has the highest pub density at 23.73 pubs per 10,000 with a total of 277 pubs!

At the other end of the scale, outer London constituencies consistently show the lowest pub densities in England, despite the city having large numbers of pubs in absolute terms. Dense residential populations in areas like Barking (1.35), East Ham (0.76) and Slough (1.31) dilute the per-capita figures significantly. East Renfrewshire in Scotland ranks last among all 632 constituencies at just 0.73 pubs per 10,000 — only 7 pubs for a constituency of nearly 100,000 people.

Click any constituency to see its name, pub count, population, density and ranking. Zoom in to see individual pub locations. Use the 🏆 rankings button to browse constituencies from highest to lowest density and click any row to fly the map to that constituency or use the locate me button to see pubs near you which is always useful.

ArcMap is dead. Avoid costly ArcGIS Pro vendor lock-in by migrating to QGIS (LTR 3.44). Learn the 5 essential steps for a smooth transition, including MXD conversion.

We built etter, an open-source Python library that turns natural language location descriptions into spatial filters. You give it "north of Lausanne" or "on the shores of Lake Geneva" — it gives you a GeoJSON geometry your app can use directly. It's LLM-agnostic, multilingual, and handles the kind of spatial nuance that breaks naive approaches. If you build location-aware products, you'll want to read this.

Se você utiliza o QGIS no seu dia a dia, sabe que os plugins são os “superpoderes” que expandem as funcionalidades do software. No entanto, com grandes poderes vêm grandes responsabilidades — e a necessidade de segurança.

Recentemente, a equipe do QGIS anunciou uma atualização vital no blog oficial: o Repositório de Plugins agora conta com ferramentas automáticas de segurança. Vamos entender por que isso é um marco para o nosso ecossistema favorito.

O que mudou no Repositório de Plugins?

A mudança é fruto da QEP 409 (QGIS Enhancement Proposal). O foco aqui não é burocratizar a vida de quem cria, mas sim elevar o padrão de confiança. Agora, todo plugin enviado ao repositório oficial passa por um scanner automático de vulnerabilidades.

O que o scanner procura? Basicamente, práticas de risco, como exposição de chaves de API (o pesadelo de qualquer dev!), bibliotecas obsoletas ou métodos de codificação que podem abrir brechas para scripts maliciosos.

Entenda os Novos Selos (Badges) de Segurança

Ao navegar pelo plugins.qgis.org, você notará ícones coloridos ao lado das versões dos plugins. Eles funcionam como um semáforo de integridade:

Selo	Significado	Ação Recomendada
🟢 Verde	O código passou nas verificações críticas sem alertas.	Pode usar com tranquilidade!
🔴 Vermelho	Foram detectados alertas que precisam de revisão do desenvolvedor.	Atenção redobrada (leia abaixo).

Importante: Por enquanto, esses selos são visíveis apenas no portal web. O gerenciador de plugins dentro do QGIS Desktop ainda não exibe esses alertas, mas isso deve mudar em versões futuras.

“Don’t Panic!”: Por que tantos plugins estão com selo vermelho?

Se você abrir o repositório agora, pode parecer que houve um apocalipse digital: muitos plugins populares estão marcados em vermelho. Calma, não jogue seu computador pela janela!

Como diria Douglas Adams:

Don’t Panic.

O escaneamento foi feito de forma retroativa. Um selo vermelho não significa necessariamente que o plugin é um vírus. Na maioria dos casos, indica que o desenvolvedor usou uma biblioteca antiga ou um padrão de código que o novo scanner considera “suspeito” por precaução. A expectativa é que a comunidade leve cerca de um ano para “esverdear” todo o repositório.

---

O que muda para quem é Desenvolvedor?

Se você contribui para o ecossistema QGIS, o jogo mudou um pouco (para melhor):

1. Feedback Instantâneo: Ao fazer o upload, o portal mostra exatamente quais linhas de código dispararam o alerta.
2. Bloqueios vs. Avisos: Algumas falhas graves impedirão a publicação da nova versão até que sejam corrigidas.
3. Falsos Positivos: O QGIS permite o uso de “pragmas” (comandos no código) para ignorar alertas específicos, desde que o desenvolvedor ateste que aquela ação é segura e necessária.

---

Conclusão: Um QGIS mais Robusto

Essa atualização é um passo gigante para manter o QGIS como a ferramenta líder em geoprocessamento opensource no mundo. Garantir que o código que rodamos em nossas máquinas (muitas vezes em ambientes corporativos rígidos) seja seguro é essencial para a sobrevivência do movimento opensource.

E você, já conferiu se os seus plugins favoritos estão “no verde”? Se encontrar algum erro em plugins que você desenvolve, aproveite para dar aquele update preventivo!

I thought it might be interesting to look at alcohol consumption and production around the world. I expected the data to be pretty easy to find an process – how wrong can you be!

Consumption figures came from the World Health Organization via Our World in Data, which publishes recorded per capita alcohol consumption broken down by beverage type — beer, wine and spirits — for most countries in the world, with data running up to 2020. The WHO figures measure litres of pure alcohol, so Claude converted these to litres of finished drink using standard ABV assumptions (beer 5%, wine 12%, spirits 40%). The total consumption layer uses pure alcohol to allow a fair comparison across drink types.

For production, the picture was more complicated. Wine production figures came from the FAO via Our World in Data, with data up to 2023 — a much better source than what we found initially. Beer and spirits production came from the UN Industrial Statistics database (UNIDO), which has patchier coverage, particularly for spirits — the USA being a notable and frustrating gap (there is a lot of spirit production which is not for beverages which distorts the figures).

You’d have thought that there would be simple and comparable data sets for consumption and production broken down by type of beverage? No, no, no. I ended up with 189 countries covered for consumption, 90-120 for production depending on drink type

The data ended up in 6 files with a number of inconsistencies. Claude wrote a python script to merge everything into a single master CSV. Production is expressed as a percentage of consumption — values above 100% mean a country produces more than it drinks and is a net exporter.

One wrinkle worth flagging: production percentages can look absurdly large for countries that produce a small amount of a drink but whose population barely consumes any — Libya has a tiny wine industry but almost nobody drinks it, which initially produced a 500% figure. I applied a minimum consumption threshold of 0.5 litres per person per year below which we don’t calculate a production percentage.

Once I had the data, it was very quick to get a quite good map but it took a heck of a lot of tweaking on the colour ramps and break points to get the choropleths performing nicely. The lesson here is that anyone can vibecode a map but you need some basic cartographic understanding (read Ken Field’s books as a starter) to make something that looks good and does not mislead.

Does the map show anything interesting? No big surprises. Eastern and Central Europe dominate alcohol consumption by pure alcohol content — the Czech Republic, Latvia and Lithuania lead the table. The beer map tells a slightly different story, with Gabon and several African nations appearing alongside the usual European suspects. Wine consumption is highly concentrated in Southern and Western Europe and the southern hemisphere. On the production side, the major exporters stand out clearly — New Zealand produces over four times what it drinks in wine, Scotland’s whisky industry means the UK produces twice its domestic spirits consumption, and Belgium and Ireland are significant beer exporters.

Two years in the making GRASS 8.5.0 is here. This feature release contains more than 2570 changes, the result of two years of focused work by the GRASS community. We deliberately postponed what would have been a 2025 release so that several interlocking pieces could land together: a new Python API, JSON output across dozens of tools, and a complete rewrite of the documentation. These changes are more useful together than they would have been in sequence, and they took time to do well.

https://www.osgeo.org/foundation-news/gdal-3-13-0-iowa-city-is-released/

Hi,

On behalf of the GDAL/OGR development team and community, I am pleased to announce the release of GDAL/OGR 3.13.0 “Iowa City”.

GDAL/OGR is a C++ geospatial data access library for raster and vector file formats, databases and web services. It includes bindings for several languages, and a variety of command line tools.

http://gdal.org/

The 3.13.0 release is a new feature release with the following highlights:

• New gdal command line interface capabilities:
  • gdal vector combine (#13895)
  • gdal vector concave-hull
  • gdal vector convex-hull
  • gdal vector create (#14210)
  • gdal vector dissolve (#13985)
  • gdal vector export-schema (#14156)
  • gdal vector update
  • gdal vector rename-layer (#14132)
  • gdal vector sort (#13351)
  • gdal dataset check
  • gdal driver cog validate (uses validate_cloud_optimized_geotiff.py underneath)
  • gdal driver gpkg validate (uses validate_gpkg.py underneath)
  • gdal pipeline: add an external step to run an external command
• Zarr: various improvements in Zarr V3 support (sharding), support for multiscales, spatial and proj extensions for EOPF Visualization products.
• COG driver: implement GDALDriver::Create() for random write creation
• Add E57 read-only raster driver to read 2D images from ASTM E2807 (E57) files
• Add SAR Compensated Phase History Data (CPHD) multi-dimensional read-only driver (#14310)
• MiraMonRaster: add creation support (#13960)
• JP2GROK: read/write driver for JPEG-2000 using Grok JPEG 2000 toolkit (the toolkit is AGPL v3 licensed)
• S102/S104/S111 driver: add write support
• NITF driver: add support for CADRG writing
• Add support for INTERLIS 2.4
• Make cloud users aware of commercial cloud providers that don’t sponsor the project and whose cloud storage protocol may be removed in the future (#14313)
• Revert removal of OGR Tiger and UK. NTF drivers (but still to be considered as living on borrowed time)
• Bump of shared lib major version

More complete information on the new features and fixes in the 3.13.0 release can be found at:

https://github.com/OSGeo/gdal/blob/v3.13.0/NEWS.md

Please also consult the migration guide when updating from prior releases:

https://gdal.org/en/latest/user/migration_guide.html#from-gdal-3-12-to-gdal-3-13

The release can be downloaded from:

• https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0.tar.gz – source as .tar.gz
• https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0.tar.gz.md5 – md5sum
• https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0.tar.gz.sig – signature
• https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0.tar.xz – source as .tar.xz
• https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0.tar.xz.md5 – md5sum
• https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0.tar.xz.sig – signature
• https://download.osgeo.org/gdal/3.13.0/gdal3130.zip – source as a zip
• https://download.osgeo.org/gdal/3.13.0/gdal3130.zip.md5 – md5sum
• https://download.osgeo.org/gdal/3.13.0/gdal3130.zip.sig – signature
• https://download.osgeo.org/gdal/3.13.0/gdalautotest-3.13.0.zip – test suite
• https://download.osgeo.org/gdal/3.13.0/gdal3130doc.zip – documentation / website

Docker images are available:

• ghcr.io/osgeo/gdal:ubuntu-full-3.13.0
• ghcr.io/osgeo/gdal:ubuntu-small-3.13.0
• ghcr.io/osgeo/gdal:alpine-normal-3.13.0
• ghcr.io/osgeo/gdal:alpine-small-3.13.0

Best regards,

Even

1 post - 1 participant

Read full topic

Foss4G-NL 2026 Call for Presentations

Dien jouw presentatie- of workshopvoorstel in!

Een FOSS4G‑evenement draait om makers én gebruikers van open source GIS‑toepassingen. Het is de plek waar we laten zien wat er mogelijk is met vrije software, waar we elkaar inspireren en waar nieuwe ideeën ontstaan.

Ben je maker van een tool, plugin, workflow of dataset? Dan is dit hét podium om te laten zien wat er allemaal kan: van slimme scripts tot verrassende visualisaties.

The path toward efficient and modern water management is not traveled through technology alone, but through close technical and human collaboration. Recently, part of the iCarto team traveled to Eswatini to work hand-in-hand with the Joint River Basin Authorities (JRBA), achieving two fundamental milestones for the project’s sustainability.

Main achievements: Billing and Real-World Data

This field visit was decisive in consolidating the system’s operability. Thanks to the joint effort, we succeeded in fulfilling the two main planned objectives:

• Billing Module Launched: The implementation and startup of the billing module is now a reality. The JRBA has started issuing and using printed invoices directly from the SIRH (Water Resources Information System). This represents a qualitative leap in their management and a critical milestone for the JRBA’s billing strategy, providing the necessary foundation to achieve their cost recovery goals.
• Integration of the 2024 Water User Survey: We successfully finalized the integration plan for incorporating the new operation areas identified during this year’s water user survey into the SIRH database. This ensures the system operates based on the actual reality on the ground, improving accuracy of decision-making and also strengthening billing and cost recovery processes.

Technology Ownership: A System Driven by Its Users

For iCarto, the success of a GIS project does not lie solely in the robustness of the code, but in how users make it their own. Seeing how the tool has been organically integrated into the institution’s daily operations is the ultimate validation of our work. The successful adoption by JRBA staff confirms that a user-centered approach—positioning the GIS as a problem solver—is the only way to build truly sustainable technology.

We would like to deeply thank the entire team and the management of the JRBA for their availability and support. Their openness and horizontal collaboration have been key to ensuring this technical deployment was fluid and effective.

Looking Toward 2026 and New Challenges

This project, which is funded by the BlueDeal program, is now entering its final phase, with a scheduled completion date in 2026.

Although we are approaching the end of this stage, we are aware that innovation in water management never stops. This visit helped us identify exciting new horizons, such as the potential implementation of SIRH Mobile and a Digital Customer Portal for water. We will continue working to ensure that GIS remains the backbone providing real and sustainable solutions to future water challenges.

La entrada Key Milestone in Eswatini: SIRH Enters Final Phase with Billing Module Implementation se publicó primero en iCarto.

GeoCat Find 2026.0 is out - the first release under that name. If you know GeoNetwork Enterprise, you know this product. We've simplified the name to bring it in line with the rest of our suite: Find,...

Week 16 is over. It's six days to Quad Rock.

• 10 hours, 11 minutes all training

• 18 miles running

• 2,385 ft D+ running

I did a small set of hard running intervals, some steady running, and one last hilly run on the Quad Rock course with a friend on Friday. We pushed the pace on the upper half of the first climb, going up Towers Trail, and I was just a few seconds off my personal bests on those segments. 10/10 effort on Saturday won't be sustainable, but it was fun and a useful check on my fitness before the race. I'll completely recover from that by the end of the week, no problem.

Week 17, race week, will be so easy that I expect to go a little stir crazy. A winter storm is arriving tomorrow, so I'll be inside, running on a treadmill and sitting in a sauna, until Thursday. I'm curious to see how much snow we get, whether it's going to stick on the mountains through race day, and how muddy it will be.