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
38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
# Skill: Raster Pipeline
|
|
|
|
Use this skill for GeoTIFF/raster metadata, clipping, tiling, band handling and remote-sensing indices.
|
|
|
|
## Read first
|
|
|
|
- `docs/RASTER_OPERATIONS_SPEC.md`
|
|
- `docs/standards/RASTER_STANDARDS.md`
|
|
- `docs/DETECTION_PIPELINE_SPEC.md` when preparing AI tiles
|
|
- `docs/STORAGE_ARCHITECTURE.md`
|
|
|
|
## Raster rules
|
|
|
|
- Preserve georeferencing metadata.
|
|
- Never drop CRS silently.
|
|
- Keep raster-derived outputs traceable to source dataset and parameters.
|
|
- Use deterministic tile naming.
|
|
- Store heavy outputs under documented storage roots, not random folders.
|
|
- For V1, prefer metadata and small fixtures over heavy real rasters.
|
|
|
|
## Operations checklist
|
|
|
|
- [ ] Validate raster readable.
|
|
- [ ] Extract CRS, bounds, transform, dimensions, band count, dtype.
|
|
- [ ] Clip by area where requested.
|
|
- [ ] Generate tiles with configured tile size and overlap.
|
|
- [ ] Preserve mapping from tile pixels to map coordinates.
|
|
- [ ] Emit metadata JSON for downstream services.
|
|
- [ ] Add tests with tiny raster fixtures when possible.
|
|
|
|
## Completion report fields
|
|
|
|
- Raster operations implemented.
|
|
- Metadata fields produced.
|
|
- Storage paths used.
|
|
- Tests run.
|
|
- Known limitations.
|