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€

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.

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:

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.

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.

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.

https://www.osgeo.org/foundation-news/torchgeo-organization-ibm-research/

The TorchGeo Organization and IBM Research are joining forces!

The TerraTorch and TerraKit libraries have joined the TorchGeo Organization! https://github.com/torchgeo is now home to 3 of the most influential and widely used open-source GeoAI libraries:

• TorchGeo: the core of the geospatial deep learning ecosystem, with more geospatial datasets and pre-trained foundation models than all other GeoAI libraries combined
• TerraTorch: higher-level abstractions that build on top of TorchGeo to make foundation model fine-tuning simple and intuitive for users from all backgrounds
• TerraKit: provides connectors and interfaces for NASA, ESA, and other data stores, allowing users to effortlessly download and build AI-ready datasets

To ensure even greater collaboration and long-term maintenance of these libraries, we are also excited to announce 2 new members joining our Technical Steering Committee:

• @Romeo Kienzler: AI Research Engineer at IBM Research, co-creator and maintainer of TerraTorch and TerraKit, and co-author of Prithvi WxC
• @Isabelle Wittmann: Research Software Engineer at IBM Research, maintainer of TerraTorch, co-organizer of the Embed2Scale EarthVision challenge, and Earth2Vec, TerraCodec, and NeuCo-Bench co-author

Romeo and Isabelle’s expertise in foundation models, neural compression, and embeddings will further strengthen the TorchGeo ecosystem, and ensure greater collaboration and compatibility between all projects we govern.

–

contact: Brian M Hamlin maplabs@light42.com #osgeo Project Mentor

1 post - 1 participant

Read full topic

You've probably seen links to "The Future of Everything is Lies, I Guess" already. I've just finished the last installment. This is an excellent series of posts with many references. If we meet to talk about the industry, I'm almost certainly going to ask if you've read it.

This is bullshit about bullshit machines, and I mean it. It is neither balanced nor complete: others have covered ecological and intellectual property issues better than I could, and there is no shortage of boosterism online. Instead, I am trying to fill in the negative spaces in the discourse. “AI” is also a fractal territory; there are many places where I flatten complex stories in service of pithy polemic. I am not trying to make nuanced, accurate predictions, but to trace the potential risks and benefits at play.

I've already come to some of the same conclusions, so I admit to confirmation bias.

El espacio no es contexto, es estructura.

Los Sistemas de Información Geográfica (GIS) parecen hoy inseparables de disciplinas como urbanismo, planificación territorial o gestión ambiental. Sin embargo, su presencia en la enseñanza académica es sorprendentemente desigual: omnipresente en geografía, marginal en arquitectura, casi inexistente en sociología, economía o ciencias políticas. Lo paradójico es que el concepto fundacional del GIS no nació de la informática ni de la ingeniería, sino de algo mucho más antiguo y urgente: un epidemiólogo británico tratando de detener una epidemia.

Un plano que cambió la forma de entender la ciudad

En 1854, Londres sufría un grave brote de cólera. La teoría dominante era clara y científicamente respaldada: la enfermedad se transmitía por el aire —los llamados «miasmas». Pero John Snow, médico con una observación incómoda, sospechaba que la teoría estaba radicalmente equivocada.

Para demostrarlo, hizo algo radical para su época: visualizar datos en un mapa. En el barrio de Soho elaboró un plano en el que marcó cada muerte registrada. Al superponer esos datos espaciales, la concentración alrededor de una única bomba de agua en Broad Street los relacionó de forma indiscutible.

La decisión fue drástica: retirar la manivela.

El resultado fue inmediato. Los casos cesaron. Los miasmas, aparentemente, se disiparon.

La teoría microbiana de Pasteur vendría después. Lo que Snow hizo fue revelador: mostró un patrón espacial tan claro que hacerlo invisible requería una negación deliberada. Y esa es exactamente la razón por la que el método es tan poderoso —y por la que fue ignorado durante años por la comunidad médica, que seguía insistiendo en que los miasmas eran reales.

Snow no manejaba capas de información, no creaba sistemas dinámicos interconectados, no procesaba múltiples variables territoriales simultáneamente. Estaba haciendo algo anterior y más primitivo, pero también más puro:

• Recopilar datos geolocalizados
• Visualizarlos en un espacio compartido
• Detectar patrones que el análisis estadístico agregado ocultaba.

De un mapa a una disciplina

El trabajo de Snow no era todavía un GIS en sentido moderno, pero sí estableció su lógica fundamental: el espacio como estructura para entender fenómenos complejos.

A lo largo del siglo XX, con el desarrollo de la informática, esta lógica se formalizó en herramientas capaces de manejar múltiples capas de información:

• Uso del suelo
• Infraestructuras
• Datos demográficos
• Variables ambientales

Así nacieron los GIS contemporáneos, que permiten analizar el territorio como un sistema dinámico e interconectado.

Los espacios olvidados

Más allá del urbanismo, el GIS sigue estando sorprendentemente ausente en la enseñanza de disciplinas donde podría aportar una capa de comprensión fundamental.

En mi etapa estudiando Arquitectura, persistía una enseñanza centrada en el prestigio del objeto puro, acercándose peligrosamente a la función escultórica por encima de la función humana y social, donde, en bastantes ocasiones, el edificio se diseña ignorando sistemáticamente las dinámicas territoriales que lo rodean; Pero la ciudad no es un lienzo neutral.

Algo similar ocurre en sociología, donde buena parte del análisis continúa siendo abstracto o estadístico, perdiendo de vista que fenómenos como la segregación o la desigualdad se manifiestan siempre en el espacio. El GIS haría visible lo que los números ocultan: que la desigualdad no es un número, es un mapa.

Incluso en campos como la salud pública —más allá del caso paradigmático de John Snow— o las ciencias políticas, el componente espacial suele quedar relegado, a pesar de ser clave para entender la distribución de enfermedades, recursos o comportamientos electorales.

En conjunto, esta ausencia no responde a una falta de relevancia, sino a inercias académicas que siguen separando el análisis espacial del estudio de fenómenos que, en esencia, son profundamente territoriales.

El GIS como herramienta para revelar (o ignorar) la desigualdad urbana.

El GIS representa una manera de pensar: Entender que donde ocurre algo es tan importante como el hecho que ocurre.

Pero no creamos que todo es claridad, el GIS no es neutral. Es una herramienta política que funciona en ambas direcciones.

Por un lado, revela: un mapa de segregación residencial es una acusación. Un GIS que superpone datos de salud, educación, empleo y contaminación sobre territorios pobres visibiliza las múltiples discriminaciones de una forma que ningún texto puede lograr. Esto es liberador. Permite fundamentar demandas de justicia con precisión espacial.

Por otro lado, naturaliza: un mapa de pobreza sin contexto de políticas de desalojo, especulación inmobiliaria o destrucción ambiental deliberada convierte un problema histórico y político en una «realidad geográfica» inevitable. El GIS puede hacer parecer natural lo que es resultado de decisiones humanas. Un mapa de «áreas de riesgo» en una ciudad segregada oculta quién puso el riesgo ahí, por qué, y en beneficio de quién.

Snow, de hecho, sabía esto. Su mapa fue un acto político. Derribó una teoría oficial y propuso una intervención concreta: retirar la manivela. El mapa sin la acción es solo estética de datos. Con la acción, es un instrumento de cambio.

¿Cómo incorporar GIS no como técnica, sino como pensamiento crítico? ¿Cómo enseñarlo sin convertirlo en herramienta de planificación tecnocrática? ¿Cómo hacer que los estudiantes de arquitectura, sociología, economía y política vean el territorio no como contexto sino como estructura?

La respuesta no está en un software mejor.

Está en reconocer que John Snow no fue un geógrafo ni un ingeniero. Fue un pensador que entendió que para intervenir en la realidad, primero tenía que verla completa. Mapeada. Estructurada. Real.

Marta Pulido. Desarrolladora GIS y arquitecto.

QGIS Cloud makes it possible to edit geospatial data collaboratively directly from the web browser. This is especially useful when several users need to update the same dataset without installing or configuring a local QGIS project.

I am struggling to come up with an idea for what to map next. A bit of a brain freeze. Have you got an idea? Leave a suggestion in the comments.

Week 15 was my peak week before Quad Rock on May 9. I didn't run a lot, but it was all high quality running.

• 14 hours, 23 minutes all training

• 24.8 miles running

• 6,020 feet D+ running

Tuesday I hiked and ran up and down Green Mountain in Boulder, my first time on that mountain. I went up the steeper east side and down the more runnable west side. The trail is ridiculously steep: in the first mile I gained 1,300 feet of elevation. There's a ladder at one point, that's how steep it is. The second mile has a short runnable section and averages only 19%. I went steadily to the top and ran the downhills of Ranger and Gregory Canyon as fast as I could while sight-reading. Green Mountain is fun, easy to access, and loved almost to death by Boulderites. The Amphitheater and Saddle Rock trails are in sad shape.

The geology of Boulder's Mountain Parks and Lory State Park are similar, but because the Green Mountain intrusion of the Boulder Creek Batholith is broader and 1,000 feet higher than at Horsetooth Mountain and Arthur's Rock, there is no schist or gneiss to be found on Green Mountain. It was shoved aside a billion and a half years ago. The red Fountain Formation sandstone that provides Boulder's striking Flatirons backdrop is immediately adjacent to igneous grandiorite and pegmatite.

Thursday I ran Quad Rock's second climb and first descent from the Horsetooth Open Space trailhead. I went hard for half of the climb and got some personal bests on a few segments. I was close to a personal best on the descent as well. Some parts of Spring Creek are in such bad shape that I rode my brakes to stay safe. Hopefully we'll get some moisture before Quad Rock, that would keep the rocks and gravel a little more glued down.

Saturday I went out for 13 miles on the Quad Rock course with other local runners. I pushed on the climbs again, got a few PRs, and a near PR on the Mill Creek climb pretty easily.

The other half of my week 15 training time was spent on my bike, on my yoga mat, or moving weights. Daily crunches, calf raises, and eccentric heel drops are keeping my hips and Achilles tendons, perennial sources of pain, in great shape. My knees are the only things bugging me now, and they'll be okay once I'm warmed up and racing.

Speaking of heel drops, I got a great tip recently from Dr. Tonya K. Olson on the Trail Runner Nation podcast: unless your heels touch down on a surface below your toes, your body may not adapt as effectively as it could. I'd been doing heel drops into space, standing on a stair step, but have switched to dropping from a thick book (Sunset Magazine's Western Garden Book, specifically). I believe it's making a difference.

Week 16 will be fine tuning, not tapering. I will run hard, but in smaller doses.

The many high summits of the Indian Peaks Range, with a modest snowpack, viewed from the top of Green Mountain (2.477 meters).

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

Hace unos días lanzamos una encuesta para decidir si se celebraba y en caso afirmativo, cómo y dónde celebrar la próxima QGISesCamp 2026. Queríamos escuchar a la comunidad, contrastar opciones y tomar la decisión con criterio compartido. Y eso es exactamente lo que ha pasado.

Tras analizar los resultados, desde la Junta de la Asociación QGIS España hemos decidido que finalmente la QGISCamp España 2026 se celebrará en Madrid.

No ha sido una decisión automática. Ambas propuestas han estado muy igualadas, con argumentos diversos, pero entendemos que la propuesta ganadora, Madrid, ha destacado por su accesibilidad, su capacidad de acogida y las facilidades logísticas para organizar un encuentro cómodo, presencial y centrado en lo que de verdad importa: compartir conocimiento, experiencias y ganas de seguir construyendo comunidad en torno a QGIS.

La QGISCamp España, ante todo, un punto de encuentro. Un día para reencontrarnos, poner cara a quienes solo conocemos por canales o repositorios, y hablar de QGIS sin prisas ni jerarquías. Talleres, charlas, pasillos, cafés y conversaciones que no caben en un programa cerrado.

El aforo estará limitado a 70 personas (por el momento), por lo que la inscripción se realizará por orden de registro mediante el formulario al que se podrá acceder desde este enlace.

Si tienes claro que quieres venir, te recomendamos inscribirte en cuanto sea posible, sin embargo, si tienes dudas, mejor espera para no ocupar una plaza que puede ser ocupada por otra persona.

Gracias a todas las personas que habéis participado en la encuesta y habéis dado vuestra opinión. Este evento es vuestro también.

¡Nos vemos en Madrid!

Welp, I'm joining the ranks of the unemployed tech workers again.

As before, I'm in a good situation. I don't depend on my former employer for health insurance. I've got some severance and savings, my family is in good health, we have a roof over our heads, and I have good connections. I don't feel afraid.

But maybe I should? The job market is worse than last time this happened to me. I've seen experienced and talented people go for weeks and months without offers, and read some harrowing stories about what under-employment looks like for older tech workers these days.

After a little detour into the biomedical field, I'm looking to get back into helping to solve important geospatial problems. If you've got them, please let me know.

Hello, my name is Sean Gillies, and this is my blog. I write about running, cooking and eating, gardening, travel, family, programming, Python, API design, geography, geographic data formats and protocols, open source, and internet standards. Fort Collins, Colorado, is my home.

Email me with questions or comments on any of my posts: sean.gillies@gmail.com.

Update: I'm currently looking for work in the geospatial field, remote or in Colorado. Please check out my CV.

We want to share some updates we have made on the QGIS Plugin Repository. In January 2026 we shared QEP 409. The proposal seeks to improve the general working practices with QGIS plugins, adding some optional and some mandatory checks to every plugin that gets published in the QGIS plugin repo. This builds on initial work (see PR) we did to run ‘soft’ checks on every plugin when they are published.

We also ‘back ran’ the new security checks on every existing plugin in the plugin repository (latest versions only) and assigned them a security badge without blocking or removing any plugin from being published.

Now if your plugin has flagged issues you will see a badge like this (in red below):

If your plugin passes all checks, you will see a green badge like this:

If you see a small ‘i’ on the left there may still be some non-blocking checks to look at.

If you are the owner of a plugin, you can log in to https://plugins.qgis.org and review the issues that have been flagged for your plugin:

If you expand the detail blocks, you can see the individual issues that were flagged:

There are two blocking issue categories (that will prevent you from publishing your plugin) and additional non-blocking issue categories (that are advisories only). You can see all the details at the information page here:

https://plugins.qgis.org/docs/security-scanning

We would like to note that these security advisories and badges are only shown on the plugins website, the plugin manager in QGIS Desktop does not yet provide any indication of the security scan results.

What to do if you have a red badge on a plugin you manage?

Firstly, don’t panic. Almost all plugins initially have this badge, but we expect over time that the repository is populated with ‘green badged’ plugins as developers publish their updates. Then review the issues listed in the report and fix them systematically, refer to https://plugins.qgis.org/docs/security-scanning for the specific tools we use on the server if you want to run them locally too.

What to do if you see a red badge on your favourite plugin.

Again, don’t panic. In a year’s time when most plugins have been updated we expect green badges to be the norm, but for now, just know that we are working on improving the security of our plugin ecosystem.

What if my plugin has a flagged issue for something that is a feature?

We know that in some cases you may actually need to embed API keys or credentials or do things that raise a flag. QGIS does not play an enforcement role beyond requiring that all newly uploaded plugins are green flagged. You can use pragmas / overrides where needed. What we are trying to do is ensure that plugin developers have visited each reported issue, considered it and either consciously chosen to ignore it, or fixed it.

What if I still have questions?

Please file a ticket at https://github.com/qgis/QGIS-Plugins-Website/issues

I have an issue with XXX

We are aware that there are some teething problems with our ruleset e.g. hashlib.md5, xml library flagging etc. Please raise an issue if you think the rules are too strict and we will update them accordingly. If you want to review how the scanning is implemented, please see https://github.com/qgis/QGIS-Plugins-Website/blob/master/qgis-app/plugins/security_scanner.py

La versión 2.7 de gvSIG Desktop incluye una nueva herramienta que permite convertir coordenadas entre distintos sistemas de referencia, que facilita por ejemplo el poder buscar coordenadas de puntos que se tienen en un sistema diferente al de la vista desde la propia aplicación, y no tener que acudir a herramientas externas. En el caso de coordenadas geográficas se puede seleccionar formato decimal, o grados, minutos y segundos.

Esta herramienta complementa al capturador de coordenadas, herramienta que ya existía en versiones anteriores de gvSIG Desktop, y con la que se podía obtener las coordenadas de un punto sobre la vista en el sistema de referencia elegido, aunque la vista estuviese en un sistema diferente. Esta herramienta permitía además guardar dichos puntos, para ser utilizados en algunos geoprocesos.

En el siguiente vídeo se muestra el funcionamiento de ambas herramientas:

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

Se você já trabalha com dados geoespaciais, provavelmente domina análise. Mas deixa eu te provocar:

Você sabe transformar isso em uma solução acessível na web?

Porque existe uma diferença enorme entre:

Gerar mapas
E entregar uma plataforma que outras pessoas realmente usam

E é exatamente aí que entra o WebGIS.

Hoje, quem se destaca não é só quem analisa dados… É quem consegue:

Centralizar informações
Publicar serviços padronizados (OGC)
Criar aplicações acessíveis via navegador
Controlar acesso e usuários
Escalar o uso dos dados

Em outras palavras: sair do desktop e ir para internet.

Agora vem o ponto que trava muita gente:

“Pra fazer isso eu preciso programar?”

Não.

Com as ferramentas certas, você consegue construir um WebGIS completo usando:

PostgreSQL + PostGIS
GeoServer
GeoNode

Tudo integrado, utilizando tecnologias open source já consolidadas no mercado. E mais importante: você aprende o fluxo completo, não só ferramentas isoladas.

Dado → Serviço → Aplicação → Usuário

Na prática, isso significa que você será capaz de:

Estruturar dados espaciais de forma profissional
Publicar mapas e serviços na web
Criar portais geoespaciais completos
Desenvolver dashboards e GeoStories
Gerenciar permissões e acessos

Esse não é um curso de programação. É um curso para quem quer resultado aplicado, utilizando ferramentas prontas e poderosas. Se você quer parar de entregar arquivos e começar a entregar soluções acessíveis, escaláveis e profissionais…

Esse é o próximo passo.

O curso é ministrado na modalidade EAD Ao Vivo, com aulas síncronas, porém, as aulas são gravadas e ficam disponíveis ao aluno por 12 meses no nosso portal do aluno.

Garanta sua vaga:

https://geocursos.com.br/webgis
https://whats.link/geocursos

GeoServer 3.0-RC is now available, and with it we can celebrate something bigger than a release candidate.

This milestone is the concrete outcome of a successful community crowdfunding campaign.

When we launched the GeoServer 3 crowdfunding initiative in September 2024, the goal was ambitious. GeoServer needed more than incremental maintenance. It needed a full platform modernization, including a new generation user experience, a stronger security foundation, a modern Java stack, improved raster processing, and the engineering effort required to carry those changes across the broader GeoServer ecosystem.

That work is now visible in GeoServer 3.0-RC.

From campaign to release candidate

The GeoServer 3 crowdfunding effort set a total target of 550,000 €. Camptocamp, GeoCat, and GeoSolutions each committed 50,000 €, establishing a community funding goal of 400,000 €. In May 2025, the campaign surpassed that goal.

That achievement mattered because GeoServer 3 was never a small upgrade. It required coordinated investment in core platform work that is essential for users, but often difficult to fund through routine maintenance alone:

• migration to a modern Spring and Jakarta based platform
• alignment with JDK 17 and current deployment environments
• replacement of aging raster processing components with ImageN
• stronger security and vulnerability management
• documentation updates and broad compatibility testing
• user interface and usability improvements across the administration experience

The consortium of Camptocamp, GeoCat, and GeoSolutions provided coordination, delivery capacity, and co-funding. Sponsors, community members, and individual donors made it possible to move from planning into implementation.

What GeoServer 3.0-RC shows

With GeoServer 3.0-RC, the results of that investment are now ready for public testing.

This release candidate introduces a modernized platform with:

• a new context-driven user experience
• a responsive administration interface
• a new full-screen layer preview
• updated documentation in Markdown
• support for modern servlet containers including Tomcat 11 and Jetty 12.1
• a straightforward upgrade path from GeoServer 2.28.x, with no changes to the GeoServer data directory

GeoServer 3.0-RC is also released together with GeoTools 35-RC and GeoWebCache 2.0-RC, making this an important ecosystem milestone, not just a version bump.

Why this matters for open source sustainability

Crowdfunding is often discussed in theory as a way to support open source. GeoServer 3 offers a practical example of what that support can achieve.

This campaign did not fund a narrow feature request. It funded the kind of foundational work that keeps a critical open source project healthy: technical modernization, security upgrades, ecosystem testing, documentation improvements, and long-term maintainability.

That is exactly the kind of work communities depend on, and exactly the kind of work that is hardest to finance unless users and organizations step forward together.

GeoServer 3.0-RC proves that this model can work.

Help us finish strong

The arrival of GeoServer 3.0-RC is also a call for community testing.

We encourage everyone to try the release candidate in their own environment, especially for:

• upgrade workflows from GeoServer 2.28.x
• the new user interface and administration workflows
• deployments on Tomcat 11 and Jetty 12
• raster-heavy and tiling-heavy workloads
• extension compatibility and operational edge cases

You can download GeoServer 3.0-RC from the release page, review the upgrade instructions, or quickly test the Docker image:

docker run -p 8080:8080 docker.osgeo.org/geoserver:3.0-RC

Please share your feedback on the GeoServer 3.0-RC discourse thread.

Thank you

GeoServer 3.0-RC is an important technical milestone, but it is also a community milestone.

Thank you to the organisations, individual donors, developers, testers, and sponsors who helped make this happen. And thank you to the consortium teams at Camptocamp, GeoCat, and GeoSolutions for carrying the work from campaign to release candidate.

GeoServer 3.0-RC is here because the community decided this work was worth funding.

That is worth celebrating.

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.

I needed my training to begin to peak in week 14. Quad Rock is in 20 days (at this writing), and I won't get much adaptation to workout loading in the last 13 days. Weeks 14 and 15 would be my last opportunities to get faster and stronger before the race. Fortunately, a return to good health and favorable weather helped make this my best week yet.

• 13 hours, 8 minutes all training

• 42.7 miles running

• 8,550 feet D+ running and treadmill

The first block of my training was dedicated to power and pure speed, The second to intense aerobic efforts. This last block is about going up and down technical mountain trails at my race pace or a bit faster. In practice, I push pretty hard for half of each climb, run the downhills as fast as I can, and otherwise keep it easy, but not slow.

I did three workouts like this, plus two shorter tempo runs at Pineridge Open Space, which is flatter than the Quad Rock course. Five days of comfortably hard to just plain hard running, a recovery ride on Tuesday, and a full day off to recover on Friday.

Today I went for a loop in Lory State Park that I did five weeks ago. The loop includes the last seven-mile stanza of the 25-mile QR poem: a 1,000 foot climb up from the Arthurs Rock aid station, some rolling terrain, and a 1,100 foot descent to the finish line. I did the loop in the same time as I did in March, but at a noticeably lower level of effort. I'm counting on being able to run at an even faster pace at a higher level of effort in May.

Thursday I ran at elevation for the ffirst time this season, a loop around Lumpy Ridge in Rocky Mountain National Park that begins just below 8,000 feet and tops out just above 9,000 feet. There is no snow to speak of at Lumpy Ridge. If the aspen in the Cow Creek drainage on the more remote north side of Lumpy Ridge had more leaves, you might think it was mid-summer.

A row of tall white aspen stems with just a few leaves, backed by dark green Douglas fir and blue spruce.

I loved seeing water in Cow Creek, even if it was only a July-level flow. At least the birds and mammals have something to drink.

A footbridge made of rough-hewn timbers spans a small mountain creek. Much local rock appears yellowish when wet, and our shallow mountain creeks appear golden.

GeoServer 3.0-RC is now available, with downloads for ( bin, war ), along with docs and extensions. We are working with OSGeo for the windows installer download, and will update this post when it is available. Windows users are asked to test out the bin download while we wait. Release available as docker image docker.osgeo.org/geoserver:3.0-RC .

This is a release candidate intended for public review and feedback. GeoServer 3.0-RC is made in conjunction with GeoTools 35-RC, and GeoWebCache 2.0-RC.

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

Please Test GeoServer 3.0-RC

We encourage everyone to try GeoServer 3.0-RC in their own environment, especially for upgrade workflows, the new user interface, and deployment on Tomcat 11 and Jetty 12. Real-world testing is the best way to catch regressions and compatibility issues before the final 3.0 release.

You may also quickly test the docker image using:

docker run -p 8080:8080 docker.osgeo.org/geoserver:3.0-RC

Please share your success, feedback, questions, and any issues you encounter on the user forum GeoServer 3.0-RC Release Candidate discourse thread.

GeoServer Cloud 3.0.0-RC

GeoServer Cloud 3.0.0-RC has also been released alongside this candidate. Cloud-native deployments can now try out GeoServer 3 in microservices form, see the v3.0.0-RC release notes for details.

To get started, follow the Kubernetes quickstart and share your feedback so we can iron out any remaining issues before the final 3.0.0 release.

Welcome to GeoServer 3

We are overjoyed to share this update 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.

There will be more technical details in the final release announcement - but for now we wish to say thank you.

Straightforward upgrade

We have taken great pains to make the upgrade process seamless from GeoServer 2.28.x.

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

   Download and try GeoServer 3.0-RC today!

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

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

   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 available to take over the responsibilities of the previously available Keycloak and OAuth2 plugins.

Please see the upgrade instructions for details.

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.

  

Details coming soon to the developers guide!

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 is overjoyed to support Tomcat 11.0.x and Jetty 12.1 application servers 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:

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.

New OAuth2 OpenID Connect Security Integration

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.

• If you previously used Keycloak, there are setup instructions for configuring with Keycloak.
• If you previously used an OAuth2 integration, you can find individual setup instructions for Google, Azure, and GitHub.

We are asking specifically for public testing during 3.0-RC timeframe allowing this module to be included as an extension for 3.0.0 release.

Thanks to Alessio Fabiani and others for key improvement. We are very much looking forward to having OAuth2 OpenID Connect support included in GeoServer.

New Documentation

The long-awaited transition to Markdown documentation has finally arrived. Welcome to our new User Manual. The older GeoServer 2.x documentation is available at Docs Archive or via the version switcher. Please help out by fixing any remaining small issues or log an issue for Peter to address.

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

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.

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.

Release notes

New features:

• GEOS-12063 [GSIP-238] GeoServer 3 UI / UX Refresh

Improvements:

• GEOS-11886 Sort entries in all .properties files alphabetically
• 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-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

Bugs:

• GEOS-10509 WFS Request fails when XML POST body is larger than 8kB
• 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-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-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

Tasks:

• GEOS-11987 ImageN 0.9.1 migration requires renaming of registryFile.jai to registryFile.imagen
• GEOS-12004 Make WMS independent 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-12071 Remove the WPS remote module
• GEOS-12064 CSS: add documentation for localized @title and @abstract metadata

Sub-tasks:

• 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-RC 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

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.x Series

Additional information on the GeoServer 3.0.x series:

• GeoServer 3.0.x User Manual

Release notes: ( 3.0-RC )

É oficial! É com muita alegria e entusiasmo que confirmo minha participação no FOSS4G 2026 em Hiroshima! 🇯🇵

Para quem não está familiarizado, o FOSS4G é o maior evento do mundo dedicado ao software livre geoespacial. Organizado pela OSGeo, é o lugar onde desenvolvedores, usuários e entusiastas se reúnem para moldar o futuro das geotecnologias.

Gratidão à Comunidade

Antes de falar das apresentações, quero expressar meu profundo agradecimento à comissão organizadora. Sabemos que realizar um evento desta magnitude exige uma dedicação quase sobre-humana. O o trabalho de vocês é fundamental para fortalecer o ecossistema global de software livre geoespacial. Obrigado por tornarem isso possível!

A Bandeira Brasileira no Japão 🇧🇷🤝🇯🇵

Nesta edição, terei a honra de levar um pouco da força da nossa comunidade para o território japonês. O Brasil tem uma das comunidades geoespaciais mais vibrantes do planeta, e é hora de mostrar como estamos transformando dados em decisões reais. Vou apresentar quatro trabalhos que cobrem desde a base comunitária até a aplicação na gestão pública:

1. QGIS Brasil: Quebrando a Barreira do Idioma

Título: Bridging the Language Gap: How the QGIS Brazil Community Drives Open Source Adoption in the Global South.

Neste trabalho, discuto como a tradução e a produção de conteúdo local são fundamentais para a democratização do acesso às geotecnologias.

2. QGIS Brasil: 16 Anos de História e o Caminho para o QGIS LATAM 2024

Título: Scaling Geospatial Communities: 16 Years of QGIS Brazil and the Path to LATAM 2024.

Uma retrospectiva da nossa jornada e como estamos expandindo nossa influência para toda a América Latina.

3. A Jornada da OSGeo Brasil

Título: The Map of Our History: The Journey of OSGeo Brazil.

A trajetória da nossa representação nacional e o fortalecimento do software livre local.

4. Inovação Pública na Sefin Caucaia

Título: From Legacy Data to National Standards: Preparing a Brazilian City for Federal Interoperability with FOSS4G.

Talvez um dos meus relatos favoritos: como estamos usando ferramentas de código aberto para modernizar a Secretaria de Finanças de Caucaia, transformando dados legados em padrões nacionais de interoperabilidade.

O que esperar?

Além das palestras, o FOSS4G é sobre troca. Mal posso esperar para aprender com os mestres, rever amigos da comunidade global e, claro, trazer muitos insights (e talvez alguns adesivos raros) para compartilhar com vocês aqui no blog.

O próximo adesivo é o FOSS4G Hiroshima 2026!

Se você também vai estar em Hiroshima ou quer saber mais sobre algum desses temas, deixe seu comentário abaixo!

Nos vemos no Japão! Ou, como dizem por lá: Hiroshima de aimashou! 🗾🗺️

Week 13 started out pretty strong. I returned to my favorite Monday evening yoga class, did a fun run with strides at Pineridge on Tuesday, and then a hard running interval workout on Towers Trail in Horsetooth Open Space on Wednesday. Thursday I had cold symptoms again and shifted to dog walking and bike riding for the rest of the week. The running numbers for the week are nothing much.

• 11 hours, 35 minutes all training

• 14.6 miles running

• 2,041 feet D+ running

By Saturday afternoon I felt much better, which gave me hope for a solid week 14.