Phoenix Informal Metadata file:

*******************************************************************
This informal metadata files contains the following information:
Section 1 -> Landsat image acquisition information
Section 2 -> Geographic information
Section 3 -> Data processing information
Section 4 -> File formats and naming conventions
Section 5 -> Background information
*******************************************************************

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
SECTION 1   IMAGE ACQUISITION DATA

All Landsat data used on this site are part of the Landsat GeoCover collection.
For more information on the Landsat GeoCover project please visit:
http://glcf.umiacs.umd.edu/portal/geocover/

All data on this website were collected approximately a decade apart.
The Landsat 5 Thematic Mapper (TM) data were acquired circa 1990 while the
Landsat 7 Enhanced Thematic Mapper (ETM+) data were collected circa 2000.

The exact collection dates for the Phoenix data are:
Landsat 7:  19 April 2000
Landsat 5:  18 March 1991
Landsat 1:  29 April 1979

Landsat scenes are identified by their unique Path and Row location.  
Path and Row are identifiers of the Landsat World Reference System (WRS-2).  
For more in depth information about the WRS, please visit:
http://ltpwww.gsfc.nasa.gov/IAS/handbook/handbook_htmls/chapter5/chapter5.html#section5.3

The Path/Row for the Phoenix scenes are:
Path 37
Row 37

These data have been subset to a 2000 by 2000 pixel area surrounding Phoenix.

For the L1 MSS data, the WRS-1 Path and Row are:
Path 40
Row 37

The Phoenix metropolitan area falls in the top right corner of the WRS-1 Path 40 Row 37 scene, therefore, it does not have data for the entire 2000 x 2000 extent as found in the Landsat 5 and 7 subsets. Hence, you will find null (black) pixels on the top and right sides of the 1979 image. 

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
SECTION 2   GEOGRAPHIC INFORMTION**

All GeoCover data have been orthorectified.  
Phoenix data are provided in the Universal Transverse Mercator (UTM) projection.  
Phoenix is in UTM Zone 12 North.  Pixel size for all bands is 28.5 m.  This includes the Landsat 7 ETM+ thermal band that has been resampled from its 57 m resolution and the Landsat 5 TM thermal band that has been resampled from its 114 m resolution and the 1979 MSS data that has been resampled from its 57 m resolution.

Image Corners in Geographic decimal degrees (latitude, longitude):
Upper Left: 33.75011111, -112.36109722
Upper Right: 33.75536111, -111.74605556
Lower Left: 33.23639167, -112.35308056
Lower Right: 33.24153889, -111.74166111



**NOTE data files are in GeoTIFF format, so MultiSpec(tm) will automatically parse the geographic information.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
SECTION 3 DATA PROCESSING

Geographic Processing
All data were geographically subset.  Therefore, pixel 1,1 of the Landsat 7 image "geographically matches" (is registered with) pixel 1,1 of the Landsat 5 and Landsat 1 data. 
This geographic matching enables accurate change detection monitoring.

Atmospheric Processing
To correct for varying atmospheric conditions a dark-object subtraction technique was used on the visible ETM+ and TM bands (3, 2, and 1).

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
SECTION 4   FILE FORMATS AND NAMING CONVENTIONS

All Landsat satellite imagery files are in TIFF format.

The naming convention for the data TIFF files is:
YYYY.MM.DD_P##R##_PLACE.tif

Where:
	YYYY = the four digit year of image acquisition
	MM = the two digit month of image acquisition
	DD = the two digit day of image acquisition
	P## = WRS Path number
	R## = WRS Row number
	PLACE = a five letter identifier of geographic location

Each data file has an accompanying TIFF World File that contains additional geographic information.  The naming convention for this file is the same except for the .tfw extension.

Both the Landsat 7 ETM+ and Landsat 5 TM data files contain seven 
data channels in Band Sequential (BSQ) order.

The band order is as follows:
Band 1 = Landsat 7 ETM+ (or L5 TM) channel 1 (Blue, 0.45 - 0.52 um)
Band 2 = Landsat 7 ETM+ (or L5 TM) channel 2 (Green, 0.52 - 0.60 um)
Band 3 = Landsat 7 ETM+ (or L5 TM) channel 3 (Red, 0.63 - 0.69 um)
Band 4 = Landsat 7 ETM+ (or L5 TM) channel 4 (Near Infrared, 0.76 - 0.90 um)
Band 5 = Landsat 7 ETM+ (or L5 TM) channel 5 (Mid Infrared, 1.55 - 1.75 um)
Band 6 = Landsat 7 ETM+ (or L5 TM) channel 6 (Thermal Band, 10.4 - 12.5 um)
Band 7 = Landsat 7 ETM+ (or L5 TM) channel 7 (Mid Infrared, 2.08 - 2.35 um) 

The Landsat 1 MSS data files contain four data channels in Band Sequential (BSQ) order.  The band order for the MSS data is as follows:
Band 1 = Landsat 1 MSS channel 4 (Green, 0.5 - 0.6 um)
Band 2 = Landsat 1 MSS channel 5 (Red, 0.6 - 0.7 um)
Band 3 = Landsat 1 MSS channel 6 (Near Infrared, 0.7 - 0.8 um)
Band 4 = Landsat 1 MSS channel 7 (Near Infrared, 0.8 - 1.1 um)

*** *** *** *** 
We have also included a number of standard 3 band (RGB) TIFFs that use various
common combinations of Landsat bands.

The naming convention for these common TIFF files is:
PLACEYYYY-RGB.tif
Where:
	PLACE = five letter place identifier
	YYYY = four digit year of image acquisition
	R = the Landsat band used in the red channel 
	G = the Landsat band used in the green channel 
	B = the Landsat band used in the blue channel 

To learn how to make your own three band composite images in MultiSpec(tm), visit:
http://observe.arc.nasa.gov/nasa/education/tools/stepby/hwtolan1.html

For general information about composites, visit:
http://landsat.gsfc.nasa.gov/education/compositor/

*** *** *** ***
For both the 1990 and 2000 data sets an image showing NDVI values has been created.  The naming convention for these NDVI TIFF files is:
PLACE_YYYY_NDVI.tif
Where:
	PLACE = five letter place identifier
	YYYY = four digit year of image acquisition

A NDVI change image showing the changes in NDVI values between 1990 and 2000 has also been created for you.  The naming convention for this file is:
PLACE_Y1_Y2_^NDVI.tif
Where:	
	PLACE = five letter place identifier
	Y1 = the two digit year of the first image acquisition
	Y2 = the two digit year of the second image acquisition

For more information about what a NDVI image is and how to create your own NDVI images in MultiSpec(tm), please visit: 
http://growsmart.gsfc.nasa.gov/lessons.html and download the "Create NDVI:  Studying Vegetation from Space" PDF file.

For more information about creating NDVI change images download the 
"Lesson:  Create (Delta)NDVI or Vegetation Loss/Growth Calculation" 
PDF file.

*** *** *** ***
Lastly, a Globe-style land cover change image has been created using the blue band data from both the circa 1990 and circa 2000 images.
The naming convention for this file is:
PLACE_Y1_Y2_CD_181.tif
Where:
	PLACE = five letter place identifier
	Y1 = the two digit year of the first image acquisition
	Y2 = the two digit year of the second image acquisition

For more information about this technique and to make your own blue band change detection files, download the following Globe tutorial:
http://www.globe.gov/tctg/lc_fg_chgdetectutorial.pdf?sectionId=492

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
SECTION 5    GENERAL BACKGROUND INFORMATION

BACKGROUND: The Landsat-7 satellite, launched on April 15, 1999, is the 
most recent addition to NASA's Landsat satellite series.  The first Landsat 
satellite was launched in 1972.  Together, data from the Landsat satellites 
provide over a 30-year record of land cover information.
