Blog

17 October 2017

Auxiliary Storage support in QGIS 3

For those who know how powerful QGIS can be using data defined widgets and expressions almost anywhere in styling and labeling settings, it remains today quite complex to store custom data. For instance, moving a simple label using the label toolbar is not straightforward, that wonderful toolbar remains desperately greyed-out for manual labeling tweaks …unless you do
10 October 2017

Undo Redo stack is back QGIS Transaction groups

Let’s keep on looking at what we did in QGIS.org grant application of early 2017 spring. At Oslandia, we use a lot the transaction groups option of QGIS. It was an experimental feature in QGIS 2.X allowing to open only one common Postgres transaction for all layers sharing the same connection string. When activated, that option will bring
7 October 2017

Refresh your maps FROM postgreSQL !

Continuing our love story with PostgreSQL and QGIS, we asked QGIS.org a grant application during early 2017 spring. The idea was to take benefit of very advanced PostgreSQL features, that probably never were used in a Desktop GIS client before. Today, let’s see what we can do with the PostgreSQL NOTIFY feature! Ever dreamt of being able to
4 October 2017

Oslandia is baking some awesome QGIS 3 new features

QGIS 3.0 is now getting closer and closer, it’s the right moment to write about some major refactor and new features we have been baking at Oslandia. A quick word about the release calendar, you probably felt like QGIS 3 freeze was expected for the end of August, didn’t you? In fact, we have so many
18 September 2017

iTowns 2 : 3D Geospatial information on the web !

Oslandia, French IGN, LIRIS CNRS Research Laboratory and Atol CD announce the release of iTowns 2, the new version of the OpenSource 3D geospatial data visualization framework for the web. Rewritten from scratch, this new major version allows users to benefit from a solid technological basis, and new 3D visualization features. Its capabilities for software
15 September 2017

Pointclouds in PostgreSQL with Foreign Data Wrappers

IGN and Oslandia have been collaborating on a research project named LI3DS. LI3DS stands for “Large Input 3D System”. The project involves acquiring data on the field, such as images and point clouds, and providing tools for storing, processing and analyzing the data. Everything developed as part of the project is opensource, and available on
14 August 2017

OSM data quality assessment: producing map to illustrate data quality

At Oslandia, we like working with Open Source tool projects and handling Open (geospatial) Data. In this article series, we will play with the OpenStreetMap (OSM) map and subsequent data. Here comes the eighth article of this series, dedicated to the OSM data quality evaluation, through production of new maps. 1 Description of OSM element
6 August 2017

OSM user classification: let’s use machine learning!

At Oslandia, we like working with Open Source tool projects and handling Open (geospatial) Data. In this article series, we will play with the OpenStreetMap (OSM) map and subsequent data. Here comes the seventh article of this series, dedicated to user classification using the power of machine learning algorithms. 1 Develop a Principle Component Analysis
31 July 2017

OSM user classification: the unavoidable metadata normalization

At Oslandia, we like working with Open Source tool projects and handling Open (geospatial) Data. In this article series, we will play with the OpenStreetMap (OSM) map and subsequent data. Here comes the sixth article of this series, dedicated to user metadata normalization. 1 Let’s remind the user metadata After the previous blog post, we
24 July 2017

OSM metadata description: the data behind the data

At Oslandia, we like working with Open Source tool projects and handling Open (geospatial) Data. In this article series, we will play with the OpenStreetMap (OSM) map and subsequent data. Here comes the fifth article of this series, dedicated to the extraction of OSM metadata starting from the OSM history data. 1 Extract OSM data