Crop Growth

last updated 1/4/19

The growth models combine user-provided information with the ClearAg field weather and soil data to provide past, current, and projected plant growth stage information specific to a particular crop planted on a specific field.

The required parameters will vary depending on whether coordinates are provided or Accounts API integration is used. For clients not using the Accounts API, required and optional parameters are listed under the “location-based” column within the Request Parameters tables. For required and optional parameters when utilizing the Accounts API, please refer to the information contained in the “Accounts API Integration” column. When utilizing the Accounts API, field, growth, activity, and feedback information present in the system will be used where necessary. The Accounts API integration will automatically pre-populate client data where applicable.

For those not currently using the Accounts API, please contact your Iteris account representative for details.

Multiple data center regions are available to meet users’ legal and performance needs. Currently, data centers exist within the United States (ag.us.clearapis.com) and the European Union (ag.eu.clearapis.com). Account and related information such as fields and growths are not shared between these regions. Data resolution and availability also vary by region, and each region requires a unique set of credentials. Please contact your account representative for account creation, data segregation, and data coverage information.

Please note that API responses are currently only provided in English.

Iteris requires the use of https when working within the ClearAg APIs.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

maturity_group,
relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

name

string

no

Unique name to assign to the growth. Default is "barley."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Barley Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Barley Growth Modify Feedback - v1.0

The Barley Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Barley Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Barley Growth with GDD Envelope - v1.1

The Barley Growth with GDD Envelope service provides spring barley growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

field_id

string

yes

ID of field on which to create the growth.

start_date

string

yes

Start time of the model, formatted either as a date string (YYYY-MM-DD) or an epoch timestamp. (Note that this is stored only as a timestamp in the database.) Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

yes

Subclass of bermuda turfgrass. Currently, only "generic" is supported.

name

string

no

Unique name to assign to the growth. Default is "turfgrass bermuda."

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

ID of target growth to modify.

start_date

string

no

Start time of the model, formatted either as a date string (YYYY-MM-DD) or an epoch timestamp. (Note that this is stored only as a timestamp in the database.) Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

no

Subclass of bermuda turfgrass. Currently, only "generic" is supported.

name

string

no

Unique name to assign to the growth.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

Response Object

Example Request

Example Response

true

Bermuda Turfgrass Growth - v1.0

The Bermuda Turfgrass Growth endpoint allows users to simulate dormancy of bermuda turfgrass and determine when it is expected to be fully dormant, fully active, and in a transition phase between these two.

Request Parameters

User-provided latitude and longitude coordinates in decimal degrees. Users are allowed a maximum of five coordinates,1 formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

start_date

string

yes

—

Start time of the model, formatted either as a date string (YYYY-MM-DD) or an epoch timestamp. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

variety

string

yes

—

Subclass of bermuda turfgrass. Currently, only "generic" is supported.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Growth ID provided by the Bermuda Turfgrass Growth Creation endpoint.

1 Additional coordinates are not counted against a client’s account.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

air_temp_max

Maximum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

air_temp_min

Minimum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. The output is "n/a" if the crop is somewhere between the previous growth stage and the next growth stage. Note that due to the perennial nature of turfgrass, the same stages can be reached multiple times in the simulation.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop was planted or the date
of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," and "medium." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "medium" relative maturity are expected to mature relatively slowly. Default is "medium."

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "canola."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values include "early," "medium-early," and "medium." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "medium" relative maturity are expected to mature relatively slowly. Default is "medium."

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

no

Epoch timestamp valid near the time that the crop was planted or the date
of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," and "medium." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "medium" relative maturity are expected to mature relatively slowly. Default is "medium."

growth_id

string

yes

Growth ID provided by and used with the Accounts API. This ID is given when a growth is successfully modified on a field in the Accounts API.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," and "medium." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "medium" relative maturity are expected to mature relatively slowly. Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Canola Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Canola Growth Modify Feedback - v1.0

The Canola Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Canola Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Canola Growth with GDD Envelope - v1.1

The Canola Growth with GDD Envelope service provides canola growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," and "medium." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "medium" relative maturity are expected to mature relatively slowly. Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

integer

no

Classification indicating how early a variety matures. Valid values range from 70 to 130, with lower values indicating an "early" relative maturity and higher values indicating a "late" relative maturity. Default is 100.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "corn."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Coded value representing the specific variety of crop planted.

plant_type

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values range from 70 to 130, with lower values indicating an "early" relative maturity and higher values indicating a "late" relative maturity. Default is 100.

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

growth_id

string

yes

Growth ID provided by and used with the Accounts API. This ID is given when a growth is successfully modified on a field in the Accounts API.

relative_maturity

integer

no

Classification indicating how early a variety matures. Valid values range from 70 to 130, with lower values indicating an "early" relative maturity and higher values indicating a "late" relative maturity. Default is 100.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

integer

no

—

Classification indicating how early a variety matures. Valid values range from 70 to 130, with lower values indicating an "early" relative maturity and higher values indicating a "late" relative maturity. Default is 100.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Corn Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Corn Growth Modify Feedback - v1.0

The Corn Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Corn Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Corn Growth with GDD Envelope - v1.1

The Corn Growth with GDD Envelope service provides corn growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

integer

no

—

Classification indicating how early a variety matures. Valid values range from 70 to 130, with lower values indicating an "early" relative maturity and higher values indicating a "late" relative maturity. Default is 100.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Default is "medium."

plant_depth

float

no

The depth in centimeters that the crop was planted. Plant depth must be a float between 0.1 and 4.9 cm. If no value is provided, the default plant depth is 3.5.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "cotton."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Default is "medium."

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

growth_id

string

yes

Growth ID provided by and used with the Accounts API. This ID is given when a growth is successfully modified on a field in the Accounts API.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Default is "medium."

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Cotton Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Cotton Growth Modify Feedback - v1.0

The Cotton Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Cotton Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Cotton Growth with GDD Envelope - v1.1

The Cotton Growth with GDD Envelope service provides cotton growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

field_id

string

yes

ID of field on which to create the growth.

plant_date,
emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

yes

Subclass of peanut. Note that either variety name or ID may be provided, and will be represented only by its ID in the database. Please refer to the Variety Enumerations section of the Appendix for the listing of supported varieties.

plant_depth

float

no

The depth (in cm) that the crop was planted. Valid values range from 0.1 to 10.0 cm. Default is 5.0.

name

string

no

Unique name to assign to the growth. Default is "peanut."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

ID of target growth to modify.

plant_date,
emergence_date

timestamp

no

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

no

Subclass of peanut. Note that either variety name or ID may be provided, and will be represented only by its ID in the database. Please refer to the Variety Enumerations section of the Appendix for the listing of supported varieties.

plant_depth

float

no

The depth (in cm) that the crop was planted. Valid values range from 0.1 to 10.0 cm.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates,1 formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

variety

string

yes

—

Subclass of peanut. Note that either variety name or ID may be provided. Please refer to the Variety Enumerations section of the Appendix for the listing of supported varieties.

plant_depth

float

no

—

The depth (in cm) that the crop was planted. Valid values range from 0.1 to 10.0 cm. Default is 5.0.

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Growth ID provided by the Peanut Growth Creation endpoint.

1 Additional coordinates are not counted against a client’s account.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from planting or emergence date, including the current date.

air_temp_max

Maximum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

air_temp_min

Minimum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

gdd

Growing degree days accumulated on the current date.

last_reproductive_stage

The last known reproductive stage.

last_stage

The last known growth stage. Contains vegetative stages until the beginning of flowering is reached, after which only new reproductive stages are provided.

last_vegetative_stage

The last known vegetative stage.

new_reproductive_stage

The crop may have entered a new reproductive stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous reproductive stage and the next reproductive stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous growth stage and the next growth stage. Contains vegetative stages until the beginning of flowering is reached, after which only new reproductive stages are provided.

new_vegetative_stage

The crop may have entered a new vegetative stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous vegetative stage and the next vegetative stage.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

field_id

string

yes

ID of field on which to create the growth.

plant_date,
emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

yes

Subclass of potato. Note that either variety name or ID may be provided, and will be represented only by its ID in the database. Please refer to the Variety Enumerations section of the Appendix for the listing of supported varieties.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "potato."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

Request Parameters

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp when the growth was created. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

emergence_date

Epoch timestamp when emergence was reached. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

ID of crop growth queried.

harvest_date

Epoch timestamp when harvest began. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Epoch timestamp when the crop was planted. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

ID of target growth to modify.

plant_date,
emergence_date

timestamp

no

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

no

Subclass of potato. Note that either variety name or ID may be provided, and will be represented only by its ID in the database. Please refer to the Variety Enumerations section of the Appendix for the listing of supported varieties.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

variety

string

yes

—

Subclass of potato. Note that either variety name or ID may be provided. Please refer to the Variety Enumerations section of the Appendix for the listing of supported varieties.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "sorghum."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

growth_id

string

yes

Growth ID provided by and used with the Accounts API. This ID is given when a growth is successfully modified on a field in the Accounts API.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Sorghum Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Sorghum Growth Modify Feedback - v1.0

The Sorghum Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Sorghum Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

field_id

string

yes

Specifies ID of field to be updated.

plant_date,
emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

maturity_group,
relative_maturity

string

no

Classification indicating how early a variety matures. Valid values fall into the following range bins: 000.0 to 000.9, 00.0 to 00.9, and 0.0 to 10.9. Multi-zero range bins indicate the earliest maturities, with values near 10.9 indicating the latest maturities. Default is 3.0. Please note that if neither relative maturity nor maturity group are specified, the default value will be stored as relative maturity; if maturity group is specified, it will be stored as relative maturity.

plant_depth

float

no

The depth (in cm) that the crop was planted. Valid values range from 0.1 to 7.5 cm. Default is 3.5.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "soybean."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values fall into the following range bins: 000.0 to 000.9, 00.0 to 00.9, and 0.0 to 10.9. Multi-zero range bins indicate the earliest maturities, with values near 10.9 indicating the latest maturities. Default is 3.0.

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Growth ID provided by the Soybean Growth Creation endpoint. This ID is given when a growth is successfully created on a field.

plant_date,
emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

maturity_group,
relative_maturity

string

no

Classification indicating how early a variety matures. Valid values fall into the following range bins: 000.0 to 000.9, 00.0 to 00.9, and 0.0 to 10.9. Multi-zero range bins indicate the earliest maturities, with values near 10.9 indicating the latest maturities. Default is 3.0. Please note that if maturity group is specified, it will be stored as relative maturity.

plant_depth

float

no

The depth (in cm) that the crop was planted. Valid values range from 0.1 to 7.5 cm. Default is 3.5.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

maturity_group

string

no

—

Classification indicating how early a variety matures. Valid values fall into the following range bins: 000.0 to 000.9, 00.0 to 00.9, and 0.0 to 10.9. Multi-zero range bins indicate the earliest maturities, with values near 10.9 indicating the latest maturities. Default is 3.0.

plant_depth

float

no

—

The depth (in cm) that the crop was planted. Valid values range from 0.1 to 7.5 cm. Default is 3.5.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from planting or emergence date, including the current date.

air_temp_avg

Average daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

air_temp_max

Maximum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

air_temp_min

Minimum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_reproductive_stage

The last known reproductive stage.

last_stage

The last known growth stage. Contains vegetative stages until the beginning of flowering is reached, after which only new reproductive stages are provided.

last_vegetative_stage

The last known vegetative stage.

new_reproductive_stage

The crop may have entered a new reproductive stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous reproductive stage and the next reproductive stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous growth stage and the next growth stage. Contains vegetative stages until the beginning of flowering is reached, after which only new reproductive stages are provided.

new_vegetative_stage

The crop may have entered a new vegetative stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous vegetative stage and the next vegetative stage.

Soybean Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Soybean Growth Modify Feedback - v1.0

The Soybean Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Soybean Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Soybean Growth with GDD Envelope - v1.1

The Soybean Growth with GDD Envelope service provides soybean growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

maturity_group

string

no

—

Classification indicating how early a variety matures. Valid values fall into the following range bins: 000.0 to 000.9, 00.0 to 00.9, and 0.0 to 10.9. Multi-zero range bins indicate the earliest maturities, with values near 10.9 indicating the latest maturities. Default is 3.0.

plant_depth

float

no

—

The depth (in cm) that the crop was planted. Valid values range from 0.1 to 7.5 cm. Default is 3.5.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from planting or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_avg

Average daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

air_temp_max

Maximum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

air_temp_min

Minimum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_reproductive_stage

The last known reproductive stage.

last_stage

The last known growth stage. Contains vegetative stages until the beginning of flowering is reached, after which only new reproductive stages are provided.

last_vegetative_stage

The last known vegetative stage.

new_reproductive_stage

The crop may have entered a new reproductive stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous reproductive stage and the next reproductive stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous growth stage and the next growth stage. Contains vegetative stages until the beginning of flowering is reached, after which only new reproductive stages are provided.

new_vegetative_stage

The crop may have entered a new vegetative stage between the current date and the previous date. "n/a" if the crop is somewhere between the previous vegetative stage and the next vegetative stage.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "spring wheat."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

growth_id

string

yes

Growth ID provided by and used with the Accounts API. This ID is given when a growth is successfully modified on a field in the Accounts API.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

scale

string

no

no

Specifies which growth scale the response will display. Valid values include "feekes," "haun," and "zadoks." Default behavior is to utilize a unified scale and display the equivalent stages from all three scales in the response.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Spring Wheat Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Spring Wheat Growth Modify Feedback - v1.0

The Spring Wheat Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Spring Wheat Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Spring Wheat Growth with GDD Envelope - v1.1

The Spring Wheat Growth with GDD Envelope service provides spring wheat growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

scale

string

no

no

Specifies which growth scale the response will display. Valid values include "feekes," "haun," and "zadoks." Default behavior is to utilize a unified scale and display the equivalent stages from all three scales in the response.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

name

string

no

Unique name to assign to the growth. Default is "sugar beet."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Sugar Beet Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Sugar Beet Growth Modify Feedback - v1.0

The Sugar Beet Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Sugar Beet Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Sugar Beet Growth with GDD Envelope - v1.1

The Sugar Beet Growth with GDD Envelope service provides sugar beet growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

name

string

no

Unique name to assign to the growth. Default is "sunflower."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Sunflower Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Sunflower Growth Modify Feedback - v1.0

The Sunflower Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Sunflower Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

plant_depth

float

no

The depth in centimeters that the crop was planted. Plant depth must be a float between 0.1 and 10.0 cm. If no value is provided, the default plant depth is 5.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

string

no

Unique name to assign to the growth. Default is "winter wheat."

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

User ID provided by the Create User endpoint as a result of adding a new user to the user information database.

growth_id

string

yes

Specifies ID of crop growth to be queried from the user information
database, provided by the Create Growth endpoint.

Response Object (JSON)

Field

Description

acres

Areal size of the field in acres.

created

Epoch timestamp in seconds. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

field_id

Specifies ID of field to which crop growth data has been assigned.

field_name

Name of the field.

growth_id

Specifies ID of crop growth queried.

harvest_date

An epoch timestamp in seconds for which harvest has begun. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

irrigation_type

Represents whether or not the cropland utilizes pivot irrigation. Valid values: 0 is "false" and 1 is "true."

latitude

Latitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

longitude

Longitude coordinate near the center of the field in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field.

max_moisture_refill

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

name

Name of the growth.

plant_date

Approximate time at which the crop was planted.

plant_name

Name of the crop plant.

plant_type

Value representing the type of crop planted. (See the Plant Enumerations section of the Appendix for a listing of plant type IDs.)

plant_subtype

Enumeration value representing plant sub-type.

relative_maturity

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

seed_variety

Additional description or notes for the seed used.

subdrainage_type

Represents whether or not the cropland utilizes drainage tile. Valid values: 0 is "false" (default) and 1 is "true."

surface_drainage_quality

Represents field drainage effectiveness. Valid values: 0 is poor, 1 is average, and 2 is good.

previous_crop

Type ID of previously planted crop.

previous_harvest_date

Epoch time which previous crop was harvested. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

previous_yield

Yield of previous crop.

previous_yield_unit

Unit of measure for previous yield.

yield_goal

Yield target of current growth.

yield_goal_unit

Unit of measure for yield goal.

zone_map_id

Zone map ID to be used with this growth when utilizing zone management products. Value will be a UUID or null.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

plant_date, emergence_date

timestamp

yes

Epoch timestamp valid near the time that the crop reached emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

growth_id

string

yes

Growth ID provided by and used with the Accounts API. This ID is given when a growth is successfully modified on a field in the Accounts API.

relative_maturity

string

no

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

plant_depth

float

no

The depth in centimeters that the crop was planted. Plant depth must be a float between 0.1 and 10.0 cm. If no value is provided, the default plant depth is 5.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

Please note that winter wheat has a vernalization (cold) requirement that must be satisfied before floral initiation can occur. This requirement will not be met if winter temperatures do not get low enough, which means that the model will not go past the First Tiller stage.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

scale

string

no

no

Specifies which growth scale (feekes, haun, or zadoks) the response will display. Default behavior is to utilize a unified scale and display the equivalent stages from all three scales in the response.

plant_depth

float

no

—

The depth in centimeters that the crop was planted. Possible values range from 0.1 to 10.0 cm. The default is 5.0 cm.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Winter Wheat Growth Add Feedback - v1.0

By providing feedback relating to the growth stage estimates, Iteris will be able to make updates and adjustments to offer its users better results in the future. The given user providing feedback must have write privileges for the field in which the field growth belongs.

Additional information related to feedback timestamp, growth feedback, and feedback stage is available in the Appendix.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

start_override

boolean

no

When this is included, the corrector system will treat this feedback as meaning "the crop entered this stage on this date." In the absence of this parameter, the corrector will treat this feedback as meaning "the crop was observed in this stage on this date."

Example Response

Winter Wheat Growth Modify Feedback - v1.0

The Winter Wheat Growth Modify Feedback endpoint allows users to modify previously provided growth stage estimate feedback. The given user providing feedback must have write privileges for the field in which the field growth belongs. At least one modification must be provided.

Request Parameters

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

feedback_id

string

yes

A unique ID returned as a result from successfully adding feedback.

timestamp

integer

yes

An epoch timestamp in seconds representing the date for which the feedback applies. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris’ definition of Epoch/Unix timestamp.

stage

string

yes

Inform the system that on the given date, the plant has entered or is currently in the provided stage. Please refer to the Crop Growth Stages section of the Appendix for a listing of accepted growth stage IDs.

Example Request

Example Response

true

Winter Wheat Growth Delete Feedback - v1.0

This endpoint allows users to delete the previously provided growth stage estimate feedback. The given user deleting feedback must have write privileges for the field in which the field growth belongs.

Example Request

Example Response

true

Winter Wheat Growth with GDD Envelope - v1.1

The Winter Wheat Growth with GDD Envelope service provides winter wheat growth information in addition to GDD envelope data. GDD envelope calculation begins from either the current day, or the planted/emergence date, whichever is further in the future. The envelope is constructed by compiling the previous 10 years of weather data, and simulating the maximum and minimum GDD that would have accumulated within those 10 years for each date. The calculated minimum and maximum values are then added to the current start of calculation date AGDD going onwards to show range of possibilities.

Request Parameters

Parameter

Type

Location-based

Accounts API Integration

Description

app_id

string

yes

yes

API ID provided by Iteris.

app_key

string

yes

yes

API key provided by Iteris.

location

lat, lon coordinates

yes

—

User-provided latitude and longitude coordinates in decimal degrees. Please verify that latitude/longitude coordinates are over soil representative of your field. Users are allowed a maximum of five coordinates1, formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

plant_date,
emergence_date

timestamp

yes

—

Epoch timestamp valid near the time that the crop was planted or the date of emergence. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

relative_maturity

string

no

—

Classification indicating how early a variety matures. Valid values include "early," "medium-early," "medium," "medium-late," and "late." Crops that have an "early" relative maturity are expected to mature relatively fast, and crops having a "late" relative maturity are expected to mature relatively slowly. Default is "medium."

scale

string

no

no

Specifies which growth scale (feekes, haun, or zadoks) the response will display. Default behavior is to utilize a unified scale and display the equivalent stages from all three scales in the response.

plant_depth

float

no

—

The depth in centimeters that the crop was planted. Possible values range from 0.1 to 10.0 cm. The default is 5.0 cm.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by and used with the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Specifies the ID given when a growth is successfully added to a field using the create growth endpoint.

1 Additional coordinates are not counted against a client’s account, but will count as additional requests in the future.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

agdd

Aggregate growing degree days from plant or emergence date, including the current date.

agdd_envelope_max

Maximum observed AGDD of the past 10 years.

agdd_envelope_max_year

Year that the maximum AGDD value was observed.

agdd_envelope_min

Minimum observed AGDD of the past 10 years.

agdd_envelope_min_year

Year that the maximum AGDD value was observed.

air_temp_max

Maximum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

air_temp_min

Minimum daily air temperature valid for the current date. Obtained from historical, forecast, or climatological data, depending on the timeframe.

feedback_id

If this field is present, it indicates a confirmed or observed growth stage on the current date.

gdd

Growing degree days accumulated on the current date.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. If new_stage is n/a, the crop is somewhere between the previous growth stage and the next growth stage.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

field_id

string

yes

ID of field on which to create the growth.

start_date

string

yes

Start time of the model, formatted either as a date string (YYYY-MM-DD) or an epoch timestamp. (Note that this is stored only as a timestamp in the database.) Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

yes

Subclass of zoysia turfgrass. Currently, only "generic" is supported.

name

string

no

Unique name to assign to the growth. Default is "turfgrass zoysia."

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Default values are optimized to the soil composition, crop type, and crop growth stage, with typical values of around 50%. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. The default value is 0%, indicating recommended irrigation activities will try to not exceed field capacity. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

zone_map_id

string

no

The target zone map id must exist for the target field. This will be a UUID. If provided and growth creation is successful, the growth will be treated as "zone aware," enabling zone management features. This property cannot be mutated after a growth has been created.

Request Parameters

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

yes

ID of target growth to modify.

start_date

string

no

Start time of the model, formatted either as a date string (YYYY-MM-DD) or an epoch timestamp. (Note that this is stored only as a timestamp in the database.) Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

variety

string

no

Subclass of zoysia turfgrass. Currently, only "generic" is supported.

name

string

no

Unique name to assign to the growth.

max_moisture_ depletion

float

no

Desired driest state the soil is allowed to attain before an irrigation recommendation is triggered, expressed as percent depletion from field capacity to wilting point. Valid values range from 0% (indicating soil moisture should not be allowed to fall below field capacity) to 100% (soil moisture is allowed to reach the permanent wilting point, at which crop death will occur). Practical values typically range from 30 to 70%. Values are internally limited to be greater than the max_moisture_refill value.

max_moisture_refill

float

no

Desired maximum amount of refill to be provided by irrigation recommendations, expressed as percent depletion from field capacity to wilting point. Valid values range from –50% (an increase in the allowed maximum soil moisture) to 50% (a decrease in the allowed maximum soil moisture). Negative values represent refill amounts that exceed field capacity and are internally limited to the soil-specific saturation point.

Response Object

Example Request

Example Response

true

Zoysia Turfgrass Growth - v1.0

The Zoysia Turfgrass Growth endpoint allows users to simulate dormancy of zoysia turfgrass and determine when it is expected to be fully dormant, fully active, and in a transition phase between these two.

Request Parameters

User-provided latitude and longitude coordinates in decimal degrees. Users are allowed a maximum of five coordinates,1 formatted as "&location=[(<lat_1>,<lon_1>),(<lat_2>,<lon_2>)]."

start_date

string

yes

—

Start time of the model, formatted either as a date string (YYYY-MM-DD) or an epoch timestamp. Please refer to the Epoch/Unix Timestamp section of the Appendix for Iteris' definition of Epoch/Unix timestamp.

days

integer

yes

yes

Number of days for which to calculate results. Possible values range from 1 to 366.

variety

string

yes

—

Subclass of zoysia turfgrass. Currently, only "generic" is supported.

account_id

string

no

yes

Your Accounts API account ID.

user_id

string

no

yes

User ID provided by the Accounts API. The user must have privileges to view information for the field to which the target growth is assigned.

growth_id

string

no

yes

Growth ID provided by the Zoysia Turfgrass Growth Creation endpoint.

1 Additional coordinates are not counted against a client’s account.

Response Object (JSON)

Field

Description

attribution

Various model attributions.

air_temp_max

Maximum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

air_temp_min

Minimum daily air temperature in degrees Fahrenheit, which may be a historical, forecast, or climatological value, depending on the timeframe.

last_stage

The last known growth stage.

new_stage

The crop may have entered a new growth stage between the current date and the previous date. The output is "n/a" if the crop is somewhere between the previous growth stage and the next growth stage. Note that due to the perennial nature of turfgrass, the same stages can be reached multiple times in the simulation.