The recent release of QGIS 1.0 provides an excellent opportunity for developers looking to create standalone mapping applications with Python. I recently posted an article on creating a very simple standalone application with Python and QGIS 1.0. Much of the Python efforts thus far have been devoted to creating QGIS plugins. I think now that we have a stable API, you’ll begin to see more custom applications that meet a specialized need.

Looks like the ink is dry on Desktop GIS and it should start shipping soon. You can get the full scoop from the Pragmatic Bookshelf. Update: It’s now shipping. See the announcement.

After a rather long lapse, I had the occasion to write some Java code recently (mainly because it didn’t look like Howard’s PySDE was functional). I didn’t like it. Not to start a language flame war, but after using Python almost exclusively for 6 months, I found Java to be cumbersome. I kept thinking “if it were Python I could do it this way”. Sending an email from Java–frightening. From Python–simple.

This weekend I finished reviewing Pragmatic Version Control Using Git by Travis Swicegood. If you are a git user or interested in learning about the latest in version control for your source code, check it out. The book is available in beta now.

This site aims to bring out some of the latest and sometimes not-so-greatest happenings in the GIS world. We’ll focus to large extent on Open Source software but hopefully mix it up to keep things interesting. We’ll explore things from the new and exciting to the dull and mundane. There are a lot of GIS/Spatial sites out there. Hopefully we can provide some content of interest and you will add this one to those you visit frequently.

QgisToMapServer converts a saved QGIS project file to a map file, ready to be served with MapServer. A binary preview version for both Mac and Windows is available now. For Linux/Unix users, the source code is available from the Git repository. QgisToMapServer is different from the plugin in QGIS. It is a standalone Python application providing the following features: Create MapServer map files from saved QGIS project files Preview the map file (requires shp2img)

The book is now available in beta. Excerpts from two of the chapters are available online. What’s a beta book? Well in this case it’s a lot like software—feature complete and ready for you to give it a spin. The announcement from the Pragmatic Bookshelf: The Pragmatic Bookshelf | Desktop GIS “From Google Maps to iPhone apps, geographic data and visualization is quickly becoming a standard part of life. Desktop GIS shows you how to assemble and use an Open Source GIS toolkit.

Getting started with Python and QGIS 3 can be a bit overwhelming. In this post we give you a quick start to get you up and running and maybe make your PyQGIS life a little easier. There are likely many ways to setup a working PyQGIS development environment—this one works pretty well. Contents Requirements Installing OSGeo4W Setting the Environment pb_tool Working on the Command Line IDE Example Workflow Creating a New Plugin Working with Existing Plugin Code Troubleshooting

Well it was a short summer here. Or perhaps we have defeated global warming. This is the view from the deck on Thursday evening: and this is the view Saturday morning: Of course nearly everyone in the country has removed their snow tires in anticipation of the upcoming May 1 deadline. As they say “Life is tough in the far north”. The good news is that now we can go directly from winter to summer…

Everybody who gets an Eee PC has to write about it–it’s required. I don’t really have much to add to the raft of reviews, except for one small point. I found myself wanting to print something and, based on my last experience, prepared for the ordeal of setting up a printer. I about fell out of the chair when I opened the Printer configuration and found that the Eee had already found the CUPS printer on my network and added it.

Using the git log leading up to the 1.7 release (June 2011) I put together a graphic that shows the growth of committers working on the project. In 2002 we had two people (me alone up until October). You can see significant jumps in developer interest in 2004 and 2008: In 2004 there were a number of releases that added significant functionality Following an announcement at FOSS4G 2007 in Victoria we released 0.

I’ve come to the conclusion that storing rasters in a database is of dubious value, particularly from a data warehouse perspective. If you manage a collection of rasters that are updated on a frequent basis, storing them in a relational database with ArcSDE quickly becomes a pain. I’m not talking about a dozen or so rasters, but rather tens of thousands. The overhead of the database and middleware just doesn’t seem to be worth it.

Matthew Perry poses the question: Why is the command line a dying art?. Funny how these things go–I was thinking about posting on this same topic just the other day, although I may be repeating myself. The efficiencies of the command line cannot be overstated. I too have seen that deer in the headlights look when a GUI-only user is first exposed to a command prompt. I have also seen people spend days on a data conversion project that could easily be accomplished in hours (or less).

In Beyond the RDBMS Sean references Martin’s post which in turn points us to a paper (gotta love the web in action) promoting “The End of an Architectural Era”. This paper advocates the complete rewrite (well trashing actually) of current RDBMS code in favor of specialized “engines”. It’s an interesting read with some good points until I got to this: Our current favorite example of this approach is Ruby-on-Rails. This system is the little language, Ruby, extended with integrated support for database access and manipulation through the “model-view-controller” programming pattern.

The Pragmatic Programmers have announced the upcoming Desktop GIS title.

The forum (http://forum.qgis.org) has been closed for new registrations and marked read-only. Users have been encouraged to use http://gis.stackexchange.com instead. If you have an thoughts on the closure, good, bad, or otherwise, please comment.

I use my MacBook as my “command center”, connecting to the other machines I need to work on using ssh and Nx. After a bit of tuning, I had this working nicely under Tiger. Enter Leopard. I upgraded my machine rather than a clean install — I’m in the middle of too many things to start from zero. Being cautious, I waited a few days to see what kind of issues might arise (such as the Blue Screen of Death).

An interesting visualization of QGIS development over the last eight years: http://woostuff.wordpress.com/2011/01/03/generating-a-gource-source-commit-history-visualization-for-qgis-quantum-gis/

Following the instructions for a “hard” upgrade in Chapter 2. Installation of the PostGIS manual results in large objects not being restored to the database. If you create a dump using pg_dump -Fc –oids and then use the postgis_restore.pl script, the oids will be restored but not the large objects. This is not really a PostGIS issue, it can happen when dealing with any PostgreSQL database. To remedy this situation I found that the pg_dumplo utility has the answer.

We’ve released version 3.1 of the Plugin Builder for QGIS 3.x. This version contains a number of bug fixes and performance enhancements. Here are some of the changes included since version 3.0.3: Fix issue with reload on generated plugins Move dialog creation to run method to improve startup performance Move help file generation files to proper method Include missing tags file Attempt to compile resources.qrc when plugin is generated (requires pyrcc5 in path) Set deployment directory in Makefile based on user OS (pb_tool is recommended over make) Check for valid URL format for tracker and repository Compiling Resource File If you have the resource compiler pyrcc5 in your path, the resource file will be compiled automatically when you generate your new plugin.