Description
Supplied pinhole pixel scale with an explicit obliquity factor.
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.
Supplied pinhole pixel scale with an explicit obliquity factor.
When to use this tool
Use Agricultural Drone Pixel Ground Size Term 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 height, sensorPixelPitch, focalLength, obliqueScale. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read groundPixelSize. Use the output convention below.
For nonnegative height and positive sensorPixelPitch, focalLength, and obliqueScale return groundPixelSize=height*sensorPixelPitch*obliqueScale/focalLength.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| height | Height | Required. Finite number; minimum 0. |
| sensorPixelPitch | Sensor Pixel Pitch | Required. Finite number; strictly above 0. |
| focalLength | Focal Length | Required. Finite number; strictly above 0. |
| obliqueScale | Oblique Scale | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| groundPixelSize | Ground Pixel Size | Required. Finite number. |
{
"input": {
"height": 100,
"sensorPixelPitch": 0.000005,
"focalLength": 0.05,
"obliqueScale": 1
},
"output": {
"groundPixelSize": 0.01
}
}Limitations and assumptions
- Pixel pitch and focal length need the same sensor length unit; the result uses the height unit per pixel. A supplied scalar obliquity factor is not a full camera, terrain, or flight-safety model.
- 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.
- Application Section Area Share
Audit supplied section geometry relative to a declared area; no application rate is selected.