CCSD1Z00000100000052CCSD1R00000300000032 DELIMITER=EOF; TYPE=CCSD1F000001; CCSD1C00000400000013 ADI=NURSHR04; CCSD1R00000300000032 DELIMITER=EOF; TYPE=CCSD1D000002; HRDI DATA SET DOCUMENTATION Whole Data Set Keyword Value Description ------- ----------------- DataSetName: HRDI data files (data version 7, 8, 9, 10, 11) DataSource: Upper Atmospheric Research Satellite (UARS), High Resolution Doppler Interferometer (HRDI) ScientificContact: Scientific aspects of the data: Dr. Wilbert Skinner Space Physics Research Laboratory Space Physics Building 2455 Hayward Ann Arbor, Michigan, USA 48109-2143 HRDRAC::SKINNER (313) 747-3960 Data Generation: Dr. David A. Gell Space Physics Research Laboratory Space Physics Building 2455 Hayward Ann Arbor, Michigan, USA 48109-2143 HRDRAC::GELL (313) 763-6221 SourceCharacteristics: The UARS spacecraft has a nearly circular, 585 kilometer apogee orbit about the earth, with an inclination of roughly 57 degrees to the equatorial plane. The orbit precesses about 5 degrees per day relative to the sun, thus over a period of about 72 days the entire diurnal cycle can be sampled (for each day's worth of data, the local solar time is nearly a constant function of latitude). The satellite is yawed thru 180 degrees approximately every 36 days, in order to keep the sun on the same side of the spacecraft. With this orbit, as HRDI makes its measurements along the limb of the earth (where most of its measurements are made), the instrument should provide coverage of the earth from -75 to 75 degrees latitude in total. Since HRDI is typically viewing on only one side of the spacecraft (northward or southward) during a single orbit, the coverage it can provide is about 35 degrees smaller (typically -75 to 40 if viewing south, or -40 to 75 if viewing north). This coverage is also mitigated by the available sunlight - HRDI can provide some measurements at night, but only provides full sets of measurements during the daytime. InvestigationObjectives: The Upper Atmospheric Research Satellite (UARS), was launched in September 1991, is providing a global data set required to understand the mechanisms controlling upper atmosphere structure and processes, as well as the response of the upper atmosphere to natural and human perturbations. The High Resolution Doppler Imager (HRDI) is the primary instrument for measuring the dynamics of the stratosphere and mesosphere. The goal of HRDI is to measure wind velocities in the stratosphere, mesosphere, and lower thermosphere during the day with an accuracy of 5 m/s, and also to measure the winds in the mesosphere and lower thermosphere at night. HRDI determines winds by measuring the Doppler shifts of atmospheric absorption and emission features. Line of sight wind measurements are taken in two directions, thus allowing the wind vector to be formed. This data, when combined with data from other UARS instruments, can greatly enhance our understanding of the processes that occur in the earth's middle atmosphere. A fall 1991 launch provided coverage of two northern hemisphere winters, a key requirement of the basic mission, but interruption of data taking by HRDI from 2-June-1992 thru 22-July-1992, caused by a failure of the UARS solar array, created a significant data loss. As the UARS mission was extended, HRDI continued to provided further data. The primary products of HRDI measurements are winds in the stratosphere (10 to 40 km.), and mesosphere/lower thermosphere (50 to 125 km). Secondarily, it is possible to recover temperature, O2 atmospheric band volume emission rate, and O3 and O(1D) mixing ratios in the mesosphere and lower thermosphere, and aerosol and molecular extinction coefficients in the stratosphere. The HRDI instrument provides a wind profile measurement on the order of once per minute. During periods when the spacecraft is in darkness, wind measurements are confined to a narrow altitude band in the mesosphere/lower thermosphere, where an emission layer provides the necessary signal level to measure winds accurately. The operating mode of the instrument determines which of the other quantities are measured, and how often a measurement is made. InstrumentAttributes: The HRDI instrument is made up of several parts, including a triple etalon Fabry-Perot interferometer, a photometer, a telescope, filter wheels, and the support electronics to control the above and to record its output. Light from the atmosphere is collected by a fully gimballed telescope that allows observation of the atmosphere on either side of the spacecraft, Light enters the instrument either from the telescope or from calibration sources by positioning a scene selection mirror. The light beam is expanded and passed through a dual filter wheel. Each filter wheel can hold eight filters. These filters transmit a spectral region about 10 Angstroms wide to the instrument. Filter wavelengths available are: 5577, 6300, 6305, 6868, 6876, 6923, 6929, 7235, 7607, 7635, 7649, 7666, and 7756 Angstroms. A small fraction of the incoming light is collected by a photometer, which provides information on the brightness in the broad spectral region. The light beam is expanded again, and goes through the triple etalon interferometer, then is focussed onto the detector. The detector is a multiple anode concentric ring detector that spatially scans the dispersed spectrum in wavelength at a very high resolution. It does this by means of an anode pattern that mimics the interference pattern produced by the interferometer. This device, known as an Image Plane Detector (IPD) allows several points in a wavelength region to be monitored simultaneously (HRDI uses measurement from 31 IPD channels). The interferometers are scanned in wavelength by using piezoelectric devices to control the spacing of the etalon gap in two of the three Fabry-Perot devices. The third is spatially scanned by the multiple anode detector mentioned above. The resolution of the instrument is approximately 0.015 Angstroms. The instrument is controlled by a dedicated microprocessor. The computer is necessary to properly control the spacing of the interferometer gaps, compensate for thermal drifts, and to point the telescope. For a more complete description of the instrument, please refer to the papers 'High Resolution Doppler Imager', section 3, and 'The High Resolution Doppler Imager', section II (see later section on Literature References for full reference). HRDI measures the Doppler shift of absorption and emission lines of molecular oxygen in the atmosphere, mainly looking above the limb of the earth. Its main product, winds, are measured by finding the Doppler shift of the atmospheric lines, then adjusting this value to compensate for the velocity of the spacecraft. In a typical science operation, the telescope is pointed at a 45 (or 135) degree angle to the spacecraft (s/c) velocity vector and 'scan' up or down in tangent height altitude. The telescope pauses in its up/down motion to collect several integration periods (each is 0.125 seconds long) of data at each of several tangent points (selected heights above the limb of the earth). Different wavelength bands are used for different altitude ranges, to maximize information content in the collected signals for the altitude in question. A typical operational cycle is to scan up and down at a fixed telescope azimuth (ex. - 45 deg. with velocity vector), then slew the telescope to a new azimuth (ex. - 135 deg. with velocity vector), repeat the scan cycle, then slew back to 45 deg. to start a new cycle. This is done so that the same volume in space can be seen from two directions (looking forwards and, later, looking backwards), to allow us to form a true wind vector from the two LOS (line of sight) components. For a more complete description of the operation of the instrument, please refer to the paper 'The High Resolution Doppler Imager', section III (see later section on Literature References for full reference). When a scan of data has been accumulated, the data are analyzed by first finding the average signal in each channel at each tangent height (HRDI produces 32 channels of data, 31 from the interferometer and one from the photometer). The signal is corrected for instrument dead time, the dark counts (background) values are subtracted from the data, the signal level for each channel is converted to Rayleighs per wavenumber, and the line of sight velocity of the atmosphere is calculated using the Doppler shift of an atmospheric absorption or emission line. (Please refer to HRDI memo S-300 for a description of the algorithm for finding the center of an absorption or emission line (see later section on Literature References for full reference).) The line of sight (l.o.s.) velocity is then corrected for the spacecraft velocity, and a weighted average of the data (which may include data with different s/c velocity components, wavenumbers, and altitudes) is formed. The scan (which now consists of averaged measurements, calculated l.o.s. velocities, and the associated collection conditions for each of several tangent heights) is then written out as a Level 2A data record. The Level 2B processing software later reads this file, then analyzes the data to produce 'profiles' (measurements of various quantities (ex. wind) at each of several tangent heights in a column in a radial direction above the earth), as follows: The 'average' values for each scan are determined (latitude, longitude, time, etc.), along with the atmospheric state for the scan's location. The atmospheric state, including the temperature, pressure, O2 density, and aerosol and molecular extinction coefficients, is determined from the results of prior processing if such results are available. If prior results are not available model values are used. 'Kernels', which show how much of a single LOS measurement comes from a certain altitude along the line of sight, are calculated for each species to be recovered, and stored in a scratch file. The recovery at an individual location is inverted, and these are averaged with nearby recoveries using a sequential estimation technique to reduce noise. The profiles are then written out to the Level 2B file, processing continuing until the entire Level 2A file has been read and processed. For a more complete description of the sequential estimation process, please refer to 'A Sequential Estimation Technique for Recovering Atmospheric Data from Orbiting Satellites' (see later section on Literature References for full reference). In the Level 3 data processing software, each profile is read sequentially from the Level 2B source file, and the location, time and type (which region of the atmosphere does the profiles contain data for, and what type of data (velocity, temperature, etc.) does it contain) are stored. The sequence of profiles of each type is divided into subsequences called 'semi-orbits'. The HRDI Level 3 processing analyzes all data (for each atmospheric region and data type) for one semi-orbit at the same time, pairing profiles for different atmospheric regions (so a single Level 3A profile can represent all results in a profile above a single point (i.e. both mesospheric/lower thermospheric and stratospheric results), filling points on the standard latitude and/or time grid by interpolation, and transforming data onto a pressure grid using NMC pressure/altitude data. For a more complete description of the Level 3 processing, please refer to HRDI memo S-379 (see later section on Literature References for full reference). MeasuredParameters: The HRDI instrument measures winds in the stratosphere and mesosphere/lower thermosphere (its main products) as well as stratospheric aerosol and molecular scattering coefficients, and mesospheric/lower thermospheric O2 band volume emission rate, temperature, and O3 and O(1D) mixing ratios. The following HRDI products are available (or will soon become available) in the level 2B and level 3A formats: species units ranges winds (meridional and zonal) meters/second Approx. -300 to 300 m/s O2 band volume emission rate photons/cm**3/second 0 to 3e5 temperature degrees Kelvin 100 to 400 deg. O3 mixing ratio * unitless 1e-4 to 1e-8 O(1D) mixing ratio * unitless 1e-11 to 1e-14 molecular and aerosol km**-1 0 to .5 extinction coefficients * (* = data product not yet available) In addition to the measured parameters and their variances, the data collection conditions are included in the data set (time, location, instrument look direction, spacecraft orbital parameters, instrument operating mode, etc.). Measurements are made approximately every minute, and have 2.5 km vertical and 250 km horizontal resolutions. The measurement interval and resolution can vary according to the operational mode of the instrument. For a description of the scientific basis for HRDI measurements, please refer to the papers 'High Resolution Doppler Imager', section 2, and 'The High Resolution Doppler Imager', section I (see later section on Literature References for full reference). DataSetQuality: The instrument has undergone extensive calibration testing pre-launch, and is calibrated in orbit several times per day. Wind products from the mesosphere and lower thermosphere have been extensively validated, mainly through comparison with ground based correlative measurements. For details please refer to 'Validation of HRDI Mesospheric and Lower Thermospheric Winds', and 'Comparison of HRDI wind measurements with radar and rocket observations', (see later section on Literature References for full reference). Other data products are in the process of validation. The quality of each data value depends to a large degree on the data collection conditions (and quality) of the measurements used to create the data value. As stated above, the goal of HRDI is to measure wind velocities in the stratosphere, mesosphere, and lower thermosphere during the day with an accuracy of 5 m/s; this remains the present estimate of uncertainty in these measurements. Accuracies of the other measured quantities are as follows (where known): standard deviations on the order of 1.7x10**3 photons/cm**3 (about 3-5 percent of the measured value) for mesospheric volume emission, 6 deg for mesospheric temperature, 5-8 percent for O3 and O(1D) mixing ratios, and 5 percent for extinction coefficients. Quality flag values, in both the data itself and the UCSS database, should be consulted in evaluating data quality. The quality flags in each of the data files are: in the Level 1 data, each integration period is marked as to whether it includes fill data or parity errors; in the Level 2A data, 'bad_data' is used to flag data which did not produce valid measurements, and 's_anomaly' flags data which were taken in the south Atlantic anomaly region; the Level 2B data also include the flag 's_anomaly', as well as 'profile_quality', which describes the overall quality of the profile (how many tangent heights were used in this particular scan, and how far apart were the measurements which were used to find the profile); the Level 3 data files contain no data quality flags as such. In addition to the quality flags in each file, the UCSS database provides a UARS standard field, and a PI private field as a means for flagging the quality of each of the cataloged data files as a whole. The UARS standard flag is of the following form 'I.J' where 'I' denotes the degree to which the files has been verified (0=machine inspected, 1=qualitative evaluation, 2=extensive analysis), and 'J' denotes the overall quality of the data (1=the data in the file are <50% good, 2=the data in the file are 50% to 75% good, 3=the data in the file are 76% to 98% good, 4=the data in the file are >98% good). The form of the PI private field is TBD. Please refer to the UCSS documentation for a more complete description of these quality flags. The variance in each measured quantity is included along with the measurement in each of the Level 2 and 3 files. These variances, and the quality flags which accompany them, give the best estimate of the quality of each of the individual measurements. The UCSS database at CDHF contains several versions of processing results for each day of data - no HRDI data earlier than version 7 should be used for scientific study. Version 7 data files include only mesospheric winds (daytime and nighttime). Version 8 files differ from version 7 files only in that they fix a problem in the v7 files for days on and after 12-Feb-1993 ('Uars day' 520 - UARS days are days since the spacecraft was activated). Version 9 files contain stratospheric wind data as well as mesospheric winds. Version 10 files differ from the prior version only in that they were created using updated corrections for the long-term drifts of the instrument, and an updated stratospheric aerosol calibration. Version 11 files were created using further corrections for the instrumental effects, and contain mesospheric temperatures, O2 band volume emission rates as well. Future versions of the files will contain mesospheric ozone and O1d mixing ratios and stratospheric aerosol extinction coefficients, in addition to the products available earlier. DataProcessingOverview: Instrument data, received at the Central Data Handling Facility (CDHF), is used to generate Level 0 files (containing raw instrument values, ex. counts). These files are processed to produce Level 1 files (in which measured levels have been converted to meaningful scientific values (ex. volts)). The Level 2A HRDI data processing software reads these Level 1 files, gathers the data into significant bundles ('tangent heights' and 'scans'), and processes the bundles to produce Level 2A files (atmospheric measurements - spectra, etc. - valid along the line of sight of the instrument at each tangent height). A 'tangent height' is defined as the data taken during the time in which the instrument is staring at a certain location in space (usually refered to as being at a given distance above the earth's surface). A 'scan' is a collection of consecutive tangent heights, between which the instrument's movement direction (up or down) is constant. A scan is intended to contain a column of tangent heights above the same point on the earth's surface. Level 2A files are read, in turn, by the HRDI Level 2B processing software, gathered into meaningful bundles (sets of scans which are consecutive in time and are of the same 'type' (the instrument was operating in the same mode)), and processed to produce Level 2B files (containing profiles of measurments of atmospheric quantities (wind, temperature, etc.) at each of several altitudes above a particular location). Level 2B files are read by the HRDI Level 3 processing software, which interpolates the profile data to standardized grid points (locations and times), and writes this data as Level 3 files (one file for each type of profile in the Level 2B files, and for each gridding method). DataUseage: The data set is mainly useful as a source of wind measurements in the stratosphere, mesosphere, and lower thermosphere. Please note that the quality flags in the data as well as the quality flags and comments in the UCSS database should be examined/understood before using the data. FileClassRelationships: Level 2A files are used to produce Level 2B files, which are in turn used to generate Level 3 files. Each Level 2A file should produce one Level 2B file. Each Level 2B file should produce several Level 3 files, depending on the operating mode of the instrument at the time the data was produced (a different Level 3 file is produced for each species/measurment type and grid). LitReferences: Please refer to information on file at CDHF (which was delivered with prior metadata information), which should include HRDI memos S-300 and S-379. For additional information please refer to the papers: 'High Resolution Doppler Imager', W. R. Skinner, P. B. Hays, and V. J. Abreu, IGARSS '87, February, 1987. 'The High Resolution Doppler Imager', Paul B. Hays, Wilbert R. Skinner, Vincent J. Abreu, and Jeng-Hwa Yee, Digest of the Topical Meeting on Optical Remote Sensing of the Atmosphere, 1990, (Optical Society of America, Washington, D. C. 1990), Vol. 4, p. 7. 'A Sequential Estimation Technique for Recovering Atmospheric Data from Orbiting Satellites', D. A. Ortland, P. B. Hays, W. R. Skinner, M. D. Burrage, A. R. Marshall, and D. A. Gell, The Upper Mesosphere and Lower Thermosphere, Geophyiscal Monograph Series, Vol 87, edited by R. Johnson and T. Killeen, AGU, Washington, D. C., 1995. 'Validation of HRDI Mesospheric and Lower Thermospheric Winds', M. D. Burrage, W. R. Skinner, A. R. Marshall, P. B. Hays, R. S. Lieberman, S. J. Franke, D. A. Gell, D. A. Ortland, F. J. Schmidlin, R. A. Vincent, and D. L. Wu, J. Geophys. Res., in press 1996. 'Comparison of HRDI wind measurements with radar and rocket observations', M. D. Burrage, W. R. Skinner, A. R. Marshall, P. B. Hays, R. S. Lieberman, D. A. Gell, D. A. Ortland, Y. T. Morton, D. L. Wu, S. J. Franke, F. J. Schmidlin, and R. A. Vincent, Geophys. Res. Letts. 20, 1259-1263, 1993. For Level 3 format information, please refer to: UARS CDHF Software System (UCSS) Programmer's Guide to Production Software Support Services (UCSS Programmer's Guide) Keyword Value ------- ----- FILE_CLASS_NAME: HRDI L3AT DATA FILE RECORD_TYPE_NAMES: SFDU_Label, File_Label_Record, Continuation_Label_Record, Data_Record ALGORITHMS: Each Level 2B profile is read, and the location, time and type (which region of the atmosphere does the profiles contain data for, and what type of data (velocity, temperature, etc.) does it contain) are stored. The sequence of profiles of each type is divided into subsequences called 'semi-orbits', during which the latitude of the satellite subpoint is monotonically increasing or decreasing. The HRDI Level 3 processing analyzes all data (for each region and data type) for one semi-orbit at the same time, pairing profiles for different atmospheric regions (so a single profile can represent both mesospheric (and lower thermospheric) and stratospheric data), filling points on the standard time grid by interpolation, and interpolating altitude gridded data onto a pressure grid (using NMC pressure vs. altitude data). FILE_CLASS_SYNTAX: Number of records is specified in the File_Label_Record List of Records in file: #1: SFDU_Label #2: File_Label_Record #3: Continuation_Label_Record Zero or more as specified in the File_Label_Record #4: Data_Record One or more as specified in the File_Label_Record The label records are produced automatically by the UCSS routines used to open (OPENL3AT), and write (WRITEL3AT) the file. FILE_CLASS_FIELD_RELATIONSHIPS: Level 2B data records are read by the Level 3 processing software and used to produce the Level 3 data records. The Level 3 processing software writes out, each measurement type to its own file, profiles interpolated onto the standard UARS grids using the standard UCSS routine (WRITEL3AT). One L2B file can be used to produce several L3AT files. FILE_CLASS_MISC: A Level 3AT data file consists of a collection of profiles of atmospheric data, gridded by altitude or pressure level, that are ordered by the time values associated with the profiles. Each record of the Level 3AT file contains a single array of data values for one parameter or specie type for a specific time. The standard times at which 3AT records may be written are every spacecraft minute (65.536 seconds) starting with the middle of the first EMAF (engineering major frame) of the day (32.768 seconds into the day). The standard pressure level values in millibars are given by: P(i) = 1000.0 * (10**(-i/6)), i=0,1,...35, while the standard altitude level values in kilometers are given by: Z(i) = 5 * i, i <= 12 Z(i) = 60 + (i - 12) * 3, 13 <= i <= 32 Z(i) = 120 + (i - 32) * 10, 33 <= i <= 50. See the UCSS Programmer's Guide to Production Software Support Services for further details about the standard data array and the Level 3AT data file format. The UCSS data formats, and therefore the corresponding SFDU structures provided herewith, are not unique to a particular instrument data set. The value shown for the FIELD_MNEMONIC keyword represents the argument used in the Level 3AT access services as documented in the UCSS Programmer's Guide. When an argument is not available the FIELD_MNEMONIC keyword is not present. 1. SFDU_Label Record -------------------- RECORD_NAME: SFDU_Label RECORD_STRUCTURE: Fixed Length RECORD_LENGTH: 60 Bytes RECORD_FIELD_NAMES: Tz_Field, Lz_Field, Ti_Field, Li_Field RECORD_SYNTAX: 4 Fields #1: Tz_Field #2: Lz_Field #3: Ti_Field #4: Li_Field 1.1 Tz_Field ------------ FIELD_NAME: Tz_Field FIELD_SYNTAX: ASCII Character*32 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: SFDU Type (Tz) Field. Constant Value = 'CCSD1Z000001'. FIELD_REPRESENTATION: 12A FIELD_DISPLAY_FORMAT: A12 1.2 Lz_Field ------------ FIELD_NAME: Lz_Field FIELD_SYNTAX: ASCII Character*8 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: SFDU Length (Lz) Field. 20 + l where l is the length of the UARS file Right justified, zero filled FIELD_REPRESENTATION: 8A FIELD_DISPLAY_FORMAT: A8 1.3 Ti_Field ------------ FIELD_NAME: Ti_Field FIELD_SYNTAX: ASCII Character*12 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: SFDU Type (Ti) Field. Constant value = 'NURS1I00xxxx' where Ti_Field (8:11) (xxxx) depends upon instrument and xxxx is the Data Descriptive Record ID (DDRI) for the file. FIELD_REPRESENTATION: 12A FIELD_DISPLAY_FORMAT: A12 1.4 Li_Field ------------ FIELD_NAME: Li_Field FIELD_SYNTAX: ASCII Character*8 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: SFDU Length (Lz) Field. Length of UARS file Right justified, zero filled FIELD_REPRESENTATION: 8A FIELD_DISPLAY_FORMAT: A8 2. File_Label_Record -------------------- RECORD_NAME: File_Label_Record RECORD_STRUCTURE: Variable Length. The record structure is as created by the standard UCSS calls to open and write to this file. See the UCSS Programmer's Guide to Production Software Support Services for details about this record. (Appendix E.) RECORD_LENGTH: Max (148 + 28 * n, length of Data_Record) where n = Value (Number_of_Time/Version_Entries_in_Record) RECORD_FIELD_NAMES: Satellite_Identifier Record_Type Instrument_Identifier Data_Subtype_Or_Species Format_Version_Number Physical_Record_Count Number_Of_Continuation_Records_For_File_Label Number_Of_Physical_Records_In_File File_Creation_Time_In_VAX_VMS_ASCII_Format Year_For_First_Data_Record Day_Of_Year_For_First_Data_Record Milliseconds_Of_Day_For_First_Data_Record Year_For_Last_Data_Record Day_Of_Year_For_Last_Data_Record Milliseconds_Of_Day_For_Last_Data_Record Data_Level UARS_Day_Number Number_Of_Data_Points_Per_Record Base_Index_Of_Data_Point_Values Record_Length_In_Bytes CCB_Version_Number File_Cycle_Number Virtual_File_Flag Total_Number_Of_Time/Version_Entries_In_File Number_Of_Time/Version_Entries_In_Record Version_Entries RECORD_SYNTAX: 26 Fields #1 : Satellite_Identifier #2 : Record_Type #3 : Instrument_Identifier #4 : Data_Subtype_Or_Species #5 : Format_Version_Number #6 : Physical_Record_Count #7 : Number_Of_Continuation_Records_For_File_Label #8 : Number_Of_Physical_Records_In_File #9 : File_Creation_Time_In_VAX_VMS_ASCII_Format #10: Year_For_First_Data_Record #11: Day_Of_Year_For_First_Data_Record #12: Milliseconds_Of_Day_For_First_Data_Record #13: Year_For_Last_Data_Record #14: Day_Of_Year_For_Last_Data_Record #15: Milliseconds_Of_Day_For_Last_Data_Record #16: Data_Level #17: UARS_Day_Number #18: Number_Of_Data_Points_Per_Record #19: Base_Index_Of_Data_Point_Values #20: Record_Length_In_Bytes #21: CCB_Version_Number #22: File_Cycle_Number #23: Virtual_File_Flag #24: Total_Number_Of_Time/Version_Entries_In_File #25: Number_Of_Time/Version_Entries_In_Record #26: Version_Entries 2.1 Satellite_Identifier ------------------------ FIELD_NAME: Satellite_Identifier FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Satellite identifier. Constant value 'UARS' FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 2.2 Record_Type --------------- FIELD_NAME: Record_Type FIELD_SYNTAX: ASCII Character*2 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Record type. Constant value ' 1' indicates a file label record. FIELD_REPRESENTATION: 2A FIELD_DISPLAY_FORMAT: A2 2.3 Instrument_Identifier ------------------------- FIELD_NAME: Instrument_Identifier FIELD_MNEMONIC: Data_Type FIELD_SYNTAX: ASCII Character*12 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Instrument identifier. Left justified, blank filled. All HRDI L3AT data files should contain 'HRDI'. FIELD_REPRESENTATION: 12A FIELD_DISPLAY_FORMAT: A12 2.4 Data_Subtype_Or_Species --------------------------- FIELD_NAME: Data_Subtype_Or_Species FIELD_MNEMONIC: Subtype FIELD_SYNTAX: ASCII Character*12 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Data subtype or species. Left justified, blank filled. The subtypes/species allowed are dependent on the instrument_type. The legal values are controlled by the UARS PCMB. The legal values for subtypes/species for the HRDI instrument are: Subtype Species MERWIN_A Meridional wind - altitude gridded MERWIN_P Meridional wind - pressure gridded ZONWIN_A Zonal wind - altitude gridded ZONWIN_P Zonal wind - pressure gridded MOLEXT_A Molecular extinction - altitude gridded MOLEXT_P Molecular extinction - pressure gridded AEREXT_A Aerosol extinction - altitude gridded AEREXT_P Aerosol extinction - pressure gridded TEMP_A Temperature - altitude gridded TEMP_P Temperature - pressure gridded VOLER_A Volume emission rate - altitude gridded VOLER_P Volume emission rate - pressure gridded O3_A Ozone mixing ratio, altitude gridded O3_P Ozone mixing ratio, pressure gridded O1D_A O singlet D mixing ratio, altitude gridded O1D_P O singlet D mixing ratio, pressure gridded FIELD_REPRESENTATION: 12A FIELD_DISPLAY_FORMAT: A12 2.5 Format_Version_Number ------------------------- FIELD_NAME: Format_Version_Number FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Format version number. Constant value ' 1' indicates that this is the first version of the Level 3AT file structure. field_representation: 4A FIELD_DISPLAY_FORMAT: A4 2.6 Physical_Record_Count ------------------------- FIELD_NAME: Physical_Record_Count FIELD_SYNTAX: ASCII character*8 string FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Physical record count. Constant value ' 1' indicates the label record is the logical first record in the file. FIELD_REPRESENTATION: 8A FIELD_DISPLAY_FORMAT: A8 2.7 Number_Of_Continuation_Records_For_File_Label ------------------------------------------------- FIELD_NAME: Number_Of_Continuation_Records_For_File_Label FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 0 FIELD_DESCRIPTION: Number of continuation records for file label for a virtual file (a level 3AT file containing a user specified time range that is not on day boundaries). Right justified, blank filled FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 2.8 Number_Of_Physical_Records_In_File -------------------------------------- FIELD_NAME: Number_Of_Physical_Records_In_File FIELD_SYNTAX: ASCII Character*8 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Number of physical records in file Right justified, blank filled Does not count SFDU label record FIELD_REPRESENTATION: 8A FIELD_DISPLAY_FORMAT: A8 2.9 File_Creation_Time_In_VAX_VMS_ASCII_Format ----------------------------------------------- FIELD_NAME: File_Creation_Time_In_VAX_VMS_ASCII_Format FIELD_SYNTAX: ASCII Character*23 String FIELD_UNITS: dd-mmm-yyyy hh:mm:ss.cc FIELD_RESOLUTION: 0.01 second FIELD_RANGE: n/a FIELD_DESCRIPTION: File creation time in VAX VMS ASCII format indicates the date and time the file was cataloged in the UCSS. FIELD_REPRESENTATION: 23A FIELD_DISPLAY_FORMAT: A23 2.10 Year_For_First_Data_Record ------------------------------- FIELD_NAME: Year_For_First_Data_Record FIELD_SYNTAX: ASCII Character*3 String FIELD_UNITS: Years since 1900 FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Year for first data record Right justified, blank filled Value is Year-1900 FIELD_REPRESENTATION: 3A FIELD_DISPLAY_FORMAT: A3 2.11 Day_Of_Year_For_First_Data_Record -------------------------------------- FIELD_NAME: Day_Of_Year_For_First_Data_Record FIELD_SYNTAX: ASCII Character*3 String FIELD_UNITS: Day of Year FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 1, <= 366 FIELD_DESCRIPTION: Day of year for first data record Right justified, blank filled FIELD_REPRESENTATION: 3A FIELD_DISPLAY_FORMAT: A3 2.12 Milliseconds_Of_Day_For_First_Data_Record ---------------------------------------------- FIELD_NAME: Milliseconds_Of_Day_For_First_Data_Record FIELD_SYNTAX: ASCII Character*8 String FIELD_UNITS: Milliseconds FIELD_RESOLUTION: 1 millisecond FIELD_RANGE: Integer >=0, <= 86399999 FIELD_DESCRIPTION: Milliseconds of day for first data record Right justified, blank filled FIELD_REPRESENTATION: 8A FIELD_DISPLAY_FORMAT: A8 2.13 Year_For_Last_Data_Record ------------------------------ FIELD_NAME: Year_For_Last_Data_Record FIELD_SYNTAX: ASCII Character*3 String FIELD_UNITS: Years since 1900 FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Year for last data record Right justified, blank filled Value is Year-1900 FIELD_REPRESENTATION: 3A FIELD_DISPLAY_FORMAT: A3 2.14 Day_Of_Year_For_Last_Data_Record ------------------------------------- FIELD_NAME: Day_Of_Year_For_Last_Data_Record FIELD_SYNTAX: ASCII Character*3 String FIELD_UNITS: Day of year FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 1, <= 366 FIELD_DESCRIPTION: Day of year for last data record Right justified, blank filled FIELD_REPRESENTATION: 3A FIELD_DISPLAY_FORMAT: A3 2.15 Milliseconds_Of_Day_For_Last_Data_Record --------------------------------------------- FIELD_NAME: Milliseconds_Of_Day_For_Last_Data_Record FIELD_SYNTAX: ASCII Character*8 String FIELD_UNITS: Milliseconds FIELD_RESOLUTION: 1 millisecond FIELD_RANGE: Integer >= 0, <= 86399999 FIELD_DESCRIPTION: Milliseconds of day for last data record Right justified, blank filled FIELD_REPRESENTATION: 8A FIELD_DISPLAY_FORMAT: A8 2.16 Data_Level --------------- FIELD_NAME: Data_Level FIELD_SYNTAX: ASCII Character*3 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Data level. Constant value '3AT' indicates data that has been placed on the standard UARS time and altitude grid (see Appendix E UCSS Programmer's Guide). FIELD_REPRESENTATION: 3A FIELD_DISPLAY_FORMAT: A3 2.17 UARS_Day_Number -------------------- FIELD_NAME: UARS_Day_Number FIELD_MNEMONIC: UARS_Day FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: Days FIELD_RESOLUTION: 1 day FIELD_RANGE: Integer >= 1 FIELD_DESCRIPTION: UARS day number (UARS day 1 = September 12, 1991) Right justified, blank filled FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 2.18 Number_Of_Data_Points_Per_Record ------------------------------------- FIELD_NAME: Number_Of_Data_Points_Per_Record FIELD_MNEMONIC: Max_Points FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 1, <= 1000 FIELD_DESCRIPTION: Number of data points per record Right justified, blank filled FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 2.19 Base_Index_Of_Data_Point_Values ------------------------------------ FIELD_NAME: Base_Index_Of_Data_Point_Values FIELD_MNEMONIC: Base_Index FIELD_SYNTAX: ASCII Character*4 String Right justified, blank filled FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 0, <= 100 FIELD_DESCRIPTION: Base_Index is determined by the instrument science team and is the starting (lowest) grid index for the standard UARS grid present in the data array of the file (i.e. the data entry in the first element in the Data3A array is the data value for the UARS standard grid at the position indicated by the value of Base_Index). The base_index, together with the Max_Points, determine the dimensions of the Level 3 array. The UARS Standard grids are defined in Section E of the UCSS Programmer's Guide. Right justified, blank filled. FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 2.20 Record_Length_In_Bytes --------------------------- FIELD_NAME: Record_Length_In_Bytes FIELD_SYNTAX: ASCII Character*5 String FIELD_UNITS: Bytes FIELD_RESOLUTION: 4 bytes FIELD_RANGE: Integer >= 148, <= 2216 FIELD_DESCRIPTION: Record length in bytes Right justified, blank filled Value is 4*Integerpart ((Max (148, 64 + 8*n) + 3)/4) where n = Value (Number_Of_Data_Points_per_Record) FIELD_REPRESENTATION: 5A FIELD_DISPLAY_FORMAT: A5 2.21 CCB_Version_Number ----------------------- FIELD_NAME: CCB_Version_Number FIELD_SYNTAX: ASCII Character*9 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >=1, <= 9999 FIELD_DESCRIPTION: Version number assigned by the UCSS Configuration Control Board in conjunction with the Principal Investigator to differentiate versions of data. Right justified, blank filled. HRDI data version 7 is the earliest which contains validated winds. FIELD_REPRESENTATION: 9A FIELD_DISPLAY_FORMAT: A9 2.22 File_Cycle_Number ---------------------- FIELD_NAME: File_Cycle_Number FIELD_SYNTAX: ASCII Character*5 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >=1, <= 31 FIELD_DESCRIPTION: File cycle number right justified, blank filled Supplied only during file creation by a Remote Access Computer data transfer, otherwise undefined The cycle number is incremented if necessary to provide a unique catalog entry at the UARS CDHF. FIELD_REPRESENTATION: 5A FIELD_DISPLAY_FORMAT: A5 FIELD_FILL_CODE: Undefined 2.23 Virtual_File_Flag ---------------------- FIELD_NAME: Virtual_File_Flag FIELD_SYNTAX: ASCII Character FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: The Virtual_File_Flag is set to ' ' if a file is a production file containing all the available data for one specific day or 'V' if the file is created by a Remote Access Computer data transfer where a user specified time range is not on day boundaries. FIELD_REPRESENTATION: 1A FIELD_DISPLAY_FORMAT: A1 2.24 Total_Number_Of_Time/Version_Entries_In_File ------------------------------------------------- FIELD_NAME: Total_Number_Of_Time/Version_Entries_In_File FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 0 FIELD_DESCRIPTION: Number of time/version entries in the file. Right justified, blank filled. Value of ' 1' if not a virtual file. FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 FIELD_FILL_CODE: 2.25 Number_Of_Time/Version_Entries_In_Record --------------------------------------------- FIELD_NAME: Number_Of_Time/Version_Entries_In_Record FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 0 FIELD_DESCRIPTION: Number of time/version entries in record Right justified, blank filled FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 2.26 Version_Entries -------------------- FIELD_NAME: Version_Entries FIELD_SYNTAX: ASCII Character*28 String 1-D Array (n), where n is value (Number_Of_Time/Version_Entries_In_Record) FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: List of version entries. Each version entry contains: Version_Entries (1:3) start year Version_Entries (4:6) start day of year Version_Entries (7:14) start milliseconds of day Version_Entries (15:24) version number Version_Entries (24:28) cycle number FIELD_REPRESENTATION: n(28A) FIELD_DISPLAY_FORMAT: nA28 3. Continuation_Label_Record ---------------------------- RECORD_NAME: Continuation_Label_Record RECORD_STRUCTURE: Variable Length RECORD_LENGTH: Max (48 + 28 * n, length of Data_Record) where n = Value (Number_of_Time/Version_Entries_in_Record) RECORD_FIELD_NAMES: Satellite_Identifier Record_Type Instrument_Identifier Data_Subtype_Or_Species Format_Version_Number Physical_Record_Count Number_Of_Time/Version_Entries_In_Record Spare Version_Entries RECORD_SYNTAX: 9 Fields #1 : Satellite_Identifier #2 : Record_Type #3 : Instrument_Identifier #4 : Data_Subtype_Or_Species #5 : Format_Version_Number #6 : Physical_Record_Count #7 : Number_Of_Time/Version_Entries_In_Record #8 : Spare #9 : Version_Entries 3.1 Satellite_Identifier ------------------------ FIELD_NAME: Satellite_Identifier FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Satellite identifier. Constant value 'UARS' FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 3.2 Record_Type --------------- FIELD_NAME: Record_Type FIELD_SYNTAX: ASCII Character*2 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Record type. Constant value ' 2' for a continuation label record format. FIELD_REPRESENTATION: 2A FIELD_DISPLAY_FORMAT: A2 3.3 Instrument_Identifier ------------------------- FIELD_NAME: Instrument_Identifier FIELD_MNEMONIC: Data_Type FIELD_SYNTAX: ASCII Character*12 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Instrument identifier. Left justified, blank filled. All HRDI L3AT data files should contain 'HRDI'. FIELD_REPRESENTATION: 12A FIELD_DISPLAY_FORMAT: A12 3.4 Data_Subtype_Or_Species --------------------------- FIELD_NAME: Data_Subtype_Or_Species FIELD_MNEMONIC: Subtype FIELD_SYNTAX: ASCII Character*12 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Data subtype or species. Left justified, blank filled. The subtypes/species allowed are dependent on the instrument_type. The legal values are controlled by the UARS PCMB. The legal values for subtypes/species for the HRDI instrument are: Subtype Species MERWIN_A Meridional wind - altitude gridded MERWIN_P Meridional wind - pressure gridded ZONWIN_A Zonal wind - altitude gridded ZONWIN_P Zonal wind - pressure gridded MOLEXT_A Molecular extinction - altitude gridded MOLEXT_P Molecular extinction - pressure gridded AEREXT_A Aerosol extinction - altitude gridded AEREXT_P Aerosol extinction - pressure gridded TEMP_A Temperature - altitude gridded TEMP_P Temperature - pressure gridded VOLER_A Volume emission rate - altitude gridded VOLER_P Volume emission rate - pressure gridded O3_A Ozone mixing ratio, altitude gridded O3_P Ozone mixing ratio, pressure gridded O1D_A O singlet D mixing ratio, altitude gridded O1D_P O singlet D mixing ratio, pressure gridded FIELD_REPRESENTATION: 12A FIELD_DISPLAY_FORMAT: A12 3.5 Format_Version_Number ------------------------- FIELD_NAME: Format_Version_Number FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Format version number. Constant value ' 1' indicates that this is the first version of the Level 3AT file structure. FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 3.6 Physical_Record_Count ------------------------- FIELD_NAME: Physical_Record_Count FIELD_SYNTAX: ASCII character*8 string FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Physical record count. Right justified blank filled. Does not include SFDU label. FIELD_REPRESENTATION: 8A FIELD_DISPLAY_FORMAT: A8 3.7 Number_Of_Time/Version_Entries_In_Record -------------------------------------------- FIELD_NAME: Number_Of_Time/Version_Entries_In_Record FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 1 FIELD_DESCRIPTION: Number of time/version entries in record Right justified, blank filled FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 3.8 Spare --------- FIELD_NAME: Spare FIELD_SYNTAX: ASCII Character*2 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Spare. Field contents undefined FIELD_REPRESENTATION: 2A FIELD_DISPLAY_FORMAT: A2 3.9 Version_Entries -------------------- FIELD_NAME: Version_Entries FIELD_SYNTAX: ASCII Character*28 String 1-D Array (n), where n is value (Number_Of_Time/Version_Entries_In_Record) FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: List of version entries. Each version entry contains: Version_Entries (1:3) start year Version_Entries (4:6) start day of year Version_Entries (7:14) start milliseconds of day Version_Entries (15:24) version number Version_Entries (24:28) cycle number FIELD_REPRESENTATION: n(28A) FIELD_DISPLAY_FORMAT: nA28 4. Data_Record -------------- RECORD_NAME: Data_record RECORD_STRUCTURE: Variable Length. Each data record of a Level 3AT file contains a single array of data values for one parameter or species type for a specific time and latitude. The record structure is as created by the standard UCSS calls to open (OPENL3AT) and write (WRITEL3AT) to this file. Records are variable length, but all data records in a single file should be of the same length. The data array is organized according to the rules of the UARS standard data array. (See the UCSS Programmer's Guide to Production Software Support Services for further details.) RECORD_LENGTH: Determined by the number of data points in the data structure. Each data record in a file should be of the same length. Max (64 + 4 * n, length of File_Label_Record) where n = Value (Total_Number_of_Points_in_the_Record) RECORD_FIELD_NAMES: Satellite_Identifier Record_Type Instrument_Identifier Physical_Record_Count Spare Total_Number_Of_Points_In_The_Record Number_Of_Actual_Points Starting_Index_Of_First_Actual_Point Record_Time_In_UDTF_Format Latitude Longitude Local_Solar_Time Solar_Zenith_Angle Data Quality RECORD_SYNTAX: 15 Fields #1 : Satellite_Identifier #2 : Record_Type #3 : Instrument_Identifier #4 : Physical_Record_Count #5 : Spare #6 : Total_Number_Of_Points_In_The_Record #7 : Number_Of_Actual_Points #8 : Starting_Index_Of_First_Actual_Point #9 : Record_Time_In_UDTF_Format #10: Latitude #11: Longitude #12: Local_Solar_Time #13: Solar_Zenith_Angle #14: Data #15: Quality Each data record is made up of one of each of the fields above, in the order listed above. 4.1 Satellite_Identifier ------------------------ FIELD_NAME: Satellite_Identifier FIELD_SYNTAX: ASCII Character*4 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Satellite identifier. Constant value 'UARS' FIELD_REPRESENTATION: 4A FIELD_DISPLAY_FORMAT: A4 4.2 Record_Type --------------- FIELD_NAME: Record_Type FIELD_SYNTAX: ASCII Character*2 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Record type. Constant value ' 3' for the data record format. FIELD_REPRESENTATION: 2A FIELD_DISPLAY_FORMAT: A2 4.3 Instrument_Identifier ------------------------- FIELD_NAME: Instrument_Identifier FIELD_MNEMONIC: Data_Type FIELD_SYNTAX: ASCII Character*12 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Instrument identifier. Left justified, blank filled. All HRDI L3AT files should contain 'HRDI'. FIELD_REPRESENTATION: 12A FIELD_DISPLAY_FORMAT: A12 4.4 Physical_Record_Count ------------------------- FIELD_NAME: Physical_Record_Count FIELD_SYNTAX: ASCII Character*8 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 2 FIELD_DESCRIPTION: Physical record count Right justified, blank filled Does not count SFDU label record FIELD_DISPLAY_FORMAT: A8 4.5 Spare --------- FIELD_NAME: Spare FIELD_SYNTAX: ASCII Character*2 String FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Spare. Constant value X'0000' FIELD_REPRESENTATION: VI2 FIELD_DISPLAY_FORMAT: I2 4.6 Total_Number_Of_Points_In_The_Record ---------------------------------------- FIELD_NAME: Total_Number_Of_Points_In_The_Record FIELD_MNEMONIC: Max_Points FIELD_SYNTAX: Scalar FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 1, <= 1000 FIELD_DESCRIPTION: Maximum number of data points in the data array. FIELD_REPRESENTATION: VI4 FIELD_DISPLAY_FORMAT: I4 4.7 Number_Of_Actual_Points --------------------------- FIELD_NAME: Number_Of_Actual_Points FIELD_MNEMONIC: Num_Points FIELD_SYNTAX: Scalar FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 1, <= 1000 FIELD_DESCRIPTION: Number of actual elements in the data array to be retrieved. FIELD_REPRESENTATION: VI4 FIELD_DISPLAY_FORMAT: I4 4.8 Starting_Index_Of_First_Actual_Point ---------------------------------------- FIELD_NAME: Starting_Index_Of_First_Actual_Point FIELD_MNEMONIC: Start_Index FIELD_SYNTAX: Scalar FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: Integer >= 0, <= 100 FIELD_DESCRIPTION: Starting grid index of first actual element in the Data3A array. FIELD_REPRESENTATION: VI4 FIELD_DISPLAY_FORMAT: I4 4.9 Record_Time_In_UDTF_Format ------------------------------- FIELD_NAME: Record_Time_In_UDTF_Format FIELD_MNEMONIC: Strt_Dattim FIELD_SYNTAX: 1-D Array (2) FIELD_UNITS: 1 millisecond FIELD_RESOLUTION: 1 millisecond FIELD_RANGE: FIELD_DESCRIPTION: Record time in UDTF format FIELD_REPRESENTATION: 2VI4 FIELD_DISPLAY_FORMAT: I5,I8 4.10 Latitude -------------- FIELD_NAME: Latitude FIELD_MNEMONIC: FIELD_SYNTAX: Scalar FIELD_UNITS: Degrees FIELD_RESOLUTION: FIELD_RANGE: >= -88.5, <= 88.5 FIELD_DESCRIPTION: Geodetic latitude. FIELD_REPRESENTATION: VR4 FIELD_DISPLAY_FORMAT: F6.2 4.11 Longitude -------------- FIELD_NAME: Longitude FIELD_MNEMONIC: FIELD_SYNTAX: Scalar FIELD_UNITS: Degrees FIELD_RESOLUTION: FIELD_RANGE: >= 0, < 360.0 FIELD_DESCRIPTION: Geodetic longitude. FIELD_REPRESENTATION: VR4 FIELD_DISPLAY_FORMAT: F7.2 4.12 Local_Solar_Time --------------------- FIELD_NAME: Local_Solar_Time FIELD_MNEMONIC: LST FIELD_SYNTAX: Scalar FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Local solar time FIELD_REPRESENTATION: VR4 FIELD_DISPLAY_FORMAT: F6.2 4.13 Solar_Zenith_Angle ----------------------- FIELD_NAME: Solar_Zenith_Angle FIELD_MNEMONIC: SZA FIELD_SYNTAX: Scalar FIELD_UNITS: n/a FIELD_RESOLUTION: n/a FIELD_RANGE: n/a FIELD_DESCRIPTION: Solar zenith angle FIELD_REPRESENTATION: VR4 FIELD_DISPLAY_FORMAT: F7.2 4.14 Data --------- FIELD_NAME: Data FIELD_MNEMONIC: Data3A FIELD_SYNTAX: 1-D Array (n), where n is value (Total_Number_Of_Points_In_The_Record) FIELD_UNITS: Depends on the type of data being written to the current file. The following lists the data species and the respective units for this field: Species Units Temperature degrees Kelvin Volume emission rate photons/cm**3/second Meridional wind meters per second Zonal wind meters per second O3 mixing ratio * unitless O(1D) mixing ratio * unitless Molecular extinction * km-1 Aerosol extinction * km-1 (* = data product not yet available) FIELD_RESOLUTION: Approx. 1e-7 times its value (it has the resolution afforded by its VAX FORTRAN storage/representation as a four byte real value). FIELD_RANGE: The range of the data stored in this array depends on the type of data being stored here (the species type), and on the exact conditions under which the data was taken. For each species the overall valid field range is as follows: Species Range Molecular extinction 0 to .5 km-1 Aerosol extinction 0 to .5 km-1 Temperature 100 to 400 degrees Kelvin Volume emission rate 0 to 1.0E7 photons/cm**3/second Meridional winds -300 to 300 meters per second Zonal winds -300 to 300 meters per second O3 mixing ratio 1e-4 to 1e-8 O(1D) mixing ratio 1e-11 to 1e-14 FIELD_DESCRIPTION: Holds the max_points data values for consecutive elements in the UARS standard data array starting at the element index, base_index. An individual Level 3 file has only one subtype, and holds only one type of data (measurement type or species). See the units description above for the file subtypes and the corresponding measurement types which occur for this field. See the UCSS Programmer's Guide to Production Software Support Services for details about the standard data array and this field. FIELD_REPRESENTATION: Max_points * VR4 FIELD_DISPLAY_FORMAT: E10.2 FIELD_FILL_CODE: INVALID_REAL_NUMBER X'00008000' FIELD_MASKS: N/A 4.15 Quality ------------ FIELD_NAME: Quality FIELD_MNEMONIC: Qual FIELD_SYNTAX: 1-D Array (n), where n is value (Total_Number_Of_Points_In_The_Record) FIELD_UNITS: Depends on the type of data being written to the current file. The following lists the data species and the respective units for this field: Species Units Molecular extinction 1/kilometers Aerosol extinction 1/kilometers Temperature degrees Kelvin Volume emission rate photons/centimeter**3/second Meridional wind meters/second Zonal wind meters/second O3 mixing ratio unitless O(1D) mixing ratio unitless FIELD_RESOLUTION: Approx. 1e-7 times its value (it has the resolution afforded by its VAX FORTRAN storage/representation as a four byte real value). FIELD_RANGE: The range of the data stored in this array depends on the type of data being stored here (the species type), and on the exact conditions under which the data was taken. For each species the overall valid field range is as follows: Species Range Molecular extinction 0 to .5 km-1 Aerosol extinction 0 to .5 km-1 Temperature 0 to 100 degrees Kelvin Volume emission rate 0 to 1.0E7 photons/cm**3/second Meridional wind 0 to 10000 meters per second Zonal wind 0 to 10000 meters per second O3 mixing ratio 0 to 1e-8 O(1D) mixing ratio 0 to 1e-20 FIELD_DESCRIPTION: Holds the max_points quality values for consecutive elements in the UARS standard data array (Data3A) starting at the element index, base_index. All HRDI Level 3 files use the standard deviation of a measurement as its quality value. See the UCSS Programmer's Guide to Production Software Support Services for details about the standard data array and this field. FIELD_REPRESENTATION: Max_points * VR4 FIELD_DISPLAY_FORMAT: E10.2 FIELD_FILL_CODE: INVALID_REAL_NUMBER X'00008000' FIELD_MASKS: N/A