Making Data Available in Visual Explorer

From Prepared Data to User Exploration

Visual Explorer presents information only when it is available for the selected crop, layer, location, and date context. This protects users from interpreting incomplete or unsuitable data as a result.

The initial v2 experience uses three layer categories:

• Crop Production for regional production, detected-area, yield, and yield-category information.
• Crop Detection for available detected-crop information at detailed map levels.
• Crop Health (NDVI) for available vegetation-health information at detailed map levels.

Each layer can have one or more available data-acquired dates. The displayed date identifies the dataset being explored and should be included whenever users record or share a finding.

Validate Availability Before User Access

Before announcing a new or updated dataset, verify that:

1. the intended region hierarchy and crop context are available;
2. the appropriate layer and data-acquired date appear in Visual Explorer;
3. map detail, tooltips, and the data panel show information that matches the selected context; and
4. Crop Production values, history, and sub-region views are available where expected.

If a crop is configured but has no customer-ready data for the selected layer or date, explain that the information is not available rather than treating the absence as a crop or production conclusion.

Communicate Context to Users

When new data becomes available, communicate the affected crops, layers, regions, and data-acquired date. Tell users about any known coverage or interpretation limits and direct them to the relevant Visual Explorer workflow.

Data stewards should investigate unexpected empty states, missing regions, or missing crop data before asking users to rely on the affected view.