Quality report
Per spatial table: rows, nulls, empties, invalids, SRID, GiST index and extent, over a read-only connection.
Deliverable: CSV with alerts per tableOcto for PostgreSQL, PostGIS and pgRouting
The database answers in SQL. Changing official data is your call.
PostGIS 3.7.0 came out on Oct 30, 2026 and requires PostgreSQL 14 to 19; PostgreSQL 14 loses support on Nov 12, 2026. Geometry, indexes, topology and networks are handled by SQL and the command line. Octo diagnoses, proposes the fix inside a transaction, shows the count first and measures the query plan. What changes in the cadastre, the tolerance and the production window stay with the data owner and the database administrator.
PostGIS3.7.0Oct 30, 2026, GPL v2 or later
PostgreSQL 14Nov 12, 2026end of support; 3.7 accepts 14 to 19
pgRouting 4.0no createTopologygraph with pgr_extractVertices
Sources12listed at the end of the page
01
What Octo does with PostGIS.
Six possible deliverables, taken from the survey. All of them start by reading the database without changing anything, and every change goes through the data owner before the COMMIT.
Geometry fixed with rollback
Diagnosis by reason, a copy of the originals, a count first and ST_MakeValid inside a transaction that only becomes a COMMIT with approval.
Measured query
EXPLAIN (ANALYZE, BUFFERS) before and after, pitfalls such as ST_Distance in the WHERE clause, GiST index created without locking writes.
Coverage and topology
Gaps and overlaps between lots with ST_CoverageInvalidEdges; topology on a copy per block, validated and with the shift measured.
Networks in pgRouting 4.x
Graph built with pgr_extractVertices, network checked, routes and service areas, and old scripts updated after the 4.0 removals.
Load and version upgrade
Load into staging with ogr2ogr, checked by count and SRID; PostgreSQL and PostGIS upgrade rehearsal on a restored copy.
02
Eight arms, no
Eight arms, no COMMIT without approval.
The same Octo cycle, applied to the spatial database. Each arm has a narrow role; people change official data and decide the production window.
-
Discovery
Surveys the database
PostgreSQL, PostGIS and pgRouting versions, extensions, schemas, spatial tables and end-of-support dates.
-
Data
Checks what is stored
SRID, type, validity, coverage and network of each table, with the quality report.
-
Security
Looks at access and exposure
Roles, passwords in scripts or projects, personal data (LGPD) and a database port open to the outside.
-
Architecture
Chooses the path
Geometry or geography, topology or simple coverage, staging before official, target version.
-
Development
Writes the SQL
Always with a count first, a copy of the affected rows, a transaction and a written rollback.
-
Review
Checks by content
Invalids after the fix, area difference, query plan, a graph with no dangling ends. "UPDATE 137" is not a check.
-
Release
Only with your OK
COMMIT, production indexes and version upgrades only in the agreed window and with the database administrator. -
Documentation
Records what changed
How many rows, which table, which tolerance, who approved and how to roll back.
Octo works as support. It does not commit transactions on official data, create indexes in production or upgrade the database without approval.
03
Each task, its own path.
The criteria Octo uses to choose, with the manual for the installed version.
| Task | Path | Note |
|---|---|---|
| Know the versions | postgis_full_version() | Cross-check with PostgreSQL end of support |
| Find invalid geometry | ST_IsValidReason grouped | Read-only |
| Fix geometry | ST_MakeValid(geom, 'method=structure') | Copy, count and transaction; GEOS 3.10+ |
| Gaps and overlaps | ST_CoverageInvalidEdges | Window function, per block; GEOS 3.12+ |
| Radius search | ST_DWithin | Not ST_Distance in the WHERE clause |
| Nearest neighbor | ORDER BY geom <-> ponto LIMIT n | Uses the GiST index |
| Create an index | CREATE INDEX CONCURRENTLY ... USING gist | Outside a transaction; ANALYZE afterward |
| Shared boundaries | postgis_topology | Copy per block; tolerance 0 means 0 in 3.7 |
| Build the graph | pgr_extractVertices | pgr_createTopology was removed in 4.0 |
| Load data | ogr2ogr -f PostgreSQL | Into staging, with a connection service |
04
From diagnosis to a quality routine.
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Database inventory
Versions, extensions, spatial tables and the quality report, without changing anything.
- End-of-support dates
- Invalids, SRID and indexes per table
- Questions for the administrator
Fixes with rollback
Geometry, coverage, indexes and graph fixed in staging, with counts and plans before and after.
- SQL with transaction and copy
- Measured query plans
- Network checked for routing
Routine and upgrade
A weekly report compared with the previous week and a version upgrade rehearsed on a copy.
- Quality tracked over time
- Rehearsal of new PostgreSQL and PostGIS versions
- Record of each change and approval
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.
5
points with a published source, each with its reference shown alongside.
- ConfirmedPostGIS 3.7.0
- Released on Oct 30, 2026; requires PostgreSQL 14–19, GEOS 3.10+ (3.15+ for all features) and PROJ 6.1+.Source: announcement on postgis.net
- ConfirmedEnd of PostgreSQL 14
- Version 14.24, supported until Nov 12, 2026; the policy is five years per major version.Source: postgresql.org, versioning
- ConfirmedpgRouting 4.0
- Removed
pgr_createTopology,pgr_analyzeGraphandpgr_nodeNetwork, among others.Source: pgRouting release notes - ConfirmedUpgrade from 3.6 to 3.7
- For a minor version, the manual documents
SELECT postgis_extensions_upgrade();, which upgrades PostGIS and its sibling extensions, instead of justALTER EXTENSION ... UPDATE.Source: PostGIS 3.7 manual, section 3.4.1 - ConfirmedpgRouting 4.0.2
- Published on Sep 5, 2026, marked as "Latest" on GitHub.Source: GitHub, v4.0.2 tag page
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 checkYour 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 signerThe 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.
PostGIS announcements and manual, the PostgreSQL versioning policy and the pgRouting documentation, consulted on Oct 31, 2026.
- PostGIS 3.7.0 announcementOct 30, 2026
- PostGIS, news3.7 RCs and betas
- PostGIS licenseGPL v2 or later
- ST_MakeValidstructure method, GEOS 3.10+
- ST_CoverageInvalidEdgesPostGIS 3.4+, GEOS 3.12+
- PostGIS, topologyCreateTopology, toTopoGeom, ValidateTopology
- PostgreSQL, versioningend of 14 on Nov 12, 2026
- PostGIS 3.7, administrationpostgis_extensions_upgrade, section 3.4.1
- pgRouting v4.0.2Sep 5, 2026
- pgRoutingalgorithms, GPLv2
- pgRouting, release notes4.0.0 removals
- pgr_extractVerticesbuilding the graph
Your spatial database, checked by what it stores.
The assessment starts with a version inventory and a quality report of every spatial table, without changing anything. You get the list of what is invalid, slow or exposed and the decisions only your team makes, and you decide with it in hand.