Determining Units of Measure

The slingshot API will return differing UOMs depending on the display which produced the file and the method of application being performed. File information is provided by the Job Data - Detail endpoint.

There are three specific formats which can be requested:

• BIN: The original As Applied zip file as the Field Computer produced it
• SHP: A zip file containing the shapefiles representing the As Applied data
• FMIS: A zip file containing extended XML and TAB suitable for Farm Manage Information Systems software

Additional file details may also be obtained by performing a call to the job data detail endpoint, https://api.ravenslingshot.com/jobdata/{fileid}.

SHP Format

To determine the UOM used, it is necessary to determine the file type being processed. There is multiple methods to identify which device produced a file. In both cases the first step is to perform a call to the Job Data - by file id endpoint to retrieve file details.

1. The response of the file detail endpoint includes in FieldComputer ID. If the access token has access to the field computer, an API call can be performed to Field Computers - by id to receive the DeviceType.

{
	"ID": "Test",
	"Name": "AgSYnc Sprayer #1",
	"DeviceType": "VIPER4PLUS",
	"Status": "Not In Job",
	"RemoteAccess": true,
	"WebAccess": true,
	"FieldHubID": "dsgd9346dgg046",
	"SoftwareVersion": "22.1.0.33",
	"LastReportDate": "2023-01-25T14:22:42Z"
}

2. The response of the file detail call will return one of 3 Job Types: a SprayerJob, YieldJob, or PlanterJob. Depending on the type, there will also be an element returned which is of the same name. Within this element there is an element named SoftwareVersion. The SoftwareVersion includes additional details of what type of device may have produced the file for example a response of VIPER4PLUS, 21.3.0.26, RAD 2.2 would indicate that a Viper4 had produced the file.

{
	"DeviceFileName": "TwoBinSingleProducts.jdp",
	"CreateDate": "2021-10-09T15:19:54Z",
	"UpdateDate": "2021-10-09-T15:20:45Z",
	"FieldComputer": "SomeTest",
	"Status": "CONVERSION_STATUS_SUCCESS",
	"JobType": "Sprayer",
	"SprayerJob": {
		"ID": "45033119",
		"JobName": "TwoBinSingleProducts",
		"FileName": "TwoBinSingleProducts.jdp",
		"StartDate": "2019-12-09T12:03:00",
		"EndDate": "2019-12-09T12:08:01",
		"SoftwareVersion": "VIPER4PLUS, 21.3.0.26, RAD 2.2",
		"AverageSpeed": "7.396066",
		"CustomerName": "Raven Innovation Campus - Raven Innovation Campus",
		"CustomerAddress": "12345 254th St., Baltic, South Dakota, 67890",
		"CustomerNumber": "783068"
	}
}

Epro and Vpro

Epro and Vpro files do not have a specified standard unit. Units can be in any format listed below:

US	Metric
Gallons / Acre	Liters / Ha
Ounces /Acre	Milliliters / Ha
Ounces / Gallon	Milliliters / Liter
Pounds / Acre	Kilograms / Ha

Viper 4 and CRX

When a file is returned from either of these models, it is necessary to determine the ProductType being applied. As mentioned above under Device Identification option 1, there is different elements returned from the field computer details endpoint response. Each response has additional details under each Product element which includes a ProductType.

Refer to the table below for the corresponding UOM for a given ProductType. Products have a Name element which can be used as a reference between the .dbf file of the shapefile and the response of the product details.

Name	ProductType	UOM
Liquid	LIQUID	Liters / Ha
Granular	GRANULAR	Kg / Ha
Injection Ratio Rate	LIQUID_INJECTION	Liters / Liter
Planter	PLANTER	Count / Ha
Spinner	SPINNER	RPM

FMIS Format

The FMIS (Farm Management Information Software) file output references International Standards Organization (ISO) 11783 Data Dictionary Items (DDIs). FMIS files reference an Implement element, of which Segment details the Ingredients being applied. Under each Segment there is a SegmentFormat tab formant element, which has a EquipmentSection. The Equipment Section References columns in the associated .tab file.

A description of DDIs and their units are listed below.

Base System ISO DDIs

The following lists the ISOBUS DDIs that are currently used by Raven's base systems. Note, since some of Raven's systems allow for all ISOBUS DDIs to be recorded one may get an ISOBUS DDI that is not on this list.

The information for these DDIs can be found at the following website which holds the ISOBUS Data Dictionary, at ISOBUS Reference.

DDI	Description
1	Setpoint Volume Per Area Application Rate
2	Actual Volume Per Area Application Rate
6	Setpoint Mass Per Area Application Rate
7	Actual Mass Per Area Application Rate
11	Setpoint Count Per Area Application Rate
12	Actual Count Per Area Application Rate
87	Mass Per Time Yield
90	Yield Total Mass
99	Crop Moisture
121	Product Density Mass Per Volume
141	Actual Work State
197	Setpoint Pump Output Pressure
198	Actual Pump Output Pressure

Raven DDI Dictionary

Listed below is information on Raven DDIs.

DD Entity	Definition	Notes	Typically Used Device Class	Unit Symbol	Resolution	Range	Revision Number	Date Added
10 - Target Rate	The set rate that the user desired to have applied.	The units of this value are not defined.	4 - Planters/Seeders 5 - Fertilizer 6 - Sprayers	None	1	Undefined	1	07/23/2014
11 - Actual Rate	The applied rate that the system actually applied.	The units of this value are not defined.	4 - Planters/Seeders 5 - Fertilizer 6 - Sprayers	None	1	Undefined	1	07/23/2014
12 - Ingredient Id	The Ingredient Id of the ingredient that was actually applied.	This identifier corresponds with the ingredients for this implement in the XML file.	4 - Planters/Seeders 5 - Fertilizer 6 - Sprayers 7 - Harvesters	Identifier	1	0 to 2147483647	1	07/23/2014
13 - Section Status	The ON or OFF status of the section.	1 - ON 0 - OFF	4 - Planters/Seeders 5 - Fertilizer 6 - Sprayers 7 - Harvesters	Status	1	0 to 1	1	08/11/2014
14 - Setpoint Volume Per Area Application Rate	Setpoint Application Rate specified as volume per area.		6 - Sprayers	L/Ha; Volume in liters per area in hectares	0.001	0 to 2147483647	1	08/11/2014
15 - Actual Volume Per Area Application Rate	Actual Application Rate specified as volume per area.		6 - Sprayers	L/Ha; Volume in liters per area in hectares	0.001	0 to 2147483647	1	08/11/2014
16 - Setpoint Mass Per Area Application Rate	Setpoint Application Rate specified as mass per area.		4 - Planters/Seeders 5 - Fertilizer	kg/Ha; Mass in kilograms per area in hectares	0.01	0 to 2147483647	1	08/11/2014
17 - Actual Mass Per Area Application Rate	Actual Application Rate specified as mass per area.		4 - Planters/Seeders 5 - Fertilizer	kg/Ha; Mass in kilograms per area in hectares	0.01	0 to 2147483647	1	08/11/2014
18 - Setpoint Revolutions Per Time Application Rate	Setpoint Spinner Rate specified as revolutions per time.		4 - Planters/Seeders 5 - Fertilizer	Rev/M; Revolutions per minute	1	0 to 2147483647	1	08/11/2014
19 - Actual Revolutions Per Time Application Rate	Actual Spinner Rate specified as revolutions per time.		4 - Planters/Seeders 5 - Fertilizer	Rev/M; Revolutions per minute	1	0 to 2147483647	1	08/11/2014
20 - Setpoint System Pressure	Setpoint System Pressure.	This is used to set the pressure to keep the system when using NH3.	5 - Fertilizer/NH3	kilopascals; Pressure in the system	0.01	0 to 2147483647	1	08/11/2014
21 - Actual System Pressure	Actual System Pressure.	The actual pressure in the system when using NH3.	5 - Fertilizer/NH3	kilopascals; Pressure in the system	0.01	0 to 2147483647	1	08/11/2014
22 - Product Id	The Product Id of the product that was actually applied.	This identifier corresponds with the product for this implement in the XML file.	4 - Planters/Seeders 5 - Fertilizer 6 - Sprayers 7 - Harvesters	Identifier	1	0 to 2147483647	1	07/23/2014