Please reach out to your Climate Corporation business team at email@example.com to discuss options.
Yes absolutely! Partner and customer support will be handled by The Climate Corporation’s support team. More information about The Climate Corporation support team can be obtained at support.climate.com
The Climate FieldView platform is one of the largest digital agriculture platforms in the world with more than 120 million acres and more than 100,000 farmers. Partners get the following benefits by creating new value by being on the platform.
Becoming a Climate FieldView platform partner is a simple 3 step process.
Just fill out the partner information form to get started
You do not have to pay to get a developer account on the platform.
You can find API documentation on the dev portal under the “Technical Docs” section.
Please work with your Climate Corporation business team member to discuss terms. You can reach your Climate business team at firstname.lastname@example.org
The Climate Corporation takes customer data privacy very seriously. Please refer to The Climate Corporation’s existing policy at https://climate.com/legal/privacy-policy.
We want to make sure our partners have a great experience building against our APIs. We will provide technical support during the implementation process.
For security reasons, Climate does not allow making API calls from a browser. You should call the Climate FieldView Platform APIs from your backend service.
If you see HTTP 403 forbidden error as shown in the picture above, most likely you have entered your x-api-key incorrectly. Please verify your x-api-key and try again.
Agronomic Data APIs
There could be many reasons why you are not able to see the expected data. Some of them are listed below:
You can use periodic polling to know when new planting or harvesting data is available. Once all results for a given query are fetched, an HTTP 304 response code is returned along with x-next-token. You can use the last x-next-token to poll periodically; if new results are available they will be returned.
The agronomic data API takes resourceOwnerId as an optional parameter. This parameter represents a unique grower in Climate FieldView application. When this parameter is present, data for that grower is returned.
The current implementation can return 206 or 200 response code whether there is more data or not. You should look for 304 response code as an indicator that no more data is available. Alternatively, the agronomic activity result set returns the length of each activity. You can use the length of the activity to page through the contents of the activity.
Please follow the steps listed here to update your planting or harvest data.
The planting and harvest activities will be available through the APIs as soon as an internet connection is available between the FieldView Cab app and the Climate cloud, while the activity is being performed.
Yes, these are the fields in which the activities took place. The user can choose a field manually, get alerted for field selection based on the boundaries (on cab app), or have the field automatically updated based on the boundaries.
The following diagram shows high-level steps for downloading the agronomic data.
Currently, there is no way to name the image you are uploading.
You can only attach one boundary to a field.
You have the ability to upload multiple images to a given field for a given date/time as long as the contentType is different.
When a file is successfully uploaded using the upload API, the file is only uploaded to a file store and processing is done later asynchronously. There could be many reasons why an upload is not showing up for a grower, some of them are listed below.
The following are high-level details of how auto import works.