This document describes the advantages and technical specification for integrating your organisation datasets with Cecil.

Advantages of integrating with Cecil

• Cecil provides an additional distribution channel for your organisation. Our customers will discover your datasets in our product documentation.
• Our unique value proposition is to deliver an intuitive developer experience. Our customers will acquire and analyse your datasets in a few simple steps.
• Our differentiator is to introduce a database system with native support for spatial data, enterprise-grade security, and OLAP architecture for highly scalable analysis. This will enable our customers to develop scalable workflows using your organisation datasets.
• We learn about your product details and we provide exceptional customer service. This will reduce your efforts in customer onboarding and support.
• We offer a simple pricing model that doesn’t have minimum usage requirements and we enable our customers to scale in a cost effective manner.

Process overview

There are 3 high-level steps across the end-to-end integration.

• Data request: Cecil initiates the process by submitting an API request to your organisation.
• Webhook notifications: Your organisation provides status notifications on data requests.
• Data delivery: Your organisation finalises the process by delivering files via S3 or HTTP.

Data request

Cecil requires an API endpoint from your organisation that allows submitting a data request, which represents a dataset purchase order for an area of interest (AOI).

Minimum requirements

• Request body containing your dataset ID and a GeoJSON in EPSG:4326 delimiting the AOI boundary, allowing up to 1,500 vertices, and supporting Polygon or MultiPolygon coordinates data type. By default, your dataset must provide all variables and full temporal coverage.
• For monitoring data requests (aka subscriptions), Cecil requires additional request body parameters for subscription settings (e.g. disabling auto renewal and choosing an end date). Additional API endpoints are also required to allow cancelling and updating subscriptions.
• Response body containing an entity ID representing Cecil’s data request in your system.

Recommended

• Request body with optional parameters that may be available in your product. For example, the ability to select specific variables and temporal coverage.