Versions Compared

Old Version 5

changes.mady.by.user R. Andres Ferreyra

Saved on

compared with

New Version 6

changes.mady.by.user Stuart Rhea

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Summary

      
AttributeTypeMultiplicityDescription / Comments
Start date/time DateTime 1 
End date/time DateTime 1 
GrowerGrowerId  Integer0..1 Farm(s) 
FarmIdsInteger0..n 
Field(s) FieldIdsInteger0..n Crop zone(s) 
CropZoneIdsInteger0..n 
Operator(s) PersonRolesPersonRole0..n Machine(s) 
MachineIdsInteger0..n 
Implement(s) ImplementIdsInteger0..n 
Total areaTotalArea VariableRepresentationValue 1Slightly redundant, but useful

2: To report per field / cropzone involved in the operation

Products used   
Average rate per product   
Total amount used per product   
Area covered  Important, as it covers the possibility of partial or spot applications.

3: 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?DocumentCorrelations    		DocumentCorrelation0..n 
    ProductUsesProductUse1..n 
    ContextContextItem0..n