How to integrate with the Inventory module

Used to calculate an absolute value emissions factor for a crop.

Regrow’s Measure API utilizes the DNDC model, a scientifically validated framework for analyzing soil dynamics. This model evaluates nutrient cycling and variations in soil carbon levels to predict greenhouse gas (GHG) outcomes that arise from changes in agricultural practices. The Measure API is structured into different modules to cater to a variety of client needs.

The Inventory module calculates an absolute value of the emissions for a given time period (and associated with growing a crop on a field). Inventory is relevant for companies looking to understand their emissions impact. In these cases, customers are not quantifying carbon credits for verification or measuring a practice change, but rather measuring progress towards sustainability or net-0 goals.

The Measure API takes in your field location and field management data (crop info, tilling events, fertilizer data, etc.). The API combines your data with field-level weather, soil info, etc. Field management data includes a recent history of events, we recommend a minimum of 3 years history but more ideally 5 years of history, as well as the reporting period for which your GHG inventory is measured. 

Today, outcomes are not calculated according to a specified carbon protocol in order to generate scope-specific assets.

Steps to integrating with Measure API - Inventory module

Integration includes four phases: 

1. create a project
2. upload field data to the project 
3. submit projects for quantification 
4. receive project results

Create a Project

The first step is to create a project. A project is a grouping of fields that will be modeled together. Give your project a unique title that will help you remember and track the project. 

Upload field data to the project

The next step is to submit fields to the project. A project can have any number of fields, but it’s recommended to group fields with some commonality. For example, you may choose to add fields into the same project based on a region (such as a country or climate region), a crop type (such that all fields growing the same crop are in a single project), or a reporting time period (such as a crop year).

A field contains a collection of data grouped into cultivation cycles. Field data include:

• Field location (field boundaries, lat/long)
• Field conditions (soil data, if available and weather)
• Management events that happened on the field per cultivation cycle (such as crop planting/harvest, tillage, irrigation and nutrient management).

Every field must have historical management events. We require a minimum of 3 years of history but more ideally we recommend 5 years of history. And a field will also have a reporting period with management events. The reporting period is the cultivation cycle / period of time for which the GHG measurements will be taken. 

The DNDC model powering the Measure API is calibrated for specific farm management events, field locations and conditions. The table below outlines the relevant information used to model GHG outcomes. Not all data in the table is required, and some field management events listed below will not have occurred on every field and likewise should not be used.

Step 3: Finalize the Project

After all your fields have been added to your project, the project can be finalized. Finalizing a project indicates that all field data has been submitted and the project is ready for modeling. Once a project is finalized, DNDC simulations will begin.

Step 4: Retrieve Project Outcomes

After the project and outcomes have been modeled, including time for QA of the results, you will be alerted that you can retrieve results.