The Geospatial Landscape

Overview

Teaching: 20 min
Exercises: ?? min
Questions
  • TBD

Objectives
  • TBD

Goals / Objectives

After completing this activity, you will:

Standalone Software packages

Most traditional GIS work is carried out in standalone apps that aim to provide end-to-end geospatial solutions. These apps are available under a wide range of licenses, and for commercial software, price points. Some of the most common are listed below.

Commercial software

** a combined graphic with logos from all the above apps would be good here **

FOSS software

The Open Source Geospatial Foundation (OSGEO) supports several actively managed GIS platforms:

** a combined graphic with logos from all the above apps would be good here **

(bonus content - GRASS Promo vid, mid 1980’s, narrated by William Shatner: https://www.youtube.com/watch?v=cZia3ShzTWM)

Online GUI/ Cloud computing

GUI vs CLI

The earliest computer systems operated without a Graphical User Interface (GUI), relying only on the Command-Line Interface (CLI). Since mapping and spatial analysis are strongly visual tasks, GIS applications benefited greatly from the emergence of GUIs and quickly came to rely heavily on them. Most modern GIS applications have very complex GUIs, with all common tools and procedures accessed via buttons and menus.

GUI Pros

GUI Cons

In scientific computing, the lack of reproducibility in point-and-click software has come to be viewed as a critical weakness. As such, scripted CLI-style workflows are again becoming popular, which leads us to another approach to doing GIS: via a programming language.

GIS in programming languages

A number of powerful geospatial processing libraries exist for general-purpose programming languages like Java and C++. However, the learning curve for these languages is steep and the effort required is excessive for users who only need a subset of their functionality.

Higher-level scripting languages like R and Python are easier to learn and use. Both now have their own packages that wrap up those geospatial processing libraries and make them easy to access and use safely. A key example is the Java Topology Suite (JTS), which is implemented in C++ as GEOS. GEOS is in turn accessible in R via the sf package and in Python via shapely. R and Python also have interface packages for GDAL, and for specific GIS apps.

This last point is a huge advantage for GIS-by-programming; these interface packages give you the ability to access functions unique to particular programs, but have your entire workflow recorded in a central document - a document that can be re-run at will. Below are lists of the key spatial packages for R and for Python.

R:

An overview of these and other R spatial packages can be accessed here.

Python:

Further reading on geospatial analysis in Python is available here (PDF, 2.7MB).

R and Python are, as programming languages, CLI tools at their core. However, using these languages together with an IDE (Integrated Development Environment) application allows some GUI features to become part of your workflow. IDEs allow the best of both worlds. They provide a place to visually examine data and other software objects, interact with your file system, and draw plots and maps, but your activities are still command-driven - recordable and reproducible.

There are several IDEs available for R, but RStudio is by far the most well-developed. Python has a wider variety to choose from, with PyDev and PyCharm popular options.

Traditional GIS apps are also moving back towards providing a scripting environment for users, further blurring the CLI/GUI divide. ESRI have adopted Python into their software, and QGIS is both Python and R-friendly.


Key Points

  • TBD