Create Boundary using CLU Data
In AgVerdict NEXT, we have had the ability to load the USDA’s CLU ( Common land units) as a visible layer onto the map. In this release we now give users the ability to select a CLU, and convert it to a boundary for that location.
The system will automatically turn on the CLU layer and select the state that the land is located. THe user can always add additional states manually if needed.
The yellow outlines are the “CLU boundaries”. The user just needs to click within the boundary to select it.
Users can continue to select more CLU boundaries if the location they are trying to create the boundary for includes multiple CLU boundaries.
Once the desired boundaries are selected, just click save and the system will save the overall combined CLU boundaries into one.
TNS Enhancements
TNS threshold support in AgVerdict has been added for Midwest Laboratories and AgVise Laboratories. Backend improvements have also been made to better support the rollout of new labs.
Within the TNS Analysis page in Sampling, Boron is now listed as both a required and toxic element. For the required section – a proper Boron level is above the 100% line and is marked in green. For a toxic amount, the Boron is in red and should be below the 100% threshold.
Zone Enhancements
Online satellite imagery can now be downloaded. This is currently limited to Sentinel 2 L1C data.
To access, use the “Imagery” option during zone creation and select “Internet Download”. Perform a search with the Cloud Coverage settings and start/end date for the data you wish to access. For most data, we recommend starting at a 6 month time range and then expanding to a year+. Select the imagery and download. It will then be made available in the “Existing Data” selection for imagery zone creation.
Add Bill To & Ship To accounts per Location
Under the Field / Block / Sub Block locations in AgVerdict NEXT, we have added the ability to select a “Bill to” and “Ship to” account to associated to that location. This information is being stored so that in the future can be pulled up in Custom reports.
IMPORTANT: Currently this information is not used in the recommendation or order. The Account that is set under the Grower information will still be the account that is in the recommendations and flow into the order.
Addressed Issues
- Addressed issues with Saved email lists being updated between the iOS app and web. There will no longer be duplicate emails that display on the iOS app, as well as edits between the two will update as expected.
- We had an issue where the acres for a blend in a standalone Order were coming across incorrect into AgVance. We have resolved the issue and this is now working as expected.
- Addressed issue with duplication of a recommendation, when a user doesn’t select to include application details, the incorporation depth was left empty. This is now working as expected and now defaults to inches.