GIS Workflows Overview
The GIS workflow system provides a live, read-only view into your application’s database, allowing users to visualize and analyze spatially-enabled business data directly in GIS tools such as QGIS or ArcGIS.
Rather than exporting files or maintaining duplicate datasets, GIS tools connect to curated outputs that always reflect the current state of your data. This ensures teams are working from a single source of truth—without manual updates or version drift.
The system is designed to be flexible and industry-agnostic, supporting any organization that tracks business data with a geographic component, not just traditional GIS or survey workflows.
What Problem Does This Solve?
Traditional workflows for sharing location-based business data often involve:
- Exporting files for mapping or review
- Emailing datasets between teams
- Maintaining multiple versions of the same information
- Losing confidence in which data is “current”
The GIS workflow system replaces that with:
- Live access to database-backed data
- Read-only safety
- Controlled, intentional exposure
- Reusable spatial views tied directly to your application
Think of it as publishing live, map-ready representations of your business data, rather than exporting static copies.
Core Concepts (High Level)
The GIS system is built around three core concepts:
1️⃣ GIS Views – What is published
A GIS View defines:
- The purpose of a map
- Which layers belong together
- Who can access the data
Views act as stable, shareable map definitions.
2️⃣ GIS Layers – How data is assembled
A GIS Layer defines:
- Which database table is queried
- How related tables are joined
- Which fields are exposed
- Which geometry is used for mapping
Layers are query definitions, not datasets, and are intended to expose business records with geographic context—not to manage or edit spatial features.
3️⃣ QGIS Connection – How data is consumed
Once a view exists, it can be accessed externally via:
- OGC API – Features endpoints
- QGIS Desktop (recommended)
External tools connect live and read-only to the view.
The Mental Model (Important)
Understanding this flow makes everything else intuitive:
Application Data ↓ GIS Layer (query + joins + geometry) ↓ GIS View (grouping + permissions) ↓ OGC API Endpoint ↓ QGIS (read-only)
Each step adds structure and safety.
Read-Only by Design
All GIS workflows are intentionally read-only.
This prevents:
- Accidental edits
- Broken relationships
- Invalid data states
- External tools bypassing application rules
All edits must be made inside the application, where validation and permissions are enforced.
Who Should Use GIS Workflows?
GIS workflows are intended for:
- Teams that track business data with locations
- Engineers or planners preparing exhibits or reports
- GIS specialists performing visualization or analysis
- Operations teams coordinating location-based work
- Advanced users who need read-only spatial access to live data
They are not required for everyday application use.
Typical Use Cases
Common scenarios include:
- Visualizing projects, assets, or properties on a map
- Reviewing operational or logistical data spatially
- Sharing live location-based data with consultants or partners
- Producing maps or exhibits based on current business data
- Creating repeatable, read-only GIS views for teams
Recommended Workflow Order
If you are new to the system, follow this sequence:
-
Create a GIS View
Define the purpose and access rules for your map. -
Create one or more GIS Layers
Assemble the data and geometry you want to expose. -
Connect the View to QGIS
Consume the data live in a GIS tool.
Each step builds on the previous one.
Workflow Guides
Use the following guides to get started:
Summary
The GIS workflow system provides a modern alternative to file-based GIS workflows.
It allows you to:
- Publish live spatial data
- Control access and exposure
- Eliminate exports and duplication
- Keep GIS users working from a single source of truth
Think of it as GIS publishing with guardrails.