- 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||Since 2009|
|Measurement||Top of the atmosphere (TOA) 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.
Limited use for agriculture until 31.12.2020 in Argentina, Armenia, Australia, Azerbaijan, Belarus, Brazil, Chile, Kazakhstan, Kyrgyzstan, Moldova, North America, Paraguay, Russia, South Africa, Tajikistan, Turkmenistan, Ukraine, Uruguay, Uzbekistan.
For ordering of PlanetScope data you will need your Planet api key. To order PlanetScope data, please use our Third Party Import Data API.
SH uses the following settings when ordering PlaneScope data:
|Provider's parameter / tool||The values used by SH for ordering|
|Top of Atmosphere Reflectance (toar) tool||is applied|
|toar scale factor||10000|
|Clip tool||is applied|
|Harmonize tool||is applied by default, user can turn it off by setting |
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|
|dataMask||The mask of data/no data pixels (more).||N/A*|
*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 default 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 options. Doing so will present data in that unit. The
Source Format specifies how and with what precision the digital numbers from which the unit is derived are encoded. The
Typical Range indicates what values are common for a given band and unit, however outliers can be expected.
For PlanetScope bands,
DN (digital numbers) are the default and only unit. Reflectance values can be obtained using the simple formula:
reflectance = DN / 10000.
|Band||Unit||Source Format||Typical Range||Note|
B1 - B4
|DN||UINT16||0 - 4000||Highly reflective pixels can have values above 10000.|
|UDM||bit mask||UINT8||0 - fully usable data|
other - potentially problematic/unusable data
|Full description in Planet's documentation (Page 91, Section 2. UNUSABLE DATA MASK FILE)|
|dataMask||N/A||Boolean||0 - no data|
1 - data
All mosaicking types are supported.