For customers that use R in their statistical modeling work, this R package helps get you up and running with our APIs with minimal integration effort. There is a function for each of our most regularly used APIs.

Note: These functions will only return metric units

Note: Prior to installation you will need a working installation of R.

Note: You will need to have the devtools library installed in R. Consult documentation if necessary.

This package can be installed directly from GitHub with the following command:

devtools::install_github("aWhereAPI/aWhere-R-Library")

1. Download this Github repo and keep the aWhere-R-Library-master folder somewhere useful on your computer, such as your Desktop or My Documents.

2. Set the Working Path in R to the location that contains the aWhere-R-Library-master folder. If you placed it on your Desktop the working directory would be something like C:\Users\USERNAME\Desktop. In R, this command is:

   • setwd("C:\Users\USERNAME\Desktop")

3. Run the following set of commands to install and add the library to your environment:

   • library(devtools)
   • install("aWhere-R-Library-master")
   • library(aWhereAPI)

In order to use any of the functions in this package, or the APIs in general, you will need API credentials provided by aWhere. These keys are used to generate an Access Token, which is then passed to each API to authenticate the request. This R package will handle token generation and usage automatically, but you will need to get API keys first.

To get API keys, follow these instructions at the aWhere Developer Community. Note that normally the API Key and Secret are made up of random characters.

Prior to using of the any other functions, you'll need to use get_token() function to generate a token. Pass the API Key and API Secret from aWhere as the two parameters to this function. For example:

get_token("JFKL24JF290FJSKAFDF","jf0afsd9af0a") 

You could also save the key and secret as variables. This function saves the token to a direct child of the base environment for use by any other aWhere function.

An alternative approach is to save your credentials to an external text file and use the load_credentials() function to load them into the environment and generate a token.

First, create a text file on your computer. Enter your API Key on the first line, and your Secret on the second, then press return/enter to create an empty third line. Save the file and note the complete path to it. For example, this might be C:\Users\USERNAME\Desktop\credentials.txt.

In R, supply the path to the credentials file to the function:

load_credentials("C:\Users\USERNAME\Desktop\credentials.txt")

This function invokes get_token() so no further work is needed to generate an Access Token.

Contents

• Field Location
  • Create a Field
  • Get Field Information
  • Update a Field
• Plantings
  • Create a Planting
  • Get a Planting
  • Update a Planting
  • Delete a Planting
• Weather
  • Observations (Daily History)
  • Forecast
  • Norms
  • Current Conditions
• Agronomics
  • Agronomic Values (Daily History)
  • Norms

By default, aWhere's APIs use Field Locations to reference the locations you wish to request data for. This is most common for tracking agricultural values over a growing season. Learn more at the aWhere Developer Community.

Use this function to create a Field Location in the aWhere Platform. You'll use the ID for this field when referencing the location in other functions. API Documentation

create_field(field_id, latitude, longitude, farm_id, field_name, acres)

• field (character)
  • An ID you use to reference the field location in all other functions.
  • Can be any combination of letters, numbers, dashes, and underscores up to 50 characters
  • Required
• latitude (numeric)
  • The latitude of the locations' centroid, in decimal notation
  • Required
• longitude (numeric)
  • The longitude of the location's centroid, in decimal notation
  • Required
• farm_id (character)
  • An ID that references the farm or entity that owns or runs the field location.
  • Can be any combination of letters, numbers, dashes, and underscores up to 50 characters
  • Required
• field_name (character)
  • A name for the field
  • Can be any combination of letters, numbers, dashes, underscores, and spaces
  • Optional
• acres (numeric)
  • The size of the location in acres
  • Optional, but may be required by your contract with aWhere

create_field("field456","40.8282","-100.5795","farmA","Some Field Location","100")

This function will return the field information saved in the aWhere Platform. API Documentation

get_fields(field_id)

• field_id (character)
  • The ID you used when creating the field location.
  • Required

get_fields('field123')

If you want to change certain properties about the Field Location, use this function. Note that at this time only the name or farm ID can be changed. API Documentation

update_field(field_id, variable_search, value_search, variable_update, value_update)

• field_id (character)
  • The ID you used when creating the field location.
  • Required
• variable_search (character)
  • Acceptable values are "name" or "farmId"
  • Required
• value_search (character)
  • If the variableToSearch matches this value, then the next property will be changed. Otherwise no update will happen.
  • Required
• variable_update (character)
  • Acceptable values are "name" or "farmId"
  • Practically, this will usually match variableToSearch, but you could opt to change one property only if the other matches valueToSearch
  • Required
• value_update (character)
  • The value to use for variableToChange
  • Required

This example will change the farmId to "TestFarmA" only if it current matches "ABC":

update_field('fieldId', 'ABC', 'farmId', 'TestFarmA')

This example will change the name of the field only if the farm ID matches "TestFarmA":

update_field('fieldId', 'TestFarmA', 'name', 'Primary Test Farm')

To delete a Field Location created with create_field(). API Documentation

delete_field(field_id, variable_search, value_search, variable_update, value_update)

• field_id (character)
  • The ID you used when creating the field location.
  • Required

delete_field('fieldId')

Whereas Field Locations define a physical location, Planting records record information about the crop and growing season. They are used when automatically calculating agronomic values since the start of a growing season. Learn more at the aWhere Developer Community.

Use this function to create a Planting for a Field Location. API Documentation

create_planting(field_id, crop, planting_date, proj_yield_amount, proj_yield_units, proj_harvest_date, yield_amount, yield_units, harvest_date) 

• field_id (character)
  • The ID you used when creating the field location.
  • Required
• crop (character)
  • The ID or short-hand code for the crop that is planted in the field
  • The ID can be retrieved from the Crops API
  • Short-hand code would be the generic name of the crop. Current options include:
    • corn | wheat | barley | canola | cotton | sugarbeet | sunflower
  • Required
• planting_date (character)
  • The date the crop was planted in the field
  • Format is YYYY-MM-DD
  • Required
• proj_yield_amount (numeric)
  • A number representing the expected yield.
  • Optional
• proj_yield_units (character)
  • The units associated with proj_yield_amount such as "bushels"
  • Optional, unless proj_yield_amount is supplied.
• proj_harvest_date (character)
  • The date the crop is expected to be harvested
  • Format is YYYY-MM-DD
  • Optional
• yield_amount (numeric)
  • A number representing the actual yield
  • Optional
• yield_units (character)
  • The units associated with yield_amount, such as "bushels"
  • Optional, unless amount is supplied
• harvest_date (character)
  • The date the field was actually harvested
  • Format is YYYY-MM-DD
  • Optional

create_planting('field123', 'corn', '2015-07-01')

Use this function to retrieve information about the planting. API Documentation

get_planting(field_id, planting_id, current)

• field_id (character)
  • The ID you used when creating the field location.
  • Optional: If not supplied then all plantings in the account are returned.
• planting_id (numeric)
  • The Planting ID as set by the aWhere platform
  • Optional: If not supplied but a field_id is, then all plantings for that field_id are returned
• current (boolean)
  • Whether to return only the current (most recent) planting
  • Optional

This example returns the most current (most recent) planting for field123:

get_planting('field123','',T)

Use this function to update the details about a Planting record. Note that once a planting is created the crop information cannot be changed (delete a the Planting record and create a new one instead). API Documentation

update_planting(field_id, crop, planting_date, proj_yield_amount, proj_yield_units, proj_harvest_date, yield_amount, yield_units, harvest_date)

• field_id (character)
  • The ID you used when creating the field location.
  • Required
• planting_id (numeric)
  • The Planting ID provided by the aWhere platform
  • This cannot be changed
  • Required
• planting_date (character)
  • The date the crop was planted in the field
  • Format is YYYY-MM-DD
  • Required
• proj_yield_amount (numeric)
  • A number representing the expected yield.
  • Optional
• proj_yield_units (character)
  • The units associated with proj_yield_amount such as "bushels"
  • Optional, unless proj_yield_amount is supplied.
• proj_harvest_date (character)
  • The date the crop is expected to be harvested
  • Format is YYYY-MM-DD
  • Optional
• yield_amount (numeric)
  • A number representing the actual yield
  • Optional
• yieldUnits (character)
  • The units associated with yield_amount, such as "bushels"
  • Optional, unless yield_amount is supplied
• harvest_date (character)
  • The date the field was actually harvested
  • Format is YYYY-MM-DD
  • Optional

If you want to keep your planting records clean for reporting and historical tracking purposes you can delete errant or incorrect plantings using this function. API Documentation

delete_planting(field_id, planting_id)

• field_id (character)
  • The ID you used when creating the field location.
  • Required
• planting_id (numeric)
  • The Planting ID provided by the aWhere platform
  • Required

delete_planting("field123", 32481941)

If you want to keep your list of active fields clean or inadvertently created a field, you can use this function. API Documentation

delete_planting(field_id)

• field_id (character)
  • The ID you used when creating the field location.
  • Required

delete_planting("field123")

The aWhere Platform provides agriculturally relevant weather data globally. There are two approaches to retrieving weather data for a location: either use the Field Location ID created with the functions above, or you can request weather data by latitude-longitude. Either is acceptable depending on the terms of your agreement with aWhere. If you intend to use aWhere's modeling capabilities in the future, you should create Field Locations and Plantings.

All weather data requests are requested point by point. There is not a way to download regional data in a single API call. Use the batch jobs system when requesting a large amount of data (e.g., many hundreds or thousands of points).

Learn more about the weather data we provide and our Weather Data APIs at the aWhere Developer Community.

This function uses the Observations API to retrieve observed weather data for any given day. By default, you can request daily data from up to 30 months ago. For data beyond that, use the Norms API (function below) to calculate long-term norms. Or, speak with your aWhere representative for access to more of the daily data archive. API Documentation

This function uses the Field Location ID to reference a location:

daily_observed_fields(field_id, day_start, day_end)

This function uses just a latitude-longitude (no Field Location required):

daily_observed_latlng(latitude, longitude, day_start, day_end)

• field_id (character)
  • The ID you used when creating the field location.
  • Required (when using the Fields approach)
• latitude and longitude (numerics)
  • The geolocation for which you want weather data
  • Required (when not using the Fields approach)
• day_start (character)
  • The starting date of a range of dates for which you want weather data
  • Alternatively, if you only want data for a single date, enter that date here
  • If not supplied, the API defaults to returning the last week of data
  • Format is YYYY-MM-DD and the date must fall before today
  • Optional
• day_end (character)
  • The ending date of a range of dates for which you want weather data.
  • If not supplied, but a day_start is, then the API returns data only for a single day
  • Format is YYYY-MM-DD and the date must fall before today and after day_start
  • Optional

Return a single day of data for a Field Location ID:

daily_observed_fields("field123", "2015-07-01")

Return two weeks of data for a geolocation:

daily_observed_latlng('39.8282', '-98.5795', '2015-07-01','2015-07-14')

Retrieve the forecast for today plus up to the next 8 days with this function. The forecast is available at multiple temporal resolutions - in 1, 2, 3, 4, 6, 8, 12, or 24-hour summary blocks. API Documentation

This function uses the Field Location ID to reference a location:

forecasts_fields(field_id, day_start, day_end, block_size)

This function uses just a latitude-longitude (no Field Location required):

forecasts_latlng(latitude, longitude, day_start, day_end, block_size)

• field_id (character)
  • The ID you used when creating the field location.
  • Required (when using the Fields approach)
• latitude and longitude (numerics)
  • The geolocation for which you want weather data
  • Required (when not using the Fields approach)
• day_start (character)
  • The starting date of a range of dates for which you want forecast data
  • Alternatively, if you only want data for a single date, enter that date here
  • If not supplied, the API defaults to today and the next seven days of data
  • Format is YYYY-MM-DD and the date must be equal to today or any of the next seven days
  • Optional
• day_end (character)
  • The ending date of a range of dates for which you want weather data.
  • If not supplied, but a day_start is, then the API returns data only for a single day
  • Format is YYYY-MM-DD and the date must fall after today and after day_start
  • Optional
• block_size (numeric)
  • The number of forecast hours to roll into a single forecast block
  • Options are 1, 2, 3, 4, 6, 8, 12, and 24
  • Default is 1 (hourly forecast)
  • Optional

Return a single day of data for a Field Location ID (hourly resolution)

forecasts_fields("field123", "2016-02-29")

Return the daily forecast for the next three days, requested for a geolocation:

forecasts_latlng('39.8282', '-98.5795', '2016-02-29','2016-03-02', 24)

The Weather Norms API allows you to offload the calculation of multi-year averages for any days of the year across any number of years for which we have data (minimum 3). This eliminates the need, most of the time, to download years and years of daily data just to calculate averages. The results also include the standard deviation for each average. API Documentation

This function uses the Field Location ID to reference a location:

weather_norms_fields(field_id, monthday_start, monthday_end, year_start, year_end, exclude_years) 

This function uses just a latitude-longitude (no Field Location required):

weather_norms_latlng(latitude, longitude, monthday_start, monthday_end, year_start, year_end, exclude_years)

• field_id (character)
  • The ID you used when creating the field location.
  • Required (when using the Fields approach)
• latitude and longitude (numerics)
  • The geolocation for which you want weather data
  • Required (when not using the Fields approach)
• monthday_start (character)
  • The month and day of the first day in a range for which you want norms.
  • Alternatively, if you only want data for a single date, enter that date here
  • Format is MM-DD
  • Required
• monthday_end (character)
  • The month and day of the last day in the range.
  • If not supplied, but a monthday_start is, then the API returns data only for a single day
  • Format is MM-DD
  • Optional
• year_start (character)
  • The first of a range of years over which to calculate norms (inclusive)
  • Note: a minimum of three years is required
  • Use a four-digit year (YYYY)
  • Optional; if not used, the API defaults to a 10-year norm
• year_end (character)
  • The last of a range of years over which to calculate norms (inclusive)
  • Note: a minimum of three years is required
  • Use a four-digit year (YYYY)
  • Optional:
    • If year_start is used then this is required
    • if not used, the API defaults to a 10-year norm
• exclude_years (vector of numerics)
  • A vector of years that you don't want included in the average
  • Note: a minimum of three years is required even after years are excluded
  • Use four-digit years (YYYY)
  • Optional

weather_norms_latlng('39.8282', '-98.5795','07-01','07-31','2010','2015')

The Current Conditions API returns a snapshot of area weather for a location using recent data from the nearest available station. While the data is QA'd before delivery, this service does not do the same advanced processing or interpolation as Daily Observed data. API Documentation

This function uses the Field Location ID to reference a location:

current_conditions_fields(field_id, sources)

This function uses just a latitude-longitude (no Field Location required):

current_conditions_latlng(latitude, longitude, sources)

• field_id (character)
  • The ID you used when creating the field location.
  • Required (when using the Fields approach)
• latitude and longitude (numerics)
  • The geolocation for which you want weather data
  • Required (when not using the Fields approach)
• sources (character)
  • Filters what kind of stations to use, as different station networks have different standards for quality and reporting
  • Options are:
    • metar = METAR stations are the National Weather Service stations commonly found at airports
    • mesonet = MESONET stations are typically high-quality stations maintained by academic or other highly-attentive organizations
    • pws = Personal Weather Stations are typically good quality but do not have the same guarantees as other networks
    • metar-mesonet = select from either METAR or MESONET stations
    • all = Use all available stations
  • Default is all
  • Optional

This example excludes personal weather stations and returns the data from nearest METAR or MESONET station:

current_conditions_latlng('39.8282', '-98.5795', 'metar-mesonet')

aWhere provides a rich set of agronomic values that adds deeper layers of insight on top of weather data alone. These functions provide quick access to derived values like GDD or PET, and the long-term norms for each value. Like the Weather APIs there are two approaches to retrieving weather data for a location: either use the Field Location ID created with the functions above, or you can request weather data by latitude-longitude. Either is acceptable depending on the terms of your agreement with aWhere. If you intend to use aWhere's modeling capabilities in the future, you should create Field Locations and Plantings.

All weather data requests are requested point by point. There is not a way to download regional data in a single API call. Use the batch jobs system when requesting a large amount of data (e.g., many hundreds or thousands of points).

Learn more at the aWhere Developer Community

Agronomic Values are calculated numbers that can be used to show the agronomic status of a field or crop. The aWhere platform can calculate GDD (using a variety of different equations), PET (using the Penman-Monteith Equation), P/PET, and accumulated precipitation, accumulated GDD, accumulated PET, and P/PET over a range of days. API Documentation

This function uses the Field Location ID to reference a location:

agronomic_values_fields(field_id, day_start, day_end, accumulation_start_date, gdd_method, gdd_base_temp, gdd_min_boundary, gdd_max_boundary) 

This function uses just a latitude-longitude (no Field Location required):

agronomic_values_latlng(field_id, day_start, day_end, accumulation_start_date, gdd_method, gdd_base_temp, gdd_min_boundary, gdd_max_boundary) 

• field_id (character)
  • The ID you used when creating the field location.
  • Required (when using the Fields approach)
• latitude and longitude (numerics)
  • The geolocation for which you want weather data
  • Required (when not using the Fields approach)
• day_start (character)
  • The starting date of a range of dates for which you want agronomic values
  • Alternatively, if you only want data for a single date, enter that date here
  • If not supplied, the API defaults to returning the last week of data
  • Format is YYYY-MM-DD and the date must fall before today
  • Optional
• day_end (character)
  • The ending date of a range of dates for which you want data.
  • If not supplied, but a day_start is, then the API returns data only for a single day
  • Format is YYYY-MM-DD and the date must fall before today and after day_start
  • Optional
• accumulation_start_date (character)
  • If you want the accumulations to start counting from a date before day_start enter that date here
  • Format is YYYY-MM-DD. The date given must fall before day_start, and cannot be more than a year before the current date.
  • Optional
• gdd_method (character)
  • Which GDD equation to use
  • Options are standard, modifiedstandard, min-temp-cap, min-temp-constant
  • See documentation on selecting and configuring a GDD equation
  • Optional
• gdd_base_temp (numeric)
  • The base temp to use with the GDD equation
  • Optional
• gdd_min_boundary (numeric)
  • The lower boundary value for the GDD equation (if used)
  • Optional
• gdd_max_boundary (numeric)
  • The upper boundary value for the GDD equation (if used)
  • Optional

agronomic_values_latlng('39.8282', '-98.5795','2015-07-01','2015-07-31','2015-06-01','modifiedstandard','10','10','30')

The Agronomic Norms API returns the long-term normals for the agronomic values on any given set of days across any range of years for which we have data. This allows you to calculate the desired averages without having to download huge data sets. API Documentation.

This function uses the Field Location ID to reference a location:

agronomic_norms_fields(field_id, monthday_start, monthday_end, year_start, year_end, exclude_years, accumulation_start_date, gdd_method, gdd_base_temp, gdd_min_boundary, gdd_max_boundary) 

This function uses just a latitude-longitude (no Field Location required):

agronomic_norms_latlng(latitude, longitude, monthday_start, monthday_end, year_start, year_end, exclude_years, accumulation_start_date, gdd_method, gdd_base_temp, gdd_min_boundary, gdd_max_boundary)

• field_id (character)
  • The ID you used when creating the field location.
  • Required (when using the Fields approach)
• latitude and longitude (numerics)
  • The geolocation for which you want weather data
  • Required (when not using the Fields approach)
• monthday_start (character)
  • The month and day of the first day in a range for which you want norms.
  • Alternatively, if you only want data for a single date, enter that date here
  • Format is MM-DD
  • Required
• monthday_end (character)
  • The month and day of the last day in the range.
  • If not supplied, but a monthday_start is, then the API returns data only for a single day
  • Format is MM-DD
  • Optional
• year_start (character)
  • The first of a range of years over which to calculate norms (inclusive)
  • Note: a minimum of three years is required
  • Use a four-digit year (YYYY)
  • Optional; if not used, the API defaults to a 10-year norm
• year_end (character)
  • The last of a range of years over which to calculate norms (inclusive)
  • Note: a minimum of three years is required
  • Use a four-digit year (YYYY)
  • Optional:
    • If year_start is used then this is required
    • if not used, the API defaults to a 10-year norm
• exclude_years (character)
  • A comma-separated list of years that you don't want included in the average
  • Note: a minimum of three years is required even after years are excluded
  • Use four-digit years (YYYY)
  • Optional
• gdd_method (character)
  • Which GDD equation to use
  • Options are standard, modifiedstandard, min-temp-cap, min-temp-constant
  • Optional
• gdd_base_temp (numeric)
  • The base temp to use with the GDD equation
  • Optional
• gdd_min_boundary (numeric)
  • The lower boundary value for the GDD equation (if used)
  • Optional
• gdd_max_boundary (numeric)
  • The upper boundary value for the GDD equation (if used)
  • Optional

agronomic_norms_latlng('39.8282', '-98.5795','07-01','07-31','2010','2015')