Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
The Random Points on Lines… is a simple interface and a user-friendly QGIS plugin that enables to generate a specified number of random points along selected line layers within QGIS. Users can control the layer selection and the number of points generated.
The Spatial Analysis Agent is a user-friendly plugin that serves as a “Copilot” in QGIS software. This Copilot allows users to perform geospatial analysis directly within QGIS using natural language queries, making it accessible for both experts and beginners. The plugin leverages the full potential of over 600 QGIS processing tools, and other external tools such as Python libraries (e.g., Geopandas, seaborn, etc.). Whether working with vector data, raster analysis, the Spatial Analysis Agent offers a flexible, AI-driven approach to enhance and automate GIS workflows.
In the last month some AI-related plugins became available for users, namely IntelliGeo and TreeEyed, which in addition to the increasing number of tools, greatly contribute for the adaptation of QGIS to current and future needs, showcasing it as one of the best options for beginners and experts alike to conduct a number of geospatial analyses.
As stated by their authors, with IntelliGeo there’s a chat interface where users can detail their requests, and the output is either a PyQGIS code or a graphical processing model, which can in turn be executed directly in QGIS.
As for the TreeEyed plugin, its main objective is the monitoring of trees by generating vector and raster datasets from high resolution RGB imagery.
Overview
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
Processing plugin that adds several scripts to assist in decision making and validation of line-type vector networks by generating inconsistencies, further expanding the “Network Analysis” tool.
By simply drawing polygons or clicking on existing polygons, this extension makes it possible to download data from OpenStreetMap (OSM) or the iDAI.gazetteer and display it on the map, including all existing attributes. The plugin is designed so that other services can also be easily integrated in the future.
This year’s user conference took place in Bratislava, organized by the Slovak QGIS User Group and hosted at the Slovak University of Technology Faculty of Civil Engineering. The event was sold out early and the venue was full of energy and excitement.
If you missed the conference or couldn’t make it to a talk due to too many great overlapping sessions, you now have the opportunity to catch up with everything on the UC 2024 playing list:
Thanks to the organizers, speakers, sponsors, and all participants for the wonderful event.
“Help us create the world’s most advanced open database on litter, brands & plastic pollution.”
This sentence welcomes us to the website of the OpenLitterMap project, which aims at providing tools for any and all citizens to capture data on litter worldwide. This data can now be directly accessed in QGIS for visualisation and analysis purposes, thanks to the efforts of the plugin’s author NaturalGIS. Well done to everyone involved, and we wish all the luck to this great project.
Overview
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
This plugin allows users to directly access SSEC RealEarth web services public catalog of near real-time satellite imagery and related ancillary data through the OGC standard web services of WMTS and WFS. A login to RealEarth is recommended to extend data volume quota before watermarking occurs, but is not required.
With the QGIS Grant Programme 2023, we were able to support six proposals (four in the first round and two in the second round) that are aimed to improve the QGIS project, including software, infrastructure, and documentation. The following reports summarize the work performed in the first four proposals:
Existing Processing algorithms Voronoi Polygons and Delaunay Triangulation have been ported to C++ and now use GEOS instead of the unmaintained Python module.
Two algorithms for generating XYZ tiles (directory and MBTiles variants) have been ported to C++ using a safer and cleaner multi-threading approach.
The Align Rasters tool, which was not exposed to Processing, has been removed and a new Processing algorithm with the same functionality has been added.
The existing Raster Calculator algorithm has been ported to C++. The algorithm now has two variants: a toolbox version that works the same way as before, and a modeler version that uses the same approach to input naming as the GDAL raster calculator.
As of QGIS 3.34, QGIS can now create and handle vertical and compound CRSes.
In QGIS 3.34 coordinate transforms were reworked so that they function correctly with vertical transformation, if both the source and destination CRS have vertical components.
In QGIS 3.36 the coordinate reference selection widgets were updated to offer choices of 2d only, compound, or vertical only CRSes.
In version 3.38, we introduced a new setting for QGIS projects, for their vertical reference system. Users can control this through project properties, and it’s accessible via PyQGIS and via associated expression variables (eg @project_vertical_crs) for use in print layouts.
Similarly, in 3.38 we introduced the API support for map layers to have a vertical CRS. (This was not exposed to users in 3.38 though)
In QGIS 3.40 so far we have exposed the vertical CRS setting for vector layers to users (via the layer properties dialog), allowing users to specify the associated vertical CRS for these layers. The vertical CRS is respected in elevation profile plots, in Identify tool results, and in 3D Map views (assuming the 3D map is created with an associated vertical CRS).
There is an open pull-request for 3.40 to expose the vertical CRS for point cloud layers in a similar way, with the vertical CRS being respected in elevation profiles, identify tool results, and 3D map views
We have open pull requests for 3.40 to show layer vertical CRS information in the layer properties “information” pages, and add expression variables at the layer scope (eg @layer_vertical_crs).
Improve test result handling on QGIS CI (#268)– Report Any tests which fail a rendering comparison will write a descriptive comment to the PR. The comment details which render tests failed, where they are in the code, and includes some helpful pointers to downloading the full test report and the QGIS developer documentation. We also implemented lots of improvements in running the tests locally and how the render test reports are generated and presented to developers.
Thank you to everyone who participated and made this round of grants a great success and thank you to all our sustaining members and donors who make this initiative possible!
For the last month of July, one short of 30 new plugins were published in the QGIS plugin repository.
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
DeraPro for projects and studies allows the download of the reference spatial data of Andalusia and make a cut of the information for a specific study area.
The CBERS Explorer is a specialized plugin developed to facilitate the search and retrieval of images from the China-Brazil Earth Resources Satellite (CBERS) program, specifically focusing on the CBERS-4A satellite with Wide Field Imager (WPM) data.
A comprehensive toolset for coordinate calculations, conversions, spatial operations, watershed analysis, land use analysis, and flood simulation in QGIS.
Tworzy słownik w formie pliku txt rozdzielanego tabulacjami dla wybranych warstw, program pozwala na eksport pełnych nazw pól danej warstwy oraz wersje jako powstanie po zmienie z gpkg do shp.
We recently launched our new website at QGIS.org. It is a ground-up overhaul and provides a fresh take on the first contact point for existing or potential users wishing to engage with the QGIS project and discover its value proposition.
A new strategy for QGIS.org websites
In this blog post, we would like to provide an overview of the goals that we had for building the new QGIS.org website and the bigger picture of how this website update fits into the broader strategy for our website plans for QGIS.
About two years ago, we started experimenting with building a new QGIS.org website based on Hugo. Hugo, as a technology choice, was less important than was our intent to develop a more modern site that addressed our strategic goals.
After some ‘in-house’ (i.e. volunteer-based) work to develop an initial version of the site, we received the go-ahead to use QGIS funds for this and put out a call in October 2023 for a company to support our work. This was ultimately won by Kontur.io, who, together with our volunteers, brought the work into high gear.
Initial analysis of the questions and actions to be quickly answered by qgis.org
Goal 1: Speak to a new audience
Our primary goal was to speak to a new audience. We are confident that QGIS can compete with all of the commercial vendors providing GIS software. We didn’t convey that well on our old website. We feel that QGIS was too apologetic in how it presented itself. We wanted a website which inspires confidence while addressing the needs of a corporate or organisational decision-maker who is looking at the QGIS project during their GIS software selection process.
The old website was very focused on the developer and contributor community. Obviously, those aspects are important since, without our fantastic community, the QGIS project would not exist. The messaging around open source is also important. Yet these ideas are secondary to the idea that QGIS is one of the best (if not the best) desktop GIS applications out there on the market – open-source or otherwise. We need to present it in this professional perspective.
So, the first goal was to change the messaging to focus on QGIS’s value proposition and take a very professional approach to presenting ourselves on the website.
User group and requirements analysis for the potential qgis.org visitors
Goal 2: Harmonisation
The second goal was to start the process of harmonising all of our website properties. QGIS.org, over the years, has built many different web properties. For example, there’s the plugins website, the feed, the changelog, the sustaining members website, the lessons website and the certification website, the new resources hub website, the API documentation, the user documentation, the user manual, the training manual, various other documentation efforts, and more. Some of those are combined in one application, There are also some less well-known resources, like our analytics.qgis.org and another one for plugin analytics. In short, we’ve a lot of resources!
With so many different web properties, they’ve devolved over time: each has its own look and feel, navigation approach and how you interact with it. Some of them were translated, and some of them were not. We want to harmonise all of these sites so that the user does not notice any change in user experience when they move from one QGIS-related site to another.
Goal 3: Harmonising deployment
In the underlying process of these changes, we’re also redeploying all of the websites on new servers, which are more up-to-date and use better security and maintenance practices. Plenty of work is happening in the background to ensure that all of the servers are in a better-maintained state, document how they’re maintained, and so on.
Goal 4: A hub and spokes
The objective of the new site design is to allow quick movement between the QGIS auxiliary sites. The QGIS.org site will form a hub that effortlessly takes visitors to whichever QGIS-related site they need to complete the task they are busy with. If you’re moving between these sites, the experience should be seamless. You should not really even be aware that you’re moving between different websites. Other than looking at the URL bar, the user presentation and experience should be harmonious between all of them.
One way we are planning to achieve this is to have a universal menu bar and footer. You will see that in the new website’s design, there is a menu bar across the top. This menu bar has two levels: the top menu and the second level, where the search bar is.
The universal menu bar
In this second row, auxiliary sites will have their own sub-menu whilst keeping the shared top-level menu. So if you, for example, are moving around in plugins and want to review the plugin list or submit a new plugin, all of that navigation will be on the second line where the search bar is currently. Regardless of which subdomain you are on, the top-level menu bar will be the same, allowing you to easily navigate back to the hub or to another subdomain.
The footer will be unified and shared between all sites, and the cascading style sheets and styling will be unified across all of the QGIS websites.
In the next phase, we will work to achieve this coherence across all the websites, though we still have a few more tweaks to make to the qgis.org site first.
Goal 5: DOTDOTW – do one thing, do one thing well
We plan to break some auxiliary websites apart into separate pieces. So, for example, the changelog management, certification management, sustaining members management, and lessons management are all in one Django app. We will split them into small single-purpose applications using some common UX metaphors so that each is a standalone application that makes it easy for a potential contributor to understand everything the application does. This will also simplify management as we can upgrade each auxiliary site on separate development cycles. We will also finally have semantic URLs, e.g. certification.qgis.org, to take you to the different areas of interest on the site.
The plugins.qgis.org is also going to be refactored so that it just has plugins and not the resource sharing we’ve added in the last few years. The resource sharing will go into its own subdomain. Similarly, the Planet website will get split into its own website (the planet is a blog aggregator or RSS aggregator) that will be in its own managed instance. Some other components (like the analytics) are difficult to split out like this because they’re linked to the same database. We will try to make sure that those are more discoverable and theme them as much as possible to match the rest of the website experience.
Goal 7: Encapsulation
Another goal we had for the QGIS.org makeover was to make the site performant and self-contained. By self-contained, we mean that it should not ‘call’ out to CDN, Google or other platforms for resources like fonts, CSS frameworks, javascript libraries, etc. There were two reasons for this:
These platforms often use such resources to track users as they move around the Internet, which we want to avoid as much as possible.
We want to wholly manage our site, be able to fix any issues independently and generally follow a path of self-determination.
Our approach also facilitated the creation of a very performant website, as you can see here. We will try to adhere to these principles for the auxiliary site updates we do in the future, too.
What about translations?
The question has come up: Why did we not want to translate the new QGIS.org when it was translated before?
Firstly, we should make it clear that we do not plan to remove translations from the user documentation, the user manual, and so on, where we think they have the most value.
For the main QGIS.org site, we question whether there is a high value in translating it. Here are some reasons why:
1. Lingua franca: If you are an IT manager in a non-English-speaking country and you want to evaluate some software, you’re going to run into a product page that presents itself in English – it is the norm for IT procurement to work in English for reviewing software products and so on.
2. Automation: Automated translations inside browsers are getting better and better. While these translations are still not completely adequate, we think they will be in one or two years’ time.
3. Translation integrity: Our pursuit of Goal 1 means that we would no longer find it acceptable to have partial website translations. We also need to ensure that the wording and phrasing are consistent with the English messaging. We also have concerns about the QA process regarding trust and review – we want to ensure that any translation truly reflects the meaning and intent of the original content and has not been adjusted during the translation process.
4. Cohesion: Our most important point is raised if we go back to this idea of cohesion between the different websites like QGIS.org, plugins.qgis.org and so on. As well as having the same styling, we also don’t want to switch between languages as you hop between the sites. We aim to present them all as one site. If we translate QGIS.org and then take you to our auxiliary sites, e.g., plugins.qgis.org, the feed, or certification pages, which are in English only, the experience is jarring.
So we must either translate everything into all of the same languages, or work in English. Translating everything is a mammoth task for the translators and for us to retrospectively add translation support to each platform. Thus, we prefer the approach of harmonising everything to one language and then focusing our translation efforts on three areas:
The application itself,
the user manual and
the training manuals.
We can leave the rest of the experience in English and instead focus on harmonising, for now, both in terms of look and feel and the technology used.
When we consider everything as one big website and what the bigger plan is, it is hopefully clearer why we didn’t think translating the landing page and QGIS.org was the best approach.
Further funded work
We hope to use more QGIS funding to support this work in the future. We’re also hoping to work again with Kontur to start moving all these auxiliary sites into their own projects, applying our style guidelines to each. Independently of that, Tim (volunteer), Lova (QGIS funded), and others are already getting started with this process.
Helping out
Do you have strong opinions about the website? Contact Tim on the PSC mailing list if you would like to get involved as a volunteer. We would love to hear from designers, word smiths, marketers, information architects, SEO specialists, web developers and those who think they can help us achieve our goals.
Conclusion
We hope our goals and process make sense for everybody and that we were able to lay out a clear, logical argument about why we don’t want to translate the new website quite yet. We want to focus on these overarching goals and then return to them later if they are still a priority for people. Everything we have built is Open Source and available at this repo, where you can also find an issue tracker to report issues and share ideas relating to the new website.
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
We would like the use this opportunity to highlight two plugins, Viper (QGIS snake Clone) and Active Break.
Viper allows to emulate in QGIS canvas the popular game Snake, providing a fun time and a bit of nostalgia for the “older” users. However it goes further than that, as it serves the purpose of teaching about geospatial concepts such as geometry objects (points, polygons) with their properties and methods, spatial indexing in the form of R-Tree, but also programming in QGIS, as well as other aspects.
On a more serious tone, if it can be said that, we present Active Break, a plugin that “simply” presents messages at specific time intervals, which can be personalized by the user and range from the more technical such as “save your project”, personal or motivational like quotes from hundreds of people on multiple subjects, or perhaps the most important, routinely reminders to take a break, relax or go have lunch. This considering the long hours we spent daily in front of the computer, with all the physical and mental health, as well as social implications. Congratulations on both authors!
Overview
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
Трансформація (перерахунок) координат вектороного шару через офіційне API Державної геодезичної мережі. Translation: Transformation of vector layer coordinates through the official API of the State Geodetic Network.
“Route Builder” is a QGIS plugin with a set of tools that calculates shortest routes in street networks using data from OpenStreetMap (OSM) and using the A* (A Star) algorithm. Users can define a region, define origin and destination points (O/D) using the coordinates collected by the plugin, these coordinates of the nodes and thus calculate the shortest route between them.
ActiveBreak is a plugin for QGIS that emits messages at the top of the canvas at time intervals from the start of work, reminding the user to take an active break, take their lunch and/or reminders indicating to save their QGIS project.
From February to March of this year, 58 new plugins were published in the QGIS plugin repository.
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
Dynamic Flow is a QGIS plugin to estimate the spatio-temporal 3D gradient flow from the point observation of the attributes values such as aggregated cell-phone mobility data.
QGIS plugin for adding and modifying zone data in compliance with the GeoZone schema, facilitating sharing with partners or uploading to a central web repository.
Este plugin clasifica las redes hídricas por medio de una etapa de enriquecimiento y otra de lógica difusa. Advertencia: Versión experimental, algunos procesos pueden ser largos de aplicar.
Apply QML style files to new layers. QML files are stored in {qgis_home}\Styles directory. QML files will be applied to a vector layer when the QML file’s basename is found as a substring of the new layer’s name. QML files will be applied to a raster layer when the QML file’s label token is found as a substring of the new layer’s name. The label token is raster_style_{label}.qml.
This plugin connects your QGIS User Profile to many openly hosted web services related to mineral exploration. These include Country and State geological surveys that provide mapped geology and data such as mineral occurence locations, geophysics, geochemistry etc.
NVDB (Norwegian Administration Road Database) it’s a plugin to analyse and manipulate road objects, like (road references, trees, light poles, traffic signs, construction area, smart devices like IP Camera, tunnels, bridges, etc)
HedgeTools is a plugin for QGIS designed to extract and characterize hedges, aiming to streamline field efforts by providing information about hedge health.
Provides Rubber Sheeting and Two Point Transformations, storing to PostGIS, Oracle and MS SQL. The Rubber Sheeting algorithm uses supplied Shift Vectors and calculates the weighted average shift from the 10 nearest Shift Vectors. The Two Point Transformations handles themes with and without a CRS.
Between December 2023 and January 2024, 45 new plugins were published in the QGIS plugin repository. On top of those, we also included another 4 from the last week of November.
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
Analyzes benthic terrain for the purposes of classifying surficial seafloor characteristics that may be used in studies of benthic habitat, geomorphology, prediction of benthic fish species distribution, marine protected area design, and more
Gratis og let adgang til GeoFA (Geografiske Fagdata i GeoDanmark) i QGIS. Free and easy access to GeoFA (Geographical Professional Data in GeoDanmark) in QGIS.
Yahoo!JAPANのYOLP Web APIを利用して、検索した結果の位置を表示します。郵便番号での検索ができます。クレジット：Webサービス by Yahoo! JAPAN （https://developer.yahoo.co.jp/sitemap/） This plugin allows the user to displays the location of search results using Yahoo!JAPAN YOLP Web API.You can search by zip code.
国土地理院のAPIを利用して、住所を検索した結果の地点を表示します。住所検索した結果から選択してポイントを追加することもできます。国土地理院API（https://msearch.gsi.go.jp/address-search/AddressSearch）から取得したデータを加工して利用。This plugin allows the user to search for a address and get its coordinates using GSI API.
This plugin generates a full text search index containing all attributes of all layers of a loaded project. The user then can use a single text-input field to search within all available attributes.
QGIS User Groups all over the world have become an essential component of the QGIS community. They provide a point of contact for local users and developers and help people connect through localized communication channels or by organizing events.
Another important aspect of users groups is that many of them also have become sustaining members of QGIS.ORG. In total, their contributions account for a significant share of our project budget.
The Danish User Group now has opened a new chapter by becoming the first user group supporting QGIS on the Flagship level. And that’s a reason to celebrate and to reminisce. For example, about the awesome time we had at the first QGIS User Conference organized at the University of Copenhagen campus in Nødebo.
And who can forget how we all struggled to pronounce QGIS 2.16 “Nødebo”?
Thank you very much to everyone from the Danish user group and to all the other user groups, small and large, who support QGIS our project and help make it even better for everyone.
We’re delighted to announce Felt’s continued flagship-level sustaining membership of QGIS. Felt’s contributions will allow us to continuously improve QGIS’ functionality and documentation, as well as the QGIS project infrastructure, including our 2024 Grant Programme.
In addition to their membership, Felt is releasing a new version of the “Add To Felt” QGIS plugin. Developed by the talented team at North Road, the plugin makes it easy to upload your data from QGIS to the web, where you can share it with colleagues and clients. The newest release includes raster data support and more robust preservation of styles from QGIS to Felt. This enables seamless integration and a flexible workflow between your desktop and the web.
Don’t miss your chance to meet Felt’s team presenting “Add To Felt” at tomorrow’s QGIS Open Day.
Felt is the first user-friendly, collaboration tool for making and sharing the maps that drive your business. Felt makes it easy to visualize your data and communicate across teams quickly. Learn more at felt.com.
Thanks to our generous donors and sustaining members, we are in the wonderful position to be able to further extend our 2024 Grant Programme and to fund an additional project that came in very close 6th in the voting results:
On behalf of the QGIS.ORG project, I would like to thank the Danish User Group who stepped up and increased their support to Flagship level, joining or recurring Flagship member Felt and all our wonderful sustaining members and donors.
with € 4,500 missing to be be funded to make it possible to store encrypted credentials in a PostgreSQL database. This improvement targets QGIS Server, particularly multi-instance setups using kubernetes, with potential QGIS Desktop improvements down the road.
If you want to help make this improvement a reality, please get in touch.
Of course, the same applies if you want to help fund any of the remaining proposals:
With the QGIS Grant Programme 2023, we were able to support four proposals in the first round and an additional two proposals through the second round that are aimed to improve the QGIS project, including software, infrastructure, and documentation. The following reports summarize the work performed in the proposals.
– 162 bugreports and feature requests which were already fixed or implemented – 29 bugreports and feature requests which are invalid (data issues, wrong use of functionality, etc) – 57 duplicate bugreports and feature requests – 5 won’t fix bugreports – 5 bugreports were converted to feature requests – 33 tickets were closed (does not contain steps to reproduce, test data and no feedback was provided within several month)
Additionally we ensured that all tickets has correct tags assigned to to make them easier to find.
Existing Processing algorithms Voronoi Polygons and Delaunay Triangulation have been ported to C++ and now use GEOS instead of the unmaintained Python module. Both algorithms have been given additional parameters to disable post-processing step (adding attributes of input points for Voronoi polygons and adding feature IDs of the 3 points forming a triangle for Delaunay triangulation) and thus improve algorithm performance. The Concave Hull algorithm has been ported to C++ and uses GEOS for QGIS builds with GEOS >= 3.11, while a port of the existing implementation based on Delaunay triangulation is used for builds with older GEOS versions.
Two algorithms for generating XYZ tiles (directory and MBTiles variants) have been ported to C++ using a safer and cleaner multi-threading approach.
The Align Rasters tool (available from the Raster → Align Rasters menu), which was not exposed to Processing, has been removed and a new Processing algorithm with the same functionality has been added. To make this possible, we have added a new QgsProcessingParameterAlignRasterLayers parameter type to Processing, which provides an adapter to QList<QgsAlignRaster::Item>. The “Raster” menu item now opens the Processing algorithm. We have also added a separate, simplified modeler-only version of the algorithm that accepts a single raster to align and returns a single raster layer output.
The existing Raster Calculator algorithm has been ported to C++. The algorithm now has two variants: a toolbox version that works the same way as before, and a modeler version that uses the same approach to input naming as the GDAL raster calculator (in the formula, you should use letters instead of layer names). The old algorithm implementation has been retained for compatibility with existing models and will be removed in QGIS 4. We have also added a separate raster calculator algorithm for creating virtual raster layers.
Improve test result handling on QGIS CI #268– Report While the original proposal was explicitly stated to be a research project with no guarantees of success, the end result is predominantly a success (with some limitations!). You can see the new failure handling in action in this PR.
What we have now is that any tests which fail a rendering comparison will write a descriptive comment to the PR, as shown in the above link. The comment details which render tests failed, where they are in the code, and includes some helpful pointers to downloading the full test report and the QGIS developer documentation.
Originally, I hoped to link directly to the full test report or include it as an attachment to the comment. Unfortunately this is NOT possible given the current Github API. There’s a bunch of notes I’ve added to the initial comment which link to the limitations / feature requests on Github’s side, so we can monitor the situation and further improve the reports if/when Github add this functionality.
As well as the above described improvements on the CI side, I’ve also implemented lots of improvements in running the tests locally and how the render test reports are generated and presented to developers!
Unification of all geometric and topological verification methods #236 – Report Our efforts are primarily focused on two main aspects of the proposal: 1. Unification of Algorithms: This component entails both refactoring existing algorithms and introducing new ones. While the refactoring phase did not reach the level of ambition initially envisioned, considerable cleanup has been achieved, particularly in eliminating code duplications, as evidenced by the PR submitted [1][2][3]. Other deduplications could be considered, but the main issue is not to break the small optimizations or adaptations to the logic of the existing code. 2. Integration of Geometry Checker Algorithms: Following the discussions within the QEP framework, we have decided to transition algorithms to those already present in the geometry checker. These algorithms encompass topological considerations. Unfortunately, due to timing constraints with the year-end and the feature freeze period, this integration was not yet completed. [4][5]
Processing Integration: Efforts have been made to incorporate the geometry checker’s algorithms into the processing framework [6][7][8]. Regrettably, these efforts have not yet been fully realized. We encountered challenges in aligning processing with the logic of the geometry checker. However, the ongoing PR by Jacky shows promising progress in overcoming these obstacles. We are optimistic about achieving the integration of geometry (and topology) checker algorithms into processing for the upcoming version. This integration aims to streamline ETL processes for verification and correction tasks, thereby enhancing codebase cleanliness.
The remaining project reports will be added as the projects wrap up.
Thank you to everyone who participated and made this round of grants a great success and thank you to all our sustaining members and donors who make this initiative possible!
The QGIS.ORG Grant Programme aims to support work from our community that would typically not be funded by client/contractor agreements. This means that we did not accept proposals for the development of new features. Instead proposals focus on infrastructure improvements and polishing of existing features.
Voting to select the successful projects was carried out by our QGIS Voting Members. Each voting member was allowed to select up to 6 proposals. The full list of votes are available here (on the first sheet). The following sheets contain the calculations used to determine the winner (for full transparency). The table below summarizes the voting tallies for the proposals:
A couple of extra notes about the voting process:
Voting was carried out based on the technical merits of the proposals and the competency of the applicants to execute on these proposals.
No restrictions were in place in terms of how many proposals could be submitted per person / organization, or how many proposals could be awarded to each proposing person / organization.
Voting was ‘blind’ (voters could not see the existing votes that had been placed).
We received 39 votes from 21 community representatives, 17 user group representatives, and the OSGeo voting member.
On behalf of the QGIS.ORG project, I would like to thank everyone who submitted proposals for this call!
We are happy to announce that QGIS User Conference will take place on 9-10 September 2024 in Bratislava, Slovakia.
The traditional Contributor Meeting will be held right after the conference on 11-13 September 2024 at the same venue.
Learn more about the user conference and the contributor meeting at the event’s web site: https://uc2024.qgis.sk/
The call for papers for the user conference is now open – you can submitproposals for talks and workshops by 31 March 2024: https://uc2024.qgis.sk/call-for-papers/
We have also started call for sponsors, with sponsorship opportunities at various levels. More details here: https://uc2024.qgis.sk/sponsors/
User Conference
The QGIS User Conference is an annual event that brings together users and developers of QGIS. The conference provides an opportunity for attendees to learn about the latest developments in QGIS, share their experiences with others, and network with other QGIS users and developers.
Contributor Meeting
QGIS Contributor Meetings are volunteer-driven events where contributors to the QGIS project from around the world get together in a common space – usually a university campus. During these events, contributors to the QGIS project take the opportunity to plan their work, hold face-to-face discussions and present new improvements to the QGIS project that they have been working on. Everybody attending the event donates their time to the project for the days of the event. As a project that is built primarily through online collaboration, these meetings provide a crucial ingredient to the future development of the QGIS project. The event is planned largely as an ‘unconference’ with minimal structured programme planning.
We are very pleased to announce that this year’s round of grants is now available. The call is open to anybody who wants to make a contribution to QGIS funded by our grant fund, subject to the call conditions outlined in the application form.
The deadline for this round is in four weeks, on 14 March 2024.
There are no new procedures in 2024. Please note the following guidelines established in previous years:
The proposal must be submitted as a ‘QEP’ (QGIS Enhancement Proposal) issue in the repo: https://github.com/qgis/QGIS-Enhancement-Proposals (tagged as Grant-2024). Following this approach will allow people to ask questions and provide public feedback on individual proposals.
Proposals must clearly define the expected final result so that we can properly assess if the goal of the proposal has been reached.
The project budgets should account for PR reviewing expenses to ensure timely handling of the project-related PRs and avoid delays caused by relying on reviewer volunteer time.
In the week after the QEP discussion period, the proposal authors are expected to write a short summary of the discussion that is suitable for use as a basis on which voting members make their decisions.
The PSC of QGIS.ORG will examine the proposals and has veto power in case a proposal does not follow guidelines or is not in line with project priorities.
For more details, please read the introduction provided in the application form.
We look forward to seeing all your great ideas for improving QGIS!
We recently held our 2023 QGIS Annual General Meeting. The minutes of this meeting are available for all to view.
This year, we did not have PSC elections. Anita Graser will continue as Vice-Chair, I will continue to serve on the PSC as chair, and our longstanding treasurer, Andreas Neumann, will complete the board. Furthermore, Jürgen Fischer, Alessandro Pasotti, and Régis Haubourg will continue on the PSC. Last but certainly not least, the PSC is completed by our project founder, Gary Sherman, and long-term PSC member Tim Sutton, who serve on the PSC as honorary PSC members. They both set the standard for our excellent project culture, and it is great to have his continued presence.
QGIS has been growing from strength to strength, backed by a fantastic community of kind and collaborative users, developers, contributors and funders. This year, we reached another important milestone for the project’s sustainability by welcoming our first flagship sustaining member – Felt. I look forward to seeing how it continues to grow and flourish.
and to reminisce. For example, about the awesome time we had at the 
