Desktop GIS - the book
The Pragmatic Programmers have announced the upcoming Desktop GIS title.
The Pragmatic Programmers have announced the upcoming Desktop GIS title.
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…
Well, the QGIS workshop at FOSS4G2007 is history. We had a capacity crowd and covered a lot of ground in a short 3 hours. Rumor is there are some pictures and heaven forbid, audio from the workshop floating around. Maybe they’ll surface at some point this week. I have a few LiveCDs left over and some of the coveted QGIS carabiners. If you run into me at the conference and want either, just ask.
The QGIS Python console is great for doing one-off tasks or experimenting with the API. Sometimes you might want to automate a task using a script, and do it without writing a full blown plugin. Currently QGIS does not have a way to load an arbitrary Python script and run it.[1] Until it does, this post illustrates a way you can create a script and run it from the console.
The raster calculator allows you to perform mathematical operations on each cell in a raster. This can be useful for converting and manipulating your rasters. Operators include: Mathematical (+, -, *, /) Trigonometric (sin, cos, tan, asin, acos, atan) Comparison (<, >, =, <=, >=) Logical (AND, OR) To perform operations on a raster or rasters, they must be loaded in QGIS.
The death of the shapefile has again been predicted—this time for 2010. The technical description of the format has been around for going on 12 years. In that time it has become a sort of lowest common denominator for data exchange. They’re everywhere. Making them go away is going to require a revolution of sorts. ESRI has been sounding the death knell for the shapefile for a while now. I agree that it isn’t a perfect format but it is nearly perfectly supported.
$ uptime 20:20:56 up 434 days, 15:31, 2 users, load average: 2.32, 0.89, 0.53
I guess Ubuntu must be popular. I’m just trying to upgrade my Feisty install so I can do the upgrade to Gutsy. Looks like it’s going to take a while…
In any sufficiently aged bureaucracy, process overshadows product.
I keep seeing more evidence that many people and organizations are migrating to open source GIS on the desktop. In many cases a mix of proprietary and open source GIS is in use. I’m wondering about other’s experiences in this area. To gain some insight, I’ve created a poll (right margin). Please take a second and vote.
This is a project I have had lingering around for a while. It is a geospatial data browser written in Python using the PyQt and QGIS bindings. It allows you to navigate a tree structure and preview raster and vector datasets. Metadata extracted from the data can be viewed as well. It supports drag and drop for any target that accepts filenames (e.g. QGIS). For screenshots and more, see http://geoapt.com/geoapt-data-browser.
One of the challenges in any open source project is accepting contributions from people that don’t have, need, or want access to your centralized source code repository. Managing repository accounts for occasional or one-time contributors can be come a bit of an administrative issue. To date, the QGIS project has accepted one-time or occasional contributions through patches submitted via a help ticket. To make it easier for you to contribute to QGIS, we have created a clone of the Subversion repository on GitHub.
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.
Using Git with Subversion makes adding new features easy. Here are the metrics for my latest QGIS hack: SVN revisions by others while working on my branch: 177 Time to complete merge with latest SVN revision: 1 second Conflicts: None Coincidence? Maybe not.
The application deadline for the Google Summer of Code is nearing (April 9). If you are interested in working on QGIS as part of GSOC and need ideas, please see Quantum GIS Wiki. We are waiting for your proposal!
If you use Vim you probably know you can use the make command to build your project. The make command looks for a Makefile in your current directory. If you are editing a file that is not in the current directory (meaning you use some Vim magic to change to the directory containing your edit buffer), make will start below the top-level of your build directory. This is often the case when doing an out-of-source build with CMake.
At the ESRI Developer Summit there was news of the File Geodatabase (FGDB) API. Based on the tweets from the summit it appears: The API will be C++ only API works on Windows and Unix/Linux (specifically RedHat, Solaris, SuSE) operating systems Rudimentary support only—features such as annotation, relationships, topologies, etc. are lacking Since ESRI is releasing a targeted API and a not a specification, support for Mac OS X is out of the question.
It’s true—everything you have ever done is wrong. If you are a developer, look at the code you wrote five years ago—it’s wrong. If you collect and store data—it’s wrong. This is the nature of human endeavor. The world used to be flat. The earth used to be the center of the universe. Discovery and development is an iterative process. What we do today will likely be replaced tomorrow. Just because we can’t be perfect at the outset doesn’t mean we shouldn’t try.
In a recent post on VerySpatial.com, Jesse was discussing the apparent dominance of U*nix and observed: ‘…the geospatial industry almost completely left behind support for UNIX-like OSes’ It is true that the proprietary GIS vendors have largely abandoned Unix and Unix-like operating systems and continue to do so. However the open source GIS community has embraced all major operating systems with software that runs on Linux, *BSD, Mac OS X, and yes, Windows.
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/