Log inSuggest an edit

Planet Satellite Imagery Products

Last updated November 2016

Disclaimer - This document is designed as a general guideline for customers interested in acquiring Planet imagery products and services. Planet takes an agile and iterative approach to its technology, and therefore may make changes to the product(s) described in this document.

Table of Contents

  1. Overview
  2. Satellite Constellations and Sensor Overview
  3. PlanetScope Imagery Product
  4. RapidEye Imagery Product
  5. Product Metadata
  6. Product Delivery
  7. Image Support Data
  8. Tile Grid Definition

1. Overview

Data Product Overview

Planet operates the PlanetScope (PS) and RapidEye (RE) Earth-imaging constellations. Imagery is collected and processed in a variety of formats to serve different use cases, be it mapping, deep learning, disaster response, precision agriculture, or simple temporal image analytics to create rich information products.

PlanetScope satellite imagery is captured as a continuous strip of single frame images known as “scenes.” Scenes may be acquired as a single RGB (red, green, blue) frame or a split-frame with a RGB half and a NIR (near-infrared) half depending on the capability of the satellite.

Planet offers three product lines for PlanetScope imagery: a Basic Scene product, an Ortho Scene product, and an Ortho Tile product. The Basic Scene product is a scaled Top of Atmosphere Radiance (at sensor) and sensor-corrected product. The Basic Scene product is designed for users with advanced image processing and geometric correction capabilities. The product is not orthorectified or corrected for terrain distortions. Ortho Scenes represent the single-frame image captures as acquired by a PlanetScope satellite with additional post processing applied. Ortho Tiles are multiple orthorectified scenes in a single strip that have been merged and then divided according to a defined grid.

Figure A: Planet Imagery Product Offerings

2. Satellite Constellations and Sensor Overview

2.1 PlanetScope Satellite Constellation and Sensor Characteristics

The PlanetScope satellite constellation consists of multiple launches of groups of individual satellites. Therefore, on-orbit capacity is constantly improving in capability or quantity, with technology improvements deployed at a rapid pace.

Each PlanetScope satellite is a CubeSat 3U form factor (10 cm by 10 cm by 30 cm). The complete PlanetScope constellation of approximately 120 satellites will be able to image the entire Earth every day (equating to a daily collection capacity of 150 million km²/day).

Table A: PlanetScope Constellation and Sensor Specifications

Mission CharacteristicSun Synchronous OrbitInternational Space Station Orbit
Orbit Altitude (reference)475 km (~98° inclination)400 km (51.6° inclination)
Max/Min Latitude Coverage+/- 81.5° (depending on season)+/- 52° (depending on season)
Equator Crossing Time9:30 - 11:30am (local solar time)Variable
Sensor TypeFThree-band frame Imager or four-band frame Imager with a split-frame NIR filterThree-band frame Imager or four-band frame Imager with a split-frame NIR filter
Spectral BandsBlue: 455 - 515 nm
Green: 500 - 590 nm
Red: 590 - 670 nm
NIR: 780 - 860 nm
Blue: 455 - 515 nm
Green: 500 - 590 nm
Red: 590 - 670 nm
NIR: 780 - 860 nm
Ground Sampling Distance (nadir)3.7 m (at reference altitude 475 km)3.0 m (approx.)
Swath WidthSwath Width24.6 km x 16.4 km (approximate)
Maximum Image Strip per Orbit20,000 sq km8,100 sq km
Revisit TimeDaily at nadir (early 2017)Variable
Image Capture Capacity150 million sq km/day (early 2017)Variable
Camera Dynamic Range12-bit12-bit

2.2 RapidEye Satellite Constellation and Sensor Characteristics

The RapidEye satellite constellation consists of five satellites collectively able to collect over 6 million square kilometers of data per day at 6.5 meter GSD (at nadir). Each satellite measures less than one cubic meter and weighs 150 kg (bus + payload). All five satellites are equipped with identical sensors and are located in the same orbital plane.

Table B: RapidEye Constellation and Sensor Specifications

Mission CharacteristicInformation
Number of Satellites5
Orbit Altitude630 km in Sun Synchronous Orbit
Equator Crossing Time11:00 am local time (approximately)
Sensor TypeMultispectral push broom
Spectral BandsBlue: 440 - 510 nm
Green: 520 - 590 nm
Red: 630 - 685 nm
Red Edge: 690 - 730 nm
NIR: 760 - 850 nm
Ground Sampling Distance (nadir)6.5 m
Swath Width77 km
Maximum Image Strip per orbitUp to 1500 km of image data per orbit
Revisit TimeDaily (off-nadir) / 5.5 days (at nadir)
Image Capture Capacity>6 million sq km/day
Camera Dynamic Range12-bit

3. PlanetScope Imagery Products

PlanetScope imagery products are available as either individual Basic Scenes, Ortho Scenes, or Ortho Tile products.

Table C: PlanetScope Satellite Image Product Processing Levels

NameDescriptionProduct Level
PlanetScope Basic Scene ProductScaled Top of Atmosphere Radiance (at sensor) and sensor corrected product. The Basic Scene product is designed for users with advanced image processing and geometric correction capabilities. This product has scene based framing and is not projected to a cartographic projection. Radiometric and sensor corrections applied to the data.Level 1B
PlanetScope Ortho Scene ProductOrthorectified, scaled Top of Atmosphere Radiance (at sensor) image product suitable for analytic and visual applications. This product has scene based framing and projected to a cartographic projection.Level 3B
PlanetScope Ortho Tile ProductRadiometric and sensor corrections applied to the data. Imagery is orthorectified and projected to a UTM projection.Level 3A

The name of each acquired PlanetScope image is designed to be unique and allow for easier recognition and sorting of the imagery. It includes the date and time of capture, as well as the id of the satellite that captured it. The name of each downloaded image product is composed of the following elements:

<acquisition date>_<acquisition time>_<satellite_id>_<productLevel><bandProduct>.<extension>

3.1 PlanetScope Basic Scene Product Specification

The PlanetScope Basic Scene product is a Scaled Top of Atmosphere Radiance (at sensor) and sensor corrected product, providing imagery as seen from the spacecraft without correction for any geometric distortions inherent in the imaging process. It has a scene based framing, and is not mapped to a cartographic projection. This product line is available in GeoTIFF and NITF 2.1 formats.

The PlanetScope Basic Scene product is a multispectral analytic data product from the satellite constellation. This product has not been processed to remove distortions caused by terrain and allows analysts to derive information products for data science and analytics.

The Basic Scene product is designed for users with advanced image processing capabilities and a desire to geometrically correct the product themselves. The imagery data is accompanied by Rational Polynomial Coefficients (RPCs) to enable orthorectification by the user.

The radiometric corrections applied to this product are:

  • Correction of relative differences of the radiometric response between detectors
  • Scaled Top of Atmospheric Radiance correction

The geometric sensor corrections applied to this product correct for:

  • Optical distortions caused by sensor optics
  • Co-registration of bands

The table below describes the attributes for the PlanetScope Basic Scene product:

Table D: PlanetScope Basic Scene Product Attributes

Product AttributeDescription
Product Components and FormatThe PlanetScope Basic Scene product consists of the following file components:
  • Image File – GeoTIFF format
  • Metadata File – XML format
  • Rational Polynomial Coefficients - XML format
  • Thumbnail File – GeoTIFF format
  • Unusable Data Mask (UDM) File – GeoTIFF format
Information Content
Analytic Bands3-band natural color (red, green, blue) or 4-band multispectral image (blue, green, red, near-infrared)
Ground Sample Distance3.7 m (at reference altitude 475 km)
Processing
Pixel Size (orthorectified)N/A
Bit DepthAnalytic (DN): 12-bit
Radiometric Calibration AccuracyRelative accuracy less than 15% @ 1 std deviation
* Temporal and Inter-Sensor
Absolute accuracy per satellite less than 20% @ 1 std deviation
Map ProjectionN/A

3.2 PlanetScope Ortho Scenes Product Specification

PlanetScope satellites collect imagery as a series of overlapping framed scenes, and these Scene products are not organized to any particular tiling grid system. The Ortho Scene products enable users to create seamless imagery by stitching together PlanetScope Ortho Scenes of their choice and clipping it to a tiling grid structure as required.

The PlanetScope Ortho Scene product is orthorectified and the product was designed for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. It has been processed to remove distortions caused by terrain and can be used for cartographic purposes. The Ortho Scenes are delivered as visual (RGB) and analytic products. Ortho Scenes are radiometrically-, sensor-, and geometrically-corrected products that are projected to a cartographic map projection. The geometric correction uses fine Digital Elevation Models (DEMs) with a post spacing of between 30 and 90 meters.

Ground Control Points (GCPs) are used in the creation of every image and the accuracy of the product will vary from region to region based on available GCPs.

The table below describes the attributes for the PlanetScope Ortho Scene product:

Table E: PlanetScope Ortho Scene Product Attributes

Product AttributeDescription
Product Components and FormatPlanetScope Ortho Scene product consists of the following file components:
  • Image File – GeoTIFF format
  • Metadata File – XML format
  • Thumbnail File – GeoTIFF format
  • Unusable Data Mask (UDM) File – GeoTIFF format
Product OrientationMap North Up
Product FramingScene Based
Bit DepthVisual: 8-bit
Product SizeNominal scene size is approximately 24 km by 7 km, but varies by altitude.
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model. Orthorectification uses GCPs and fine DEMs (30 m to 90 m posting).
Horizontal DatumWGS84
Map ProjectionUTM
Resampling KernelCubic Convolution

3.2.1 PlanetScope Visual Ortho Scene Product Specification

The PlanetScope Visual Ortho Scene product is orthorectified and color-corrected (using a color curve). This correction attempts to optimize colors as seen by the human eye providing images as they would look if viewed from the perspective of the satellite. This product has been processed to remove distortions caused by terrain and can be used for cartographic mapping and visualization purposes. This correction also eliminates the perspective effect on the ground (not on buildings), restoring the geometry of a vertical shot. Additionally, a correction is made to the sun angle in each image to account for differences in latitude and time of acquisition.

The Visual Ortho Scene product is optimal for simple and direct use of an image. It is designed and made visually appealing for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. The product can be used and ingested directly into a Geographic Information System.

Table F: PlanetScope Visual Ortho Scene Product Attributes

Product AttributeDescription
Information Content
Visual Bands3-band natural color (red, green, blue)
Ground Sample Distance3.7 m (at reference altitude 475 km)
Processing
Pixel Size (orthorectified)3 m
Bit Depth8-bit
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model. Spacecraft-related effects are corrected using attitude telemetry and best available ephemeris data. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting) to <10 m RMSE positional accuracy.
Positional Accuracy<10 m RMSE
Color EnhancementsEnhanced for visual use and corrected for sun angle.

3.2.2 PlanetScope Analytic Ortho Scene Product Specification

The PlanetScope Analytic Ortho Scene product is orthorectified, multispectral data from the satellite constellation. Analytic products are calibrated multispectral imagery products that have been processed to allow analysts to derive information products for data science and analytics. This product is designed for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. The product has been processed to remove distortions caused by terrain and can be used for many data science and analytic applications. It eliminates the perspective effect on the ground (not on buildings), restoring the geometry of a vertical shot. The orthorectified analytic scene is optimal for value-added image processing such as land cover classifications. In addition to orthorectification, the imagery has radiometric corrections applied to correct for any sensor artifacts and transformation to at-sensor radiance.

Table G: PlanetScope Analytic Ortho Scene Product Attributes

Product AttributeDescription
Information Content
Analytics Bands
  • PSScene3Band: 3-band multispectral image (red, green, blue)
  • PSScene4Band: 4-band multispectral image (near-infrared, red, green, blue)
Ground Sample Distance3.7 m (at reference altitude 475 km)
Processing
Pixel Size (orthorectified)3 m
Bit DepthAnalytic (DN): 12-bit, Analytic (Radiance): 16-bit
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model. Spacecraft-related effects are corrected using attitude telemetry and best available ephemeris data. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting) to <10 m RMSE positional accuracy.
Positional Accuracy<10 m RMSE
Radiometric Calibration Accuracy
  • Relative accuracy less than 15% @ 1 std deviation
  • Temporal and Inter-Sensor
  • Absolute accuracy per satellite less than 20% @ 1 std deviation

3.3 PlanetScope Ortho Tile Product Specification

The PlanetScope Ortho Tile products offer PlanetScope Satellite imagery orthorectified as individual 25 km by 25 km tiles referenced to a fixed, standard image tile grid system. This product was designed for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. It has been processed to remove distortions caused by terrain and can be used for cartographic purposes.

For PlanetScope split-frame satellites, imagery is collected as a series of overlapping framed scenes from a single satellite in a single pass. These scenes are subsequently orthorectified and an ortho tile is then generated from a collection of consecutive scenes, typically 4 to 5. The process of conversion of framed scene to ortho tile is outlined in the figure below.

The PlanetScope Ortho Tile products are radiometrically-, sensor-, and geometrically-corrected and aligned to a cartographic map projection. The geometric correction uses fine DEMs with a post spacing of between 30 and 90 meters. GCPs are used in the creation of every image and the accuracy of the product will vary from region to region based on available GCPs.

Figure B: PlanetScope Scene to Ortho Tile Conversion

The table below describes the attributes for the PlanetScope Ortho Tile product:

Table H: PlanetScope Ortho Tile Product Attributes

Product AttributeDescription
Product Components and FormatPlanetScope Ortho Tile product consists of the following file components:
  • Image File – GeoTIFF format
  • Metadata File – XML format
  • Thumbnail File – GeoTIFF format
  • Unusable Data Mask (UDM) File – GeoTIFF format
Product OrientationMap North Up
Product FramingPlanetScope Ortho Tiles are based on a worldwide, fixed UTM grid system. The grid is defined in 24 km by 24 km tile centers, with 1 km of overlap (each tile has an additional 500 m overlap with adjacent tiles), resulting in 25 km by 25 km tiles.
Pixel Size (orthorectified)3.125 m
Bit Depth16-bit unsigned integers
Product SizeTile size is 25 km (8000 lines) by 25 km (8000 columns). 5 to 500 Mbytes per Tile for 4 bands at 3.125 m pixel size after orthorectification.
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting).
Horizontal DatumWGS84
Map ProjectionUTM
Resampling KernelCubic Convolution

3.3.1 PlanetScope Visual Ortho Tile Product Specification

The PlanetScope Visual Ortho Tile product is orthorectified and color-corrected (using a color curve). This correction attempts to optimize colors as seen by the human eye providing images as they would look if viewed from the perspective of the satellite. It has been processed to remove distortions caused by terrain and can be used for cartographic mapping and visualization purposes. It eliminates the perspective effect on the ground (not on buildings), restoring the geometry of a vertical shot. Additionally, a correction is made to the sun angle in each image to account for differences in latitude and time of acquisition.

The Visual product is optimal for simple and direct use of the image. It is designed and made visually appealing for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. The product can be used and ingested directly into a Geographic Information System.

Table I: PlanetScope Visual Ortho Tile Product Attributes

Product AttributeDescription
Information Content
Visual Bands3-band natural color (red, green, blue)
Ground Sample Distance3.7 m (at reference altitude 475 km)
Processing
Pixel Size (orthorectified)3.125 m
Bit Depth8-bit
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model, bands are co-registered, and spacecraft-related effects are corrected using attitude telemetry and best available ephemeris data. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting) to <10 m m RMSE positional accuracy.
Positional Accuracy<10 m RMSE
Color EnhancementsEnhanced for visual use and corrected for sun angle.

3.3.2 PlanetScope Analytic Ortho Tile Product Specification

The PlanetScope Analytic Ortho Tile product is orthorectified, multispectral data from the satellite constellation. Analytic products are calibrated multispectral imagery products that have been processed to allow analysts to derive information products for data science and analytics. This product is designed for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. It has been processed to remove distortions caused by terrain and can be used for many data science and analytic applications. It eliminates the perspective effect on the ground (not on buildings), restoring the geometry of a vertical shot. The orthorectified visual imagery is optimal for value-added image processing including vegetation indices, land cover classifications, etc. In addition to orthorectification, the imagery has radiometric corrections applied to correct for any sensor artifacts and transformation to scaled at-sensor radiance.

Figure C: PlanetScope Analytic Ortho Tiles with RGB (left) and NIR False-Color Composite (right)

Table J: PlanetScope Analytic Ortho Tile Product Attributes

Product AttributeDescription
Information Content
Analytics Bands4-band multispectral image (blue, green, red, near-infrared)
Ground Sample Distance3.7 m (at reference altitude 475 km)
Processing
Pixel Size (orthorectified)3.125 m
Bit DepthAnalytic (DN): 12-bit, Analytic (Radiance): 16-bit
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model. Spacecraft-related effects are corrected using attitude telemetry and best available ephemeris data. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting) to <10 m RMSE positional accuracy.
Positional Accuracy<10 m RMSE
Radiometric Calibration Accuracy
  • Relative accuracy less than 15% @ 1 std deviation
  • Temporal and Inter-Sensor
  • Absolute accuracy per satellite less than 20% @ 1 std deviation

Figure D: PlanetScope Analytic Bands

4. RapidEye Imagery Products

RapidEye imagery products are available in two different processing levels to be directly applicable to customer needs.

Table K: RapidEye Satellite Image Product Processing Levels

NameDescriptionProduct Level
RapidEye Basic Scene ProductRadiometric and sensor corrections applied to the data. On-board spacecraft attitude and ephemeris applied to the data.Level 1B
RapidEye Ortho Tile ProductRadiometric and sensor corrections applied to the data. Imagery is orthorectified using the RPCs and an elevation model.Level 3A

TThe name of each acquired RapidEye image is designed to be unique and allow for easier recognition and sorting of the imagery. It includes the date and time of capture, as well as the id of the satellite that captured it. The name of each downloaded image product is composed of the following elements:

RapidEye Ortho Tiles: <tileid><acquisition_date><satellite_id><productLevel><productType>.<extension>

RapidEye Basic Scenes: <acquisition_date>_<satellite_id>_<productLevel>_<bandnumber>.<extension>

4.1 RapidEye Basic Scene Product Specification

The RapidEye Basic product is the least processed of the available RapidEye imagery products. This product is designed for customers with advanced image processing capabilities and a desire to geometrically correct the product themselves. This product line will be available in GeoTIFF and NITF formats.

The RapidEye Basic Scene product is radiometrically- and sensor-corrected, providing imagery as seen from the spacecraft without correction for any geometric distortions inherent in the imaging process, and is not mapped to a cartographic projection. The imagery data is accompanied by all spacecraft telemetry necessary for the processing of the data into a geo-corrected form, or when matched with a stereo pair, for the generation of digital elevation data. Resolution of the images is 6.5 meters GSD at nadir. The images are resampled to a coordinate system defined by an idealized basic camera model for band alignment.

The radiometric corrections applied to this product are:

  • Correction of relative differences of the radiometric response between detectors
  • Non-responsive detector filling which fills null values from detectors that are no longer responding
  • Conversion to absolute radiometric values based on calibration coefficients

The geometric sensor corrections applied to this product correct for:

  • Internal detector geometry which combines the two sensor chipsets into a virtual array
  • Optical distortions caused by sensor optics
  • Registration of all bands together to ensure all bands line up with each other correctly

The table below lists the product attributes for the RapidEye Basic Scene product.

Table L: RapidEye Basic Scene Product Attributes

Product AttributeDescription
Product Components and FormatRapidEye Basic Scene product consists of the following file components:
  • Image File – Image product delivered as a group of single-band NITF or GeoTIFF files with associated RPC values. Bands are co-registered.
  • Metadata File – XML format metadata file and GeoJSON metadata available
  • Unusable Data Mask (UDM) file – GeoTIFF format
  • Spacecraft information (SCI) file - XML format and contains additional information related to spacecraft attitude, spacecraft ephemeris, spacecraft temperature measurements, line imaging times, camera geometry, and radiometric calibration data.
  • Browse Image - GeoTIFF format
Product OrientationSpacecraft/Sensor Orientation
Product FramingGeographic based framing – a geographic region is defined by two corners. The product width is close to the full image swath as observed by all bands (77 km at nadir, subject to minor trimming of up to 3 km during processing) with a product length of between 50 and 300 km.
Ground Sample Distance (nadir)6.5 m
Bit Depth16-bit unsigned integers
Pixel Size (orthorectified)
  • Variable number of pixels (less than 11980 per line) and up to a maximum of 46154 lines per band.
  • 462 Mbytes/25 km along track for 5 bands.
  • Maximum 5544 Mbytes.
Geometric CorrectionsIdealized sensor, orbit and attitude models. Bands are co-registered.
Horizontal DatumWGS84
Map ProjectionN/A
Resampling KernelCubic Convolution

4.2 RapidEye Ortho Tile Product Specification

The RapidEye Ortho Tile products offer RapidEye Satellite imagery orthorectified as individual 25 km by 25 km tiles. This product was designed for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. It has been processed to remove distortions caused by terrain and can be used for many cartographic purposes.

The RapidEye Ortho Tile products are radiometrically-, sensor- and geometrically-corrected and aligned to a cartographic map projection. The geometric correction uses fine DEMs with a post spacing of between 30 and 90 meters. GCPs are used in the creation of every image and the accuracy of the product will vary from region to region based on available GCPs. RapidEye Ortho Tile products are output as 25 km by 25 km tiles referenced to a fixed, standard RapidEye image tile grid system.

The table below lists the product attributes for the RapidEye Ortho Tile product.

Table M: RapidEye Ortho Tile Product Attributes

Product AttributeDescription
Product Components and FormatRapidEye Ortho Tile product consists of the following file components:
  • Image File – GeoTIFF file that contains image data and geolocation information
  • Metadata File – XML format metadata file and GeoJSON metadata available
  • Thumbnail File – GeoTIFF format
  • Unusable Data Mask (UDM) File – GeoTIFF format
Product OrientationMap North Up
Product FramingRapidEye Ortho Tiles are based on a worldwide, fixed UTM grid system. The grid is defined in 24 km by 24 km tile centers, with 1 km of overlap (each tile has an additional 500 m overlap with adjacent tiles), resulting in 25 km by 25 km tiles.
Pixel Size (orthorectified)5 m
Bit DepthVisual: 8-bit, Analytic: 16-bit
Product SizeTile size is 25 km (5000 lines) by 25 km (5000 columns). 250 Mbytes per Tile for 5 bands at 5 m pixel size after orthorectification.
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model, bands are co-registered, and spacecraft-related effects are corrected using attitude telemetry and best available ephemeris data. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting).
Horizontal DatumWGS84
Map ProjectionUTM
Resampling KernelCubic Convolution

4.2.1 RapidEye Visual Ortho Tile Product Specification

The RapidEye Visual Ortho Tile product is orthorectified and color-corrected (using a color curve). This correction attempts to optimize colors as seen by the human eye providing images as they would look if viewed from the perspective of the satellite. It has been processed to remove distortions caused by terrain and can be used for cartographic mapping and visualization purposes. It eliminates the perspective effect on the ground (not on buildings), restoring the geometry of a vertical shot. Additionally, a correction is made to the sun angle in each image to account for differences in latitude and time of acquisition.

The Visual product is optimal for simple and direct use of the image. It is designed and made visually appealing for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. The product can be used and ingested directly into a Geographic Information System.

Below is a sample of a RapidEye Visual Ortho Tile:

Figure E: RapidEye Visual Ortho Tile

Table N: RapidEye Visual Ortho Tile Product Attributes

Product AttributeDescription
Information Content
Visual Bands3-band natural color (red, green, blue)
Ground Sample Distance6.5 m (at reference altitude 630 km)
Processing
Pixel Size (orthorectified)5 m
Bit Depth8-bit
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model, ban are co-registered, and spacecraft-related effects are corrected using attitude telemetry and best available ephemeris data. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting) to <10 m RMSE positional accuracy.
Positional Accuracy<10 m RMSE
Radiometric Corrections
  • Correction of relative differences of the radiometric response between detectors.
  • Non-responsive detector filling which fills nulls values from detectors that are no longer responding.
  • Conversion to absolute radiometric values based on calibration coefficients.
Color EnhancementsEnhanced for visual use and corrected for sun angle.

4.2.2 RapidEye Analytic Ortho Tile Product Specification

The RapidEye Analytic Ortho Tile product is orthorectified, multispectral data from the RapidEye satellite constellation. This product is designed for a wide variety of applications that require imagery with an accurate geolocation and cartographic projection. It has been processed to remove distortions caused by terrain and can be used for many data science and analytic applications. It eliminates the perspective effect on the ground (not on buildings), restoring the geometry of a vertical shot. The orthorectified imagery is optimal for value-added image processing including vegetation indices, land cover classifications, etc. In addition to orthorectification, the imagery has radiometric corrections applied to correct for any sensor artifacts and transformation to at-sensor radiance.

Table O: RapidEye Analytic Ortho Tile Product Attributes

Product AttributeDescription
Information Content
Analytics Bands5-band multispectral image (blue, green, red, red edge, near-infrared)
Ground Sample Distance6.5 m (at reference altitude 630 km)
Processing
Pixel Size (orthorectified)5 m
Bit Depth16-bit
Geometric CorrectionsSensor-related effects are corrected using sensor telemetry and a sensor model. Spacecraft-related effects are corrected using attitude telemetry and best available ephemeris data. Orthorectified using GCPs and fine DEMs (30 m to 90 m posting) to <10 m RMSE positional accuracy.
Positional Accuracy<10 m RMSE
Radiometric Calibration Accuracy
  • Correction of relative differences of the radiometric response between detectors.
  • Non-responsive detector filling which fills nulls values from detectors that are no longer responding.
  • Conversion to absolute radiometric values based on calibration coefficients.

5. Product Metadata

5.1 Ortho Tiles

5.1.1 PlanetScope

As mentioned in earlier sections, the Ortho Tile data in the Planet API will contain metadata in machine-readable GeoJSON and supported by standards-compliant GIS tools (e.g. GDAL and derivatives, JavaScript libraries). The product metadata is also provided in XML format.

The table below describes the GeoJSON metadata schema for PlanetScope Ortho Tile products:

Table P: PlanetScope Ortho Tile GeoJSON Metadata Schema

ParameterDescriptionType
acquiredThe RFC 3339 acquisition time of underlying imagery.string
anamolous_pixelsTPercentage of anomalous pixels. Pixels that have image quality issues documented in the quality taxonomy (e.g. hot columns). This is represented spatially within the UDM.number
black_fillRatio of image containing artificial black fill due to clipping to actual data.number (0 - 1)
cloud_coverRatio of the area covered by clouds to that which is uncovered.number (0 - 1)
columnsNumber of columns in the image.number
epsg_codeThe identifier for the grid cell that the imagery product is coming from if the product is an Ortho Tile (not used if Scene).number
grid_cellThe grid cell identifier of the gridded item.string
gsdThe ground sampling distance of the image acquisition.number
item_typeThe name of the item type that models shared imagery data schema.string (e.g. "PSOrthoTile")
origin_xULX coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
origin_yULY coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
pixel_resolutionPixel resolution of the imagery in meters.number
providerName of the imagery provider.string (e.g. "planetscope", "rapideye")
publishedThe RFC 3339 timestamp at which this item was added to the API.string
rowsNumber of rows in the imagery.number
satellite_idGlobally unique identifier of the satellite that acquired the underlying imagery.string
sun_azimuthAngle from true north to the sun vector projected on the horizontal plane in degrees.number (0 - 360)
sun_elevationElevation angle of the sun in degrees.number (0 - 90)
updatedThe RFC 3339 timestamp at which this item was updated in the API.string
usable_dataRatio of the usable to unusable portion of the imagery due to cloud cover or black fill.number (0 - 1)
view_angleSpacecraft across-track off-nadir viewing angle used for imaging, in degrees with + being east and - being west.number (-25 - 25)

5.1.2 RapidEye

The table below describes the GeoJSON metadata schema for RapidEye Ortho Tile products:

Table Q: RapidEye Ortho Tile GeoJSON Metadata Schema

ParameterDescriptionType
acquiredThe RFC 3339 acquisition time of underlying imagery.string
anamolous_pixelsPercentage of anomalous pixels. Pixels that have image quality issues documented in the quality taxonomy (e.g. hot columns). This is represented spatially within the UDM.number
black_fillRatio of image containing artificial black fill due to clipping to actual data.number (0 - 1)
cloud_coverRatio of the area covered by clouds to that which is uncovered.number (0 - 1)
columnsNumber of columns in the image.number
epsg_codeThe identifier for the grid cell that the imagery product is coming from if the product is an imagery tile (not used if scene).number
grid_cellThe grid cell identifier of the gridded item.string
gsdThe ground sampling distance of the image acquisition.number
item_typeThe name of the item type that models shared imagery data schema.string (e.g. "PSOrthoTile")
origin_xULX coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
origin_yULY coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
pixel_resolutionPixel resolution of the imagery in meters.number
providerName of the imagery provider.string (e.g. "planetscope", "rapideye")
publishedThe RFC 3339 timestamp at which this item was added to the API.string
rowsNumber of rows in the image.number
satellite_idGlobally unique identifier of the satellite that acquired the underlying imagery.string
sun_azimuthAngle from true north to the sun vector projected on the horizontal plane in degrees.number (0 - 360)
sun_elevationElevation angle of the sun in degrees.number (0 - 90)
updatedThe RFC 3339 timestamp at which this item was updated in the API.string
usable_dataRatio of the usable to unusable portion of the imagery due to cloud cover or black fill.number (0 - 1)
view_angleSpacecraft across-track off-nadir viewing angle used for imaging, in degrees with + being east and - being west.number (-25 - 25)

5.2 Ortho Scenes

5.2.1 PlanetScope

The tables below describe the GeoJSON metadata schema for PlanetScope Ortho Scene products:

Table R: PlanetScope Ortho Scene GeoJSON Metadata Schema

ParameterDescriptionType
acquiredThe RFC 3339 acquisition time of the image.string
anamolous_pixelsPercentage of anomalous pixels. Pixels that have image quality issues documented in the quality taxonomy (e.g. hot columns). This is represented spatially within the UDM.number
cloud_coverRatio of the area covered by clouds to that which is uncovered.number (0 - 1)
columnsNumber of columns in the image.number
epsg_codeThe identifier for the grid cell that the imagery product is coming from if the product is an imagery tile (not used if scene).number
gsdThe ground sampling distance of the image acquisition.number
instrumentThe generation of the satellite telescope.string (e.g. ”PS0”, “PS1”, ”PS2”)
item_typeThe name of the item type that models shared imagery data schema.string (e.g. “PSScene3Band”, ”PSScene4Band”)
origin_xULX coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
origin_yULY coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
pixel_resolutionPixel resolution of the imagery in meters.number
providerName of the imagery provider.string ("planetscope", "rapideye")
publishedThe RFC 3339 timestamp at which this item was added to the API.string
rowsNumber of rows in the image.number
satellite_idGlobally unique identifier of the satellite that acquired the underlying imagery.string
sun_azimuthAngle from true north to the sun vector projected on the horizontal plane in degrees.number (0 - 360)
sun_elevationElevation angle of the sun in degrees.number (0 - 90)
updatedThe RFC 3339 timestamp at which this item was updated in the API.string
usable_dataRatio of the usable to unusable portion of the imagery due to cloud cover or black fill.number (0 - 1)
view_angleSpacecraft across-track off-nadir viewing angle used for imaging, in degrees with + being east and - being west.number (-25 - 25)

5.3 Basic Scenes

5.3.1 PlanetScope

The following describes the GeoJSON metadata schema for PlanetScope Basic Scene products:

Table S: PlanetScope Basic Scene GeoJSON Metadata Schema

ParameterDescriptionType
acquiredThe RFC 3339 acquisition time of the image.string
anamolous_pixelsPercentage of anomalous pixels. Pixels that have image quality issues documented in the quality taxonomy (e.g. hot columns). This is represented spatially within the UDM.number
cloud_coverRatio of the area covered by clouds to that which is uncovered.number (0 - 1)
columnsNumber of columns in the image.number
epsg_codeThe identifier for the grid cell that the imagery product is coming from if the product is an imagery tile (not used if scene).number
gsdThe ground sampling distance of the image acquisition.number
instrumentThe generation of the satellite telescope.string (e.g. ”PS0”, “PS1”, ”PS2”)
item_typeThe name of the item type that models shared imagery data schema.string (e.g. “PSScene3Band”, ”PSScene4Band”)
origin_xULX coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
origin_yULY coordinate of the extent of the data. The coordinate references the top left corner of the top left pixel.number
pixel_resolutionPixel resolution of the imagery in meters.number
providerName of the imagery provider.string ("planetscope", "rapideye")
publishedThe RFC 3339 timestamp at which this item was added to the API.string
rowsNumber of rows in the image.number
satellite_idGlobally unique identifier of the satellite that acquired the underlying imagery.string
sun_azimuthAngle from true north to the sun vector projected on the horizontal plane in degrees.number (0 - 360)
sun_elevationElevation angle of the sun in degrees.number (0 - 90)
updatedThe RFC 3339 timestamp at which this item was updated in the API.string
usable_dataRatio of the usable to unusable portion of the imagery due to cloud cover or black fill.number (0 - 1)
view_angleSpacecraft across-track off-nadir viewing angle used for imaging, in degrees with + being east and - being west.number (-25 - 25)

5.3.2 RapidEye

The following describes the GeoJSON metadata schema for RapidEye Basic Scene products:

Table T: RapidEye Basic Scene GeoJSON Metadata Schema

ParameterDescriptionType
acquiredThe time that image was taken in ISO 8601 format, in UTC.string
areaArea covered by the image (excluding black_fill) in square kilometers.number
cloud_cover.estimatedThe estimated percentage of the image covered by clouds.number (0-100)
image_statistics.gsdThe ground sample distance (distance between pixel centers measured on the ground) of the image in meters.number
rapideye.black_fillThe percent of image pixels without valid image data.number (0-100)
rapideye.catalog_idThe base RapidEye Level 3A catalog id.string
rapideye.tile_idThe RapidEye tile id - corresponds to a fixed footprint.string
sat.altThe altitude of the satellite when the image was taken in kilometers.number
sat.idA unique identifier for the satellite that captured this image.string
sat.off_nadirThe angle off nadir in degrees at which the image was taken (absolute view angle).number
sat.view_angleThe view angle in degrees at which the image was taken.number
sat.azimuth_angleThe azimuth of the satellite from the imaged location at the time of capture in degrees.number
strip_idThe base RapidEye Level 1B catalog id.string
sun.altitudeThe altitude (angle above horizon) of the sun from the imaged location at the time of capture in degrees.number
sun_azimuthThe azimuth (angle clockwise from north) of the sun from the imaged location at the time of capture in degrees.number

6. Product Delivery

All imagery products are made available via Application Processing Interface (API) and Graphical User Interface (GUI).

6.1 Planet Application Programming Interface (API)

The Planet API offers REST API access that allows listing, filtering, and downloading of data to anyone using a valid API key. The metadata features described later in this document are all available in the responses to API queries. The full TIFF / GeoTIFF image data files are accessible (in the different product formats) at the /full URL endpoints.

Metadata associate with imagery products can be requested through the API endpoint: https://api.planet.com/data/v1/.

The table below shows a list of all the item types in the Data API:

Table U: Planet Data API - Item Types

Item TypeDescription
PSScene3BandPlanetScope 3-band Basic and Ortho Scenes. Scenes are framed as captured.
  • Analytic imagery band order: Band 1 = Red, Band 2 = Green, Band 3 = Blue
  • Visual imagery band order: Band 1 = Red, Band 2 = Green, Band 3 = Blue
PSScene4BandPlanetScope 4-band Basic and Ortho Scenes. Scenes are framed as captured.
  • Analytic imagery band order: Band 1 = Blue, Band 2 = Green, Band 3 = Red, Band 4 = Near-infrared
PSOrthoTilePlanetScope 4-band Ortho Tiles as 25 km x 25 km UTM Tiles.
  • Analytic imagery band order: Band 1 = Blue, Band 2 = Green, Band 3 = Red, Band 4 = Near-infrared
  • Visual imagery Band order: Band 1 = Red, Band 2 = Green, Band 3 = Blue
RESceneRapidEye 5-band Basic, scene-/strip- based framing.
  • Analytic imagery band order: Band 1 = Blue, Band 2 = Green, Band 3 = Red, Band 4 = Red edge, Band 5 = Near-infrared
REOrthoTileRapidEye 5-band Ortho Tiles as 25 km x 25 km UTM tiles.
  • Analytic imagery band order: Band 1 = Blue, Band 2 = Green, Band 3 = Red, Band 4 = Red edge, Band 5 = Near-infrared
  • Visual imagery band order: Band 1 = Red, Band 2 = Green, Band 3 = Blue

The table below shows a list of all the asset types in the Data API:

Table V: Planet Data API - Asset Types

Asset TypeDescription
browseVisual browse image for the Basic Scene product.
udmUsable Data Mask.
visualVisual product.
visual_xmlVisual product metadata in XML format.
analyticRadiometrically-calibrated imagery suitable for analytic applications.
analytic_dnNon-radiometrically calibrated imagery suitable for analytic applications.
analytic_xmlAnalytic product metadata in XML format.
analytic_dn_xmlPlanetScope 3-band (RGB) Analytic Ortho Scene metadata in an XML format.
basic_analyticPlanetScope 3-band (RGB) or 4-band (BGRN) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_sciRapidEye spacecraft information metadata in XML format.
basic_analytic_dnPlanetScope 3-band (RGB) 4-band (BGRN) Analytic DN Basic Sensor corrected - band or 4-band Basic Scene product, designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_xmlXML metadata for the Basic Analytic Product.
basic_analytic_dn_xmlPlanetScope 3-band (RGB) or 4-band (BGRN) Analytic DN Basic Scene metadata XML metadata.
basic_analytic_nitfPlanetScope 4-band (BGRN) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product stored in the NITF format, designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_rpcRational Polynomial Coefficients text file used to orthorectify the Basic Scene.
basic_analytic_rpc_nitfRational Polynomial Coefficients text file used to orthorectify the PlanetScope 4-band (BGRN) Analytic NITF Basic scene.
basic_analytic_dn_rpcRational Polynomial Coefficients text file used to orthorectify the PlanetScope 3-band (RGB) or 4-band (BGRN) Analytic DN Basic Scene.
basic_analytic_xml_nitfXML metadata for the NITF Basic Scene.
basic_analytic_dn_nitfPlanetScope 4-band (BGRN) Sensor corrected Basic Scene product stored in the NITF format, designed for users with advanced image processing and geometric correction capabilities. Scene based framing, stored in an NITF format, and not projected to a cartographic projection.
basic_analytic_dn_xml_nitfXML metadata for the PlanetScope 4-band (BGRN) Analytic DN NITF Basic Scene.
basic_analytic_dn_rpc_nitfRational Polynomial Coefficients text file used to orthorectify the PlanetScope 4-band (BGRN) Analytic DN NITF Basic scene.
basic_analytic_b1RapidEye Band 1 (Blue) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b2RapidEye Band 2 (Green) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b3RapidEye Band 3 (Red) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b4RapidEye Band 4 (Red Edge) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b5RapidEye Band 5 (Near-infrared) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b1_nitfRapidEye Band 1 (Blue) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product in the NITF format, designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b2_nitfRapidEye Band 2 (Green) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product in the NITF format, designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b3_nitfRapidEye Band 3 (Red) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product in the NITF format, designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b4_nitfRapidEye Band 4 (Red Edge) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product in the NITF format, designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_analytic_b5_nitfRapidEye Band 5 (Blue) scaled Top of Atmosphere Radiance (at sensor) and Sensor corrected, Basic Scene product in the NITF format, designed for users with advanced image processing and geometric correction capabilities. Scene based framing and not projected to a cartographic projection.
basic_udmUnusable Data Mask: Unusable data bit mask in GeoTIFF format for the Basic Scene product.

6.2 Planet Graphical User Interface (GUI)

Planet GUIs are a set of web-based tools that can be used to search Planet’s catalog of imagery, view metadata, and download full-resolution images. The interface and all of its features are built entirely on the externally available Planet API. The Planet Explorer Beta is the newest web-based GUI tool wih a redesigned search and discovery experience.

The link to the Planet Explorer Beta is: https://www.planet.com/explorer/

Planet’s GUI allows users to:

  • View Timelapse Mosaics: A user can view Planet’s quarterly and monthly mosaics for all of 2016, and can zoom in up to zoom level 12 (38 m / pixel per OpenStreetMap)
  • Search: A user can Search for any location or a specific area of interest by entering into the input box OR by uploading a geometry file (Shapefile, GeoJSON, KML, or WKT).
  • Save Search: The Save functionality allows a user to save search criteria based on area of interest, dates, and filters.
  • Filter: A user can filter by a specific date range and/or customizing metadata parameters (e.g. estimated cloud cover, GSD).
  • Zoom and Preview Imagery: Zoom and Preview allows a user to zoom in or out of the selected area and preview imagery.
  • View Imagery Details: A user can review metadata details about each imagery product.
  • Download: The Download icon allows a user to download imagery based on subscription type.
  • Draw Tools: These tools allow you to specify an area to see imagery results. The draw tool capabilities available are drawing a circle, drawing a rectangle, drawing a polygon, and/or limiting the size of the drawing to the size of loadable imagery.
  • Imagery Compare Tool: The Compare Tool allows you to compare sets of Planet imagery from different dates.

Planet also enables additional functionality in the form of “Labs,” which are demonstrations of capability made accessible to users through the GUI. Labs are active product features and will evolve over time based on Planet technology evolution and user feedback.

6.3 Planet Account Management Tools

As part of the Planet GUI, an administration and account management tool is provided. This tool is used to change user settings and to see past data orders. In addition, users who have administrator privileges will be able to manage users in their organization as well as review usage statistics.

The core functionality provided by account management tools are outlined below, and Planet may evolve Account Management tools over time to meet user needs:

  • User Accounts Overview: Every user account on the Planet Platform is uniquely identified by an email address. Each user also has a unique API key that can be used when interacting programmatically with the Platform.
  • Organization and Sub-organization Overview: Every user on the Planet Platform belongs to one organization. The Platform also supports “sub-organizations,” which are organizations that are attached to a “parent” organization. An administrator of a parent organization is also considered an administrator on all sub-organizations.
  • Account Privileges: Every user account on the Planet Platform has one of two roles: user or administrator. An administrator has elevated access and can perform certain user management operations or download usage metrics that are not available to standard users. An administrator of a parent organization is also considered an administrator on all sub-organizations. Administrators can enable or disable administrator status and enable or disable users’ access to the platform altogether.
  • Orders and Usage Review: This tool records all part orders made and allows users and administrators to view and download past orders. Usage metrics are also made available, including imagery products downloaded and bandwidth usage. Usage metrics are displayed for each individual API key that is part of the organization.

6.4 File Format

The Basic Scene products are available as NITF and GeoTIFFs; the Visual and Analytic Ortho Tile products are GeoTIFFs.

The Ortho Tile product GeoTIFFs are resampled at 3.125 m, and projected in the UTM projection using the WGS84 datum. An alpha mask is provided as a binary color channel. The alpha mask can be used to remove or hide low-image-quality pixels near the periphery of a given scene. The alpha mask compensates for effects due to vignetting, low SNR, or hot or cold pixels.

The Ortho Scene product GeoTIFFs are resampled at 3 m, and projected in the UTM projection using the WGS84 datum. An alpha mask is provided as a binary color channel. The alpha mask can be used to remove or hide low-image-quality pixels near the periphery of a given scene. The alpha mask compensates for effects due to vignetting, low SNR, or hot or cold pixels.

6.5 Bulk Delivery Folder Structure

Sets of imagery products can be ordered through the Planet API. The name of the parent folder is:

  • planet_order_[id]

Bulk deliveries are delivered in a .zip folder file format. Each .zip file contains:

  • A README file within formation about the order.
  • A subfolder for each scene requested named with the scene id.
  • Each subfolder contains the TIFF or GeoTIFF requested and an associated metadata file.
  • If basic data is requested,the subfolder will also contain an RPC text file.

7. Image Support Data

All PlanetScope and RapidEye Ortho Tile Products are accompanied by a set of image support data (ISD) files. These ISD files provide important information regarding the image and are useful sources of ancillary data related to the image. The ISD files are:

A. General XML Metadata File
B. Unusable Data Mask File

Each file is described along with its contents and format in the following sections.

7.1 General XML Metadata File

All PlanetScope and RapidEye Ortho Tile Products will be accompanied by a single general XML metadata file. This file contains a description of basic elements of the image. The file is written in Geographic Markup Language (GML) version 3.1.1 and follows the application schema defined in the Open Geospatial Consortium (OGC) Best Practices document for Optical Earth Observation products version 0.9.3, see http://www.opengeospatial.org/standards/gml.

The contents of the metadata file will vary depending on the image product processing level. All metadata files will contain a series of metadata fields common to all imagery products regardless of the processing level. However, some fields within this group of metadata may only apply to certain product levels. In ad- dition, certain blocks within the metadata file apply only to certain product types. These blocks are noted within the table.

The table below describes the fields present in the General XML Metadata file for all product levels.

Table W: General XML Metadata File Field Descriptions

General Metadata File Field Contents

FieldDescription
“metaDataProperty” Block
EarthObservationMetaData
IdentifierRoot file name of the image
statusStatus type of image, if newly acquired or produced from a previously archived image
downlinkedTo
acquisitionStationX-band downlink station that received image from satellite
acquisitionDateDate and time image was acquired by satellite
archivedIn
archivingCenterLocation where image is archived
archivingDateDate image was archived
archivingIdentifierCatalog ID of image
processing
processorNameName of ground processing system
processorVersionVersion of processor
nativeProductFormatNative image format of the raw image data
license
licenseTypeName of selected license for the product
resourceLinkHyperlink to the physical license file
versionIsdVersion of the ISD
orderIdOrder ID of the product
tileIdTile ID of the product corresponding to the Tile Grid
pixelFormatNumber of bits per pixel per band in the product image file.
"validTime" Block
TimePeriod
beginPositionStart date and time of acquisition for source image take used to create product, in UTC
endPositionEnd date and time of acquisition for source image take used to create product, in UTC
“using” Block
EarthObservationEquipment
platform
shortNameIdentifies the name of the satellite platform used to collect the image
serialIdentifierID of the satellite that acquired the data
orbitTypeOrbit type of satellite platform
instrument
shortNameIdentifies the name of the satellite instrument used to collect the image
sensor
sensorTypeType of sensor used to acquire the data.
resolutionSpatial resolution of the sensor used to acquire the image, units in meters
scanTypeType of scanning system used by the sensor
acquisitionParameters
orbitDirectionThe direction the satellite was trav- eling in its orbit when the image was acquired
incidenceAngleThe angle between the view direction of the satellite and a line perpendicular to the image or tile center.
illumination AzimuthAngleSun azimuth angle at center of product, in degrees from North (clockwise) at the time of the first image line
illumination ElevationAngleSun elevation angle at center of prod- uct, in degrees
azimuthAngleThe angle from true north at the image or tile center to the scan (line) direction at image center, in clockwise positive degrees.
spaceCraftView AngleSpacecraft across-track o -nadir view- ing angle used for imaging, in degrees with “+” being East and “-” being West
acquisitionDateTimeDate and Time at which the data was imaged, in UTC. Note: the imaging times will be somewhat di erent for each spectral band. This field is not intended to provide accurate image time tagging and hence is simply the imaging time of some (unspecified) part of the image.
“target” Block
Footprint
multiExtentOf
posListPosition listing of the four corners of the image in geodetic coordinates in the format: ULX ULY URX URY LRX LRY LLX LLY ULX ULY, where X = latitude and Y = longitude
centerOf
posPosition of center of product in geodetic coordinate X and Y, where X = latitude and Y = longitude
geographicLocation
topLeft
latitudeLatitude of top left corner in geodetic WGS84 coordinates
longitudeLongitude of top left corner in geodetic WGS84 coordinates
topRight
latitudeLatitude of top right corner in geodetic WGS84 coordinates
longitudeLongitude of top right corner in geodetic WGS84 coordinates
bottomLeft
latitudeLatitude of bottom left corner in geodetic WGS84 coordinates
longitudeLongitude of bottom left corner in geodetic WGS84 coordinates
bottomRight
latitudeLatitude of bottom right corner in geodetic WGS84 coordinates
longitudeLongitude of bottom right corner in geodetic WGS84 coordinates
“resultOf“ Block
EarthObservationResult
browse
BrowseInformation
typeType of browse image that accompanies the image product as part of the ISD
reference SystemIdentifierIdentifies the reference system used for the browse image
fileNameName of the browse image file
product
fileNameName of image file.
sizeThe size of the image product in kbytes
productFormatFile format of the image product
spatialReferenceSystem
epsgCodeEPSG code that corresponds to the datum and projection information of the image
geodeticDatumName of datum used for the map projection of the image
projectionProjection system used for the image
projectionZoneZone used for map projection
resamplingKernelResampling method used to produce the image. The list of possible algorithms is extendable.
numRowsNumber of rows (lines) in the image
numColumnsNumber of columns (pixels) per line in the image
numBandsNumber of bands in the image product
rowGsdThe GSD of the rows (lines) within the image product
columnGsdThe GSD of the columns (pixels) within the image product
radiometric CorrectionAppliedIndicates whether radiometric correction has been applied to the image
geoCorrectionLevelLevel of correction applied to the image
elevationCorrectionAppliedType of elevation correction applied to the image
atmosphericCorrectionAppliedIndicates whether atmospheric correction has been ap- plied to the image
atmosphericCorrectionParameters
autoVisibilityIndicates whether the visibility was automatically calculated or defaulted
aerosolTypeThe aerosol type used for atmospheric correction
waterVaporThe water vapor category used
hazeRemovalIndicates whether haze removal was performed
roughTerrainCorrectionIndicates whether rough terrain correction was performed
bRDFIndicates whether BRDF correction was performed
mask
MaskInformation
typeType of mask file accompanying the image as part of the ISD
formatFormat of the mask file
referenceSystemIdentifierEPSG code that corresponds to the datum and projection information of the mask file
fileNameFile name of the mask file
cloudCoverPercentageEstimate of cloud cover within the image
cloudCoverPercentageQuotationModeMethod of cloud cover determination
unusableDataPercentagePercent of unusable data with the file
The following group is repeated for each spectral band included in the image product
bandSpecificMetadata
bandNumberNumber (1-5) by which the spectral band is identified.
startDateTimeStart time and date of band, in UTC
endDateTimeEnd time and date of band, in UTC
percentMissingLinesPercentage of missing lines in the source data of this band
percentSuspectLinesPercentage of suspect lines (lines that contained downlink errors) in the source data for the band
binningIndicates the binning used (across track x along track)
shiftingIndicates the sensor applied right shifting
maskingIndicates the sensor applied masking
radiometricScaleFactorProvides the parameter to convert the pixel value to radiance (for radiance product) or reflectance (for a reflectance product). To convert to radiance/reflectance engineering units, the pixel values should be multiplied by this scale factor. Hence the pixel values in the product are:

Radiance product: (W/m2 sr μm) / (Radiometric Scale Factor). The Radiometric Scale Factor is expected to be 1/100. For instance, a product pixel value of 1510 would represent radiance units of 15.1 W/m2 sr μm.

Reflectance product: Percentage / (Radiometric Scale Factor). The Radiometric Scale Factor is expected to be 1/100. For instance, a product pixel value of 1510 would represent 15.1% reflectance.
The remaining metadata fields are only included in the file for L1B RapidEye Basic products
spacecraftInformationMetadataFileName of the XML file containing attitude, ephemeris and time for the 1B image
rpcMetadataFileName of XML file containing RPC information for the 1B image

File Naming

The General XML Metadata file will follow the naming conventions as in the example below.

Example: 2328007_2010-09-21_RE4_3A_visual_metadata.xml

7.2 Unusable Data Mask File

All PlanetScope and RapidEye Ortho Tile Products will be accompanied by an unusable data mask file.

The unusable data mask file provides information on areas of unusable data within an image (e.g. cloud and non-imaged areas). As mentioned previously, the pixel size after orthorectification will be 3.125 m for PlanetScope and 5 m for RapidEye. It is suggested that when using the file to check for usable data, a buffer of at least 1 pixel should be considered. Each bit in the 8-bit pixel identifies whether the corresponding part of the product contains useful imagery:

  • Bit 0: Identifies whether the area contains blackfill in all bands (this area was not imaged by the spacecraft). A value of “1” indicates blackfill.
  • Bit 1: Identifies whether the area is cloud covered. A value of “1” indicates cloud covered. Cloud detec- tion is performed on a decimated version of the image (i.e. the browse image) and hence small clouds may be missed. Cloud areas are those that have pixel values in the assessed band (Red, NIR or Green) that are above a configurable threshold. This algorithm will:
  • Assess snow as cloud;
  • Assess cloud shadow as cloud free;
  • Assess haze as cloud free.
  • Bit 2: Identifies whether the area contains missing (lost during downlink) or suspect (contains down- link errors) data in the Blue band. A value of “1” indicates missing/suspect data. If the product does not include this band, the value is set to “0”.
  • Bit 3: Identifies whether the area contains missing (lost during downlink and hence blackfilled) or sus- pect (contains downlink errors) data in the Green band. A value of “1” indicates missing/suspect data. If the product does not include this band, the value is set to “0”.
  • Bit 4: Identifies whether the area contains missing (lost during downlink) or suspect (contains down- link errors) data in the Red band. A value of “1” indicates missing/suspect data. If the product does not include this band, the value is set to “0”.
  • Bit 5: Identifies whether the area contains missing (lost during downlink) or suspect (contains downlink errors) data in the Red Edge band. A value of “1” indicates missing/suspect data. If the product does not include this band, the value is set to “0”.
  • Bit 6: Identifies whether the area contains missing (lost during downlink) or suspect (contains down- link errors) data in the NIR band. A value of “1” indicates missing/suspect data. If the product does not include this band, the value is set to “0”.
  • Bit 7: Is currently set to “0”.

Figure F: Concepts behind the Unusable Data Mask File

File Naming

The General XML Metadata file will follow the naming conventions as in the example below.

Example: 328007_2010-09-21_RE4_3A_visual_udm.tif

8. Tile Grid Definition

Ortho Tile imagery products are based on the UTM map grid as shown in the figures below. The grid is defined in 24 km by 24 km tile centers, with 1km of overlap, resulting in 25km by 25km tiles.

Figure G: Layout of UTM Zones

A RapidEye tile is named by the UTM zone number, the grid row number, and the grid column number within the UTM zone in the following format:

<ZZRRRCC>

where:

  • ZZ = UTM Zone Number (This eld is not padded with a zero for single digit zones in the tile shape le)
  • RRR = Tile Row Number (increasing from South to North, see Figure H)
  • CC = Tile Column Number (increasing from West to East, see Figure H)

Example:

  • Tile 547904 = UTM Zone = 5, Tile Row = 479, Tile Column = 04
  • Tile 3363308 = UTM Zone = 33, Tile Row = 633, Tile Column = 08

Figure H: Layout of Tile Grid within a single UTM Zone

Due to the convergence at the poles, the number of grid columns varies with grid row as illustrated in Figure H.

Figure I: Illustration of grid layout of Rows and Columns for a single UTM Zone

The center point of the tiles within a single UTM zone are defined in the UTM map projection to which standard transformations from UTM map coordinates (x,y) to WGS84 geodetic coordinates (latitude and longitude) can be applied.

  • col = 1 ... 29
  • row = 1 ... 780
  • Xcol = False Easting + (col –15) x Tile Width + Tile Width/2
  • Yrow = (row – 391) x Tile Height + Tile Height/2

where:

  • X and Y are in meters
  • False Easting = 500,000m
  • Tile Width = 24,000m
  • Tile Height = 24,000m

The numbers 15 and 391 are needed to align to the UTM zone origin.