(Clique aqui para a tradução em português)
Welcome to the December 2023 release notes, covering the final product release of the year. In the spirit of the season, while we may not be Santa Claus, we do have some product news for you to unwrap. We’re excited to launch Leaf Input Validator (more on that below), as well as a few improvements to how operation units and invalid field boundaries can be handled. So take a look under the ‘Leaf-y’ Christmas tree with us and let's unwrap these new features:
🔍 Introducing Input Validator
2.136.0
We are excited to introduce Leaf Input Validator: a new, automated way to match inconsistent inputs from machine data to inputs from leading input databases including CDMS and Agrian. Input Validator helps you structure input data in two main ways:
-
From the start: a type to search API that links to a product list, cross-associated with the leading product databases in the industry. This allows input names to be entered correctly before an operation happens.
-
Retroactively: For historical data, or when input names are manually entered, Leaf’s validation model matches the input used with known inputs sourced from leading input databases. Associations can be created, removed, and updated on an account or user level, which gives users a customized experience, and Leaf’s validation model uses these adjustments to improve predictions further.
🪄 Automatically fix invalid field boundaries
2.136.0
Ever wished for a quick fix to just handle problematic invalid geometries? If so, your wish is granted with our new automaticFixBoundary configuration! If set to true, the configuration will attempt to correct invalid geometries received from providers via the Field Boundary Management service. The default value is false.
To identify if the geometry was automatically fixed, a new property will be available in the boundary response: "fixStatus": "FIXED". If it didn’t work, the fixStatus will return as “FAILED”. This property will be available for ‘Get all boundaries from a Field’, ‘Get active boundary from a Field’, and ‘Get a Boundary’ endpoints.
📏 Choose your preferred units of measure for machine data
2.136.0
'Tis the season…for unit choices! The new configuration ‘unitMeasurement’ gives you the freedom to choose the system of output units for Machine Files, Field Operations summaries and GeoJSONs (standardGeoJSON and filteredGeoJSON).
You can select METRIC or IMPERIAL at the API owner level or LeafUser level. The default unit of measure is DEFAULT which is based on the machine settings. If your customer’s data isn’t in the unit you’ve specified, we’ll take care of the translation work for you and ensure that all of the output of Leaf is in your chosen units.
Find unitMeasurement configuration
View units of measurement doc
Have questions or thoughts? Reach out to us at help@withleaf.io.
Otherwise, from all of us here at Leaf, we wish you a Merry Christmas and a Happy New Year! We’re excited to keep moving the industry forward with you in 2024.
