To enroll projects in the Nori marketplace and get an estimate on projections for NRTs, we require 20 years worth of historic data. Accurate and verifiable data is always preferable but we realize that oftentimes growers may not have all the data Nori is asking for. The Smart Defaults tool was developed to make things easier to automatically import the required data using publicly available data sets to produce a complete data set ready for running and NRT projection.
This feature is still in Beta which means we are only inviting a few select pilot participants to use it. We want an easier way for you to access this tool in the future, but for now you will need to use our URL workaround. Follow these steps to get back to Smart Defaults from our Nori account.
Click on the project you’d like to use / edit Smart Defaults for
In the URL in your browser window, replace the words land-management with smart-defaults
That should get you back to the Smart Defaults overview page that looks like this:
Wherever possible, Nori attempts to provide a complete set of records that you the Grower can then correct then in places where it’s hard or impossible to guess at how something was done, we simply ask.
Nori gathers data from publicly available repositories like regional norms for historical events based on where your project is located based on the boundaries of your fields. Today that’s what we do for crop rotation and fertilizer values which comes from the NASS Crop Layer Database.
Some information you, the grower, will be asked to provide based on your own knowledge of how this land was managed historically.
Based on your responses to the Smart Defaults prompts, you will see some placeholder defaults that you can review and make modifications. These values are derived from our quantification partner, COMET-Farm and are used in their tool for theoretical modeling.
When applying Smart Defaults, these default values will be imported to the INPUTS tab of your sheet as well as into your Field Records themselves field sets you had selected for import. These defaults can be further modified under the INPUTS tab of the sheet which would update the values in the individual Field Records across all fields where those defaults are applied. However, changes made in your individual Field Records will not update your defaults under the INPUTS tab and changes to the INPUTS tab will not update what you provided in the Smart Defaults tool.
If you are a Granular customer and have already imported records via our Granular Import tool, you will be directed to provide compatible classifications under the INPUTS tab. Those classifications and any edits you make to their default values will update your individual Field Records where data was imported from Granular but will not be accessible from the Smart Defaults tool.
These two features help create defaults but they do not update each other at this time. You can think of both the Granular Import tool and the Smart Defaults tool as separate, one way streets. Values will cascade down to your individual Field Records but changes made to your individual records will not update the INPUTS tab and changes to the INPUTS tab will not update your values under Smart Defaults, and if you are a Granular customer, changes you make to records imported from Granular will not update your records on your actual Granular account.
If you decide to use Smart Defaults again, the feature will remember for each activity the values you provided. That means if you run Smart Defaults again for new fields, you will be able to apply the same default values you already specified using this feature for all the same crops that were included in your crop rotations for the previous set of fields. Please note that if you are importing different defaults for different year ranges, Smart Defaults will remember the last set of defaults per crop but it will not remember the years in which they were applied or keep track of multiple default sets for the same crops across multiple years.
While Nori is not prescriptive as to when the right moment is to use this tool, there is a lot of flexibility available based on how the tool works. Generally, it is advised to use smart defaults at the end of your data entry (after current and future management operations have been entered).
You’ll see a series of check marks along the left side of the table next to the field names. By turning those on and off you can specify which fields you want to apply the defaults to which will be displayed as a reminder on subsequent prompts. This is meant to be a workaround for applying different defaults to different fields.
For all activities except crop rotation, you will be able to review what you last used as Smart Default values. You can change those values and import again to just override a single activity if you choose instead of doing the whole process over again. Note that you can also edit your defaults inside the Field Records Inputs tab which is where your data from Smart Defaults is populated.
We understand that for many events like applying fertilizer and tillage there are multiple events that can happen for a single crop in a single season. Currently this feature only supports a single event but we have multiple events as something on our current roadmap. For now, we are advising growers to specify the “main event” in all instances where more than one event occurred.
There are known issues with how Smart Defaults handles perennials that will limit their effectiveness for Growers that have perennials in crop profile. We will work to address these issues in future updates but may not support your specific management scenario in the current version.
Write something here that explains how it behaves differently that all other prompts and that this is to be expected.
This feature is in our backlog of things to support next.
This feature is in our backlog of things to support next.