Custom Software
QGIS Plugin Development
Custom QGIS plugins for hydrological workflows, catchment delineation, floodplain export, and modelling-platform bridges. Delivered as scoped engagements with handover documentation.
Plugin Scoped project
Examples
- Automating catchment delineation and rainfall aggregation for internal hydrological workflows
- Exporting floodline outputs to the GIS formats a specific municipality accepts
- Bridging QGIS to HEC-RAS or MIKE so modellers stop moving files by hand
- Batch-processing LIDAR or DEM tiles into catchment-ready derivatives
Who it’s for
Engineering teams, municipalities, and mining water teams whose QGIS sits at the centre of a workflow that is mostly manual — moving files, running the same tool chain on every new project, exporting to formats the reviewer expects. We turn those workflows into plugins so your team clicks a button instead of clicking thirty.
What you get
- A QGIS plugin written in Python, tested against the LTR version of QGIS you run.
- A short handover document: what the plugin does, where its configuration lives, how to extend it.
- The source repository, licensed to you — no lock-in to a vendor portal.
- Optional unit tests for the pieces that matter (typically data conversion, not UI).
How we work
- Scope. We sit with the team that will use the plugin and watch the current workflow. The plugin is only as valuable as the steps it actually replaces — we confirm those before we write code.
- Design. A short design note pins down the inputs, outputs, failure modes, and UI shape. Usually one to two pages, not a waterfall document.
- Build. Incremental, with the team trying it on their data as each piece lands. Feedback in days, not at the end.
- Handover. Install instructions, a short demo with the team, and the source repo handed across. We fix genuine bugs for an agreed period after go-live.
Stack & interoperability
- QGIS: Python API (PyQGIS), PyQt5 or PyQt6 depending on target QGIS version.
- Modelling platforms: HEC-RAS, MIKE (via file format bridges; no reverse-engineered APIs), EPANET.
- GIS: GeoTIFF, ESRI shapefile, GeoPackage, KML.
- Data: CSV, Parquet, PostGIS where a central database is involved.
We do not build plugins for proprietary platforms we don’t have a licence for. If your workflow involves a tool we haven’t worked with, we will say so up front.
What this is not
- Not shrinkwrap software. Each plugin is scoped around a specific workflow; we don’t sell a generic “water plugin” off the shelf.
- Not a commitment to maintain your plugin forever. We offer retainer arrangements for ongoing maintenance if you need them, but they are separate engagements.