SENTINEL-1 PDGS
IMPLEMENTATION
Ref : S1PD.SP.00110.ASTR
Issue : 01 Rev. : 07
Date : 20th December 2012
Page : v
ESA unclassified – for official use
pp. 45, 46, 17, 68, 69,
75, 76, 84
Description of “General Product Information” section of
Manifests updated in order to reflect interpretation of
Instrument configuration ID and Mission Data Take ID, as
clarified in [CDB-03]
p. 17
List of Record types for GPRS ( Table 18 ) updated as per
updated version of [TDB-32]
p.113, 115
Typo in the definition of value range for Mission Data
Take Identifier has been fixed (000000-FFFFFF replaced
by 000001-FFFFFF)
1/4 22/08/2011
pp. 25, 26, 48, 49, 51
to 60, 71 to 97, 99 to
104, 110 to 113
Annexed zip archive
files
Usage of <safe:extension> element and of namespaces
specific to Sentinel-1 L0 Products have been introduced in
order to add elements specific to Sentinel-1 L0, while
keeping the Manifests compliant to XFDU and SAFE Core
specifications, as per JIRA issue S1PDGS-1745.
pp. 29, 33
Annexed zip archive
files
Hierarchical structure of Manifest and Data Component
Schema modified to accommodate elements specific to
Sentinel-1 L0 Products, introduced through the
<safe:extension> mechanism, as per JIRA issue S1PDGS-
1745.
p. 17
Missing examples of Data Component name for GPS L0
Product added in section 3.4.3
1/5 14/11/2011
pp. 44, 46 to 54, 65 to
72, 74 to 81, 83 to 90,
92 to 97, 103 to 106
Annexed zip archive
files
Completed the list of Manifest schemas for L0 format ,
aligned to document issue 1.4, as per Jira issue S1PDGS-
2182. Completed the set of Data Component files for all
S1 L0 Product types. Schemas are provided as annexed
files.
Minor typos and disalignments between provided schemas
and description of content of Manifests for some Product
Types have been fixed. Reference to Metadata Objects
IDS detailed (reported both Metadata Object ID and
corresponding xmlDataType)
p. 24, 44
Typos in definition of SAFE Manifest Schema root path
and in the provided example of a specialization
namespace
Fig. 1, Fig. 2
Fixed minor disalignments of hierarchical tree of Manifest
and Data Component Schemas w.r.t. provided complete
set of Schemas
pp. 10, 11, 25, 33, 37,
45, 60, 88, 95
Updated document version in annexed zip archive files
name
Fig. 3
Minor update of S1 L0 Product family tree in order to
highlight RFC Products content
pp. 59, 71, 80, 89
Definition of instrument footprint revised (area defined by 4
or more coordinates, excluding nadir points)
pp. 49, 68, 76, 94
Definition of Packet Store ID corrected (removed incorrect
sentence “equal to VC ID”)
p.iv Date of Change Log for version 1.3 corrected
