<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<?xml-model href="https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1J00.sch" schematypens="http://purl.oclc.org/dsdl/schematron"?>

<Product_Observational xmlns="http://pds.nasa.gov/pds4/pds/v1" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:schemaLocation="http://pds.nasa.gov/pds4/pds/v1 https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1J00.xsd">
  <Identification_Area>
    <logical_identifier>urn:nasa:pds:clementine1_gravity_and_topography:topography_data:gltm2bpr</logical_identifier>
    <version_id>1.0</version_id>
    <title>Clementine 1: Topographic Profiles</title>
    <information_model_version>1.19.0.0</information_model_version>
    <product_class>Product_Observational</product_class>
    <Modification_History>
      <Modification_Detail>
        <modification_date>2023-02-13</modification_date>
        <version_id>1.0</version_id>
        <description>PDS4 migrated product.</description>
      </Modification_Detail>
    </Modification_History>
  </Identification_Area>
  <Observation_Area>
    <Time_Coordinates>
      <start_date_time xsi:nil="true" nilReason="inapplicable"></start_date_time>
      <stop_date_time xsi:nil="true" nilReason="inapplicable"></stop_date_time>
    </Time_Coordinates>
    <Investigation_Area>
      <name>Deep Space Program Science Experiment</name>
      <type>Mission</type>
      <Internal_Reference>
        <lid_reference>urn:nasa:pds:context:investigation:mission.deep_space_program_science_experiment</lid_reference>
        <reference_type>data_to_investigation</reference_type>
        <comment>Clementine 1</comment>
      </Internal_Reference>
    </Investigation_Area>
    <Observing_System>
      <Observing_System_Component>
        <name>Clementine 1</name>
        <type>Host</type>
        <Internal_Reference>
          <lid_reference>urn:nasa:pds:context:instrument_host:spacecraft.clem1</lid_reference>
          <reference_type>is_instrument_host</reference_type>
        </Internal_Reference>
      </Observing_System_Component>
      <Observing_System_Component>
        <name>LIDAR High-Resolution Imager</name>
        <type>Instrument</type>
        <Internal_Reference>
          <lid_reference>urn:nasa:pds:context:instrument:clem1.lidar</lid_reference>
          <reference_type>is_instrument</reference_type>
        </Internal_Reference>
      </Observing_System_Component>
    </Observing_System>
    <Target_Identification>
      <name>Moon</name>
      <type>Satellite</type>
      <Internal_Reference>
        <lid_reference>urn:nasa:pds:context:target:satellite.earth.moon</lid_reference>
        <reference_type>data_to_target</reference_type>
      </Internal_Reference>
    </Target_Identification>
  </Observation_Area>
  
  <File_Area_Observational>
    <File>
      <file_name>gltm2bpr.tab</file_name>
      <comment>
        This file contains
        topographic profiles and related data along each observational
        pass during which LIDAR laser range data were acquired.  The data
        were created using the final spacecraft orientation and orbital
        solutions.  The laser ranges are believed to be correct, but
        there may be unresolvable ambiguities due to noise.
      </comment>
    </File>
    <Table_Character>
      <offset unit="byte">0</offset>
      <records>72548</records>
      <description>
        The GLTM-2B profiles table
        contains the laser ranges and related data for each orbit
        profile. Each row in the table contains the date/times,
        positions of laser bounce points, relative elevations,
        revolution number, and trigger bins. The (delimited) data
        require 80 ASCII characters; these are followed by a pad of 2
        unspecified ASCII characters, an ASCII carriage-return, and an
        ASCII line-feed.
      </description>
      <record_delimiter>Carriage-Return Line-Feed</record_delimiter>
      <Record_Character>
        <fields>9</fields>
        <groups>0</groups>
        <record_length unit="byte">84</record_length>
        <Field_Character>
          <name>universal time</name>
          <field_number>1</field_number>
          <field_location unit="byte">1</field_location>
          <data_type>ASCII_Date_Time_YMD</data_type>
          <field_length unit="byte">23</field_length>
          <description>
            The date and time of the laser fire, in Universal Time 
            Coordinates (UTC), for that point in the orbit.
          </description>
        </Field_Character>
        <Field_Character>
          <name>longitude</name>
          <field_number>2</field_number>
          <field_location unit="byte">25</field_location>
          <data_type>ASCII_Real</data_type>
          <field_length unit="byte">9</field_length>
          <unit>degree</unit>
          <description>
            The longitude of the laser bounce point, in IAU body-fixed 
            coordinates. Positive longitude direction is east.
          </description>
        </Field_Character>
        <Field_Character>
          <name>latitude</name>
          <field_number>3</field_number>
          <field_location unit="byte">35</field_location>
          <data_type>ASCII_Real</data_type>
          <field_length unit="byte">9</field_length>
          <unit>degree</unit>
          <description>
            The latitude of the laser bounce point, in IAU body-fixed 
            coordinates.
          </description>
        </Field_Character>
        <Field_Character>
          <name>elevation</name>
          <field_number>4</field_number>
          <field_location unit="byte">45</field_location>
          <data_type>ASCII_Real</data_type>
          <field_length unit="byte">8</field_length>
          <unit>meter</unit>
          <description>
            The elevation in meters above a spheroid of radius 1738 km 
            at the equator, with a flattening of 1/3234.93 corresponding 
            to the flattening of the geoid.
          </description>
        </Field_Character>
        <Field_Character>
          <name>relative elevation</name>
          <field_number>5</field_number>
          <field_location unit="byte">54</field_location>
          <data_type>ASCII_Real</data_type>
          <field_length unit="byte">8</field_length>
          <unit>meter</unit>          
          <description>
            The elevation in meters relative to a 1738 km radius sphere.
          </description>
        </Field_Character>
        <Field_Character>
          <name>revolution number</name>
          <field_number>6</field_number>
          <field_location unit="byte">63</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            The revolution during which data were acquired for that 
            point.  The revolutions included are from 20-332.  Ranges 
            acquired on calibration passes 8-19 were discarded as too 
            noisy.
          </description>
        </Field_Character>
        <Field_Character>
          <name>bin</name>
          <field_number>7</field_number>
          <field_location unit="byte">68</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            A number designating whether
            the data are the result of a trigger before (0), inside
            (1-4), or after (5) the range window.  The lidar
            electronics triggered on photon pulses continuously, and
            recorded up to four pulses within a programmable range
            window.  The last trigger before and the first trigger after
            the range window were also recorded.  Usually, but not
            always, the first trigger within the range window was the
            valid range.  For some laser shots, multiple pulses were
            detected within the expected time interval for lunar
            reflections.  At most one of these pulses is designated valid
            in this archive.
          </description>
        </Field_Character>
        <Field_Character>
          <name>new bin</name>
          <field_number>8</field_number>
          <field_location unit="byte">71</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Many triggers occurred due to
            noise in the electronics and could not possibly have resulted
            from lunar surface reflections.  Those triggers that could
            have resulted from topography within a +/- 12 km distance
            from the reference lunar spheroid (see elevations, column 4)
            were assigned bins from 1 to 4.  These bins were used as
            weights in the filtering procedure (Smith et al., The
            Topography of the Moon from the Clementine LIDAR, submitted
            to Journal of Geophysical Research, 1995).  These weights
            corresponded to a value of sigma = NEWBIN * (1 km), for each
            trigger.  The filter iteratively estimates the topography,
            with an a priori covariance function given by
            cov(R) = (5 km)^2 * exp(-R/170), where R is distance in km
            between any two points on the Moon.  The filter passes ranges
            within 2.0 sigma of the predicted range.
          </description>
        </Field_Character>
        <Field_Character>
          <name>nadir angle</name>
          <field_number>9</field_number>
          <field_location unit="byte">74</field_location>
          <data_type>ASCII_Real</data_type>
          <field_length unit="byte">7</field_length>
          <unit>degree</unit>
          <description>
            The angle off nadir,
            calculated from spacecraft quaternion data using star
            tracking.  A number of passes were intentionally pointed
            off-nadir in order to cover previously skipped regions, and
            in some cases spacecraft commands inadvertently resulted in
            off-nadir pointing.  Where quaternion data were missing, the
            interpolation software generated spurious angles, but the
            lidar is assumed to be nominally nadir-pointing, as the
            ranges appear valid.  Angles greater than 15 degrees
            correspond to missing quaternion data.
          </description>
        </Field_Character>
      </Record_Character>
    </Table_Character>
  </File_Area_Observational>

  <File_Area_Observational_Supplemental>
    <File>
      <file_name>gltm2bpr.lbl</file_name>
    </File>
    <Stream_Text>
      <offset unit="byte">0</offset>
      <parsing_standard_id>PDS3</parsing_standard_id>
      <description>Original PDS3 label</description>
      <record_delimiter>Carriage-Return Line-Feed</record_delimiter>
    </Stream_Text>
  </File_Area_Observational_Supplemental>
</Product_Observational>
