If you want to use Planet data with Sentinel Hub tools and APIs, then you need to first deliver data to a Sentinel Hub collection. This post is a primer on how to deliver data to Sentinel Hub collections.
First though, what is a collection? A collection is a way of organizing imagery on Planet Insights Platform so that it can be used in APIs such as the Catalog, Process, Statistics, and OGC APIs. Collections consist of imagery that is all the same sensor and format. This means that a collection can’t mix PlanetScope and SkySat, or 8-band and 4-band imagery.
For some datasets, collections are ready to be used, such as those for public missions like Sentinel and Landsat. However, for Planet data products, you must first order your data and send it to your own personal collection. Below are the different ways to accomplish this.
Note: To do any of these workflows, you will need a Sentinel Hub account. All Planet customers can create Sentinel Hub accounts and receive limited access at no additional cost. See more details here:
1) Subscriptions or Orders API - Delivery to Sentinel Hub Collection
You can use the Planet Subscriptions or Orders API to deliver imagery directly to a Sentinel Hub collection. Which API you should use depends on your use-case, but generally the Orders API is designed for orders of discrete imagery while the Subscriptions API is designed for longer time spans and ongoing monitoring.
With either API, simply add a hosting block to your request and optionally specify a Sentinel Hub collection ID. If no collection ID is specified, one will be created for you.
- Subscriptions API Delivery to Sentinel Hub Collection
- Orders API Delivery to Sentinel Hub Collection
Prefer to learn by doing? Check out these Jupyter notebooks for each API.
- Subscriptions API Delivery to Sentinel Hub Collection
- Orders API Delivery to Sentinel Hub Collection
Note: It’s best to organize all of your related orders and subscriptions into a single collection. For example, all orders for a specific project or customer or analysis would go to one collection. The notebooks above show how to get the collection ID from an order and re-use it for future orders.
2) EO Browser
If you are looking for a web application where you can deliver data to Sentinel Hub, you can use EO Browser. In EO Browser you can create Orders and Subscriptions (which correlate to the previously mentioned APIs). Through the interface you can specify all of the parameters like the date range, area of interest, asset types, and destination collection ID.
See this user guide on ordering commercial data in EO Browser. This example goes through order Planetary Variables, but is also applicable to other datasets including PlanetScope and SkySat.
3) Bring Your Own COG (BYOC) API
The BYOC API is a more advanced workflow. With this API, you can register Cloud Optimized GeoTIFFs (COG) stored in AWS S3 buckets. For example, if you’ve previously ordered Planet data to your own AWS storage, you could use the BYOC API to register data. You can find documentation for this API in the Sentinel Hub documentation.
Note: If you use the other options for delivering data to a Sentinel Hub collection, you do not need to use the BYOC API as this is automatically done for you.
