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
26 lines
1021 B
Markdown
26 lines
1021 B
Markdown
# ADR-001 — Technology Stack
|
|
|
|
## Status
|
|
Accepted for V1.
|
|
|
|
## Context
|
|
GeoIntel Kempen must demonstrate modern web development, geospatial processing, and GeoAI engineering. The stack must be realistic for a portfolio project while remaining close to professional workflows.
|
|
|
|
## Decision
|
|
Use:
|
|
|
|
- Frontend: React + TypeScript.
|
|
- Map UI: MapLibre GL with Deck.gl where advanced overlays are useful.
|
|
- Backend: FastAPI.
|
|
- Database: PostgreSQL + PostGIS.
|
|
- Processing: GeoPandas, Shapely, Rasterio, PyProj, GDAL-compatible tools.
|
|
- AI: PyTorch with Ultralytics YOLO first; SAM/segmentation later.
|
|
- Jobs: Redis + RQ for V1.
|
|
- Storage: local filesystem with explicit storage abstraction.
|
|
|
|
## Consequences
|
|
This stack keeps the first build achievable while matching the vacancy profile closely: Python, raster/vector processing, computer vision, AI pipelines, and GIS outputs.
|
|
|
|
## Non-goals
|
|
Do not introduce Django, Flask, MongoDB, Firebase, or a second frontend framework unless a future ADR explicitly replaces this decision.
|