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
695 B
695 B
CRS Policy
API Boundary
GeoJSON in API responses should be EPSG:4326.
Analytical Operations
For Belgium/Kempen projected calculations, use EPSG:31370 where possible.
Raster Operations
Raster operations must preserve source CRS unless a reproject operation is explicitly requested.
Required Metadata
Every dataset must store:
- source CRS;
- normalized CRS string;
- bounds in source CRS;
- bounds in EPSG:4326;
- transform/affine for rasters where available.
Unsupported Cases
If CRS cannot be determined:
- dataset can be stored as
metadata_failedorrequires_crs; - processing requiring geospatial alignment must be blocked;
- UI must ask for CRS or show limitation.