Description
Audit supplied section geometry relative to a declared area; no application rate is selected.
Precision-agriculture measurements combine spatial cells, sensor clocks, travel speeds, band signals, and application records. A correction or weighted share is meaningful only when coordinate frames, units, timestamps, and coverage bases agree. Supplied calibration and support flags remain distinct from measurements that establish them.
Audit supplied section geometry relative to a declared area; no application rate is selected.
When to use this tool
Use Application Section Area Share when you have the stated field, sensor, map, or application records and need this correction or geometric/accounting component.
How to use the tool and how it works
- Enter sectionWidth, travelledDistance, totalArea. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sectionArea, share. Use the output convention below.
Require nonnegative sectionWidth and travelledDistance and positive totalArea. Return sectionArea=sectionWidth*travelledDistance and share=sectionArea/totalArea.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sectionWidth | Section Width | Required. Finite number; minimum 0. |
| travelledDistance | Travelled Distance | Required. Finite number; minimum 0. |
| totalArea | Total Area | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sectionArea | Section Area | Required. Finite number. |
| share | Section area divided by totalArea; may exceed one. | Required. Finite number. |
{
"input": {
"sectionWidth": 2,
"travelledDistance": 10,
"totalArea": 100
},
"output": {
"sectionArea": 20,
"share": 0.2
}
}Limitations and assumptions
- The rectangular area product must use the totalArea unit. Share may exceed one because repeated or overlapping passes are not removed or constrained to the total.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.
Alternative or Complementary methods
Verify the measurement calibration, coordinate frame, spatial support, and clock convention before combining this term into a map or control workflow. Use a complete equipment or field model when geometric and operating constraints matter.
References
Similar or alternative tools
- Application Map Prescribed Observed Residual
Compare supplied map-cell values with explicit area weights.
- Implement Section Lateral Offset Rotation Term
Rotate supplied forward/right offsets using a clockwise-from-north heading.