Sample responses
Overview
This page shows and describes sample responses from Leaf API, along with a list of what properties you can expect for each type of data.
Operation Summary
Leaf returns operation file summaries in a standardized format. Summaries use
the point data to derive basic information about the operation and include links
to the original files and images of an operation. Naturally, different
types of operations contain different properties. For instance, an applied
operation will contain appliedRate, whereas a harvested operation will
contain wetMass and other Yield properties. The resource below shows a typical return. A list of
all properties is available here.
A list of the properties as well as a sample summary response for an operation file is included below.
An operation returned by Leaf can be an individual file or contain multiple
individual files (uploaded, merged or uploaded).
If the operation contains more than one individual file, another key is added to
the resource, the "sources" key, that is a list of individual file ids.
If the operation was created by an upload on the /batch endpoint, the "batchId"
key will be added to the resource with the corresponding uuid.
Sample Summary response
You can move through the three tabs below to see a sample of how Leaf returns each of the operation types.
- Planted
- Applied
- Harvested
- Tillage
This is an example of a summary for a "harvested" operation
Properties
Select the tab you want to see: "planted", "applied", "harvested", or "tillage".
- Planted
- Applied
- Harvested
- Tillage
| key | presence | type |
|---|---|---|
| crop | * | string |
| seedRate | * | dict |
| operationType | * | string "planted" |
| totalArea | * | float |
| elevation | * | dict |
| variety | ** | string |
| seedRateTarget | ** | dict |
| seedDepth | ** | dict |
| machinery | ** | list of machineInfo objects |
| speed | ** | dict |
| totalPlanted | ** | int (number of seeds) |
* = Always in response
** = Usually in response but not required to pass tests
Standard Geojson
When the data is present in the original file, Leaf standardizes names and units to create the standardGeojson.
Below we list all the properties in the standardGeojson.
Sample Response
Each operation file returns with a "standardgeojson" URL that allows you to download a full point dataset from the operation in a standardized geojson format. Below is an example of the format of each point in these files.
- Planted
- Applied
- Harvested
- Tillage
Properties
- Planted
- Applied
- Harvested
- Tillage
| key | presence | type | example units | description |
|---|---|---|---|---|
| coords | * | Point (x,y) | - | Point (x,y) |
| timestamp | * | string | - | ISO 8601 date, complete and with Z. example: 2011-10-05T14:48:00.000Z |
| crop | * | string | - | Crop type (normalized) |
| area | * | float | ft² or m² | Area represented by point |
| heading | * | float | degrees | Heading of machine at point |
| distance | * | float | ft or m | Distance travelled since previous point |
| elevation | * | float | ft or m | Distance to sea level |
| operationType | * | string | - | string "planted" |
| equipmentWidth | * | float | ft or m | Width of implement |
| recordingStatus | * | Boolean | - | Recording status of machine at point |
| seedRate | * | int | seeds/m² or seeds/ac | The rate of seeds planted at point |
| variety | ** | string | - | The variety of seed being planted |
| speed | ** | float | ft/s or m/s | Speed of machine at point |
| sectionId | ** | int | - | ID of implement sensor section |
| machinery | ** | list of machineInfo objects | - | name of machine & implement |
| seedRateTarget | ** | int | seeds/m² or seeds/ac | The target rate of seeds to be planted at the point |
| seedDepth | ** | float | cm | The depth at which seeds were planted at point |
* = Always in response
** = Usually in response but not required to pass tests