From satellite to farm decision. A visual reference for the build phase — covering data architecture, interface principles, and responsive design across field and desktop contexts.
The dashboard presents what the water is doing. It does not tell the farmer what to do about it. Metrics show values and site-relative context rather than a traffic-light risk score that pre-digests the judgment for someone who knows their water better than any satellite does.
Alert triggers are configured by the grower, not preset by the system. A kelp farm in the Gulf of Finland has different temperature tolerances than a mussel farm off Brittany. The farmer's local expertise defines the parameters. The system holds and monitors them.
Every metric is shown against the site's own historical baseline, not a generic regional average. This respects the ecological specificity of each location and makes the data readable to someone who has watched that particular stretch of water across multiple seasons.
The field context is not an edge case. It is the primary use environment. The interface must work on a device that may be wet, in direct sunlight, held in one hand, by someone whose attention is divided between the screen and the water around them.
Every metric is traceable to its source — Sentinel-3 SLSTR, CMEMS IBI model, Sentinel-2 MSI — accessible one tap away. Farmers and regulators should be able to see exactly what the dashboard is showing and where it came from, without needing to trust the system blindly.