Minimize POD Products and Requirements

The Precise Orbital products and auxiliary data generated by the Copernicus POD (Precise Orbit Determination) Service for the Sentinel-2 mission corresponds to NRT timeliness, having two different types of products.

  1. Near Real-Time orbital products (NRT) are generated based on immediate GPS L0 availability with the near real-time GPS orbits and clocks provided by EGP
  2. Near Real Time predicted (PRE) products are computed a certain time ahead of an astronomical event, particularly the ascending node crossing

Details on the official POD products are available in the File Format Specification document. A brief description of the POD products is included hereafter.

The NRT orbital product (AUX_RESORB) generation is associated to the availability of a new GPS L0 file (SAD PDI), which typically has coverage of an orbit. It contains the latest PVT in the GPS L0 file that triggered its generation plus 2 orbits backwards. Thus, the official POD NRT products for Sentinel-2 typically show overlaps between 1 or 2 orbits, depending on the coverage of the GPS L0.

The PRE orbital product (AUX_PREORB) is generated at least 90 minutes before the predicted ascending node crossing (ANX) and contains 5 state vectors at the node crossings (i.e., 2 orbits).

Each of these products has different timeliness and accuracy requirements, which are summarised in the following table:

Copernicus POD Sentinel-2 Orbital Files Requirements
Category Latency Orbit Accuracy
NRT Predicted
90 minutes before ANX 10 m (2D RMS 3-sigma)
30 minutes 3 m (3D RMS 1-sigma)

The timeliness and performance results of the precise orbital products are provided in the Quality Control section.

Additionally, the GNSS L1B RINEX files for Sentinel-2 are delivered on a daily basis to the PDGS with a latency of 7 days. These files contain the decoded GPS observations (pseudorange and carrier phase) following the International GNSS Service (IGS) RINEX ICD. The Sentinel-2 GNSS L1B RINEX data products are made available to the user community through the ESA Copernicus Open Access Hub.

Moreover, performing POD requires making use of the satellite attitude Quaternions files and validating the results obtained against an external reference solution. The user community can also find the Quaternions files on the ESA Copernicus Open Access Hub. At this moment, there are no precise orbit files available on the ESA Copernicus Open Access Hub from the CPOD Service.

If necessary, a preliminary Test Data Set (TDS) has been made available to the user community to perform a proper POD. The files for this TDS have been computed by the Copernicus POD Service for August 2018. A release note describing the TDS and where to find the inputs required to do POD is included in the TDS itself.