Jens
faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
28 lines
894 B
Markdown
28 lines
894 B
Markdown
# ADR-002 — PostGIS as Spatial Source of Truth
|
|
|
|
## Status
|
|
Accepted for V1.
|
|
|
|
## Context
|
|
GeoIntel stores areas, datasets, AI detections, segmentations, QA geometries, and exports. Spatial operations need to be queryable and persistent.
|
|
|
|
## Decision
|
|
Use PostgreSQL with PostGIS as the canonical database for:
|
|
|
|
- project areas,
|
|
- dataset spatial bounds,
|
|
- vector features,
|
|
- detection polygons/boxes,
|
|
- segmentation polygons,
|
|
- QA/QC geometries,
|
|
- spatial metadata,
|
|
- analysis outputs.
|
|
|
|
Raw rasters, tiles, masks, and large binary artifacts stay on disk/object storage. PostGIS stores metadata and vectorized results.
|
|
|
|
## Consequences
|
|
The backend can do spatial filtering, intersections, bounding-box queries, and QA matching without reloading every file. The portfolio visibly demonstrates professional GIS database skills.
|
|
|
|
## Non-goals
|
|
Do not store full large rasters as database blobs in V1.
|