ESA UNCLASSIFIED – For Official Use esrin
Via Galileo Galilei
Casella Postale 64
00044 Frascati
Italy
T +39 06 9418 01
F +39 06 9418 0280
www.esa.int
GMES Sentinels Precise Orbit Determination (POD) Service: OFL POD Service and NRT POD
Facility File Format Specifications
GMES Sentinels POD Service File Format Specification [GMES-GSEG-EOPG-FS-10-0075] Issue1-3.doc
Prepared by
Reference
Issue
Revision
Date of Issue
Status
Document Type
Distribution
Sentinels POD Team
GMES-GSEG-EOPG-FS-10-0075
1
3
06/02/2013
Approved/Applicable
SD
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Title GMES Sentinels Precise Orbit Determination (POD) Service: OFL POD Service and NRT
POD Facility File Format Specifications
Issue 1
Revision 3
Author Sentinels POD Team
Date 06/05/2013
Approved by
Date
Pierre Féménias
06/05/2013
Reason for change
Creation first draft
Issue
0
Revision
1
Date
30/09/2010
Update after Comments from Sentinel-2 and 0
Sentinel-3 PDGS Teams
2
21/10/2010
Update to take into account the Sentinel-1 1
PDGS PDR RIDs and the new applicable
document named EEFF Tailoring for the
payload Data Ground Segment of the
Sentinel Missions [GMES-GSEG-EOPG-TN2010-0099]
0
10/01/2011
Update to take into account comments from 1
Sentinel-3 PDGS Team before the PDGS
PDR
1
28/02/2011
Update to take into account S-3 PDGS PDR 1
RIDs
2
15/06/2011
Update to take into account S-1 GS&PDGS 1
CDR RIDs
3
06/02/2013
Page 2/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Issue 0
Revision 2
Reason for change
Date
•
Included summary on POD Service and types 21/10/2010
of orbits
Pages
7
Paragraph(s)
1
•
Moved information (baseline and source)
from Fixed Header to Variable Header
16, 21, 27, 33
2.1.6.2, .2.6.2,
2.3.6.2, 2.4.8,
•
Sentinel-2
orbit
products:
included
3σ confidence for position accuracy and TBC
in naming convention
13, 19
2.1.4,2.1.5,
2.2.4, 2.2.5
•
Included details on Platform Data files for
Sentinel-3
48
4.3
•
Included footnote Table 1, column File Type
9
1.2
•
Clarification
on
description
GN_1_ROE_AX orbit file
38, 39, 40
2.5
•
Minor amendments and editorials
All
All
Pages
Paragraph(s)
of
Issue 1
Revision 0
Reason for change
Date
Document updated to take into account the 10/01/2011
Sentinel-1 PDGS PDR RIDs:
•
IF-36
47
4.2.1
•
IF-31
23
29
35
41
2.2.6.3, table 10
2.3.6.3, table 14
2.4.6.3, table 18
2.5.6.3, table 21
•
IF-32
23
28
33
38
3.2.1, 3.2.3
3.3.3
3.4.3
3.5.1, 3.5.3
•
IF-29
14
2.1.1
2.2.1
Page 3/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 20
26
32
38
2.3.1
2.4.1
2.5.1
2.1.1
•
IF-30
14
•
IF-35
18
23
28
33
Document updated to be in-line with the new
applicable document [AD-02] EEFF Tailoring
3.1.6.2
3.2.6.2
3.3.6.2
3.4.6.2
All pages on file All sections on
naming definition
file
naming
definition
for the payload Data Ground Segment of the
Sentinel
Missions
[GMES-GSEG-EOPG-TN-
2010-0099]
Issue 1
Revision 1
Reason for change
Date
Update to take into account comments from 28/02/2011
Sentinel-3 PDGS Team before the PDGS PDR
Pages
Paragraph(s)
•
Definition of the Site Centre, sub-field of the
Mandatory Prefix of the instance id, for S3
PDGS
15
2
•
Rewording of Predicted orbit file description
17
3.1.1
•
Reformatting of all tables
All
All
•
Added one column on Table 2 named
“Originator”
1, table 2
1.2
Update to take into account request from S-213/05/2011
PDGS Team: S2 MAIS Action ID #13315
•
C Format specification for Restituted Orbit
Files
Table 10, page 26
3.2.6.3
•
Inclusion of an example for S-2 Restituted
Orbit File
Page 28
3.2.6.5 (new)
Page 4/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Table 6, page 19, 20
3.1.6.3
Pages
Paragraph(s)
RID 149: S-3 NRT POD orbit file name and usage
43
3.5
RID 433: Platform File names
11, 16, 54, 55, 56, 58
1.2, 2, 4.3,
RID 575: Restituted Attitude in POD
53, 55-58
4.2
Pages
Paragraph(s)
•
RID PDGS-187: Time_Reference tag
Applies to all Sentinels
27, 29, 40, 42
3.1.6.2, 3.2.6.2,
3.2.6.4, 3.4.6.2,
3.4.6.4
•
RID PDGS-150: File version
Applies to all Sentinels
27, 39, 55
•
RID PDGS-152: Absolute orbit
Applies to all Sentinels
28, 41
Updated to ensure alignment with POD-S1PDGS
ICD (files coverage)
25, 38
Inconsistencies between files definitions and
examples solved.
55, 58
POD Restituted Attitude file format definition
and example aligned to EO CFI expected format
54-59
•
C Format specification for Predicted Orbit
Files
Issue 1
Revision 2
Reason for change
Date
Document updated to take into account the S-3 25/06/2011
PDGS PDR RIDs:
Issue 1
Revision 3
Reason for change
Date
Document updated to take into account the S-1 06/02/2013
GS&PDGS CDR RIDs:
3.1.6.1, 3.2.6.1,
3.3.6.1, 3.4.6.1,
3.1.6.3, 3.3.6.3,
3.5.6.3,
4.2.7,
4.3.7
3.2.6.3, 3.4.6.3
3.2.3, 3.4.3
4.2.7, 4.2.9.1
4.2
Page 5/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Table of contents:
Error! Not a valid heading level range.
Page 6/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Table of figures:
Figure 1: POD Service Products Overview ................................................................................................................................. 9 Figure 2: POD Service Orbit Products Structure .................................................................................................................... 16 Table of tables:
Table 1: POD Service Products and Auxiliary Data Files Overview vs Sentinels mission ...................................................... 10 Table 2: POD Service Products vs Sentinel Mission ................................................................................................................ 11 Table 3: Predicted Orbit File – Fixed Header ......................................................................................................................... 17 Table 4: Predicted Orbit File – Variable Header ..................................................................................................................... 18 Table 5: Predicted Orbit File – Data Block .............................................................................................................................. 18 Table 6: Predicted Orbit File – OSV ........................................................................................................................................ 18 Table 7 : Restituted Orbit File – Fixed Header ....................................................................................................................... 23 Table 8: Restituted Orbit File – Variable Header ................................................................................................................... 24 Table 9: Restituted Orbit File – Data Block ............................................................................................................................ 25 Table 10: Restituted Orbit File – OSV ..................................................................................................................................... 25 Table 11: MOE Orbit File – Fixed Header ............................................................................................................................... 29 Table 12: MOE Orbit File – Variable Header .......................................................................................................................... 31 Table 13: MOE Orbit File – Data Block ................................................................................................................................... 31 Table 14: MOE Orbit File – OSV.............................................................................................................................................. 31 Table 15 : POE Restituted Orbit File – Fixed Header ............................................................................................................. 36 Table 16: POE Orbit File – Variable Header ........................................................................................................................... 37 Table 17: POE Restituted Orbit File – Data Block................................................................................................................... 37 Table 18: POE Restituted Orbit File – OSV ............................................................................................................................. 37 Table 19: NRT Restituted orbit file – Fixed Header................................................................................................................ 43 Table 20: NRT Restituted Orbit File – Variable Header ........................................................................................................ 44 Table 21: NRT Restituted Orbit File – Data Block .................................................................................................................. 44 Table 22 : NRT Restituted Orbit File – OSV ........................................................................................................................... 44 Table 23 : GNSS USO Monitoring File – Fixed Header .......................................................................................................... 48 Table 24 : Attitude Restituted File – Fixed Header ................................................................................................................ 51 Table 25: Restituted Attitude File – Data Block...................................................................................................................... 53 Table 26: Restituted Attitude File – Quaternions Data .......................................................................................................... 53 Table 27: Restituted Attitude File – List of Quaternions Data ............................................................................................... 53 Table 28: Restituted Attitude File – Quaternions ................................................................................................................... 53 Table 29 : Preliminary and Precise Platform File – Fixed Header ......................................................................................... 58 Table 30: Preliminary and Precise Platform File – Data Block .............................................................................................. 59 Table 31: Preliminary and Precise Platform File – PTF .......................................................................................................... 59 Page 7/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 1
INTRODUCTION
The GMES Sentinel Missions (Sentinel-1, Sentinel-2 and Sentinel-3) will embark a common GPS
Receiver and the following types of orbits will be generated for each Sentinel mission:
•
On ground Precise Orbit Determination (POD) solutions
•
On-board Navigation solutions
The on ground POD solutions will be generated by the GMES Sentinels Precise Orbit
Determination (POD) Service, which will include the Off-line (OFL) POD Service and the NRT POD
Facility. The NRT POD Facility will be part of the Data Processing Ground Segment (PDGS) of
Sentinel-2 and Sentinel-3.
On ground solutions will be also generated by the FOS (i.e. predicted and restituted orbits) for the
three Sentinel Missions. The FOS orbit products will be passed to the OFL POD Service by the
PDGS and will be used for off-line monitoring purposes only. The FOS orbit products are not
described in this document.
The on-board navigation solutions will be used for processing S-1 and S-2 fast delivery products
and will be passed to the OFL POD Service by the PDGS for off-line monitoring purposes. The
format of the on-board navigation solutions are not described in this document.
The present document describes the format of all products and auxiliary data generated on ground
by the OFL POD Service and the NRT POD Facility.
1.1
Purpose and Scope
The purpose of the document is to define the product structure and the content of each file
generated and delivered by the OFL POD Service and the NRT POD Facility across its interfaces to
the Sentinels (1, 2 and 3) PDGSs.
For sake of simplicity, the products generated by the OFL POD Service and NRT POD Facility will
be referred in this document as “POD Service Products”.
1.2
POD Service Products Overview
This section provides an overview of the products and auxiliary files generated by the Sentinels
POD Service with indication on the Sentinel Mission applicability.
The POD Service will generate the following products, schematized in Figure 1:
1. POD Orbit Files, i.e. orbit state vectors (OSV) based on the orbit determination performed
by the POD Service based on the GPSR input data.
2. Auxiliary Files, i.e. products requested by the Sentinels Missions PDGSs to be used in
support to the Mission data processing
Page 8/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3. Quality Control Reports, i.e. reports containing the outcome of the quality control and long
term monitoring functionality of the POD Service
4. GNSS L1b files for Sentinel-3
Figure 1: POD Service Products Overview
Page 9/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Table 1 below summarizes the POD Service products with indication on the applicability of each
product to the Sentinel Mission.
Product
Type
POD Orbit
Files
GNSS L1b
files
Auxiliary
Files for
Sentinels
Quality
Control
Reports
Description
File Type
Predicted Orbit File
AUX_PREORB
Restituted Orbit File
AUX_RESORB
Medium Orbit Ephemerides
(MOE) Orbit File
AUX_MOEORB
Precise Orbit Ephemerides
(POE) Orbit File
AUX_POEORB
NRT Restituted Orbit File for
SENTINEL-3
ROE_AX
L1b files GNSS
TBD
GNSS USO Monitoring
AUX_GNSUSO
Attitude Restituted Data for
Sentinel-1
AUX_RESATT
Platform Data for Sentinel-3
AUX_PRLPTF
AUX_PRCPTF
Reports on the quality of the
POD Service Products
TBD
Sentinel-1
Sentinel-2
X
X
X
X
X
X
X
X
X
X
X
X
X
Table 1: POD Service Products and Auxiliary Data Files Overview vs Sentinels mission
Page 10/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Sentinel-3
X
ESA UNCLASSIFIED – For Official Use Table 2 below resumes the POD Service Products that will be generated for each Sentinel Mission.
It also provides information on the originator of the products, i.e. if generated by the OFL POD
Service or the NRT POD Facility.
Mission
Sentinel-1
Sentinel-2
Sentinel-3
POD Product
Originator
Restituted Orbit File
OFL POD
Precise Orbit Ephemerides (POE) Orbit File
OFL POD
Attitude Restituted Data
OFL POD
Reports on the quality of the POD products
OFL POD
Predicted Orbit File
NRT POD
Restituted Orbit File
NRT POD
Reports on the quality of the POD products
OFL POD
NRT Restituted Orbit File
NRT POD
Medium Orbit Ephemerides (MOE) Orbit File
OFL POD
Precise Orbit Ephemerides (POE) Orbit File
OFL POD
L1b files GNSS
OFL POD
GNSS USO Monitoring
OFL POD
Platform Data
OFL POD
Reports on the quality of the POD Products
OFL POD
Table 2: POD Service Products vs Sentinel Mission
1.3
Normative Reference Documents
[AD-1] Sentinel 3 PDGS File Naming Convention GMES-S3GS-EOPG-TN-09-0009
[AD-2] Earth Explorer File Format Tailoring for the Payload Data Ground Segment of the Sentinel
Missions GMES-GSEG-EOPG-TN-2010-0099
[AD-3] Earth Explorer Ground Segment File Format Standard PE-TN-ESA-GS-0001
1.4
Informative Reference Documents
[RD-1] Sentinels POD to Sentinel-1 PDGS Interface Control Document, GMES-GSEG-EOPG-IC-100063, Issue 0.1
[RD-2] Sentinel-1 PDGS to Sentinels POD Interface Control Document, GMES-GSEG-EOPG-IC-100076, Issue 0.1
[RD-3] A Quality Assurance Framework for Earth Observation - Key Guidelines, Version: 2.0 –
September 2008
Page 11/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 1.5
ASCII
DORIS
EEFFS
GMES
GNSS
GPSR
MOE
NRT
NTC
OFL
OSV
PDGS
POE
POD
RINEX
S-1
S-2
S-3
STC
SLR
TAI
TBC
TBD
UT1
UTC
XML
Acronyms
American Standard Code for Information Interchange
Doppler Orbitography and Radiopositioning Integrated by Satellite
Earth Explorer File Format Standard
Global Monitoring for Environment and Security
Global Navigation Satellite System
Global Positioning System Receiver
Medium Orbit Ephemerides
Near Real Time
Non Time Critical
Off-line
Orbit State Vector
Payload Data Ground Segment
Precise Orbit Ephemerides
Precise Orbit Determination
Receiver Independent Exchange Format
GMES Sentinel-1
GMES Sentinel-2
GMES Sentinel-3
Slow Time Critical
Satellite Laser Ranging
International Atomic Time
To Be Confirmed
To Be Defined
Universal Time
Coordinated Universal Time
eXtensible Markup Language
Page 12/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 2
NAMING CONVENTION
The applicable file naming convention for the files generated by the POD is the tailoring of the
Earth Explorer File Format Standard (EEFFS) for the Payload Data Ground Segment (PDGS) of the
Sentinel missions defined in [AD-2].
All files generated by the POD will follow the convention, apart from one file: the Sentinel-3 NRT
Restituted Orbit File, which follows the Sentinel-3 File naming convention defined in [AD-1].
The tailoring of the Earth Explorer File Format Standard (EEFFS) file naming is detailed below.
MMM_CCCC_TTTTTTTTTT_<instance_id>.EOF
The file name must be in the exact format as shown (characters shall only be in uppercase), where:
MMM
is the Mission ID, a 3 characters field alphanumeric defined as follows:
-
_
CCCC
_
TTTTTTTTTT
S1A, S1B (applicable to Sentinel 1A and Sentinel 1B), S1_ is
applicable to the constellation
- S2A, S2B (applicable to Sentinel 2A and Sentinel 2B), S2_ is
applicable to the constellation
- S3A, S3B (applicable to Sentinel 3A and Sentinel 3B), S3_ is
applicable to the constellation
is an underscore separator (1 character fixed string)
is the File Class. Allowed values are:
OPER for "Routine Operations" files
TEST for internal tests
REPx for reprocessing (x being a figure from 1 to n)
TDxx for processing Test Data Sets (xx=00..99)
is an underscore separator (1 character fixed string)
is the File Type field (10-characters) is subdivided into two sub-fields
as follows:
1. FFFF = File Category
To the maximum feasible extent, the File Category field shall be
shared across the Sentinels Missions from a default list, as defined
below:
• AUX_:
auxiliary data files;
• CNF_:
configuration files;
• LOG_:
log files;
• MPL_:
mission-planning files;
• REP_:
reporting
files
of
performed
operations
(acquisition, production, etc);
• etc
2. DDDDDD = Semantic Descriptor
Page 13/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use The Semantic Descriptor can be composed of uppercase letters,
digits or underscores “_”. The Semantic Descriptor is unique for a
given File Type and must be as descriptive as possible given the 6
character limitation to characterise the information contained by the
file.
For the POD Files, the following is defined:
•
•
•
•
•
•
•
•
< instance_id>
PREORB: Predicted Orbit File;
RESORB: Restituted orbit file;
MOEORB: Medium Orbit Ephemerides (MOE) Orbit File;
POEORB: Precise Orbit Ephemerides (POE) Orbit File;
GNSUSO: GNSS USO Monitoring File;
RESATT: Restituted Attitude Data for Sentinel-1;
PRLPTF: Preliminary Platform Data for Sentinel-3;
PRCPTF: Precise Platform Data for Sentinel-3;
The File Instance ID is used to define several sub-fields within the
filename according to the nature of the file. For usage for the Sentinel
PDGS, the File Instance ID is further decomposed into a set of
mandatory sub-fields in the prefix, complemented by optional ones in
the trailing portion of the filename
Mandatory Prefix:
The File Instance ID mandatory part is subdivided into sub-fields
as follows: ssss_yyyymmddThhmmss
where:
•
ssss is the Site Centre of the file originator:
-­‐
MPC_ is assigned to the Mission Performance
Centre of S-2 PDGS (where the NRT POD will be
deployed)
•
yyyymmddThhmmss is the Creation Date
Optional Sufix:
Based on every file-type, the optional suffix allows further
characterisation of the scope of every file as specifically relevant
to the type of file. The suffix may be simply omitted when
unnecessary to the defined file-type.
When applicable to the file-type, the optional suffix is appended
to the mandatory prefix starting with an underscore character
immediately followed by a one-character field defining the
specific tailoring of the remainder of the suffix from a list of welldefined options:
<optional-suffix> = _Ivvvvvvvv…
where :
Page 14/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use •
•
I is a one-character option Identifier (e.g. ‘V’, ‘B’, ‘D’, etc);
vvvvvvvv… contains the trailing Option Value.
Option_V – Applicability Time Period < Option_V suffix> =
_VyyyymmddThhmmss_YYYYMMDDTHHMMSS
where:
• yyyymmddThhmmss is the Validity Start Time
• YYYYMMDDTHHMMSS is the Validity Stop Time
Option_D – Data Source < Option_D suffix> = _Dvvv
Consisting in a one letter text indicating the source data. Allowed
values are:
• GNS for GNSS data
• G_D for GNSS + DORIS data
• GDS for GNSS + DORIS + SLR
• vvv (TBD) for any TBD combination of source data
AAA
3
is the file extension. Allowed values are: EOF
ORBIT FILES
The POD Service orbit products will follow the Earth Explorer File Format Standard [AD-3] and the
Tailoring of the Earth Explorer File Format Standard of the PDGS of the Sentinel missions defined
in [AD-2]. When no specific tailoring is described, the standard [AD-3] directly applies.
The format is applicable to all POD Service orbit products generated for the three Sentinel
Missions.
The POD Service orbit products structure is composed of a single file (*.EOF) containing both the
Header and the Datablock Sections. The Datablock section includes one Data set consisting of one
list of OSVs.
This structure is represented in the following figure:
Page 15/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Figure 2: POD Service Orbit Products Structure
3.1
PREDICTED ORBIT FILE (AUX_PREORB)
3.1.1
Description
This file contains the Orbit State Vectors (OSV) generated by the orbit determination process of the
POD Service. The OSV is calculated in Earth-fixed Coordinate Frame, whenever the S/C crosses the
J2000 equator. The OSVs are at epochs of ascending node crossings i.e. one per orbital revolution.
3.1.2
Dissemination
This product type will be delivered to the Sentinel-2 PDGS.
Page 16/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3.1.3
Data Latency/Coverage
The file will be made available within 90 minutes before Sentinel-2 ANX.
Frequency generation is TBD.
Each file covers the next orbit plus TBD orbits of predictions, starting at the generation time, and
contains TBD Orbit State Vector (OSV) per orbit.
3.1.4
Accuracy
Position accuracy is < 10m (2D) 3σ
3.1.5
Naming Convention
The applicable file naming convention is defined in [AD-2] and detailed in Section 2.
Example of a Predicted Orbit file name:
S2A_OPER_AUX_PREORB_MPC__20100101T000000_V20100101T010000_20100101T020000.EOF
3.1.6
Data Structure and Definition
The orbit prediction file is formatted using XML-tags. Each Predicted Orbit File consists of a single
file (*.EOF) containing both the Header and the Datablock sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
3.1.6.1 XML Fixed Header Section
Table 3: Predicted Orbit File – Fixed Header
XML Tag Name
(Level 1)
XML Tag
Name
(Level 2)
Value
File_Name
File_Description
Notes
Mission
File_Class
File_Type
Validity_Period
Page 17/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Description
As defined in Section 2 without the
extension.
POD Predicted Orbit
File
Variable
Sentinel-MU
Variable
AUX_PREORB
Free Text
11 characters string with the following
form: Sentinel-MU
where:
“Sentinel-“
is a fixed string;
M = the second character of the Mission ID
specified within the File Name (section 2);
U = the third character of the Mission ID
specified within the File Name (section 2).
Consistent with file class in Section 2
Same as File Type in Section 2
ESA UNCLASSIFIED – For Official Use Validity_Sta
rt
Variable
Validity_Sto
p
Variable
File_Version
UTC time consistent with Validity Start
Date in Section 2. Format:
UTC=yyyy-mm-ddThh:mm:ss
UTC time consistent with Validity Stop
Date in Section 2. Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of the File_Version field starts
from 0001 and increases by 1 every time a
new version of the same file is generated.
0001
Source
System
MPC_
A string with 4 characters. The System field
value must be equal to the File Name Site
Centre field value as defined in section 2
Corresponds to the facility deployed on the
Site Centre that generated the file: in this
case the NRT POD Facility deployed on the
MPC
Creator
NPOD
Creator_Ver
sion
Creation_Da
te
Variable
Variable
Date of creation. Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of this field must correspond to
the File Name Creation Date field defined
as part of the mandatory sub-fields of the
File Instance ID (Section 2)
3.1.6.2 Variable Header Section
Table 4: Predicted Orbit File – Variable Header
XML Tag Name
(Level 1)
Ref_Frame
Time_Reference
XML Tag Name
(Level 2)
Value
EARTH_FIXED
UTC
Description
Coordinate Frame ID
Time Reference ID
3.1.6.3 Data Block Section
One Data set consists of one list of OSVs in ASCII xml format.
Table 5: Predicted Orbit File – Data Block
XML Tag Name
Level 1
List_of_OSVs
Value
Description
list
See Table below for elements content.
Table 6: Predicted Orbit File – OSV
Page 18/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use XML
Name
TAI
Tag
Type
Unit
date
string
UTC
date
string
UT1
date
string
Absolute_Orbit
int
X
Y
Z
VX
VY
VZ
Quality
float
float
float
float
float
float
String
m
m
m
m/s
m/s
m/s
Page 19/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use C Format
Description
TAI date and time of OSV, in ASCII standard time
format, including time reference and microseconds.
TAI=yyyy-mm-ddThh:mm:ss.ssssss
UTC date and time of OSV, in ASCII standard time
format,
including
time
reference
and
microseconds.
UTC=yyyy-mm-ddThh:mm:ss.ssssss
UT1 date and time of OSV, in ASCII standard time
format,
including
time
reference
and
microseconds.
UT1=yyyy-mm-ddThh:mm:ss.ssssss
%+05ld
Absolute orbit counter
This counter is incremented by a single unit
when crossing the earth-fixed ascending node..
%+012.3lf
%+012.3lf
%+012.3lf
%+012.6lf
%+012.6lf
%+012.6lf
TBD
X position in earth-fixed coordinate system.
Y position in earth-fixed coordinate system.
Z position in earth-fixed coordinate system.
X velocity in earth-fixed coordinate system.
Y velocity in earth-fixed coordinate system.
Z velocity in earth-fixed coordinate system.
ESA UNCLASSIFIED – For Official Use 3.1.6.4 Example of a File
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name> S2A_OPER_AUX_PREORB_MPC__20071116T130432_V20160306T000000_20160313T010000</File_Name>
<File_Description>Predicted Orbit File</File_Description>
<Notes></Notes>
<Mission>Sentinel-2A</Mission>
<File_Class>OPER</File_Class>
<File_Type>AUX_PREORB</File_Type>
<Validity_Period>
<Validity_Start>UTC=2016-03-06T00:00:00</Validity_Start>
<Validity_Stop>UTC=2016-03-13T01:00:00</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>MPC_</System>
<Creator>NPOD</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=2007-11-16T13:04:32</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
<Ref_Frame>EARTH-FIXED</Ref_Frame>
<Time_Reference>UTC</Time_Reference>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<List_of_OSVs count="110">
<OSV>
<TAI>TAI=2016-03-06T00:36:53.959000</TAI>
<UTC>UTC=2016-03-06T00:36:19.959000</UTC>
<UT1>UT1=2016-03-06T00:36:20.068000</UT1>
<Absolute_Orbit>+42244</Absolute_Orbit>
<X unit="m">-1069530.706</X>
<Y unit="m">-6689213.247</Y>
<Z unit="m">+0002623.994</Z>
<VX unit="m/s">-1410.364622</VX>
<VY unit="m/s">+0238.533479</VY>
<VZ unit="m/s">+7615.362798</VZ>
<Quality>0000000000000</Quality>
</OSV>
<OSV>
<TAI>TAI=2016-03-06T02:09:22.659000</TAI>
<UTC>UTC=2016-03-06T02:08:48.659000</UTC>
Page 20/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use <UT1>UT1=2016-03-06T02:08:48.768000</UT1>
<Absolute_Orbit>+42245</Absolute_Orbit>
<X unit="m">-3610035.328</X>
<Y unit="m">-5731945.800</Y>
<Z unit="m">+0002614.761</Z>
<VX unit="m/s">-1203.476302</VX>
<VY unit="m/s">+0773.248416</VY>
<VZ unit="m/s">+7615.498893</VZ>
<Quality>0000000000000</Quality>
</OSV>
</List_of_OSVs>
</Data_Block>
</Earth_Explorer_File>
Page 21/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3.2
RESTITUTED ORBIT FILE (AUX_RESORB)
3.2.1
Description
This file contains the restituted Orbit State Vectors (OSV) based on the orbit determination
performed by the POD Service. The OSVs frequency will be of 10 seconds (TBC). The State Vectors
will be in Earth-fixed reference.
3.2.2
Dissemination
The file will be made available to the PDGS of Sentinel-1 and Sentinel-2 and will be used for
generating Sentinel-1 and Sentinel-2 Mission products.
3.2.3
Data Latency/Coverage
For Sentinel-1 the file will be generated within 3 hours (from reception of GNSS data in the POD
server). The file coverage will be one satellite orbit, from ascending node ANX plus an overlap of 5
OSV (configurable) before and after the satellite orbit time span. The values of the overlapping OSV
will be the same in two consecutive files.
For Sentinel-2 the file will be generated within 30 minutes (from reception of GNSS data in the
POD server). The file coverage will be equal to the latest PVT contained within the received satellite
ancillary data that triggers such generation with 2 orbits [TBC] backwards. 5 OSV (TBC) will be
added after the period of the latest PVT. The values of the overlapping OSV will be the same in two
consecutive files.
3.2.4
Accuracy
For Sentinel-1 the accuracy will be < 10 cm (2D) 3 σ
For Sentinel-2 the accuracy will be < 3m (3D) 3 σ
3.2.5
Naming Convention
The applicable file naming convention is defined in [AD-2] and detailed in Section 2.
Example of Restituted Orbit File names for Sentinel-1 and Sentinel-2 Missions:
S1A_OPER_AUX_RESORB_OPOD_20100101T000000_V20100101T010000_20100101T020000.EOF
S2A_OPER_AUX_RESORB_MPC__20100101T000000_V20100101T010000_20100101T020000.EOF
Page 22/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3.2.6
Data Structure and Definition
The Restituted orbit file is formatted using XML-tags and has the same format as the orbit
prediction file. Each Restituted Orbit File consists of a single file (*.EOF) containing both the
Header and the Datablock Sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
3.2.6.1 XML Fixed Header Section
Table 7 : Restituted Orbit File – Fixed Header
XML Tag Name
(Level 1)
File_Name
XML Tag Name
(Level 2)
Value
Description
As defined in Section 2
without the extension.
File_Description
Notes
Mission
POD Restituted
Orbit File
Variable
Sentinel-MU
File_Class
Variable
File_Type
AUX_RESORB
Free Text
11 characters string with the
following form: SentinelMU
where:
“Sentinel-“
is a fixed
string;
M = the second character of
the Mission ID specified
within the File Name
(section 2);
U = the third character of
the Mission ID specified
within the File Name
(section 2).
Consistent with file class in
Section 2
Same as File Type in
Section 2
Validity_Period
Validity_Start
Variable
Validity_Stop
Variable
Page 23/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use UTC time consistent with
Validity Start Date in
Section 2 Format:
UTC=yyyy-mmddThh:mm:ss
UTC time consistent with
Validity Stop Date in
ESA UNCLASSIFIED – For Official Use File_Version
0001
Section 2. Format:
UTC=yyyy-mmddThh:mm:ss
The value of the
File_Version field starts
from 0001 and increases by
1 every time a new version
of the same file is
generated.
Source
System
Variable
Creator
Variable
Creator_Version
Creation_Date
Variable
Variable
A string with 4 characters.
The System field value must
be equal to the File Name
Site Centre field value as
defined in section 2
Corresponds to the facility
deployed on the Site Centre
that generated the file
(NPOD for the NRT POD
Facility and OPOD for the
Facility of the OFL POD
Service)
Date of creation. Format:
UTC=yyyy-mmddThh:mm:ss
The value of this field must
correspond to the File
Name Creation Date field
defined as part of the
mandatory sub-fields of the
File Instance ID (Section 2)
3.2.6.2 Variable Header Section
Table 8: Restituted Orbit File – Variable Header
XML Tag Name
(Level 1)
Ref_Frame
Time_Reference
XML Tag Name
(Level 2)
Value
EARTH_FIXED
UTC
3.2.6.3 Data Block Section
One Data set consists of one list of OSVs in ASCII xml format.
Page 24/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Description
Coordinate Frame ID
Time Reference ID
ESA UNCLASSIFIED – For Official Use Table 9: Restituted Orbit File – Data Block
XML Tag
Name
Level 1
List_of_OSVs
Value
Description
list
See Table below for elements content.
Table 10: Restituted Orbit File – OSV
XML Tag
Name
Type
Unit
TAI
date
string
UTC
date
string
UT1
date
string
C
Format
TAI date and time of OSV, in ASCII
standard time format, including time
reference and micro-seconds.
TAI=yyyy-mm-ddThh:mm:ss.ssssss
UTC date and time of OSV, in ASCII
standard time format, including time
reference and microseconds.
UTC=yyyy-mm-ddThh:mm:ss.ssssss
UT1 date and time of OSV, in ASCII
standard time format, including time
reference and microseconds.
Absolute_Orbit
int
%+05ld
X
float
m
%+012.3lf
Y
float
m
%+012.3lf
Z
float
m
%+012.3lf
VX
float
m/s
%+012.6lf
VY
float
m/s
%+012.6lf
VZ
float
m/s
%+012.6lf
Quality
String
String
TBD
Page 25/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Description
UT1=yyyy-mm-ddThh:mm:ss.ssssss
Absolute orbit counter
This counter is incremented by a single
unit when crossing the earth-fixed
ascending node.
X position in earth-fixed coordinate
system.
Y position in earth-fixed coordinate
system.
Z position in earth-fixed coordinate
system.
X velocity in earth-fixed coordinate
system.
Y velocity in earth-fixed coordinate
system.
Z velocity in earth-fixed coordinate
system.
ESA UNCLASSIFIED – For Official Use 3.2.6.4 Example of a File for Sentinel-1
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name>S1A_OPER_AUX_RESORB_OPOD_20120101T030000_V20111231T215720_20111231T233730</File_Name>
<File_Description>POD Restituted Orbit File</File_Description>
<Notes></Notes>
<Mission>Sentinel-1A</Mission>
<File_Class>OPER</File_Class>
<File_Type>AUX_RESORB</File_Type>
<Validity_Period>
<Validity_Start>UTC=2011-12-31T21:57:20</Validity_Start>
<Validity_Stop>UTC=2011-12-31T23:37:30</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>OPOD</System>
<Creator>OPOD</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=2012-01-01T03:00:00</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
<Ref_Frame>EARTH_FIXED</Ref_Frame>
<Time_Reference>UTC</Time_Reference>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<List_of_OSVs count="602">
<OSV>
<TAI>TAI=2011-12-31T21:57:54.000000</TAI>
<UTC>UTC=2011-12-31T21:57:20.000000</UTC>
<UT1>UT1=2011-12-31T21:57:20.000002</UT1>
<Absolute_Orbit>+01767</Absolute_Orbit>
<X unit="m">+3647461.238</X>
<Y unit="m">-6055786.165</Y>
<Z unit="m">-0333545.604</Z>
<VX unit="m/s">-1181.021623</VX>
<VY unit="m/s">-1110.141649</VY>
<VZ unit="m/s">+7421.878362</VZ>
<Quality>0000000000000</Quality>
</OSV>
<OSV>
<TAI>TAI=2011-12-31T21:58:04.000000</TAI>
<UTC>UTC=2011-12-31T21:57:30.000000</UTC>
Page 26/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use <UT1>UT1=2011-12-31T21:57:30.000002</UT1>
<Absolute_Orbit>+01767</Absolute_Orbit>
<X unit="m">+3635438.930</X>
<Y unit="m">-6066539.396</Y>
<Z unit="m">-0259309.274</Z>
<VX unit="m/s">-1223.397364</VX>
<VY unit="m/s">-1040.464602</VY>
<VZ unit="m/s">+7425.224765</VZ>
<Quality>0000000000000</Quality>
</OSV>
…
</List_of_OSVs>
</Data_Block>
</Earth_Explorer_File>
3.2.6.5 Example of a File for Sentinel-2
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name> S2A_OPER_AUX_RESORB_MPC__20100101T000000_V20160306T000000_20160313T010000</File_Name>
<File_Description>POD Restituted Orbit File</File_Description>
<Notes></Notes>
<Mission> Sentinel-2A</Mission>
<File_Class>OPER</File_Class>
<File_Type>AUX_RESORB</File_Type>
<Validity_Period>
<Validity_Start>UTC=2016-03-06T00:00:00</Validity_Start>
<Validity_Stop>UTC=2016-03-13T01:00:00</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>MPC_</System>
<Creator>NPOD</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=2010-01-01T00:00:00</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
<Ref_Frame>EARTH-FIXED</Ref_Frame>
<Time_Reference>UTC</Time_Reference>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<List_of_OSVs count="10141">
<OSV>
<TAI>TAI=2016-03-06T00:00:34.000000</TAI>
Page 27/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use <UTC>UTC=2016-03-06T00:00:00.000000</UTC>
<UT1>UT1=2016-03-06T00:00:00.109000</UT1>
<Absolute_Orbit>+42243</Absolute_Orbit>
<X unit="m">+0519641.779</X>
<Y unit="m">+5278659.929</Y>
<Z unit="m">-4220599.988</Z>
<VX unit="m/s">+1113.622468</VX>
<VY unit="m/s">-4842.338815</VY>
<VZ unit="m/s">-5925.935594</VZ>
<Quality>0000000000000</Quality>
</OSV>
<OSV>
<TAI>TAI=2016-03-06T00:01:34.000000</TAI>
<UTC>UTC=2016-03-06T00:01:00.000000</UTC>
<UT1>UT1=2016-03-06T00:01:00.109000</UT1>
<Absolute_Orbit>+42243</Absolute_Orbit>
<X unit="m">+0583912.227</X>
<Y unit="m">+4975970.019</Y>
<Z unit="m">-4566150.959</Z>
<VX unit="m/s">+1027.326972</VX>
<VY unit="m/s">-5243.308832</VY>
<VZ unit="m/s">-5588.035384</VZ>
<Quality>0000000000000</Quality>
</OSV>
…
</List_of_OSVs>
</Data_Block>
</Earth_Explorer_File>
Page 28/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3.3
MEDIUM ORBIT EPHEMERIDES (MOE) ORBIT FILE (AUX_MOEORB)
3.3.1
Description
This file contains the Medium Orbit Ephemerides (MOE), corresponding to the Preliminary
Restituted Orbit State Vectors (OSV) based on the orbit determination performed by the POD
Service. The State Vectors will be in Earth-fixed reference.
3.3.2
Dissemination
The file will be made available to the Sentinel-3 PDGS and will be used for generating Level 2 SRAL
STC Mission products.
3.3.3
Data Latency/Coverage
One file will be generated per day covering approximately 26 hours: 1 26-hours file per day (d) for
extrapolated and restituted MOE – Data for d-2 22h to d-1 24h.
Each file contains OSVs at fixed time steps of 10 seconds interval (TBC). (The time intervals are
configurable.)
3.3.4
Accuracy
The accuracy will be 4 cm threshold with a target of 3cm (Radial).
3.3.5
Naming Convention
The applicable file naming convention is defined in [AD-2] and detailed in Section 2.
Example of a MOE Orbit file
name:S3A_OPER_AUX_MOEORB_OPOD_20100101T000000_V20100101T010000_20100101T020000_DGNS.EOF
3.3.6
Data Structure and Definition
The Medium Orbit Ephemeride (MOE) Restituted orbit file is formatted using XML-tags and has
the same format as the orbit prediction file. Each MOE Restituted Orbit File consists of a single file
(*.EOF) containing both the Header and the Datablock Sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
3.3.6.1 XML Fixed Header Section
Table 11: MOE Orbit File – Fixed Header
XML Tag Name
(Level 1)
XML Tag Name
(Level 2)
Page 29/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Value
Description
ESA UNCLASSIFIED – For Official Use File_Name
As defined in Section 2 without
the extension.
File_Description
Notes
Mission
POD MOE
Restituted
Orbit File
Variable
Sentinel-MU
File_Class
Variable
File_Type
POD#ORBMO
E
Free Text
11 characters string with the
following form: Sentinel-MU
where:
“Sentinel-“
is
a
fixed
string;
M = the second character of the
Mission ID specified within the
File Name (section 2);
U = the third character of the
Mission ID specified within the
File Name (section 2).
Consistent with file class in
Section 2
Same as File Type in Section 2
Validity_Period
Validity_Start
Variable
Validity_Stop
Variable
File_Version
0001
UTC time consistent with
Validity Start Date in Section 2
Format:
UTC=yyyy-mm-ddThh:mm:ss
UTC time consistent with
Validity Stop Date in Section 2.
Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of the File_Version
field starts from 0001 and
increases by 1 every time a new
version of the same file is
generated.
Source
System
OPOD
Creator
OPOD
Creator_Version
Creation_Date
Variable
Variable
Page 30/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use A string with 4 characters. The
System field value must be
equal to the File Name Site
Centre field value as defined in
section 2
Corresponds to the facility
deployed on the Site Centre that
generated the file
Date of creation. Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of this field must
ESA UNCLASSIFIED – For Official Use correspond to the File Name
Creation Date field defined as
part of the mandatory subfields of the File Instance ID
(Section 2)
3.3.6.2 Variable Header Section
Table 12: MOE Orbit File – Variable Header
XML Tag Name
(Level 1)
Source Data
XML Tag Name
(Level 2)
Value
Variable
Ref_Frame
Time_Reference
EARTH_FIXED
UTC
Description
Same as Optional Suffix Data
Source Section 2.
Coordinate Frame ID
Time Reference ID
3.3.6.3 Data Block Section
One Data set consists of one list of OSVs in ASCII xml format
Table 13: MOE Orbit File – Data Block
XML Tag Name
Level 1
List_of_OSVs
Value
Description
list
See Table below for elements content.
Table 14: MOE Orbit File – OSV
XML Tag
Name
TAI
Type
Unit
Description
date
string
UTC
date
string
UT1
date
string
TAI date and time of OSV, in ASCII standard time format,
including time reference and micro-seconds.
TAI=yyyy-mm-ddThh:mm:ss.ssssss
UTC date and time of OSV, in ASCII standard time
format, including time reference and microseconds.
UTC=yyyy-mm-ddThh:mm:ss.ssssss
UT1 date and time of OSV, in ASCII standard time format,
including time reference and microseconds.
UT1=yyyy-mm-ddThh:mm:ss.ssssss
Absolute_Orbit
int
X
Y
Z
VX
float
float
float
float
Absolute orbit counter
This counter is incremented by a single unit when
crossing the earth-fixed ascending node.
m
m
m
m/s
Page 31/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use X position in earth-fixed coordinate system.
Y position in earth-fixed coordinate system.
Z position in earth-fixed coordinate system.
X velocity in earth-fixed coordinate system.
ESA UNCLASSIFIED – For Official Use VY
VZ
Quality
float
float
String
m/s
m/s
Page 32/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Y velocity in earth-fixed coordinate system.
Z velocity in earth-fixed coordinate system.
ESA UNCLASSIFIED – For Official Use 3.3.6.4 Example of a File
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name> S3A_OPER_AUX_MOEORB_OPOD_20100101T000000_V20160306T0000000_20160313T010000_DGNS</File_Name>
<File_Description>POD MOE Restituted Orbit File</File_Description>
<Notes></Notes>
<Mission> Sentinel 3</Mission>
<File_Class>OPER</File_Class>
<File_Type>AUX_MOEORB</File_Type>
<Validity_Period>
<Validity_Start>UTC=2016-03-06T00:00:00</Validity_Start>
<Validity_Stop>UTC=2016-03-13T01:00:00</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>OPOD</System>
<Creator>OPOD</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=2010-01-01T00:00:00</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
<Source Data>DGNS</Source Data>
<Ref_Frame>EARTH-FIXED</Ref_Frame>
<Time_Reference>UTC</Time_Reference>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<List_of_OSVs count="10141">
<OSV>
<TAI>TAI=2016-03-06T00:00:34.000000</TAI>
<UTC>UTC=2016-03-06T00:00:00.000000</UTC>
<UT1>UT1=2016-03-06T00:00:00.109000</UT1>
<Absolute_Orbit>+42243</Absolute_Orbit>
<X unit="m">+0519641.779</X>
<Y unit="m">+5278659.929</Y>
<Z unit="m">-4220599.988</Z>
<VX unit="m/s">+1113.622468</VX>
<VY unit="m/s">-4842.338815</VY>
<VZ unit="m/s">-5925.935594</VZ>
<Quality>0000000000000</Quality>
</OSV>
<OSV>
<TAI>TAI=2016-03-06T00:01:34.000000</TAI>
Page 33/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use <UTC>UTC=2016-03-06T00:01:00.000000</UTC>
<UT1>UT1=2016-03-06T00:01:00.109000</UT1>
<Absolute_Orbit>+42243</Absolute_Orbit>
<X unit="m">+0583912.227</X>
<Y unit="m">+4975970.019</Y>
<Z unit="m">-4566150.959</Z>
<VX unit="m/s">+1027.326972</VX>
<VY unit="m/s">-5243.308832</VY>
<VZ unit="m/s">-5588.035384</VZ>
<Quality>0000000000000</Quality>
</OSV>
…
</List_of_OSVs>
</Data_Block>
</Earth_Explorer_File>
Page 34/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3.4
Precise ORBIT EPHEMERIDES (POE) ORBIT FILE (AUX_POEORB)
3.4.1
Description
This file contains the Precise Orbit Ephemerides (POE) Restituted Orbit State Vectors (OSV) based
on the orbit determination performed by the POD Service. The State Vectors will be in Earth-fixed
reference.
3.4.2
Dissemination
The file will be made available to the PDGS of Sentinel-1 and Sentinel-3 and will be used for
supporting the generation of the following Mission Products:
•
Sentinel-1 off-line SAR Mission Products
•
Sentinel-3 Level 2 SRAL NTC Mission Products.
3.4.3
Data Latency/Coverage
Sentinel-1:
Each file covers approximately 28 hours (one complete day plus 2 hours overlap at start and
end) and contains OSVs at fixed time steps of 10 seconds intervals (TBC). (The time intervals
are configurable)
Files frequency generation: One file per day.
Files will be delivered within 20 days after data acquisition.
Sentinel-3:
Each file covers approximately 26 hours and contains OSVs at fixed time steps of 10 seconds
intervals (TBC). (The time intervals are configurable.).
Files frequency generation: n+1 26-hours files per n-days (sub) cycle.
Files will be delivered within 20 days after data acquisition.
3.4.4
Accuracy
5 cm (3D) for Sentinel-1 files
3 cm (Radial) threshold with a target of 2cm for Sentinel-3 files
3.4.5
Naming Convention
The applicable file naming convention is defined in [AD-2] and detailed in Section 2.
Example of POE Orbit File names for Sentinel-1 and Sentinel-3 Missions:
S1A_OPER_AUX_POEORB_OPOD_20100101T000000_V20100101T010000_20100101T020000.EOF
S3A_OPER_AUX_POEORB_OPOD_20100101T000000_V20100101T010000_20100101T020000_DGNS.EOF
Page 35/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3.4.6
Data Structure and Definition
The Precise Orbit Ephemeride (POE) Restituted orbit file is formatted using XML-tags and has the
same format as the orbit prediction file. Each POE Restituted Orbit File consists of a single file
(*.EOF) containing both the Header and the Datablock Sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
3.4.6.1 XML Fixed Header Section
Table 15 : POE Restituted Orbit File – Fixed Header
XML Tag Name
(Level 1)
File_Name
XML Tag Name
(Level 2)
Value
Description
As defined in Section 2 without
the extension.
File_Description
POD POE
Restituted Orbit
File
Variable
Sentinel-MU
Notes
Mission
Variable
File_Type
Validity_Period
AUX_POEORB
Validity_Start
Variable
Validity_Stop
Variable
File_Version
Page 36/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use 0001
Free Text
11 characters string with the
following form: Sentinel-MU
where:
“Sentinel-“
is
a
fixed
string;
M = the second character of
the Mission ID specified
within the File Name (section
2);
U = the third character of the
Mission ID specified within
the File Name (section 2).
Consistent with file class in
Section 2
Same as File Type in Section 2
UTC time consistent with
Validity Start Date in Section
2. Format:
UTC=yyyy-mm-ddThh:mm:ss
UTC time consistent with
Validity Stop Date in Section 2.
Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of the File_Version
field starts from 0001 and
increases by 1 every time a new
ESA UNCLASSIFIED – For Official Use version of the same file is
generated.
Source
System
OPOD
Creator
Variable
Creator_Version
Creation_Date
Variable
Variable
A string with 4 characters. The
System field value must be
equal to the File Name Site
Centre field value as defined in
section 2
Corresponds to the facility
deployed on the Site Centre
that generated the file
Date of creation. Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of this field must
correspond to the File Name
Creation Date field defined as
part of the mandatory subfields of the File Instance ID
(Section 2)
3.4.6.2 Variable Header Section
Table 16: POE Orbit File – Variable Header
XML Tag Name
(Level 1)
Source Data1
XML Tag Name
(Level 2)
Value
Variable
Ref_Frame
Time_Reference
EARTH_FIXED
UTC
Description
Same as Optional Suffix Data
Source Section 2.
Coordinate Frame ID
Time Reference ID
3.4.6.3 Data Block Section
One Data set consists of one list of OSVs in ASCII xml format.
Table 17: POE Restituted Orbit File – Data Block
XML Tag Name
Level 1
List_of_OSVs
Value
Description
list
See Table below for elements content.
Table 18: POE Restituted Orbit File – OSV
1
Applicable only for Sentinel-3 POE Orbit Files
Page 37/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use XML Tag
Name
Type
Unit
TAI
date
string
UTC
date
string
UT1
date
string
Absolute_Orbit
int
X
Y
Z
VX
VY
VZ
Quality
float
float
float
float
float
float
String
m
m
m
m/s
m/s
m/s
OFL and NRT POD File Format Specifications
ESA UNCLASSIFIED – For Official Use Description
TAI date and time of OSV, in ASCII standard
time format, including time reference and
micro-seconds.
TAI=yyyy-mm-ddThh:mm:ss.ssssss
UTC date and time of OSV, in ASCII standard
time format, including time reference and
microseconds.
UTC=yyyy-mm-ddThh:mm:ss.ssssss
UT1 date and time of OSV, in ASCII standard
time format, including time reference and
microseconds.
TBD
Page 38/63
Date 06/02/2013 Issue 1 Rev 3
C
Format
TBD
TBD
TBD
TBD
TBD
TBD
TBD
UT1=yyyy-mm-ddThh:mm:ss.ssssss
Absolute orbit counter
This counter is incremented by a single unit
when crossing the earth-fixed ascending
node.
X position in earth-fixed coordinate system.
Y position in earth-fixed coordinate system.
Z position in earth-fixed coordinate system.
X velocity in earth-fixed coordinate system.
Y velocity in earth-fixed coordinate system.
Z velocity in earth-fixed coordinate system.
ESA UNCLASSIFIED – For Official Use 3.4.6.4 Example of a File
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name>S1A_OPER_AUX_POEORB_OPOD_20120120T120000_V20111230T220000_20120101T020000</File_Name>
<File_Description>POD POE Restituted Orbit File</File_Description>
<Notes></Notes>
<Mission>Sentinel-1A</Mission>
<File_Class>OPER</File_Class>
<File_Type>AUX_POEORB</File_Type>
<Validity_Period>
<Validity_Start>UTC=2011-12-30T22:00:00</Validity_Start>
<Validity_Stop>UTC=2012-01-01T02:00:00</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>OPOD</System>
<Creator>OPOD</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=2012-01-20T12:00:00</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
<Ref_Frame>EARTH_FIXED</Ref_Frame>
<Time_Reference>UTC</Time_Reference>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<List_of_OSVs count="10081">
<OSV>
<TAI>TAI=2011-12-30T22:00:34.000000</TAI>
<UTC>UTC=2011-12-30T22:00:00.000000</UTC>
<UT1>UT1=2011-12-30T22:00:00.000002</UT1>
<Absolute_Orbit>+01753</Absolute_Orbit>
<X unit="m">-3599358.964</X>
<Y unit="m">+5453815.346</Y>
<Z unit="m">+2707517.365</Z>
<VX unit="m/s">-0206.827074</VX>
<VY unit="m/s">+3277.962135</VY>
<VZ unit="m/s">-6850.435396</VZ>
<Quality>0000000000000</Quality>
</OSV>
<OSV>
<TAI>TAI=2011-12-30T22:00:44.000000</TAI>
<UTC>UTC=2011-12-30T22:00:10.000000</UTC>
Page 39/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use <UT1>UT1=2011-12-30T22:00:10.000002</UT1>
<Absolute_Orbit>+01753</Absolute_Orbit>
<X unit="m">-3601201.516</X>
<Y unit="m">+5486289.828</Y>
<Z unit="m">+2638861.300</Z>
<VX unit="m/s">-0161.714142</VX>
<VY unit="m/s">+3216.884901</VY>
<VZ unit="m/s">-6880.636774</VZ>
<Quality>0000000000000</Quality>
</OSV>
…
</List_of_OSVs>
</Data_Block>
</Earth_Explorer_File>
Page 40/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 3.5
NRT RESTITUTED ORBIT FILE for SENTINEL-3 (SR___ROE_AX)
3.5.1
Description
This file contains the NRT Restituted Orbit State Vectors (OSV) based on the orbit determination
performed by the NRT POD Facility. The State Vectors will be in Earth-fixed reference.
3.5.2
Dissemination
The NRT POD Facility will be plugged into the Sentinel-3 PDGS.
The file will be used for supporting the generation of Sentinel-3 NRT SRAL Level 1 and Level 2
Products.
3.5.3
Data Latency/Coverage
One file will be generated for each GNSS Level0 data. Each file coverage will be equal to the input
file coverage (GNSS data) plus at least 5 OSV (TBC) before and after the period of the GNSS data in
input. The values of the overlapping OSV will be the same in two consecutive files. One file will be
generated for each input received and contains OSVs at fixed time steps of 10 seconds intervals
(TBC). (The time intervals are configurable.)
Every file will be generated within 30 minutes from the reception of input data.
3.5.4
Accuracy
10 cm rms threshold with a target of 8cm (3D)
3.5.5
Naming Convention
The NRT POD Facility is part of the Sentinel-3 PDGS and therefore the NRT Restituted orbit filename will be compliant to the file-naming convention adopted by the Sentinel-3 PDGS and defined
in [AD-1].
The file naming convention is identified by the sequence of fields described here below:
MMM_SS_L_TTTTTT_yyyymmddThhmmss_YYYYMMDDTHHMMSS_<instance
ID>_GGG_<class ID>_vv. <extension>
The above fields constitute the smaller set of information which ensures that each Logical File
name is unique, within the context of Sentinel 3 PDGS.
The part in brackets indicates that the relevant field content can vary by case as described in the
following table.
MMM
Mission ID
Page 41/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use SS
L
TTTTTT
yyyymmddThhmmss
YYYYMMDDTHHMMSS
<instance ID>
GGG
Consists of 3 characters, either uppercase letters or digits.
S3A = Sentinel- 3A
S3B = Sentinel-3B
Data source/consumer
Consists of 2 uppercase letters.
This field indicates the data source of the instrument data or
the data consumer of the auxiliary data:
AX = for multi instrument auxiliary data
Processing level
Consists of 1 digit or 1 underscore “_” if processing level is not
applicable.
This field can indicate the instrument data product processing
stage or the processing level of applicability for the auxiliary
data.
“0” for Level-0
“1” for Level-1
“2” for Level-2
Data Type ID
Consists of 6 characters, either uppercase letters or digits or
underscores “_”.
The suffix “AX “ in the last 2 digits indicates an auxiliary data
Data Start sensing time
Consists of 15 characters, either uppercase letters or digits.
Data Sensing/Validity date/time format:
8 char., all digits, for the date: “yyyymmdd”, year,
month, day
1 uppercase T: “T”
6 char., all digits, for the time: “hhmmss”, hour,
minutes, seconds
Data Stop sensing time
Consists of 15 characters, either uppercase letters or digits.
Data Sensing/Validity date/time format:
8 char., all digits, for the date: “yyyymmdd”, year,
month, day
1 uppercase T: “T”
6 char., all digits, for the time: “hhmmss”, hour,
minutes, seconds
Instance ID for auxiliary data
Auxiliary file creation date, 2 underscores “_”
YYYYMMDDTHHMMSS__
Product Generating Centre
Consists of 3 characters, either uppercase letters or digits
(TBD)
Page 42/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use <class ID>
Consists of 8 characters, either uppercase letters or digits or
underscores.
class ID for auxiliary data is TBD
vv
File versioning
Consists of 2 digits, starting from 00. It makes unique the file
name, (e.g reprocessing twice or more time the same input data
)
Filename extension
Up to 4 characters
examples: .EEF
<extension>
Example:
S3A_SR___ROE_AX_20150101T102500_20150101T101500___EUM_<class id>_00.EEF
Class ID is TBD
3.5.6
Data Structure and Definition
The NRT Restituted orbit file is formatted using XML-tags, see table below. Each NRT Restituted
Orbit File consists of a single file containing both the Header and the Datablock Sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
3.5.6.1 XML Fixed Header Section
Table 19: NRT Restituted orbit file – Fixed Header
XML Tag Name
(Level 1)
File_Name
XML Tag Name
(Level 2)
Value
Description
As defined in Section 3.5.5
without the extension.
File_Description
Notes
Mission
NRT POD
Restituted
Orbit File
Variable
Sentinel-3#
File_Class
Variable
File_Type
SR___ROE_
AX
Free Text
# indicates the spacecraft ID;
A, B
Same as Class ID in Section
3.5.5
Validity_Period
Validity_Start
Page 43/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Variable
UTC time consistent with
Validity Start Date in Section
3.5.5. Format:
UTC=yyyy-mm-ddThh:mm:ss
ESA UNCLASSIFIED – For Official Use Validity_Stop
Variable
File_Version
Variable
UTC time consistent with
Validity Stop Date in Section
3.5.5. Format:
UTC=yyyy-mm-ddThh:mm:ss
Same as version in Section
3.5.5.
Source
System
NRT POD
Creator
Variable
Creator_Version
Creation_Date
Variable
Variable
Name of the Ground Segment
element creating the file
Name of the tool, within the
Ground Segment element,
creating the file
Version of the tool
Date of creation. Format:
UTC=yyyy-mm-ddThh:mm:ss
3.5.6.2 Variable Header Section
Table 20: NRT Restituted Orbit File – Variable Header
XML Tag Name
(Level 1)
Ref_Frame
Time_Reference
(TBC)
XML Tag Name
(Level 2)
Value
EARTH_FIXED
UTC
Description
Coordinate Frame ID
Time Reference ID
3.5.6.3 Data Block Section
One Data set consisting of one list of OSVs.
Table 21: NRT Restituted Orbit File – Data Block
XML Tag Name
Level 1
List_of_OSVs
Value
Description
list
See Table below for elements content.
Table 22 : NRT Restituted Orbit File – OSV
XML Tag
Name
TAI
Type
Unit
Description
date
string
UTC
date
string
UT1
date
string
TAI date and time of OSV, in ASCII standard time
format, including time reference and micro-seconds.
TAI=yyyy-mm-ddThh:mm:ss.ssssss
UTC date and time of OSV, in ASCII standard time
format, including time reference and microseconds.
UTC=yyyy-mm-ddThh:mm:ss.ssssss
UT1 date and time of OSV, in ASCII standard time
Page 44/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Absolute_Orbit
int
X
Y
Z
VX
VY
VZ
Quality
float
float
float
float
float
float
String
m
m
m
m/s
m/s
m/s
Page 45/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use format, including time reference and microseconds.
UT1=yyyy-mm-ddThh:mm:ss.ssssss
Absolute orbit counter
This counter is incremented by a single unit when
crossing the earth-fixed ascending node.
X position in earth-fixed coordinate system.
Y position in earth-fixed coordinate system.
Z position in earth-fixed coordinate system.
X velocity in earth-fixed coordinate system.
Y velocity in earth-fixed coordinate system.
Z velocity in earth-fixed coordinate system.
ESA UNCLASSIFIED – For Official Use 3.5.6.4 Example of a File
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name> S3A_SR___ROE_AX_20150101T102500_20150101T101500___EUM_<class id>_00</File_Name>
<File_Description>POD NRT Restituted Orbit File</File_Description>
<Notes></Notes>
<Mission> Sentinel 3A</Mission>
<File_Class>TBD</File_Class>
<File_Type>SR___ROE_AX</File_Type>
<Validity_Period>
<Validity_Start>UTC=2015-01-01T10:25:00</Validity_Start>
<Validity_Stop>UTC=2015-01-01T10:15:00</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>NRT POD</System>
<Creator>PODSW</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=2007-11-16T13:04:32</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
<Ref_Frame>EARTH-FIXED</Ref_Frame>
<Time_Reference>UTC</Time_Reference>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<List_of_OSVs count="10141">
<OSV>
<TAI>TAI=2016-03-06T00:00:34.000000</TAI>
<UTC>UTC=2016-03-06T00:00:00.000000</UTC>
<UT1>UT1=2016-03-06T00:00:00.109000</UT1>
<Absolute_Orbit>+42243</Absolute_Orbit>
<X unit="m">+0519641.779</X>
<Y unit="m">+5278659.929</Y>
<Z unit="m">-4220599.988</Z>
<VX unit="m/s">+1113.622468</VX>
<VY unit="m/s">-4842.338815</VY>
<VZ unit="m/s">-5925.935594</VZ>
<Quality>0000000000000</Quality>
</OSV>
<OSV>
<TAI>TAI=2016-03-06T00:01:34.000000</TAI>
<UTC>UTC=2016-03-06T00:01:00.000000</UTC>
Page 46/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use <UT1>UT1=2016-03-06T00:01:00.109000</UT1>
<Absolute_Orbit>+42243</Absolute_Orbit>
<X unit="m">+0583912.227</X>
<Y unit="m">+4975970.019</Y>
<Z unit="m">-4566150.959</Z>
<VX unit="m/s">+1027.326972</VX>
<VY unit="m/s">-5243.308832</VY>
<VZ unit="m/s">-5588.035384</VZ>
<Quality>0000000000000</Quality>
</OSV>
…
</List_of_OSVs>
</Data_Block>
</Earth_Explorer_File>
Page 47/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 4
AUXILIARY FILES FOR SENTINELS
4.1
GNSS USO Monitoring (AUX_GNSUSO)
4.1.1
Description
This file contains the GNSS USO frequency monitoring based on the time correlation packets
issued by the GPS receiver. It provides the correlation between IMT (instrument measurement
time) which precisely describes how the GPSR clock oscillator behaves, and GPS time.
4.1.2
Dissemination
TBD
4.1.3
Data Latency/Coverage
TBD
4.1.4
Naming Convention
The applicable file naming convention is defined in [AD-2] and detailed in Section 2.
Example of a GNSS USO Monitoring File name:
S3A_OPER_AUX_GNSUSO_OPOD_20100101T000000_V20100101T010000_20100101T020000.EOF
4.1.5
Data Structure and Definition
The GNSS USO Monitoring file is formatted using XML-tags. Each File consists of a single file
(*.EOF) containing both the Header and the Datablock Sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
4.1.5.1 XML Fixed Header Section
Table 23 : GNSS USO Monitoring File – Fixed Header
XML Tag Name
(Level 1)
XML Tag
Name
(Level 2)
File_Name
Page 48/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Value
Description
As defined in Section 2 without
ESA UNCLASSIFIED – For Official Use the extension.
File_Description
GNSS USO Monitoring
File
Variable
Sentinel-3#
Notes
Mission
Variable
File_Type
Validity_Period
AUX_GNSUSO
Validity_Sta
rt
Variable
Validity_Sto
p
Variable
File_Version
0001
Free Text
# indicates the spacecraft ID;
A,B
Consistent with file class in
Section 2
Same as File Type in Section 2
UTC time consistent with
Validity Start Date in Section
2. Format:
UTC=yyyy-mm-ddThh:mm:ss
UTC time consistent with
Validity Stop Date in Section 2.
Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of the File_Version
field starts from 0001 and
increases by 1 every time a new
version of the same file is
generated.
Source
System
OPOD
Creator
Variable
Creator_Ver
sion
Creation_D
ate
Variable
4.1.5.2 Variable Header Section
No variable header present
Page 49/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Variable
A string with 4 characters. The
System field value must be
equal to the File Name Site
Centre field value as defined in
section 2
Corresponds to the facility
deployed on the Site Centre
that generated the file
Date of creation. Format:
UTC=yyyy-mm-ddThh:mm:ss
The value of this field must
correspond to the File Name
Creation Date field defined as
part of the mandatory subfields of the File Instance ID
(Section 2)
ESA UNCLASSIFIED – For Official Use 4.1.5.3 Data Block Section
TBD
Page 50/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 4.2
Attitude Restituted Data for Sentinel-1 (AUX_RESATT)
4.2.1
Description
This file contains the restituted attitude data computed by the POD based on the attitude
quaternions computed on-board by the AOCS and provided to the POD Service within the Sentinel1 PDGS SAR Level 0 Annotations Products.
4.2.2
Dissemination
TBD
4.2.3
Data Latency/Coverage
TBD
4.2.4
Accuracy
4.2.5
Naming Convention
The applicable file naming convention is defined in [AD-2] and detailed in Section 2.
Example of a Restituted Attitude file name:
S1A_OPER_AUX_RESATT_OPOD_20100101T000000_V20100101T010000_20100101T020000.EOF
4.2.6
Data Structure and Definition
The Attitude Restituted files will follow the Earth Explorer File Format Standard [AD-3] and the
Tailoring of the Earth Explorer File Format Standard of the PDGS of the Sentinel missions defined
in [AD-2]. When no specific tailoring is described, the standard [AD-3] directly applies.
Each Platform File consists of a single file (*.EOF) containing both the Header and the Datablock
Sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
4.2.7
XML Fixed Header Section
Table 24 : Attitude Restituted File – Fixed Header
Page 51/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use XML Tag Name
(Level 1)
File_Name
XML Tag Name
(Level 2)
Value
Description
As defined in Section 2
without the extension.
File_Description
Notes
Mission
Attitude
Restituted data
File
Variable
Sentinel-1#
File_Class
Variable
File_Type
AUX_RESATT
Free Text
# indicates the spacecraft ID;
A,B
Consistent with file class in
Section 2
Same as File Type in Section
2
Validity_Period
Validity_Start
Variable
Validity_Stop
Variable
File_Version
0001
UTC time consistent with
Validity Start Date in Section
2. Format:
UTC=yyyy-mmddThh:mm:ss
UTC time consistent with
Validity Stop Date in Section
2. Format:
UTC=yyyy-mmddThh:mm:ss
The value of the File_Version
field starts from 0001 and
increases by 1 every time a
new version of the same file is
generated.
Source
System
OPOD
Creator
Variable
Creator_Version
Creation_Date
Variable
Variable
Page 52/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use A string with 4 characters.
The System field value must
be equal to the File Name Site
Centre field value as defined
in section 2
Corresponds to the facility
deployed on the Site Centre
that generated the file
Date of creation. Format:
UTC=yyyy-mmddThh:mm:ss
The value of this field must
correspond to the File Name
Creation Date field defined as
part of the mandatory subfields of the File Instance ID
ESA UNCLASSIFIED – For Official Use (Section 2)
4.2.8
Variable Header Section
No variable header present
4.2.9
Data Block Section
The data block format is ASCII xml.
Table 25: Restituted Attitude File – Data Block
XML Tag Name
Level 1
Attitude_File_Type
Type
Description
string
Attitude_Data_Type
string
Max_Gap
Unit=”s”
Quaternion_Data
Structures: see
tables below
The initial attitude frame:
Sat_Attitude
It defines the type of attitude data:
Quaternions
Maximum gap detected in the file, i.e. maximum
amount of seconds between two consecutive sets of
quaternions.
Structure for the list of quaternions
Table 26: Restituted Attitude File – Quaternions Data
XML Tag Name
Type
Inertial_Ref_Frame
string
Unit
List_of_Quaternions
count=”n”
Description
Reference frame:
EARTH_FIXED
List of Quaternions
Table 27: Restituted Attitude File – List of Quaternions Data
XML Tag Name
Type
Quaternions
Structure (see
Table 28)
Unit
Description
Set of quaternions for a given time
representing the transformation
between Earth-Centered-Earth-Fixed
and satellite attitude frame. It is
recommended to write quaternions
with 9 decimal digits.
Table 28: Restituted Attitude File – Quaternions
XML Tag Name
Type
Attribute
Description
Time
string
ref=”UTC”
Date for the quaternions.
Page 53/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use Q1
Q2
Q3
Q4
real
real
real
real
The date format is CCSDS-A with
reference and microseconds
(UTC=yyyy-mmddThh:nn:ss.uuuuuu)
Quaternion
Quaternion
Quaternion
Quaternion
Note: The following quaternions definition, consistent with EO CFI v4.4 conventions, has to be
used:
⎛ θ ⎞
⎟
⎝ 2 ⎠
⎛ θ ⎞
Q2 = e y ⋅ sin ⎜ ⎟
⎝ 2 ⎠
⎛ θ ⎞
Q3 = e z ⋅ sin ⎜ ⎟
⎝ 2 ⎠
⎛ θ ⎞
Q4 = cos⎜ ⎟
⎝ 2 ⎠
Q1 = e x ⋅ sin ⎜
(
)
where e x , e y , e z are the direction cosines of the rotation axis and
is the rotation angle.
Then (Q1, Q2, Q3) corresponds to the vector part of the quaternion and Q4 is the scalar part of the
quaternion.
Page 54/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 4.2.9.1 Example of a File
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name>S1A_OPER_AUX_RESATT_OPOD_20120120T120000_V20111230T220000_20120101T020000</File_Name>
<File_Description>Attitude Restituted data File</File_Description>
<Notes></Notes>
<Mission>Sentinel-1A</Mission>
<File_Class>OPER</File_Class>
<File_Type>AUX_RESATT</File_Type>
<Validity_Period>
<Validity_Start>UTC=2011-12-30T22:00:00</Validity_Start>
<Validity_Stop>UTC=2012-01-01T02:00:00</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>OPOD</System>
<Creator>OPOD</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=UTC=2012-01-20T12:00:00</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<Attitude_File_Type>Sat_Attitude</Attitude_File_Type>
<Attitude_Data_Type>Quaternions</Attitude_Data_Type>
<Max_Gap unit="s">1</Max_Gap>
<Quaternion_Data>
<Inertial_Ref_Frame>EARTH_FIXED</Inertial_Ref_Frame>
<List_of_Quaternions count="100801">
<Quaternions>
<Time ref="UTC">UTC=2011-12-30T22:00:00.000000</Time>
<Q1>0.205523</Q1>
<Q2>0.694593</Q2>
<Q3>-0.029401</Q3>
<Q4>0.688793</Q4>
</Quaternions>
<Quaternions>
<Time ref="UTC">UTC=2011-12-30T22:00:01.000000</Time>
<Q1>0.205315</Q1>
<Q2>0.694556</Q2>
<Q3>-0.029188</Q3>
<Q4>0.688902</Q4>
Page 55/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use </Quaternions>
<Quaternions>
<Time ref="UTC">UTC=2011-12-30T22:00:02.000000</Time>
<Q1>0.205107</Q1>
<Q2>0.694518</Q2>
<Q3>-0.028975</Q3>
<Q4>0.689011</Q4>
</Quaternions>
<Quaternions>
<Time ref="UTC">UTC=2011-12-30T22:00:03.000000</Time>
<Q1>0.204899</Q1>
<Q2>0.694481</Q2>
<Q3>-0.028762</Q3>
<Q4>0.689119</Q4>
</Quaternions>
<Quaternions>
<Time ref="UTC">UTC=2011-12-30T22:00:04.000000</Time>
<Q1>0.204691</Q1>
<Q2>0.694443</Q2>
<Q3>-0.028549</Q3>
<Q4>0.689228</Q4>
</Quaternions>
…
</List_of_Quaternions>
</Quaternion_Data>
</Data_Block>
</Earth_Explorer_File>
Page 56/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 4.3
Platform Data files for Sentinel-3
4.3.1
Description
Two files are foreseen to be generated with different timeliness:
1. Preliminary Platform file (AUX_PRLPTF)
2. Precise Platform file (AUX_PRCPTF)
Both files contain information on:
•
the nadir projection of the distance between the altimeter antenna center of phase and the
satellite center of gravity (m)
•
the platform derived off nadir angle (degrees)
4.3.2
Dissemination
The files will be passed to the Sentinel-3 PDGS and will be used for supporting the generation of the
Level 2 SRAL Mission products as follows:
•
The Preliminary Platform file will be used for generating Sentinel-3 STC products;
•
The Precise Platform file will be used for generating Sentinel-3 NTC products;
•
For NRT production, the latest Preliminary Platform file shall be used.
4.3.3
Data Latency/Coverage
The platform files will be generated by the POD Service during orbit processing. The processing
delay will be therefore related to the MOE and POE Orbit files productions.
Each file covers approximately 26 hours and will be generated as follows:
•
The Preliminary Platform file will be generated and transferred to the PDGS once per day in
nominal routine case. Time coverage for the day (d) ranges from d-1 at 22h to d at 24h.
•
The Precise Platform file will be generated and transferred to the PDGS within 20 days after
data acquisition. Time coverage for the day (d) ranges from d-2 at 22h to d-1 at 24h.
4.3.4
Accuracy
TBD
4.3.5
Naming Convention
The applicable file naming convention is defined in [AD-2] and detailed in Section 2.
Example of a Preliminary and a Precise Platform File name:
S3A_OPER_ AUX_PRLPTF_OPOD_20100101T000000_V20100101T010000_20100101T020000.EOF
S3A_OPER_ AUX_PRCPTF_OPOD_20100101T000000_V20100101T010000_20100101T020000.EOF
Page 57/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 4.3.6
Data Structure and Definition
The Platform files will follow the Earth Explorer File Format Standard [AD-3] and the Tailoring of
the Earth Explorer File Format Standard of the PDGS of the Sentinel missions defined in [AD-2].
When no specific tailoring is described, the standard [AD-3] directly applies..
Each Platform File consists of a single file (*.EOF) containing both the Header and the Datablock
Sections.
The Header will be structured in two sections:
•
Fixed Header
•
Variable Header
4.3.7
XML Fixed Header Section
Table 29 : Preliminary and Precise Platform File – Fixed Header
XML Tag Name
(Level 1)
File_Name
XML Tag Name
(Level 2)
Value
Description
As defined in Section 2
without the extension.
File_Description
Notes
Mission
Preliminary
Platform file
or
Precise Platform
file
Variable
Sentinel-3#
File_Class
Variable
File_Type
AUX_PRLPTF
AUX_PRCPTF
Free Text
# indicates the spacecraft ID;
A,B
Consistent with file class in
Section 2
Same as File Type in Section
2
Validity_Period
Validity_Start
Variable
Validity_Stop
Variable
File_Version
Page 58/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use 0001
UTC time consistent with
Validity Start Date in Section
2. Format:
UTC=yyyy-mmddThh:mm:ss
UTC time consistent with
Validity Stop Date in Section
2. Format:
UTC=yyyy-mmddThh:mm:ss
The value of the File_Version
field starts from 0001 and
increases by 1 every time a
new version of the same file is
ESA UNCLASSIFIED – For Official Use generated.
Source
4.3.8
System
OPOD
Creator
Variable
Creator_Version
Creation_Date
Variable
Variable
A string with 4 characters.
The System field value must
be equal to the File Name Site
Centre field value as defined
in section 2
Corresponds to the facility
deployed on the Site Centre
that generated the file
Date of creation. Format:
UTC=yyyy-mmddThh:mm:ss
The value of this field must
correspond to the File Name
Creation Date field defined as
part of the mandatory subfields of the File Instance ID
(Section 2)
Variable Header Section
No variable header present
4.3.9
Data Block Section
The data block format is ASCII xml.
Table 30: Preliminary and Precise Platform File – Data Block
XML Tag Name
Level 1
List_of_PTFs
Value
Description
List
See Table below for elements content.
Table 31: Preliminary and Precise Platform File – PTF
XML Tag
Name
TAI
Type
UTC
date
Unit
date
Page 59/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use Description
TAI date and time of PTF Values, in ASCII
standard time format, including time reference
and micro-seconds.
TAI=yyyy-mm-ddThh:mm:ss.ssssss
UTC date and time of PTF Values, in ASCII
standard time format, including time reference
and microseconds.
ESA UNCLASSIFIED – For Official Use UT1
date
Off_Nadir_Angle
Dist_Ant_COG
float
float
Quality
String
degree
meter
Page 60/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use UTC=yyyy-mm-ddThh:mm:ss.ssssss
UT1 date and time of PTF Values, in ASCII
standard time format, including time reference
and microseconds.
UT1=yyyy-mm-ddThh:mm:ss.ssssss
Altimeter (SRAL) Antenna Mispointing Angle
Distance between the antenna phase center and
the center of gravity of the satellite (nadir
projection)
ESA UNCLASSIFIED – For Official Use 4.3.9.1 Example of a File
<?xml version="1.0" ?>
<Earth_Explorer_File>
<Earth_Explorer_Header>
<Fixed_Header>
<File_Name> S3A_OPER_ AUX_PRLPTF_OPOD_20071116T130432_V20120506T000000_20120516T010000</File_Name>
<File_Description>Preliminary Platform File</File_Description>
<Notes></Notes>
<Mission> Sentinel-3A</Mission>
<File_Class>OPER</File_Class>
<File_Type>AUX_PRLPTF</File_Type>
<Validity_Period>
<Validity_Start>UTC=2012-05-06T00:00:00</Validity_Start>
<Validity_Stop>UTC=2012-05-16T01:00:00</Validity_Stop>
</Validity_Period>
<File_Version>0001</File_Version>
<Source>
<System>OPOD</System>
<Creator>OPOD</Creator>
<Creator_Version>1.0</Creator_Version>
<Creation_Date>UTC=2007-11-16T13:04:32</Creation_Date>
</Source>
</Fixed_Header>
<Variable_Header>
</Variable_Header>
</Earth_Explorer_Header>
<Data_Block type="xml">
<List_of_PTFs count="1589">
<PTF>
<TAI>TAI=2016-03-06T00:00:34.000000</TAI>
<UTC>UTC=2016-03-06T00:00:00.000000</UTC>
<UT1>UT1=2016-03-06T00:00:00.109000</UT1>
< Off_Nadir_Angle>0.000</Off_Nadir_Angle >
< Dist_Ant_COG >0.471</ Dist_Ant_COG >
<Quality>0000000000000</Quality>
</ PTF >
< PTF >
<TAI>TAI=2016-03-06T00:00:34.000000</TAI>
<UTC>UTC=2016-03-06T00:00:00.000000</UTC>
<UT1>UT1=2016-03-06T00:00:00.109000</UT1>
< Off_Nadir_Angle > 0.000</ Off_Nadir_Angle >
< Dist_Ant_COG >0.471</ Dist_Ant_COG >
<Quality>0000000000000</Quality>
</ PTF >
</List_of_ PTFs>
</Data_Block>
Page 61/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use </Earth_Explorer_File>
Page 62/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use ESA UNCLASSIFIED – For Official Use 5
SENTINEL-3 GNSS L1B RINEX FORMAT
5.1.1
Description
Each GNSS Level 1 file consists of a single file. This file contains GNSS measurements processed at
Level 1.
5.1.2
Dissemination
The file will be made available to the Sentinel-3 PDGS for being disseminated to the SALP.
5.1.3
Data Latency/Coverage
One file will be generated for each GNSS Level 0 data made available by the Sentinel-3 PDGS.
The file coverage will be equal to the input file coverage (GNSS data).
5.1.4
Accuracy
TBD
5.1.5
Naming Convention
TBD
5.1.6
Data Structure and Definition
TBD
6
QUALITY CONTROL REPORTS
6.1.1
Description
Periodic reports based on the results of the long-term monitoring and validation of the orbit and
attitude data performed by the POD Service.
6.1.2
Naming Convention
TBD
6.1.3
Data Structure and Definition
Sentinel-1 quality control reports will be formatted as XML files plus human readable files (HTML
and PDF).
TBD for Sentinel-2 and Sentinel-3
Detailed format is TBD.
Page 63/63
OFL and NRT POD File Format Specifications
Date 06/02/2013 Issue 1 Rev 3
ESA UNCLASSIFIED – For Official Use