Mash Nishihama
Raytheon ITSS
December 13, 2004

                  Control Point Chip File Format
                           Version "002"
                        December 13, 2004

This document describes the format of the chip files that will be used
internally by the land control point matching routines of the MODIS
geolocation software.  This document replaces the previous version (001)
of this document dated October 11, 2004.

The chip files are named based upon the following format, which describes
the satellite data that the chip was obtained from:

MOD03CHP.L.prc..hdf

Where:
  L         -> Stands for Landsat
      -> Date of Aquisition, (4 digits representing calendar year
               followed by 3 digits for the Julian day of year, with leading
               zeros)  Example:  Jan. 1, 1993 = 1993001
      -> Landsat WRS Path Number (3 digits, with leading zeros)
       -> Landsat WRS Row Number (3 digits, with leading zeros)
      -> Sequence number of chip from scene.  (2 digits, with
               leading zeros)  If there are 5 chips from, they will be
               numbered 01, 02, 03, 04, and 05
   -> Chip Format (3 digits, with leading zeros)


The Granule ID in the metadata of the file will be the same as the
filename.

The chip is stored in HDF in four 2-dimensional SD arrays.  See
www.hdf.uiuc.edu for HDF and SD terminology.  These arrays contain the
3-dimensional coordinates of the point in Earth Centered Rotating (ECR)
coordinates and a one-byte intensity value from the TM image.
Each array is the same dimension, nominally 800 samples by 800 lines.
Currently, only one band is stored in the chip files.  Future plans will
allow for multiple bands being stored in the same file.

The arrays are:

  float ECR_x_coordinate_array
  float ECR_y_coordinate_array
  float ECR_z_coordinate_array
  byte  Band_1

There are 12 global SD attributes:
IMAGENAME          -> Name of the image from which the chips were extracted
MAPPROJECTION      -> Map projection code for chips (should be UTM)
DATASOURCE         -> Satellite from which data was aquired

SENSORTYPE         -> Name of sensor on satellite

PIXELSCALE         -> Resolution of the TM pixel in meters
			(New in version 002)
DATALIBRARY        -> Type of processing (MRLC is precision corrected)
	`		(Removed in version 002)

ArchiveMetadata.0  -> ECS required fields (see below)
CoreMetadata.0     -> ECS required fields (see below)
ALGORITHMDATETIME  -> Time that the algorithm was compiled
IDNUMBER           -> Unique 4-digit ID for each chip.  The list of the files
                      corresponding to the When the final list
                      of chips are complete, The PACKINGLIST for MOD_PR03CP
                      will list the ID corresponding to specific files will
                     be index
FEATURELATITUDE    -> Center latitude (in degrees)
FEATURELONGITUDE   -> Center longitude (in degrees)
FEATUREHEIGHT      -> Height above ellipsoid (in meters)
FEATUREECR         -> Array of three coordinates (in meters)

Current chips use TM band 3 for imagery.  Future versions of the chip format
should store this data in the metadata.

The Coremetadata and ArchiveMetadata fields are organized as follows:

CoreMetadata.0:
    GROUP                  = INVENTORYMETADATA
      GROUPTYPE            = MASTERGROUP

      GROUP                  = ECSDATAGRANULE

        OBJECT                 = LOCALGRANULEID
          NUM_VAL              = 1
          VALUE                = 
        END_OBJECT             = LOCALGRANULEID

      END_GROUP              = ECSDATAGRANULE

      GROUP                  = COLLECTIONDESCRIPTIONCLASS

        OBJECT                 = VERSIONID
          NUM_VAL              = 1
          VALUE                = 
        END_OBJECT             = VERSIONID

      END_GROUP              = COLLECTIONDESCRIPTIONCLASS

      GROUP                  = RANGEDATETIME

        OBJECT                 = RANGEENDINGDATETIME
          NUM_VAL              = 1
          VALUE                = "T