Skip to content

README.md

Latest commit

 

History

History
86 lines (58 loc) · 2.72 KB

README.md

File metadata and controls

86 lines (58 loc) · 2.72 KB

Cibolabs API

The cibolabs APIs provide access to data for two cibolabs services:

  • The Agricultural Feedbase Monitor (AFM)
  • Pasture Key

Learn more about these services at cibolabs.com.au.

Quick links

The AFM API

AFM measures pasture biomass and ground cover for supported territories (e.g. Australia) using satellite imagery, captured every five days. The image data are processed at 80 m resolution. View the maps here.

The AFM API calculates pasture biomass and ground cover statistics (the mean, standard deviation, etc) for areas of interest over time. The data are extracted from the images and the statistics calculated at the time of the request.

AFM API

The AFM Tile API

Use the AFM Tile API to retrieve raster products, in png file format, to display in web mapping applications.

The tile API follows the XYZ tile protocol, which is a standard for serving tiles over the web.

AFM Tile API

The Pasture Key API

Pasture Key is like AFM. However, it measures pasture biomass and ground cover for paddocks at high detail, 10 m, resolution. Data are processed for every satellite overpass, which is typically every 5 days.

The Pasture Key API provides access to pasture biomass and ground cover statistics for a farm's paddocks over time.

The Pasture Key API requires that you or your customers have an active Pasture Key subscription. This is because the statistics are pre-computed (at every satellite overpass) and stored in our database for fast retrieval.

Pasture Key API

Demo Pasture Key Web App

The Pasture Key Tile API

Use the Pasture Key Tile API to retrieve raster products, in png file format, to display in web mapping applications.

The tile API follows the XYZ tile protocol, which is a standard for serving tiles over the web.

Pasture Key Tile API

Accessing the APIs

Access requires credentials. Contact us at support@cibolabs.com.au.

Exchange your credentials for an access token using the Login API.

A typical workflow

A typical workflow is:

  • Use our login end point to exchange your credentials for an access token
  • Pass the access token in the Authorization header of your http requests to our APIs' endpoints