Arable Backend API 3.5.0 Release Notes

July 27,  2022

Instance affected

Production

Components

api-device v1.13.0

api-user v3.40.2

data-processing v0.26.3

api-weather v2.20.1

app-admin 1.17.0

postgresDB 12.0.0

APIs

Documentation: https://developer.arable.com/

URL: https://api.arable.cloud/api/v2/

3rd Party Sensors

Sentek Drill and Drop Soil Moisture Probe DD-MTS and DD-MT

Davis Wind Anemometer 6410 and 7911

GEMS PS41 Series Pressure Switch

Type of Release

Minor Release

Version

3.5.0

Req. ID

As a user on the new sites-based platform, you can now upload the site boundaries for all of your fields in no time. New in this release is the option to share Shapefiles with the Arable Customer Success team, streamlining your onboarding to the new field-centric data view in Arable Web and Mobile. This view greatly improves data continuity within and across growing seasons. Contact Customer Success today to get started! 

Spray Timing Window APIs were added in Arable site-platform APIs. The spray window is determined by validating rainfall, wind, and optionally temperature and relative humidity. Default thresholds are for wind 6 m/s, temperature <30 ℃ and relative humidity >45%. As for rainfall, it is considered bad conditions for spraying if it is currently raining, there are more than 50 mm within the next 24 hrs or more than 25 mm within 1 hr of application. 

For the Rainfall Model, we added several new input parameters such as humidity and sunlight to bolster the reliability of system reports. 

For the Temperature Model, we extended our measurement range from -20°C to 60°C and increased the overall accuracy of the model.

Description

Ticket ID

Fixes a data processing hang issue where the seasons data volume is significantly larger which causes the GDD data missing at times.

BAC-I2757

Fixes the Notes- Annotation moment API to return the weather and plant data with last sync data if the latest data is not synced yet. 

BAC-I2804

Fixes the performance issue of daily and hourly data api endpoints by optimizing the database queries.

BAC-I2867

Fixes the /locations/summary api endpoint to return the last sync value instead of null.

BAC-I2869

Fixes the schemas api endpoint for calibrated data access to the authenticated subscriber.

BAC-I2880

Fixes the unit conversion error for SLP values in historical api endpoint as per the unit of measurement described in the input params.

BAC-I2939

Fixes the daily data summary for locations and sites are corrected for the given date range instead of always returning one year data limits.

BAC-I2964

Fixes the timeline api endpoint for sites to return the daily data records with days resolution to include the current day irrespective of the time of day of the user request.

BAC-I2859

Fixes the data error reporting negative NDVI values for the site summary api.

BAC-I2932

Fixes a bug to handle the negative values for CL indes in the site/locations - summary, plant and data/daily api endpoints.

BAC-I2841

Fixes the sites and location summary api endpoints to not report the incorrect stale data when the device data is not synched. Eliminates the false temp alerts with the incorrect stale temp data.

BAC-I2901

Fixes the device location association anomaly when the device is deployed from the inventory to the customer location for the first time.

BAC-I2351

Description

Ticket ID

When you are considering moving to the new sites-framework, then the entire organization should transition at the same time. The reason for this is that deployment naming is different with the site-view than with the location view, and could cause confusion if some have transitioned and others have not. An automated naming for new Arable Mark deployments will occur as soon as one of the device owners has Sites enabled. The location name will then be device ID + deployment time stamp.  

AR1-T618

It can take several minutes (up to an hour) to see measurement data after a new installation if the unit was not properly undeployed after the previous installation, as data will have been collected during transport and the Mark will send its data in FIFO mode. 

AR1-T685

If GPS isn't available at a deployment (e.g., deployed indoors), the deployment may fail with a server-side exception. It is important to note that the Arable system is currently based on the availability of GPS in order to provide accurate locations on maps and in calculations. We are looking into how we can operate better with adding the GPS coordinates via the API (and UI) if not automatically reported by the Arable Mark 2.

AR1-T444

While the API documentation at https://developer.arable.com/ is helpful, it is auto-generated and is missing a list of all available endpoints. We will add this into the Guide section in the future. In the meantime, if you need more help related to understanding the endpoints available on each API route, please review this file or contact Arable Customer Success via the Help icon in your app. 

BUGS-760

The Arable Mark omits to send any wind speed data in case of zero wind speed. That is today shown as missing data in the Arable API. A better handling of zero wind speed is planned to be introduced in an upcoming release. 

BUGS-1454