Category
Agricultural computer vision: what field imagery can and cannot determine
Definition
Agricultural computer vision is the application of machine-vision models to imagery captured in working crop fields — from vehicle-mounted rigs, handheld devices, or aircraft — in order to identify plants, pests, life stages, and visible damage, and to locate them within the frame. It estimates what is visible in an image. It does not, on its own, establish field-scale pest pressure, biological significance, or whether treatment is justified.
This page separates what a vision model estimates from what a management decision requires, and states plainly what Swathmark has and has not demonstrated.
- Published
- Last updated
What is agricultural computer vision?
It is the use of computer-vision models on imagery captured in working crop fields to identify plants, pests, life stages, and damage and to locate them within the frame. The output is an estimate about an image, not a conclusion about a field.
It is machine vision applied to a domain that breaks most of machine vision's convenient assumptions. The imagery is operational rather than curated: it is collected during normal field activity, under whatever light, dust, wind, and canopy conditions apply that day. That is the distinction from benchmark computer vision, where the images are selected before the model ever sees them.
- Vehicle- or implement-mounted rigs capturing along a pass at working speed.
- Handheld or phone capture during scouting rounds.
- Aerial capture from uncrewed aircraft, at coarser ground resolution.
- Fixed in-field cameras observing a known plot over time.
Ground resolution at the target — not sensor megapixels — determines whether a small pest or an early life stage is resolvable at all.
What can computer vision determine from a field image?
Within the area an image actually covers, and under capture conditions the model has been evaluated for, it can estimate presence, position, apparent species, apparent life stage, and visible damage. Each of those is an estimate carrying its own uncertainty.
| Observation | What the model estimates | What it does not establish |
|---|---|---|
| Presence | That a target appears at a location in this frame. | That the target is present, or absent, elsewhere in the field. |
| Species | The most likely species given appearance at this scale. | Confirmed identity where two species are near-identical at a stage. |
| Life stage | The apparent developmental stage of what is visible. | Stage distribution across the population. |
| Count and density | Counts within the imaged area. | Field-scale pest pressure, which depends on sampling design. |
| Damage | Visible loss of leaf area in view. | Cause of the damage, or its yield consequence. |
What can computer vision not determine from a field image?
It cannot see what the canopy hides, resolve species that look alike at a given stage, extrapolate one frame to a whole field, or judge whether an intervention is warranted. Those limits are structural, not defects to be engineered away.
- Occluded targets: insects on leaf undersides, within the canopy, or in soil are absent from the image, and absence from an image is not absence from the field.
- Look-alike confusion: closely related species, and early stages of unrelated ones, can be visually indistinguishable at field capture resolution.
- Sampling reach: coverage, pass spacing, and route determine what the imagery can represent. A model cannot recover information the capture never collected.
- Biological significance: whether an observed level of a pest matters depends on crop stage, growing conditions, and a threshold defined outside the model.
- Regulatory judgment: product choice and label compliance are not visual questions and are not addressed by any model output.
How is agricultural computer vision different from crop scouting?
Scouting samples plants by eye and produces a skilled human judgment on the spot. Computer vision applies a fixed, versioned model to whatever imagery it is given, so it is repeatable and reviewable but blind to everything outside the frame.
| Property | Crop scouting | Computer vision |
|---|---|---|
| Coverage | Sampled plants along a route. | Whatever the capture pass imaged. |
| Repeatability | Varies with scout, fatigue, and time available. | Identical output for identical input and model version. |
| Context available | Can lift leaves, dig, and read the whole field. | Limited to what the sensor recorded. |
| Reviewable later | Depends on notes taken. | Source image and model version are retained. |
| Where judgment sits | With the scout, in the moment. | In a versioned policy, applied after detection. |
They are complementary rather than competing. Scouting supplies the biological ground truth that a model has to be trained and evaluated against; imagery supplies coverage and a durable record that scouting notes do not.
Why does image quality decide whether a model output is usable?
A model will return a confident-looking answer on an unusable image, because nothing in inference checks whether the input was fit for the question. Assessing quality before inference is what stops a capture defect from becoming a wrong decision.
Motion blur at working speed, underexposed canopy shade, water or dust on the lens, and insufficient resolution at the target all degrade an output without announcing themselves. Verification therefore runs ahead of detection, and an asset that fails is treated as an invalid input rather than a weak one.
How does Swathmark use computer vision?
As one stage of a longer chain. Detection output is combined with verified capture context, biological context, a versioned threshold policy, and explicit uncertainty handling before any treat, no-treat, or abstain decision is produced.
- 1Register the capture: farm, field, crop, session, rig, calibration, and capture geometry.
- 2Verify the asset: data rights, metadata completeness, calibration state, and measured image quality.
- 3Run a versioned detection model and record which model and calibration produced the output.
- 4Add biological context: life stage, density within the imaged area, and crop stage.
- 5Evaluate against a versioned threshold policy, carrying uncertainty forward rather than discarding it.
- 6Emit treat, no-treat, or abstain, with a decision record that can be re-read later.
What has Swathmark demonstrated about its models?
No model-performance figures are published. Accuracy, recall, precision, calibration, and false-treatment rate are conditional claims that require an approved evidence record stating dataset, crop, pest, and model version, and none has been approved for publication.
That is a deliberate policy rather than an omission. A performance number published without its dataset, operating conditions, crop, pest, and model version cannot be checked by anyone, and cannot be relied on by a grower deciding whether to act.
Inputs, outputs, limitations, and evidence status
Inputs
- Field imagery belonging to a registered capture session.
- Capture metadata: farm, field, crop, date, rig, and capture geometry.
- Camera calibration state at the time of capture.
- Recorded data rights covering analysis and, separately, training use.
- Annotations and adjudicated biological labels, for training and evaluation.
Outputs
- Per-image detections with position and a confidence value.
- Apparent life-stage estimate where the stage is visually separable.
- Counts and visible damage within the imaged area only.
- Measured image-quality assessment for the asset.
- An explicit invalid-input result where verification fails.
Limitations
- Estimates image content; does not establish field-scale pest pressure.
- Cannot detect occluded targets on leaf undersides, inside the canopy, or in soil.
- Look-alike species and early stages may be indistinguishable at capture resolution.
- Degraded capture — blur, exposure, dust, water on the lens — invalidates output.
- Produces no agronomic, pesticide-label, or treatment advice.
Evidence status
- No accuracy, recall, precision, calibration, or false-treatment figures are published.
- The first validation domain is Colorado potato beetle in potatoes.
- Generalization across crops, regions, and capture systems is a design goal, not a demonstrated result.
- Product interfaces shown on this site are illustrative and labeled as such.
Terms used on this page
Definitions are shared site-wide. The full list is in the glossary.
- Agricultural computer vision
- The application of computer-vision models to imagery captured in working crop fields in order to identify plants, pests, life stages, symptoms, and their location within the frame. It estimates what is visible in an image; it does not by itself establish whether an action is justified.
- Detection
- A model output asserting that a target — a pest, a life stage, a symptom — is present at a location in an image, usually with a confidence value. A detection is an estimate about an image, not a statement about a field.
- Image quality
- The measured suitability of an image for analysis: focus, motion blur, exposure, occlusion, resolution at the target, and coverage of the intended area. Quality is assessed against the task, not judged by eye.
- Crop scouting
- Structured in-field inspection of a crop to estimate pest presence, life stage, and pressure, typically by sampling plants along a route. Scouting is skilled, sampled, and time-limited — which is why its coverage and repeatability vary.
- Model version
- The specific, immutable identifier of the trained model that produced a detection, together with the dataset and training run behind it. Without a recorded model version, a past result cannot be reproduced or re-examined.
Related topics
- Pest decision platformHow a pest decision platform differs from pest detection: the verified inputs it requires, the treat, no-treat, or abstain outputs it produces, and who uses it.
- Field data verificationThe capture metadata, rights, calibration, and image-quality checks a field image must pass before it can support a decision or enter a training dataset.
- Biological threshold policiesWhat a biological threshold policy contains, how it differs from a detection, who sets thresholds, and why policy is versioned separately from model code.
- Colorado potato beetleColorado potato beetle biology and life stages, what computer vision can detect for each, why Swathmark starts here, and the current validation and evidence status.
Swathmark does not provide agronomic, pesticide-label, or treatment advice. Thresholds, product selection, and label compliance remain the responsibility of the grower and their advisers. Scope of use.
