Bill and I have a podcast that we do almost once a month. Podcasts are a lot of fun because you can talk about things easier than writing about them. There is a free flow of ideas (or maybe garbage) out of your head and on to a mp3. One topic we talked about months ago was GIS clients. We talked about tools we use but I just happened to be listening to it last night and I realized maybe I wasn’t as honest with myself as I should have been.

GIS users, if you need a friend, get a dog.

I’m not a GIS user…

Fair point though, what is a GIS user? I think of it as someone who uses GIS software. But even that it is somewhat of a mess because one person’s GIS software is another person’s toolkit. Ignoring that issue for a second, what do I use for GIS?

  2. Turf.js
  3. Elastic
  4. PostGIS

I think that pretty much covers it. I mean there is some Shapely and some other libraries, but that short list is all I use anymore. That of course has a lot to do with my job, if I was GIS Manager at the City of Townsville I might need other tools, but that list above is pretty much it. I can’t help but think of these things as Toolkits rather than GIS software. They are all part of a deeper workflow that I use when I need to use it. The end result is never QGIS, ArcGIS, uDIG or whatever madness you use in your daily life. It is either GeoJSON or “database” (where database could mean a lot of things).

God made men. Men made proprietary software systems

This blog is about to have it’s 15th year anniversary and I can’t think of a better example of how things have changed since that moment. I also think GIS lends itself for this workflow orientated environment anyway. Ignoring the crazy ArcGIS Desktop years with wizard based GIS, mostly GIS has been scripting workflows to accomplish your needs. Fortran, AML, Python, you name it. We use these methods to not only get results but document them. In the end I think all the tools we use for GIS are Toolkits and not software. Yes, one must put a name on something, but GIS has always been about toolkits, even in proprietary workflows, and will always be this. Maybe when we check in right before I retire in 2035 we can see how we are doing with this.

My guess? Still using toolkits.

Toolkits are a “real genius” move…

2 replies on “Toolkits”

“Toolkits” was the underlying successful paradigm of Unix back in the 70s and Linux in more modern times. I got a lot of bang out of that philosophy and built more than one company around it. UI GIS frustrates me in the inability to capture complicated workflows and run them again. It’s not impossible, just harder than it should be. FME is a good middle road for GIS / Toolkits.

Well this is well stated. Yes, it is much harder than it should be to pipe one process into another. We were promised an IFTTT type tool by now 😉

Leave a Reply