AG-E-E-2209-R03

ASTER LEVEL 1
DATA PRODUCTS
SPECIFICATION
(GDS Version)
Version 1.3

June 25, 2001

ERSDAC
Earth Remote Sensing
Data Analysis Center

Revision History
No.
1
2
3
4
5

Title
ASTER Level 1 Data Products Specification
(AG-E-E-2076-R00)
ASTER Level 1 Data Products Specification
(AG-E-E-2209-R00)
ASTER Level 1 Data Products Specification
(AG-E-E-2209-R01)
ASTER Level 1 Data Products Specification
(AG-E-E-2209-R02)
ASTER Level 1 Data Products Specification
(AG-E-E-2209-R03)

1-1

Rev.
Ver. β
Ver. 1.0
Ver. 1.1

Date
Oct. 18,
1996
Jun. 30, 1997

Ver. 1.2

Nov. 10,
1997
Jul. 24, 1998

Ver. 1.3

Jun. 25, 2001

Change Details-1 (1/6)
(Ver. β

⇒ Ver. 1.0)

Ver. 1.0
Update Comments (based on Ver. β)
Ver. β
2.2 Data Structure
- Radiometric correction table is inserted into the Swath that we create.
- Browse data is deleted from this document.
chg. 2.2 Data Structure: Figure 2.2-1
p.2-2
p.2-2
2.3.1.1 Inventory Metadata
- Inventory Metadata of Level 1A Data Product has modified based on the concept of “Unified” Inventory
Metadata for all ASTER products and related requirements.
- ‘ProductionDateTime’ is added on account of Toolkit MET Tool's update.
del. The objects described in Italics
Item 12 ~ 14

add. ShortName
Item 1

add. ProductionDateTime
Item 3

2.3.1.2 ASTER GDS Generic Metadata
- This title has been changed to “ASTER Generic Metadata”.
- ASTER GDS Generic Metadata of Level 1A Data Product has modified based on the concept of
“Unified” ASTER Generic Metadata for all ASTER products and related requirements.
2.3.1.2 ASTER GDS Generic Metadata: changed the title
chg.
p.2-5
p.2-5
name to ASTER Generic Metadata
Item 11.2,
del. Several objects described in Italics

12.3, 13
chg. Several objects described in Italics
Item 12.1 ~ 2
Item 10.7 ~ 8
Inventory
mv. GenerationDateandTime
Item 4
metadata
add. Scene Orientation Angle
Item
10.9

2.3.1.3 GDS Generic Metadata:
- GDS Generic Metadata is newly added to reflect the discussion results in the ASTER Science Team (in
consideration).
2.3.1.3 Product Specific Metadata(VNIR)
- HDF file attribute name is changed on account of Toolkit's update.
- Descriptions of some items in Product Specific Metadata(VNIR) have been modified to reflect the
discussion results in the ASTER Science Team.
(x = 1 ~ 4)
- The description of items concerning VNIR Band-2 is omitted on account that these items are created in
the same manner (similar to VNIR Band-1).
chg. Geometric Correction: Number of lattice point is revised.
Item x.3
Item x.3
Number of Bad Pixels: The elements of this Item are rewritten
chg.
Item x.5.1
Item x.5.1
to match with those of SWIR and TIR.
List of Bad Pixels: Separated this group from this attribute for
del.
Item x.5.2

flexibility and convenience of storing.
Unit Conversion Coefficients: Offset value is revised, and 2
chg.
Item x.6
Item x.6
other parameters are deleted.
add. Destripe Parameter
Item x.7, 4.8

2.3.1.4 Product Specific Metadata(SWIR)
- HDF file attribute name is changed on account of Toolkit's update.
- Descriptions of some items in Product Specific Metadata(SWIR) have been modified to reflect the
discussion results in the ASTER Science Team.
(x = 1 ~ 6)
- The descriptions of items concerning SWIR Band-5,6,7,8,9 are omitted on account that these items are
created in the same manner (similar to SWIR Band-4).
chg. Geometric Correction: Number of lattice point is revised.
Item x.3
Item x.3
List of Bad Pixels: Separated this group from this attribute for
del.
Item x.5.2

flexibility and convenience of storing.
Unit Conversion Coefficients: Offset value is revised, and 2
chg.
Item x.6
Item x.6
other parameters are deleted.
1-2

4.7.8 . Destripe Parameter 1-3 Item x. add.

2-29 chg. vgroup name: VNIR_Group is changed to VNIR. Note 2: Evaluation area size is revised.7.3.3.3.1.4 VNIR Band 3N Swath .New data type ‘RadiometricCorrTable’ is added to Table 2.0 Update Comments (based on Ver.4-2 revised Observation Time: Rewritten to match with CCSDS Day chg.2-29 2. Geometric Correction: Number of lattice point is revised.3.4.New data field ‘RadiometricCorrTable’ is added to Table 2. Dimension Size of each filed: Number of lattice point is Table 2. Image Data Information: TIR pixel numbers are revised.14 are omitted on account that these items are created in the same manner (similar to TIR Band-10).4-3 Table 2.4-1. chg.1.3. (x = 1 ~ 5) .5 Product Specific Metadata(TIR) . β 2. chg. chg.2-50 p.Vgroup name and class are changed to VNIR and 1A.3. p. vgroup class: 1A (processing level) p.HDF file attribute name is changed on account of Toolkit's update.3-1 chg.3. p.4-2 Table 2. β) Ver. Unit Conversion Coefficients: Offset value is revised.13.2-32  2. TIR Short Term Calibration Information Item 8  2. 1.2-49 p. Table 2.3. chg.3.Change Details-1 (2/6) (Ver.3.2-30 add.2-47 p.2 chg.3 VNIR Band 2 Swath 2.4.3-1.Ancillary data volumes are revised in Table 2.3.4.7 Bad Pixel Information .5 VNIR Band 3B Swath .3. chg.6 Radiometric Correction Table .4-3 Table 2. p.6 Item x. Radiometric correction table Table 2. TIR) and stored as a new data object.2 Cloud Coverage Table . 1-4 . Table 2.3-1 and number of items in Cloud Coverage Table are modified. add.2 VNIR Band 1 Swath .4-1 and 2.Product specific attributes ‘List of Bad Pixel’ for all processed bands are divided from Product Specific metadata(VNIR.3.5. 4. Radiometric correction table Table 2.4-2. and 2 chg.2 Item x.8  add.3.The descriptions of these objects are omitted on account that these objects are created in the same manner (similar to VNIR Band 1 Swath).4-2 Table 2.3. 2.12.3.3. β ⇒ Ver. Item x. Table 2.3.3.3. 2.3-1: Dimension size is revised.1 Overview .2  2. Destripe Parameter Item x.3-1 Table 2.4-3 Segmented Time Code.3. Item x.3. add.3. Item x.4-3 revised Observation Time: Rewritten to match with CCSDS Day chg.3.Evaluation area sizes of Table 2.3 List of Bad Pixels: Separated this group from this attribute for del.2-47 p. Item x.3. p. Dimension Size of each filed: Number of lattice point is Table 2.These objects are deleted from Level 1A Data Product to reflect the changing data type. 1.3.4.4. SWIR.6 other parameters are deleted. “Note 2” (descriptions about spacecraft time format) Note 2  2.4-3  2. respectively.The descriptions of items concerning TIR Band-11.3 Item x.3 Ancillary Data .2-32 add.0) Ver.3.Descriptions of some items in Product Specific Metadata(TIR) have been modified to reflect the discussion results in the ASTER Science Team. “Relative Scan Number” changed to “Time Tag”. .4. “Note” changed to “Note 1”.4-2 Segmented Time Code.4-3. chg.3. Table 2. add.2  flexibility and convenience of storing.

The descriptions of these objects are omitted on account that these objects are created in the same manner (similar to SWIR Band 4 Swath).7 SWIR Band 9 Swath .This Data type has been changed because of the rearrangement of Level 1A Data Product concept.9 SWIR Supplement Data . Data model: data type is revised.3.5.4. Dimension Size: Record size is added as nominal value. Table 2.5.5.3. Table 2. Table 2. 1.3. Dimension Size of each filed: Number of lattice point is Table 2.2-59 p.Vgroup name and class are changed to SWIR and 1A.New data field ‘RadiometricCorrTable’ is added to Table 2.3.2-53  2. p.5 SWIR Band 7 Swath 2.5. β ⇒ Ver. Radiometric correction table Table 2.4.3.5-2 revised Observation Time: Rewritten to match with CCSDS Day chg.5.3.3.0) Ver. Radiometric correction table  1-5 .6 SWIR Band 8 Swath 2.3.3.6-2 Table 2.2-47  chg. vgroup name: TIR_Group is changed to TIR.Browse data is deleted from this document based on the separation of Level 1A Product and Browse Data.5.3. p.2-80 p.6-1 and 2. chg. “Relative Scan Number” changed to “Time Tag”.2-40 add. respectively.3.5-2  2.6-2 Table 2.1 Overview .8 VNIR Browse Image .Browse data is deleted from this document based on the separation of Level 1A Product and Browse Data.3.5-2 Segmented Time Code.5-2 Table 2.4-9 Table 2.3.6-2 Segmented Time Code.2 SWIR Band 4 Swath .New data field ‘RadiometricCorrTable’ is added to Table 2. p. 2. Table 2.6-2 Table 2.6-2 add.5. Dimension Size: Record size is added as nominal value.6.3.3.3.7 VNIR Supplement Data . 2.3.2 TIR Band 10 Swath .3.3. vgroup class: 1A (processing level) p. add.3.10 SWIR Browse Image .3. chg.6-2 revised Observation Time: Rewritten to match with CCSDS Day chg.1 Overview .3. chg. . respectively.This Data type has been changed because of the rearrangement of Level 1A Data Product concept.3.Change Details-1 (3/6) (Ver.3. chg.3.5-14 Table 2.2-38  chg. p.5-2.These objects are deleted from Level 1A Data Product to reflect the changing data type. p.5-1 and 2.4-4 2.2-40  2.2-53 add. β) Ver. 1. 2.2-73 p.5.3.3. vgroup name: SWIR_Group is changed to SWIR.5-4 2. Data model: data type is revised.0 Update Comments (based on Ver. 2.3 SWIR Band 5 Swath 2.3. Dimension Size of Image Data: TIR pixel number is revised. Table 2.5-2 Table 2.6.3. chg. “Relative Scan Number” changed to “Time Tag”.6-2.2-56 p.5.2-47 add. β 2.Supplement data volumes are revised. chg. p.5.3.3.2-38 add. Dimension Size of each filed: Number of lattice point is Table 2.3. vgroup class: 1A (processing level) p.Vgroup name and class are changed to TIR and 1A.3.8 Radiometric Correction Table .4 SWIR Band 6 Swath 2. chg.

9  3.2-1.2 Data Structure . . 1.GDS Generic Metadata is newly added to reflect the discussion results in the ASTER Science Team (in consideration).This Data type has been changed because of the rearrangement of Level 1A Data Product concept. 13 chg. β) Ver.3 TIR Band 11 Swath 2.3.Browse data is deleted from this document based on the separation of Level 1A Product and Browse Data. 2.1 ~ 2 Item 10. β ⇒ Ver.Data structure was reconstructed to reflect the discussion results in the ASTER Science Team.6-3 2.6. p.3.2-88 p.6-11 Table 2.9 TIR Browse Image . Scene Orientation Angle Item 10.3.3. ProductionDateTime Item 3  3.3. .3. del.2-59 add.3-2 3. The objects described in Italics Item 12 ~ 14  add.2 ASTER GDS Generic Metadata .1.ASTER GDS Generic Metadata of Level 1A Data Product has modified based on the concept of “Unified” ASTER Generic Metadata for all ASTER products and related requirements. . p.1.2 ASTER GDS Generic Metadata: changed the title chg.0 Update Comments (based on Ver.8 TIR Supplement Data . Table 2.3-5 name to ASTER Generic Metadata Item 11. . “Relative Scan Number” changed to “Time Tag”.‘ProductionDateTime’ is added on account of Toolkit MET Tool's update.7 Radiometric Correction Table .6. Several objects described in Italics Item 12.3-2 p. Data model: data type is revised.The descriptions of these objects are omitted on account that these objects are created in the same manner (similar to TIR Band 10 Swath).This title has been changed to “ASTER Generic Metadata”. 1.6 TIR Band 14 Swath .These objects are deleted from Level 1A Data Product to reflect the changing data type.Inventory Metadata of Level 1B Data Product has modified based on the concept of “Unified” Inventory Metadata for all ASTER products and related requirements.2-59  chg. del.2.5 TIR Band 13 Swath 2. chg.Ancillary and Supplement data are newly added to Level 1B Data Product.4 TIR Band 12 Swath 2.2-1 p.2 Data Structure: Figure 2.6.6. 2. Several objects described in Italics  12.3. 3.1 Inventory Metadata .3 GDS Generic Metadata: .3. Dimension Size: Record size is added as nominal value.6.3.1.New Data type ‘Geolocation Fields Data’ is added to Figure 3. ShortName Item 1  add. GenerationDateandTime Item 4 metadata add.1.3.Change Details-1 (4/6) (Ver. . 2.3.Supplement data volumes are revised. β 2. p. 2.0) Ver. chg. 1-6 .6.3.3.6.7 ~ 8 Inventory mv.3.3-5 p.

(x = 1 ~ 4) .3.4 Unit Conversion Coefficients: Offset value is revised.1.3. 1.2.1 chg. Item x.These objects are deleted on account that all images are stored to one swath at every subsystem. .The descriptions of items concerning SWIR Band-5.6.7 Bad Pixel Information .3-21 add. Image Statistics: Description is revised.3.3. Item x. β) Ver. 1-7 . Item x. Item x. 3.3. Item x.4 Item x.3. 3.3-21  3.1.Descriptions of some items in Product Specific Metadata(VNIR) have been modified to reflect the discussion results in the ASTER Science Team.5 Item x.3. Item x. p.3-21 (Mercator → SOM) chg.1.2 Item x.2 Item x.HDF file attribute name is changed on account of Toolkit's update.12.4 chg.2 Ancillary Data .1 chg. 2 Item x. SWIR. 2 Item x.3. .3-51 p.2 chg.3N.3.The descriptions of items concerning VNIR Band-2. Item x.3. Number/List of Bad Pixels: Descriptions are revised. vgroup name: VNIR_Group is changed to VNIR.0 Update Comments (based on Ver. and 2 chg.1.3.2 VNIR Group . and 2 Item x.3.2. Number/List of Bad Pixels: Descriptions are revised. Map projection: Supported map projection is revised. Number/List of Bad Pixels: Descriptions are revised. Processing Parameters: Descriptions are revised.3.2 chg. .3.5 Item x.Descriptions of some items in Product Specific Metadata(SWIR) have been modified to reflect the discussion results in the ASTER Science Team.4 Item x. Image Statistics: Description is revised.14 are omitted on account that these items are created in the same manner (similar to TIR Band-10).3 Product Specific Metadata(VNIR) . 3.Descriptions of some items in Product Specific Metadata(TIR) have been modified to reflect the discussion results in the ASTER Science Team. chg. . 1. and 2 chg.1.5 Item x. chg. vgroup class: 1B (processing level) p.3 VNIR Band 2 Swath 3.2 Item x. Processing Parameters: Descriptions are revised.3B are omitted on account that these items are created in the same manner (similar to VNIR Band-1). β ⇒ Ver. Item x.5 other parameters are deleted.3-51 p. Item x.9 are omitted on account that these items are created in the same manner (similar to SWIR Band-4).0) Ver.4 VNIR Band 3N Swath 3. Item x.5 other parameters are deleted.5 VNIR Band 3B Swath .HDF file attribute name is changed on account of Toolkit's update.4 Product Specific Metadata(SWIR) .All image data are stored to only 1 Swath Object mapping with the newly added geolocation table. Image Statistics: Description is revised.HDF file attribute name is changed on account of Toolkit's update.1 chg. chg.5 Product Specific Metadata(TIR) .2.3.13. (x = 1 ~ 5) . β 3.7.The contents of VNIR Group are modified to reflect the discussion results in the ASTER Science Team. 3. p. TIR) and stored as a new data object.Ancillary data is added as a new data object ‘Ancillary_Data’. Processing Parameters: Descriptions are revised.4 Item x.2 chg.Change Details-1 (5/6) (Ver.8. Item x.4 Unit Conversion Coefficients: Offset value is revised. (x = 1 ~ 6) . 2 Item x. chg. Unit Conversion Coefficients: Offset value is revised.Product specific attributes ‘List of Bad Pixel’ for all processed bands are divided from Product Specific metadata(VNIR. 3.5 other parameters are deleted.2.1.3.1.2 VNIR Band 1 Swath 3.The descriptions of items concerning TIR Band-11.

1-8 .3.3.3.3 VNIR Supplement Data .VNIR Supplement data is added as a new data object ‘VNIR_Supplement’.

SWIR Supplement data is added as a new data object ‘SWIR_Supplement’. .3.3. chg. .3. β 3.6 SWIR Band 8 Swath 3.3 SWIR Group . vgroup class: 1B (processing level) p. 1. 10.The contents of SWIR Group are modified to reflect the discussion results in the ASTER Science Team.3.4.These objects are deleted on account that all images are stored to one swath at every subsystem.3-25  3.5 SWIR Band 7 Swath 3.3 SWIR Supplement Data .3.6 TIR Band 14 Swath .All image data are stored to only 1 Swath Object mapping with the newly added geolocation table.4 TIR Band 12 Swath 3. β) Ver.3 SWIR Band 5 Swath 3.3-55. NOTES: add.3.3-2.3. vgroup name: SWIR_Group is changed to SWIR.3.3.4 TIR Group .4 SWIR Band 6 Swath 3.4.3.3.3. chg.Abbreviations and Acronyms are refreshed. p.4-2 is revised 4.3-23  Dimension Size of geolocation fields: Number of lattice point Table 3.2 TIR Band 10 Swath 3.3 TIR Band 11 Swath 3.0 Update Comments (based on Ver. chg. 8.3.7 SWIR Band 9 Swath .3.: deleted item mv.All image data are stored to only 1 Swath Object mapping with the newly added geolocation table. 57.: moved item 1-9 . Table 3.3. 60 3.3.These objects are deleted on account that all images are stored to one swath at every subsystem.TIR Supplement data is added as a new data object ‘TIR_Supplement’. 56.3 TIR Supplement Data . chg.4. p. Abbreviations and Acronyms .4.3.3-23 add.3. 3. vgroup class: 1B (processing level) p.4.0) Ver.Change Details-1 (6/6) (Ver.2 SWIR Band 4 Swath 3.3. 59.5. vgroup name: TIR_Group is changed to TIR.3. 3. 6.: added item chg.3-25 add.The contents of TIR Group are modified to reflect the discussion results in the ASTER Science Team.: changed item del.5 TIR Band 13 Swath 3.3. 12 Block Size: Block Size is revised. 1.3-23 58.4.3. p.3. There are some additional corrected and modified parts that are hardly interpreted on account of the obscured expression. p. β ⇒ Ver.3-61 p.3-55 p. 3.

1. chg. .3.3. 1.8 4. is corrected.1-1 Processing chg.The format information is added to the description of the “IDofASTERGDSDataGranule”.1) Update Comments (based on Ver.3 4.3. . 3N.The decriptions and the objects are added to the “DestripeParameter”s. 3.3. 3.8 chg. chg. and the newest version of them apply to this specification.0 Ver.5 Product Specific Metadata(SWIR) . chg. ASTER Level1 Data Products Specification p. 4. Algorithm Development Specification: ASTER Level-1 Data p.1 Applicable Documents. FirstPixelAddressGroup Item 4.6.6.2-1 2.6. 3.1.1. 1. UnitConversionCoefff4 Item 1.The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions. GeometricCorrection1. (TBD in Ver. .The description of characteristics is modified to remove obscurity. BoundingRectangle Item 6 Item 6 chg. (TBD in Ver.The decriptions and the objects are added to the “DestripeParameter”s.3 Time Code Format .7.6. DestripeParameter4 Item 1. “Ancillary Group” Figure 2.0) Ver. SingleDateTime Item7 Item 7 2. 1.3. .7 2. Item 1. It is because “DataID” (Data ID) and “GenDT” (Generation Date and Time) of Level-0 data cannot be acquired by PGE during Level-1A generation.7 Item 1.The description of the “SingleDateTime” is slightly changed to remove the obscured expression. UnitConversionCoefff1.0) chg.2 Data Structure .7.6 Product Specific Metadata(TIR) . 1. 3B Item 1. Item 1.6 chg. DestripeParameter10 Item 1. DestripeParameter1. 1. Item 8 Item 8 2.2 ASTER Generic Metadata .The nominal values for “GeometricCorrection” are corrected.3.Change Details-2 (1/3) (Ver.The data stored in the elements of “SourceDataProduct” are changed.3.Some of the documents were revised.1.7 2.6 4.6 Item 1. (TBD in Ver.7 2.7. 1. 3B Item 1.3.3 chg.4 Product Specific Metadata(VNIR) .1-1 1. 3.The description of the Spacecraft Time Format is slightly revised to remove the obscured expression.The misprinting in the description about “decimal fraction of a second”(d→d).1-1 p.0) chg.The decriptions and the objects are added to the “DestripeParameter”s. 3B Item 1. 4. 1-10 .2 Cloud Coverage Table . 3N.1-1 p.1 1.3. UnitConversionCoefff10 Item 1. .“Ancillary Group” is added to the figure of the data structure. add. Item 1.The nominal value of “Ncycles” of “FirstPixelAddressGroup” is changed to 10. 1. chg.2-1 Figure 2.0. 2.1. 1.1. . the nominal values in along-track direction and those in cross-track direction were described oppositely. SourceDataProduct.1-1 p.0 ⇒ Ver. 4.3.6 chg. .The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions.7. 3N.6 chg. ‘N/A’s are stored in those elements.1 Inventory Metadata . In version 1. 3. 3.7 Item 1. Interface Specification: ASTER Level-1 Data Processing p.6 Item 1.7 Item 4.1-1 chg. .The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions. IDofASTERGDSDataGranule Item 1 Item 1 chg.The description of the “BoundingRectangle” is slightly changed to remove the obscured expression.0) .

1. . which consists of Ancillary data records.The nominal record number is modified to reflect the discussion results with the ASTER Science Team.3-1 Table 2. UnitConversionCoefff4 Item 1.3.2 Data Structure .3. Variable Size of “Velocity” Table 2.The misprints in the dimension size and in the nominal record count number are corrected.3.The resolution and range of “Attitude Rate” are corrected. according to description in ATBD.5 3.3. Variable Size of “Magnetic_Coil” Table 2. chg.5-1 Table 2.3.2-1 3.3.3. SourceDataProduct.The variable size of some field data is changed to store them correctly.0 ⇒ Ver.3-1 chg.3.The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions.3.1.2 SWIR Band 4 Swath .3-1 Table 2.1. Variable Size of “Attitude_Rate” Table 2.1 2.The data stored in the elements of “SourceDataProduct” are changed.3.7 TIR Supplement Data .3. add. UnitConversionCoefff1 Item 1.5 Item 1.3-1 chg. is added.The misprint in the nominal record count number is corrected.5 Product Specific Metadata(SWIR) .1) Update Comments (based on Ver. No. (Item number) 12 ~ 49 Table 2. 1.“TBD”s in the description of VNIR Supplement Data are changed to “Spare”.1. chg.2-1 Figure 3.3.5-4 2.3-1 Table 2.5-1 2.3. 1.5 3.6 VNIR Supplemet Data . chg.5-4 are corrected.3.3. chg.3. chg.0) Ver.The nominal record count number for Chopper and Encoder data is added.5. Variable Size of “Attitude_Angle” Table 2.3.“Ancillary Group” is added to the figure of the data structure. 1.6. (Item number) 45 ~ 57 Table 2.3-1 Table 2.2 ASTER Generic Metadata .3. 1.5 Item 1.0 Ver. ‘N/A’ is stored in “DataTyp” (Data Type). .The range of “Solar Position” and “Moon Position” are changed to reflect the discussion results with the ASTER Science Team. ParallaxOffset Table 2.3-1 chg.8 SWIR Supplement Data . No.5 Item 1.3-1 Table 2.The format information is added to the description of the “IDofASTERGDSDataGranule”.3.5 1-11 .The misprints in the item numbers in Table 2.The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions. .The description about vgroup.3.5-4 Table 2.4.Unit of “ParallaxOffset” is corrected to degree. Item 8 Item 8 3.3-1 chg. chg. chg.3.3. Variable Size of “Time_Conversion” Table 2. UnitConversionCoefff10 Item 1. “Ancillary Group” Figure 3. 1.3.Change Details-2 (2/3) (Ver. .3.4-4 Table 2. IDofASTERGDSDataGranule Item1 Item 1 chg.5.3. Variable Size of “Position” Table 2. .4 Product Specific Metadata(VNIR) . .The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions.3.3-1 2. 3.3.3 Ancillary Data . chg. .3.3-1 Table 2.4-4 2.6 Product Specific Metadata(TIR) .3-1 chg.

0) Ver.3. 1. chg.1) Update Comments (based on Ver.Change Details-2 (3/3) (Ver.: moved item 1-12 .The nominal record number is modified to reflect the discussion results with the ASTER Science Team.: changed item del. Dimension Size of “Latitude” and “Longitude” Table 3.The description about vgroup. 1.3.3.“Dimension Size” of geolocation field is redesigned to reflect the discussion results with the ASTER Science Team.2 Ancillary Data . 3. which consists of Ancillary data records. 1.3-2 Table 3.3-2 There are some additional corrected and modified parts that are hardly interpreted on account of the obscured expression.: deleted item mv. 1. 1. .: added item chg. is added.2 VNIR Swath . NOTES: add.3.3.0 ⇒ Ver.1 3.0 Ver.

3.2 ASTER Generic Metadata .The description of characteristics is modified to remove the ambiguous expressions.3. 1. chg.6 VNIR Supplemet Data .1.1-1 p.1-1 p.1-1 chg. UnitConversionCoefff1. 3N.The data stored in the elements of “SourceDataProduct” are changed.3.2 1.2-1 Figure 2. 3B Item 1.1. chg. .4. No.1 Applicable Documents.: added item chg.“Ancillary Group” is added to the figure of the data structure.1-1 Processing chg.7 Item 1.6 Map Projection Parameters .1.4-4 NOTES: add. 3B Item 1. IDofASTERGDSDataGranule Item 1 Item 1 chg.Change Details-3 (Ver. 3N.7 2. 1.3.: changed item del. . 1.3.1-1 1.7 2.1 ⇒ Ver.“TBD”s in the description of VNIR Supplement Data are changed to “Spare”.The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions. “Ancillary Group” Figure 2. Item 8 Item 8 2.The data stored.4-4 Table 2. add.6 Product Specific Metadata(TIR) .2 Cloud Coverage Table . DestripeParameter4 Item 1.1 Ver. SourceDataProduct. (Item number) 45 ~ 57 Table 2.Some of the documents were revised. and the newest version of them apply to this specification. GeometricCorrection1.The descriptions of the map projection parameters are added.3.3 chg.: deleted item mv.3 Item 1.2-1 2. 1.1-1 p.: moved item 1-13 .2 Data Structure . It is because “DataID”. chg.3. chg. 2. according to description.1. ASTER Level1 Data Products Specification p. 1. chg. Algorithm Development Specification: ASTER Level-1 Data p. DestripeParameter10 Item 1. chg.6 Item 1.7 Item 1. Interface Specification: ASTER Level-1 Data Processing p.4 Product Specific Metadata(VNIR) .The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions.3.The data stored in the “ConUnit” of “UnitConversionCoeff”s are added to the descriptions.6 2.1.1) Ver.5 Product Specific Metadata(SWIR) .2) Update Comments (based on Ver. 2.

5.3 Item 4.3.2 SWIR Band 4 Swath .3.9 NOTES: add.3.2 ASTER Generic Metadata .2 VNIR Band 1 Swath .: moved item 1-14 . Revised to accommodate a processing scene : nominal is Table 2.9 Item 10.4-3 modified.2 ASTER Generic Metadata .“SceneOrientationAngle” in the description of ASTER Generic Metadata is changed to “MapOrientationAngle”.3 2. SatelliteVelocity Item 10 Item 10 2. 1.3.Number of lines in frame for VNIR 3B is revised.6 VNIR Supplement Data . chg SatellitePosition Item 9 Item 9 chg. SatelliteVelocity Item 7 Item 7 2.The nominal record count number is modified. 1.3.2 TIR Band 10 Swath .3) Update Comments (based on Ver. ImageDataInformation3B Item 4.The coordinate system of “SatellitePosition” and “SatelliteVelocity” is revised.The coordinate system of “SatellitePosition” and “SatelliteVelocity” is revised.4-3 Table 2. .1.2 Item 4.: added item chg.9 Item 10.3.The nominal value for “GeometricCorrection3B” is modified.The nominal record count number is modified. chg SatellitePosition Item 7 Item 7 chg. chg.3 Ancillary Data .2 chg.: deleted item mv. chg. 2. Dimension Size of mapping to geolocation array : ImageData Table 2.4.3.3. 1.5 VNIR Band 3B Swath .4-3 is modified.4-3 Table 2. GeometricCorrection3B Item 4.9 2.4. SatellitePosition Item 6 Item 6 chg.The explanation of “SceneOrientationAngle” is modified.6.The coordinate system of “SatellitePosition” and “SatelliteVelocity” is revised. chg.2 Ver. MapOrientationAngle Item 10.4 Product Specific Metadata(VNIR) .Change Details-4 (Ver. chg.1. 1. 2.2 ⇒ Ver.3.2) Ver.3. SatelliteVelocity Item 8 Item 8 3.1.3 2.3. chg SceneOrientationAngle Item 10. 1.: changed item del.Number of lines in frame for VNIR 3B is revised.3.3. 2.4. chg.

South Dakota.S. located at the U.0). Geological Survey’s EROS Data Center in Sioux Falls. These data are distributed by the EROS Data Center Distributed Active Archive Center (EDC DAAC). which are generated from the software of ASTER Level-1 Data Processing Subsystem (Version 2. 1-15 . ACKNOWLEDGMENT The ASTER level-1 data product generation software needs the GTOPO30 in the processing subsystem.00).PREFACE This Specification defines Level-1A and 1B Data Products (GDS L1PGE versionVersion 04.

2 SWIR Band 4 Swath -----------------------------------------------------------------------------------.1211 2.4843 2.1 Metadata-----------------------------------------------------------------------------------------------------------.6 TIR Band 14 Swath-------------------------------------------------------------------------------------.3.3329 2.4338 2.6.5045 2.1.5 TIR Band 13 Swath-------------------------------------------------------------------------------------.6.5247 2.3.5 SWIR Band 7 Swath -----------------------------------------------------------------------------------.6862 3.3.5.3.5.6.2 1. Level 1A Data Product ----------------------------------------------------------------------------------------------------.1 Inventory Metadata -----------------------------------------------------------------------------------------.1 2.1.6.3.4 2.3.4843 2.8 SWIR Supplement Data--------------------------------------------------------------------------------.3.6458 2.3632 2.2 ASTER Generic Metadata---------------------------------------------------------------------------------.1 1.4843 2.1. Level 1 Overview ----------------------------------------------------------------------------------------------------------.5.2 Coordinates Systems --------------------------------------------------------------------------------------------------.5550 2.1 Overview -------------------------------------------------------------------------------------------------.1.5 SWIR Group --------------------------------------------------------------------------------------------------.3.1 Overview -------------------------------------------------------------------------------------------------.3.4.5.1 1.4 TIR Band 12 Swath-------------------------------------------------------------------------------------.1 1.2 Reference Documents--------------------------------------------------------------------------------------------.3 SWIR Band 5 Swath -----------------------------------------------------------------------------------.4035 2.3.4 VNIR Group --------------------------------------------------------------------------------------------------.5 Strip Observation Mode ----------------------------------------------------------------------------------------------.2724 2.2120 2.1312 2.3.4 Data Type Definitions ------------------------------------------------------------------------------------------------.6761 2.4035 2.3.1.1 Applicable Standards -------------------------------------------------------------------------------------------------.3.5146 2.1 2.6.6256 2.3.2 VNIR Band 1 Swath------------------------------------------------------------------------------------.3 Time Code Formats ---------------------------------------------------------------------------------------------------.3 GDS Generic Metadata --------------------------------------------------------------------------------.2 Data Structure ---------------------------------------------------------------------------------------------------------.5.4 VNIR Band 3N Swath ---------------------------------------------------------------------------------.4.6 SWIR Band 8 Swath -----------------------------------------------------------------------------------.4540 2.3.6 TIR Group-----------------------------------------------------------------------------------------------------.1.4 SWIR Band 6 Swath -----------------------------------------------------------------------------------.3 VNIR Band 2 Swath------------------------------------------------------------------------------------.3.3.6 2.4 1.7 SWIR Band 9 Swath -----------------------------------------------------------------------------------.6256 2.1.3 Ancillary Data ------------------------------------------------------------------------------------------------.1 2.5.6559 2.4439 2.3.3.4641 2.3 Data Format ------------------------------------------------------------------------------------------------------------.3 TIR Band 11 Swath-------------------------------------------------------------------------------------.5 VNIR Band 3B Swath----------------------------------------------------------------------------------.3.2 TIR Band 10 Swath-------------------------------------------------------------------------------------.3.3.7 Bad Pixel Information----------------------------------------------------------------------------------.5.3.6660 2.6.5 Product Specific Metadata(SWIR) -------------------------------------------------------------------.6 VNIR Supplement Data--------------------------------------------------------------------------------.4 Product Specific Metadata(VNIR)--------------------------------------------------------------------.6 Map Projection Parameters ------------------------------------------------------------------------------------------.3. Level 1B Data Product ----------------------------------------------------------------------------------------------------.3.6.3.4.5.4.3 2.6 Product Specific Metadata(TIR) ----------------------------------------------------------------------.3 2.1 1.3.3733 2.4035 2.5449 2.3.4.5348 2.1.3 1.3.7 TIR Supplement Data ----------------------------------------------------------------------------------.7 2.5 1.3.3.3.1 Overview ---------------------------------------------------------------------------------------------------------------.4.Table of Contents 1.3.2 Cloud Coverage Table---------------------------------------------------------------------------------------.1.1 Overview -------------------------------------------------------------------------------------------------.1 1-16 .3.6256 2.1 Applicable Documents ------------------------------------------------------------------------------------------.

3028 Appendix A.3.3 Data Format ------------------------------------------------------------------------------------------------------------.2725 3.1 Inventory Metadata --------------------------------------------------------------------------------------------.6 Product Specific Metadata(TIR) -------------------------------------------------------------------------.2321 3.3.3.4 Product Specific Metadata(VNIR)-----------------------------------------------------------------------.2 Ancillary Data ---------------------------------------------------------------------------------------------------.2119 3.3.1 Metadata-----------------------------------------------------------------------------------------------------------.5 Product Specific Metadata(SWIR) ----------------------------------------------------------------------.3.1 3.1211 3.1816 3.2826 3.3.1.2 SWIR Swath ------------------------------------------------------------------------------------------------.1 3.1.3. Programming Model -----------------------------------------------------------------------------------------.4 SWIR Group -----------------------------------------------------------------------------------------------------.2 Data Structure ---------------------------------------------------------------------------------------------------------.3 TIR Supplement Data -------------------------------------------------------------------------------------.1 Overview---------------------------------------------------------------------------------------------------------------.1110 3.1 Overview ----------------------------------------------------------------------------------------------------.2725 3.3.2 Swath -------------------------------------------------------------------------------------------------------------------.1.4.1.2624 3.3 VNIR Group -----------------------------------------------------------------------------------------------------.1.5 TIR Group--------------------------------------------------------------------------------------------------------.1 A.3.2927 3.3.3.2422 3.3 VNIR Supplement Data-----------------------------------------------------------------------------------.2 VNIR Swath ------------------------------------------------------------------------------------------------.3.5.3 SWIR Supplement Data-----------------------------------------------------------------------------------.1 1-17 .3.5 3.5.1 Abbreviations and Acronyms -----------------------------------------------------------------------------------------------.3.2 TIR Swath --------------------------------------------------------------------------------------------------.1.1 Overview ---------------------------------------------------------------------------------------------------------------.3 3.4.7 Bad Pixel Information-------------------------------------------------------------------------------------.2523 3.3 GDS Generic Metadata -----------------------------------------------------------------------------------.3.3.2927 3.1 Overview ----------------------------------------------------------------------------------------------------.3.2422 3.3.1413 3.3 3.2725 3.3.3.2927 3.4.3.1.3.3 3.3.3.5.1 Overview ----------------------------------------------------------------------------------------------------.3.2 ASTER Generic Metadata ------------------------------------------------------------------------------------.1 A.

. unless cited otherwise herein. Nov. Jul.1r3.2. 1997 HDF-EOS Library User's Guide for the ECS Project. 31.2. [ 8] 333-CD-004-001 1997 Science Data Processing Segment (SDPS) Database Design and [ 9] 311-CD-002-005 Database Schema Specifications for the ECS Project. Jun. Hughes Information Technology Systems. 1997 [ 2] CCSDS 641. α. 1996 [ 2] ERSDAC-LEL/9-16 Algorithm Development Specification: ASTER Level-1 Data Processing (for Ver. Volume 2: [ 5] 170-TP-006-002 Function Reference Guide. Blue Book. Interface Control Document between EDOS and ASTER [ 1] 510-ICD-EDOS/ASTER GDS.3. Version 2. the National Center for Super[ 6] none computing Applications at University of Illinois at UrbanaChampaign. Jul. prepared by Level-1 Data Working Group.2 Reference Documents The following documents are used as background reference documents related to this Specification. 3. 1996 [ 7] WBS-WP-003-001 The HDF-EOS Swath Concept. Mar.0+). Hughes Information Technology Systems.4). Apr. Issue 2.1). 31.2A). Level 1 Overview 1. 1998 (in Japanese) [ 3] ERSDAC-LEL/9-13 ASTER Level 1 Data Products Specification (Science Version. 1996 [ 1] ERSDAC-LEL/8-9 1.0 Draft). Mar.0-B-2 Time Code Formats. 1994 (in Japanese) 1-1 . Algorithm Theoretical Basis Document for ASTER Level-1 Data Processing (Ver. Jan. Revision 1. Apr.1 Applicable Documents The following documents apply to this Specification in whole. 1995 Release B. Ver. 1998 (in Japanese) [ 5] AG-S-E-0409-R03 ASTER GDS Core Meta Data Specification (Version 1. Japan. and those reference documents that indirectly apply to obtain background information related.1. CDRL B311. A White Paper for ECS Project.0 SCF Toolkit Users Guide for the ECS Project.1. June. 2001 Interface Specification: ASTER Level-1 Data Processing (for [ 4] ERSDAC Ver. Volume 1: [ 4] 170-TP-005-003 Overview and Examples. Apr. 1. β ). April 1990 HDF-EOS Library User's Guide for the ECS Project. 30. Mar. 1998 [11] ERSDAC-LEL/7-5 Interface Specification: ASTER Level-1 Data Processing (for Ver. Blue Book. ASTER Science Team. May 1996 [10] ERSDAC-LEL/9-18 ASTER Browse Data Products Specification (Science Version.0-B-1 Parameter Value Language Specification (CCSD006). 1997 HDF User's Guide Version 4. 31.1. 1. Ver.2. 22. May 1992 [ 3] CCSDS 301. 1.0).1 Applicable Standards This section identifies documents that directly apply in defining this interface specification.

(1) Spacecraft Reference Frame . with north positive [Reference Direction] X-axis : directed toward the prime (Greenwich) meridian 1-2 .2 Coordinates Systems This section describes the definition of the following coordinates systems used in this specification. anti-parallel to the angular momentum (4) Earth-Centered Inertial Coordinates System (Mean Equator and Equinox of J2000) [Origin] Center of the Earth [Reference Plane] X-Y Plane : plane of Earth's mean equator Z-axis : along Earth's rotational axis. forming a right-handed coordinates system.attitude reference frame of spacecraft bus [Origin] Spacecraft Center of Mass [Reference Direction] X-axis : Roll axis Y-axis : Pitch axis Z-axis : Yaw axis (3) Orbital Reference Frame .Spacecraft Reference Frame .Earth Greenwich Coordinates System Note: Above all coordinates systems are a cartesian coordinates system.Orbital Reference Frame . .1. with north positive [Reference Direction] X-axis : directed toward the vernal equinox (5) Earth Greenwich (Earth-Centered Rotating: ECR) Coordinates System [Origin] Center of the Earth [Reference Plane] X-Y Plane : plane of Earth's equator Z-axis : along Earth's rotational axis.reference frame of flight attitude on orbit [Origin] Spacecraft Center of Mass [Reference Plane] X-Y Plane : normal to the position vector Z-axis : directed toward geocentric nadir [Reference Direction] X-axis : the vector cross product between Z-axis and Yaxis that is normal to the orbit.Earth-Centered Inertial Coordinates System .

or 31 according to the month) : a separator : a two character subfield for hours. this information is not included in these products). for decimal fraction of a second. (1) CCSDS ASCII Calendar Segmented Time Code (ASCII) CCSDS ASCII segmented time code is composed of a variable number of ASCII characters forming the T-field. The first bit is always ‘0’. The time code formats can be represented as a combination of a preamble (P) field and a time (T) field. Washington DC 20546). (CCSDS 301.0-B-2) issued by the Consultative Committee for Space Data Systems (NASA Code-OS. YYYY MM DD T hh mm ss d→ →d Z : a four character subfield for year. ASCII time code variations are UTC (Universal Time Coordinated) based and leap second corrections are made. Width (bits) 16 32 16 Description Days since 1958 January 1. (n < 6). with each digit in range 0 ~ 9 (optional) : a terminator (2) Spacecraft Time Format (CDS) Spacecraft Time Format contains the 64-bit CCSDS Day Segmented Time Code (DST) Tfield. which rolls over at a module specified for each counter.d…dZ where.3 Time Code Formats Time and Date described in Level 1A and 1B Data Products are expressed in two formats. cascaded with the adjacent counters. Each segment represents the state of a binary counter. April 1990. Time Code Formats. 29. 30. Spacecraft Time Code consists of a selected number of continuous time segments. The format for ASCII Time Code A as used in ASTER Level-1 Data Processing Subsystem: YYYY-MM-DDThh:mm:ssZ or YYYY-MM-DDThh:mm:ss.. Issue 2. But the P-field is implied and not actually transmitted (i. with values 00 ~ 59 (00 ~ 60 in a positive leap second interval. with value in range 1970 ~ 2038 : a two character subfield for month with values 01 ~ 12. Millisecond of Day (number milliseconds since begining of current day) Microsecond of Millisecond (number microseconds in current millisecond) 1-3 Units Days msec µsec . leading zeros : a two character subfield for day with values in the range 01 ~ eom (where eom is 28. Both time code formats are defined in CCSDS Blue Book. CCSDS ASCII Time Code (A format) and Spacecraft Time Format (CCSDS Day Segmented Time Code: CDS). 00 ~ 58 in the case of negative leap second) : an n-character subfield. with values 00 ~ 59 : a two character subfield for seconds. with values 00 ~ 23 : a two character subfield for minutes.1.e. NASA.

1. Definition Name DATETIME FLOAT DOUBLE STRING INT8 UINT8 INT16 UINT16 INT32 UINT32 INTEGER Description CCSDS ASCII Time Code (A format) IEEE single-precision (32-bit) format float type IEEE double-precision (64-bit) format float type A text string value consists of a text string lexical elements 8-bit integer type 8-bit unsigned integer type 16-bit integer type 16-bit unsigned integer type 32-bit integer type 32-bit unsigned integer type Same as INT32 1-4 .4 Data Type Definitions These definitions are used in comparison expressions to determine the type of data products.

14” ‘ASTER_TIR’ OFF OFF “XXXX3N3BXXXXXXXXXXXXXXX ‘ASTER_STEREO’ XXXXXXX” ON ON “XXXXXXXXXXXXXXXXXXXX101 ‘ASTER_TIR’ 1121314” ON ON “XXXXXXXXXXXXXXXXXXXX101 ‘ASTER_TIR’ 1121314” NOTES: (*1) Refer to the table 2. XXXXXX” OFF ON “XXXXXXXXXXXXXXXXXXXX101 ‘ASTER_TIR’ 1121314” ON ON “XXXXXXXX04050607080910111213 ‘ASTER_SWIR’. item 9.5-2 expresses the conceptual view of the strip observation mode.1 ‘ASTERObservationMode (*2) Refer to the table 2.3. item 9. ‘ASTER_SWIR’.3. ‘ASTER_TIR’ OFF OFF “01023N3BXXXXXXXXXXXXXXXX ‘ASTER_VNIR’.5-1 shows the methodological concept for deciding the strip observation mode at sensor operate. Table 1. item 2 ‘SensorShortName (*4) See the table 1.1-2.2.3 ‘ProcessedBands (*3) Refer to the table 2.1-2 Coneptual view of strip observation mode. Table 1.3. Table 1.5-1 Strip Observation Mode ASTER OBS Mode*1 Processed Bands Sensor Short Name VNIR1 VNIR2 SWIR TIR ON ON ON ON OFF OFF OFF OFF OFF ON ON ON OFF OFF ON ON “01023N3B0405060708091011121314” ‘ASTER_VNIR’.1-3.1. 1-5 Strip Observation Mode Estimatable Table Mode VST (1) VST+T (6) V (2) T (3) ST ST+T V Stereo (4) (7) (5) VST+T (6) ST+T (7) .5 Strip Observation Mode Following definitions are used in comparison expressions to determine the strip observation mode.1-2.

Table 1.5-2 Conceptual view of strip observation mode Sensor Sensor operation by mode based on time coordinate Time (1) VST (full) mode VNIR1 VNIR2 SWIR TIR (2) V mode VNIR1 VNIR2 (3) T mode TIR (4) ST mode SWIR TIR (5) V Stereo mode VNIR2 (6) VST+T mode VNIR1 VNIR2 SWIR TIR (7) ST+T mode SWIR TIR 1-6 .

The software uses the geo-coordinate transformation (GCT) tools. contained in the SDP Toolkit routines.0 1-7 .6 Map Projection Parameters This section describes the definition of the map projection parameters used in L1B processing.) (*2) The software of ASTER Level-1 Data Processing Subsystem uses the TM in place of UTM. Latitude is negative south of equator.1. for the treatments of the scene across the zone boundary. (Longitude is negative west of Greenwich.5201613) PFlag End of path flag for Landsat: 0 = start of path. counter-clockwise from equator AscLong Longitude of ascending orbit at equator PSRev Period of satellite revolution in minutes LRat Landsat ratio to compare for confusion at northern end of orbit (ASTER: 0. Table 1. where.5-3 Projection Transformation Package Projection Parameters Elements (2/2) Name UTM*2 LAMCC PS EQRECT SOM 9 PSRev Array Element*1 10 11 12 LRat PFlag 13 zero NOTES: (*1) All array elements with blank fields are set to zero. based on the commonly available packages general cartographic transformation package (GCTP).5-3 Projection Transformation Package Projection Parameters Elements (1/2) Name UTM*2 LAMCC PS 1 SMajor SMajor SMajor EQRECT Sphere SOM SMajor 2 SMinor SMinor SMinor 3 Factor STDPR1 Array Element*1 4 5 CentMer STDPR2 CentMer LongPol CentMer SMinor IncAng AscLong 6 OriginLat OriginLat LTrueScal e LTrueScal e 7 FE FE FE 8 FN FN FN FE FN FE FN Table 1. 1 = end of path (ASTER: 0) zero 0. SMajor Semi-major axis of the ellipsoid SMinor Semi-minor axis of the ellipsoid Sphere Radius of reference sphere STDPR1 Latitude of the first standard parallel STDPR2 Latitude of the second standard parallel CentMer Longitude of the central meridian OriginLat Latitude of the projection origin FE False easting in the same units as the semi-major axis FN False northing in the same units as the semi-major axis LTrueScale Latitude of true scale LongPol Longitude down below pole of map Factor Scale factor at central meridian CentLat Latitude of center of projection IncAng Inclination of orbit at ascending node.. All angles are in radians.

2-1. V. Some category shall not set in the product. (2) Data Structure The physical format of Level 1A Data Product is shown in Figure 2. Level 1A Data defines a scene center on the spectral image as (l.2-1 shows the conceptual view of the physical format of the product in case of full mode (VST) operation.e. p). T. Each file contains a complete 1-scene image data extracted from Level-0 data and corrected for the SWIR and TIR detector's alignment. and the calculated cloud coverage values. i. ST.. Note: VNIR (4 bands) and SWIR (6 bands) image data are 8-bit unsigned integer science data. Data structure represented in Figure 2. and Swath Layout parts in one HDF file. 2-1 . where ‘l’ and ‘p’ are estimated from the following equations. stored to the Swath object at every band. in case that it can not be applied to the dataset on account of the selected operational mode. Vgroup/Vdata. the satellite ancillary data. l = Tranc ( number of lines in scene / 2) + 1 p = Tranc (number of pixels per line / 2) + 1 Tranc(x) truncates the value to the greatest integral value less than or equal to x. spacecraft's supplement data. SDS.1 Overview Level 1A Data Product is an HDF file. Furthermore it includes also the radiometric. Level 1A Data Product 2. V stereo. All of these data are stored together with Metadata. 2. the geometric and the SWIR parallax correction tables.2. etc.2 Data Structure (1) Data Type Level 1A Data Product within HDF file is constructed from six categories of HDF data object. and TIR (5 bands) image data are 16-bit unsigned integer science data.

2-1 Physical Data of Level 1A Data Product 2-2 .Level 1A Data Product Inventory Metadata Metadata ASTER Generic Metadata GDS Generic Metadata Product Specific Metadata (VNIR) Product Specific Metadata (SWIR) Product Specific Metadata (TIR) Bad Pixel Informations Cloud Coverage Table Ancillary Data VNIR Group VNIR Band 1 Swath GeoFields (1D/2D) DataFields (1D/2D) Radiometric Coefficient VNIR Band 2 Swath VNIR Band 3N Swath VNIR Band 3B Swath non-mapping data mapping data Supplement Data SWIR Group SWIR Band 4 Swath SWIR Band 5 Swath SWIR Band 6 Swath SWIR Band 7 Swath SWIR Band 8 Swath SWIR Band 9 Swath Supplement Data TIR Group TIR Band 10 Swath TIR Band 11 Swath TIR Band 12 Swath TIR Band 13 Swath TIR Band 14 Swath Supplement Group Supplement Temp Supplement Chopper : these objects are similar to "VNIR Band 1 Swath". Supplement Encoder Figure 2.

refer to SCF Toolkit Users Guide for the ECS Project. (6) ProductSpecificMetadataTIR :including the attribute about band-10. This includes information that identifies a dataset. 14 data and input (Level0) data. 8. 5. which are named as follows. quality. 13. Metadata entries are described in Object Description Language (ODL) and CLASS system (for twodimensional arrays). and condition.2. contents. process and interpret the data. About concept and definition of master groups.1 Metadata Level 1A Metadata consists of seven Master Groups. Metadata can also provide information needed to decode. Appendix J. (1) InventoryMetadata (2) ASTERGenericMetadata (3) GDSGenericMetadata (4) ProductSpecificMetadataVNIR :including the attribute about band-1. 6.11. (7) BadPixelInformation :including the attribute about lists of bad pixels every band. 9 data and input (Level0) data.3 Data Format 2. 2-3 . giving characteristics such as its origin. 2. (5) ProductSpecificMetadataSWIR :including the attribute about band-4. The term “metadata” relates to all information of a descriptive nature that is associated with a product or dataset.3. 7. 12. and can include items such as the software that was used to create the data. Details are provided in Appendix J of the SCF Toolkit Users Guide (Reference [8]). 3N. 3B data and input (Level0) data.

2.Reference [9]). ‘ASTER’ fixed. group names are written in Bold characters.3. A group contains a set of objects that all have a similar theme. ‘AM-1’ fixed. 1 Group/Object Name ShortName type*1 string 2 SizeMBDataGranule double 3 ProductionDateTime datetime 4 5 6 PlatformShortName InstrumentShortName BoundingRectangle string string 1 WestBoundingCoordinate double 2 NorthBoundingCoordinate double 3 EastBoundingCoordinate double 4 SouthBoundingCoordinate double 2-4 Description The short name for information that identifies a dataset: ‘ASTL1A’ The volume of data contained in the granule.3. The attributes included in Inventory Metadata are associated with 311-CD-002-005 (DID311 -. and are written to the HDF file attribute named “coremetadata. Eastern-most coordinate of the scene expressed in longitude. Inventory Metadata contains ASTER Meta-Parameters in Generic header for ASTER GDS Products (about Generic header for ASTER GDS Products.1 Inventory Metadata (1) Indexes of Objects The object list of Inventory Metadata is shown in Table 2.1-1 List of Objects in Inventory Metadata (1/2) No.3. (In Table 2. . Northern-most coordinate of the scene expressed in geodetic latitude. Inventory Metadata attributes apply to the whole L1A product. Southern-most coordinate of the scene expressed in geodetic latitude. Unit: Mbytes Generation date and time of this Level 1A product.1-1.) Table 2. This block contains area coverage for a granule.1. see ASTER LEVEL 1 DATA PRODUCTS SPECIFICATION -.0”. Western-most coordinate of the scene expressed in longitude.Applicable [3]).1-1.3.

Unit: % The stating what reprocessing has been performed on this granule. The date of the nearest planned QA peer review in future. ‘reprocessed twice’. at which the center of the scene is observed. The percentage of missing data in the scene.1-1 List of Objects in Inventory Metadata (2/2) Group/Object Name SingleDateTime type*1 1 2 TimeofDay CalendarDate Review string string 1 FutureReviewDate string 2 ScienceReviewDate string No. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character). format: YYYYMMDD The date of the last QA peer review. ‘reprocessed n times’} The version of PGE The classification of the science data processing level: ‘1A’ The type of map projection used: ‘N/A’ NOTES: (*1) Object types used in Metadata are a. format: YYYYMMDD This block contains measures of quality for a granule. d. integer c. format: hhmmssd…dZ format: YYYYMMDD This block provides for dates and status as applicable for collection that are active. string 2-5 .Table 2. datetime: CCSDS A (UTC) Format b. Unit: % The percentage of out of bounds data in the scene. {‘not reprocessed’.3. 7 8 9 QAStats 1 QAPercentMissingData double 2 QAPercentOutofBoundsData double 3 QAPercentInterpolatedData double 10 ReprocessingActual string 11 12 PGEVersion ProcessingLevelID string string 13 MapProjectionName string Description This contains the time of day and calendar date. ‘reprocessed once’. Unit: % The percentage of interpolated data in the scene.

n = number of sensors ‘VNIR’ or ‘SWIR’ or ‘TIR’ pointing angle in degrees YYYY-MMDDThh:mm:ss.3.e.2. This container contains the level of the data acquisition gain for VNIR and SWIR. respectively. Format: ‘ASTL1A YYMMDDHH MMSSyymmddNNNN’ where. ‘ASTER-GDS’ fixed.3. see ASTER LEVEL 1 DATA PRODUCTS SPECIFICATION -. A group contains a set of objects that all have a similar theme... and others use SWIR band 6 or TIR band 11 for S+T or T. not associated with DID311. YYMMDD:observation date HHMMSS:observation time yymmdd:the data granule generation date NNNN:the data granule sequential No. The baseline of the scene location is VNIR band 2 for a set of 3 sensors V+S+T.2 ASTER Generic Metadata (1) Indexes of Objects The Object list ofASTER Generic Metadata is shown in Table 2. group names are written in Bold characters. 1 Group/Object Name IDofASTERGDSDataGranule type*1 string 2 3 4 ReceivingCenter ProcessingCenter PointingAngles string string 1 2 3 5 PointingAnglesContainer(n)*2 SensorName(n)*2 PointingAngle(n)*2 SettingTimeofPointing(n)*2 GainInformation GainInformationContainer(n)* 2 2-6 string double datetime Description This provides a unique identifier for location of a data granule held in ASTER GDS.dZ The information of the gain level.3. The ASTER Parameters are the specific attributes.Applicable [3]).0”. i.3. ASTER Generic Metadata contains ASTER Parameters in Generic Header for ASTER GDS Products (about Generic header for ASTER GDS Products.) Table 2.d.1.1-2 List of Object in ASTER Generic Metadata (1/5) No.1-2.1-2. Specification of the pointing angles of ASTER sensors. (per day) ‘EDOS’ fixed. . ASTER Generic Metadata attributes are written to the HDF file attribute named “productmetadata. (In Table 2.

(Version. Formats of these parameters are the same as Item 6. Version: Version No. (Version.1-2 List of Object in ASTER Generic Metadata (2/5) No. Issuancedate.’02’. (Version. Comments) where.’05’. Band Gain) where .3.’07’. Unit: % . Issuancedate: Issuance Date Comments: Comments The version information of the radiometric correction data. The version information of the geometric correction data. The version information of the Coarse DEM database. The information about the cloud coverage of the scene The percentage of cloud coverage for the whole scene.Table 2. The information about the quality of this product.’3N’.’0 6’.’3B’.’09’ Band Gain: for VNIR: ‘HGH’: high gain ‘NOR’: normal gain ‘LOW’: low gain for SWIR: ‘HGH’: high gain ‘NOR’: normal gain ‘LO1’: low gain 1 ‘LO2’: low gain 2 when data is not acquired or doesn't exist: ‘OFF’ Calibration information used to generate the geometric and radiometric correction tables.1.’08’. 5 1 Group/Object Name Gain(n)*2 6 CalibrationInformation type*1 string 1 GeometricDBversion string 2 RadiometricDBversion string 3 CoarseDEMversion*3 string 7 DataQuality 1 CloudCoverage 1 SceneCloudCoverage integer 2-7 Description (Band Number. Comments) where. Issuancedate. Comments) where. Issuancedate.’04’. Band Number: ‘01’. Formats of these parameters are the same as Item 6.1.

The information about sensors used to acquire data. GenDT: ‘N/A’ fixed. or not existing in the granule) . qclr) where.1-2 List of Object in ASTER Generic Metadata (3/5) Group/Object Name QuadrantCloudCoverage type*1 integer 8 SourceDataProduct string 9 InstrumentInformation No. qcll. DataTyp: Data type. (qcul. DataID: ‘N/A’ fixed. The types of ASTER operation. Observation) where. The observation mode of each sensor group.3. 7 1 2 1 ASTEROperationMode 2 ObservationMode string ObservationModeContainer(n) *2 1 ASTERObservationMode(n)*2 2-8 string Description The percentage for 4 quarters of a scene. qcur. The container of ASTER observation mode. GenDT.Table 2. (SGname. ‘OBSERVATION’ or ‘CALIBRATION’ or ‘TEST’ This group contains ASTER observation mode. DataTyp) where. qcul: upper left qcur: upper right qcll: lower left qclr: lower right Unit: % The information about the input data used for generating this Level-1A product. (DataID. SGname: ‘VNIR1’ or ‘VNIR2’ or ‘SWIR’ or ‘TIR’ Observation: ‘ON’ (data is acquired) or ‘OFF’ (data is not acquired. ‘PDS’ or ‘EDS’ or ‘DDS’.

14 is used in the granule generation) = XX (data corresponding to the band position marked with XX is not used) Example: Value = ‘XXXXXXXX04 05060708091011121314’ . ~ .3B. 02. ~ .3 ProcessedBands string 2-9 The status of all bands during observation.02. flag = 01. Format: set of flags described as 2-bytes string.3N.14 (data of band 01.3N.

el) where. SWIR and TIR. 0. (resolution of VNIR. az: azimuth angle in degree. The scene identifier defined by path. -90. resolution of TIR) Unit: meter This group contains the information about 4 corner coordinates of the scene.0 measured eastward from North. (lat. row and view. el: elevation angle in degree.1-2 List of Object in ASTER Generic Metadata (4/5) Group/Object Name SceneInformation type*1 1 ASTERSceneID integer 2 OrbitNumber*4 integer 3 RecurrentCycleNumber*4 integer 4 FlyingDirection string 5 SolarDirection double 6 SpatialResolution integer 7 SceneFourCorners No.0<el<90. resolution of SWIR. The sun direction as seen from the scene center.0 The nominal spatial resolutions of VNIR. revolution ) where. 10 1 UpperLeft double 2-10 Description The information about the scene concerning with the data granule. lat: geodetic latitude long: geodetic longitude Unit: degree . path: 1-233 (nominal) row: 1-670 view: 1-7 (-1 for offnominal pointing) The orbit number of the satellite. long) where. (az.0<az<360. when data is acquired. ‘DE’: descending direction. This denotes the coordinates of the upper-left corner of the scene. row.Table 2.3. (cycle . (path. view) where. ‘AS’: ascending direction.) revolution: 1-233 (nominal) The satellite flight direction when observation is done. The satellite recurrent cycle number and the revolution number in the cycle. cycle: 1-260 (max.

7. (lat. datetime: CCSDS A (UTC) Format b. NOTES: (*1) Object types used in Metadata are a. (lat.0 long: East longitude -180. long) where. (lat. long) where. d.0 Unit: degree This denotes the azimuth angle made by the meridian at scene center and the along-track direction. Formats of these parameters are the same as Item 10. (lat. and TIR band 11 for T alone are used. (*4) This object is copied from the value denoted in the schedule information that AOS provided.0<lat<90.0<long<180. rotating from North toward East. string (*2) Object whose name followed by (n) has “class” attribute. integer c.Table 2. SWIR band 4 for S+T.3. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character).1 This denotes the coordinates of the lower-right corner of the scene. (*3) Level-1 data product generation software needs GTOPO30 as the source of the ASTER Coarse DEM data.1 Longitude and latitude of the scene center. 180.7. within the range [0. Formats of these parameters are the same as Item 10. respectively (Unit: degree). lat: geodetic latitude -90. Formats of these parameters are the same as Item 10. It may repeat n-times. 10 7 Description This denotes the coordinates of the upper-right corner of the scene.1 This denotes the coordinates of the lower-left corner of the scene.0.0] of the scene VNIR band 2 for a set of sensors V+S+T. 2-11 .7. long) where.1-2 List of Object in ASTER Generic Metadata (5/5) 2 Group/Object Name UpperRight type*1 double 3 LowerLeft double 4 LowerRight double 8 SceneCenter double 9 SceneOrientationAngle double No. long) where.

3. e. ’ASTER_SWIR’. ‘ASTER_TIR’) 2-12 . string (*2) This item ‘SensorShortName’ contains all available sensor short names.3. The ID of ASTER GDS browse granule generated using this Level 1A data product.g. 1 Object Name SensorShortName type*1 string 2 IDofASTERGDSDataBrowse string Description The redundant array of short name for all sensors using in generating the product*2: ‘ASTER_VNIR’. Table 2. ‘ASTER_TIR’) for S+T: (‘ASTER_SWIR’. ‘ASTER_SWIR’.1. for a set of sensors V+S+T: (‘ASTER_VNIR’. d. GDS Generic Metadata attributes are written to the HDF file named attribute “productmetadata. The attributes included in GDS Generic Metadata are the specific attributes. i.3. for ASTER GDS products. datetime: CCSDS A (UTC) Format b. ’ASTER_TIR’. integer c. not associated with DID311 nor the ASTER Parameters.2. NOTES: (*1) Object types used in Metadata are a. ’ASTER_STEREO’. GDS Generic Metadata contains the generic header specified by GDS..1-3 List of Object in GDS Generic Metadata No.1-3.e.3 GDS Generic Metadata (1) Indexes of Objects The Object list of GDS Generic Metadata is shown in Table 2. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character).1”.

3.4 Product Specific Metadata(VNIR) (1) Indexes of Objects The Object list of Product Specific Metadata(VNIR) is shown in Table 2. 1 Group/Object Name VNIRBand1Data 1 2 ExtractionfromL01 2-13 . Product Specific Metadata(VNIR) attributes are written to the HDF file attribute named “productmetadata.v”. Product Specific Metadata(VNIR) includes product specific attributes.3.2. npx: Number of pixels per line (4100: fixed) nln: Number of lines in frame (4200: nominal) bpp: Bytes per pixel (1: fixed) No. (npx.e. Identifier of PDS including the first (n=1)or the last (n=2) scan. (In Table 2. RSC is scan count in each PDS. 1 ExtractionfromL01Contain er(n)*2 RSC1(n)*2 integer 2 SST1(n)*2 datetime 3 PDSid1(n)*2 string ImageDataInformation1 integer RSC (relative scan count) of the first (n=1) or the last (n=2) scan ( ≥ 0). The information about the extraction from Level-0 Group-1 PDSs (PDSs contains VNIR band 1 and band 2 strip data) in order to make VNIR Band 1 Data.1-4. A group contains a set of objects that all have a similar theme.1.1-4. not associated with DID311. group names are written in Bold characters.3.) Table 2. i. nln.1-4 List of Object in Level 1A Product Specific Metadata(VNIR) (1/7) type*1 Description The information about VNIR band 1 of Level-1A.3. The information of VNIR band 1 image data. bpp) where. SST (scan start time) of the first (n=1) or the last (n=2) scan.

(410: nominal) The information of VNIR Band-1 radiometric correction table (stored in VNIR Band-1 Swath). nmp: number of missing pixels. nlpat: number of lattice points in along-track direction. This group denotes the information about destripe parameters for Band 1 image data. (11: nominal) dlpat: distance between two neighbor lattice points in along-track direction. . ndct: number of detectors used. (nmp.3. ndd: number of damaged detectors.Table 2. dlpct) where. dlpat. (nlpat. npara) where. This group contains the coefficients used for radiance conversion. The information about bad pixels. 1 3 1 6 NumberofBadPixels1 integer UnitConversionCoeff1 1 2 3 7 Incl1 Offset1 ConUnit1 double double string DestripeParameter1 1 NumberofParameters1 integer 2-14 Description The information of VNIR Band-1 Swath geolocation field. (12: nominal) nlpct: number of lattice points in cross-track direction. nlpct. nelm: number of elements of the list of bad pixels*3. (400: nominal) dlpct: distance between two neighbor lattice points in cross-track direction. (ndct. Inclination Value Offset Value Converted Unit ‘W/m2/sr/µm’ fixed. from the pixel value of the band-1 image. nelm) where. ndd.1-4 List of Object in Level 1A Product Specific Metadata(VNIR) (2/7) Group/Object Name GeometricCorrection1 type*1 integer 4 RadiometricCorrection1 integer 5 DataQuality1 No. (4100: fixed) npara: number of parameters (3: fixed) This group contains the information about the quality of Level 1A VNIR Band-1 data. Total number of destripe parameters.

. (nlpat.DPn) n= Number of Parameters1 For next VNIRBand2Data..2). (12: nominal) nlpct: number of lattice points in cross-track direction.Table 2. 1 7 2 2 ~ 2. (410: nominal) 2-15 . VNIRBand3NData The information about VNIR band 3N of Level-1A. SST3N(n)*2 datetime SST (scan start time) of the first (n=1) or the last (n=2) scan. (npx. (400: nominal) dlpct: distance between two neighbor lattice points in cross-track direction. ExtractionfromL03N The information about the extraction from Level-0 Group-2 PDSs (PDSs contains VNIR band 3N and band 3B strip data) in order to make VNIR Band 3N Data. nlpct. ImageDataInformation3N integer The information of VNIR Band 3N image data.2 3 1 1 2 3 2 3 Group/Object Name ListofParameters1 type*1 string*4 Description Destripe Parameters (DP1. (11: nominal) dlpat: distance between two neighbor lattice points in along-track direction. DP2. nlpat: number of lattice points in along-track direction.1-4 List of Object in Level 1A Product Specific Metadata(VNIR) (3/7) No.7. nln... DP3. PDSid3N(n)*2 string Identifier of PDS including the first (n=1) or the last (n=2) scan.. dlpat. ExtractionfromL03NConta iner(n)*2 RSC3N(n)*2 integer RSC (relative scan count) of the first (n=1) or the last (n=2) scan (≥ 0). RSC is scan count in each PDS.3.7. dlpct) where. repeat the above items (1 through 1. npx: Number of pixels per line (4100: fixed) nln: Number of lines in frame (4200: nominal) bpp: Bytes per pixel (1: fixed) GeometricCorrection3N integer The information of VNIR Band-3N Swath geolocation field. bpp) where..

nelm: number of elements of the list of bad pixels*3. ndct: number of detectors used. RSC (relative scan count) of the first (n=1) or the last (n=2) scan (≥ 0).. ndd. Total number of destripe parameters.Table 2. This group contains the coefficients used for radiance conversion. (4100: fixed) npara: number of parameters (3: fixed) This group contains the information about the quality of Level 1A VNIR Band-3N data. The information of missing data.DPn) n= Number of Parameters3N The information about VNIR band 3B of Level-1A. The information about the extraction from Level-0 Group-2 PDSs (PDSs contains VNIR band 3N and band 3B strip data) in order to make VNIR Band 3B Data. (ndct. DP3. DP2... RSC is scan count in each PDS.1-4 List of Object in Level 1A Product Specific Metadata(VNIR) (4/7) No. SST (scan start time) of the first (n=1) or the last (n=2) scan. Destripe Parameters (DP1. This group denotes the information about destripe parameters for Band 3N image data. npara) where.. ndd: number of damaged detectors.3. 3 4 Group/Object Name RadiometricCorrection3N 5 type*1 integer DataQuality3N 1 6 NumberofBadPixels3N integer UnitConversionCoeff3N 1 2 3 7 Incl3N Offset3N ConUnit3N double double string DestripeParameter3N 1 2 4 NumberofParameters3N ListofParameters3N integer string*4 VNIRBand3BData 1 ExtractionfromL03B 1 ExtractionfromL03BConta iner(n)*2 RSC3B(n)*2 integer 2 SST3B(n)*2 datetime 2-16 Description The information of VNIR Band-3N radiometric correction table (stored in VNIR Band 3N Swath). . nelm) where. Inclination Value Offset Value Converted Unit ‘W/m2/sr/µm’ fixed.. nmp: number of missing pixels.. (nmp. from the pixel value of the band-3N image.

(11: nominal) dlpat: distance between two neighbor lattice points in along-track direction.3. bpp) where. ndd: number of damaged detectors. nmp: number of missing pixels. (nlpat. (500: nominal) The information of VNIR Band-3B radiometric correction table (stored in VNIR band 3B Swath).Table 2. (400: nominal) dlpct: distance between two neighbor lattice points in cross-track direction.1-4 List of Object in Level 1A Product Specific Metadata(VNIR) (5/7) Group/Object Name PDSid3B(n)*2 type*1 string 2 ImageDataInformation3B integer 3 GeometricCorrection3B integer 4 RadiometricCorrection3B integer 5 DataQuality3B No. 4 1 3 1 NumberofBadPixels3B integer 2-17 Description Identifier of PDS including the first (n=1) or the last (n=2) scan. (npx. nln. (ndct. npara) where. nlpat: number of lattice points in along-track direction. (nmp. dlpct) where. (5000: fixed) npara: number of parameters (3: fixed) This group contains the information about the quality of Level 1A VNIR Band-3B data. ndct: number of detectors used. ndd. npx: Number of pixels per line (5000: fixed) nln: Number of lines in frame (5400: nominal) bpp: Bytes per pixel (1: fixed) The information of VNIR Band-3B Swath geolocation field. nelm: number of elements of the list of bad pixels*3. nlpct. nelm) where. (15: nominal) nlpct: number of lattice points in cross-track direction. The information of VNIR Band 3B image data. dlpat. . The information about bad pixels.

Last packet time for this PDS.. (Sc. This group identifies the address of the first available pixel in each refreshing cycle of VNIR band-3B image data. DP3.. DP2.. The information about PDSs of Level-0 Group-1. First packet time for this PDS. Total number of destripe parameters. The identifier of the input data type (defined by EDOS). Number of packets in this PDS. ‘PDS’: Production Data Set ‘EDS’: Expedited Data Set ‘DDS’: Direct down-link Data Set ‘TEST’: Test Data . Inclination Value Offset Value Converted Unit ‘W/m2/sr/µm’ fixed. (nominal = 10) This identifies the address of the first available pixel in each refreshing cycle of VNIR band-3B image data..1-4 List of Object in Level 1A Product Specific Metadata(VNIR) (6/7) No.3.. Number of refreshing cycle.Table 2. Ad) where. Identifier of this PDS assigned by EDOS. This group contains the information of L0 Group-1 data set (PDSs). from the pixel value of the band-3B image. 4 6 1 2 3 7 Group/Object Name UnitConversionCoeff3B type*1 Incl3B Offset3B ConUnit3B double double string FirstPixelAddressGroup 1 Ncycles 2 FPAddress FPAddressContainer(n)*2 1 FirstPixelAddress(n)*2 8 integer integer DestripeParameter3B 1 2 5 NumberofParameters3B ListofParameters3B integer string*4 Level0VNIRG1Data 1 L0DataSetG1 L0DataSetG1Container(n) *2 2 1 PDSidG1(n)*2 string 2 3 4 FirstPacketTimeG1(n)*2 LastPacketTimeG1(n)*2 PacketCountsG1(n)*2 L0DataTypeG1 datetime datetime integer string 2-18 Description This group contains the coefficients used for radiance conversion..DPn) n= Number of Parameters3B The information about Level-0 Group-1 which contains VNIR band 1 and 2 data. Sc: Relative scan count Ad: Address This group denotes the information about destripe parameters for Band 3B image data. Destripe Parameters (DP1.

Table 2.3.1-4 List of Object in Level 1A Product Specific Metadata(VNIR) (7/7)
Group/Object Name
L0DataQualityG1

type*1

1

SensorGroupNameG1

string

2

NumberofPacketsG1

integer

3

PercentofMissingPacketsG
1

double

4

PercentofCorrectedPackets
G1

double

No.
5 3

6

Level0VNIRG2Data

1

L0DataSetG2
L0DataSetG2Container(n)
*2

1

PDSidG2(n)*2

string

2
3
4
2

FirstPacketTimeG2(n)*2
LastPacketTimeG2(n)*2
PacketCountsG2(n)*2
L0DataTypeG2

datetime
datetime
integer
string

3

L0DataQualityG2

1

SensorGroupNameG2

string

2

NumberofPacketsG2

integer

3

PercentofMissingPacketsG
2

double

4

PercentofCorrectedPackets
G2

double

Description
This specifies the number of input
packets used to generate the data
granule, and their quality.
Sensor group name:
‘VNIR1’ (fixed)
Number of packets used to generate the
scene data of each group.
The percentage of missing packets of
each group.
Unit: %
The percentage of packets with errors
corrected by Reed Solomon (R-S)
decoding.
Unit: %
The information about
Level-0 Group-2 which contains VNIR
band 3N and 3B data.
This group contains the information of
L0 Group-2 data set (PDSs).
The information about PDSs of Level-0
Group-2.
Identifier of this PDS assigned by
EDOS.
First packet time for this PDS.
Last packet time for this PDS.
Number of packets in this PDS.
The identifier of the input data type
(defined by EDOS).
‘PDS’: Production Data Set
‘EDS’: Expedited Data Set
‘DDS’: Direct down-link
Data Set
‘TEST’: Test Data
This specifies the number of input
packets used to generate the data
granule, and their quality.
Sensor group name:
‘VNIR2’ (fixed)
Number of packets used to generate the
scene data of each group.
The percentage of missing packets of
each group.
Unit: %
The percentage of packets with errors
corrected by Reed Solomon (R-S)
decoding.
Unit: %

NOTES:
(*1) Object types used in Metadata are
a. datetime: CCSDS A (UTC) Format
b. integer
c. double: the floating point value is rounded to the appropriate number
(6 digits after the decimal-point character).
d. string
2-19

(*2) Object whose name followed by (n) has “class” attribute. It may repeat n-times.
(*3) The information concerning the list of bad pixels apart from this attribute and is written
to the separated attribute named “badpixelinformation”. Refer to the section 2.3.1.7,
titled Bad Pixel Information.
(*4) SCF Toolkit does not support exponential numbers correspond to the Third Numerical
Representation (NR3) in ISO 6093, then this should be expressed as a quoted strings.
Each number is represented by two sequences of decimal digits called the significant
(i.e., mantissa) and exponent, separated by the ASCII character E (e.g. Value=(“+1.23E-1”,
“-4.99E+2”)).

2-20

2.3.1.5 Product Specific Metadata(SWIR)
(1) Indexes of Objects
The Object list of Product Specific Metadata(SWIR) is shown in Table 2.3.1-5. Product Specific
Metadata(SWIR) attributes are written to the HDF file attribute named “productmetadata.s”.
Product Specific Metadata(SWIR) includes product specific attributes, i.e. not associated with
DID311.
(In Table 2.3.1-5, group names are written in Bold characters. A group contains a set of objects that
all have a similar theme.)

Table 2.3.1-5 List of Object in Level 1A Product Specific Metadata(SWIR) (1/4)
type*1

Description
The information about SWIR
band 4 of Level-1A.
The information about the
extraction from Level-0
Group-3 PDSs (PDSs contains
SWIR strip data) in order to
make SWIR band 4 data.

1

ExtractionfromL04Container(
n)*2
RSC4(n)*2

integer

2

SST4(n)*2

datetime

3

PDSid4(n)*2

string

ImageDataInformation4

integer

RSC (relative scan count) of
the first (n=1) or the last (n=2)
scan (>0). RSC is scan count
in each PDS.
SST (scan start time) of the
first (n=1) or the last (n=2)
scan.
Identifier of PDS including the
first (n=1) or the last (n=2)
scan.
The information of SWIR
band 4 image data.
(npx, nln, bpp)
where,
npx: Number of pixels per
line (2048: fixed)
nln: Number of lines in
frame (2100: nominal)
bpp: Bytes per pixel
(1: fixed)

No.
1

Group/Object Name
SWIRBand4Data

1

2

ExtractionfromL04

2-21

ndct: number of detectors used. (20: nominal) dlpct: distance between two neighbor lattice points in cross-track direction. (ndct. (104: nominal) dlpat: distance between two neighbor lattice points in along-track direction.3. The information about bad pixels. (2048: fixed) npara: number of parameters (3: fixed) This group contains the information about the quality of Level 1A SWIR Band-4 data. dlpct) where. (20: nominal) The information of SWIR Band4 radiometric correction table (stored in SWIR band 4 Swath). from the pixel value of the band-4 image. (nmp. This group denotes the information about destripe parameters for Band 4 image data. nmp: number of missing pixels. ndd. nlpat: number of lattice points in along-track direction. Total number of destripe parameters. nelm: number of elements of the list of bad pixels*3. dlpat. Inclination Value Offset Value Converted Unit ‘W/m2 /sr/µm’ fixed. nlpct. (106: nominal) nlpct: number of lattice points in cross-track direction.Table 2. This group contains the coefficients used for radiance conversion. . npara) where. ndd: number of damaged detectors. nelm) where.1-5 List of Object in Level 1A Product Specific Metadata(SWIR) (2/4) Group/Object Name GeometricCorrection4 type*1 integer 4 RadiometricCorrection4 integer 5 DataQuality4 No. (nlpat. 1 3 1 6 NumberofBadPixels4 integer UnitConversionCoeff4 1 2 3 7 Incl4 Offset4 ConUnit4 double double string DestripeParameter4 1 NumberofParameters4 integer 2-22 Description The information of SWIR Band4 Swath geolocation field.

‘PDS’: Production Data Set ‘EDS’: Expedited Data Set ‘DDS’: Direct down-link Data Set ‘TEST’: Test Data L0DataQuality This specifies the number of input packets used to generate the data granule.2 5 ~ 5.2).. repeat the above items (1 through 1. For next SWIRBand7Data.2 6 ~ 6.2). DP3.7.7. repeat the above items (1 through 1. repeat the above items (1 through 1.2). Unit: % SWIRRegistrationQuality The registration information of SWIR based on VNIR.. For next SWIRBand6Data.7.7.7. *2 PacketCounts(n) integer Number of packets in this PDS. repeat the above items (1 through 1.7.. PDSid(n)*2 string Identifier of this PDS assigned by EDOS..1-5 List of Object in Level 1A Product Specific Metadata(SWIR) (3/4) No.. L0DataSetContainer(n)*2 The information about PDSs of Level-0 Group-3.7. 2-23 .2).3. repeat the above items (1 through 1. Unit: % PercentofCorrectedPackets double The percentage of packets with errors corrected by Reed Solomon (R-S) decoding. and their quality. DP2. Level0SWIRData The information about Level-0 Group-3 which contains SWIR data.7. FirstPacketTime(n)*2 datetime First packet time for this PDS.DPn) n= Number of Parameters4 For next SWIRBand5Data.2 7 1 1 2 3 4 2 3 1 2 3 4 8 type*1 string*4 Group/Object Name ListofParameters4 Description Destripe Parameters (DP1. L0DataType string The identifier of the input data type (defined by EDOS)..Table 2. LastPacketTime(n)*2 datetime Last packet time for this PDS. PercentofMissingPackets double The percentage of missing packets of each group.7. 1 7 2 2 ~ 2. For next SWIRBand8Data.7.2).2 4 ~ 4. For next SWIRBand9Data. L0DataSet This group contains the information of L0 SWIR data set (PDSs).2 3 ~ 3. SensorGroupName string Sensor group name : ‘SWIR’ (fixed) NumberofPackets integer Number of packets used to generate the scene data of each group.

.1 ProcessingFlag integer 2-24 0: no output. 2: output is extracted from registration file. 1: output is the result computed. because processing is impossible. 4: output obtained by other method.

then this should be expressed as a quoted strings. Unit: % The Average Correlation Coefficient. The percentage of image matching used in the SWIR parallax correction processing. datetime: CCSDS A (UTC) Format b. titled Bad Pixel Information. PAOset) where. NOTES: (*1) Object types used in Metadata are a. VOThld: Vector offset threshold The information of SWIR parallax correction. Standard deviation offset value. 8 2 3 9 ParallaxCorrectionQuality 1 PctImageMatch integer 2 AvgCorrelCoef double 3 Cthld double Description The number of measurements The number of measurement points. PAOset: average offset in cross track direction. (LSDOset. (*3) The information concerning the list of bad pixels apart from this attribute and is written to the separated attribute named “badpixelinformation”. LSDOset: SD offset in along track direction.7.3. POThld. Threshold value.Table 2. Average offset value. The Correlation Threshold value. POThld: offset threshold in cross track direction. PSDOset: SD offset in cross track direction. VOThld) where. string (*2) Object whose name followed by (n) has “class” attribute. integer c. (*4) SCF Toolkit does not support exponential numbers correspond to the Third Numerical Representation (NR3) in ISO 6093. CThld: Correction threshold LOThld: offset threshold in along track direction.3. (LAOset. LAOset: average offset in along track direction. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character). LOThld. It may repeat n-times. Each number is represented by two sequences of decimal digits called the significant 2-25 . Refer to the section 2. d. PSDOset) where.1-5 List of Object in Level 1A Product Specific Metadata(SWIR) (4/4) Group/Object Name NumberofMeasurements MeasurementPointNumber type*1 integer integer 4 AverageOffset double 5 StandardDeviationOffset double 6 Threshold double No. (CThld.1.

“-4. 2-26 . separated by the ASCII character E (e.g.99E+2”)).e.(i..23E-1”. Value=(“+1. mantissa) and exponent.

1.) Table 2. not associated with DID311.e.6 Product Specific Metadata(TIR) (1) Indexes of Objects The Object list of Product Specific Metadata(TIR) is shown in Table 2. A group contains a set of objects that all have a similar theme.3. SST (scan start time) of the first (n=1) or the last (n=2) scan. npx: number of pixels per line (700: fixed) nln: number of line in frame (700: nominal) bpp: bytes per pixel (2: fixed) No. Product Specific Metadata(TIR) includes product specific attributes.3. The information of TIR band 10 image data.3. i. The information about the extraction from Level-0 Group-4 PDSs (PDSs contains TIR strip data) in order to make TIR Band 10 data. (npx.1-6. (In Table 2. nln.3.1-6.2.1-6 List of Object in Level 1A Product Specific Metadata(TIR) (1/4) type*1 Description The information about TIR band 10 of Level-1A. 1 Group/Object Name TIRBand10Data 1 2 ExtractionfromL010 2-27 . bpp) where. Identifier of PDS including the first (n=1) or the last (n=2) scan. 1 ExtractionfromL04Container( n)*2 RSC10(n)*2 integer 2 SST10(n)*2 datetime 3 PDSid10(n)*2 string ImageDataInformation10 integer RSC (relative scan count) of the first (n=1) or the last (n=2) scan (>0). Product Specific Metadata(TIR) attributes are written to the HDF file attribute named “productmetadata. RSC is scan count in each PDS.t”. group names are written in Bold characters.

3 GeometricCorrection10 integer 2-28 The information of TIR band 10 Swath geolocation field. (nlpat. dlpat. nlpat: number of lattice points in along-track direction. nlpct. (11: nominal) dlpat: distance between two neighbor lattice points in along-track direction. (11: nominal) nlpct: number of lattice points in cross-track direction. dlpct) where. (70: nominal) . (70: nominal) dlpct: distance between two neighbor lattice points in cross-track direction.

nelm) where.2 5 ~ 5. FirstPacketTime(n)*2 datetime First packet time for this PDS. npara) where. repeat the above items (1 through 1.7. (ndct.. nelm: number of elements of the list of bad pixels*3.DPn) n= Number of Parameters10 For next TIRBand11Data.2).7.3.. repeat the above items (1 through 1. DP2. 1 4 Group/Object Name RadiometricCorrection10 5 1 6 1 2 3 7 1 2 2 ~ 2.7.Table 2. NumberofBadPixels10 integer The information about bad pixels.7.2 6 1 1 2 type*1 integer Description The information of TIR Band-10 radiometric correction table (stored in TIR band 10 Swath).7. Incl10 double Inclination Value Offset10 double Offset Value ConUnit10 string Converted Unit ‘W/m2 /sr/µm’ fixed.2).1-6 List of Object in Level 1A Product Specific Metadata(TIR) (2/4) No... repeat the above items (1 through 1. from the pixel value of the band-10 image. NumberofParameters10 integer Total number of destripe parameters.. (nmp. PDSid(n)*2 string Identifier of this PDS assigned by EDOS. L0DataSetContainer(n)*2 The information about PDSs of Level-0 Group-4 data. UnitConversionCoeff10 This group contains the coefficients used for radiance conversion.7. ndd: number of damaged detectors. repeat the above items (1 through 1. DestripeParameter10 This group denotes the information about destripe parameters for Band 10 image data. ndct: number of detectors used. For next TIRBand12Data. L0DataSet This group contains the information of L0 TIR Group-10 data set (PDSs). For next TIRBand13Data. ndd.2).2 3 ~ 3. (10: fixed) npara: number of parameters (3: fixed) DataQuality10 This group contains the information about the quality of Level 1A TIR data. ListofParameters10 string*4 Destripe Parameters (DP1. DP3..7.7.2 4 ~ 4.2). nmp: number of missing pixels. 2-29 . For next TIRBand14Data. Level0TIRData The information about Level-0 Group-4 which contains TIR data.

Number of packets in this PDS. Unit: % The percentage of packets with errors corrected by Reed Solomon (R-S) decoding. The percentage of missing packets of each group. because processing is impossible. and their quality. Sensor group name: ‘TIR’ (fixed) Number of packets used to generate the scene data of each group.Table 2. . 0: no output. The number of measurements The number of measurement points. Unit: % The registration information of TIR based on VNIR.3. (LAOset. Average offset value. LAOset: average offset in along track direction.1-6 List of Object in Level 1A Product Specific Metadata(TIR) (3/4) No. 4: output obtained by other method. PAOset) where. 1: output is the result computed. The identifier of the input data type (defined by EDOS). 2: output is extracted from registration file. 6 1 3 4 2 3 7 type*1 datetime integer string Group/Object Name LastPacketTime(n)*2 PacketCounts(n)*2 L0DataType L0DataQuality 1 SensorGroupName string 2 NumberofPackets integer 3 PercentofMissingPackets double 4 PercentofCorrectedPackets double TIRRegistrationQuality 1 ProcessingFlag integer 2 3 NumberofMeasurements MeasurementPointNumber integer integer 4 AverageOffset double 2-30 Description Last packet time for this PDS. ‘PDS’: Production Data Set ‘EDS’: Expedited Data Set ‘DDS’: Direct down-link Data Set ‘TEST’: Test Data This specifies the number of input packets used to generate the data granule. PAOset: average offset in cross track direction.

ctmn3) ChopperTempStd(n) *2 double Standard deviation value for each of three temperature group.Table 2. BlackBodyMean10(n)*2 double Black body image data mean value for each TIR Band 10’s detector. (ctmn1. mn2. POThld. PSDOset: Pixel direction SD offset in cross track direction. Information of TIR Band 10. CThld: Correction threshold LOThld: offset threshold in along track direction POThld: offset threshold in cross track direction VOThld: Vector offset threshold TIRSTCInfo*5 This denotes the Short-Term Calibration (STC) Information of TIR data. (bbtm1. ~ . BlackBodyInfo(n)*2 The Black Body Temperature information. ~ . (ctsd1. ~ .1-6 List of Object in Level 1A Product Specific Metadata(TIR) (4/4) No. BlackBodyTempMean(n) *2 double Mean value for each of five temperature group.mn 10 ) BlackBodyStd10(n)*2 double Black body image data standard deviation value for each TIR Band 10’s detector. ~ .sd10 ) For ShortTermCalInfo11~ShortTermCalInfo14 repeat the above items. LOThld. ctmn2 . bbtsd2. LSDOset: Line direction SD offset in along track direction. sd2. VOThld) where.bbtsd5 ) ChopperInfo(n) *2 The Chopper Temperatuer information. (LSDOset. 7 5 type*1 double Group/Object Name StandardDeviationOffset 6 8 1 1 2 2 ~ 5. (sd1. ctsd2 . bbtm2 . (CThld. (mn1. ChopperTempMean(n) *2 double Mean value for each of three temperature group.2 6 1 2 7 1 2 Description Standard deviation offset value. ctsd3) NOTES: 2-31 .3. TIRSTCInfoContainer(n)*2 n = 1: pre-STC n = 2: post-STC ShortTermCalInfo10(n)*2 The Short-Term Cal. PSDOset) where.bbtm5) BlackBodyTempStd(n) *2 double Standard deviation value for each of five temperature group. Threshold double Threshold value. (bbtsd1.

1. “-4.99E+2”)). mantissa) and exponent.g. (*3) The information concerning the list of bad pixels apart from this attribute and is written to the separated attribute named “badpixelinformation”..1.1 through 8.2 do NOT exist for the data type of the source data product that stores ‘EDS’ (Refer to the item 8 in the table 2. Each number is represented by two sequences of decimal digits called the significant (i. (*4) SCF Toolkit does not support exponential numbers correspond to the Third Numerical Representation (NR3) in ISO 6093.7.23E-1”. datetime: CCSDS A (UTC) Format b. titled Bad Pixel Information.e.7. Value=(“+1. Refer to the section 2. 2-32 .3. integer c. separated by the ASCII character E (e.3.(*1) Object types used in Metadata are a. d. then this should be expressed as a quoted strings.1-2). double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character). string (*2) Object whose name followed by (n) has “class” attribute. (*5) Item 8. It may repeat n-times.

3). The number of elements of the list of bad pixels This group contains the list of bad pixels. Bad Pixel Information includes product specific attributes.2.3). CauseofBadPixel1(n)*2 string The cause of bad data: ‘M’: Data missing*3 ‘D’: Damaged Detector For next Band2Information.3.3.1. For next Band6Information. For next Band4Information.2.2.) Bad Pixel information is set for every band individually. LPNo: The line number in cross-track segment (or the pixel number in along-track segment) including BPS.1-7 List of Object in Bad Pixel Information (1/2) Group/Object Name Band1Information type*1 1 NumberofElement1 integer 2 ListofBadPixels1 ListofBadPixels1Contain er(n) No. For next Band3BInformation. repeat the above items (1 through 1. Bad Pixel Information attributes are written to the HDF file attribute named “badpixelinformation”.3 2-33 . FPL.3).3 6 ~ 6. ‘C’ = cross-track ‘A’ = along-track BadPixelSegments1(n)*2 integer Location information for each bad pixel element.2. repeat the above items (1 through 1. (LPNo.3.2.2.3).2.2.2.2. For next Band8Information. LPL) where.2. repeat the above items (1 through 1. repeat the above items (1 through 1.7 Bad Pixel Information (1) Indexes of Objects The Object list of Bad Pixel Information is shown in Table 2. When the band image has no bad pixel. For next Band3NInformation.3.3 10 ~ 10. this specific attribute will not appear in the HDF-EOS attribute.2. For next Band9Information. A group contains a set of objects that all have a similar theme. repeat the above items (1 through 1.3). For next Band5Information.2. not associated with DID311. So. repeat the above items (1 through 1. i.e.3). Table 2.2. the corresponding bad pixel information is not set in this attribute.3 3 ~ 3.2.2.3). repeat the above items (1 through 1. LPL: Last pixel (or line) number of BPS.3). *2 1 DirectionofBadPixel1(n)* string The direction of bad pixel segment. and the mandatory attributes for their objects are flagged as “FALSE”.1-7.3 4 ~ 4.1-7.3 7 ~ 7.3 8 ~ 8. in case that all bands have no bad pixel.2. repeat the above items (1 through 1.2. 2 2 3 2 ~ 2. (In Table 2. FPL: First pixel (or line) number of BPS. group names are written in Bold characters.3).2. repeat the above items (1 through 1. 1 Description This group contains the information about the bad pixels with respect to the Level 1A VNIR Band-1 image. For next Band7Information.3 5 ~ 5.3 9 ~ 9.

d.3 13 ~ 13.2.2.2.3 Group/Object Name type*1 Description For next Band10Information.3).2.1-7 List of Object in Bad Pixel Information (2/2) No.Table 2.2. 11 ~ 11. ‘Me’ for even pixel and ‘Mo’ for odd pixel.3.2.2.3). datetime: CCSDS A (UTC) Format b. NOTES: (*1) Object types used in Metadata are a. repeat the above items (1 through 1. repeat the above items (1 through 1.3).3 14 ~ 14. repeat the above items (1 through 1. For next Band12Information. repeat the above items (1 through 1. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character).2. string (*2) Object whose name followed by (n) has “class” attribute.3 15 ~ 15. For next Band13Information. It may repeat n-times. For next Band14Information. repeat the above items (1 through 1.3).2. (*3) Just in case of SWIR.3 12 ~ 12.2. 2-34 . integer c.3). For next Band11Information.

2-35 .This page intentionally left blank.

the lattice coordinates of SWIR Geometric Correction Table (GCT) is used as center of evaluation rectangle. c) If both SWIR and VNIR data are not available. Table 2. a) In nominal case.2-1 d) Contents: each element is 1 byte data. Reference Coordinate Evaluation area size SWIR 20L*20P 2-36 VNIR 41L*41P TIR 6L*6P .2. (*2) Cloud coverage table is entered in the order with [line][pixel]. SensorShortName contains only “ASTER_TIR” and ASTERObservationMode identifies VST or ST mode). (e.3.3. titled Strip Observation Mode. b) If SWIR data is not available. the reference coordinate for the cloud coverage table will be ‘SWIR’ (not ‘TIR’). See the section 1.2 Cloud Coverage Table (1) Description Cloud coverage table is available for Level 1A Product corresponding to each ASTER Observation (OBS) modes. the lattice coordinate of TIR GCT will be used.. indicates clear (= 0) or cloudy (= 1) for the rectangular area (the definition of those area is shown in Note 1 and Note 2 below).g.. (2) Characteristics a) Data model: SDS (2 Dimensional Array) b) Object Name: Cloud_Coverage_Table c) Format: Refer to Table 2.2-1 Size of Cloud Coverage Data Reference Coordinates SWIR*1 VNIR TIR Dimension Size [n][104] *2 [n][100] *2 [n][117] *2 Variable Type UINT8 UINT8 UINT8 (*1) In case that the strip observation mode is “VST+T” or “ST+T” and only TIR data is included in the product(i. Note 2: Evaluation area size is shown as follows.3. n: nominal value 106 in case of SWIR) Note 1: Reference Coordinates will change depending on condition of observation.5. Line size is depending on a processing scene. the lattice coordinate of VNIR GCT will be used as center instead.e.

3-1 Format of Ancillary Data (1/2) Field Name Time_Tag Primary_Header Order 4 6 Variable Size UINT16 UINT8 Secondary_Header 8 UINT8 Flag_Byte 1 UINT8 Time_Conversion 3 INT8 Position 3 INT32 Velocity 3 INT32 Attitude_Angle 3 INT16 Description Time Tag (UTC): Spacecraft Time Format CCSDS Primary Packet Header for downlink. Attitude Angle (Roll. (2) Characteristics Ancillary Data Group contains a series of Ancillary Data Records through the use of Vgroup API. This may be added to the Spacecraft Clock time to derive UTC time. a) Data model: Vdata b) Object Name: Ancillary_Data c) Class Name: Anci_Record.024 sec). This field is part of the secondary header of the packet for downlink.3. Spacecraft clock time in CCSDS Day-Segmented Format. Other bits are reserved and will contain data zero. The code epoch is January 1. an extra number of ancillary data will be extracted and provided. Spacecraft Position (x. Flag Byte -. expressed in Earth Centered Inertial frame (mean Equator and Equinox of J2000). To ensure the conformity with instrument data. Time Conversion -. 2-37 .3-1 shows the format and the contents of Ancillary Data. Bit 0: Secondary Header ID Flag (always a data zero) Bit 1-63: Time Stamp -. used for ground routing and processing. 1958.Estimated difference between UTC and the Spacecraft Clock. z) -. in order to match with the scene observation time. z) -. vgroup name: Ancillary_Data class: Ancillary Each record of Ancillary Data has following characteristics. Yaw) -. Since ancillary data appended to onboard instrument data are updated once per major cycle time (1. and called Time Tag.3.12 ~ 31 records) d) Format and contents: Table 2. y.3.3.n (n: Record count number -. Spacecraft Velocity (x. expressed in the Orbital Reference frame. This field is part of the secondary header of the packet for downlink. Some Ancillary Data contains multiple entries per field.Estimated position of the spacecraft.Estimated velocity of the spacecraft.2.The estimated attitude of the spacecraft.3 Ancillary Data (1) Description Ancillary Data includes the satellite's orbit/attitude data. Order that is the number of components in a field is also shown in Table 2.Flags for ground data processing control. First (most significant) bit is the "quick look" bit. This is used as control data for extracted Image Data.Epoch of the data in the ancillary data message. y. Table 2. and their time tags. the time data which represents the ancillary data updating time(UTC) is assigned to the leading ancillary data. expressed in Earth Centered Inertial frame (mean Equator and Equinox of J2000). Pitch.3-1.

expressed in the Orbital Reference frame.Attitude_Rate 3 INT16 Attitude Rate (Roll.The estimated attitude rate of the spacecraft. Pitch. 2-38 . Yaw) -.

z) -. y. z) -.Currents flowing in each of the magnetic torque coils used for Spacecraft momentum unloading.Components of unit vector. y. Solar Array Current -.125 m Spacecraft Velocity Attitude Angle Attitude Rate Magnetic Coil Current 244*10-6 m/s 1.0 A 7.Table 2.0 arcsec 0. Note 1: Resolution and Range are shown as follows. y. Moon Position (x.0 A Solar Array Current Solar Position Moon Position 1. Solar Position (x. Ancillary Data Primary Header Secondary Header Time Stamp Flag Byte Time Conversion Resolution N/A N/A 1µsec N/A 1µsec Spacecraft Position 0.8*10-3 +1 +1 2-39 Range N/A N/A 1958-2047 N/A +8. z) -. expressed in the Spacecraft Reference frame.3*106µsec +268*106 m 0-256 A . pointing in the direction of the Moon.3.5 arcsec/sec 15. expressed in the Spacecraft Reference frame.3-1 Format of Ancillary Data (2/2) Field Name Magnetic_Coil Order 3 Variable Size INT8 Solar_Array 1 UINT8 Solar_Position 3 INT8 Moon_Position 3 INT8 Description Magnetic Coil Current (x.8*10-3 7.6*10-3 A +524*103 m/s +2048 arcsec +1024 arcsec/sec +2. pointing in the direction of the Sun.Current flowing from the Spacecraft solar array.Components of the unit vector.

3. We require that every swath contain some geolocation component. The data itself is stored in multidimensional arrays in the swath.3.3. In a swath. g on Al Scan Lines Figure 2. Vgroup name that establishes access to a Vgroup is as follows.4.2. 2D Data Array Satellite 00 42 4100 3 3D Data Array bl Ta 10 e 11 3 Geolocation Array Cross Track Geolocation 1 Table 1 Longitude 10 Latitude Scene Line  No. Each Band is stored as separate Swath structure.1 Overview VNIR Group contains an SDS and a series of Swath Objects through the use of the Vgroup API. geolocation information is stored as a series of arrays. a series of 2D geolocation arrays. one per geolocation object.4 VNIR Group 2.3. Consider Figure 2.2 VNIR Band 1 Swath (1) Structure A single swath contains any number of Tables and Multidimensional Arrays.4-1. vgroup name: VNIR class: 1A 2. The only limitation is that the first dimension is the Track dimension.3.4-1 Conceptual View of Example of Swath 2-40 k ac Tr . which is represent of a swath consisting of a combination of 2D and 3D data arrays. There is however one type of information that is special: geolocation information.4. and a single 1D geolocation tables. a series of data tables.

Latitude Type Geolocation Array 2. Av. line) based on image data arcsec line of sight vector (roll. AttitudeRate Data Table 10.4-2 Format of data items in VNIR Band 1 Swath Field Name Latitude Longitude SceneLineNumber LatticePoint SightVector SatellitePosition SatelliteVelocity AttitudeAngle AttitudeRate ObservationTime ImageData RadiometricCorrTable Dimension Size [n][11] [n][11] [n] [n][11][2] [n][11][3] [n][3] [n][3] [n][3] [n][3] [n][4] [4200][4100] Variable Type DOUBLE DOUBLE INT32 INT32 DOUBLE DOUBLE DOUBLE DOUBLE DOUBLE UINT16 UINT8 [4100][3] FLOAT n: revised to accommodate a processing scene (12: nominal).0.3.4-2 shows the format of them.4-1 shows the contents of Swath Object.3. yaw) N/A observation time of this lattice point (UTC) Format: Spacecraft Time Format N/A Level 1A spectral band image data N/A radiometric correction coefficients of equation: L =AV*V/GV+DV The order of the last dimension of these coefficients is (Dv. y. pitch.0) line coordinates based on the strip image pixel. SightVector 3D Data Array 6. The order of the first dimension corresponds to the detector number. Field Name 1. 180. 90.0. yaw) in orbital reference frame m satellite position vector (x.3. 2-41 Remarks geolocation field (Array) geolocation field (Array) geolocation field (Table) mapping to geolocation array mapping to geolocation array mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation array non-mapping to geolocation array . Table 2.3. ObservationTime Data Table 11. SatellitePosition SatelliteVelocity AttitudeAngle Data Table Data Table Data Table 9. Longitude Geolocation Array 3. 7. 8. Table 2.4-1 shows the List of data items in VNIR Band 1 Swath. ImageData 2D Data Array RadiometricCorrTable 2D Data Array Unit deg.(2) Characteristics Table 2. line lattice point coordinates (pixel. a) Data model: Swath b) Object Name: VNIR_Band1 c) Format: Table 2. z) at ECR m/sec satellite velocity vector (x. pitch. geocentric longitude: decimal degree on range [-180. Table 2.0] deg. y. pitch.4-1 List of data items in Level 1A VNIR Band 1 Swath No. Gv). z) at ECR arcsec satellite attitude angle (roll. 4. Comments geocentric latitude: decimal degree on range [-90.3. yaw) in orbital reference frame arcsec/sec satellite attitude angular velocity (roll. SceneLineNumber LatticePoint Geolocation Table 3D Data Array 5. 12.

(3) Block Size Block size is shown as follows. Type Geolocation Array Geolocation Table Block size 400 lines * 410 pixels 400 lines 2-42 .

3.4. a) Data model: Swath b) Object Name: VNIR_Band2 c) Format: The format of each item in Swath object is similar to the one in Table 2. (2) Characteristics The contents of VNIR Band 2 Swath are similar to the items in Table 2.3.4.4-2.2.2. 2-43 .4-1.3.3 VNIR Band 2 Swath (1) Structure Refer to the section 2.3. titled VNIR Band 1 Swath.

3. a) Data model: Swath b) Object Name: VNIR_Band3N c) Format: The format of each item in Swath object is similar to the one in Table 2.3. (2) Characteristics The contents of VNIR Band 3N Swath are similar to the items in Table 2.4.2. 2-44 .2.4.4 VNIR Band 3N Swath (1) Structure Refer to the section 2.3.4-1. titled VNIR Band 1 Swath.3.4-2.

Type Geolocation Array Geolocation Table Block size 400 lines * 500 pixels 400 lines 2-45 .3.5 VNIR Band 3B Swath (1) Structure Refer to the section 2.4-1.2.2.4-3 shows the format of one the contents of Swath Object.3.4-3 Format of data items in VNIR Band 3B Swath Field Name Latitude Longitude SceneLineNumber LatticePoint SightVector SatellitePosition SatelliteVelocity AttitudeAngle AttitudeRate ObservationTime ImageData RadiometricCorrTable Dimension Size [n][11] [n][11] [n] [n][11][2] [n][11][3] [n][3] [n][3] [n][3] [n][3] [n][4] [5400][5000] Variable Type DOUBLE DOUBLE INT32 INT32 DOUBLE DOUBLE DOUBLE DOUBLE DOUBLE UINT16 UINT8 [5000][3] FLOAT Remarks geolocation field (Array) geolocation field (Array) geolocation field (Table) mapping to geolocation array mapping to geolocation array mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation array non-mapping to geolocation array n: revised to accommodate a processing scene (15: nominal).3. Table 2.3.4.3. a) Data model: Swath b) Object Name: VNIR_Band3B c) Format: Table 2.4. (3) Block Size Block size is shown as follows. titled VNIR Band 1 Swath. (2) Characteristics The contents of VNIR Band 3B Swath are similar to the items in Table 2.

calibration data. Dimension Size Variable Type [n][58] UINT8 n: revised to accommodate a record count number. Temperature Photodiode 1 Temperature Photodiode 2A Temperature Photodiode 2B Temperature VSP 1 Temperature VSP 2 Temperature VEL Base Plate Temperature Nadir Telescope Temperature 1 Nadir Telescope Temperature 2 Nadir Telescope Temperature 3 Preamp 2 Temperature Backward Telescope Temperature 2 Backward Telescope Temperature 3 VPS Lamp Power Supply Voltage Photodiode 1A Output Photodiode 1B Output Photodiode 2A Output Photodiode 2B Output Electric Calibration Voltage.*1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Description Time Tag (UTC): Spacecraft Time Format (Time Tag is assigned to the leading supplement data to ensure the conformity with instrument data.2 Electric Calibration Voltage.1 Electric Calibration Voltage.6 VNIR Supplement Data (1) Description VNIR Supplement Data contains VNIR status data. etc.4.3.3 2-46 . (9600: nominal) Table 2.) Band 1 Detector Temperature Band 2 Detector Temperature Band 3N Detector Temperature Band 3B Detector Temperature Calibration Lamp A Temperature Calibration Lamp B Temperature Monitor Amp.4-4 shows the contents of Supplement Data with relation to each column of the last dimension.3. pointing angles.4-4 Format of VNIR Supplement Data (1/2) No.3. (2) Characteristics a) Data model: SDS (2 Dimensional Array) b) Object Name: VNIR_Supplement c) Format: Dimension size and variable type are as follows. Table 2.2.

1).0) Bit-6. Normal=(0.1).4 VSP1 APS Vol.1). Bit-4) Low=(0. Normal=(0. -10V Pointing Angle 1 Pointing Angle 2 Initial Extract Address 1 Initial Extract Address 2 Spare Spare Bit-0: OPE. The dimension is entered in C order (‘0’ origin). Normal=(0.Table 2.0) Bit-4. Bit-2) Low=(0.5: Band 2 Gain Selection (Bit-5. Optical/Electric Calibration Selection Bit-1: Band 3 A/B Selection Bit-2.0) Bit-0: Calibration Lamp A/B Selection Bit-1: PS1 On/Off Bit-2: PS3 On/Off Bit-3: Table Cancel On/Off Bit-4: PS4 On/Off Bit-5: Spare Bit-6: Spare Bit-7: Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare NOTES: (*1) ‘No.4-4 Format of VNIR Supplement Data (2/2) No.0). +10V VSP1 APS Vol.0).*1 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 Description Electric Calibration Voltage.3. Bit-6) Low=(0.0). 2-47 . High=(1.’ expresses the relative position in the last dimension.7: Band 1 Gain Selection (Bit-7. High=(1.3: Band 3 Gain Selection (Bit-3. High=(1.

parallax correction (∆lat. deg. y. SatellitePosition SatelliteVelocity AttitudeAngle Data Table Data Table Data Table 12.5-1 shows the contents of Swath Object.3. 4. titled VNIR Band 1 Swath. 11.5-2 shows the format of them. Table 2. z) at ECR m/sec satellite velocity vector (x.5 SWIR Group 2. 180. 90. Vgroup name that establishes access to a Vgroup is as follows. Latitude Type Geolocation Array 2. z) at ECR arcsec satellite attitude angle (roll. ObservationTime Data Table 14.3. SceneLineNumber LatticePoint Geolocation Table 3D Data Array 5.0.0.5. Gs). 2-48 .3. a) Data model: Swath b) Object Name: SWIR_Band4 c) Format: Table 2. ParallaxOffset Evaluation 3D Data Array 2D Data Array 9.2. pitch.3. vgroup name: SWIR class: 1A 2.3. SightVector 3D Data Array 6. Longitude Geolocation Array 3. ∆long) N/A 1: Image matching 2: using DEM m satellite position vector (x. 15. line Lattice point coordinates (pixel. IntertelescopeOffset 3D Data Array 7. AttitudeRate Data Table 13.5-1 shows the List of data items in SWIR Band 4 Swath. angular displacements of SWIR in geocentric latitude and longitude as compared to VNIR. ImageData 2D Data Array RadiometricCorrTable 2D Data Array Unit deg. Comments geocentric latitude: decimal degree on range [-90. geocentric longitude: decimal degree on range [-180. Field Name 1. yaw) N/A observation time of this lattice point Format: Spacecraft Time Format N/A Level 1A spectral band image data N/A Radiometric correction coefficients of equation: L = AS*V/GS + DS The order of the last dimension of these coefficients is (Ds.3.5. y.1 Overview SWIR Group contains an SDS and a series of Swath Objects through the use of the Vgroup API.2 SWIR Band 4 Swath (1) Structure Refer to the section 2. pitch.3. yaw) in orbital reference frame deg.3.0] deg. The order of the first dimension corresponds to the detector number. As.5-1 List of data items in Level 1A SWIR Band 4 Swath No. pitch.0) line coordinates based on the strip image pixel. Table 2. yaw) in orbital reference frame arcsec/sec satellite attitude angular velocity (roll. 10. (2) Characteristics Table 2. line) based on image data arcsec line of sight vector (roll.4. 8.2.

Type Geolocation Array Geolocation Table Block size 20 lines * 20 pixels 20 lines 2-49 .Table 2.5-2 Format of data items in SWIR Band 4 Swath Field Name Latitude Longitude SceneLineNumber LatticePoint SightVector IntertelescopeOffset ParallaxOffset Evaluation SatellitePosition SatelliteVelocity AttitudeAngle AttitudeRate ObservationTime ImageData RadiometricCorrTable Dimension Size [n][104] [n][104] [n] [n][104][2] [n][104][3] [n][104][2] [n][104][2] [n][104] [n][3] [n][3] [n][3] [n][3] [n][4] [2100][2048] Variable Type DOUBLE DOUBLE INT32 INT32 DOUBLE FLOAT FLOAT INT32 DOUBLE DOUBLE DOUBLE DOUBLE UINT16 UINT8 [2048][3] FLOAT Remarks geolocation field (Array) geolocation field (Array) geolocation field (Table) mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation array non-mapping to geolocation array n: revised to accommodate a processing scene (106: nominal). (3) Block Size Block size is shown as follows.3.

4.3 SWIR Band 5 Swath (1) Structure Refer to the section 2.5-1.3. 2-50 .2.3. titled VNIR Band 1 Swath. (2) Characteristics The contents of SWIR Band 5 Swath are similar to the items in Table 2.5-2.3. a) Data model: Swath b) Object Name: SWIR_Band5 c) Format: The format of each item in Swath object is similar to the one in Table 2.3.2.5.

3.5-2.4.5.2. a) Data model: Swath b) Object Name: SWIR_Band6 c) Format: The format of each item in Swath object is similar to the one in Table 2. titled VNIR Band 1 Swath.3. (2) Characteristics The contents of SWIR Band 6 Swath are similar to the items in Table 2.4 SWIR Band 6 Swath (1) Structure Refer to the section 2.3.2.3. 2-51 .5-1.

4.2.3.3.3.5.3.5-2. 2-52 . (2) Characteristics The contents of SWIR Band 7 Swath are similar to the items in Table 2.5-1.2.5 SWIR Band 7 Swath (1) Structure Refer to the section 2. titled VNIR Band 1 Swath. a) Data model: Swath b) Object Name: SWIR_Band7 c) Format: The format of each item in Swath object is similar to the one in Table 2.

(2) Characteristics The contents of SWIR Band 8 Swath are similar to the items in Table 2.3.5-2.6 SWIR Band 8 Swath (1) Structure Refer to the section 2. a) Data model: Swath b) Object Name: SWIR_Band8 c) Format: The format of each item in Swath object is similar to the one in Table 2.4.3. titled VNIR Band 1 Swath. 2-53 .2.3.2.5.3.5-1.

2.3.3.4.7 SWIR Band 9 Swath (1) Structure Refer to the section 2. 2-54 .5.2. a) Data model: Swath b) Object Name: SWIR_Band9 c) Format: The format of each item in Swath object is similar to the one in Table 2.3. titled VNIR Band 1 Swath.5-1.5-2. (2) Characteristics The contents of SWIR Band 9 Swath are similar to the items in Table 2.3.

8 SWIR Supplement Data (1) Description SWIR Supplement Data contains SWIR status data.5-4~8. pointing angles.7) from WORD#38 to WORD#53 in Table 2.3.5-3 Contents of SWIR Supplement Data Frame Number Contents of the Entries 0 all of synchronous code. Increment of frame number is attended on this update.5-4 shows the contents of Supplement Data with relation to each column of the last dimension.3. 1 all of synchronous code. Since SWIR Supplement Data is updated once per cycle time (4.3.1) from WORD#38 to WORD#53 in Table 2.3. 3 all of synchronous code.3.3.3. 0 & 1 (MF-0. etc. write following entries repeatedly concerning above four frames. and reserved field and Major Frame No.3. (2) Characteristics a) Data Model: SDS (2 Dimensional Array) b) Object Name: SWIR_Supplement c) Format: Dimension size and variable type are as follows. and reserved field and Major Frame No. … Table 2.5-5~8 show the contents of Supplement Data in detail. Table 2. 4 & 5 (MF-4. frame number. and reserved field and Major Frame No.5) from WORD#38 to WORD#53 in Table 2. frame number.3. calibration data. frame number. 2 all of synchronous code. (2510: nominal) Table 2.398msec).2.5-4~8.5-4 Format of SWIR Supplement Data (1/4) No. 2 & 3 (MF-2.5. Table 2.3) from WORD#38 to WORD#53 in Table 2. 6 & 7 (MF-6.*1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Description Time Tag: Spacecraft Time Format Synchronous Code (6DE2B846) Frame Number (sequential number from 0 to 224-1) 2-55 . Dimension Size Variable Type [n][49] UINT8 n: revised to accommodate a record count number. Table 2.5-3 shows the contents of each entry. and reserved field and Major Frame No.5-4~8.5-4~8.3. frame number.

*1 15 16 17 18 19 20 21 22 23 24 Description WORD#38 MF-0: Optics monitor voltage A MF-2: Optics monitor voltage A MF-4: Optics monitor voltage A MF-6: Optics monitor voltage A WORD#38 MF-1: Cooler current 3 MF-3: Cooler current 3 MF-5: Cooler current 3 MF-7: Cooler current 3 WORD#39 MF-0: Spare MF-2: Spare MF-4: Spare MF-6: Spare WORD#39 MF-1: Cooler current 4 MF-3: Cooler current 4 MF-5: Cooler current 4 MF-7: Cooler current 4 WORD#40 MF-0: Optics monitor voltage B MF-2: Optics monitor voltage B MF-4: Optics monitor voltage B MF-6: Optics monitor voltage B WORD#40 MF-1: Detector temperature (NARROW) MF-3: Detector temperature (NARROW) MF-5: Detector temperature (NARROW) MF-7: Detector temperature (NARROW) WORD#41 MF-0: Spare MF-2: Spare MF-4: Spare MF-6: Spare WORD#41 MF-1: TLM/CMD circuit reference voltage 1 MF-3: TLM/CMD circuit reference voltage 1 MF-5: TLM/CMD circuit reference voltage 1 MF-7: TLM/CMD circuit reference voltage 1 WORD#42 MF-0: Cooler current 1 MF-2: Cooler current 1 MF-4: Cooler current 1 MF-6: Cooler current 1 WORD#42 MF-1: TLM/CMD circuit reference voltage 2 MF-3: TLM/CMD circuit reference voltage 2 MF-5: TLM/CMD circuit reference voltage 2 MF-7: TLM/CMD circuit reference voltage 2 2-56 .Table 2.3.5-4 Format of SWIR Supplement Data (2/4) No.

25 WORD#43 MF-0: Cooler current 2 MF-2: Cooler current 2 MF-4: Cooler current 2 MF-6: Cooler current 2 2-57 .

5-6 MF-4: See Table 2.3.3.5-5 (MF-1.3.3.3.5-6 WORD#45 MF-1: Drive plus width MF-3: Drive plus width MF-5: Drive plus width MF-7: Drive plus width WORD#46 MF-0: A/D reference voltage (Band 4) MF-2: Detector Dewar temperature MF-4: Collector module temperature 1 MF-6: Spare WORD#46 MF-1: Calibration lamp voltage A MF-3: Barrel STR temperature MF-5: Electrical circuit temperature 1 (DRV) MF-7: Spare WORD#47 MF-0: A/D reference voltage (Band 5) MF-2: Radiator temperature (Inner) MF-4: Collector module temperature 2 MF-6: Spare WORD#47 MF-1: Calibration lamp voltage B MF-3: INE Mount temperature MF-5: Electrical circuit temperature 2 (PRO) MF-7: Spare WORD#48 MF-0: A/D reference voltage (Band 6) MF-2: Radiator temperature A MF-4: Detector preamp/dewar temperature A MF-6: Spare WORD#48 MF-1: Detector temperature (Wide) MF-3: Electrical circuit 1 temperature MF-5: Electrical circuit temperature 3A (CT) MF-7: Spare WORD#49 MF-0: A/D reference voltage (Band 7) MF-2: Cover temperature 2A (-X) MF-4: Pointing mechanism temperature MF-6: Spare 2-58 .3.3.5-6 MF-2: See Table 2.5-5 (MF-0. 5.*1 26 27 28 29 30 31 32 33 34 35 36 37 Description WORD#43 MF-1: TLM/CMD circuit reference voltage 3 MF-3: TLM/CMD circuit reference voltage 3 MF-5: TLM/CMD circuit reference voltage 3 MF-7: TLM/CMD circuit reference voltage 3 WORD#44 See Table 2. 2.5-4 Format of SWIR Supplement Data (3/4) No.Table 2. 4. 6) WORD#44 See Table 2.5-6 MF-6: See Table 2. 7) WORD#45 MF-0: See Table 2. 3.

The dimension is entered in C order (‘0’ origin).’ expresses the relative position in the last dimension.5-8 MF-6: Spare WORD#53 MF-1: See Table 2.3.5-7 MF-4: See Table 2.3.5-8 MF-4: See Table 2.3.3.5-4 Format of SWIR Supplement Data (4/4) No.3.5-7 MF-6: Spare WORD#52 MF-1: See Table 2.5-7 MF-3: See Table 2.5-8 MF-3: See Table 2.*1 38 39 40 41 42 43 44 45 46 47 48 Description WORD#49 MF-1: Motor amplitude MF-3: Electrical circuit 2 temperature MF-5: Electrical circuit temperature 4 (CAL) MF-7: Spare WORD#50 MF-0: A/D reference voltage (Band 8) MF-2: Cover temperature 1A (+X) MF-4: Cooler temperature 1A (COMP) MF-6: Spare WORD#50 MF-1: Spare MF-3: Pointing mechanism temperature 1 (MTR) MF-5: Optics monitor temperature A MF-7: Spare WORD#51 MF-0: A/D reference voltage (Band 9) MF-2: Cover temperature 3A (+Z) MF-4: Cooler temperature 2A (C-FNG) MF-6: Spare WORD#51 MF-1: Spare MF-3: Calibration lamp temperature MF-5: Optics monitor temperature B MF-7: Spare WORD#52 MF-0: Drive plus number 1 MF-2: See Table 2.3.3.Table 2.5-8 MF-5: Spare MF-7: Spare reserved reserved NOTES: (*1) ‘No.3.3. 2-59 .5-7 MF-5: Spare MF-7: Spare WORD#53 MF-0: Drive plus number 2 MF-2: See Table 2.

2.Table 2.5-5 WORD#44 Major Frame 0.3. 3. 4. 2.5-6 WORD#45 Major Frame 0. 6 1. 6 Contents Bit-0: Pointing mirror encoder 2 Bit-1: Pointing mirror encoder 2 Bit-2: Pointing mirror encoder 2 Bit-3: Pointing mirror encoder 2 Bit-4: Pointing mirror encoder 2 Bit-5: Pointing mirror encoder 2 Bit-6: Pointing mirror encoder 2 Bit-7: Pointing mirror encoder 2 Table 2.3.5-7 WORD#52 (1/2) Major Frame 1 2 Contents Bit-0: Band 4 gain status Bit-1: Band 4 gain status Bit-2: Band 5 gain status Bit-3: Band 5 gain status Bit-4: Band 6 gain status Bit-5: Band 6 gain status Bit-6: Spare Bit-7: Spare Bit-0: DIG SIG PROC PWR Bit-1: TML/CMD PWR on/off Bit-2: Analog circuit power on/off Bit-3: Spare Bit-4: Spare Bit-5: Spare Bit-6: Pointing CIR PWR Bit-7: Spare 2-60 .3. 5. 4. 7 Contents Bit-0: Pointing mirror encoder 1 Bit-1: Pointing mirror encoder 1 Bit-2: Pointing mirror encoder 1 Bit-3: Pointing mirror encoder 1 Bit-4: Pointing mirror encoder 1 Bit-5: Pointing mirror encoder 1 Bit-6: Pointing mirror encoder 1 Bit-7: Pointing mirror encoder 1 Bit-0: Pointing mirror encoder 3 Bit-1: Mirror position status Bit-2: Mirror position status Bit-3: Mirror position limit status Bit-4: Limit ENA/DISA Bit-5: Pointing motor ENA/DISA Bit-6: Encoder on/off Bit-7: Motor rotation CW/CCW Table 2.

5-7 WORD#52 (2/2) Major Frame 3 4 Contents Bit-0: THER CIR PWR Bit-1: Spare Bit-2: Spare Bit-3: Heater 3 on/off Bit-4: Heater 4 on/off Bit-5: Heater 5 on/off Bit-6: Spare Bit-7: Spare Bit-0: Party flag status Bit-1: ERR CMD DIS status Bit-2: ERR CMD DIS status Bit-3: ERR CMD DIS status Bit-4: ERR CMD DIS status Bit-5: ERR CMD DIS status Bit-6: Spare Bit-7: Spare Table 2.3.5-8 WORD#53 Major Frame 1 2 3 4 Contents Bit-0: Band 7 gain status Bit-1: Band 7 gain status Bit-2: Band 8 gain status Bit-3: Band 8 gain status Bit-4: Band 9 gain status Bit-5: Band 9 gain status Bit-6: Spare Bit-7: Spare Bit-0: Calibration lamp power on/off Bit-1: Calibration lamp A/B selection Bit-2: Spare Bit-3: Spare Bit-4: Spare Bit-5: Spare Bit-6: Spare Bit-7: Spare Bit-0: CLR motor amplitude status Bit-1: CLR motor amplitude status Bit-2: Spare Bit-3: Spare Bit-4: Detector temperature set status Bit-5: Detector temperature set status Bit-6: Spare Bit-7: Spare Bit-0: Motor position status Bit-1: Motor position status Bit-2: Spare Bit-3: Spare Bit-4: Spare Bit-5: Spare Bit-6: Spare Bit-7: Spare 2-61 .3.Table 2.

3.6-1 shows the List of data items in TIR Band 10 Swath. a) Data model: Swath b) Object Name: TIR_Band10 c) Format: Table 2. yaw) in orbital reference frame deg. line Lattice point coordinates (pixel. ImageData RadiometricCorrTable 2D Data Array 2D Data Array Unit deg.4. line) based on image data arcsec line of sight vector (roll.6 TIR Group 2. SceneLineNumber 4.3. vgroup name: TIR class: 1A 2. z) at ECR arcsec satellite attitude angle (roll. 8. LatticePoint Type Geolocation Array Geolocation Array Geolocation Table 3D Data Array 5. C2).0. pitch. 14. SightVector 3D Data Array 6.2.3.0] geocentric longitude: decimal degree on range [-180. deg.3. 90. Table 2.0) coordinates based on the strip image pixel.6-1 shows the contents of Swath Object.6. C1.3. z) at ECR m/sec satellite velocity vector (x. The order of the first dimension corresponds to the detector number.1 Overview TIR Group contains a Vgroup and a series of Swath Objects through the use of the Vgroup API.0.3. ObservationTime Data Table 12.3. Vgroup name that establishes access to a Vgroup is as follows. pitch. yaw) N/A observation time of this lattice point Format: Spacecraft Time Format pixel deviation of start position of detectors in the cross-track direction between scans N/A Level 1A spectral band image data N/A Radiometric correction coefficients of equation: L = C0 + C1 * V + C2 * V ^ 2 The order of the last dimension of these coefficients is (C0. IntertelescopeOffset 3D Data Array 7.6-2 shows the format of them.2 TIR Band 10 Swath (1) Structure Refer to the section 2. 180. Table 2. titled VNIR Band 1 Swath.2. Field Name 1. 9.3. y. Latitude 2. InterpolationParameter Data Table 13. pitch. (2) Characteristics Table 2. y.6. angular displacements of TIR in geocentric latitude and longitude as compared to VNIR. yaw) in orbital reference frame arcsec/sec satellite attitude angular velocity (roll. 2-62 . line Comments geocentric latitude: decimal degree on range [-90. m satellite position vector (x. Longitude 3. AttitudeRate Data Table 11.6-1 List of data items in Level 1A TIR Band 10 Swath No. SatellitePosition SatelliteVelocity AttitudeAngle Data Table Data Table Data Table 10.

(3) Block Size Block size is shown as follows.3. Type Geolocation Array Geolocation Table Block size 70 lines * 70 pixels 70 lines 2-63 .Table 2.6-2 Format of data items in TIR Band 10 Swath Field Name Latitude Longitude SceneLineNumber LatticePoint SightVector IntertelescopeOffset SatellitePosition SatelliteVelocity AttitudeAngle AttitudeRate ObservationTime InterpolationParameter ImageData Dimension Size [n][11] [n][11] [n] [n][11][2] [n][11][3] [n][11][2] [n][3] [n][3] [n][3] [n][3] [n][4] [n] [700][700] Variable Type DOUBLE DOUBLE INT32 INT32 DOUBLE FLOAT DOUBLE DOUBLE DOUBLE DOUBLE UINT16 DOUBLE UINT16 RadiometricCorrTable [10][3] FLOAT Remarks geolocation field (Array) geolocation field (Array) geolocation field (Table) mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation table mapping to geolocation array non-mapping to geolocation array n: revised to accommodate a processing scene (11: nominal).

6-2.4. a) Data model: Swath b) Object Name: TIR_Band11 c) Format: The format of each item in Swath object is similar to the one in Table 2.2.2. 2-64 .3. (2) Characteristics The contents of TIR Band 11 Swath are similar to the items in Table 2.6-1.3.3. titled VNIR Band 1 Swath.3.3 TIR Band 11 Swath (1) Structure Refer to the section 2.6.

3.6-1. a) Data model: Swath b) Object Name: TIR_Band12 c) Format: The format of each item in Swath object is similar to the one in Table 2.2.3.6-2.6.3. (2) Characteristics The contents of TIR Band 12 Swath are similar to the items in Table 2.4 TIR Band 12 Swath (1) Structure Refer to the section 2.3. 2-65 .2. titled VNIR Band 1 Swath.4.

5 TIR Band 13 Swath (1) Structure Refer to the section 2.2.6.6-2. (2) Characteristics The contents of TIR Band 13 Swath are similar to the items in Table 2.3.6-1. titled VNIR Band 1 Swath. 2-66 . a) Data model: Swath b) Object Name: TIR_Band13 c) Format: The format of each item in Swath object is similar to the one in Table 2.3.2.3.4.3.

6-2. (2) Characteristics The contents of TIR Band 14 Swath are similar to the items in Table 2.2.3.6 TIR Band 14 Swath (1) Structure Refer to the section 2.4. a) Data model: Swath b) Object Name: TIR_Band14 c) Format: The format of each item in Swath object is similar to the one in Table 2. titled VNIR Band 1 Swath.2.6.3. 2-67 .6-1.3.3.

2. (*2) Temperature Data consists of two samplings within the each column. vgroup name that establishes access to a Vgroup is as follows. calibration data.3. Table 2. vgroup name: TIR_Supplement class: Supplement (2) Characteristics Three categories in Vgroup object are shown as follows. etc.3.*1 0 1 2 3 4 5 6 7 8 9 10 11 12 Description Time Tag: Spacecraft Time Format Detector Temperature*2 Temperature of Black-Body*2 Temperature of Chopper*2 Temperature of Telescope*2 Temperature of Lens*2 NOTES: (*1) ‘No. Table 2. Chopper. TIR Supplement Data contains a series of SDS (Temperature. pointing angles. (71: nominal) Table 2. The dimension is entered in C order (‘0’ origin).3. Supplement Data about Temperature a) Data Object: SDS (2 Dimensional Array) b) Object Name: TIR_Supplement_Temp c) Format: Table 2. and Encoder) through the use of the Vgroup API.6-4 Format of TIR Supplement Data (Temperature) No.6-4 shows the contents of Supplement Data about temperatures with relation to each column of the last dimension.3.’ expresses the relative position in the last dimension.3.6-3 shows the dimension size and variable type.7 TIR Supplement Data (1) Description TIR Supplement Data contains TIR status data.6. Each column is segmented as follows: Segment Width (bits) Temperature 12 Spare 2-68 4 Temperature Spare 12 4 .6-3 Dimension Size & Variable Type of TIR Supplement Data (Temperature) Dimension Size Variable Type [n][13] UINT32 n: revised to accommodate a record count number.

3. (71: nominal) NOTES: (*1) Chopper image is stored as ‘record * sampling * detector * component’. (71: nominal) 2-69 .6-5 shows the format and contents of Supplement Data about chopper images.6-6 shows the format and contents of Supplement Data about encoder data.3.Supplement Data about Chopper a) Data Object: SDS (4 Dimensional Array) b) Object Name: TIR_Supplement_Chopper c) Format: Table 2. Table 2.3.6-6 Format of TIR Supplement Data (Encoder) Dimension Size Variable Type [n][935] UINT16 n: revised to accommodate a processing scene.6-5 Format of TIR Supplement Data (Chopper*2) Dimension Size Variable Type [n][100][10][8]*1 UINT8 n: revised to accommodate a processing scene. Table 2. (*2) Each chopper image represents as follows: Component [0] [1] Band 10 Segment Width (bits) 12 [2] [3] [4] [5] [6] Band 11 Band 12 Band 13 Band 14 12 12 12 12 [7] Spare 4 Supplement Data about Encoder a) Data Object: SDS (2 Dimensional Array) b) Object Name: TIR_Supplement_Encoder c) Format: Table 2.3.

This page intentionally left blank. 2-70 .

V. T. VB(V stereo). DNmax is allocated to the specified maximum radiance for the instrument design. ST.. The definition of scene center in Level 1B is the actual center on the rotated coordinates (L1B coordinates). All of these data are stored together with Metadata.1 Overview Level 1B Data Products is an HDF file. And furthermore for SWIR in particular. Note 1: Resolution is shown as follows. and Swath Layout parts in one HDF file. Level 1B Product is created by performing the geometric and radiometric corrections on the original Level 1A image data. Data structure represented in Figure 3. the location on L1B image is between pixels). Level 1B Data Product 3. Vgroup/Vdata.. Note: VNIR (4 bands) and SWIR (6 bands) image data are 8-bit unsigned integer science data. and the result is projected onto rotated map (rotated to “path oriented” coordinate) at full instrument resolutions. (2) Data Structure The physical data of Level 1B Data Product is shown in Figure 3. and TIR (5 bands) image data are 16-bit unsigned integer science data in each category. not same as in L1A (i. the parallax errors due to the spatial locations of all of its bands are also corrected. Subsystem Resolution VNIR 15 m SWIR 30 m TIR 90 m Note 2: Saturation Digital Number (DN) Subsystem VNIR SWIR TIR DNmin 1 1 1 DNmax 255 255 4095 dummy pixel 0 0 0 DNmin is allocated to zero radiance. The Level 1B Data generation includes also scene registrations for SWIR and TIR data.0”. 3-1 . etc. Some category shall not set in the product.2-1 shows the conceptual view of the physical format of the product in case of full mode (VST) operation.3. SDS.e. Level 1B Data defines a scene center as the geodetic center of the scene obtained from L1A attribute named ‘SceneCenter’ in the HDF-EOS attribute “productmetadata. 3. i.e.2 Data Structure (1) Data Type There are five categories of HDF data type included in Level 1B data product. in case that it can not be applied to the dataset on account of the selected operational mode. Each file contains a complete 1-scene image data generated from Level 1A Data.2-1.

Level 1B Data Product Metadata Inventory Metadata ASTER Generic Metadata GDS Generic Metadata Product Specific Metadata (VNIR) Product Specific Metadata (SWIR) Product Specific Metadata (TIR) Bad Pixel Informations Ancillary Data VNIR Group VNIR Swath GeoFields (2D) VNIR Band 1 VNIR Band 2 VNIR Band 3N VNIR Band 3B Supplement Data SWIR Group SWIR Swath GeoFields (2D) SWIR Band 4 SWIR Band 5 SWIR Band 6 SWIR Band 7 SWIR Band 8 SWIR Band 9 Supplement Data TIR Group TIR Swath GeoFields (2D) TIR Band 10 TIR Band 11 TIR Band 12 TIR Band 13 TIR Band 14 Supplement Group Supplement Temp Supplement Chopper Supplement Encoder Figure 3. .2-1 Physical Data of Level 1B Data Product 3-2 .

8 and 9 data (6) ProductSpecificMetadataTIR :including the attribute about band-10. and are written to the HDF file attribute named “coremetadata.1-1 List of Objects in Inventory Metadata (1/2) No.1-1. (7) BadPixelInformation :including the attribute about lists of bad pixels every band. at which the center of the scene is observed.Applicable [3]). Southern-most coordinate of the scene expressed in geodetic latitude.1 Inventory Metadata (1) Indexes of Objects The object list of Inventory Metadata is shown in Table 3. Western-most coordinate of the scene expressed in longitude.3. 12.3. 2. This contains the time of day and calendar date. Eastern-most coordinate of the scene expressed in longitude. 5. ‘AM-1’ fixed. which are named as follows. 3N and 3B data.) Table 3.1 Metadata Level 1B Metadata consists of seven Master Groups. 1 Group/Object Name ShortName type*1 string 2 SizeMBDataGranule double 3 ProductionDateTime datetime 4 5 6 PlatformShortName InstrumentShortName BoundingRectangle string string 1 WestBoundingCoordinate double 2 NorthBoundingCoordinate double 3 EastBoundingCoordinate double 4 SouthBoundingCoordinate double 7 SingleDateTime 1 2 TimeofDay CalendarDate string string 3-3 Description The short name for information that identifies a dataset: ‘ASTL1B’ The volume of data contained in the granule. format: hhmmssd→dZ format: YYYYMMDD . (5) ProductSpecificMetadataSWIR :including the attribute about band-4. This block contains area coverage for a granule.3.11.3 Data Format 3.0”.3.3. Unit: Mbytes Generation date and time of this Level 1B product. Northern-most coordinate of the scene expressed in geodetic latitude. Inventory Metadata contains ASTER Meta-Parameters in Generic header for ASTER GDS Products (about Generic header for ASTER GDS Products.1. Inventory Metadata attributes apply to the whole L1B product. 6. (In Table 3.3. 13 and 14 data. A group contains a set of objects that all have a similar theme.1-1. The attributes included in Inventory Metadata are associated with DID311. see ASTER LEVEL 1 DATA PRODUCTS SPECIFICATION -. ‘ASTER’ fixed. group names are written in Bold characters. (1) InventoryMetadata (2) ASTERGenericMetadata (3) GDSGenericMetadata (4) ProductSpecificMetadataVNIR :including the attribute about band-1. 3. 7.

Table 3.3.1-1 List of Objects in Inventory Metadata (2/2)
Group/Object Name
Review

type*1

1

FutureReviewDate

string

2

ScienceReviewDate

string

No.
8

9

QAStats
1

QAPercentMissingData

double

2

QAPercentOutofBoundsData

double

3

QAPercentInterpolatedData

double

10

ReprocessingActual

string

11
12

PGEVersion
ProcessingLevelID

string
string

13

MapProjectionName

string

Description
This block provides for dates and
status as applicable for collection that
are active.
The date of the nearest planned QA
peer review in future.
format: YYYYMMDD
The date of the last QA peer review.
format: YYYYMMDD
This block contains measures of
quality for a granule.
The percentage of missing data in the
scene.
Unit: %
The percentage of out of bounds data
in the scene.
Unit: %
The percentage of interpolated data in
the scene.
Unit: %
The stating what reprocessing has
been performed on this granule.
{‘not reprocessed’, ‘reprocessed
once’, ‘reprocessed twice’,
‘reprocessing n times’}
The version of PGE
The classification of the science data
processing level: ‘1B’
The name of the mapping method for
the data. The available map
projection methods are as follows:
‘Equi-Rectangular’,
‘Lambert Conformal Conic’,
‘Polar Stereographic’,
‘Space Oblique Mercator’, and
‘Universal Transverse Mercator’

NOTES:
(*1) Object types used in Metadata are
a. datetime: CCSDS A (UTC) Format
b. integer
c. double: the floating point value is rounded to the appropriate number
(6 digits after the decimal-point character).
d. string

3-4

3.3.1.2 ASTER Generic Metadata
(1) Indexes of Objects
The Object list of ASTER Generic Metadata is shown in Table 3.3.1-2. ASTER Generic Metadata
attributes are written to the HDF file attribute named “productmetadata.0”.
ASTER Generic Metadata contains ASTER Parameters in Generic Header for ASTER GDS Products
(about Generic header for ASTER GDS Products, see ASTER LEVEL 1 DATA PRODUCTS
SPECIFICATION -- Applicable [3]). The ASTER Parameters are ASTER GDS specific attributes,
i.e. not associated with DID311.
(In Table 3.3.1-2, group names are written in Bold characters. A group contains a set of objects that
all have a similar theme.)

Table 3.3.1-2 List of Object in ASTER Generic Metadata (1/5)
No.
1

Group/Object Name
IDofASTERGDSDataGranule

type*1
string

2
3
4

ReceivingCenter
ProcessingCenter
PointingAngles

string
string

1
2
3
5

PointingAnglesContainer(n)*2
SensorName(n)*2
PointingAngle(n)*2
SettingTimeofPointing(n)*2
GainInformation
GainInformationContainer(n)*

string
double
datetime

2

3-5

Description
This provides a unique identifier for
location of a data granule held in
ASTER GDS.
Format:
‘ASTL1B YYMMDDHH
MMSSyymmddNNNN’
where,
YYMMDD:observation date
HHMMSS:observation time
yymmdd:the data granule
generation date
NNNN:the data granule
sequential No.
(per day)
‘EDOS’ fixed.
‘ASTER-GDS’ fixed.
Specification of the pointing angles of
ASTER sensors.
n = number of sensors
‘VNIR’ or ‘SWIR’ or ‘TIR’
pointing angle in degrees
YYYY-MM-DDThh:mm:ss.d→dZ
The information of the gain level.
This container contains the level of the
data acquisition gain for VNIR and
SWIR.

Table 3.3.1-2 List of Object in ASTER Generic Metadata (2/5)
No.
5
1

Group/Object Name
Gain(n)*2

6

CalibrationInformation

type*1
string

1

GeometricDBversion

string

2

RadiometricDBversion

string

3

CoarseDEMversion*3

string

7

DataQuality
1

CloudCoverage
1

SceneCloudCoverage

integer

3-6

Description
(Band Number, Band Gain)
where ,
Band Number:
‘01’,’02’,’3N’,’3B’,’04’,’05’,’06’,’07’,’
08’,’09’
Band Gain:
for VNIR:
‘HGH’: high gain
‘NOR’: normal gain
‘LOW’: low gain
for SWIR:
‘HGH’: high gain
‘NOR’: normal gain
‘LO1’: low gain 1
‘LO2’: low gain 2
when data is not acquired
or doesn't exist:
‘OFF’
Calibration information used to generate
the geometric and radiometric correction
tables.
The version information of the geometric
correction data.
(Version, Issuancedate, Comments)
where,
Version: Version No.
Issuance date: Issuance Date
Comments: Comments
The version information of the
radiometric correction data.
(Version, Issuancedate, Comments)
where,
Formats of these parameters are the
same as Item 6.1.
The version information of the Coarse
DEM database.
(Version, Issuancedate, Comments)
where,
Formats of these parameters are the
same as Item 6.1.
The information about the quality of this
product.
The information about the cloud
coverage of the scene
The percentage of cloud coverage for the
whole scene.
Unit: %

qcul: upper left qcur: upper right qcll: lower left qclr: lower right Unit: % The information about the input data used for generating this Level-1B product. qclr) where. 7 1 9 2 1 ASTEROperationMode 2 ObservationMode string ObservationModeContainer(n) *2 1 ASTERObservationMode(n)*2 string 3-7 Description The percentage for 4 quarters of a scene. GenDT: Generation date and time.Table 3. The container of ASTER observation mode. DataTyp) where. (SGname. qcll. or not existing in the granule) . DataTyp: copy of L1A. Observation) where. The observation mode of each sensor group. qcur. GenDT. The types of ASTER operation. ‘OBSERVATION’ or ‘CALIBRATION’ or ‘TEST’ This group contains ASTER observation mode.1-2 List of Object in ASTER Generic Metadata (3/5) Group/Object Name QuadrantCloudCoverage type*1 integer 8 SourceDataProduct string 9 InstrumentInformation No.3. SGname: ‘VNIR1’ or ‘VNIR2’ or ‘SWIR’ or ‘TIR’ Observation: ‘ON’ (data is acquired) or ‘OFF’ (data is not acquired. (DataID. (qcul. DataID: ID of input L1A Data Granule. The information about sensors used to acquire data.

3N.14 (data of band 01. ~ . flag = 01. 02.3N.14 is used in the granule generation) = XX (data corresponding to the band position marked with XX is not used) Example: Value = ‘XXXXXXXX04 05060708091011121314’ .3 ProcessedBands string 3-8 The status of all bands during observation.3B. Format: set of flags described as 2-bytes string.02. ~ .

‘DE’: descending direction.3. (lat.0 measured eastward from North. (az. The scene identifier defined by path.0<az<360. row.) revolution: 1-233 (nominal) The satellite flight direction when observation is done. lat: geodetic latitude long: geodetic longitude Unit: degree .0 The nominal spatial resolutions of VNIR.Table 3. row and view. SWIR and TIR. resolution of SWIR. long) where. (cycle. 0. (resolution of VNIR. path: 1-233 (nominal) row: 1-670 view: 1-7 (-1 for offnominal pointing) The orbit number of the satellite. The satellite recurrent cycle number and the revolution number in the cycle.1-2 List of Object in ASTER Generic Metadata (4/5) Group/Object Name SceneInformation type*1 1 ASTERSceneID integer 2 OrbitNumber*4 integer 3 RecurrentCycleNumber*4 integer 4 FlyingDirection string 5 SolarDirection double 6 SpatialResolution integer 7 SceneFourCorners No. -90. resolution of TIR) Unit: meter This group contains the information about 4 corner coordinates of the scene. view) where. ‘AS’: ascending direction. cycle: 1-260 (max. The sun direction as seen from the scene center. el) where. el: elevation angle in degree. This denotes the coordinates of the upper-left corner of the scene. (path. when data is acquired.0<el<90. az: azimuth angle in degree. revolution) where. 10 1 UpperLeft double 3-9 Description The information about the scene concerning with the data granule.

7. long) where.0 long: East longitude -180.1-2 List of Object in ASTER Generic Metadata (5/5) 2 Group/Object Name UpperRight type*1 double 3 LowerLeft double 4 LowerRight double 8 SceneCenter double 9 MapOrientationAngle double No.0<lat<90. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character). long) where. (lat. Unit: degree NOTES: (*1) Object types used in Metadata are a.1 This denotes the coordinates of the lower-right corner of the scene. 180. lat: geodetic latitude -90. d. long) where.1 This denotes the coordinates of the lower-left corner of the scene (lat. string (*2) Object whose name followed by (n) has “class” attribute. (*3) Level-1 data product generation software needs GTOPO30 as the source of the ASTER Coarse DEM data. 3-10 . 10 7 Description This denotes the coordinates of the upper-right corner of the scene.3.0<long<180.0 Unit: degree This denotes the angle between the path oriented image and the map oriented image within the range [-180. datetime: CCSDS A (UTC) Format b.1 Longitude and latitude of the scene center. It may repeat n-times. Formats of these parameters are the same as Item 10.7. (lat. long) where. (*4) This object is copied from the value denoted in the schedule information that AOS provied.0]. Formats of these parameters are the same as Item 10.Table 3. (lat. Formats of these parameters are the same as Item 10.7. integer c.0.

1-3 List of Object in GDS Generic Metadata No.. ‘ASTER_TIR’) (*3) This item is carried from L-1A information (L-1B browse is not created. GDS Generic Metadata attributes are written to the HDF file named attribute “productmetadata. ’ASTER_TIR’. d. 3-11 .e.1”. ’ASTER_SWIR’. NOTES: (*1) Object types used in Metadata are a. Table 3. for a set of sensors V+S+T: (‘ASTER_VNIR’. datetime: CCSDS A (UTC) Format b. 1 Object Name SensorShortName type*1 string 2 IDofASTERGDSDataBrowse string Description The redundant array of short name for all sensors using in generating the product*2: ‘ASTER_VNIR’. The ID of ASTER GDS browse granule generated using input Level 1A data product. The attributes included in GDS Generic Metadata are the specific attributes. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character).3.g.3.3 GDS Generic Metadata (1) Indexes of Objects The Object list of GDS Generic Metadata is shown in Table 3.3. and so refer to L-1A browse product as L-1B browse image. ‘ASTER_SWIR’.1. ‘ASTER_TIR’) for S+T: (‘ASTER_SWIR’.1-3. GDS Generic Metadata contains the generic header specified by GDS for ASTER GDS products. e.). integer c. ’ASTER_STEREO’.3.*3. string (*2) This item ‘SensorShortName’ contains all available sensor short names. not associated with DID311 nor the ASTER Parameters. i.

3.3.1.4 Product Specific Metadata(VNIR)
(1) Indexes of Objects
The Object list of Product Specific Metadata(VNIR) is shown in Table 3.3.1-4. Product Specific
Metadata(VNIR) attributes are written to the HDF file attribute named “productmetadata.v”.
Product Specific Metadata(VNIR) includes product specific attributes, i.e. not associated with DID311.
(In Table 3.3.1-4, group names are written in Bold characters. A group contains a set of objects that
all have a similar theme.)

Table 3.3.1-4 List of Object in Level 1B Product Specific Metadata(VNIR) (1/2)
Group/Object Name
VNIRBand1Data

type*1

1

ImageDataInformation1

integer

2

ImageStatistics1

No.
1

3

1

MinandMax1

integer

2

MeanandStd1

double

3

ModeandMedian1

integer

DataQuality1

3-12

Description
The information about VNIR
band 1 of Level-1B
The information of VNIR band 1
image data.
(npx, nln, bpp)
where,
npx: Number of pixels per
line (4980: nominal)
nln: Number of lines in
frame (4200: nominal)
bpp: Bytes per pixel
(1: fixed)
The statistical information about
the quality of Level 1B VNIR
band 1 data.
Minimum and Maximum value in
this band of Level 1B VNIR
image data.
(min, max)
where,
min: Minimum value
(1 < min < 255)
max: Maximum value
(1 < max < 255)
Mean and Standard deviation
value in this band of Level 1B
VNIR image data.
(mean, sd)
where,
mean: Mean value
(1.0 < mean < 255.0)
sd: Standard deviation value
Mode and Median value in this
band of Level 1B VNIR image
data.
(mode, med)
where,
mode: Mode value
(1 < mode < 255)
med: Median value
(1 < med < 255)
This group contains the
information about the quality of
Level 1B band 1 VNIR data.

Table 3.3.1-4 List of Object in Level 1B Product Specific Metadata(VNIR) (2/2)
No.
1
3

1

4

1

2
3
4

5

6

5

1
2
3
2 ~ 2.5.3
3 ~ 3.5.3
4 ~ 4.5.3

type*1
integer

Group/Object Name
NumberofBadPixels1

Description
The number of bad pixels in the
L-1B VNIR band-1 image.
(nbp, ncg)
where,
nbp: number of bad pixels.
ncg: number of elements of
the list of bad pixels*3.
ProcessingParameters1
This group contains the
parameters used by Level-1B
generation processing.
CorIntel1
string
Correction of the intertelescope
error of SWIR and TIR: ‘N/A’
fixed.
CorPara1
string
Correction of the SWIR parallax
error: ‘N/A’ fixed.
ResMethod1
string
Resampling Method:
‘BL’ or ‘NN’ or ‘CC’
MPMethod1
string
Map Projection Method:
‘UTM’, ‘PS’, ‘LAMCC’, ‘SOM’,
or ‘EQRECT’
ProjectionParameters1
double
Parameters used in GCTP Map
projection. (when parameters that
are not used are filled with the
value “0.0”.)
UTMZoneCode1
integer
Zone code for UTM projection
(when mapping without UTM.: 0
fixed). If southern zone is
intended then use negative values.
UnitConversionCoeff1
This group contains the
coefficients used for radiance
conversion, from the pixel value
of the band-1 image.
Incl1
double
Inclination Value
Offset1
double
Offset Value
ConUnit1
string
Converted Unit
‘W/m2/sr/µm’ fixed.
For next VNIRBand2Data, repeat the above items (1 through 1.5.3).
For next VNIRBand3NData, repeat the above items (1 through 1.5.3).
For next VNIRBand3BData, repeat the above items (1 through 1.5.3).

NOTES:
(*1) Object types used in Metadata are
a. datetime: CCSDS A (UTC) Format
b. integer
c. double: the floating point value is rounded to the appropriate number
(6 digits after the decimal-point character).
d. string
(*2) Object whose name followed by (n) has “class” attribute. It may repeat n-times.
(*3) The information concerning the list of bad pixels apart from this attribute and is written
to the separated attribute named “badpixelinformation”. Refer to the section 3.3.1.7,
titled Bad Pixel Information.
(*4) Level 1B image is projected onto map using GCTP map projection tools through SCF
Toolkit. About the parameters used in GCTP, see Appendix G of SCF Toolkit Users
Guide (reference [8]).
3-13

3.3.1.5 Product Specific Metadata(SWIR)
(1) Indexes of Objects
The Object list of Product Specific Metadata(SWIR) is shown in Table 3.3.1-5. Product Specific
Metadata(SWIR) attributes are written to the HDF file attribute named “productmetadata.s”.
Product Specific Metadata(SWIR) includes product specific attributes, i.e. not associated with
DID311.
(In Table 3.3.1-5, group names are written in Bold characters. A group contains a set of objects that
all have a similar theme.)

Table 3.3.1-5 List of Object in Level 1B Product Specific Metadata(SWIR) (1/3)
Group/Object Name
SWIRBand4Data

type*1

1

ImageDataInformation4

integer

2

ImageStatistics4

No.
1

1

MinandMax4

integer

2

MeanandStd4

double

3

ModeandMedian4

integer

3-14

Description
The information about SWIR band
4 of Level-1B.
The information of SWIR band 4
image data.
(npx, nln, bpp)
where,
npx: Number of pixels per
line (2490: nominal)
nln: Number of lines in
frame (2100: nominal)
bpp: Bytes per pixel
(1: fixed)
The statistical information about
the quality of Level 1B SWIR band
4 data.
Minimum and Maximum value in
this band of Level 1B SWIR image
data.
(min, max)
where,
min: Minimum value
(1 < min < 255)
max: Maximum value
(1 < max. < 255)
Mean and Standard deviation value
in this band of Level 1B SWIR
image data.
(mean, sd)
where,
mean: Mean value
(1.0 < mean < 255.0)
sd: Standard deviation value
Mode and Median value in this
band of Level 1B SWIR image
data.
(mode, med)
where,
mode: Mode value
(1 ≤ mode ≤ 255)
med: Median value
(1 < med < 255)

3-15 .3 DataQuality4 This group contains the information about the quality of Level 1B SWIR data.

LSDOset: SD offset in along track direction. (LAOset. The percentage of image matching used in the SWIR parallax correction processing.3. (CThld. Threshold value. ncg: number of elements of the list of bad pixels*3. LOThld. VOThld) where. PSDOset: SD offset in cross track direction. (LSDOset. 2: output is extracted from registration file. Average offset value. Standard deviation offset value. 1 3 1 2 3 type*1 integer Group/Object Name NumberofBadPixels4 SWIRRegistrationQuality4 1 ProcessingFlag4 integer 2 NumberofMeasurements4 3 MeasurementPointNumber4 4 AverageOffset4 integer integer double 5 StandardDeviationOffset4 double 6 Threshold4 double ParallaxCorrectionQuality4 1 PctImageMatch4 integer 2 AvgCorrelCoef4 double 3-16 Description The number of bad pixels in the L1B SWIR band-4 image. 4: output obtained by other method. Processing flag: 0: no output. ncg) where.1-5 List of Object in Level 1B Product Specific Metadata(SWIR) (2/3) No. LAOset: average offset in along track direction. The number of measurements The number of measurement points. CThld: Correction threshold LOThld: offset threshold in along track direction POThld: offset threshold in cross track direction VOThld: Vector offset threshold The information of SWIR parallax correction. PSDOset) where.Table 3. 1: output is the result computed. (nbp. POThld. because processing is impossible. Unit: % The Average Correlation Coefficient. . The registration information of SWIR based on VNIR. PAOset: average offset in cross track direction. PAOset) where. nbp: number of bad pixels.

see Appendix G of SCF Toolkit Users Guide (reference [8]).0”.1-5 List of Object in Level 1B Product Specific Metadata(SWIR) (3/3) No.1.3. Incl4 double Inclination Value Offset4 double Offset Value ConUnit4 string Converted Unit ‘W/m2/sr/µm’ fixed. ‘SOM’. (*4) Level 1B image is projected onto map using GCTP map projection tools through SCF Toolkit.) UTMZoneCode4 integer Zone code for UTM projection (when mapping without UTM. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character). 3-17 .3. For next SWIRBand4Data. (*3) The information concerning the list of bad pixels apart from this attribute and is written to the separated attribute named “badpixelinformation”. About the parameters used in GCTP. This group contains the parameters used by Level-1B generation processing. If southern zone is intended then use negative values.5.5. repeat the above items (1 through 1. NOTES: (*1) Object types used in Metadata are a. integer c.3). titled Bad Pixel Information.5. from the pixel value of the band-4 image.5. string (*2) Object whose name followed by (n) has “class” attribute.: 0 fixed).5. d.3). or ‘EQRECT’ ProjectionParameters4 double Parameters used in GCTP Map projection. Refer to the section 3.3). repeat the above items (1 through 1.3 3 ~ 3.5. For next SWIRBand6Data.5. repeat the above items (1 through 1. repeat the above items (1 through 1.3). ‘PS’. ‘LAMCC’.3). CorIntel4 string Correction of the intertelescope error of SWIR and TIR: ‘Corrected Intertelescope Error’ or ‘Uncorrected Intertelescope Error’ CorPara4 string Correction of the SWIR parallax error: ‘Corrected Parallax Error’ or ‘Uncorrected Parallax Error’ ResMethod4 string Resampling Method: ‘BL’ or ‘NN’ or ‘CC’ MPMethod4 string Map Projection Method: ‘UTM’.3 6 ~ 6.5.3 5 ~ 5.7. UnitConversionCoeff4 This group contains the coefficients used for radiance conversion.5.Table 3.3 4 ~ 4. repeat the above items (1 through 1. it may repeat n-times. For next SWIRBand5Data. Group/Object Name 1 3 3 3 Cthld4 4 ProcessingParameters4 1 2 3 4 5 6 5 1 2 3 2 ~ 2.5. datetime: CCSDS A (UTC) Format b.3 type*1 double Description The Correlation Threshold value. (when parameters that are not used are filled with the value “0. For next SWIRBand7Data. For next SWIRBand8Data.

A group contains a set of objects that all have a similar theme. Product Specific Metadata(TIR) includes product specific attributes. npx: Number of pixels per line (830: nominal) nln: Number of lines in frame (700: nominal) bpp: Bytes per pixel (2: fixed) The statistical information about the quality of Level 1B TIR data. < 4095) Mean and Standard deviation value in this band of Level 1B TIR image data. mean: Mean value (1.t”. (mean. Product Specific Metadata(TIR) attributes are written to the HDF file attribute named “productmetadata. group names are written in Bold characters.3.) Table 3.1-6.0) sd: Standard deviation value Mode and Median value in this band of Level 1B TIR image data. mode: Mode value (1 < mode < 4095) med: Median value (1 < med. (npx.6 Product Specific Metadata(TIR) (1) Indexes of Objects The Object list of Product Specific Metadata(TIR) is shown in Table 3. (In Table 3.1-6. i. < 4095) This group contains the information about the quality of Level 1B TIR data. sd) where.1.e. The information of TIR band 10 image data.3. not associated with DID311.3.0 < mean < 4095. Minimum and Maximum value in this band of Level 1B TIR image data. max) where.3. min: Minimum value (1 < min < 4095) max: Maximum value (1 < max.3. nln. bpp) where.1-6 List of Object in Level 1B Product Specific Metadata(TIR) (1/3) Group/Object Name TIRBand10Data type*1 1 ImageDataInformation10 integer 2 ImageStatistics10 No. (mode. (min. . med) where. 1 3 1 MinandMax10 integer 2 MeanandStd10 double 3 ModeandMedian10 integer DataQuality10 3-18 Description The information about TIR band 10 of Level-1B.

3. PSDOset) where. Correction of the intertelescope error of SWIR and TIR: ‘Corrected Intertelescope Error’ or ‘Uncorrected Intertelescope Error’ . PAOset) where. Average offset value. PAOset: average offset in cross track direction. The registration information of TIR based on VNIR. 4: output obtained by other method. Threshold value. (LAOset. 1: output is the result computed. Standard deviation offset value. ncg) where. (CThld. Processing flag: 0: no output. (LSDOset. ncg: number of elements of the list of bad pixels*3. POThld. LSDOset: SD offset in along track direction. nbp: number of bad pixels. (nbp. 2: output is extracted from registration file. LOThld.1-6 List of Object in Level 1B Product Specific Metadata(TIR) (2/3) No. LAOset: average offset in along track direction. because processing is impossible.Table 3. CThld: Correction threshold LOThld: offset threshold in along track direction POThld: offset threshold in cross track direction VOThld: Vector offset threshold This group contains the parameters used by Level-1B generation processing. 1 3 1 2 4 Group/Object Name NumberofBadPixels10 type*1 integer TIRRegistrationQuality10 1 ProcessingFlag10 integer 2 NumberofMeasurements10 3 MeasurementPointNumber10 4 AverageOffset10 integer integer double 5 StandardDeviationOffset10 double 6 Threshold10 double ProcessingParameters10 1 CorIntel10 string 3-19 Description The number of bad pixels in the L-1B TIR band-10 image. The number of measurements The number of measurement points. VOThld) where. PSDOset: SD offset in cross track direction.

Table 3. For next TIRBand13Data. ResMethod10 string Resampling Method: ‘BL’ or ‘NN’ or ‘CC’ MPMethod10 string Map Projection Method: ‘UTM’. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character). (*3) The information concerning the list of bad pixels apart from this attribute and is written to the separated attribute named “badpixelinformation”. (when parameters that are not used are filled with the value “0.7.) UTMZoneCode10 integer Zone code for UTM projection (when mapping without UTM. 3-20 . from the pixel value of the band-10 image.3). repeat the above items (1 through 1.5.5. NOTES: (*1) Object types used in Metadata are a.3 Group/Object Name CorPara10 type*1 string Description Correction of the SWIR parallax error: ‘N/A’ fixed.5. About the parameters used in GCTP. or ‘EQRECT’ ProjectionParameters10 double Parameters used in GCTP Map projection.3 3 ~ 3. repeat the above items (1 through 1.5. ‘LAMCC’. integer c. 1 4 2 3 4 5 6 5 1 2 3 2 ~ 2.: 0 fixed). string (*2) Object whose name followed by (n) has “class” attribute. repeat the above items (1 through 1. datetime: CCSDS A (UTC) Format b.3 5 ~ 5. For next TIRBand12Data. If southern zone is intended then use negative values. see Appendix G of SCF Toolkit Users Guide (reference [8]). Refer to the section 3. repeat the above items (1 through 1.3).5.0”. ‘PS’.3.5.5. Incl10 double Inclination Value Offset10 double Offset Value ConUnit10 string Converted Unit ‘W/m2/sr/µm’ fixed. ‘SOM’. (*4) Level 1B image is projected onto map using GCTP map projection tools through SCF Toolkit.3). For next TIRBand11Data.1-6 List of Object in Level 1B Product Specific Metadata(TIR) (3/3) No. titled Bad Pixel Information. For next TIRBand14Data. it may repeat n-times.3 4 ~ 4. UnitConversionCoeff10 This group contains the coefficients used for radiance conversion.1.3.3).5. d.

1 9 ~ 9.1). FP. For next Band3BInformation. Bad Pixel Information attributes are written to the HDF file attribute named “badpixelinformation”.1 7 ~ 7. and the mandatory attributes for their objects are flagged as “FALSE”.2. group names are written in Bold characters.3.1). For next Band6Information.1 3 ~ 3.2.2.7 Bad Pixel Information (1) Indexes of Objects The Object list of Bad Pixel Information is shown in Table 3. not associated with DID311.1). 3-21 integer Description This group contains the information concerning bad (interpolated) pixel of Level 1B VNIR Band-1 image.2.3.2. repeat the above items (1 through 1.1). LP) where.2.1).1 8 ~ 8. 1 1 2 ~ 2. (In Table 3.2.1-7. repeat the above items (1 through 1. No group that has no bad pixel.2.1).2. Lno: The line number including bad pixel segment FP: First pixel number of BPS LP: Last pixel number of BPS For next Band2Information. For next Band5Information. repeat the above items (1 through 1. repeat the above items (1 through 1. For next Band4Information.2.2.1). is set in this attribute. For next Band7Information.1 4 ~ 4. So.e.2. in case that all bands have no bad pixel.1). For next Band8Information.1. repeat the above items (1 through 1.1 ListofBadPixels1Container(n )*2 BadPixelSegments1(n)*2 Location information for each bad pixel element.1 6 ~ 6. this specific attribute will not appear in the HDF-EOS attribute.2.2. Table 3. repeat the above items (1 through 1.2.3.1 10 ~ 10. For next Band3NInformation.1-7.1-7 List of Object in Bad Pixel Information (1/2) Group/Object Name Band1Information type*1 1 NumberofElement1 integer 2 ListofBadPixels1 No. For next Band9Information. Bad Pixel Information includes product specific attributes.1). repeat the above items (1 through 1. A group contains a set of objects that all have a similar theme. .2.2.3.) Bad Pixel information is set for every band individually. (Lno.3. namely. repeat the above items (1 through 1. i.1 5 ~ 5. The number of elements of the list of bad pixels This group contains the locations of bad pixels.2. repeat the above items (1 through 1.

1).1). It may repeat n-times.1). NOTES: (*1) Object types used in Metadata are a.1 13 ~ 13. double: the floating point value is rounded to the appropriate number (6 digits after the decimal-point character).1).2. string (*2) Object whose name followed by (n) has “class” attribute. repeat the above items (1 through 1.2. 11 ~ 11.2.2.2.2.3.1-7 List of Object in Bad Pixel Information (2/2) No. 1.2. repeat the above items (1 through For next Band11Information. repeat the above items (1 through For next Band12Information.1).1 15 ~ 15. 3-22 . repeat the above items (1 through For next Band14Information.1 14 ~ 14. integer c. repeat the above items (1 through For next Band13Information. 1.2.2.2. d.Table 3. datetime: CCSDS A (UTC) Format b.1 Group/Object Name type*1 Description For next Band10Information. 1.1 12 ~ 12. 1.

the time data which represents the ancillary data updating time(UTC) is assigned to the leading ancillary data.n (n: Record count number -. 3-23 . This is used as control data for extracted Image Data.3. vgroup name: Ancillary_Data class: Ancillary Each record of Ancillary Data has following characteristics. and called Time Tag. a) Data model: Vdata b) Object Name: Ancillary_Data c) Class Name: Anci_Record. and their time tags. (2) Characteristics Ancillary Data Group contains a series of Ancillary Data Records through the use of Vgroup API.3.12 ~ 29 records) d) Format and contents: see Table 2.2 Ancillary Data (1) Description Ancillary Data includes the satellite's orbit/attitude data.3-1. To ensure the conformity with instrument data. Since ancillary data appended to onboard instrument data are updated once per major cycle time (1.024 sec).3. an extra number of ancillary data will be extracted and provided. in order to match with the scene observation time.

and so on).3. Polar Stereographic (PS). Cubic Convolution (CC) For further details on projection parameters (Projection Codes. Vgroup name that establishes access to a Vgroup is as follows. 3-24 .1 Overview VNIR Group contains an SDS and a Swath Object through the use of the Vgroup API. which for this release is: Map projection methods: Geographic (EQRECT). and Universal Transverse Mercator (UTM) Resampling methods: Nearest Neighbor (NN). Lambert Conformal Conic (LAMCC).3. vgroup name: VNIR class: 1B (1) Concept of Level 1B Data Product The Level 1B Data Product is generated for the requested map projection and the resampling method. Space Oblique Mercator (SOM). Bi-Linear (BL). please refer to the HDF-EOS User's Guide for ECS Project (Reference [4]) and the SDP Toolkit Users Guide for the ECS Project (Reference [8]).3.3.3 VNIR Group 3. Zone Codes.

3. 2. 180. though the Level 1B swath consists of a series of 2D data array (VNIR image data: Band 1.4-1).2 VNIR Swath (1) Structure A single swath contains any number of Tables and Multidimensional Arrays.0] geocentric longitude: decimal degree on range [-180.3.3. all bands in the same telescope are stored as a data field of the swath created per telescope.3.0.3-2 shows the format of one.3.0. 3N.3-1 shows the contents of Swath Object.3-1 List of data items in Level 1B VNIR Swath No. geolocation information is stored as a series of arrays. 5.3.3. Latitude Type Geolocation Array Unit deg. 3. and share the same geolocation information. Type Geolocation Array Block size 420 lines * 498 pixels 3-25 . The data itself is stored in multidimensional arrays in the swath.3-2 Format of data items in VNIR Swath Field Name Latitude Longitude ImageData1 ImageData2 ImageData3N ImageData3B Dimension Size [11][11] [11][11] [4200][4980] [4200][4980] [4200][4980] [4600][4980] Variable Type DOUBLE DOUBLE UINT8 UINT8 UINT8 UINT8 Remarks geolocation field (Array) geolocation field (Array) mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array (3) Block Size Block size is shown as follows. ImageData1 ImageData2 ImageData3N ImageData3B 2D Data Array 2D Data Array 2D Data Array 2D Data Array N/A N/A N/A N/A Comments geocentric latitude: decimal degree on range [-90.3. For the Level 1B Data Product. 3B) and a 2D geolocation arrays only. 2. 90. The only limitation is that the first dimension is the Track dimension. 6.3. Longitude Geolocation Array deg. 4.0) Level 1B spectral band 1 image data Level 1B spectral band 2 image data Level 1B spectral band 3N image data Level 1B spectral band 3B image data Table 3. Table 3. Table 3. a) Data model: Swath b) Object Name: VNIR_Swath c) Format: Table 3. There is however one type of information that is special: geolocation information.3-1 shows the List of data items in VNIR Swath (Swath data for VNIR). The structure of each Swath is almost as same as the Level 1A Swath (see Figure 2. Field Name 1. (2) Characteristics Table 3. We require that every swath contain some geolocation component. In a swath.

3. titled VNIR Supplement Data.3.3.3 VNIR Supplement Data (1) Description VNIR Supplement Data contains VNIR status data. (2) Characteristics a) Data model: SDS (2 Dimensional Array) b) Object Name: VNIR_Supplement c) Format: see the section 2. calibration data.4.6. pointing angles. 3-26 . etc.3.

180. Table 3. 90.0) Level 1B spectral band 4 image data Level 1B spectral band 5 image data Level 1B spectral band 6 image data Level 1B spectral band 7 image data Level 1B spectral band 8 image data Level 1B spectral band 9 image data Table 3.4-1 shows the contents of Swath Object. Latitude Type Geolocation Array Unit deg.3.0] geocentric longitude: decimal degree on range [-180.0. Vgroup name that establishes access to a Vgroup is as follows. a) Data model: Swath b) Object Name: SWIR_Swath c) Format: Table 3. 4. 6. (2) Characteristics Table 3. Table 3. Type Geolocation Array Block size 210 lines * 249 pixels 3-27 . 8.4 SWIR Group 3.3. 5.4-1 List of data items in Level 1B SWIR Swath No.3.1 Overview SWIR Group contains an SDS and a Swath Object through the use of the Vgroup API. vgroup name: SWIR class: 1B 3.2 SWIR Swath (1) Structure Refer to the section 3.4. 3. titled VNIR Swath. 2.3.3.3. Field Name 1.3.2.4-2 Format of data items in SWIR Swath Field Name Latitude Longitude ImageData4 ImageData5 ImageData6 ImageData7 ImageData8 ImageData9 Dimension Size [11][11] [11][11] [2100][2490] [2100][2490] [2100][2490] [2100][2490] [2100][2490] [2100][2490] Variable Type DOUBLE DOUBLE UINT8 UINT8 UINT8 UINT8 UINT8 UINT8 Remarks geolocation field (Array) geolocation field (Array) mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array (3) Block Size Block size is shown as follows.3.3. Longitude Geolocation Array deg.3.4-1 shows the List of data items in SWIR Swath (Swath data for SWIR). ImageData4 ImageData5 ImageData6 ImageData7 ImageData8 ImageData9 2D Data Array 2D Data Array 2D Data Array 2D Data Array 2D Data Array 2D Data Array N/A N/A N/A N/A N/A N/A Comments geocentric latitude: decimal degree on range [-90.3.0. 7.4.4-2 shows the format of one.

titled SWIR Supplement Data.3 SWIR Supplement Data (1) Description SWIR Supplement Data contains SWIR status data.3.5. etc. calibration data.8. 3-28 .3.4. (2) Characteristics a) Data Model: SDS (2 Dimensional Array) b) Object Name: SWIR_Supplement c) Format: see the section 2.3. pointing angles.

3. Type Geolocation Array Block size 70 lines * 83 pixels 3-29 .5-1 shows the List of data items in TIR Swath (Swath data for TIR).0.1 Overview TIR Group contains a Vgroup and a Swath Object through the use of the Vgroup API.3. (2) Characteristics Table 3.3.3. Latitude Type Geolocation Array Unit deg.0] geocentric longitude: decimal degree on range [-180. 5.5-1 List of data items in Level 1B TIR Swath No.3. 2.2 TIR Swath (1) Structure Refer to the section 3.0) Level 1B spectral band 10 image data Level 1B spectral band 11 image data Level 1B spectral band 12 image data Level 1B spectral band 13 image data Level 1B spectral band 14 image data Table 3.3. 6. Table 3. 90. Longitude Geolocation Array deg. vgroup name: TIR class: 1B 3. Field Name 1.3.0.3. 180.5 TIR Group 3.5-2 Format of data items in TIR Swath Field Name Latitude Longitude ImageData10 ImageData11 ImageData12 ImageData13 ImageData14 Dimension Size [11][11] [11][11] [700][830] [700][830] [700][830] [700][830] [700][830] Variable Type DOUBLE DOUBLE UINT16 UINT16 UINT16 UINT16 UINT16 Remarks geolocation field (Array) geolocation field (Array) mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array mapping to geolocation array (3) Block Size Block size is shown as follows.3.5.5-2 shows the format of one. titled VNIR Swath. 7. Table 3.3. ImageData10 ImageData11 ImageData12 ImageData13 ImageData14 2D Data Array 2D Data Array 2D Data Array 2D Data Array 2D Data Array N/A N/A N/A N/A N/A Comments geocentric latitude: decimal degree on range [-90.5-1 shows the contents of Swath Object. Vgroup name that establishes access to a Vgroup is as follows. a) Data model: Swath b) Object Name: TIR_Swath c) Format: Table 3.5. 4. 3.2.3.

TIR Supplement Data contains a series of SDS (Temperature. 3-30 .6.3. calibration data. vgroup name: TIR_Supplement class: Supplement (2) Characteristics See the section 2.3 TIR Supplement Data (1) Description TIR Supplement Data contains TIR status data. Chopper.5.7. pointing angles.3. and Encoder) through the use of the Vgroup API. etc.3. titled TIR Supplement Data. vgroup name that establishes access to a Vgroup is as follows.

5 Terminate swath access to the file by disposing of the file ID. SWinqgeofields(sw_id.2 Swath The programming model for accessing a swath data set through the SW interface is as follows: 1. dim_list) . number_type.1 Overview This Section contains programming model for accessing Level 1A and 1B Data Products by the Swath API. rank. Perform desired operations on data set. dims. 2. 3. A. number_type) . SWreadfield(sw_id. edge. field_name. SWextractregion(region_id. A-1 . mode) . corner_lat. for further detailed references. stride. The reader is directed to The HDF-EOS User's Guide for the ECS Project (Reference [4]). buffer) . To access a single swath data set in Level 1A Data Product (HDF file). sw_id = SWattach(file_id. SWinqdatafields(sw_id.Appendix A. swath_name) . 4. Open the file and initialize the SW interface by obtaining a file ID from a file name. entry_code. field_name. status = SWclose(file_id) . Sections 7 and 8. field_list. Open a swath data set by obtaining a swath ID from a swath name. rank. number_type) . string_buffer_size) . SWfieldinfo(sw_id. SWdefboxregion(sw_id. <Optional operations> inquiry or subset or read by using function as follows: SWnentires(sw_id. corner_lon. start. rank. buffer) . Close the swath data set by disposing of swath ID. status = SWdetach(sw_id) . field_list. field_name. DFACC_READ) . external_made. Programming Model A. the calling program must contain the following sequence of C calls: file_id = SWopen(filename.

Abbreviations and Acronyms A . Science Data Processing Segment (SDPS) Database Design and Database Schema Specifications for the ECS Project. AA-1 . May 1996 (Reference [9]) DOUBLE: double type (IEEE Double-Precision Format) DPS: Data Processing Subsystem E . ECEF: Earth Centered. CC: Cubic Convolution CCSDS: Consultative Committee on Space Data System CDRL: Construct Data Requirement List CDS: CCSDS Day Segmented Time Code COTS: commercial off-the-shelf CSCI: Computer Software Configuration Item D . Earth Fixed ECI: Earth centered inertial ECR: Earth centered rotating ECS: EOSDIS Core System EDC: EROS Data Center (DAAC) EDS: Expedited Data Set EDOS: EOSDIS Data and Operation System EOS: Earth Observing System EOSDIS: Earth Observing System Data and Information System EQRECT: Equi-Rectangular (Geographic. FLOAT: float type (IEEE Single-Precision Format) G . BL: Bi-Linear BPS: Bad Pixel Segment C . AOS: ASTER Operations Segment API: Application Program Interface APID: Application Process IDentifier ASCII: American Standard Code for Information Interchange ASTER: Advanced Spaceborne Thermal Emission and Reflection Radiometer (formerly ITIR) ATBD: Algorithm Theoretical Basis Document B . DAAC: Distributed Active Archive Center DDL: Direct Down Link DDS: DDL Data Set DEM: Digital Elevation Model DID: Data Item Description DID311: 311-CD-002-005. Uniform Longitude/Latitude) EROS: Earth Resource Observation System ERSDAC: Earth Remote Sensing Data Analysis Center ESDIS: Earth Science Data and Information System eom: End of month F .

LAMCC: Lambert Conformal Conic M .GCT: geo-coordinate transformation GCTP: General Cartographic Transformation Package GDS: Ground Data System GMT: Greenwich Mean Time GSFC: Goddard Space Flight Center GTOPO30: Global Topographic 30-arc-seconds DEM H . PDS: Production Data Set PGE: Product Generation Executive PGS: Product Generation System PGSTK: Product Generation System Toolkit POSIX: Portable Operating System Interface for Computer Environments PS: Polar Stereographic AA-2 . N/A: Not Applicable NASA: National Aeronautics and Space Administration NCSA: the National Center for Supercomputing Applications NN: Nearest Neighbor O . JD: Julian Day JPL: Jet Propulsion Laboratory L . MCF: Metadata Configuration File MJD: Modified Julian Day N . OBS: Observation ODL: Object Description Language P . I/F: interface I/O: input/output ICD: Interface Control Document ID: IDentification IEEE: Institute of Electrical and Electronics Engineers IERS: International Earth Rotation Service IMS: Information Management System INT8: 8-bit integer type INT16: 16-bit integer type INT32: 32-bit integer type INT64: 64-bit integer type IR: Interim Release ISO: International Standards Organization J . HDF: Hierarchical Data Format HDF-EOS: an EOS proposed standard for a specialized HDF data format HITC: Hughes Information Technology Corporation I .

RIS8: 8-bit Raster type RIS24: 24-bit Raster type RMS: Root Mean Squared RTF: Rich Text Format S . WGS84: World Geometric System '84 AA-3 .: United States UINT8: 8-bit unsigned integer type. QA: Quality Assurance R . UINT16: 16-bit unsigned integer type. VNIR: Visible and Near Infrared W .PVL: Parameter Value Language Q . U. UINT32: 32-bit unsigned integer type UINT64: 64-bit unsigned integer type UT: Universal Time UTC: Universal Time Coordinated UTM: Universal Transverse Mercator V . SCF: Science Computing Facility SDP: Science Data Production SDTS: Spacial Data Transfer Standard SDPS: Science Data Processing Segment SDPS/W: Science Data Processing Software SDPTK: SDP Toolkit CSCI SGI: Silicon Graphics Incorporated SOM: Space Oblique Mercator SW: Swath SWIR: Shortwave Infrared T .S. TAI: International Atomic Time TBD: To Be Determined TBR: To Be Resolved TBS: To Be Specified TIR: Thermal Infrared U .