Initial public release
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
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
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
# Pass 04 — Project, Area and Dataset API
|
||||
|
||||
## Goal
|
||||
|
||||
Implement first real API slice.
|
||||
|
||||
## Implement
|
||||
|
||||
- Project create/list/read.
|
||||
- Area create/list/read for a project.
|
||||
- Dataset registration endpoint and metadata placeholder contract.
|
||||
- Validation for GeoJSON polygon areas.
|
||||
- Contract tests with fixtures.
|
||||
|
||||
## Constraints
|
||||
|
||||
- No frontend-only fake data assumptions.
|
||||
- Invalid geometry must produce structured error.
|
||||
- Dataset upload may be scaffolded, but response contracts must be stable.
|
||||
|
||||
## Validation
|
||||
|
||||
- API tests.
|
||||
- Contract fixture comparison where possible.
|
||||
- Backend import.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- A client can create a project, add an area, register a dataset and retrieve them.
|
||||
- Responses follow the documented envelope.
|
||||
- Execution log updated.
|
||||
Reference in New Issue
Block a user