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.

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

There’s been several posts to GIS StackExchange along the lines of: Where’s my .qgis3 folder? Prior to QGIS 3, the .qgis/.qgis2 folder was found under your home directory. At version 3, the folder has moved to a more standard profile location for your operating system. There are a couple of ways to determine where the folder is located: Use the Settings->User Profiles->Open active profile folder menu item Use QgsApplication.qgisSettingsDirPath from Python or the console Here are the “standard” locations for Linux, Mac, and Windows, as found under your HOME directory:

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).

Following up on my last post, Running Scripts in the Python Console, I created a plugin to simplify running scripts: The Script Runner plugin allows you to add your scripts to a list so they are readily available. You can then run them to automate QGIS tasks and have full access to the PyQGIS API. In addition, you can view information about the classes, methods, and functions in your module as well as browse the source:

The QGIS project has a number of support channels. Like many open source projects, these are loosely coupled. Recently the forum was made read-only and this has prompted a number of questions and concerns about how to receive support. This post outlines the ways in which you can get your questions answered. Home Page The QGIS home page has links to all the documentation and community resources. The navigation panel on the left has links to both the Community resources and the manual.

GIS data is like an illicit drug. You can’t control it. It travels in secret and hides in the dark alleys of your organization. Its effect spreads and enslaves those that use it. In the end it can lead to ruin. Well maybe its not that bad but organizing and managing your GIS data is difficult. If you need to maintain canonical datasets, the spread of “temporary” and/or “working” copies is your enemy.

This week we look at a newly arrived plugin named qNote. This plugin allows you to create a note and store it in a QGIS project file. When the project is loaded, the note is restored and can be viewed in the qNote panel. This little plugin provides a way to attach metadata to a project. Things you might want to include in a note are: Content of the project Purpose Area of interest Where the data came from Who created the project This information can be helpful when sharing a project or when you forget what you did six months after the fact.

Writing a QGIS plugin is not overly complicated but represents a bit of work. Using git in conjunction with your development efforts can make sure your investment in coding time is preserved. Development Tools The QGIS project team has set up a central location for plugin development which includes pretty much everything you need to develop and support your plugins, including: Issue tracking Wiki Documents

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…

This week we look at the OpenLayers plugin for QGIS. This plugin allows you to add a number of image services to your map canvas: Google Physical Streets Hybrid Satellite OpenStreetMap Yahoo Street Hybrid Satellite Bing Road Aerial Aerial with labels Installing the Plugin The OpenLayers plugin is installed like all other Python plugins. From the the Plugins menu in QGIS, choose Fetch Python Plugins.

Getting started with Python and QGIS 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 Python Packages Working on the Command Line IDE Example Workflow Creating a New Plugin Working with Existing Plugin Code Troubleshooting

Why would you want to run the Windows version of QGIS on Linux? Because its there. Actually, it may be a useful way to test the Windows version without firing up the dusty old Win32 box. I did this more out of curiosity than anything else. I installed Crossover Linux (http://www.codeweavers.com/products/cxoffice) on an Ubuntu Dapper box. During the install process you are given the option to install Windows software. Of course QGIS isn’t in the list of supported software, but there is an option to install Unsupported Software.

Is desktop GIS software a rusty old car with no wheels? Bouncing around the blogosphere sometimes leaves you with that impression. All the excitement these days seems to center around mashups, hacks, and mapping in your web browser. It’s definitely cool stuff. A number of folks think this is the future of GIS, even when it comes to doing analysis. Part of this trend stems from a desire to deliver mapping to the masses.

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.

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.

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.

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 week we highlight the Points to Paths plugin, a handy way to convert a series of points into line features. This plugin lets you “connect the dots” based on an common attribute and a sequence field. The attribute field determines which points should be grouped together into a line. The sequence field determines the order in which the points will connected. The output from this plugin is a shapefile.

I’ve had to lower my expectations of the Open Source GIS user community. Now that I have your attention, I’ll explain. The OSGIS user community by and large is composed of a great bunch of folks. Its the few that have soured my outlook a bit. I repeatedly see posts to mailing lists blasting one application or the other (usually not to the project’s own list but another). The software stinks, doesn’t work right, the developers are stupid, its not as good as X, Y, or Z, and so forth.