The preview calls out the dashboard workflow and the blocked GeoMiniLM production gate, so the model work is not presented as launched.
GeoVis LM
A GIS and scientific visualization lab that runs terrain, flood, wildfire, vector-overlay, report, dashboard, worker, and GeoMiniLM workflow experiments while keeping model deployment behind a failed production gate.
GeoVisLM milestones and blocked model path.
The operational path has moved forward. The model-assisted recommendation path is blocked until a future sealed gate passes.
Move from geospatial scripts toward a reliable operations workflow.
GeoVisLM needed to connect DEM inputs, vector overlays, generated maps, reports, auth, durable run history, and worker execution without overstating the readiness of its small workflow model.
Verify the operational path separately from the model path.
The dashboard, worker, output browsing, auth, project sharing, comments, Docker validation, and Prime deployment checks are tracked as completed work. GeoMiniLM recommendation integration is held back behind explicit evaluation gates.
The GeoMiniLM production gate failed and deployment remains blocked.
Candidate `0bc44b0` scored `0.6475` against a required `0.7600`; all-record, category-floor, threshold, and confidence gates failed. The frozen validation outcomes are not used for direct tuning.
Verified milestones
- Terrain analysis produces slope, hillshade, terrain-risk maps, summaries, and reports from DEM inputs.
- Flood-risk, wildfire-risk, vector-overlay, QGIS plan-only, and ParaView-compatible entry points are documented.
- Dashboard supports projects, runs, validated uploads, lifecycle history, output browsing, report generation, auth, and optional bearer access.
- Docker Compose validation covers dashboard, persistent worker, PostGIS, output storage, health, and readiness.
- Project sharing and report comments passed 72 local tests plus operational smoke and deployment checks.
Blocked gate and next path
- Production deployment and dashboard integration for GeoMiniLM remain blocked.
- Development contract requires grouped workflow-family holdouts and per-category floors before future candidate selection.
- A future formal production gate must pass on a new sealed shadow set before dashboard recommendations can ship.
- Recommendation UI remains a planned approval-first workflow, not a live production claim.