Every tab respects the current scope: Field, Season, Block filter, active index, and pass date from the time scrubber. Change any of them and the tab redraws.
Trend
The seasonal time series for the current Field or Block scope, plotted with phenology bands. What it shows- One line per active index (default: the index selected in the layer switcher, plus NDMI as a companion when available).
- Confidence band (P10 to P90) around each line. Wider band means fewer clear passes in that window.
- Vertical phenology bands (emergence, tillering, booting, heading, ripening) from the Risk Model phenology clock.
- Dots for satellite passes; hollow dots for cloud-blocked passes.
- Markers for scout completions and applied VRA maps overlaid on the timeline.
Best for: retrospective review, season-over-season comparison (pair with Compare tab), yield-projection sanity checks.
Distribution
The per-pixel histogram of the selected index for the currently selected pass. What it shows- X axis: index value (e.g., NDVI
-1to+1). - Y axis: pixel count within the current Field or Block scope.
- Colored bands aligned with the map legend so a color on the map maps to a bucket on the histogram.
- Optional overlay: the same distribution from the previous pass (dashed line), so you can see the shift.
Best for: deciding whether an issue is field-wide (weather / uniform stress) or patchy (biotic / infrastructure), and sizing the case for variable-rate application.
Findings
All rule-card matches (active and resolved) for the current Field and Season, ranked by severity and recency. What it shows- One row per finding, with:
- Rule card id and human name (e.g.,
rice_blast— “Blast”) - Severity band (Info / Low / Medium / High / Critical)
- Affected Blocks (chips)
- Yield-at-risk % and estimated loss (t), resolved through the layered yield-impact
- Days-to-mitigate countdown or resolution timestamp
- Top action from
mitigation.actions
- Rule card id and human name (e.g.,
- Filter chips for status (active / resolved / dismissed), severity, and rule-card category.
- Sort by severity, by countdown, or by first-fired timestamp.
- Rows with a red countdown chip are the day’s must-do items.
- Rows with
raise_contradictionbadges are cases where a scout report disagreed with the signal; they need a supervisor look, not just a scout follow-up. Contradictions come fromactivity_bindingson the rule card. - Rows marked
map.appliedshow that mitigation was executed; the countdown stops and severity is reset per the rule card.
Captures
Every image and upload attached to this Field this Season. What it shows- Chronological grid of thumbnails:
- Satellite passes (source labeled: Sentinel-2, Sentinel-1, Landsat, Planet, custom drone)
- Scout uploads (photos with GPS)
- Drone survey outputs (orthomosaic, per-pass NDVI)
- Verification bundles (satellite pre / post pair when applicable)
- Each thumbnail carries source, date, cloud cover (if satellite), and uploader (if human).
- Click a capture to load it as the active pass on the map and scrubber.
Best for: media archive, audit prep, and validating a suspicious pass against a scout photo taken the same day.
Compare
Side-by-side comparison of the current view against another Field, Block, cycle, or index. The cycle comparison respects Crop Cycle Models: rice compares Main-to-Main aligned by phenology week; oil palm compares Production Year at the same Tree Age Cohort; pineapple compares Batches at the same age from planting. See Cycle Analysis for the full mode reference. What it showsSame Field, another cycle
Two Trend curves overlaid, aligned by phenology week (cyclical), calendar month (perennial), or age from planting (rolling continuous). The picker only offers cycles that are comparable (same
season_type for cyclical, same Tree Age Cohort for perennial).Same cycle, another Field or Block
Two curves plus two Distribution histograms. Best for peer comparison across an Estate (e.g., is Field F1 running behind Field F2?).
Same Field, another index
NDVI vs NDMI on the same axis. Best for diagnosing whether canopy stress and water stress are correlated or independent.
Rule-card level
All Fields in the Estate that fired the same rule card this cycle. Best for seeing whether a hazard is field-specific or Estate-wide.
- Diverging curves after a specific event: check that event in the Actions tab.
- Curves that converge at harvest despite different mid-season shapes: the field self-corrected. Useful for validating that mitigation actions actually worked.
- Curves that stay apart: consistent variety or ecosystem effect. Consider updating
variety_grouporecosystemon the field record so the Risk Model uses the right multiplier next season.
Actions
The Field-scoped slice of Activity Log: everything that was done, is being done, or is scheduled here. What it shows- One condensed timeline row per event: alerts, scout tasks, VRA lifecycle, verifications, phenology transitions, imagery ticks.
- Bar length equals event duration or countdown window.
- Color equals severity for alerts and status for tasks.
- Assignee avatars for scout tasks and VRA reviews.
- Dependency arrows:
risk → scout → VRA → verificationchains rendered when spawning relations exist.
Best for: at-a-glance answer to “what has happened on this Field this Season, and did we respond?”, without leaving the workspace.
Tab decision guide
Related
- Fields Workspace Overview - the workspace this reference documents.
- Field Data Model - Field, Block, Zone, Season, Observation.
- Risk Model - the rule cards behind the Findings tab.
- Activity Log - full timeline, of which the Actions tab is a Field slice.
- Vegetation Indices - the metrics behind Trend and Distribution.