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.
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:
Circuitscape for Processing — analysis of heterogeneous landscapes (for example, to model movement, gene flow of plants and animals, or to identify areas important for connectivity conservation)
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 (or newer) 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.
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.
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.
TauDEM (Terrain Analysis Using Digital Elevation Models) is a set of Digital Elevation Model (DEM) tools for extracting and analysing hydrological information from the topography represented by a DEM. It was developed at Utah State University (USU) for hydrological analysis of digital elevation models and watershed delineation.
TauDEM has recently been integrated into QGIS as a SEXTANTE provider. This makes it possible to run TauDEM tools directly from QGIS, easily perform complex analysis workflows, and view the generated results.
In this post, I will show how to perform some hydrological analysis tasks in QGIS using TauDEM, namely how to delineate watersheds and extract stream networks.
SEXTANTE is a powerful and flexible platform for performing geospatial analysis in QGIS. It provides access to its own geoprocessing functions as well as algorithms implemented in third-party applications, making analysis easier and more productive.
Initially written in Java and only available to gvSIG users, SEXTANTE has gradually extended its presence to other GIS. In 2012, a Python version was developed for use with QGIS. It immediately attracted a lot of interest from users and developers alike, and in September 2012 SEXTANTE was integrated into QGIS as a core plugin.
SEXTANTE in QGIS allows you to use the main features of well-known third-party GIS tools (SAGA GIS, GRASS GIS, TauDEM, OrfeoToolBox…) and algorithms implemented directly in SEXTANTE (fTools, MMQGISX…) via a unified interface.
It also offers a wide range of possibilities for automating data processing: combining repetitive steps of applying algorithms to data in a custom analysis model, writing and using Python scripts, batch processing mode. Advanced users can further increase their productivity by using SEXTANTE algorithms and the Python console together.
Attempts to import SEXTANTE from its SVN repository into the QGIS repository on GitHub with the history intact are a thing of the past. Also in the past were numerous fixes for bugs that appeared after the import, writing build rules, and fixing issues caused by the directory structure change. SEXTANTE is now officially included in QGIS as a core plugin.
Thanks to Victor, Tim, Camilo. Well, and me too :-).
Together with Victor, we have implemented in SEXTANTE the ability to save output to any OGR-compatible format or memory layer and to set the output data encoding. The only thing missing is the ability to set dataset and layer creation options. In the future, we plan to add support for saving results to spatial databases.
In the meantime, we are fixing bugs and making sure that all the algorithms are fully functional. In particular, there are 16 algorithms in fTools that are still untested.
Reviewed 19 fTools tools in two groups: cleaned up the code, fixed some bugs, optimised a bit. There is still as much to do. Then test and if no critical bugs appear, I will commit.