- Almost daily coverage worldwide
- 3.7-4.1 m pixel size (resampled to 3 m)
- Blue, Green, Red, Near Infrared (+Red Edge and more in near future)
PlanetScope satellite constellation consists of more than 130 small satellites called Doves. Each Dove satellite is a CubeSat made of three cubic units and thus measures only 10 cm x 10 cm x 30 cm. The satellites are launched in groups, which constantly improves mission's characteristics such as revisit times, spatial and spectral resolutions. The constellation is constantly "on" and does not require an acquisition planning.
PlanetScope data is an excellent source for vegetation monitoring. It complements Sentinel-2 data with better spatial resolution and better temporal coverage, which is especially important in cloudy areas as it increases the chance of acquiring a cloudless image.
|Spatial resolution||3 m (resampled)|
|Sensor||Four-band frame Imager: Blue, Red, Green and Near-Infrared band|
|Revisit time||1 day|
|Data availability||Global since 2016|
Top of the atmosphere reflectance,
|Common usage/purpose||Land-cover maps, land-change detection maps, vegetation monitoring|
The PlanetScope products are released under the license available here.
Note: If you already have you Planet's api key you can skip this section and continue with Ordering PlanetScope Data.
The process of purchasing of PlanetScope data in Sentinel Hub goes as follows:
- Check the pricing and conditions. If you would like to buy bigger area send us an e-mail and we will prepare a custom offer.
- Go to the "Billing" section in your SH Dashboard and buy the Planet Scope plan.
- You will get an invitation from Planet to sign EULA, after which you will receive your Planet's api key.
Once you have your Planet's api key you can proceed to Ordering PlanetScope Data.
- Vouchers for non-commercial use available, sponsored by ESA, follow this link.
- Volume discounts possible for large users. Contact us.
- Existing Planet users can use the data through Sentinel Hub using their own credentials.
- Minimum area per order is 0.01 km2.
- Maximum number of items per order is 500. Orders listing more than 500 itemIds have to be split, and subscriptions must be used instead of search-based orders that match more than 500 items.
For ordering of PlanetScope data you will need your Planet api key. To order PlanetScope data, please use our Third Party Data Import API. Data can be ordered individually or by subscribing to all data that match your criteria.
PlanetScope data can be ordered through SH either as scaled top of the atmosphere reflectance or surface reflectance, according to the requested asset type. Furthermore, ordering usable data mask bands (UDM2) is recommended, as the user gets all the available PlanetScope bands. The cost does not increase when including UDM2 bands.
The value of the
productBundle parameter specifies what will be ordered:
|Ordered Asset Type||Ordered Bands|
|top of the atmosphere reflectance||B1-B4 and UDM|
|top of the atmosphere reflectance||B1-B4 and UDM and UDM2|
|surface reflectance||B1-B4 and UDM|
|surface reflectance||B1-B4 and UDM and UDM2|
Subscriptions currently only support the surface reflectance asset type and the UDM2 bands are always included,
productBundle parameter in a subscription must be
Harmonization tool is applied by default.
User can turn it off by setting
"NONE" when placing an order. Harmonization is not supported for
analytic_sr asset type.
When using subscriptions, currently only the surface reflectance asset type is supported, therefore
harmonizeTo must be set to
Other parameters are set by SH and cannot be changed by the user.
|Provider's parameter / tool||The values used by SH for ordering|
|Top of Atmosphere Reflectance (toar) tool|
is applied for asset type
not applied for asset type
|Clip tool||is applied|
Note: If you would need any other PlanetScope product, please contact us.
Once your order is successfully finished the ordered data will be available in one of your BYOC collections. The tiles in the collection will correspond to PlanetScope scenes. To access the data you will need the id of this collection.
Accessing of the PlanetScope data is similar to accessing any other BYOC data. All processing and filtering options listed there can be used. However, the settings specific for accessing of PlantScope data are listed below.
|https://services.sentinel-hub.com/||Contains the data purchased by individual user|
Use the id of the BYOC collection into which your PlanetScope data was delivered as a value of parameter
input.data.dataFilter.collectionId in the
process API requests. See BYOC data access for more information.
This chapter will explain the bands and data which can be set in the evalscript input object.
Any string listed in the column Name can be an element of the
input.bands array in your evalscript.
|B1||Blue, 455 - 515 nm||3m|
|B2||Green, 500 - 590 nm||3m|
|B3||Red, 590 - 670 nm||3m|
|B4||Near Infrared, 780 - 860 nm||3m|
|UDM||Unusable Data Mask||3m|
|UDM2_Clear*||Usable Data mask - Clear mask||3m|
|UDM2_Snow*||Usable Data mask - Snow mask||3m|
|UDM2_Shadow*||Usable Data mask - Shadow mask||3m|
|UDM2_LightHaze*||Usable Data mask - Light haze mask||3m|
|UDM2_HeavyHaze*||Usable Data mask - Heavy haze mask||3m|
|UDM2_Cloud*||Usable Data mask - Cloud mask||3m|
|UDM2_Confidence*||Usable Data mask - Confidence map||3m|
|dataMask||The mask of data/no data pixels (more).||N/A**|
* The UDM2 bands are available only for orders where the
productBundle field is set to
** dataMask has no source resolution as it is calculated for each output pixel.
The data values for each band in your custom script are presented in the units as specified here. In case more than one unit is available for a given band, you may optionally set the value of
input.units in your evalscript
setup function to one of the values in the
Sentinel Hub Units column. Doing so will present data in that unit. The Sentinel Hub
units parameter combines the physical quantity and corresponding units of measurement values. As such, some names more closely resemble physical quantities, others resemble units of measurement.
Source Format specifies how and with what precision the digital numbers (
DN) from which the unit is derived are encoded. Bands requested in
DN units contain the pixel values which are the result of ordering and preprocessing the data as explained in the chapter Ordering PlanetScope Data. Note that resampling may produce interpolated values.
DN is also used whenever a band is derived computationally (like dataMask); such bands can be identified by having
DN units and
N/A source format.
For PlanetScope bands,
DN are the default and only unit. Reflectance values can be obtained for bands B1 - B4 using the simple formula:
reflectance = DN / 10000.
Typical Range indicates what values are common for a given band and unit, however outliers can be expected.
|Band||Physical Quantity (units)||Sentinel Hub Units||Source Format||Typical Range|
B1 - B4
|Scaled reflectance (unitless)||DN||UINT16||0 - 4000. |
Highly reflective pixels can have values above 10000.
|UDM||Unusable data mask (unitless)||DN||UINT8||0 - fully usable data|
other - potentially problematic/unusable data
Full description is in Planet's documentation (Page 91, Section 2. UNUSABLE DATA MASK FILE).
|UDM2_Clear||Unusable data mask (unitless)||DN||UINT8||0 - not clear|
1 - clear
|UDM2_Snow||Snow mask (unitless)||DN||UINT8||0 - not snow|
1 - snow
|UDM2_Shadow||Shadow mask (unitless)||DN||UINT8||0 - not shadow|
1 - shadow
|UDM2_LightHaze||Light haze mask (unitless)||DN||UINT8||0 - not light haze|
1 - light haze
|UDM2_HeavyHaze||Heavy haze mask (unitless)||DN||UINT8||0 - not heavy haze|
1 - heavy haze
|UDM2_Cloud||Cloud mask (unitless)||DN||UINT8||0 - not cloud|
1 - cloud
|UDM2_Confidence||Confidence map (percent)||DN||UINT8||0 - 100|
|dataMask||N/A||DN||N/A||0 - no data|
1 - data
All mosaicking types are supported.