Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
To Report per Operation
| Attribute | Description / Comments |
|---|
| Start date/time | |
| End date/time | |
| Grower | |
| Farm(s) | |
| Field(s) | |
| Crop zone(s) | |
| Operator(s) | |
| Machine(s) | |
| Implement(s) | |
| Total area | Slightly redundant, but useful |
To report per field / cropzone |
| Products used | |
| Average rate per product | |
| Total amount used per product | |
| Area covered | |
Calculated |
| REI | Restricted-entry interval. Calculation needs: - There are climate-dependent options for the REI value. This is average annual precipitation-dependent, and could be a user-specified setting in a first version.
- The REI needs to be added to the application end-time to calculate a (very useful) re-entry date/time. A challenging aspect of this is that REI should be geopolitical-context-dependent; how do we express to the system, in a data-driven way, what to do with it?
|
| PHI | Pre-harvest interval. Calculation needs: - There are crop-dependent options for the PHI value. This would require that the crop protection reference data API use known (and shared) crop codes.
- The PHI needs to be added to the application end-time to calculate a (very useful) re-entry date/time. A challenging aspect of this is that REI should be geopolitical-context-dependent; how do we express to the system, in a data-driven way, what to do with it?
|