Skip to content
Octo × QGIS PT Request an assessment

Octo for QGIS, PyQGIS and batch processing

QGIS runs without opening the window. The scale and the signature remain yours.

QGIS is open source, ships every four months and, since 4.0 (Mar 6, 2026), runs on Qt6. Almost everything done on screen has a command-line path: qgis_process runs algorithms and models, PyQGIS scripts audit projects and export entire atlases to PDF. Octo builds these batches and checks them by content. Scale, method and the map signature stay with the technical lead and the cartographer.

Request an assessment See what it does
Four layers of a fictitious project stacked in perspective, from bottom to top: relief in elevation bands, drainage, blocks and labels; on the right, a terminal runs qgis_process and an atlas script, and three A3 PDF sheets come out checked, one of them flagged for review relief · DTM drainage · r.watershed blocks · SIRGAS 2000 / UTM F-005 atlas coverage FICTITIOUS PROJECT · EPSG:31983 $ qgis_process run native:clip results: OUTPUT … OK $ python3 atlas_lote.py … 120 sheets · 2 to review F-005 OK F-006 OK empty layer? F-007 REVIEW
Illustration: a project's layers become checked atlas sheets; fictitious data.
QGIS LTR3.443.44.15 on the roadmap page, Oct 31, 2026
QGIS 4.0 on Qt6Mar 6, 2026next LTR: 4.4.4, scheduled for Mar 5, 2027
Cadence4 monthsone LTR every three releases
Sources11listed at the end of the page
01

What Octo does with QGIS.

Six possible deliverables, taken from the survey. All of them start by reading the project and the installation without changing anything, and all go through the lead before becoming a product.

Project audit

Reads the .qgz with PyQGIS and lists broken layers, missing CRS, passwords stored in the source and layouts with atlases, with the password masked in the report.

Deliverable: CSV per layer + list of what to fix

Batches with qgis_process

Fixes, reprojects, clips and dissolves dozens of layers without opening QGIS, with a JSON log per step and the algorithm's help saved alongside.

Deliverable: ready layers + checked log

Batch atlas

Exports one sheet per feature with QgsLayoutExporter.exportToPdfs and checks the signature, number of sheets and size of each PDF.

Deliverable: sheets + check report

Testable models

Turns a repeated procedure into a processing model, with a fictitious test layer and the expected result noted.

Deliverable: model + reproducible test

GRASS inside QGIS

Hydrology and heavy raster through the GRASS provider, finding the installation's actual prefix and parameters before running.

Deliverable: watersheds and drainage + points to validate

Moving to QGIS 4

Inventory of versions and plugins, Qt6 check, critical projects opened in both versions and comparison of batches and PDFs.

Deliverable: report of differences for the team to decide
02

Eight arms, one map checked before it ships.

The same Octo cycle, applied to QGIS. Each arm has a narrow role; people choose the scale and method and sign the map.

  1. Discovery

    Surveys the installation

    QGIS versions on each machine, active plugins, processing providers, critical projects and where the data comes from.

  2. Data

    Checks origin and CRS

    CRS, date and source of each layer, required license attribution and up to which scale the data holds up.

  3. Security

    Looks at what leaks

    Passwords stored in projects, personal data in shared layers (LGPD) and plugins of unknown origin.

  4. Architecture

    Chooses the path

    LTR or latest release; model or script; qgis_process or PyQGIS; where the batch runs.

  5. Development

    Writes the script

    qgis_process batches, PyQGIS scripts and models, always with a dry-run mode and the actual help saved.

  6. Review

    Checks by content

    Feature count, extent, area, PDF signature and a rendered sheet by sample. Exit code zero is not a check.

  7. Release

    Only with your OK

    A batch is delivered, a plugin swapped or a workstation migrated only after the lead's approval.

  8. Documentation

    Records what was done

    QGIS version, algorithms and parameters, exported sheets and who approved each batch.

Octo works as support. It does not choose the scale or the method, sign maps or change workstation versions without approval.

03

Each task, its own path.

The criteria Octo uses to choose, with the documentation for the installed version.

TaskPathNote
Know which algorithms existqgis_process listSave the list with the version
See the actual parametersqgis_process help <alg>Compare with the script before running
Run in batchqgis_process --json run <alg> -- ...QT_QPA_PLATFORM=offscreen headless
Long parametersqgis_process run <alg> - with JSONinputs key; can include project_path
Run a modelqgis_process run modelo.model3Test layer with expected result
Export an atlasPyQGIS QgsLayoutExporter.exportToPdfsCheck %PDF, number of sheets, size
Audit a projectPyQGIS QgsProject.readMask passwords in the report
HydrologyGRASS provider in processingPrefix and parameters from help
Plugin for QGIS 4qgisMaximumVersion=4.99 + qgis.PyQtpyqgis4-checker check on upload
04

From the one-off batch to repeatable production.

Three steps. Each one only makes sense after the previous one has shown results on your team.

A proposal, not a promise

1 Today

Inventory

Versions, plugins and critical projects, with broken layers and exposed passwords, without changing anything.

  • Version and plugins per machine
  • Audit of critical projects
  • Questions for the technical coordinator
Benefit: know what exists before changing
2 Next

Checked batches

Repeated atlases and processing become scripts with a dry run, a log and an exceptions report.

  • PDF atlas with a check
  • qgis_process batches with a log
  • Models with a test layer
Benefit: the team reviews exceptions, not sheet by sheet
3 Later

Version under control

Move to LTR 4.x with a pilot, comparative tests and a way back.

  • Plugins checked for Qt6
  • Projects compared in both versions
  • Record of who approved each step
Benefit: a version change with no surprises on the map
05

Confirmed in a source.

Each point below has a source published by the project or by the organization responsible for the standard. The sources are in the next section.

3

points with a published source, each with its reference shown alongside.

ConfirmedQGIS 4.0 on Qt6
Released on Mar 6, 2026, described as the migration of the core "onto the Qt6 framework".Source: QGIS 4.0 visual changelog
ConfirmedNext LTR
4.2 will not be an LTR; the LTR becomes 4.4.4, scheduled for Mar 5, 2027.Source: blog.qgis.org, Oct 3, 2026
Confirmadoqgis_process
list, help, run with -- or JSON via standard input, --json, and QT_QPA_PLATFORM=offscreen headless.Source: QGIS 3.44 manual
06

What Octo does and what stays with you.

Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Surveys, calculates, organizes and produces the documents: spreadsheets, reports, maps and drafts.

Deliverable: material ready to check

Your team checks

The licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.

Step: review by the signer

The signer

Octo does not sign. Projects, technical reports, ART/RRT, accountability reports and any official document are still signed by the company's or agency's licensed professional: here, the technical lead for the map or the survey.

Signature: technical lead for the map or survey
07

Sources.

Roadmap, changelog, blog, manual and API of the QGIS project, GRASS news and the OpenStreetMap license page, consulted on Oct 31, 2026.

Your QGIS, checked by what it delivers.

The assessment starts with an inventory of versions, plugins and critical projects, without changing anything. You get the list of what is broken, what is exposed and the decisions only your team makes, and you decide with it in hand.

Request an assessment