QGIS repetitive-task automation

SPEC

Technical spec

Map: QGIS
Scripting: Python
PyQGIS
Data: GDAL/OGR

FIT

A good fit when

The same editing, conversion, and export steps are repeated by hand every week
Results differ by operator, so checking them takes longer than the work itself
The processing order is settled but exists only as a document

PREBUILT

Example components

These components illustrate the proposed structure. Template features and scope will be confirmed after implementation and verification.

Processing model skeleton: A QGIS processing model that already takes input layers, parameters, and an output path. Only the steps specific to your work are swapped in.
PyQGIS script set: Reusable functions and error handling for coordinate transforms, attribute cleanup, and spatial operations, collected in one place.
Run log and result report: A fixed format that records processed counts, skipped counts, and failure reasons to a file.
Re-run procedure document: A document template for the run steps and prerequisites, so the same sequence still works after a handover.

The layout and design are adapted to each project.

SCREENS

Example screens

Example screens are being prepared.

SCOPE

In scope

Deliverables

A PyQGIS script or Processing model
Documentation of how to run it and the input/output rules
Execution results against sample data

In scope

Review of the current manual procedure and definition of the automation scope
Implementation of the script or processing model
Verification on the agreed QGIS version in your environment
One revision round after acceptance

Out of scope

QGIS plugin UI development
Server deployment and scheduled execution
Correcting source data quality
Collecting new data

Scope and exclusions are defined before the work starts. The schedule and detailed terms are fixed in the SOW after we talk.

The problem this solves

Repeating the same procedure by hand costs time and produces different results depending on who runs it. Moving a fixed procedure into a script shortens the run and makes the result reproducible against the same criteria.

How it runs

Review the current manual procedure and the input and output data.
Fix the automation scope and the exclusions in writing.
Implement the script or processing model and verify results against sample data.
Verify the execution result in your environment.

Scope versus additional development

If it does not behave as the agreed procedure specifies, that is a defect and is fixed at no charge. Support for a new procedure or a new data type that was not agreed is additional development and is quoted separately.

FAQ

Frequently asked questions

What kind of work can be automated?: Work with a fixed procedure: layer cleanup, attribute calculation, coordinate transforms, spatial joins, exports. Tasks whose judgement criteria change each time need those rules defined first.
Does it work on a different QGIS version?: Behaviour is verified on the QGIS version agreed in the contract. Supporting another version is added to the scope and verified separately.

Need a particular setup?

Tell me which screens and integrations you need, and I will come back with what is feasible.

Ask about this setup