majorversionnumber:
Major version number of the LITE Level 1 data. It is used to identify format revisions.
Units: none, Range: 1 - 10, Size in bytes: 1.
minorversionnumber:
Minor version number of the LITE level 1 data. It is used to identify parameter or data revisions.
Units: none, Range: 1 - 10, Size in bytes: 1.
datatakeid:
Datatake (A to Z) or Snapshot ID (SS001 to SS100).
Units: none, Range: 32 - 127, Size in bytes: 7.
orbitnumber:
Orbit number.
Units: none, Range: 5 - 150, Size in bytes: 1.
idnumber:
ID number assigned to the laser shot. This value was assigned during post processing and does not
correspond to the number of the actual laser shot.
Units: none, Range: 1000001 - 99023743, Size in bytes: 4.
gmtday:
Day, Greenwich Mean Time.
Units: days, Range: 245 - 262, Size in bytes: 2.
gmthour:
Hour, Greenwich Mean Time.
Units: hours, Range: 0 - 23, Size in bytes: 1.
gmtmin:
Minute, Greenwich Mean Time.
Units: minutes, Range: 0 - 59, Size in bytes: 1.
gmtsec:
Second, Greenwich Mean Time. The number of seconds is gmtsec + 0.01*gmthund.
Units: seconds, Range: 0 - 59, Size in bytes: 1.
gmthund:
Hundredth of a second, Greenwich Mean Time. The number of seconds is gmtsec + 0.01*gmthund.
Units: hundredth of second, Range: 0 - 99, Size in bytes: 1.
metday:
Day, Mission Elapsed Time.
Units: none, Range: 0 - 9, Size in bytes: 2.
methour:
Hour, Mission Elapsed Time.
Units: none, Range: 0 - 23, Size in bytes: 1.
metmin:
Minute, Mission Elapsed Time.
Units: none, Range: 0 - 59, Size in bytes: 1.
metsec:
Second, Mission Elapsed Time. The number of seconds is metsec + 0.01*methund.
Units: none, Range: 0 - 59, Size in bytes: 1.
methund:
Hundredth of a second, Mission Elapsed Time. The number of seconds is metsec + 0.01*methund.
Units: none, Range: 0 - 99, Size in bytes: 1.
latitude:
Geodetic latitude of LITE footprint.
Refer to Locating the LITE Footprint to Earth Coordinates.
Units: degrees, Range: -59.0 - 59.0, Size in bytes: 4.
longitude:
Longitude of LITE footprint.
Refer to Locating the LITE Footprint to Earth Coordinates.
Units: degrees, Range: -179.9999 - 179.9999, Size in bytes: 4.
shuttlealtitude:
Shuttle altitude. Normally, the Shuttle altitude is the measured perpendicular distance from the Shuttle to a
point on the surface of the reference geoid. The Shuttle altitude in the Level 1 data is the distance as
described above plus a small extension so that a right triangle with the LITE vector as the hypotenuse can be formed.
The LITE vector is a vector along the LITE laser beam that extends from the center of the Shuttle cargo bay
to the surface of the reference geoid. The length is the distance from the Shuttle to the point where the
LITE vector intersects the surface of the reference geoid.
Refer to Locating the Space Shuttle to Earth Coordinates.
Refer to the Range Calculation Document
for a description of how Shuttle altitude, off-nadir angle, and the LITE altitude grid are used in range calculations.
Units: km, Range: 238.0 - 276.0, Size in bytes: 4.
offnadirangle:
Off-nadir angle. This is the angle between the LITE vector and the
perpendicular from the Shuttle to the surface of the reference geoid.
Refer to Locating the LITE Footprint to Earth Coordinates.
Refer to the Range Calculation Document
for a description of how Shuttle altitude, off-nadir angle, and the LITE altitude grid are used in range calculations.
Units: degrees, Range: 0.0 - 53.0, Size in bytes: 4.
digitizerondelay:
The time delay between the 10 Hz clock pulse and the start of digitizing. The digitizer-on delay begins
with the 10 Hz clock pulse, which precedes the laser firing by 200.26 microseconds for laser A and 200.28
microseconds for laser B.
Refer to the Range Calculation Document
for a description of how Shuttle altitude, off-nadir angle, and the LITE altitude grid are used in range calculations.
Units: microseconds, Range: 1280.0 - 1727.0, Size in bytes: 4.
datatakemode:
Datatake mode flag, 0 = day, 1 = night.
Units: none, Range: 0 - 1, Size in bytes: 1.
specialopsmode:
Special operation mode flag, 0 = normal, 1 = multiscatter, 2 = gain change, 3 = mode transition.
Units: none, Range: 0 - 3, Size in bytes: 1.
profilevalidstatus:
Profile [valid/questionable/invalid] flag, 0 = valid, 1 = 355 questionable, 2 = 532 questionable,
4 = 1064 questionable, 8 = 355 invalid, 16 = 532 invalid, 32 = 1064 invalid.
Profiles may be questionable due to bad ISDB/AOE data, boresight not aligned, 355 or 532 nm high voltage
greater than -1000, 1064 nm high voltage greater than -399, or underflow occurred in baseline subtraction region.
Profiles may be invalid due to motor/wheel/filter motion, aperture wheel in closed position, high voltage
disabled, or the number of saturated counts in a profile are greater than 460.
The value of this flag results from an "or" operation.
Refer to the Profile Validity Document for instructions to unpack this parameter.
landwaterflag:
Land/Water flag. 0 = land, 1 = water.
Units: none, Range: 0 - 1, Size in bytes: 2.
surfelevfootprint:
Surface elevation at footprint location.
The U.S. Geological Survey GTOPO30, Global 30 Arc Second Elevation Data Set, was source of global elevation data.
htt../edcwww.cr.usgs.gov/landdaac/gtopo30/gtopo30.html.
Units: km, Range: 0.0 - 8.0, Size in bytes: 4.
metdataalts:
Altitudes that correspond to the 18 standard pressure levels (1000, 850, 700, 500, 400, 300, 250, 200, 150,
100, 70, 50, 30, 10, 5, 2, 1, and 0.4 mb).
Units: km, Range: 0.0 - 56.0, Size in bytes: 72.
mettemps:
NMC Temperatures recorded at the 18 standard pressure levels described above.
Units: Kelvin, Range: 0.0 - 319.0, Size in bytes: 72.
alttropopause:
NMC tropopause height.
Units: km, Range: 6.0 - 17.0, Size in bytes: 4.
temptropopause:
NMC tropopause temperature.
Units: Kelvin, Range: 190.0 - 238.0, Size in bytes: 4.
laserselected:
Laser in use flag, 0 = A, 1 = B.
Units: none, Range: 0 - 1, Size in bytes: 1.
baalignmentstatus:
Boresight aligned flag, 0 = not aligned, 1 = aligned.
Units: none, Range: 0 - 1, Size in bytes: 1.
isdbstatus:
ISDB validity flag, 0 = invalid, 1 = valid. Invalid means that ISDB values from a previous time were used
or values in the ISDB were out of range. The profiles may be valid, but information obtained from the ISDB
may be questionable.
Units: none, Range: 0 - 1, Size in bytes: 1.
badatastatus:
Boresight assembly data status flag, 0 = invalid, 1 = valid. If invalid, then the profile validity is questionable.
Units: none, Range: 0 - 1, Size in bytes: 1.
aoedatastatus:
Aft-optics data status flag, 0 = invalid, 1 = valid. If invalid, then information stored in the following
locations were obtained from a previous AOE status report:motor motion, aperture wheel status, background
monitor gain, attenuation setting, filter status, background value, high voltage enabled, high voltage,
energy monitor, and PMT gain.
Units: none, Range: 0 - 1, Size in bytes: 1.
motorinmotion:
Motor [no motion/motion] flag, 0 = no motion, 1 = motion.
Units: none, Range: 0 - 1, Size in bytes: 1.
aperwheelstatus:
Aperture wheel status flag, 0 = closed, 1 = large, 2 = annular, 3 = small, 4 = in motion.
Units: none, Range: 0 - 4, Size in bytes: 1.
backgroundmongain:
Background monitor gain setting [day/night] flag, 0 = day, 1 = night.
Units: none, Range: 0 - 1, Size in bytes: 1.
surfacemode355:
Surface mode configuration flag, 0 = not surface mode, 1 = in transition in or out of surface mode, 2 = in surface mode.
Refer to the plot showing the locations where surface mode is set.
Units: none, Range: 0 - 2, Size in bytes: 1.
dbattenuation355:
Attenuation setting. The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: db, Range: 0 - 49, Size in bytes: 1.
numbersatabovesurf355:
Number of saturated values above the surface.
Units: none, Range: 0 - 3000, Size in bytes: 2.
highestsatsample355:
Altitude of highest saturated sample.
Units: km, Range: -5.0 - 40.0, Size in bytes: 4.
numberunderflows355:
Number of underflow occurrences in profile between -5.0 to 40.0 km.
Units: none, Range: 0 - 3000, Size in bytes: 2.
filterstatus355:
Filter status [out/in/in motion] flag. 0 = out, 1 = in, 2 = in motion.
Units: none, Range: 0 - 2, Size in bytes: 1.
calibrationstatus355:
Calibration status flag, 0 = estimated, 1 = calculated, 2 = not available.
Units: none, Range: 0 - 2, Size in bytes: 1.
calibrationfactor355:
Calibration factor.
Units: none, Range: 1.0e+04 - 1.0e+16, Size in bytes: 4.
baselinerippleremvd355:
Fixed phase baseline ripple removal flag, 0 = not removed, 1 = removed.
Units: none, Range: 0 - 1, Size in bytes: 1.
osbackgroundvalue355:
Random phase baseline oscillation removal flag, 0 = not removed, 1 = removed.
Units: none, Range: 0 - 1, Size in bytes: 1.
backgroundvalue355:
Background value.
Units: none, Range: 0 - 255, Size in bytes: 1.
highvoltage355enabled:
High voltage [disabled/enabled] flag, 0 = disabled, 1 = enabled.
Units: none, Range: 0 - 1, Size in bytes: 1.
highvoltage355:
Measured high voltage value.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: volts, Range: -2398.0 - -149.0, Size in bytes: 4.
energymonitor355:
Measured energy value.
Units: mjoules, Range: 0.0 - 201.0, Size in bytes: 4.
pmtgain355:
PMT gain.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: none, Range: 0.05 - 693077.85, Size in bytes: 4.
baselinesubmethod355:
Baseline method used flag, 0 = slope method, 1 = averaged signal method.
Units: none, Range: 0 - 1, Size in bytes: 1.
outofrangsubreg355:
Out of range conditions in baseline subtraction region flag, 0 = none, 1 = underflow, 2 = overflow, 3 = underflow and overflow.
Units: none, Range: 0 - 1, Size in bytes: 1.
anomalousprof355:
Anomalous profiles flag, 0 = normal, 1 = anomalous. A profile is anomalous if it originally passed all profile validity tests, but
upon visual inspection appears to be invalid or questionable.
Units: none, Range: 0 - 1, Size in bytes: 1.
fillbyte1:
Fill byte.
Units: none, Range: 0, Size in bytes: 1.
surfacemode532:
Surface mode configuration flag, 0 = not surface mode, 1 = in transition in or out of surface mode, 2 = in surface mode.
Refer to the plot showing the locations where surface mode is set.
Units: none, Range: 0 - 2, Size in bytes: 1.
dbattenuation532:
Attenuation setting. The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document .
Units: db, Range: 0 - 49, Size in bytes: 1.
numbersatabovesurf532:
Number of saturated values above the surface.
Units: none, Range: 0 - 3000, Size in bytes: 2.
highestsatsample532:
Altitude of highest saturated sample.
Units: km, Range: -5.0 - 40.0, Size in bytes: 4.
numberunderflows532:
Number of underflow occurrences in profile between -5.0 to 40.0 km.
Units: none, Range: 0 - 3000, Size in bytes: 2.
filterstatus532:
Filter status [out/in/in motion] flag. 0 = out, 1 = in, 2 = in motion.
Units: none, Range: 0 - 2, Size in bytes: 1.
calibrationstatus532:
Calibration status flag, 0 = estimated, 1 = calculated, 2 = not available.
Units: none, Range: 0 - 2, Size in bytes: 1.
calibrationfactor532:
Calibration factor.
Units: none, Range: 1.0e14 - 1.0e16, Size in bytes: 1.
baselinerippleremvd532:
Fixed phase baseline ripple removal flag, 0 = not removed, 1 = removed.
Units: none, Range: 0 - 1, Size in bytes: 1.
oscillationremoved532:
Random phase baseline oscillation removal flag, 0 = not removed, 1 = removed.
Units: none, Range: 0 - 1, Size in bytes: 1.
backgroundvalue532:
Background value.
Units: none, Range: 0 - 255, Size in bytes: 1.
highvoltage532enabled:
High voltage [disabled/enabled] flag, 0 = disabled, 1 = enabled.
Units: none, Range: 0 - 1, Size in bytes: 1.
highvoltage532:
Measured high voltage value.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: volts, Range: -1330.93 - -159.20, Size in bytes: 4.
energymonitor532:
Measured energy value.
Units: mjoules, Range: 0.0 - 201.0, Size in bytes: 4.
pmtgain532:
PMT gain.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: none, Range: 0.0 - 72582.23, Size in bytes: 4.
baselinesubmethod532:
Baseline method used flag, 0 = slope method, 1 = averaged signal method.
Units: none, Range: 0 - 1, Size in bytes: 1.
outofrangsubreg532:
Out of range conditions in baseline subtraction region flag, 0 = none, 1 = underflow, 2 = overflow, 3 = underflow and overflow.
Units: none, Range: 0 - 1, Size in bytes: 1.
anomalousprof532:
Anomalous profiles flag, 0 = normal, 1 = anomalous. A profile is anomalous if it originally passed all profile validity tests, but
upon visual inspection appears to be invalid or questionable.
Units: none, Range: 0 - 1, Size in bytes: 1.
fillbyte2:
Fill byte.
Units: none, Range: 0, Size in bytes: 1.
surfacemode064:
Surface mode configuration flag, 0 = not surface mode, 1 = in transition in or out of surface mode, 2 = in surface mode.
Refer to the plot showing the locations where surface mode is set.
Units: none, Range: 0 - 2, Size in bytes: 1.
dbattenuation064:
Attenuation setting. The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: db, Range: 0 - 49, Size in bytes: 1.
numbersatabovesurf064:
Number of saturated values above the surface.
Units: none, Range: 0 - 3000, Size in bytes: 2.
highestsatsample064:
Altitude of highest saturated sample.
Units: km, Range: -5.0 - 40.0, Size in bytes: 4.
numberunderflows064:
Number of underflow occurrences in profile between -5.0 to 40.0 km.
Units: none, Range: 0 - 3000, Size in bytes: 2.
filterstatus064:
Filter status [out/in/in motion] flag. 0 = out, 1 = in, 2 = in motion.
Units: none, Range: 0 - 2, Size in bytes: 1.
calibrationstatus064:
Calibration status flag, 0 = estimated, 1 = calculated, 2 = not available.
Units: none, Range: 0 - 2, Size in bytes: 1.
calibrationfactor064:
Calibration factor.
Units: none, Range: 1.0e14 - 1.0e16, Size in bytes: 4.
baselinerippleremvd064:
Fixed phase baseline ripple removal flag, 0 = not removed, 1 = removed.
Units: none, Range: 0 - 1, Size in bytes: 1.
oscillationremoved064:
Random phase baseline oscillation removal flag, 0 = not removed, 1 = removed.
Units: none, Range: 0 - 1, Size in bytes: 1.
backgroundvalue064:
Background value.
Units: none, Range: 0 - 255, Size in bytes: 1.
highvoltage064enabled:
High voltage [disabled/enabled] flag, 0 = disabled, 1 = enabled.
Units: none, Range: 0 - 1, Size in bytes: 1.
highvoltage064:
Measured high voltage value.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: volts, Range: -436.4 - -371.1, Size in bytes: 4.
energymonitor064:
Measured energy value.
Units: mjoules, Range: 0.0 - 201.0, Size in bytes: 4.
apdgain064:
APD gain.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: none, Range: 75.0, Size in bytes: 4.
baselinesubmethod064:
Baseline method used flag, 1 = averaged signal method.
Units: none, Range: 1, Size in bytes: 1.
outofrangsubreg064:
Out of range conditions in baseline subtraction region flag, 0 = none, 1 = underflow, 2 = overflow, 3 = underflow and overflow.
Units: none, Range: 0 - 1, Size in bytes: 1.
anomalousprof064:
Anomalous profiles flag, 0 = normal, 1 = anomalous. A profile is anomalous if it originally passed all profile validity tests, but
upon visual inspection appears to be invalid or questionable.
Units: none, Range: 0 - 1, Size in bytes: 1.
fillbyte3:
Fill byte.
Units: none, Range: 0, Size in bytes: 1.
timeedsinthour:
Hour, EDS Interrupt time.
Units: hours, Range: 0 - 23, Size in bytes: 1.
timeedsintmin:
Minute, EDS Interrupt time.
Units: minutes, Range: 0 - 59, Size in bytes: 1.
timeedsintsec:
Second, EDS Interrupt time.
Units: seconds, Range: 0 - 59, Size in bytes: 1.
1
timeedsinthund:
Hundredth of second, EDS Interrupt time.
Units: hundredth of a second, Range: 0 - 99, size in bytes: 1.
reserved1:
Reserved for user to define.
Units: none, Range: 0, Size in bytes: 10.
highvoltage355cmd:
Commanded high voltage value.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: volts, Range: -1719.6 - -1072.2, Size in bytes: 4.
highvoltage532cmd:
Commanded high voltage value.
The relationship between attenuation, high voltage, and gain are presented in the
Level 1 Gain Calculation Document.
Units: volts, Range: -1336.1 - -1067.2, Size in bytes: 4.
reserved2:
Reserved for user to define.
Units: none, Range: 0, Size in bytes: 4.
b0_355:
Baseline subtraction value for 355 channel.
Units: none, Range: 12345, Size in bytes: 4.
b0_532:
Baseline subtraction value for 532 channel.
Units: none, Range: 12345, Size in bytes: 4.
b0_064:
Baseline subtraction value for 1064 channel.
Units: none, Range: 12345, Size in bytes: 4.
outofrng355abv40:
355 channel overflow/underflow above 40 km flag, 0 = none, 1 = underflow, 2 = overflow, 3 = underflow and overflow.
Units: none, Range: 0 - 3, Size in bytes: 1.
outofrng532abv40:
532 channel overflow/underflow above 40 km flag, 0 = none, 1 = underflow, 2 = overflow, 3 = underflow and overflow.
Units: none, Range: 0 - 3, Size in bytes: 1.
outofrng064abv40:
1064 channel overflow/underflow above 40 km flag, 0 = none, 1 = underflow, 2 = overflow, 3 = underflow and overflow.
Units: none, Range: 0 - 3, Size in bytes: 1.
outofrange355:
Packed byte array identifying which elements in the Level 1 lidar profile were out of range before Level 1
processing was performed. Unpacking this parameter yields a 3000 element array
filled with values of zero or one indicating whether the preprocessed count values were in or out of range,
respectively. The grid locations of this array correspond to the grid locations of the Level 1 altitude array.
Units: none, Range: 0 - 1, Size in bytes: 375.
outofrange532:
Packed byte array identifying which elements in the Level 1 lidar profile were out of range before Level 1
processing was performed. Unpacking this parameter yields a 3000 element array
filled with values of zero or one indicating whether the preprocessed count values were in or out of range,
respectively. The grid locations of this array correspond to the grid locations of the Level 1 altitude array.
Units: none, Range: 0 - 1, Size in bytes: 375.
outofrange064:
Packed byte array identifying which elements in the Level 1 lidar profile were out of range before Level 1
processing was performed. Unpacking this parameter yields a 3000 element array
filled with values of zero or one indicating whether the preprocessed count values were in or out of range,
respectively. The grid locations of this array correspond to the grid locations of the Level 1 altitude array.
Units: none, Range: 0 - 1, Size in bytes: 375.
top355:
Index value of the altitude array corresponding to the highest altitude of the first valid 355 nm profile value.
Units: none, Range: 0 - 2999, Size in bytes: 2.
bot355:
Index value of the altitude array corresponding to the lowest altitude of the last valid 355 nm profile value.
Units: none, Range: 0 - 2999, Size in bytes: 2.
top532:
Index value of the altitude array corresponding to the highest altitude where the first valid 532 nm profile value begins.
Units: none, Range: 0 - 2999, Size in bytes: 2.
bot532:
Index value of the altitude array corresponding to the lowest altitude of the last valid 532 nm profile value.
Units: none, Range: 0 - 2999, Size in bytes: 2.
top064:
Index value of the altitude array corresponding to the highest altitude of the first valid 1064 nm profile value.
Units: none, Range: 0 - 2999, Size in bytes: 2.
bot064:
Index value of the altitude array corresponding to the lowest altitude of the last valid 1064 nm profile value.
Units: none, Range: 0 - 2999, Size in bytes: 2.
profile355:
LITE level 1 profile for 355 nm wavelength. Level 1 profiles are formed by removing the fixed phase
and random phase oscillations, performing offset subtraction, registering the lidar profiles to a
uniform grid from -3.985 to 40.0 km with a 15 m vertical resolution, and supplying a calibration
factor.
profiles. Fill values = 9999.0
