Key Takeaways
- Who: This guide is for public sector IT directors, facility managers, and municipal leaders evaluating GIS software options.
- What: It explains what open source GIS software is, its benefits (no licensing fees, customizability, rolling releases), limitations (training, implementation costs), and the 7 categories of open source GIS tools available.
- Benefit: You’ll learn how to convert manual mapping and asset tracking into automated workflows with PSD Citywide’s integrated Enterprise GIS and CMMS platform, which merges open source tools (Geoserver, PostgreSQL/PostGIS, QGIS, QField) with extensive support and training to eliminate excessive licensing costs.
Free and open source software (FOSS) is increasingly being adopted by public sector organizations worldwide. The Canadian government’s Directive on Service and Digital (effective April 1, 2020) mandates that “where possible, use open standards and open source software first” and that “all source code must be released under an appropriate open source software license.” At the provincial level, British Columbia has long championed open data and open source through its Ministry of Citizens’ Services Guidelines on the Use of Open Source Software. At the municipal level, PSD Citywide’s Geospatial Maturity Index found that in 2019, just over 20% of respondents used open source GIS software; a number likely growing as open source GIS gains popularity.
As governments become progressively open and budgets become increasingly constrained, the time is ripe to consider open source software as a viable alternative to Commercial Off-The-Shelf (COTS) solutions. This guide gives public sector organizations the background information needed to make informed decisions about open source GIS software.
See PSD Citywide’s Enterprise GIS Solution →
What Is Open Source GIS Software for Public Sector Agencies?
Fundamentally, open source software can be obtained for free, whereas COTS software is mostly sold with strict licensing. You can download and install open source software on any number of workstations, while COTS software often limits the number of workstations per license. With open source software, you can also download the source code and modify or customize the application since it’s freely released and distributed. With COTS software, the source code is usually a company secret, rarely seen by end users.
Key Differences Between Open Source and COTS Software
| Feature | Open Source Software | COTS (Commercial Off-The-Shelf) |
|---|---|---|
| Licensing Cost | Free ($0 annually) | Often $100,000+ annually for GIS |
| Workstation Limits | Unlimited installations | Restricted per license |
| Source Code Access | Fully accessible and modifiable | Company secret, rarely accessible |
| Development Team | Dozens to hundreds of end users, academics, paid volunteers, companies | Finite group of employed developers |
| Bug/Security Fixes | Often identified quicker (many eyes on code) | Varies by vendor timeline |
| Release Cycle | Rolling release (daily/weekly updates) | Major releases years apart (except bug fixes) |
| Proprietary Code | Cannot contain proprietary code under different license | Can contain open source code if license permits |
| Feature Access | All features freely available (no paid tiers unless specified) | May require payment for specific tools/features |
Interestingly, COTS software can actually contain open source code if the license permits redistribution, modification, and sale. For example, the MIT License allows developers to deal with the software without restriction, including the right to sell copies. This means many COTS developers leverage open source tools (database management systems, visualization libraries, wiki applications). The majority of web servers online are Linux-based, smartphone operating systems contain open source code, and even expensive purchased software likely contains some open source code.
What Are the Benefits of Open Source Software for Public Sector Organizations?
Open source software has many benefits for public sector organizations, with the lack of licensing fees being the primary advantage.
Primary and Secondary Benefits of Open Source GIS
| Benefit Category | Specific Advantage | Public Sector Impact |
|---|---|---|
| Financial | No licensing fees | Eliminates $100,000+ annual GIS licensing costs |
| Financial | No surprise license fee increases | More affordable operating costs over time |
| Procurement | Eliminates software purchasing red tape | Faster deployment without approval delays |
| Deployment | Install on every desk without additional costs | Removes barriers to software adoption |
| Functionality | Developed by and for end users | More intuitive and feature-rich |
| Customization | Highly customizable | Extensible with new features and capabilities |
| Support | Large user group + core developers | Community support from end users and developers |
| Interoperability | Built using up-to-date standards | Reads/writes most file formats from COTS software |
While the software license is free, organizations should be aware that costs still exist for training, implementation, and development time to customize the solution. However, these costs may exist even with COTS software.
What Types of Open Source GIS Software Are Available?
The open source GIS software landscape is vast. Unlike office software suites (where there are only a few mature options like OpenOffice and LibreOffice), there are dozens of mature GIS applications, many in active development for decades. Some are even core modules within COTS GIS software.
Open source GIS software falls into seven broad categories:
The 7 Categories of Open Source GIS Software
| Category | What It Does | Popular Examples |
|---|---|---|
| 1. Content Management Systems (GeoCMS) | Displays GIS layers, documents, multimedia on maps; allows customized map layouts | GeoNode |
| 2. Metadata Catalogs | Database with layer information (date created, owner, license); conforms to international or national standards | GeoNetwork |
| 3. Desktop GIS Applications | Robust geoprocessing tools rivaling COTS; includes advanced analysis capabilities | GRASS, Geographic Resources Analysis Support System (since 1982, 350+ modules) SAGA, System for Automated Geoscientific Analyses (since 2001) QGIS (since 2002, v3) |
| 4. Web-based GIS (webGIS) | Frameworks to build dynamic webGIS applications for public engagement and open data sharing |
OpenLayers Leaflet qgis2web plugin GeoMoose Map Bender |
| 5. GIS Servers | Shares geospatial data via standardized Open Geospatial Consortium services (WMS for imagery, WFS for vector data) |
Geoserver MapServer QGIS Server |
| 6. Spatial Databases | Client-server & file-based architecture types; centralized relational database managing data access roles, backups, spatial analysis |
PostgreSQL/PostGIS (since 2001) client-server Geopackage (.gpkg) file-based |
| 7. Mobile Data Collection | Field data collection applications for online/offline data gathering |
QField for QGIS (Android) Mergin/Input App for QGIS (subscription-based) |
Desktop GIS Applications Deep Dive
GRASS (Geographic Resources Analysis Support System): Oldest and most widely used, developed since 1982. It has over 350 core modules for advanced GIS functions including complex 3D point cloud analysis and terrain analysis. There is a steep learning curve, though, so it’s used mostly by advanced analysts and researchers.
SAGA (System for Automated Geoscientific Analyses): Developed at University of Hamburg since 2001. It uses a modular framework with hundreds of tools for terrain analysis, simulation, image classification, geostatistics, and hydrological analysis. It’s used most commonly as remote sensing tool, and has a learning curve for traditional GIS users.
QGIS: Most commonly used open source desktop GIS today. Since development began in 2002, it’s become a major competitor to COTS GIS software. Version 3 includes hundreds of core geoprocessing tools, integrates GRASS/SAGA/3rd party tools, and allows custom plugins via Plugin Library. Layout similar to traditional COTS GIS makes migration painless with high-quality documentation and third-party training options.
How Do You Build an Enterprise GIS Solution with Open Source Tools?
Having reviewed the various types of open source GIS applications, it’s possible to assemble an enterprise GIS solution.
PSD Citywide’s Enterprise GIS: Open Source + Professional Support
PSD Citywide’s Enterprise GIS merges these open source tools:
-
Geoserver (GIS server)
-
PostgreSQL/PostGIS (spatial database)
-
QGIS (desktop application)
-
QField (mobile data collection)
-
Customized software for municipal workflows
This type of solution allows public sector organizations to build a more sustainable GIS department without the burden of excessive software licensing costs, while gaining:
-
Extensive support and training
-
SLA-backed technical assistance
- Seamless Computerized Maintenance Management System (CMMS) integration
For many organizations, taking the plunge into open source GIS is a big step, but a necessary one to advance their organization’s GIS and asset management strategy.
Request a Demo of PSD Citywide Enterprise GIS →
When Should Your Municipality Choose Open Source GIS vs. PSD Citywide Enterprise GIS?
Choose open source DIY when:
-
In-House GIS Expertise: You have skilled GIS staff or an IT team capable of managing the implementation
-
Budget for Training: You can invest in separate staff training and onboarding
-
Implementation Timeline: A 6–12 month timeline is acceptable for deployment
-
Support Requirements: Community forum support is sufficient for your needs
-
CMMS Integration: Custom development for CMMS integration is acceptable
-
Maintenance Capacity: Your internal IT team can handle updates, security patches, and system administration
-
Mission-Critical Needs: This is for non-critical projects where downtime is tolerable
Choose PSD Citywide Enterprise GIS when:
-
In-House GIS Expertise: You have limited GIS expertise and need vendor support
-
Budget for Training: You want included onboarding and ongoing training
-
Implementation Timeline: You need rapid deployment (4–8 weeks instead of 6–12 months)
-
Support Requirements: You need 24/7 SLA-backed technical support with guaranteed response times
-
CMMS Integration: You want native CMMS integration without custom development
-
Maintenance Capacity: You want automatic updates and maintenance handled for you
-
Mission-Critical Needs: This is for mission-critical municipal operations where reliability is essential
