Tag: processing

Conefor for Processing

13.07.2023 14:19 ·  GIS  ·  qgis, plugins, processing

At the beginning of the year, I developed a new plugin — Conefor for Processing.

Conefor (previously known as Conefor Sensinode) is a tool to quantify the importance of habitat areas and links for the maintenance of connectivity. It is also used to evaluate the impacts on connectivity of habitat and landscape changes. Conefor is used to conduct a spatial ecology analysis and conservation planning. The Conefor for Processing plugin contains tools to prepare data and perform all types of analysis available in the Conefor.

The new plugin is a great addition to the Circuitscape provider I have developed before. Together, these plugins create a powerful set of tools for spatial ecology and conservation, allowing researchers from different fields to predict the movements of animals, evaluate the impact of climate change on range shifts, analyse the spread of invasive species or disease, understand how landscape patterns affect gene flow, and much more.

Processing providers updated for QGIS 3

17.01.2018 17:43 ·  GIS  ·  qgis, plugins, processing

As QGIS 3.0 has entered the “hard freeze” phase, it is time to update the plugins. I decided to start with Processing providers, as they are the most relevant. As of today, all of them are updated and available for installation from my plugin repository:

WhiteboxTools for Processing

23.12.2017 09:59 ·  GIS  ·  qgis, plugins, processing

Yesterday I published a new plugin — WhiteboxTools Processing provider.

WhiteboxTools provides a set of spatial analysis tools, primarily for raster data. It was developed as a response to numerous requests coming from users of the specialized GIS called Whitebox GAT. People wanted to use Whitebox GAT functionality in automated data processing workflows. At the time of this post, WhiteboxTools already contains more than 250 tools from Whitebox GAT and about the same number will be added in the near future. The WhiteboxTools for Processing plugin I have developed integrates these tools into QGIS.

The plugin is already available from my plugin repository. Only QGIS 3.0 is supported. Currently, the plugin has an experimental status, so do not forget to enable experimental plugins in the QGIS Plugin Manager settings. In addition to the plugin, you should also download and install WhiteboxTools and specify their location in the Processing settings.

fTools is dead

01.03.2016 15:48 ·  GIS  ·  qgis, processing, ftools

If you have been using QGIS for ages, you surely know what the fTools plugin is. For a long time, it was practically the only tool for performing vector geoprocessing operations. With the advent of Processing, the need for fTools significantly decreased because most of the fTools algorithms were also available in Processing. And today, the fTools era is over.

All fTools algorithms that were missing from Processing have been implemented. The fTools plugin has been removed. Processing has been “taught” to create menu entries and bind algorithms to them. This means that the “Vector” menu has not disappeared, and you will find all the tools in their usual places. The only difference is that instead of custom fTools dialogs, you will see automatically generated Processing dialogs.

Hacking Processing

12.11.2014 15:43 ·  GIS  ·  qgis, processing

I’m pretty sure that the heterogeneity of the Processing plugin’s graphical interface is not something that many people (if any) pay attention to. And it is very likely that the code responsible for the generation of the interface has never been seen by anyone other than the developers. Since everything works as expected, everyone is happy with it. And it does not matter what the windows or buttons look like. Let alone the code. In fact, both are important. A unified interface looks professional, is more convenient and pleasant to use, while clean, well-structured code is easier to maintain and extend.

My first thought was to do a crowdfunding campaign like Matthias, but then I changed my mind. So now I am slowly fixing it in my spare time. I’m hoping to get this done in time for the 2.8 release, which will be a long-term supported release.