OSGeo Statement: EU Cyber Resilience Act

QGIS Planet

3.3.11 - Darién

What's Changed

  • Fix snapped coordinate cursors disappear under certain project/layer CRS conditions
  • Fix value map and value relation editor widgets' handling of special characters (such as < and >)
  • Harmonize handling of QField's multi-value relation editor widget with that of QGIS
  • Insure that the orientation value is between 0 and 360 (instead of ~-90 to 270)

Full Changelog: v3.3.10...v3.3.11

Learn More

3.3.10 - Darién

What's Changed

  • Multiple improvements to make cloud project attachments (photos, videos, audio clips, etc.) upload smoother
  • Generated print and atlas layouts as well as photos can be pushed to QFieldCloud via the project folder panel

Full Changelog: v3.3.9...v3.3.10

Learn More

Plugin Update – July, 2024

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:

MariaDB to QGIS
Fetches longitude (x) and latitude (y) data from MariaDB and writes it to a Shapefile or GeoPackage and adds it to your map.
Print Selection
Outputs selected features to text console.
DeraPro
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.
QPackageQGZ
QPackage is a tool to save both your QGIS project and data contained in the project to a new directory.
ArgentinaGeoServices
A QGIS plugin to import WMS Geoservices from Argentina.
T Vertical Sessions
Used to Vertical Sessions of Lidar Point Cloud.
BuenosAires Converter
A QGIS plugin that converts layers to EPSG:9497.
Make Sector
Plugin to create sector, circle radius, and spidergraph delimited and vector layer.
CBERS-4A WPM Explorer
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.
FPT Plot Alocation
Plot alocation for forest inventory.
QGISpell
Creates context menu spell checking for attribute data based on ENCHANT libraries.
ur-scape Data Importer
Import data to ur-scape.
MorphAL
MorphAL plugin for QGIS.
LER+
Nem adgang til LER2 forespørgsler.
Threshold to ROI
Create ROI (Region of Interest) with threshold values.
Spell Checker
Check the spelling of words in Print Layout elements.
Filter By Selection
Filter a given layer by the selected feature and attribute of another layer.
Natur i Norge kartlegging
Natur i Norge (NiN) mapping tool.
AIAMAS – AI-Assisted Map Styler
Symbolize your vector layers in seconds.
Sentinel 2 Image Downloader
This plugin allows users to download Sentinel-2 images.
MapSafe
Safeguard datasets using masking, encryption and notarisation.
GPX Maker for GARMIN® devices
This plugin exports GPX files for GARMIN® devices.
QGIS Sound Effects
Add sound effects to QGIS to make work less boring.
Mosaic Tool
A plugin to mosaic bands from selected raster layers.
Polaris
QGIS interface for Polaris through Polaris-Studio
ArcGeek Calculator
A comprehensive toolset for coordinate calculations, conversions, spatial operations, watershed analysis, land use analysis, and flood simulation in QGIS.
Auxiliary Labeldata Importer
Helps you to import Labeldata, stored in an auxiliary Layer from another Project.
Sections
Creates a section polygon layer from a point layer.
Slownik warstw
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.

Learn More

3.3.9 - Darién

What's Changed

  • Fix handling of auto-generated FIDs in feature forms
  • Fix current_parent_* expression values for (embedded) feature model
  • Improve robustness of file path handling

Full Changelog: v3.3.8...v3.3.9

Learn More

(Fr) En direct des Journées Utilisateurs QGIS-fr !

Sorry, this entry is only available in French.

Learn More

3.3.8 - Darién

What's Changed

  • Fix Value relation editor widget not auto-completing on second feature
  • Fix settings' panel tabs not translatable
  • Fix untranslatable map canvas menu item and install/upgrade message
  • Fix value relation handling of group name display when multi-selection is enabled
  • Make the About QField data directory location a clickable hyperlink when relevant

Full Changelog: v3.3.7...v3.3.8

Learn More

Happy 41st birthday, GRASS GIS!

Today, we celebrate a true geospatial legend: GRASS GIS!

The post Happy 41st birthday, GRASS GIS! appeared first on Markus Neteler Consulting.

Learn More

Introducing the new QGIS.org website

We have a new website!

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.

Questions to be quickly answered by qgis.org
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 analysis
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:

  1. These platforms often use such resources to track users as they move around the Internet, which we want to avoid as much as possible.
  2. 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:

  1. The application itself,
  2. the user manual and
  3. 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.

Thanks for reading. Go spatial without compromise 🚀🗺

Cheers, Tim, Marco and Anita

Learn More

Adding external WMS to the QGIS Cloud Web Map

The use of WMS/WMTS layers in a QGIS Cloud map project can significantly degrade the performance of the map display. I have already discussed how to counter this problem in an earlier post. One of the solutions is to load external WMS as background layers. The problem with this approach, however, is that only one WMS background layer can be loaded at a time. If further WMS layers are to be loaded into the map at the same time, this approach cannot be used.
Learn More

3.3.7 - Darién

What's Changed

  • Improve legend's parent/children visual representation
  • Insure that exif tags from photo being sketched are transferred onto the resulting drawing
  • Fix regression with addition of relationship children against geopackages with FOREIGN KEY constraints
  • Fix missing elevation profile chart labels

Full Changelog: v3.3.6...v3.3.7

Learn More