Analysis-Ready PlanetScope

logo

Analysis-Ready PlanetScope (ARPS) is harmonized, cloud-masked, and spatially consistent near-daily stacks of images that enable time-series analysis and machine learning applications.

About Analysis-Ready PlanetScope data

Highlights

  • 3.0-4.1 m GSD (resampled to 3 m)
  • Blue, Green, Red, Near Infrared bands
  • and additionally cloud mask and scene provenance bands

Data information

Analysis-Ready PlanetScope is a temporally and spatially consistent Surface Reflectance (SR) data product that is primarily driven by Planet’s near-daily Dove-C, Dove-R and SuperDove imagery. It is generated by radiometrically informing PlanetScope data with third-party earth observation data sources (Landsat, Sentinel-2, MODIS, VIIRS). The spectral bands and spectral response functions of ARPS data are equivalent to the blue (B2), green (B3), red (B4), and narrow NIR (B8a) bands of Sentinel-2 (ESA 2024). The resulting product is temporally and radiometrically consistent time series optimized for quantitative analysis of change that occurs at the >= 1 day time scale. The core use case is analytical modeling and change detection focused on vegetation phenology and spectral change. These indicators are particularly valuable in agricultural, forestry and land use-change applications.

More information about ARPS data can be found here.

Basic facts

PropertyInfo
Spatial resolution3 m (resampled)
Revisit timeThe product is produced on-demand, it is available with near-daily frequency
Spatial coverageglobal
Data availabilityJanuary 1, 2017
Available measurementsSurface reflectance
Common usage/purposeChange detection focused on vegetation phenology. Any other spectral change can also be detected, it is particularly valuable in agricultural, forestry and land use-change applications.

Purchasing Analysis-Ready PlanetScope data

If you would like to purchase Analysis-Ready PlanetScope, please contact Planet Sales.

Subscribing to Analysis-Ready PlanetScope Data

To subscribe to Analysis-Ready PlanetScope Data, use Planet's Subscriptions API with the option to deliver data to Sentinel Hub. This is the preferred way of subscribing to ARPS data.

Subscription to ARPS data is for now also possible using TPDI subscriptions endpoint or via EO Browser's "Commercial Data" tab. You will have to specify values for parameters type and id as explained below.

The minimum individual subscription area is 25 square kilometers, and is subject to some shape constraints. You can subscribe to smaller areas, however, you will be billed for the minimum area.

Note that delivery of the data can take anytime from a few hours up to a week depending on the request.

id parameter

One Analysis-Ready PlanetScope product is available:

idDescription
PS_ARD_SR_DAILYNear-daily radiometrically-calibrated analytic image

More information:

type parameter

For ARPS always use value analysis_ready_ps.

Other parameters

Other parameters are set by SH and cannot be changed by the user.

Provider's parameter / toolThe values used by SH for ordering
Clip toolis applied using geometry specified by the user

More information:

Once the data is successfully delivered it will be available in one of your BYOC collections. The tiles in the collection will correspond to Analysis-Ready PlanetScope scenes. To access the data you will need the id of this collection.

Accessing Analysis-Ready PlanetScope Data

Accessing the Analysis-Ready 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 Analysis-Ready PlantScope data are listed below.

Endpoint Locations

ServiceNotes
https://services.sentinel-hub.com/Contains the data purchased by individual user

Filtering Options

collectionId

Use the id of the BYOC collection into which your PlanetScope data was delivered as a value of parameter input.data.type in the process API requests. See BYOC data access for more information.

Available Bands and Data

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.

NameDescriptionResolution
blueBlue3m
greenGreen3m
redRed3m
nirNear Infrared3m
cloud_maskCloud and shadow mask3m
scene_maskPixel provenance has integers which can be mapped to PlanetScope scene IDs using the information in the QA raster's metadata header.
NOTE: Currently the only way to get the raster's metadata header is to download the original files. We are working on making the metadata available directly in Sentinel Hub.
3m
dataMaskThe mask of data/no data pixels (more).N/A*

* dataMask has no source resolution as it is calculated for each output pixel.

Units

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.

The Source Format specifies how and with what precision the digital numbers (DN) from which the unit is derived are encoded. 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 Analysis-Ready PlanetScope bands, DN are the default and only unit. Reflectance values can be obtained for the optical bands using the simple formula: reflectance = DN / 10000.

The Typical Range indicates what values are common for a given band and unit, however outliers can be expected.

BandPhysical Quantity (units)Sentinel Hub UnitsSource FormatTypical Range
Optical bandsScaled reflectance (unitless)DNINT160 - 4000.
Highly reflective pixels can have values up to 10000.
cloud_maskCloud mask (unitless)DNINT161 - clear
2 - bright cloud
3 - cloud shadows
4 - haze
5 - adjacent clouds/cloud shadows
6 - additional haze or cloud elements
7 - contamination including snow
scene_maskPixel provenance (unitless)DNINT160 - 1000
dataMaskN/ADNN/A0 - no data
1 - data

Mosaicking

All mosaicking types are supported.

Examples

Analysis-Ready PlanetScope examples