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
32 lines
987 B
Markdown
32 lines
987 B
Markdown
# Domain Model Contract
|
|
|
|
## Core aggregates
|
|
|
|
### Project
|
|
A project is an investigation workspace. It contains areas, datasets, analyses, and exports.
|
|
|
|
### Area
|
|
A spatial polygon or selected administrative unit used to clip and analyze datasets.
|
|
|
|
### Dataset
|
|
A source artifact or external reference. Datasets can be raster, vector, reference, model output, mask, or export.
|
|
|
|
### AnalysisRun
|
|
A tracked execution of a pipeline such as detection, segmentation, QA, clipping, tiling, or index computation.
|
|
|
|
### Detection
|
|
A model-derived feature, usually a georeferenced bounding box or polygon.
|
|
|
|
### Segmentation
|
|
A mask-derived polygon or raster mask output.
|
|
|
|
### QualityCheck
|
|
A comparison between model outputs and reference data such as GRB.
|
|
|
|
## Geometry rules
|
|
|
|
- Use SRID 4326 for API-level GeoJSON interchange unless explicitly documented.
|
|
- Use projected CRS for area/length calculations when required.
|
|
- Store original CRS metadata for every dataset.
|
|
- Never calculate area in degrees.
|