About a week ago, Alessandro Furieri announced the release of SpatiaLite 4.0.0 — a spatial extension to SQLite. There are not just a lot of changes, there are VERY many of them. And some of them may cause compatibility problems, so all users should read the migration guide.
Among the most interesting features:
tessellation support
VirtualOGR driver
support for SQL/MM topology
and more
And yesterday, the SpatiaLite data provider in QGIS was updated. Compatibility with databases created in previous versions of SpatiaLite is maintained. However, you will need to convert your databases to the SpatiaLite 4.0.0 format (you can use spatialite_convert from spatialite-tools) to take full advantage of the new features.
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.
Two of my plugins are in the TOP-20 by downloads, 4 by ratings and 5 by votes. It’s a small thing, but it’s nice.
My plugins
Actually, the list is not complete, as there are still C++ plugins that are distributed as source code and plugins that are not published in the official repository. And some plugins, although they have been significantly reworked by me and are now maintained by me, were originally created by others.
As I wrote before, Oslandia kept their promise, and during the 8th QGIS developer meeting, the Atlas plugin was integrated into the QGIS print composer. This has been made possible thanks to the financial support (although not the full amount has been raised) of the following individuals and organisations:
Agence de l’eau Adour-Garonne
City of Uster, Switzerland
Spencer Gardner
Giovanni Allegri
John C. Tull
Bill Williamson
Ujaval Gandhi
The workflow remains the same: create a print layout and specify a coverage layer that will be used to generate the atlas. In addition, it is now possible to create complex labels using the full power of QgsExpression and the attributes of the coverage layer.
Let’s go through the process of making an atlas step by step.
QGIS plugin developers should note that it was decided at the hackfest to make changes to the plugin metadata. Namely:
added mandatory author field
added mandatory email field
the authorName field is declared deprecated and is ignored when parsing metadata
The new fields must be present in both the __init__.py file and the metadata.txt file. The purpose of this change is to separate the actual author of the plugin from the plugin maintainer. For plugins already uploaded to the repository, these metadata fields will be filled in automatically using information from LDAP, but for all new plugins, these fields should be set by the developer.
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.
SEXTANTE will soon become part of QGIS: the code freeze in the old repository and the migration are scheduled for 20th August. After the migration, only the Java-related part will remain in the old repository, while QGIS will get a new core plugin.
In this context, I have decided to revise the fTools provider code, synchronise it with the original utilities, and generally prepare for migration and code removal in any way possible. I will be happy if someone helps with testing and is willing to publish plugin package with the latest fixes.
