Module 20: Data Quality, Ethics & Careers

20.4 Open Source vs Proprietary GIS

Navigating the QGIS vs ArcGIS question — and the modern browser-based alternatives.

Lesson 98 of 100·12 min read

Key takeaways

Open-source GIS (QGIS, PostGIS, GDAL) matches or exceeds proprietary for most tasks.

Commercial tools offer integration, support, and specific vertical features.

Modern browser-based tools (Atlas) are changing what "desktop GIS" means.

Introduction

"Should we use QGIS or ArcGIS?" is one of the most common questions in GIS teams. The honest answer: it depends. This lesson lays out the trade-offs and practical guidance.

Open-source GIS

QGIS

Full-featured desktop GIS. Features:

All common data formats.
~1000 processing algorithms (native + GRASS + SAGA).
Layouts, printing, reports.
Scriptable in Python.
Plugin ecosystem.

Downsides: polish varies; some niche features lag commercial; community support is excellent but inconsistent.

PostGIS

The gold-standard spatial database. Open-source, extends PostgreSQL with geometry types and spatial SQL.

GDAL / OGR

Underlies essentially every other GIS tool. Command-line plus Python bindings.

GRASS GIS

Older open-source GIS with deep raster / hydrology capabilities. Integrates with QGIS.

Python stack

GeoPandas, Rasterio, Xarray, PySAL, Shapely — as covered in Module 18.

Commercial GIS

ArcGIS Pro / Online

Esri's flagship. Deep enterprise integration (ArcGIS Online, server, mobile). Strengths:

Integrated data management across desktop, server, cloud.
Specialist extensions (3D Analyst, Spatial Analyst, Network Analyst).
Commercial support, training, certifications.
Dominant in US government and many enterprise environments.

Weaknesses: licence costs, vendor lock-in, Windows-centric (Pro is Windows-only).

FME

Data transformation (ETL). Unbeatable for obscure format conversion.

Global Mapper

Lightweight desktop GIS; good value for individual licences.

Carto, Mapbox, Google Maps Platform

Commercial web mapping platforms with managed infrastructure.

Atlas

Modern browser-based GIS with collaboration features and AI assistants. It is strongest when the work needs to move from "I analysed this locally" to "other people can inspect, comment on, and use this map in the browser."

Decision factors

Cost

Open-source has no licence fee. Commercial can be tens of thousands per seat per year. For individual analysts and small orgs, open-source wins on cost alone.

Skills

ArcGIS dominates education in the US; many junior analysts know ArcGIS, fewer know QGIS. Training investment is real.

Ecosystem

Some industries (US federal government, utilities) have deep ArcGIS integration. Switching costs high.

Features

For most day-to-day tasks, QGIS matches ArcGIS. Specialist features (ModelBuilder, 3D Analyst, some niche extensions) still favour ArcGIS. Open-source often catches up within 2–5 years.

Support

Commercial licences come with support contracts. Open-source relies on community + paid consulting (Boundless, MapGears, etc.).

Longevity

Open-source projects with active communities (QGIS, PostGIS) won't disappear. Small commercial vendors have gone out of business; your data becomes trapped.

Pragmatic recommendations

Individual / small team / startup: open-source (QGIS + PostGIS + GeoPandas) unless a specific feature demands commercial.
US federal / large enterprise: evaluate ArcGIS integration; mix with open-source for flexibility.
Web mapping: open-source frontend (MapLibre) + PostGIS backend is the modern default.
Teaching: QGIS + Python — skills transfer anywhere.
Research / academia: open-source + Python for reproducibility.

Mixed environments work fine

Most successful GIS teams run both. Use ArcGIS where it excels; use QGIS / Python / PostGIS for the 80 % of routine work. Data interchange via GeoPackage, GeoJSON, or direct PostGIS connections.

Browser-based as the new default

Modern browser-based GIS (Atlas, Felt, ArcGIS Online's new experience) change the equation: no install, collaborative by default, cloud-native data sources. For many workflows these are replacing both desktop tools. Expect this to accelerate.

The pragmatic pattern is mixed: do heavy local or scripted processing in QGIS, PostGIS, or Python; publish the result in Atlas when the next step is review, sharing, lightweight editing, or a simple dashboard. That keeps the analysis reproducible without forcing every collaborator into the same desktop setup.

Self-check exercises

1. Why is "free" not the only reason to choose open source?

Longevity (no vendor shutdown risk), extensibility (add features yourself), transparency (audit algorithms), portability (runs on any OS), community (global user base), and lack of vendor lock-in. The "free" aspect matters most for small orgs and individuals; for enterprises, the other factors often dominate.

2. When would you pick ArcGIS over QGIS for a production workflow?

When your organisation already has deep ArcGIS Online or Enterprise integration, when you need specific extensions (LocateXT for text geocoding, some utility-network tools), when your customers require Esri deliverables, or when your team's skills are strongly tilted toward ArcGIS and retraining isn't practical. For greenfield projects without these constraints, QGIS + Python is usually a better long-term bet.

3. How does a team migrate from ArcGIS to QGIS without disrupting work?

Incrementally. Run both in parallel during transition. Convert data to open formats (GeoPackage, GeoTIFF). Migrate workflows one at a time, starting with least critical. Invest in training. Keep ArcGIS licences during transition for specific tasks that haven't been ported. Typical full migration: 6–18 months for a team of 5–20 analysts.

Summary

Open-source GIS (QGIS, PostGIS, GeoPandas) matches commercial for most tasks.
Commercial (ArcGIS, FME) retains strengths in enterprise integration and specific verticals.
Mixed environments are common and pragmatic.
Browser-based tools are changing the landscape.
Pick based on features, skills, ecosystem, and total cost of ownership.