Satellite crop monitoring with dated field observations
Review field observations and available spectral layers with their dates, source context and coverage limits.
A satellite observation is useful when you can tell which field and date it describes. AgriDigi connects field selection, an observation configuration and saved results in a single workspace. Start with the correct field boundary, review the available engine and analysis settings, and keep the acquisition or observation date in view when examining the result.
The observation workflow is separate from planting records, crop-photo analysis and physical device control. Use it to review available field evidence alongside the crop stage, recent work and conditions you observed on the ground. An attractive map alone does not explain why one part of a field differs from another.
From a field boundary to a dated observation
Select an owned field or the supported boundary input, then review its outline and area. Configure the observation using the available date window, engine and analysis controls. Read any account, credit or availability information before starting a request. A missing result should be investigated through its reported status rather than treated as a zero measurement.
Inspect the returned map layers, metrics and summary together. The results workflow includes observation history, and supported views offer comparison and reporting controls. Review which dates and layers are being compared and whether the result contains usable coverage. Keep the underlying field boundary and source context consistent when evaluating a change.
Example: investigate a change in one field
- Open satellite observation and select the intended field. Confirm its saved boundary rather than relying on the field name alone.
- Choose the available observation settings and date window. Review the selected engine and request information before submitting.
- Inspect the result date, selected spectral layer and available metrics. Note missing coverage or a reported processing problem.
- Open a previous saved result when available. Compare the date, boundary and layer before treating a visible difference as a field change.
- Use the observation to prioritize a field check. Record the actual finding and any subsequent work in the appropriate field or task record.
The observation retains its date and field context, while a field visit and any resulting task remain separately recorded evidence.
What to review before you use this workflow
- This workflow does not promise live imagery, cloud-free coverage, a fixed revisit interval or a successful observation on every requested date. The selected engine and available source determine what can be returned.
- Spectral indices and generated summaries do not establish a diagnosis, a treatment recommendation or a guaranteed yield improvement. Check the source and confirm consequential decisions through appropriate field assessment.
- Features, supported layers, request capacity and credit use depend on the current platform and account configuration. The public guide does not grant access to a field or start an observation request.
Frequently asked questions
Is a satellite observation a live view of my field?
No. Review the observation date and the imagery or processing source shown with the result. Availability depends on the selected date window, coverage, enabled engine and account access.
Can a vegetation index diagnose a crop problem?
An index is an observation to investigate alongside field conditions and other records. It does not establish a disease, prescribe treatment or prove the cause of a change.
Can I compare observations from different dates?
The workspace provides saved observation history and comparison controls where supported. Review the field boundary, source, selected layer and available data before interpreting a difference.
Explore the workflow in your workspace
Sign in to use your private farm workspace. Access depends on the modules available to your account.