Page 1 of 3 (51 posts)

  • talks about »
  • uncategorized


Last update:
Tue Dec 1 05:00:10 2015

A Django site.

QGIS Planet

A word of thanks to the hosts of the 14th QGIS Hackfest in Gran Canaria

Last weekend (November 5th – November 8th, 2015) was a special occasion for the QGIS Project – we convened the 14th our ‘hackfest’ meeting!

QGIS hackfests are events where an organiser provides a space for collaboration and members of the community converge and self-organise to improve the QGIS project. We are very much dependent on the good will of our hosts – typically universities – for providing these spaces and the logistics needed to manage the provision of accommodation, food, internet and other needs of our participants over the duration of the hackfest. For this event our gracious hosts were Universitas de Las Palmas de Gran Canaria. Our presence at the University was endorsed and facilitated by:

  •  Rector of ULPGC: José Regidor García
  •  ULPGC Manager: Conrado Domínguez Trujillo
  •  CIO of ULPGC and Director of OSL (“oficina de software libre”, or Free Software Office): Jose Pablo Suárez Rivero.
  •  Councilor of New Technologies Area, Public Administration and Sports at Las Palmas de Gran Canaria Town Hall:  Aridany Romero Vega
  •  Senior professor of computer Science: Agustín Trujillo Pino
The local coordination team was headed up by Pablo Fernández Moniz (CTO and GIS Analyst). Pablo did an amazing job in pulling all the strands together making the event happen! He was assisted by an awesome team of helpers, and participants:
  • Design: Ramsés Cabello Developer (staff at the event): Jaisiel Santana Almedia
  •  Developer (staff at the event): Alejandro Sánchez Medina
  •  Developer (staff at the event): Chano OrtegaTrujillo
  •  Developer (staff at the event): Moises Bonilla

Our heartfelt thanks to all of the people who worked so hard to make this event happen, and to the participants who travelled from far and wide to attend the event. These events are a significant factor in the success of the QGIS project – they allow our developers and contributors to meet face to face and delve deep into technical issues that would be impossible to do under the somewhat disconnected collaboration environment provided by the internet.

Key Activities

There were just under 30 people in attendance at the hackfest – here are just a few of the activities that they were busy with during the hackfest:
  • Qt5 / Python 3 proof of concept by Matthias Kuhn
  • Topological editing with GRASS plugin (Radim Blazek) – video (not from event)
  • Geoserver explorer plugin (Luigi Pirelli)
  • General discussion and planning for the improvement of contribution workflows (pull requests, tickets, QEPs) and infrastructure (Redmine)
  • Improvement of analysis tools (ftools, processing) and their documentation
  • General bug fixes (Jürgen Fischer)
  • Improvements to the website (Richard Duivenvoorde and Anita Graser)
  • Implementation of a GitHub webhook to insert a ‘[FEATURE] issue’ so that documenters know to document new features as they are added to QGIS (Richard Duivenvoorde and Raymond Nijssen)
  • Processing support for loading Oracle data via OGR (Giovanni Manghi)
  • Launched the Italian QGIS User Group, updates to the  documentation of Lizmap web client, managed the Italian translation, the python plugin queue (Paolo Cavallini)

QGIS Sponsorship

Many of the costs not covered by our hosts were covered from central funds including food and travel costs for a number of participants. These funds originate from our donors and sponsorships and are an invaluable resource for the project to allow us to facilitate these events and move the development of QGIS forward. We encourage you to donate to the QGIS or become a sponsor if you would like to foster further innovation and support the long terms goals of the project.

More Information

If you would like further information about what was covered in the event, and to get a feel of the general atmosphere of the event, check out some of these links:

I will update the list above as more reports backs become available.


With thanks from your project chair and the whole QGIS community,


Your donations/sponsorships help to maintain and improve the quality of QGIS

The QGIS project is growing in size, number of contributors/contributions and code complexity. This introduces challenges for the project, especially for maintaining quality. Maintaining and improving quality is one of the main concerns of the QGIS.ORG board and some core developers.

Past and current QA efforts

Tim Sutton introduced a first unit test framework several years ago. But it wasn’t very visible then and passing the tests as a prerequisite to make changes to master wasn’t enforced. About a year ago, Matthias Kuhn introduced automated unit testing for the Linux builds – using Travis continuous integration testing. At our github page you can always see whether the master version builds fine and whether the tests are passing – see the green “Build passing” button at the beginning of the file.

Since then, OS X automated building/testing was added. Pull requests (new contributions from developers) can be tested prior to integration into the master branch. Another effort was to use coverity code scans to detect memory leaks. Nyall Dawson and others did a lot of improvements/fixes due to this automated code scans.

Upcoming challenges

There is still a lot to do regarding quality and automated testing. Because continuous integration tests were only introduced about a year ago, it means that still a lot of areas in the code base remain untested. Also, the current unit tests do not test GUI interactions. There is an ongoing discussion if critical classes should have unit tests enforced for any code changes. Finally, our bug queue at is still quite long, with lots of bigger and minor issues.

Your financial support really matters!

This is where your donations and sponsorships come in. For the past 3-4 releases we were able to pay 2-4 developers who worked for several days concentrating on bug fixing. For QGIS 2.12 we had Nyall Dawson, Jürgen Fischer and Larry Shaffer working on bug fixing. We also financially support Giovanni Manghi for working on our bug tracker (e.g. classifying issues correctly, trying to reproduce the issue, ask bug reporters for more details).

Now – you may wonder why they didn’t fix all the “BLOCKER”s first and then continue on with “HIGH”, “NORMAL” “LOW”  issues – and why a lot of unreported issues and issues with label “LOW” were also fixed? The answer is that it is often more efficient for the developers to concentrate on a certain part of the code – e.g. concentrating on geometry, labeling and editing issues, as Nyall did for this round of bug fixing. This means that he would not only fix issues labeled as “BLOCKER” or “HIGH” but also other bugs that are in the same code. Finally, not all of the “Blocker” and “High” bugs are reproducable or the issue may be much too hard/time consuming to fix.

Due to your financial support, the 3 developers were able to fix the following list of issues for the QGIS 2.12 release – many of the fixes also get back-ported to QGIS 2.8 LTS release:

  • Sweep of all changed dialogs, ensuring tab order is correct
  • UNREPORTED: Only save effect element if it is non-default (decreases size of qgs project files)
  • HIGH: Fix map rotation not considered for ellipse marker data defined rotation (#13367)
  • HIGH: Maintain order of recent expressions (#13461)
  • NORMAL: Make sure recent expression group is always listed last (#13462)
  • NORMAL: [diagrams] Fix initial value of transparency slider not set (#13434)
  • UNREPORTED: Fix potential crashes in renderer widgets
  • NORMAL: Fix legends are empty if presets used with filtered legend (#13300)
  • UNREPORTED: Fix crashes and inconsistent ui when atlas is set to a geometryless layer
  • BLOCKER: Fix diagrams are always shown, regardless of setting (#13501)
  • BLOCKER: Fix fill ring tool used with advanced digitising crashes QGIS (#13355)
  • NORMAL: Fix add ring/fill ring tool works on first polygon (#13069)
  • BLOCKER: Fix missing sip bindings for renderers (#13545)
  • BLOCKER: Fix crash in label property dialog (#13543)
  • NORMAL: Fix hardcoded border for raster legend items (#13540)
  • BLOCKER: Fix symbols drawn multiple times in rule based renderer if symbol (#13220)
  • BLOCKER: Use a model for node editor table, fixed hang when node tool used on large feature (#13541)
  • BLOCKER: Fix node tool duplicates nodes when topological editing and snap are both enabled (#13466)
  • NORMAL: Fix broken data defined SVG marker outline width (#13423)
  • HIGH: Scale svg marker outline width to match context (#11522)
  • HIGH: Allow coloring of svg markers and svg fills when used with graduated/categorised renderers (#11658)
  • HIGH: Fix svg outline widths are incorrectly scaled (#11522)
  • UNREPORTED: Fix snapping options dialog not correctly initialised when loading projects
  • UNREPORTED: Fix uninitialized variables in advanced digitizing dock which meant that sometimes advanced digitising tools would be activated unexpectedly
  • NORMAL: Fix curved labels ignore line orientation placement flag (#5778)
  • UNREPORTED: [console] Move run button earlier in console editor toolbar (prevents it being hidden in overflow menu on small screens)
  • UNREPORTED: Fix fill and outline color for svg markers sometimes enabled even though SVG file does not support parameters
  • UNREPORTED: Fix svg marker colors not correctly restored from project
  • UNREPORTED: If svg files with params do not have a default value set, then don’t reset the fill/border color and border width when changing svg marker/svg fill SVG files (made the behaviour consistent between the svg marker and the other marker symbols)
  • NORMAL: Fix svg symbols are shown in white and hard to see in svg picker (#10908)
  • NORMAL: Fix refining rule based renderer using expression (#10815)
  • UNREPORTED: Fix crash when changing symbol types on windows
  • BLOCKER: Fix split parts tool only leaves one of the newly created parts (#13421)
  • BLOCKER: Fix using add part tool to add part to geometryless rows (#12885, #11319)
  • UNREPORTED: Fix some potential crashes with edit tools and null geometry
  • UNREPORTED (thought I’d submitted this years ago but can’t find the issue now): Allow adding features with empty geometry via attribute table
  • HIGH: Allow delete part tool to remove geometry from single type point and line layers (#13258)
  • LOW: Fix overview canvas background color not set (#11157)
  • Add some unit tests for QgsWKBTypes
  • NORMAL: When adding ring to a geometry, add z or m dimensions to the ring geometry if required (#7400, #7401)
  • NORMAL: Also show features with modified geometry when “show edited and new features” filter is active in attribute dialog (#11684)
  • BLOCKER: Fix broken apply button in label config dialog (#13543)
  • BLOCKER: Fix area calculation when OTF active and no ellipsoid, add unit test (#13601)
  • UNREPORTED: Fix exporting geometry collections to WKT would result in invalid WKT
  • UNREPORTED: Fix unable to import WKT using MultiPoint(1 1,2 2,…) format
  • UNREPORTED: Fix GeometryCollection WKT to support collections with multi* children and GeometryCollection children (allowed by spec)
  • Add a bunch of unit tests to geometry
    – UNREPORTED: Fix calculation of area and length of mixed geometry collections
  • UNREPORTED: Fix geometry casting in python bindings (missing MultiLineString and GeometryCollection casts)
  • UNREPORTED: Fix calculation of length/perimeter for geometry collections
  • UNREPORTED: when creating geometry from WKT, upgrade dimensionality of geometry if coordinates are 3/4 dimensional
  • UNREPORTED: match dimensionality of collections to child dimensionality
  • UNREPORTED: fix area of curves was non-zero if curve is closed
  • UNREPORTED: don’t consider m values when testing for curve closedness
  • NORMAL: Fix merge attributes tool sets skipped attributes to null (#13231)
  • NORMAL: Add skip all option to merge attributes dialog (#6958)
  • UNREPORTED: Fix QgsStatisticalSummary sometimes returning 0 for StDevSample stat
  • UNREPORTED: Fix storing string representations of doubles in an int field results in NULL rather than converting value to int
  • NORMAL: Fix merge attributes/features tool resets values to null for int fields and add a warning if merged attribute value is not compatible with field type (#12842)
  • Fix a LOT of leaks relating to geometry and GEOS operations, labeling
  • UNREPORTED: [pal] Fix regression in placement for free/horizontal polygon labels
  • Add tooltips to advanced digitizing dock
  • Fix a crash in filtered legends
  • Reviewed and merged several bug fix PRs
  • #13433: Help text for rpad and lpad in field calculator are mixed up
  • #13417: missing
  • #13420: Strange behaviour of newly ‘saved as’ project
  • #13463: Identify Results panel always show newly created features in the list
  • #13538: PostGIS tables containing MultiPolygonZ crash QGIS master
  • #13546: qgis trying to update first empty text row with null in db
  • #13027: Join by location does not work when layers have equivalent field names
  • #13032: Save as… fails to populate fields if layer has similar names only different by case
  • #13052: Problem with reshape
  • #10747: Cannot copy/paste points features
  • #13506: Processing help files for QGIS algs all dead now
  • #13274: API combine method for geometry
  • #11755: Real precision (Shapefile)
  • #9208: QGIS crashes when using addAttributes on any vector data provider
  • #13579: Crash Dump 2.11 with user defined expressions
  • #10515: QGIS Crash when trying to load a point layer to georss file
  • #11276: Setting radius units to meters produces incorrect results
  • #13641: editing a feature in a PostGIS layer does not work when the PK contains NULLs
  • #13631: when ELSE rule exists in Styling, all Labels are rendered regardless of styling groups being active/inactive
  • #13638: Cannot load emptry Postgis views
  • #8255: in edit mode changing primary key discards geometry modifications
  • #13594: DB Manager – unable to add a Postgres/PostGIS raster as layer
  • #13446: MYSQL Project File
  • #13310: nightly build packages failing to install with grass error
  • (PR#2378: Allow postgis layers from queries to have multiple column primary keys)
  • (PR#2376: the test for uniqueness now also works for multiple columns by SebDieBln)
  • (#13645: ftools “line intersection” crashes qgis)
  • (#13646: Merge shapefiles from fTools crashes QGIS)
  • transifex updates & german translation
  • attribute editing: don’t allow editing without ChangeAttributeValues capability
  • vector layer: avoid some crashs when methods are called on invalid layers
  • oracle provider: fix call of sdo_filter to verify a spatial index is present
  • #13641: postgres provider: verify unique constraint if NOT NULL is not set on key columns (shortly after release)
  • Commit 6a4544f fix fetching of redirected wms capabilities (followup e95bf6d)

Open Source, why?


During my professional and personal life, I have worked with much different software, with all kinds of licenses. Most of them would be proprietary, closed and / or commercial code. So why devote my time and learning “exclusively” to Open Source?

Without going into detail about the differences between open source software and free software, there are several reasons why FOSS (Free and Open Source Software) interest me.

The first is obviously freedom. Be free to use the software in any context and for any purpose, without being limited by the costs of software acquisition and / or the rules and conditions imposed by the manufacturer (as many said free (as beer) software do). That allows me to, for example, familiarize myself with its features without having to use piracy, or, as a freelancer worker, develop my work based on my technical capacities rather than my financial ones.

Second, the community and collaborative factor. The fact that open source software is built by user and for users, where the main goal is to enhance the software functionality (and not just raise the number of sales), and wherein each enhancement introduced by an individual or company is subsequently shared for the benefit of the whole community, avoiding duplication and “reinventing the wheel”. This is done in part through a lot of volunteer work and constant sharing of knowledge, either by the programmers or users. Thus, together, we all evolve at the same time as the software itself. In addition, everyone can contribute in some way, by producing code, writing and preparing supporting documentation, translating them into other languages or just by reporting bugs.

Finally, the “costs“. The adoption of open source software in enterprises (including the public ones), allow them to focus their investments in training of the human resources and the possible (and desirable) sponsoring of new features that are essential for their workflow, usually for a small portion of the values to spend on the acquisition of commercial software (that usually “forces” the purchase of features that may never be used).

Introducing the QGIS Board

The QGIS PSC (Project Steering Committee) is in transition to becoming a Board. We are registering the project as a Swiss ‘Verein‘ (Association) which will be known as QGIS.ORG and will function as a not-for-profit company, serving the interests of the QGIS project.  The motivation for the transition to a legal entity is described in QGIS QEP (QGIS Enhancement Proposal) #16. The board will be constituted of the same members of the PSC but will gain the executive responsibilities required of our Verein statutes.

New chair and vice-chair

Our long time project founder, Gary Sherman, has stepped down from his role as project chair. I (Tim Sutton) have been elected by the QGIS PSC as Gary Sherman’s replacement by the incoming Board. In addition Paolo Cavallini has been elected as vice chair. Gary will continue to serve as an active voting member of the Board, and will maintain life-long honorary membership on the board.

A special note of thanks

In a world where proprietary GIS software licenses cost many times more than the annual income of most of its citizens, free access to spatial visualisation and analysis tools through QGIS (and its constituent projects such as GRASS, GEOS and GDAL) is a profoundly disruptive force for good.

QGIS is a available to anyone with a reasonably modern computer. It makes the wise utilisation of the earth’s scarce resources and the ability to take care of its citizen’s civic and humanitarian needs based on sound spatial decision-making, that much more possible for a huge swathe of society which would otherwise have been disenfranchised.

Even in developed societies where finance is not necessarily the limiting factor, we cannot underestimate the impact of a software platform that is a freely extensible and shared body of knowledge. QGIS is a platform that enhances the ability of governments and private organisations to deliver services that deeply enrich the lives of their citizens and customers.

Gary’s selfless contribution of the QGIS source code has thus had a far reaching affect on many people’s lives – including my own. Under Gary’s stewardship, the project has evolved from a very basic simple GIS data browser that ran on one platform and could only work with PostGIS data, to a fully-fledged production-ready GIS that can be used on the desktop, in your own custom applications and to serve web maps and services.

Gary has been and will remain an inspirational figure to all of us in the QGIS project – the project he started 13 years ago in 2002. We look forward to his continued involvement on the Board.

Going forward

Our goal as the QGIS.ORG Board is to continue the work started by Gary and to position QGIS as the de facto desktop GIS application, capable of providing a wide range of functionality and richness of features, so that it is no longer necessary to use proprietary GIS software to understand and manage our world.

We are looking for funders for the QGIS.ORG non-profit company. As a foundation project to many humanitarian, municipal, government, NGO, conservation and industry related FOSS tools, we would like to secure funding for the core QGIS project to hire full-time staff so that we can improve the quality and functionality of QGIS for all our users.

To date we have subsisted mainly on micro donations and small-scale sponsorships for which we are very grateful (keep them coming!). This has been very useful but has never take us to the point where we can employ staff full-time to work solely for the good of the project. We would like to establish a team of full-time developers, documentation writers etc.….so we have quite a mountain to climb!

Over the coming months we will be actively seeking out new sources of funding to support these goals, whilst never losing sight of our core principles of Open Governance, Open Source and Open Community. We hope you will join us and support us in this exciting new chapter of the QGIS project!

Your Board

  • Tim Sutton (Chair)
  • Paolo Cavallini (vice-Chair)
  • Andreas Neumann (Treasurer)
  • Gary Sherman (life time honorary member)
  • Anita Graser
  • Otto Dassau
  • Richard Duivenvoorde
  • Marco Hugentobler
  • Jürgen Fischer


Tim Sutton
Incoming QGIS Board Chair

QGIS Crowdfunding project: 2.5D Rendering of buildings/polygons

QGIS already supports various different renderers, such as
categorized, rule-based, point-displacement, 25d_renderingheatmap, etc. This allows for advanced cartographic representations. In addition, there are plugins available, such as “qgis2threejs” or “QGIS Globe”, which allow to view and export QGIS data in the third dimension. While these plugins are very useful, they also have limitations: they are not fully integrated with the QGIS styling mechanisms and can’t be integrated in the QGIS print composer for  high-quality printing.

This crowd funding project aims to extend QGIS renderers with oblique views. The third dimension of the polygon is controlled by an attribute or expression and global angles. The representations can be combined with other QGIS styling options, such as symbol levels, layer effects, categories and rules. Applications are rendering buildings according to their actual heights (similar to Google maps 2.5d rendering) or thematic maps where the polygons are extruded according to an attribute to be represented.

This project is primarily financed by ADUGA and the regional council of Picardy in France. However, of the 20k Euros, 5k are still missing, to fully implement the project.

Thank you for helping us out by contributing to this crowd funding campaign over at OpenGIS.

Announcing the release of QGIS 2.12

This week we have more great news from Jürgen Fischer, our release manager:

“QGIS is a user friendly Open Source Geographic Information System that runs on Linux, Unix, Mac OSX, and Windows.

We are very pleased to announce the release of QGIS 2.12 ‘Lyon’. Lyon was the host city to our developer meet up in April 2012.

Latest Release

This is another regular release following our four monthly schedule.  It again brings many nice new features to QGIS.

Please also note that we’re constantly keeping our long term release QGIS 2.8 ‘Wien’ in good shape to better suit more conservative production setups.

New Features in QGIS 2.12 ‘Lyon’

QGIS 2.12 includes many great new features, tweaks and enhancements to make the
most popular Free desktop GIS even more feature filled and useful.  Visit the visual changelog that highlights some of the new additions.

Whenever new features are added to software they introduce the possibility of new bugs – if you encounter any problems with this release, please file a ticket on the QGIS Bug Tracker (

The source code and binaries for Windows, Debian and Ubuntu are already available via the large download link on our home page:  More packages will follow as soon as the package maintainers finish their work. Please revisit the page if your platform is not available yet.”


Dica para ajustar posição de símbolos em QGIS | Hack to adjust map symbols location in QGIS

De quando em vez aparecem-me zonas com demasiado símbolos no mesmo local, e pensei como seria fantástico se os pudesse arrastar para um local mais conveniente sem ter de alterar as suas geometrias, tal como é possível fazer com as etiquetas. Esse pensamento deu-me a ideia base para a dica que vou demonstrar.

Now and then I get too many map symbols (points) in the same place, and I thought how nice it would be if we could drag n’ drop them around without messing with their geometries position, just like we do with labels. That thought gave me an idea for a cool hack.

Escolha a sua camada de pontos e comece por criar dois novos campos chamados symbX e symbY (Tipo: Decimal; Tamanho: 20; precisão: 5). No separador “Estilo” das propriedades da camada, defina para cada nível do seu símbolo o seguinte: Escolher “unidade do mapa” como a unidade para as opções de afastamento; Usar a seguinte expressão na opção afastamento das propriedades definidas por dados.

Choose your point layer and start by creating two new fields called symbX and symbY (Type: Decimal number; Size: 20; Precision: 5). Now go the layer properties and in the Style tab edit your symbol. For each level of your symbol select “map units” as the offset units, and set the following expression in the offset data define properties option:

    tostring($x - symbX) + ',' + tostring($y - symbY)

Screenshot from 2015-02-22 18:18:43

Tenha atenção que, se as coordenadas do seu mapa tiver valores negativos, será necessário uma pequena alteração ao código. E. g., se tiver valores negativos em X deverá usar-se  antes a expressão “tostring(symbX -$x)”.

Beware that if your coordinates have negative values you need to adapt the code. E.g., If you have negative values in X you should use “tostring(symbX -$x)” instead.

De forma temporária coloque etiquetas na sua camada usando um texto pequeno (eu usei o ‘+’ (sinal de mais) centrado e com um buffer branco) e defina as coordenadas X e Y dos propriedades definidadas por dados usando os campos symbX e symbY,

Now, temporarly  label your layer with a small convenient text (I used a centered ‘+’ (plus sign) with a white buffer) and set its coordinates to data defined using the symbX and symbY Fields.

Screenshot from 2015-02-22 22:42:07

A partir desse momento, quando usar a ferramenta de mover etiquetas, não só alterará a posição da etiqueta, mas também a do próprio símbolo! Fantástico, não?

From this point on, when you use the move label tool, not only the label position change but also the actual symbol! Pretty cool, isn’t it?


Note que as geometria dos elementos não são alteradas durante o processo. Para além disso, lembre-se que neste caso também poderá adicionar linhas de guia para ligar os símbolos à posição original do ponto.

Notice that the features geometries are not changed during the process. Also, remember that in this case you can also add leading lines to connect the symbols to the original position of the points.

Calcular coordenadas do centroide de polígonos | Calculate polygon centroid’s coordinates

Tive necessidade de, numa camada de polígonos, adicionar colunas à tabela de atributos com as coordenadas dos centroides das geometria. Cheguei às seguintes expressões para calcular as coordenadas X e Y, respectivamente:

I had the need to add columns with the coordinates of polygons centroids. I came up with the following expressions to calculate X e Y, respectively:


A expressão parece bastante banal, mas ainda demorei a perceber que, não existindo funções x(geometry) e y(geometry), podia usar as funções xmin() e ymin() para obter as coordenadas dos centroides dos polígonos. Uma vez que esta não foi a primeira vez que precisei de usar estas expressões, fica agora o registo para não me voltar a esquecer.

The expression seems quite simple, but it toke me some time before I realize that, not having a x(geometry) and y(geometry) functions, I could use the xmin() and ymin() to get the coordinates of the polygons centroids. Since this wasn’t the first time I had to use this expressions, this post will work as a reminder for the future.

Take the QGIS User Survey – in Romanian!

Thanks to community member Sorin Călinică, there is now a Romania version of the QGIS User Survey available. We look forward to seeing your responses!

Take the QGIS user survey – in Ukranian!

Thanks to QGIS Community member Alexander Bruy, our Ukranian users can now also participate in the QGIS User Survey in their native language!

Take the QGIS User Survey – in Spanish!

Another great community contribution – you can now participate in the QGIS user survey if you are a Spanish speaker! Thanks to Luigi Pirelli and Victor Olaya for contributing this.

Take the QGIS User Survey – in French!

Another wonderful contribution from the QGIS community, the 2015 QGIS User survey is now available in French! Thanks for René-Luc Dhont for contributing the French translations.

Take the QGIS User Survey in Portuguese!

Thanks to our awesome community, the QGIS User survey is now available in Portuguese! We are looking forward to hearing how the Portuguese speaking community is using QGIS!

Take the QGIS user survey!

Call for applications: QGIS Manual Update and Improvement

Dear QGIS community,

In the last few years we have been steadily improving the amount of funding we are able to accumulate in the QGIS project. Our goal in obtaining funding is always to ‘make QGIS better’. Up until now we have focussed funding on high profile aspects of the project: Funding regular hackfests, paying for bug fixing work prior to releases, funding infrastructure such as servers, domain name registrations etc.

With improved funding levels we now have the opportunity to also start addressing some of the many less obvious components of QGIS that badly need attention, but often don’t attract volunteers. In our PSC meetings it was agreed that we would start this initiative by funding one or more experienced users to improve the QGIS manual. Here, briefly, is the vision:

As an experienced QGIS user you currently have two main resources: The QGIS manual and the QGIS training manual. In this call we focus on the manual, which is already an excellent resource on available functionality in QGIS.

  • The challenge is to keep it synchronised with all new features, and examples and figures often run the risk of being out of date. This is the case already for several chapters of the manual for the latest QGIS releases and we want to start optimizing this.

    We would love to see the QGIS manual providing a readable narrative explaining the purpose (with images and illustrations if needed) of each feature. It can also provide short sample snippet where useful, which in many cases you can simply cut and paste into your code and then tweak to get started.

    For this funded effort we are thus seeking one or more individuals to lay the foundation for this work:

    * verify and improve the norms and guidelines of the documentation and
    especially its update process together with the PSC.
    * update the manual to include all features that are available within the latest QGIS release (2.12).
    * update figures, if necessary according to the defined guidelines (size, desktop-environment, resolution,…).
    * populate the manual with further short examples and improved descriptions, without competing with the training manual.
    * do these in a nice clear and concise writing style, taking inspiration from other software manuals, if available.

    If you think this is something you are able to do, please contact the QGIS PSC using this form and let us know!

    Best wishes,

Feature freeze is now in effect for QGIS 2.12

A note from Jürgen Fischer, our release manager, heralds the start of preparations for QGIS 2.12. We depend all users out there to test it and report issues so we can make the best possible release. An edit version of the email to the developer mailing list from Jürgen follows:


I’d like to remind everyone that the 2.11 development cycle ended yesterday at
12:00 UTC. We are now in feature freeze on the road to the 2.12 release on 2015-10-23

Now we (the community) need to prepare QGIS for the release. No new features will be added anymore.

  • Users, if not already begun, should now start
    extensive testing of master and report bugs on the QGIS hub.
  • Developers should move their focus from creating new features to fixing bugs.
  • Translators can can continue their work (we maintain all our translations on transifex now).

The nightly builds of QGIS testing available for Windows (download here), Linux (Debian and Ubuntu) and Mac
OS X (download here) are now effectively snapshots of what’s going to be released.  Except of course
for the bugs that are going to be fixed until release day.  For Windows there will also be weekly release candidates of the standalone installer. Lets keep up working together to make 2.12 another great release.


Registration open for QGIS hackfest in Gran Canaria, November 2015

Dear QGIS developers

Collage Las Palmas de Gran Canaria

We will be holding our 14th hackfest in Gran Canaria over November 5th – November 8th, 2015. You can read more about the plans for this meet up and register your intention to attend on the hackfest wikipage. This is a developer centric hackfest where we invite coders, documenters, testers, graphic artists, translators and anyone else who is interested in improving QGIS for the benefit of all our users. General users of QGIS are of course also welcome to join us, but we will not be holding any specific user-centric workshops or talks like we do at our user conferences.

The QGIS hackfests are an important aspect of the project, playing an key role in facilitating collaboration and planning within the community of developers and contributors who combine their efforts to put out three releases of QGIS each year. We rely on the goodwill and sponsorship of our grateful users and their host organisations to financially sustain the QGIS project. If you are in a position of influence, we ask you to please consider sponsoring QGIS to support this hackfest and other project related activities.

We would like to thank Pablo Fernández Moniz and his co-organisers from Universidad de las Palmas de Gran Canaria for organising the event. If you are able to support his event organisation activities in any way, please contact him at 

We look forward to seeing your all there!

The QGIS Team

Call for applications: QGIS API Documentation Improvement

Dear QGIS DevelopersIn the last few years we have been steadily improving the amount of funding we are able to accumulate in the QGIS project. Our goal in obtaining funding is always to ‘make QGIS better’. Up until now we have focussed funding on high profile aspects of the project: Funding regular hackfests, paying for bug fixing work prior to releases, funding infrastructure such as servers, domain name registrations etc.

With improved funding levels we now have the opportunity to also start addressing some of the many less obvious components of QGIS that badly need attention, but often don’t attract volunteers. In our July 2015 PSC meeting it was agreed that we would start this initiative by funding one or more developers to improve the python documentation in QGIS. Here, briefly, is the vision:

Lets take our inspiration from Qt. As a foundational library for QGIS, I have always loved the fact that Qt4 is so well documented. Take a look at this for example –

The Qt4 documentation provides a readable narrative explaining the purpose (with images and illustrations if needed) of each class. It also provides a code snippet, which in many cases you can simply cut and paste into your code and then tweak to get started.

As a PyQGIS programmer you have two main resources: The QGIS Python cookbook and the QGIS C++ API documentation. The cookbook is an excellent resource, but it is hard to keep it synchronised with the code base – so examples often run the risk of being out of date, or don’t leverage new functionality that makes its way into the code base. The C++ documentation is good in terms of coverage, but it often lacks detail and as a python programmer you may find it a bit off putting since the text is littered with examples using pointers. Also, the C++ documentation isn’t always a one to one match for python users, and doesn’t explain python specific behaviour such as how ownership is passed around with returning objects.

Wouldn’t it be nice if the C++ API documentation also included the content that is in the python cookbook? And wouldn’t it be nice if the C++ documentation became the C++ *and* Python API documentation – catering for users of both programming languages and providing for a single point of reference and maintenance? Even better the python documentation would live right in the C++ code, so that anytime someone touches the code base they can easily maintain the documentation without needing to jump through a lot of hoops.

For this funded effort we are thus seeking one or more individuals to lay the foundation for this work:

  • establish norms and guidelines for improving the doxygen API docs so that each documented resource can include both python and C++ documentation.
  • port the cookbook content over to the API documentation
  • create doxygen pages to provide a starting point for python programmers to be able to carry out common activities they need
  • populate the API docs with Python examples and improved descriptions
  • do these in a nice clear and concise writing style, again taking inspiration from the fine work that Qt has done
  • perhaps do something really smart to generate docs from the SIP API and incorporate it into our doxygen doctree?

If you think this is something you are able to do, please contact the QGIS PSC using this form and let us know!

Click here to apply here if you are interested in this work

Point release QGIS 2.8.3 ‘Wien’ is ready!

We are very pleased to announce the point release of QGIS 2.8.3 ‘Wien’. Wien is German for ‘Vienna’ – host city to our developer meet up in November 2009 and again in March 2014.

As point release it contains no new features, but 150 changes to fix bugs (see…final-2_8_3 for a full list).

Even when only fixes are added to software they introduce the possibility of new bugs – if you encounter any problems with this release, please file a ticket on the QGIS Bug Tracker ( Please consult the existing and closed issues there before filing any new ones.

The source code and binaries for Windows, Debian and Ubuntu are already available via the large download link on our home page ( More packages will follow as soon as the package maintainers finish their work. Please revisit the page if your platform is not available yet.


We would like to thank the developers, documenters, testers and all the many folks out there who volunteer their time and effort (or fund people to do so).

From the QGIS community we hope you enjoy this release! If you wish to donate time, money or otherwise get involved in making QGIS more awesome, please wander along to and lend a hand!

Finally we would like to thank our official sponsors for the invaluable financial support they provide to this project:

Gold Sponsor:
Asia Air Survey, Japan (

Silver Sponsors:
Sourcepole AG, Switzerland (
Office of Public Works, Ireland, Ireland (
AGH University of Science and Technology, Poland (
State of Vorarlberg, Austria (

Bronze Sponsors:
Nicholas Pearson Associates, UK (
QGIS Poland, Poland (, Italy (>, Australia (
Gaia3D, Inc., South Korea (
Royal Borough of Windsor and Maidenhead, UK (
Chartwell Consultants Ltd., Canada (
Trage Wegen vzw, Belgium (
GFI – Gesellschaft für Informationstechnologie mbH, Germany (
GKG Kassel,(Dr.-Ing. Claas Leiner), Germany (
GIS-Support, Poland (
ADLARES GmbH, Germany (, Italy (, Germany (
Customer Analytics, USA (
Avioportolano Italia, Italy (
Faculty of Geology, Geophysics and Environmental Protection,
AGH University of Science and Technology, Poland (
Urbsol, Australia (
MappingGIS, Spain (>)
GIS3W, Italy (
Lutra Consulting, UK (

A current list of donors who have made financial contributions large and small to the project can be seen on our donors list (

If you would like to become and official project sponsor, please visit our sponsorship page for details. Sponsoring QGIS helps us to fund our six monthly developer meetings, maintain project infrastructure and fund bug fixing efforts (

QGIS is Free software and you are under no obligation to pay anything to use it – in fact we want to encourage people far and wide to use it regardless of what your financial or social status is – we believe empowering people with spatial decision making tools will result in a better society for all of humanity.

Sponsoring QGIS helps us to fund our six monthly developer meetings, maintain project infrastructure and fund bug fixing efforts.

Happy QGISing!


The QGIS Team!

  • Page 1 of 3 ( 51 posts )
  • >>
  • uncategorized

Back to Top