GPM - DPR - L1 Product Format Documentation - V5 - E
GPM - DPR - L1 Product Format Documentation - V5 - E
TRMM/PR
L1 Product Format Documentation
Product Version 5
Version 3.1
Octover, 2017
Reference
(1) RECIPITATION PROCESSING SYSTEM, GLOBALPRECIPITATION MEASUREMENT, File
Specification for GPM Products
(2) PRECIPITATION PROCESSING SYSTEM GLOBAL PRECIPITATION MEASUREMENT
Metadata for GPM Products
i
Table of Contents
ii
1. Data Format Structure
1
1.1 Dimension Definition
2
1.2 Data Format Structure for 1BKu
3
1.3 Data Format Structure for 1BKa
4
1.4 Data Format Structure for each Group
5
1.4 Data Format Structure for each Group
6
1.4 Data Format Structure for each Group
7
1.4 Data Format Structure for each Group
8
1.4 Data Format Structure for each Group
9
1.4 Data Format Structure for each Group
10
2. UContents of Objects in each Group
11
2.1 Metadata
2.1.1 FileHeader
2.1 Metadata
Metadata has seven elements. Figure 2.1-1 shows metadata structure.
FileHeader Metadata(Attribute)
InputRecord Metadata(Attribute)
NavigationRecord Metadata(Attribute)
FileInfo Metadata(Attribute)
DPRKa(u)Info Metadata(Attribute)
2.1.1 FileHeader
FileHeader contains metadata of general interest. This group appears in all data products. Table
2.1.1-1 shows each metadata elements in FileHeader.
Table2.1.1-1 FileHeaderElements
Data size
No Element Description
(bytes)
12
2.1 Metadata
2.1.1 FileHeader
Data size
No Element Description
(bytes)
Values are: TRMM GPM MULTI F10 ... F18 AQUAGCOMW1 CORIOLIS MT1
7 SatelliteName NOAA15 ... NOAA19 METOPANPP. More values will be added as they are 10
known.
Values are: PR TMI VIRS PRTMI KU KA DPR GMIDPRGMI MERGED SSMI
8 InstrumentName SSMIS AMSRE AMSR2 WINDSATMADRAS AMSUA AMSUB SAPHIR 10
MHS ATMS. Morevalues will be added as they are known.
The date and time this granule was generated. The format is
YYYY-MM-DDTHH:MM:SS.sssZ, where YYYY is 4-digit year, MM is month
9 GenerationDateTime number, DD is day of month, T is "T", HH is hour, MM is minute, SS is second, 50
sss is millisecond, and Z is "Z". All fields are zero-filled. The missing value is
constructed by replacing all digits with 9, i.e., 9999-99-99T99:99:99.999Z.
The start time defining this granule. The format is the same as
GenerationDateTime. DETAILS: An orbital granule starts when the satellite is at
the position defined by GranuleStart. Thus the start time is not the first scan time.
10 StartGranuleDateTime 50
Some algorithms have overlap scans in the file before the start time as defined in
SwathHeader. A monthly granule starts on the first ms of the month, for example
March 1998 would be 1998-03-01T00:00:00.000Z.
The stop time defining this granule. The format is the sameas
GenerationDateTime. DETAILS: An orbital granule stopswhen the satellite is at
the position defined by GranuleStart.Thus the stop time is not the last scan time.
11 StopGranuleDateTime 50
Some algorithmshave overlap scans in the file after the stop time asdefined in
SwathHeader. A monthly granule stops on the lastms of the month, for example
March 1998 would be 1998-03-31T23:59:59.999Z.
The number of this granule, which starts as in GranuleStart.
If the GranuleStart is identical to the orbit start, then the GranuleNumber will be
12 GranuleNumber 50
the same as the orbit number. The GranuleNumber will have 6 digits, including
leading zeroes, for example 001234.
The starting place in the orbit of this granule. Currently defined values
15 GranuleStart are ”SOUTHERNMOST LATITUDE” and ”NORTHBOUND EQUATOR 50
CROSSING”.
The time interval covered by this granule. Values are ”ORBIT”, ”HALF
16 TimeInterval ORBIT”, ”HALF HOUR”, ”HOUR”, ”3 HOUR”, ”DAY”, ”DAY ASC”, DAY 50
DES”, ”MONTH”, ”CONTACT”.
13
2.1 Metadata
2.1.2 InputRecord
2.1.2 InputRecord
InputRecord contains a record of input files for this granule.This group appears in Level 1, Level 2,
and Level 3 orbital data products. Level 3 time averaged products have thesame information
separated into 3 groups since they have many inputs. Table 2.1.2-1 shows each metadata elements in
InputRecord.
2 InputAlgorithmVersions A list of algorithm versions of the input files for this granule. 1000
A list of generation date times of the input files for this granule. The format is the
3 InputGenerationDateTimes 1000
same as GenerationDateTime.
2.1.3 NavigationRecord
NavigationRecord contains navigation metadata for this granule. This group appears inLevel 1,
Level 2, and Level 3 orbital data products.Table 2.1.3-1 shows each metadata elements in
NavigationRecord.
The longitude where the satellite crosses the equator going from
1 LongitudeOnEquator 50
south to north.
The UTC time when the satellite crosses the equator going from
2 UTCDateTimeOnEquator 50
south to north. The format is the same as GenerationDate Time.
6 GeoControlFileName Name of the GeoTK Control Parameters File input for processing. 50
14
2.1 Metadata
2.1.3 NavigationRecord
Data size
No Element Description
(bytes)
Values are
”0 CONSTANT INPUT TEST VALUE”,
”1 GROUND ESTIMATED STATE (GES)”,
”2 GPS FILTERED SOLUTION (GEONS)”,
”3 GPS POINT SOLUTION (PVT)”,
7 EphemerisSource ”4 ON BOARD PROPAGATED (OBP)”, 50
”5 OEM GROUND EPHEMERIS FILE”,
”6 GEONS WITH FALLBACK AS FLAGGED”,
”7 PVT WITH FALLBACK AS FLAGGED”,
”8 OBP WITH FALLBACK AS FLAGGED”,
”9 GES WITH FALLBACK AS FLAGGED”.
values are
8 AttitudeSource ”0 CONSTANT INPUTS FOR TESTING”, 50
”1 ON BOARD CALCULATED PITCH ROLL YAW”.
Euler rotation sequence, first rotation axis. Values are "1","2", "3"
13 SensorAlignmentFirstRotationAxis 50
(representing X, Y, Z).
Euler rotation sequence, second rotation axis. Values are "1","2", "3"
14 SensorAlignmentSecondRotationAxis 50
(representing X, Y, Z).
Euler rotation sequence, third rotation axis. Values are "1","2", "3"
15 SensorAlignmentThirdRotationAxis 50
(representing X, Y, Z).
15
2.1 Metadata
2.1.4 FileInfo
2.1.4 FileInfo
FileInfo contains metadata used by the PPS I/O Toolkit.This group appears in all data products.
Table 2.1.4-1 shows each metadata elements in FileInfo.
The version of the data format used to write this file. This version is separate for
1 DataFormatVersion 50
each AlgorithmID. The order is: "a" "b" ... "z" "aa" "ab" ... "az" "ba" "bb".
The version of metadata used to write this file. This version is separate for each
3 MetadataVersion 50
AlgorithmID. The order is: "a" "b" ... "z" "aa" "ab" ... "az" "ba" "bb" ...
The filename of the primary blueprint file that defined the format used to write
5 BlueprintFilename 50
this file.
The version of TKIO used to create I/O routines to write this file. TKIOVersion
7 TKIOVersion 50
does not define the format used to write this file.
The style in which the metadata was written, e.g., "PVL"."PVL" means
8 MetadataStyle 50
< parameter >=< value >.
The endian type of the system that wrote this file. Values are "BIG ENDIAN" and
9 EndianType 50
"LITTLE ENDIAN".
16
2.1 Metadata
2.1.5 JAXAInfo
2.1.5 JAXAInfo
JAXAInfo contains metadata requested by JAXA.Used by DPR algorithms and GSMaP. Table
2.1.5-1 shows each metadata elements in JAXAInfo.
Table 2.1.5-1 JAXAInfoElements
Data size
No Element Description
(bytes)
Granule First Scan UTC Date. Date is a 24 character string. The format is
YYYY-MM-DDTHH:MM:SS.sssZ, where YYYY is 4-digit year, MM is
month number, DD is day of month, T is ”T”, HH is hour, MM is minute,
1 GranuleFirstScanUTCDateTime 50
SS is second, sss is millisecond, and Z is ”Z”. All fields are zero-filled.
The missing value is constructed by replacing all digits with 9,
i.e.,9999-99-99T99:99:99.999Z.
Granule Last Scan UTC Date. Date is a 24 character string. The format is
YYYY-MM-DDTHH:MM:SS.sssZ, where YYYY is 4-digit year, MM is
2 GranuleLastScanUTCDateTime 50
month number, DD is day of month, T is ”T”, HH is hour, MM is minute,
SS is second, sss is millisecond, and Z is ”Z”. All fields are zero-filled.
The total quality of GPM KuPR/KaPR L1B product is defined based on the
number of missing scans.
3 TotalQualityCode Quality meaning are 50
Good: missing scans > 0
EG(Empty Granule): missing scans = 0
17
2.1 Metadata
2.1.6 DPRKuInfo
Data size
No Element Description
(bytes)
2.1.6 DPRKuInfo
DPR KuInfo contains DPR Ku and PR information. This group appears in 1BKu and 1BPR. Table
2.1.6-1 shows each metadata elements in DPRKuInfo.
1 scanAngleObsVersion The version of scan angle table which is used for non-external calibration mode. 100
2 scanAngleExtVersion The version of scan angle table which is used for external calibration mode. 100
7 logAveOffset The offset value (dB) between logarithmic average and normal average. 100
8 alignmentAngleBasicEtoA Rotation angle (degrees) from electrical axis to antenna axis. 100
9 alignmentAngleOffsetAtoM Offset angle (degrees) from antenna axis to mechanical axis. 100
2.1.7 DPRKaInfo
DPR KaInfo contains DPR Ka information. This group appears in 1BKa. It is same as DPRKuInfo.
Please see “2.1.6-1 DPRKuInfo”.
18
2.1 Metadata
2.1.8 SwathHeader
2.1.8 SwathHeader
SwathHeader contains metadata for each swath. This group appears in Level 1 and Level 2 data
products. Table 2.1.8-1 shows each metadata elements in SwathHeader.
Table2.1.8-1 SwathHeaderElements
Data size
No Element Description
(bytes)
The scans read by TKreadScan are a ”set”. For single swath data, one scan is
read so NumberScansInSet=1. For multiple swath data, one TKreadScan may
read more than one scan. For example, for SSM/I data one TKreadScan reads
1 NumberScansInSet 50
one low frequency scan and two high frequency scans. Therefore
NumberScansInSet=1 for the low frequency swath and Number-ScansInSet=2
for the high frequency swath.
The maximum allowed number of total scans in this swath. Total scans =
2 MaximumNumberScansTotal 50
overlap scans before granule + scans in granule + overlap scans after granule.
3 NumberScansBeforeGranule The number of overlap scans before the first scan of the granule in this swath. 50
5 NumberScansAfterGranule The number of overlap scans after the last scan of the granule in this swath. 50
19
2.2 Data Group
SwathHeader Metadata(Attribute)
ScanTime Group
Receiver Group
Transmitter Group
scanStatus Group
navigation Group
rayPointing Group
HouseKeeping Group
Calibration Group
20
2.2 Data Group
2.2.1 ScanTime (Group)
(1) Year
Type Array Unit
4-digit year, e.g., 2014. Values range from 1950 to 2100 years.
Missing value:
N/A
(2) Month
Type Array Unit
(3) DayOfMonth
Type Array Unit
(4) Hour
Type Array Unit
21
2.2 Data Group
2.2.1 ScanTime (Group)
(5) Minute
Type Array Unit
(6) Second
Type Array Unit
(7) MilliSecond
Type Array Unit
(8) DayOfYear
Type Array Unit
(9) SecondOfDay
Type Array Unit
A time associated with the scan. It is expressed as the UTC seconds of theday.Values range from 0
to 86400 s.
Missing value:
N/A
22
2.2 Data Group
2.2.2 Latitude
2.2.2 Latitude
(1) Latitude
Type Array Unit
The earth latitude of the center of the IFOV at the altitude of the earth ellipsoid. Latitudeis positive
north, negative south. Values range from -90 to 90 degrees.
Missing value:
-9999.9
2.2.3 Longitude
(1) Longitude
Type Array Unit
The earth longitude of the center of the IFOV at the altitude of the earth ellipsoid.Longitude is
positive east, negative west. A point on the 180th meridian has the value-180 degrees.Values range
from -180 to 180 degrees.
Missing value:
-9999.9
(1) echoPower
Type Array Unit
It is received power, which is multiplied by 100. Bins where data is not written due to a
transmission, calibration, or other problem, including an entire scan of missing bins, have the value
of -30000. Outrange bins of the observation area controlled by VPRF tables have the value of -29999.
The range is -120 dBm to -20 dBm, which corresponds to values in the file from -12000 to -2000.
Missing values:
“Count value”: internal calibration mode.
-29999 : Outrange bins of the observation area.
-30000 : missing value.
23
2.2 Data Group
2.2.4 Receiver (Group)
(2) echoCount
Type Array Unit
The total signal count at the antenna input that includes both echo and noise power. The signal
count is stored on both observation mode and calibration mode. It is basically a copy of science
telemetry raw data for sampling range bins. 0 is set to both interpolated range bin and outrange bin of
the observation mode.
Missing values:
0:at missing scan, thinning out range (normal sample) and out of observation range.
(3) noisePower
Type Array Unit
An average of the received noise power for each angle bins during suspended 4 pulses. The range
is -120 dBm to -20 dBm which corresponds to values in the file from -12000 to -2000.
Missing value:
-30000 : at missing scan and internal calibration mode.
(4) noiseCount
Type Array Unit
An average of the received noise count for each angle bins during suspended 4 pulses.
Missing value:
-9999.9 : at missing scan and internal calibration mode.
(5) noiseSampleNumber
Type Array Unit
It is the number of noise samplings defined by VPRF table. Values range from 0 to 140 Number.
Missing value:
-9999 : at missing scan and internal calibration mode.
24
2.2 Data Group
2.2.5 Transmitter (Group)
(6) echoSampleNumber
Type Array Unit
It is the number of received pulse defined by VPRF table. Values range from 0 to 60 Number.
Missing value:
48 : at internal calibration mode.
-99 : at missing scan.
(7) rxAntGain
Type Array Unit
(8) receivedPulseWidth
Type Array Unit
Received pulse width (s) after passing through band pass filter of FCIF.
Missing value:
-9999.9 : at missing scan and internal calibration mode.
(1) radarTransPower
Type Array Unit
The total (sum) power of 128 SSPA elements corrected with SSPA temperature in orbit. It is based
on ground test temperature data of SSPA transmission power.
Missing value:
-9999.9 : at missing scan and internal calibration mode.
(2) transPulseWidth
Type Array Unit
Transmitted pulse width corrected with FCIF temperature in orbit, based on temperaturetest data of
25
2.2 Data Group
2.2.5 Transmitter (Group)
26
2.2 Data Group
2.2.6 VertLocate (Group)
(3) txAntGain
Type Array Unit
(1) landOceanFlag
Type Array Unit
Missing value:
-9999 : Land or Ocean Database is missing.
(2) scLocalZenith
Type Array Unit
The angle, in degrees, between the local zenith and the beam’s center line. The local (geodetic)
zenith at the intersection of the ray and the earth ellipsoid is used. Values range from 0 to 90 degrees.
Missing value:
-9999.9
(3) startBinRange
Type Array Unit
It is the distance from the satellite to the center of the first range bin. Values range from 350000 to
500000 m.
Missing value:
-9999 : at missing scan and internal calibration mode.
27
2.2 Data Group
2.2.6 VertLocate (Group)
(4) echoHighResBinNumber
Type Array Unit
It is the number of sampling without thinning out (over sampling). Values range from 1 to 260
range bin number at NS and MS while from 1 to 130 at HS.
Missing values :
-9999 : at missing scan.
42 : at internal calibration mode.
(5) echoLowResBinNumber
Type Array Unit
It is the number of sampling with thinning out (normal sample). Values range from 1 to 260 range
bin number at NS and MS while from 1 to 130 at HS.
Missing value:
-9999 : at missing scan and internal calibration mode.
(6) binEllipsoid
Type Array Unit
The range bin number of the earth ellipsoid. Values range from 1 to 260 range bin number at NS
and MS, from 1 to 130 at HS.
Missing value:
-9999 : at missing scan and internal calibration mode.
(7) scRangeEllipsoid
Type Array Unit
28
2.2 Data Group
2.2.6 VertLocate (Group)
(8) binDEM
Type Array Unit
The range bin number of the average DEM surface elevation in a box centered on the IFOV.
Reference width is 5 km x 5 km. Reference number of pixels in the direction of latitude is 7. On the
other hand, the number of pixels in the direction of longitude reference is changed to 21-7 by latitude.
Values range from 1 to 260 range bin number at NS and MS while from 1 to 130 at HS.
Missing value:
-9999 : at missing scan and internal calibration mode and in case DEM is missing.
(9) scRangeDEM
Type Array Unit
(10) DEMHmean
Type Array Unit
DEMHmean is defined as averaged DEM height, whose SRTM-30, in each ray. Values range from
0 to 9000 m.
Missing value:
-9999.9 : DEM is missing
(11) binDEMHtop
Type Array Unit
The range bin number of the maximum DEM surface elevation in a box centered on the IFOV.
Reference width is 5 km x 5 km. Reference number of pixels in the direction of latitude is 7. On the
other hand, the number of pixels in the direction of longitude reference is changed to 21-7 by latitude.
Values range from 1 to 260 range bin number at NS and MS, from 1 to 130 at HS.
Missing value:
-9999 : at missing scan and internal calibration mode and in case DEM is missing.
29
2.2 Data Group
2.2.6 VertLocate (Group)
(12) binDEMHbottom
Type Array Unit
The range bin number of the minimum DEM surface elevation in a box centered on the IFOV.
Reference width is 5 km x 5 km. Reference number of pixels in the direction of latitude is 7. On the
other hand, the number of pixels in the direction of longitude reference is changed to 21-7 by latitude.
Values range from 1 to 260 range bin number at NS and MS, from 1 to 130 at HS.
Missing value:
-9999 : at missing scan and internal calibration mode and in case DEM is missing.
(13) binEchoPeak
Type Array Unit
It is the range bin number which has maximum echoPower in each scan and each angle bin. Values
range from 1 to 260 range bin number at NS and MS, from 1 to 130 at HS.
Missing value:
-9999 : at missing scan and internal calibration mode.
(14) alongTrackBeamWidth
Type Array Unit
Radar beamwidth (degree) at the point transmitted power reaches one half of peak power in the
along-track direction.
Missing value:
N/A
(15) crossTrackBeamWidth
Type Array Unit
Radar beamwidth (degree) at the point transmitted power reaches one half of peak power along the
cross-track direction.
Missing value:
N/A
30
2.2 Data Group
2.2.6 VertLocate (Group)
(16) mainlobeEdge
Type Array Unit
Absolute distance in range bin numbers between the detected surface and the upper edge of the
clutter from the mainlobe.
Missing value:
N/A
(17) sidelobeRange
Type Array Unit
Absolute distance in range bin numbers between the detected surface and the upper clutter position
from the sidelobe.
Missing value:
N/A
(18) ellipsoidBinOffset
Type Array Unit
It is the distance between center of binEllipsoid range bin and Ellipsoid position.
Missing value:
-9999.9 : at missing scan and internal calibration mode.
(19) rangeBinSize
Type Array Unit
31
2.2 Data Group
2.2.6 VertLocate (Group)
(20) ratioLand
Type Array Unit
(21) ratioOcean
Type Array Unit
(22) ratioInLand
Type Array Unit
(23) ratioCoast
Type Array Unit
32
2.2 Data Group
2.2.7 scanStatus (Group)
(1) dataQuality
Type Array Unit
A summary of data quality in the scan. Unless this is 0 (normal), the scan data is meaningless to
higher precipitation processing. Bit 0 is the least significant bit (i.e., if bit i = 1 and other bits = 0, the
unsigned integer value is 2**i).
Bit Meaning
0 : missing
5 : geoError is not zero
6 : modeStatus is not zero
(2) dataWarning
Type Array Unit
33
2.2 Data Group
2.2.7 scanStatus (Group)
(3) missing
Indicates whether information is contained in the scan data. The values are:
Bit Meaning
0 : Scan is missing
1 : Science telemetry packet missing
2 : Science telemetry segment withing packet missing
3 : Science telemetry other missing
4 : Housekeeping (HK) telemetry packet missing
5 : Spare (always 0)
6 : Spare (always 0)
7 : Spare (always 0)
(4) modeStatus
Type Array Unit
A summary of status modes. If all status modes are routine, all bits in modeStatus = 0. Routine
means that scan data has been measured in the normal operational situation as far as the status modes
are concerned. modeStatus does not assess geolocation quality. modeStatus is broken into 8 bit flags.
Each bit = 0 if the status is routine but the bit = 1 if the status is not routine. Bit 0 is the least
significant bit (i.e., if bit i = 1 and other bits = 0, the unsigned integer value is 2**i). The non-routine
situations follow:
Bit Meaning
0 : Spare (always 0)
1 : SCorientation not 0 or 180
2: pointingStatus not 0
3 : Non-routine limitErrorFlag
4 : Non-routine operationalMode (not 1 or 11)
5 : Spare (always 0)
6 : Spare (always 0)
7 : Spare (always 0)
34
2.2 Data Group
2.2.7 scanStatus (Group)
(5) geoError
Type Array Unit
A summary of geolocation errors in the scan. geoError is used to set a bit in dataQuality. A zero
integer value of geoError indicates ’good’ geolocation. A non-zero value broken down into the bit
flags below indicates the specified reason, where bit 0 is the least significant bit (i.e., if bit i = 1 and
other bits = 0 the unsigned integer value is 2**i). Bits 0, 4, 5, 8 and 9 are per pixel error flags. If the
number of bad pixels (for any of the reasons specified by these flags) is greater than the threshold
then bit 7 = 1 and each of these flags is set to 1 if any pixel is bad for that reason. At launch this
threshold is zero, so data is flagged if any pixel is bad. If the number of bad pixels is less than or
equal to the threshold then bit 7 = 0 and all of these flags are also 0.
Bit Meaning
0 : Latitude limit exceeded for viewed pixel locations
1 : Negative scan time, invalid input
2 : Error getting spacecraft attitude at scan mid-time
3 : Error getting spacecraft ephemeris at scan mid-time
4 : Invalid input non-unit ray vector for any pixel
5 : Ray misses Earth for any pixel with normal pointing
6 : Nadir calculation error for subsatellite position
7 : Pixel count with geolocation error over threshold
8 : Error in getting spacecraft attitude for any pixel
9 : Error in getting spacecraft ephemeris for any pixel
10 : Spare (always 0)
11 : Spare (always 0)
12 : Spare (always 0)
13 : Spare (always 0)
14 : Spare (always 0)
15 : Spare (always 0)
35
2.2 Data Group
2.2.7 scanStatus (Group)
(6) geoWarning
Type Array Unit
A summary of geolocation warnings in the scan. geoWarning does not set a bit in dataQuality.
Warnings indicate unusual conditions. These conditions do not indicate bad geolocation but are
flagged as a warning that further review of the data may be useful. A zero integer value indicates
usual geolocation. A non-zero value broken down into the following bit flags indicates the following,
where bit 0 is the least significant bit (i.e., if bit i = 1 and other bits = 0 the unsigned integer value is
2**i):
Bit Meaning
0 : Ephemeris Gap Interpolated
1 : Attitude Gap Interpolated
2 : Attitude jump/discontinuity
3 : Attitude out of range
4 : Anomalous Time Step
5 : GHA not calculated due to error
6 : SunData (Group) not calculated due to error
7 : Failure to calculate Sun in inertial coordinates
8 : Fallback to GES ephemeris
9 : Fallback to GEONS ephemeris
10 : Fallback to PVT ephemeris
11 : Fallback to OBP ephemeris
12 : Spare (always 0)
13 : Spare (always 0)
14 : Spare (always 0)
15 : Spare (always 0)
36
2.2 Data Group
2.2.7 scanStatus (Group)
(7) SCorientation
Type Array Unit
The positive angle of the spacecraft vector (v) from the satellite forward direction of motion,
measured clockwise facing down. We define v in the same direction as the spacecraft axis +X, which
is also the center of the GMI scan. If SCorientation is not 0 or 180, a bit is set to 1 in modeStatus.
Value Meaning
0 : +X forward (yaw 0)
180 : -X forward (yaw 180)
-8000 : Non-nominal pointing
-9999 : Missing
(8) pointingStatus
Type Array Unit
It is provided by the GeoTK. A value of zero means the pointing is good. Non-zero values indicate
non-nominal pointing. If pointingStatus is non-zero, a bit in modeStatus is set to 1.
Value Meaning
0 : Nominal pointing in Mission Science Mode
1 : GPS point solution stale and PVT ephemeris used
2 : GEONS solution stale and GEONS ephemeris used
-8000 : Non-nominal mission science orientation
-9999 : Missing
37
2.2 Data Group
2.2.7 scanStatus (Group)
(9) acsModeMidScan
Type Array Unit
It is provided by the GeoTK as taken from Attitude Control System telemetry and is provided in
this format for information only.
Value Meaning
0 : LAUNCH
1 : RATENULL
2 : SUNPOINT
3 : GSPM (Gyro-less Sun Point)
4 : MSM (Mission Science Mode)
5 : SLEW
6 : DELTAH
7 : DELTAV
(10) targetSelectionMidScan
Type Array Unit
It is provided by the GeoTK as taken from Attitude Control System telemetry and is provided in
this format for information only.
Value Meaning
0 : S/C Z axis nadir, +X in flight direction
1 : Flight Z axis nadir, +X in flight direction
2 : S/C Z axis nadir, -X in flight direction
3 : Flight Z axis nadir, -X in flight direction
4 : +90 yaw for DPR antenna pattern calibration
5 : -90 yaw for DPR antenna pattern calibration
-99 : Missing
Other standard target orientations TBD
38
2.2 Data Group
2.2.7 scanStatus (Group)
(11) operationalMode
Type Array Unit
39
2.2 Data Group
2.2.7 scanStatus (Group)
(12) limitErrorFlag
Type Array Unit
It has 2 error information. One is as for noise power limit, another one is as for binEllipsoid limit.
The former is defined that if there are more than 2 overlimitted rays in a swath, limitErrorFlag(at
0bit) is adapted. On the other hand, the later is defined that if there is even an overlimitted ray,
limitErrorFlag(at 1bit) is adapted. Then, LimitErrorFlag is used in modeStatus, dataQuality in
scanStatus Group picks it up consequently.
The values are
Bit Meaning
0 : noise power limit error
1 : binEllipsoid is missing
2 : Spare (always 0)
3 : Spare (always 0)
4 : Spare (always 0)
5 : Spare (always 0)
6 : Spare (always 0)
7 : Spare (always 0)
(13) FractionalGranuleNumber
Type Array Unit
The floating point granule number. The granule begins at the Southern-most point of the
spacecraft’s trajectory. For example, FractionalGranuleNumber = 10.5 means the spacecraft is
halfway through granule 10 and starting the descending half of the granule. Values range from 0 to
100000. In Near Real Time (NRT) process, granule number is stored only ‘0’, so Fractional Granule
Number less than 1.0.
Missing value:
N/A
40
2.2 Data Group
2.2.8 navigation (Group)
(1) scPos
Type Array Unit
The position vector(m) of the spacecraft in Earth-Centered Earth Fixed (ECEF) Coordinates at the
Scan mid-Time (i.e., time at the middle pixel/IFOV of the active scan period). Values range from
-10000000 to 10000000 m.
Missing value:
-9999.9
(2) scVel
Type Array Unit
The velocity vector (m/s) of the spacecraft in ECEF Coordinates at the Scan mid-Time.Values
range from -10000000 to 10000000 m/s.
Missing value:
-9999.9
(3) scLat
Type Array Unit
The geodesic latitude (decimal degrees) of the spacecraft at the Scan mid-Time. Values range from
-70 to 70 degrees.
Missing value:
-9999.9
(4) scLon
Type Array Unit
The geodesic longitude (decimal degrees) of the spacecraft at the Scan mid-Time. Values range
from -180 to 180 degrees.
Missing value:
-9999.9
41
2.2 Data Group
2.2.8 navigation (Group)
(5) scAlt
Type Array Unit
The altitude (m) of the spacecraft above the Earth Ellipsiod at the Scan mid-Time. It is computed
by GeoTK. Values range from 350000 to 500000 m.
Missing value:
-9999.9
(6) dprAlt
Type Array Unit
The altitude (m) of the spacecraft above the Earth Ellipsiod at the Scan mid-Time from DPR
science telemetry. This is empty in non-DPR products. It is stored ‘GPS Altitude Data’ with LSB
equal to 10m in DPR science telemetry.Values range from 350000 to 500000 m.
Missing value:
-9999.9 : at missing scan and internal calibration mode.
(7) scAttRollGeoc
Type Array Unit
The geocentric satellite attitude Euler roll angle (degrees) at the Scan mid-Time. The order of the
components in the file is roll, pitch, and yaw. However, the angles are computed using a 3-2-1 Euler
rotation sequence representing the rotation order yaw, pitch, and roll for the rotation from Orbital
Coordinates to the spacecraft body coordinates. Orbital Coordinates represent an orthogonal triad in
Geocentric Inertial Coordinates where the Z-axis is toward the geocentric nadir, the Y-axis is
perpendicular to the spacecraft velocity opposite the orbit normal direction, and the X-axis is
approximately in the velocity direction for a near circular orbit. Note this is geocentric, not geodetic,
referenced, so that pitch and roll will have twice orbital frequency components due to the onboard
control system following the oblate geodetic Earth horizon. Note also that the yaw value will show
an orbital frequency component relative to the Earth fixed ground track due to the Earth rotation
relative to inertial coordinates. Values range from -180 to 180 degrees.
Missing value:
-9999.9
42
2.2 Data Group
2.2.8 navigation (Group)
(8) scAttPitchGeoc
Type Array Unit
The geocentric satellite attitude Euler pitch angle (degrees) at the Scan mid-Time.Values range
from -180 to 180 degrees.
Missing value:
-9999.9
(9) scAttYawGeoc
Type Array Unit
The geocentric satellite attitude Euler yaw angle (degrees) at the Scan mid-Time. Values range
from -135 to 225 degrees.
Missing value:
-9999.9
(10) scAttRollGeod
Type Array Unit
The geodetic satellite attitude Euler roll angle (degrees) at the Scan mid-Time. The order of the
components in the file is roll, pitch, and yaw. However, the angles are computed using a 3-2-1 Euler
rotation sequence representing the rotation order yaw, pitch, and roll for the rotation from Geodetic
Coordinates to the spacecraft body coordinates. Geodetic Coordinates represent an orthogonal triad
in Geocentric Inertial Coordinates where the Z-axis is toward the geodetic nadir, the Y-axis is
perpendicular to the spacecraft velocity opposite the orbit normal direction, and the X-axis is
approximately in the velocity direction for a near circular orbit. Values range from -180 to 180
degrees.
Missing value:
-9999.9
(11) scAttPitchGeod
Type Array Unit
The geodedic satellite attitude Euler pitch angle (degrees) at the Scan mid-Time.Values range from
-180 to 180 degrees.
Missing value:
-9999.9
43
2.2 Data Group
2.2.8 navigation (Group)
(12) scAttYawGeod
Type Array Unit
The geodedic satellite attitude Euler yaw angle (degrees) at the Scan mid-Time. Values range from
-135 to 225 degrees.
Missing value:
-9999.9
(13) greenHourAng
Type Array Unit
The rotation angle (degrees) from Geocentric Inertial Coordinates to Earth Fixed Coordinates.
Values range from 0 to 390 degrees.
Missing value:
-9999.9
(14) timeMidScan
Type Array Unit
The Scan mid-Time in GPS Atomic time, namely the seconds since 0000 UTC,6 Jan
1980.timeMidScan is used as the reference time for the scPos and scVel values. Values range from 0
to 10000000000 s.
Missing value:
-9999.9
(15) timeMidScanOffset
Type Array Unit
Offset from the secondary header packet time to the timeMidScan.Values range from 0 to 100 s.
Missing value:
-9999.9
44
2.2 Data Group
2.2.9 rayPointing (Group)
(1) rayDirectionX
Type Array Unit
Unit ray direction x component in mechanical coordinates. Values range from -1.0 to 1.0.
Missing value:
N/A
(2) rayDirectionY
Type Array Unit
Unit ray direction y component in mechanical coordinates. Values range from -1.0 to 1.0.
Missing value:
N/A
(3) instrumentYaw
Type Array Unit
Yaw of mechanical coordinates with reference to geodetic coordinates. Values range from -135 to
225 degrees.
Missing value:
-9999.9
(4) instrumentPitch
Type Array Unit
Pitch of mechanical coordinates with reference to geodetic coordinates. Values range from -90 to
90 degrees.
Missing value:
-9999.9
45
2.2 Data Group
2.2.10 HouseKeeping (Group)
(5) instrumentRoll
Type Array Unit
Roll of mechanical coordinates with reference to geodetic coordinates. Values range from -180 to
180 degrees.
Missing value:
-9999.9
(6) rayTiming
Type Array Unit
The time delay from the secondary header packet time tag to each ray (assumed as midtime of all
radar pulses for the associated rayDirection). Values range from 0 to 1.6 s.
Missing value:
N/A
(7) scanAngle
Type Array Unit
Angle (degrees) of the ray from nominal nadir offset about the mechanical x axis. The sign of
the angle is consistent with the sensor y-axis, i.e., the angle is positive to the right of the direction of
travel if the spacecraft is in normal mode.
Missing value:
N/A
(1) rxAtt
Type Array Unit
46
2.2 Data Group
2.2.10 HouseKeeping (Group)
(2) rxAttGainOffset
Type Array Unit
(3) binDiffPeakDEM
Type Array Unit
It is the number of difference for range bin between “binEchoPeak” and “binDEM”. It is used to
ensure that the VPRF is switched in accordance with the GPM satellite altitude. Values range from
-260 to 260 range bin number at NS and MS, from -130 to 130 range bin number at HS respectively.
Missing value:
-9999 : at missing scan and internal calibration mode.
(4) scTime
Type Array Unit
It is expressed as TAI time with epoch of 0000Z Jan 6, 1980. This time is space craft clock time
for N scan in secondary header.
Missing value:
N/A
(5) vprfTableVersion
Type Array Unit
47
2.2 Data Group
2.2.10 HouseKeeping (Group)
(6) vprfTableSelect
Type Array Unit
vprfTableSelect is the selected number of VPRF table for altitude which is used in L1B process.
The range is 1 to 25.
Missing value:
-99 : at missing scan and internal calibration mode.
48
2.2 Data Group
2.2.10 HouseKeeping (Group)
under 396.5 1
396.5 ~ under 397.5 2
397.5 ~ under 398.5 3
398.5 ~ under 399.5 4
399.5 ~ under 400.5 5
400.5 ~ under 401.5 6
401.5 ~ under 402.5 7
402.5 ~ under 403.5 8
403.5 ~ under 404.5 9
404.5 ~ under 405.5 10
405.5 ~ under 406.5 11
406.5 ~ under 407.5 12
407.5 ~ under 408.5 13
408.5 ~ under 409.5 14
409.5 ~ under 410.5 15
410.5 ~ under 411.5 16
411.5 ~ under 412.5 17
412.5 ~ under 413.5 18
413.5 ~ under 414.5 19
414.5 ~ under 415.5 20
415.5 ~ under 416.5 21
416.5 ~ under 417.5 22
417.5 ~ under 418.5 23
418.5 ~ under 419.5 24
419.5 and over 25
49
2.2 Data Group
2.2.10 HouseKeeping (Group)
(7) catchingInt
Type Array Unit
The timing that receive window is open for the first reflected TX pulse. If catchingInt is set “12”,
then the first TX pulse is received with receive window after the 12th TX pulse.
In the case of nominal operation, catchingInt is adapted “12”, that is, VPRF table is adapted.
Another case, which may be GPS Status trouble situation, it is set “8” and limited PRF is loaded.
Missing values are defined as:
-99 at missing scan and internal calibration mode.
(8) scdpFlag
Type Array Unit
scdpFlag shows the flag information of A side or B side of the system control/data processing
(SCDP) system.
Bit Meaning
0 : 0 : SCDP A-side、1:SCDP B-side
1 : Priority is 1 at Basic System Table. Refer to Basic System Table.
2 : Priority is 2 at Basic System Table. Refer to HK telemetry.
3 : Priority is 2 at Basic System Table. Refer to Basic System Table.
4 : (spare)
5 : (spare)
6 : (spare)
7 : (spare)
50
2.2 Data Group
2.2.10 HouseKeeping (Group)
(9) fcifFlag
Type Array Unit
(10) logAmpNoiseLevel
Type Array Unit
It is the Noise Level at Log Amp Termination which is stored in science telemetry.
Missing value:
-9999 : at missing scan and internal calibration mode.
(11) delay
Type Array Unit
It is the timing offset value from space craft time in NS. In MS and HS, it is defined as offset time
value from the base delay time. They are used to adjust for beam matching of along track direction.
Values range from 0 to 3360 Number.
Missing value:
N/A
51
2.2 Data Group
2.2.10 HouseKeeping (Group)
(12) seqCountL1A
Type Array Unit
It is the scan number which is determined by the L1A product.Values range from 1 to 27000
counts.
Missing value:
-9999
(13) fcifTemp
Type Array Unit
The temperature of FCIF component, which is averaged during about 3 minutes. The first
dimension is temperature and the other is the number of referenced HK telemetry. Temperature
values are multiplied by 100 and stored as a 2 byte integer. The range is -50C to 50C which
correspond to values from -5000 to 5000.
Missing value:
-9999
(14) lnaTemp
Type Array Unit
The temperature of LNA component, which is averaged during about 3 minutes. The first
dimension is temperature and the other is the number of referenced HK telemetry. Temperature
values are multiplied by 100 and stored as a 2 byte integer. The range is -50C to 50C which
corresponds to values from -5000 to 5000.
Missing value:
-9999
52
2.2 Data Group
2.2.10 HouseKeeping (Group)
(15) rdaTemp
Type Array Unit
The temperature of RDA component, which is averaged during about 3 minutes. The first
dimension is temperature and the other is the number of referenced HK telemetry. Temperature
values are multiplied by 100 and stored as a 2 byte integer. The range is -50C to 50C which
correspond to values from -5000 to 5000.
Missing value:
-9999
(16) divcomb1Temp
Type Array Unit
The temperature of divcomb1, which is averaged during about 3 minutes.The first dimension is
temperature and the other is the number of referenced HK telemetry. Temperature values are
multiplied by 100 and stored as a 2 byte integer.The range is -50C to 50C which correspond to values
from -5000 to 5000.
Missing value:
-9999
(17) divcomb2Temp
Type Array Unit
The temperature of divcomb2, which is averaged during about 3 minutes.The first dimension is
temperature and the other is the number of referenced HK telemetry. Temperature values are
multiplied by 100 and stored as a 2 byte integer. The range is -50C to 50C which correspond to
values from -5000 to 5000.
Missing value:
-9999
53
2.2 Data Group
2.2.10 HouseKeeping (Group)
(18) sspaTemp
Type Array Unit
The temperature of RDA component, which is averaged during about 3 minutes. The first
dimension is temperature and the other is the number of referenced HK telemetry. Temperature
values are multiplied by 100 and stored as a 2 byte integer. The range is -50C to 50C which
correspond to values from -5000 to 5000.
Missing value:
-9999
(19) rxGain
Type Array Unit
(20) scdpFlagAB
Type Array Unit
The scdpFlagAB includes information for flag of the SCDP A or SCPD B only.
-99: missing
Bit Meaning
0: SCDP A side is selected.
1: SCDP B side is selected.
(21) fcifFlagAB
Type Array Unit
The fcifFlagAB includes information for flag of the FCIF A or FCIF B only.
-99: missing
The values of the flag are:
0 : FCIF A side is selected.
1: FCIF B side is selected.
54
2.2 Data Group
2.2.11 Calibration (Group)
(1) fcifInPower
Type Array Unit
It is input power value of FCIF and is set at internal calibration mode. At another mode, the value
of fcifInPower is set as missing.
Missing value:
-30000: except internal calibration mode.
(2) intAttSelect
Type Array Unit
It is the selected number of internal attenuation that is controlled automatically with 32 steps and is
set by internal mode. At another mode, the value of fcifInPower is set as missing. Values range from
1 to 32 Number.
Missing value:
-99 : except internal calibration mode.
55
2.2 Data Group
2.2.11 Calibration (Group)
(3) sspaLnaSelect
Type Array Unit
In the case of SSPA mode, it is stored number of LNA. On the other hand, in the case of LNA
mode, it is stored the number of SSPA. At the other modes, missing value is stored. Values range
from 1 to 128 Number.
Missing value:
-9999 : except SSPA and LNA analysis mode.
(4) angleBinSelect
Type Array Unit
It is the selected beam number used SSPA and LNA analysis mode. In case of another operational
mode, the value of angleBinSelect is set as missing. Values range from 1 to 49 Number.
Missing value:
-99 : except SSPA and LNA analysis mode.
56
3 The List of Elements of the Data Group
57
3.1 The List of Elements of NS Data Group of 1BKu and 1BPR
58
3.1 The List of Elements of NS Data Group of 1BKu and 1BPR
59
3.1 The List of Elements of NS Data Group of 1BKu and 1BPR
sidelobeRange signed
[nray][nscan] 2B int
ellipsoidBinOffset 4B float
[nray][nscan]
rangeBinSize [m] 4B float
[nscan]
ratioLand signed
[nray][nscan] 1B int
ratioOcean signed
[nray][nscan] 1B int
ratioInLand signed
[nray][nscan] 1B int
ratioCoast signed
[nray][nscan] 1B int
scanStatus dataQuality signed
[nscan] 1B int
dataWarning signed
[nscan] 1B int
missing signed
[nscan] 1B int
modeStatus signed
[nscan] 1B int
geoError signed
[nscan] 2B int
geoWarning signed
[nscan] 2B int
Scorientation -9999
[nscan]
operationalMode 1 20 signed
[nscan] 1B int
limitErrorFlag signed
[nscan] 1B int
60
3.1 The List of Elements of NS Data Group of 1BKu and 1BPR
61
3.1 The List of Elements of NS Data Group of 1BKu and 1BPR
fcifFlag 0 1 signed
[nscan] 1B int
fcifFlagAB -99 0 1 signed
[nscan] 1B int
rxGain -9999.9 4B float
[nray][nscan]
scdpFlagAB -99 0 1 signed
[nscan] 1B int
logAmpNoiseLevel -9999 [dBm] signed
[nscan] 2B int
Delay -9999 0 3360 signed
[nscan] 2B int
seqCountL1A -9999 0 27000 signed
[nscan] 2B int
fcifTemp -9999 -5000 5000 [C] signed
[2 x nscan] 2B int
lnaTemp -9999 -5000 5000 [C] signed
[2 x nscan] 2B int
rdaTemp -9999 -5000 5000 [C] signed
[ 2x nscan] 2B int
divcomb1Temp -9999 -5000 5000 [C] signed
[2 x nscan] 2B int
divcomb2Temp -9999 -5000 5000 [C] signed
[2 x nscan] 2B int
sspaTemp -9999 -5000 5000 [C] signed
[2 x nscan] 2B int
Calibration fcifInPower -32734 [dBm] signed
[nscan] 2B int
62
3.1 The List of Elements of NS Data Group of 1BKu and 1BPR
63
3.2 The List of Elements of MS Data Group of 1BKa
64
3.2 The List of Elements of MS Data Group of 1BKa
65
3.2 The List of Elements of MS Data Group of 1BKa
sidelobeRange signed
[nrayMS][nscan] 2B int
ellipsoidBinOffset 4B float
[nrayMS][nscan]
rangeBinSize [m] 4B float
[nscan]
ratioLand signed
[nrayMS][nscan] 1B int
ratioOcean signed
[nrayMS][nscan] 1B int
ratioInLand signed
[nrayMS][nscan] 1B int
ratioCoast signed
[nrayMS][nscan] 1B int
scanStatus dataQuality signed
[nscan] 1B int
dataWarning signed
[nscan] 1B int
missing signed
[nscan] 1B int
modeStatus signed
[nscan] 1B int
geoError signed
[nscan] 2B int
geoWarning signed
[nscan] 2B int
SCorientation -9999 signed
[nscan] 2B int
pointingStatus -9999 signed
[nscan] 2B int
acsModeMidScan signed
[nscan] 1B int
targetSelectionMidScan -99 signed
[nscan] 1B int
operationalMode 1 20 signed
[nscan] 1B int
limitErrorFlag signed
[nscan] 1B int
66
3.2 The List of Elements of MS Data Group of 1BKa
67
3.2 The List of Elements of MS Data Group of 1BKa
68
3.2 The List of Elements of MS Data Group of 1BKa
69
3.3 The List of Elements of HS Data Group of 1BKa
echoCount 0 unsigned
[nbinHS][nrayHS][nscan] 1B int
70
3.3 The List of Elements of HS Data Group of 1BKa
71
3.3 The List of Elements of HS Data Group of 1BKa
mainlobeEdge signed
[nrayHS][nscan] 2B int
sidelobeRange signed
[nrayHS][nscan] 2B int
ellipsoidBinOffset 4B float
[nrayHS][nscan]
ratioLand signed
[nrayHS][nscan] 1B int
ratioOcean signed
[nrayHS][nscan] 1B int
ratioInLand signed
[nrayHS][nscan] 1B int
ratioCoast signed
[nrayHS][nscan] 1B int
dataWarning signed
[nscan] 1B int
missing signed
[nscan] 1B int
modeStatus signed
[nscan] 1B int
geoError signed
[nscan] 2B int
geoWarning signed
[nscan] 2B int
SCorientation -9999 signed
[nscan] 2B int
pointingStatus -9999 signed
[nscan] 2B int
72
3.3 The List of Elements of HS Data Group of 1BKa
acsModeMidScan signed
[nscan] 1B int
limitErrorFlag signed
[nscan] 1B int
73
3.3 The List of Elements of HS Data Group of 1BKa
74
3.3 The List of Elements of HS Data Group of 1BKa
75
Index
76
dielectricConstantKa ............................................... 18
1 dielectricConstantKu ............................................... 17
divcomb1Temp ......................................53, 62, 68, 75
1BKa ................................................. 2, 4, 18, 64, 70
divcomb2Temp ......................................53, 62, 68, 75
1BKu ....................................................... 2, 3, 18, 58
DOI ....................................................................... 12
DOIauthority .......................................................... 12
A DOIshortName ....................................................... 12
dprAlt ...................................................42, 61, 67, 73
acsModeMidScan.................................. 38, 60, 66, 73
DPRKaInfo ............................................................ 18
AlgorithmID ..................................................... 12, 16
DPRKuInfo ............................................................ 18
AlgorithmVersion ................................................... 12
alignmentAngleBasicEtoA ....................................... 18
alignmentAngleOffsetAtoM ..................................... 18 E
alongTrackBeamWidth .......................... 30, 59, 65, 72
echoCount .............................................24, 58, 64, 70
angleBinSelect ...................................... 56, 63, 69, 75
echoHighResBinNumber ........................28, 59, 65, 71
AttitudeFileName.................................................... 14
echoLowResBinNumber .........................28, 59, 65, 71
AttitudeSource ........................................................ 15
echoPower ............................................23, 30, 58, 64
echoSampleNumber ...............................25, 58, 64, 70
B ellipsoidBinOffset ..................................31, 60, 66, 72
EmptyGranule ........................................................ 13
binDEM ......................................... 29, 47, 59, 65, 71
EndianType ............................................................ 16
binDEMHbottom .................................. 30, 59, 65, 71
EphemerisFileName ................................................ 14
binDEMHtop ........................................ 29, 59, 65, 71
EphemerisSource .................................................... 15
binDiffPeakDEM .................................. 47, 62, 68, 74
eqvWavelength ....................................................... 18
binEchoPeak................................... 30, 47, 59, 65, 71
binEllipsoid ...............................28, 31, 40, 59, 65, 71
BlueprintFilename................................................... 16 F
BlueprintVersion..................................................... 16
fcifFlag .................................................51, 62, 68, 74
fcifFlagAB ............................................54, 62, 68, 74
C fcifInPower ...........................................55, 62, 68, 75
fcifIoTableVersion .................................................. 18
Calibration ................................10, 39, 55, 62, 68, 75
fcifTemp ...............................................52, 62, 68, 74
catchingInt ........................................... 50, 62, 68, 74
FileHeader ............................................................. 12
crossTrackBeamWidth .......................... 30, 59, 65, 72
FileInfo .................................................................. 16
FileName ............................................................... 12
D FirstScanLat ........................................................... 17
FirstScanLon .......................................................... 17
DataFormatVersion ................................................. 16
FormatPackage ....................................................... 16
dataQuality ..........................33, 35, 36, 40, 60, 66, 72
FractionalGranuleNumber.......................40, 60, 66, 73
dataWarning ......................................... 33, 60, 66, 72
DayOfMonth ........................................ 21, 58, 64, 70
DayOfYear ........................................... 22, 58, 64, 70
G
delay .................................................... 46, 51, 68, 74
GenerationDateTime ......................................... 13, 14
DEMHmean ......................................... 29, 59, 65, 71
77
GeoControlFileName .............................................. 14 limitErrorFlag ..................................34, 40, 60, 66, 73
geoError ......................................... 33, 35, 60, 66, 72 lnaTemp ................................................52, 62, 68, 75
GeoToolkitVersion.................................................. 15 logAmpNoiseLevel ................................51, 62, 68, 74
geoWarning .................................... 33, 36, 60, 66, 72 logAveOffset .......................................................... 18
GranuleFirstScanUTCDateTime ............................... 17 Longitude........................................17, 20, 23, 58, 64
GranuleLastScanUTCDateTime ............................... 17 LongitudeOnEquator ............................................... 14
GranuleNumber ...................................................... 13
GranuleStart ........................................................... 13 M
greenHourAng ...................................... 44, 61, 67, 73
mainlobeEdge ........................................31, 59, 65, 72
H MaximumNumberScansTotal ................................... 19
MeanSolarBetaAngle .............................................. 14
Hour .................................................... 21, 58, 64, 70 MetadataStyle ......................................................... 16
HouseKeeping ................................ 10, 46, 62, 68, 74 MetadataVersion ..................................................... 16
HS ........................................................................... 2 MilliSecond...........................................22, 58, 64, 70
Minute ..................................................22, 58, 64, 70
78
O scAttRollGeod .......................................43, 61, 67, 73
scAttYawGeoc ......................................43, 61, 67, 73
operationalMode ............................................... 34, 39 scAttYawGeod ......................................44, 61, 67, 73
scdpFlag ...............................................50, 62, 68, 74
radarTransPower ................................... 25, 59, 65, 71 scVel ..............................................41, 44, 61, 67, 73
S T
scAttPitchGeoc ..................................... 43, 61, 67, 73 Transmitter ........................................6, 25, 59, 65, 71
79
txAntGain ............................................ 27, 59, 65, 71 vprfTableSelect ...............................48, 49, 62, 68, 74
vprfTableVersion ...................................47, 62, 68, 74
U
Y
UTCDateTimeOnEquator ........................................ 14
Year .....................................................21, 58, 64, 70
80