We recognize that certain weather events may have caused crop damage. We want you to know that we are dedicated to your database being the best it can be and know that we are here to assist you.
Reasons for Crop Loss:
- Drowned Crop
- Prevented Plant
- Chemical Damage
- Not Planted
- Drought
- Hail
- Wind
- Whole Field Crop Destruct
As an advisor, what two things should you do to handle lost crop?
- Communicate with your Advisor Support Representative to create a Crop Loss Polygon!
- Communicate whether you want your Crop Loss Polygon to display a “0” yield or any other value. We recommend utilizing a value of 1 or greater (non-zero value).
-
- “1” (or greater) yield = Reports in Decision will include these areas in Cost calculations.
- “0” yield = Reports in Decision will exclude these areas from Cost calculations.
- “1” (or greater) yield = Reports in Decision will include these areas in Cost calculations.
How does this help me?
- Dashboards allow for filtering out data that has been designated as “Crop Loss”.
- System-wide, in Reports and Group data, Crop Loss areas are separated as their own unique crop type, keeping them from averaging with the rest of the data. This provides you with a cleaner database.
What happens if I don’t tell my Advisor Support Rep to create a Crop Loss Polygon?
- Harvest File with Zero Data Points (The Grower kept the harvester head down and it recorded “0” as the yield).
How it affects Premier Decision & Analytics:
-
- Your reports will show “0” yield.
-
-
- The hybrid/variety will be assigned that value of “0” and may misrepresent your product performance in reports, dashboards, and queries.
-
How it affects Premier Precision:
-
- When calculating your VR nutrient recs using the yield file for removal, the neighboring yield points will still interpolate into your “0” yield areas, generating a removal within the “0” yield areas.
- In this example, the “0” yield acres are substantially more than the “Zero Rate” acres in the removal file, due to interpolation.
- When calculating your VR nutrient recs using the yield file for removal, the neighboring yield points will still interpolate into your “0” yield areas, generating a removal within the “0” yield areas.
NOTE: By default, zero yield points will remain in your yield file. If you would like them removed, you must communicate that to your Advisor Support Representative prior to processing. If you have them removed, then you will have NULL values.
2. Harvest File with crop loss areas that do not have any yield points (Grower picked up the head and it did not record or “0” data points have been removed).
How it affects Premier Decision & Analytics:
-
- All data associated with these areas are assigned a “None” value and will be excluded from the data it is associated with. (Note: Even though a field’s total bounded acres will appear on Reports, such as this field’s Top Ten Report, the values are not included.)
-
- Reports in Decision will exclude these areas from Cost calculations.
- There were still expenses that were incurred in that area, so that’s why we strongly recommend using a Crop Loss Polygon with a value of “1” or greater.
- Reports in Decision will exclude these areas from Cost calculations.
How it affects Premier Precision:
- This will behave the same as scenario 1, above.
KEY Takeaways:
- You need to think about your P & K strategy for your fields when assigning a Crop Loss Polygon, as the PRem and KRem values will pull into Precision. These values will then be used in any Equations using a yield file.
- Areas with 0 or None yield data will not report cost data.
- When running queries, there are two ways to eliminate these areas that have a yield assigned as “1” or greater is to:
-
- Set the Min. Yield to a value that would exclude that data.
- Add Seed Variety as a variable in order to be able to filter out the Crop Loss data from the rest of your data .
- Set the Min. Yield to a value that would exclude that data.
