Change history for TERRA L1B EV 1KM File Specification ============================================================================ ============================================================================ V6.1.14 06/26/2012 Added the doi metadata. ============================================================================ ============================================================================ V6.1.12 11/29/2011 Removed the "mixed" option from Scan Type since no scan is mixed. ============================================================================ ============================================================================ V6.1.8 11/15/2010 SI value of 65524 will be set to the scans with both sides of PCLW electronics on. Change the line "(reserved for future use)" to: (reserved for future use) 65501 - 65523 15 Corrected the description of Geolocation SDSs ============================================================================ ============================================================================ V6.0.0 05/22/2008 Added following 4 global attributes used by 250m and 500m bands only: "Detector_Quality_Flag2" "deadSubframeDataPercent" "dead_subframes" "noisy_subframe" SI value of 65525 will be set to the pixels affected by dead subframes Change the line "(reserved for future use)" to: (reserved for future use) 65501 - 65524 15 No interpolation for dead detectors. ============================================================================ ============================================================================ V5.0.4 01/11/2005 Added flowing two global attributes: "HDFEOS_FractionalOffset_10*nscans_MODIS_SWATH_Type_L1B" "HDFEOS_FractionalOffset_Max_EV_frames_MODIS_SWATH_Type_L1B" ============================================================================ ============================================================================ V4.3.0 10/27/2003 The meaning of "bit QA flags" Bit 1 ("Spacecraft Maneuver") was changed to reflect whether any of the spacecraft attitude angles yaw, pitch, or roll are greater than threshold values set within the QA LUTs. Added Bit 26, "Sci Abnormal", which is set when SS_FR_SCIABNORM is set, which reflects the way Bit 1 was formerly set. Changed examples to be specific to MODIS/Terra. ============================================================================ ============================================================================ V4.0.5 07/15/2002 Added "bit QA flags" Bit 24, "dropped scan(s) between leading granule and granule being processed", and Bit 25, "dropped scan(s) between granule being processed and trailing granule". ============================================================================ ============================================================================ V4.0.0 03/27/2002 1. Added ECS Archive Metadata object "ProcessingEnvironment". 2. Added flag value 65526 (Calibration coefficient b1 could not be computed) to list of flags. ============================================================================ ============================================================================ ALL CHANGES BELOW WERE MADE TO COMMON AQUA/TERRA PRODUCT FILE SPECIFICATIONS and are included for completeness. ============================================================================ ============================================================================ V3.0.0 04/01/2001 (change effective with MOD_PR02, V3.0.0) ============================================================================ ============================================================================ (reference: CCR ****) 1. Set "ASSOCIATEDPLATFORMSHORTNAME.1" to "MODIS" 2. Removed "ASSOCIATEDPLATFORMSHORTNAME.2", "ASSOCIATEDINSTRUMENTSHORTNAME.2", "ASSOCIATEDSENSORSHORTNAME.2", "ASSOCIATEDPLATFORMSHORTNAME.3", "ASSOCIATEDINSTRUMENTSHORTNAME.3", "ASSOCIATEDSENSORSHORTNAME.3", "ASSOCIATEDPLATFORMSHORTNAME.4", "ASSOCIATEDINSTRUMENTSHORTNAME.4", and "ASSOCIATEDSENSORSHORTNAME.4". ============================================================================ ============================================================================ V2.5.1 01/12/2001 (changes effective with MOD_PR02, V2.5.5) ============================================================================ ============================================================================ (reference: CCR 528) 1. Added global attribute "Granule Average QA Values". 2. Added global attribute "Solar Irradiance on RSB Detectors over pi" 3. Under "Reason for unusable data": (1) changed 65529 from "(unused)" to "TEB radiance or RSB dn** exceeds the maximum of scaling range", (2) removed the line for "Moon in SV port for TEB band" since that is obsolete, and (3) clarified the meaning of 65530. 4. Added attributes to each uncertainty index SDS: specified_uncertainty, scaling_factor, uncertainty_units. Also, in the introduction to section II, clarified the way to calculate % uncertainty from uncertainty index. (miscellaneous) 1. Corrected a few typos and clarified a few notes. ============================================================================ ============================================================================ V2.5.0, release 2 08/18/2000 (changes effective with MOD_PR02, V2.5.0) ============================================================================ ============================================================================ There is currently no CCR for this change. Prior to delivering V2.5.0, it was learned that the MCF files were not constructed properly. Rather than having ASSOCIATEDSENSORSHORTNAME appear as ("VNIR","SWIR","MIR","TIR"), there should be multiple containers in the MCF files for the object "AssociatedPlatformInstrumentSensorContainer", one for each value in ASSOCIATEDSENSORSHORTNAME. Thus, in the file specifications, there will be: | ASSOCIATEDPLATFORMSHORTNAME.1 "Terra" or "Aqua" | +-----------------------------------------------------------------------------+ | ASSOCIATEDINSTRUMENTSHORTNAME.1 "MODIS" | +-----------------------------------------------------------------------------+ | ASSOCIATEDSENSORSHORTNAME.1 "VNIR" | +-----------------------------------------------------------------------------+ | ASSOCIATEDPLATFORMSHORTNAME.2 "Terra" or "Aqua" | +-----------------------------------------------------------------------------+ | ASSOCIATEDINSTRUMENTSHORTNAME.2 "MODIS" | +-----------------------------------------------------------------------------+ | ASSOCIATEDSENSORSHORTNAME.2 "SWIR" | +-----------------------------------------------------------------------------+ | ASSOCIATEDPLATFORMSHORTNAME.3 "Terra" or "Aqua" | +-----------------------------------------------------------------------------+ | ASSOCIATEDINSTRUMENTSHORTNAME.3 "MODIS" | +-----------------------------------------------------------------------------+ | ASSOCIATEDSENSORSHORTNAME.3 "MIR" | +-----------------------------------------------------------------------------+ | ASSOCIATEDPLATFORMSHORTNAME.4 "Terra" or "Aqua" | +-----------------------------------------------------------------------------+ | ASSOCIATEDINSTRUMENTSHORTNAME.4 "MODIS" | +-----------------------------------------------------------------------------+ | ASSOCIATEDSENSORSHORTNAME.4 "TIR" | ============================================================================ ============================================================================ V2.5.0 08/15/2000 (changes effective with MOD_PR02, V2.5.0) ============================================================================ ============================================================================ There are two groups of changes: (1) planned changes unrelated to Aqua, and (2) changes required by Aqua. I) Planned changes unrelated to Aqua ------------------------------------ CCR 525: Approval pending Title: Change HDF-EOS Dimension Name for MOD021KM Geo Data Sets In Section 1.5, change all instances of the HDF-EOS dimension name "Max_EV_frames/5+1" to "1KM_geo_dim". Immediately below the table of dimension names, add the following: Note: Dimension_8, "1KM_geo_dim", is computed as Max_EV_Frames/5+1. CCR 526: Approval pending Title: Remove Obsolete Data from MOD02 Products Remove the following obsolete metadata: Sec. 1.3: "Post Processing Indicates Bad data" Sec. 1.4.1: "Managers VIS/NIR Quality Index" "Managers SWIR Quality Index" "Managers MWIR/LWIR Quality Index" "Discontinuities in linear gain b1 across granules" Remove the following obsolete SDS attributes: Sec. 2.9: "corrected_counts..." attributes of EV_1KM_Emissive SDS For all of the above, remove the annotations in the file specifications that describe these items as obsolete. Miscellaneous changes (no CCR filed). Clarify the follow items: A) section 1.6, note 2, bits 18-19, under the "Meaning" column, change "SRCA off" to "undetermined", B) section 1.3, note 1, remove the phrase: "(204 is the maximum)". C) added ".1" to ASSOCIATEDPLATFORMSHORTNAME, ASSOCIATEDINSTRUMENTSHORTNAME, ASSOCIATEDSENSORSHORTNAME II) Changes required by Aqua ---------------------------- 1. Provide examples for both Terra and Aqua for the following: LOCALGRANULEID SHORTNAME ASSOCIATEDPLATFORMSHORTNAME 2. Clarify the examples of ASSOCIATEDSENSORSHORTNAME: 1km and obc file: ("VNIR","SWIR","MIR","TIR") ============================================================================ ============================================================================ V2.4.1 07/10/2000 (changes effective with MOD_PR02, V2.4.3) ============================================================================ ============================================================================ CCR 527: Approval pending Title: Interpolate Dead Detector Scaled Integers In the table of unusable values (Section II), add an asterisk next to the value of 65531 and add the following note immediately below the table: * The "Dead Detector List" attribute (Section 1.4.1) identifies those detectors that are declared non-functional (cannot be calibrated). If possible, a valid SI value will be interpolated from the nearest functional detectors within the same scan. If not possible, the value will be set at 65531. This change affects how scientists interpret the values in the Level 1B product scaled-integer (SI) SDSs when detectors are flagged as dead. The "Dead Detector List" attribute remains the definitive data object in the product for scientists to read to determine whether or not a detector has been flagged as dead. An additional side effect of this change is that there will now likely be some non-zero values in the ECS core metadata fields QAPERCENTINTERPOLATEDDATA, which were previously all set to zero. Additional Change (no CCR required): The table describing the "Detector Quality Flag" attribute underwent minor corrections. ============================================================================ ============================================================================ V2.4.0 04/24/2000 ============================================================================ ============================================================================ CCR 523: Approval pending Title: New MCF Files and File Spec Explanations for ECS Metadata Changes 1. Incorporate new MCF files into MOD_PR02 delivered from ECS. 2. In ECS Core Metadata, in the example for for SCIENCEQUALITYFLAG, add "Not Investigated" as the example. 3. In ECS Archive Metadata, add: DESCRREVISION "1.0" PRODUCTIONHISTORY (for future use) CCR 508: Approved for adding QA attributes: 11/22/1999 Part of this CCR was approved on 11/22/1999: add several new granule level attributes for QA purposes. The following attributes have now been added for this release (see details in the file specifications): % L1A EV All Scan Data are Missing % L1A EV RSB DN Not in Day Mode % L1A EV DN Missing Within Scan % Dead Detector EV Data % Sector Rotation EV Data % Saturated EV Data % TEB EV Data With Moon in SVP % EV Data Where Cannot Compute BG DN % RSB EV Data With dn** Below Scale % EV Data Where Nadir Door Closed % EV Data Not Calibrated Bit QA Flags Last Value Bit QA Flags Change ============================================================================ ============================================================================ L1B V2.3.1 12/28/1999 ============================================================================ ============================================================================ CCR 513: Approved: 12/28/1999 Title: Revise unusable data value for fill value to include RSB at night CCR 505, which was approved and implemented for L1B V2.3.0, created a specific unusable data value for RSB at night mode which was different than the HDF fill value of 65535. However, an unintended and consequence of this change is that the output granules of MOD_PR02 for night mode are no longer reduced in volume from the full-size day-mode granules. Consequently, we need to change the meaning of fill value back to include reflective band data at night so that the night mode data volume is reduced as before. The downstream readers will be unaffected by this change. In each L1B EV File specification (MOD021KM.fs, MOD02HKM.fs, MOD02QKM.fs), inSection II, under the notes on "Specific Data Values": 1. Change the description of the value of 65535 to: Fill Value (includes reflective band data at night and completely missing L1A scans) 2. Delete the line: Reflective Band Data not telemetered (night mode) 65525 15 3. Change the line "(reserved for future use)" to: (reserved for future use) 65501 - 65525 15 ============================================================================ ============================================================================ L1B V2.3.0 12/14/1999 ============================================================================ ============================================================================ CCR 470: Approved: 5/3/1999 Title: L1B Uncertainties The level 1B products should record the uncertainties of the reflectance products. Previous versions of level 1b recorded the radiance errors. This change does not affect the file format. The attached document (UncertaintiesSDS CCR, a word 98 file) should replace the Uncertainties SDS's section in the MS Word supplements to each file spec. And, for clarity, the description of each RSB uncertainty SDS in the file spec itself should state explicitly that it records the uncertainties in the reflectance product. At present, the description does not identify to which RSB product the uncertainty SDS's apply. ============================================================================ ============================================================================ CCR 486: Approved: 9/27/1999 Title: L1B File Specifications Clarifications 1. Add to MOD021KM.fs at the beginning: =============DETECTOR ORDER CONVENTION FOR DETECTOR DEPENDENT DATA============ The "SBRS" detector order convention refers to the numbering of detectors on each focal plane assembly as defined by the manufacturer. In this convention, the numbering of detectors is opposite in direction from the satellite track direction. The "product" detector order convention is the reverse of the SBRS convention. The product detector order convention was defined to allow consecutive scans to be laid down on an image with the last detector of one scan abutting the first detector of the next scan. ALL DATA ITEMS WITHIN THIS FILE FOLLOW THE "PRODUCT" DETECTOR ORDER CONVENTION. ============================================================================== ============================================================================ 2. Add a note in section 1.3 of each L1B EV file specification (MOD021KM.fs, MOD02HKM.fs, MOD02QKM.fs) on the meaning and usage of "Number of Scans". Note on usage of "Number of Scans". The value of the global attribute "Number of Scans" is used in the dimensioning of many of the data items within this product. In later descriptions of the dimensions of data items, the shortened string "nscans" is used to represent the value of the attribute "Number of Scans". This value will typically be 203 or 204 during operations (204 is the maximum). However, the file format supports any value greater than zero. 3. Clarify the explanation of how the L1B Swath Metadata is implemented in section 1.6 of each L1B EV file specification (MOD021KM.fs, MOD02HKM.fs, MOD02QKM.fs). These data are stored as a single HDF Vdata table having the name "Level 1B Swath Metadata". The number of records is equal to nscans (determined by the "Number of Scans" global attribute). The table below describes the fields of this Vdata object. ============================================================================ ============================================================================ CCR 485: Rejected: 11/22/1999 Title: Remove Unused QA Metadata "Discontinuities in..." From L1B Files This CCR proposed to remove the granule level QA metadata item "Discontinuities in linear gain b1 across granules" which contains only fill values and is not planned to be implemented. This CCR was rejected to ensure that L1B version 2.3.0 is backward compatible with current readers at launch. However, the CCB recommended adding a note to the file specs identifying this as an obsolete data item that will be removed at launch + 6 months. This note was added. ============================================================================ ============================================================================ CCR 488: Rejected: 11/22/1999 Title: L1B File 1km File -- Remove Emissive "counts" attributes This CCR proposed to remove the following attributes of the "EV_1km_Emissive" scaled integer SDS: "corrected_counts_scales", "corrected_counts_offset", "corrected_counts_units", since these are populated with fill values and should not be used by users. This CCR was rejected to ensure that L1B version 2.3.0 is backward compatible with current readers at launch. However, the CCB recommended adding a note to the file specs identifying these as obsolete attributes that will be removed at launch + 6 months. This note was added. ============================================================================ ============================================================================ CCR 491: Approved: 11/22/1999 Title: MOD02 File Specifications, Electronics Redundancy Vector Change This change was approved as long as the name of the attribute "Electronics Redundancy Vector" stays the same. The meaning of the bits was changed, the number of subsystems was expanded, the implementation was changed to being from telemetry, not a LUT. The attribute "Electronics Configuration Change" was added. ============================================================================ ============================================================================ CCR 498: Approved: 11/22/1999 Title: L1B EV File Specifications Corrections, delete misleading statement The unusable data value "TEB radiance below 0" was changed to unused. ============================================================================ ============================================================================ CCR 501: Approved: 11/22/1999 Title: Add additional granule level attributes: Detector Quality Flag and Earth-Sun Distance These two attributes were added. ============================================================================ ============================================================================ CCR 502: Approved: 11/22/1999 Title: L1B File Specifications Documentation Clarifications and Changes The examples of ALGORITHMPACKAGEVERSION, ALGORITHMPACKAGEMATURITYCODE, and ALGORITHMPACKAGENAME were changed to be more accurate. A note was added about computed the uncertainty in percent from the uncertainty index (the CCR proposed specific formulas. However, due to conflicting opinions within MCST about the formulas, the note simply stated to see the Product User's Guide). ============================================================================ ============================================================================ CCR 504: Rejected: 11/22/1999 Title: Remove Unused L1B Product Metadata "Post Processing Indicates Bad data" This CCR proposed to remove the granule level attribute "Post Processing Indicates Bad data" which contains only fill values and is not planned to be implemented. This CCR was rejected to ensure that L1B version 2.3.0 is backward compatible with current readers at launch. However, the CCB recommended adding a note to the file specs identifying this as an obsolete data item that will be removed at launch + 6 months. This note was added. ============================================================================ ============================================================================ CCR 505: Approved: 11/22/1999 Title: Revise and add unusable SI values to L1B file spec documentation. The list of unusable data values changed in Section II and explanation was added for the case of NAD closed. ============================================================================ ============================================================================ CCR 508: Rejected/Approved: 11/22/1999 Title: Remove unused attributes and add additional granule level QA attributes in L1B files. This CCR proposed to remove the granule level attributes: "Managers VIS/NIR Quality Index", "Managers SWIR Quality Index", and "Managers MWIR/LWIR Quality Index" which contains only fill values and is not planned to be implemented. This part of the CCR was rejected to ensure that L1B version 2.3.0 is backward compatible with current readers at launch. However, the CCB recommended adding a note to the file specs identifying this as an obsolete data item that will be removed at launch + 6 months. This note was added. This CCR also proposed to add several granule level attributes for QA purposes. This part of the CCR was approved. However, the attributes have not yet been implemented in L1B V2.3.0. They will be implemented in the next release. This CCR also proposed to add meaning to 2 bits of the Bit QA Flags. This part of the CCR was also approved and the changes were made for V2.3.0. ============================================================================ ============================================================================ L1B V2.2.0 5/30/1999 ============================================================================ ============================================================================ CCR 465: 3/16/1999 Approved: 4/19/1999 Title: Add SDS for Band26 to L1B 1km File Specification MOD021KM.fs For night and mixed granules, Band 26 (considered a reflective solar band) currently contains fillValue for any scan that is not a "Day" scan. However, these data are required by members of the science team for all scans, regardless of day or night. It is not desirable to add data to the existing SDS for reflective solar bands because the granule size for night granules will increase substantially. Also, it is not desirable to add Band 26 to the emissive SDS or remove it from the current reflective solar bands SDS because of the impact to current readers and the very substantial code modifications that would be required. Therefore, it is most practical to add band 26 as a separate SDS, always written to the file, regardless of day or night, and regardless of whether Bnad 26 data exist in the reflective solar bands SDS. This means that for day scans, there will be some duplication of information in the granule. ============================================================================ ============================================================================ CCR 473: 4/23/1999 Approved: 6/7/1999 Title: Change to L1B EV File Specifications MOD021KM.fs, MOD02HKM.fs, MOD02QKM.fs Remove the following MODIS level 1B QA granule metadata field: "All L1B Error Flags Off", "Noise in MWIR ADC Temperature", "Noise in LWIR ADC Temperature", "Noise in VIS ADC Temperature", "Noise in NIR 1km ADC Temperature", "Noise in band 1 ADC Temperature", "Noise in band 2 ADC Temperature", "Noise in SWIR Bands ADC Temperature". Change "Bit QA Flags" in "Level 1B Swath Metadata" by adding: bit 20 moon in keep out box for any RSB band bit 21 moon in keep out box for any TEB band bit 22 All SV data are bad for any reflective solar band bit 23 All BB data are bad for any reflective solar band and changing: bit 11 from "Instrument Standby Mode" to "Unused" bit 14 from "BB/Cavity Temperature Differential" to "Unused". Change "VERSIONID" example to integer value of 1 Change QA granule Metadata "Change in response since pre-launch" to "Discontinuities in linear gain b1 across granules" and change its count to 160 (number of emissive detectors). Add band and detector order description right before section 1.1) as following: For attributes dimensioned 38 (number of bands), the band order is: 1, 2, 3, .. , 13lo, 13hi, 14lo, 14hi, 15, .. , 36. For the reflective bands, total of 22, the order is: 1, 2, 3, .. , 13lo, 13hi, 14lo, 14hi, .. , 19, 26. The order of the 490 detectors follows the order of the 38 bands described earlier. Within each band, the order of detectors is along the track direction (opposite the SBRS detector board convention). ============================================================================ ============================================================================ CCR 477: 5/19/1999 Approved: 6/7/1999 Title: Change the way bad data values are signaled Reserve values of the scaled integer representation, SI, of the corrected digital signals for the RSB's and of the radiances of the TEB's written to the MOD02 products to signal the reason why data are bad. Set the uncertainty index for these conditions to 15, except as indicated. Reason for bad data SI UI RSB night mode 65535 255 L1A DN is missing 65534 15 Detector is saturated 65533 15 Cannot compute zero point DN 65532 15 Detector is dead 65531 15 RSB dn* below bottom end of range for writing to scaled integer 65530 15 TEB radiance below 0 65529 15 Other calibration failure 65528 15 In addition, documentation should make clear that the UI is written to the four least significant bits of an 8-bit word. ============================================================================ ============================================================================ L1B V2.1.1 3/1/1999 ============================================================================ ============================================================================ CCR 457: December 23, 1998 Approved: January 11, 1999 Changes Requested for L1B V2.1.1 EV 1KM File Specification: 1 3 descriptive sentences immediately under title bar: Replace these sentences with: "This document specifies the format for the MODIS Level 1B 1km earth-view (EV) product. The product is implemented in an HDF file." Justification: The current description is not a description of the file spec itself. Reference to where the file specification can be obtained should be provided in the User's Manual. 2 Contents: add item III) Band-subsetting SDSs. Justification: we propose to add a description of the band-subsetting SDS currently being written to the product. 3 Contents: add item IV) Geolocation SDSs Justification: we propose to add a description of the geolocation SDSs currently being written to the product. 4 Section I) Global Metadata, under Contents: delete the subsections contents lines 1.5.1 and 1.5.2. Justification: there is only one section, 1.5, and there is no need for subsections. 5 Section 1.3, MODIS Level 1B Product Granule Metadata, item Focal Plane Set Point State: change the description of "0=Running open loop" to "0=Running uncontrolled". Justification: the term "uncontrolled" is the correct term according to Ed Knight. The algorithm itself is unchanged. 6 Section 1.3, MODIS Level 1B Product Granule Metadata: delete "Note 1" and "Note 2". Justification: These notes are not needed to understand the data format, and only serve to unnecessarily lengthen the L1B file specs. They also are described in the L1B Product User's Guide. 7 Section 1.3, MODIS Level 1B Product Granule Metadata, just below the table for Electronics Redundancy Vector: delete the "note". Justification: the explanation is already included in within the heading of the table itself and the note is redundant. 8 Section 1.5, Level 1B HDF-EOS SWATH Metadata: delete the subsection title bar just below the section title bar. Justification: there is only one section for section 1.5 and there is no need for a subsection. 9 Section 1.6, Level 1B Swath Metadata: Delete the field "No. thermistor outliers". Justification: the next item, "No. of OBC BB thermistor outliers" represents the same information according to Ed Knight. This will result in a change to the code. Currently, a stub is written for "No. thermistor outliers". That stub would be deleted from the code. 10 Section 1.6, Level 1B Swath Metadata: Change the description of the Bit QA Flags to "(see table below)". Justification: The current description is not correct as it is written. 11 Section 1.6, Level 1B Swath Metadata, Notes section: delete notes 1 and 4, renumber notes 2 and 3 to be 1 and 2, respectively. Justification: These notes are not needed to understand the data format, and only serve to unnecessarily lengthen the L1B file specs. They also are described in the L1B Product User's Guide. 12 Section II, description: change the "indices of the samples used..." to "number of samples used ...". Justification: Make the description accurate. The actual values in the "Samples_Used" SDSs are the number of samples used, not indices. 13 Section II, item 2.1, Composite index map: Delete item 2.1 and renumber the other items accordingly. Add a shorter, more accurate description to the description section. Justification: Item 2.1 is unnecessarily long and has some misleading information and information from all the products mixed in it. 14 Section 2.4 (old number), EV_250_Aggr1km_RefSB_Samples_Used: change the description from "indices of " to "number of ". Also change the attribute value of valid_range to "0, 28". Justification: The correct meaning is number of samples, not indices of the samples. Also, the maximum number of samples used could be 28, not 3. The file spec description is wrong, the code is OK. 15 Section 2.7 (old number), EV_500_Aggr1km_RefSB_Samples_Used: change the description from "indices of " to "number of ". Also change the attribute value of valid_range to "0, 6". Justification: The correct meaning is number of samples, not indices of the samples. Also, the maximum number of samples used could be 6, not 3. The file spec description is wrong, the code is OK. 16 After Section II: Add Section III) Band-Subsetting SDSs and add a description of the "Band_250M", "Band_500", "Band_1KM_RefSB", and "Band_1KM_Emissive" SDSs and their attribute (long_name). Justification: The description of the these SDSs needs to be added because they are SDSs that are written to the product file. While the L1B code currently writes out the SDSs, it does not write out any attributes. Therefore, adding a long_name attribute involves adding that to the code. 17 After Section III: Change Section III to Section IV) Geolocation SDSs and renumber accordingly. 18 Sections 3.6 and 3.7 (old numbers): change the descriptions for SolarZenith and SolarAzimuth to correct descriptions. Justification: the current descriptions are copies of the description of the range and are therefore incorrect. 19 Geolocation subsections: renumber starting at .1. Justification: consistency with all other subsection numberings.