IDF is the data format used by Austrian authorities to publish the official open government street graph. It’s basically a text file describing network nodes, links, and permissions for different modes of transport.
Since, to my knowledge, there hasn’t been any open source IDF parser available so far, I’ve started to write my own using PyQGIS. You can find the script which is meant to be run in the QGIS Python console in my Github QGIS-resources repo.
I haven’t implemented all details yet but it successfully parses nodes and links from the two example IDF files that have been published so far as can be seen in the following screenshot which shows the Klagenfurt example data:
If you are interested in advancing this project, just get in touch here or on Github.
If you follow my blog, you’ve most certainly seen the post How to create illuminated contours, Tanaka-style from earlier this year. As Victor Olaya noted correctly in the comments, the workflow to create this effect lends itself perfectly to being automated with a Processing model.
The model needs only two inputs: the digital elevation model raster and the interval at which we want the contours to be created:
The model steps are straightforward: the contours are generated and split into short segments before the segment orientation is computed using the following code in the Advanced Python Field Calculator:
p1 = $geom.asPolyline()
p2 = $geom.asPolyline()[-1]
a = p1.azimuth(p2)
if a < 0:
a += 360
value = a
You can find the finished model on Github. Happy QGISing!
It’s my pleasure to report back from this year’s AGIT and GI_Forum conference (German and English speaking respectively). It was great to meet the gathered GIS crowd! If you missed it, don’t despair: I’ve compiled a personal summary on Storify, and papers (German, English) and posters are available online. Here’s a pick of my favorite posters:
I also had the pleasure to be involved in multiple presentations this year:
QGIS at the OSGeo Day
As part of the OSGeo Day, I had the chance to present the latest and greatest QGIS features for map design in front of a full house:
Routing with OSM
On a slightly different note, my colleague Markus Straub and I presented an introduction to routing with OpenStreetMap covering which kind of routing-related information is available in OSM as well as a selection of different tools to perform routing on OSM.
Solving the “unnamed link” problem
In this talk, I presented approaches to solving issues with route descriptions that contain unnamed pedestrian or cycle paths.
Here you can find the full open access paper: Graser, A., & Straub, M. (2015). Improving Navigation: Automated Name Extraction for Separately Mapped Pedestrian and Cycle Links. GI_Forum ‒ Journal for Geographic Information Science, 1-2015, 546-556, doi:10.1553/giscience2015s546.
Inferring road popularity from GPS trajectories
In this talk, my colleague Markus Straub presented our new approach to computing how popular a certain road is. The resulting popularity value can be used for planning as well as routing.
Here you can find the full open access paper: Straub, M., & Graser, A. (2015). Learning from Experts: Inferring Road Popularity from GPS Trajectories. GI_Forum ‒ Journal for Geographic Information Science, 1-2015, 41-50, doi:10.1553/giscience2015s41.
If you are following QGIS on Twitter you’ve probably noticed the increasing number of tweets by journalists using QGIS.
For example this map in the Financial Times by Hannah Dormido
or this one with overview maps and three different levels of details
or this map with semi-transparent label backgrounds and nice flag images
or even Time Manager animations by raoulranoa in the Los Angeles Times
I think this is a great development and a sign of how wide-spread QGIS usage is today.
If you know of any other examples or if you are a journalist using QGIS yourself, I’d love to see more!
Do you like the QGIS heatmap functionality? Did you know that QGIS can also create animated heatmaps?
The following video tutorial shows all necessary steps. To reproduce it, you can get the sample data from my Time Manager workshop at #QGIS2015.
With the release of 2.10 right around the corner, it’s time to have a look at the new features this version of QGIS will bring. One area which has received a lot of development attention is layer styling. In particular, I want to point out the following new features:
1. Graduated symbol size
The graduated renderer has been expanded. Formerly, only color-graduated symbols could be created automatically. Now, it is possible to choose between color and size-graduated styles:
2. Symbol size assistant
On a similar note, I’m sure you’ll enjoy the size assistant for data-defined size:
What’s particularly great about this feature is that it also creates a proper legend for the data-defined sizes:
3. Interactive class exploration and definition
Another great addition to the graduated renderer dialog is the histogram tab which visualizes the distribution of values as well as the defined class borders. Additionally, the user can interactively change the classes by moving the class borders:
4. Live layer effects
Since Nyall’s crowd funding initiative for live layer effects was a resounding success, it is now possible to create amazing effects for your vector styles such as shadows, glow, and blur effects:
I’m very much looking forward to seeing all the new map designs this enables on the QGIS map Flickr group.
Thanks to everyone who was involved in developing and funding these new features!
If you follow the QGIS developer mailing list, you’ve probably seen threads about the next major release: 3.0. The topic has been one of the many points we talked about at the latest QGIS developer meeting and Tim Sutton sums up the discussed plan in a post published today:
One hot topic was ‘when will QGIS 3.0 be released’. The short answer to that question is that ‘we don’t know’ – Jürgen Fischer and Matthias Kuhn are still investigating our options and once they have had enough time to understand the implications of upgrading to Qt5, Python 3 etc. they will make some recommendations. I can tell you that we agreed to announce clearly and long in advance (e.g. 1 year) the roadmap to moving to QGIS 3.0 so that plugin builders and others who are using QGIS libraries for building third party apps will have enough time to be ready for the transition. At the moment it is still uncertain if there even is a pressing need to make the transition, so we are going to hang back and wait for Jürgen & Matthias’ feedback.
The take-away message here is that the QGIS team is aware of the current developments around Python and Qt and will keep the community updated about the further development path well before any move.