USGS - science for a changing world
National Park Service Home Page.

Biology - Biological Informatics Program - Vegetation Characterization Program

Spatial Vegetation Data FAQ Metadata

Frequently-anticipated questions:


What does this data set describe?

Title:
Zion National Park Vegetation Mapping Project - Spatial Vegetation Data
Abstract:
This metadata is for the vegetation and land-use geo-spatial database for Zion National Park and surrounding areas. The project is authorized as part of the USGS/NPS Vegetation Mapping Program. The program is being administered by the Core Science Systems (CSS), United States Geological Survey (USGS). The USGS/CSS is responsible for overall management and oversight of all ongoing mapping efforts. This mapping effort was performed by the U.S. Bureau of Reclamation's (USBR) Remote Sensing and GIS Group, Technical Service Center, Denver, Colorado and NatureServe (formally The Nature Conservancy). The vegetation mapping program is part of a larger Inventory and Monitoring (I&M) program started by the National Park Service (NPS).
  1. How should this data set be cited?

    USBR Remote Sensing and GIS Group, Denver, Colorado, Unpublished Material, Zion National Park Vegetation Mapping Project Vegetation Coverage.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -113.25564
    East_Bounding_Coordinate: -112.823821
    North_Bounding_Coordinate: 37.532
    South_Bounding_Coordinate: 37.106056
    Description_of_Geographic_Extent: Zion National Park and environs

  3. What does it look like?

    <http://biology.usgs.gov/npsveg/zion/images/zionvegmap.pdf> (PDF)
    Graphic file showing vegetation distribution of Zion NP. Low resolution for web browser.
    <http://biology.usgs.gov/npsveg/zion/images/zionvegmap_poster.pdf> (PDF)
    Graphic file showing vegetation distribution of Zion NP and environs, by ecological subgroups. High resolution for web browser.

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: 22-Jun-1999
    Currentness_Reference: ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: map: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • Complete chain (123530)
      • Label point (41337)
      • GT-polygon composed of chains (41337)

    2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 12
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -111
      Latitude_of_Projection_Origin: 0
      False_Easting: 500000
      False_Northing: 0

      Planar coordinates are encoded using Coordinate Pair
      Abscissae (x-coordinates) are specified to the nearest 0.000499
      Ordinates (y-coordinates) are specified to the nearest 0.000499
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257.

  7. How does the data set describe geographic features?

    Entity_and_Attribute_Overview:
    Attributes were either generated by ArcInfo or assigned by the USBR Remote Sensing GIS Group.
    Entity_and_Attribute_Detail_Citation:
    Zion National Park Vegetation Mapping Project Final Report (DOI - USGS/USBR)
    zion_veg.aat
    Zion National Park Vegetation Mapping Project: Vegetation Coverage Arc Attribute Table (Source: Dan Cogan USBR Remote Sensing and GIS Group)

    DIGTYPE
    Arc (line) attribute - denotes how the arc was entered/created. Denotes lines that represent Park, Project, and Vegetation polygon boundaries. (Source: USBR Remote Sensing and GIS Group)

    ValueDefinition
    1Represents lines that were drawn using heads-up digitizing.
    2Represents scanned lines that were smoothed.
    3Represents lines that are the project boundary.

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    FNODE#
    Internal node number for the beginning of an arc (from-node). (Source: ESRI)

    Whole numbers that are automatically generated.

    LENGTH
    Length of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    LPOLY#
    Internal node number for the left polygon. (Source: ESRI)

    Whole numbers that are automatically generated.

    RPOLY#
    Internal node number for the right polygon. (Source: ESRI)

    Whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    TNODE#
    Internal node number for the end of an arc (to-node). (Source: ESRI)

    Whole numbers that are automatically generated.

    ZION_VEG#
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    ZION_VEG-ID
    User-defined feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    zion_veg.pat
    Zion National Park Vegetation Mapping Project: Vegetation Coverage Arc Attribute Table (Source: Dan Cogan USBR Remote Sensing and GIS Group)

    ALL_CNAME
    NVCS Alliance Common Name(s) (Source: National Vegetation Classification System)

    Text

    ALL_KEY
    NVCS Alliance Code(s) (Source: National Vegetation Classification System)

    Text

    ALL_NAME
    NVCS Alliance Scientific Name(s) (Source: National Vegetation Classification System)

    Text

    AREA
    Area of feature in internal units (meters) squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    ASN_CEGL
    NVCS Internal Code for Plant Association(s) (Source: National Vegetation Classification System)

    Text

    ASN_CNAME
    NVCS Association Common Name(s) (Part 1) (Source: National Vegetation Classification System)

    Text

    ASN_CNAME2
    NVCS Association Common Name(s) (Part 2) (Source: National Vegetation Classification System)

    Text

    ASN_NAME1
    NVCS Association Scientific Name(s) (Part 1) (Source: National Vegetation Classification System)

    Text

    ASN_NAME2
    NVCS Association Scientific Name(s) (Part 2) (Source: National Vegetation Classification System)

    Text

    ASPEN
    Indicates the presence of aspen in polygon (yes/no). (Source: USBR Remote Sensing and GIS Group)

    ValueDefinition
    YesSingle aspen trees/shrubs were observed in the polygon.
    NoNo single aspen trees/shrubs were observed in the polyogn.

    Text

    BURN
    Indicates the evidence of a recent burn in polygon (yes/no). (Source: USBR Remote Sensing and GIS Group)

    ValueDefinition
    YesEvidence of a recent burn was observed.
    NoNo evidence of a recent burn was observed.

    Text

    CC_GRASS
    Percent canopy cover in the herbaceous stratum. (Source: Zion National Park)

    ValueDefinition
    N/AThis attribute was not applicable for this vegetation or land-cover type.
    0-5%Canopy cover of the herbaceous stratum is estimated to be greater than 0 but less than 5%.
    5-25%Canopy cover of the herbaceous stratum is estimated to be greater than 5% but less than 25%.
    25-50%Canopy cover of the herbaceous stratum is estimated to be greater than 25% but less than 50%.
    50-75%Canopy cover of the herbaceous stratum is estimated to be greater than 50% but less than 75%.
    75-100%Canopy cover of the herbaceous stratum is estimated to be greater than 75%.

    Percentage and Text

    CC_SHRUB
    Percent canopy cover in the shrub stratum. (Source: Zion National Park)

    ValueDefinition
    N/AThis attribute was not applicable for this vegetation or land-cover type.
    0-5%Canopy cover of the shrub stratum is estimated to be greater than 0 but less than 5%.
    5-25%Canopy cover of the shrub stratum is estimated to be greater than 5% but less than 25%.
    25-50%Canopy cover of the shrub stratum is estimated to be greater than 25% but less than 50%.
    50-75%Canopy cover of the shrub stratum is estimated to be greater than 50% but less than 75%.
    75-100%Canopy cover of the shrub stratum is estimated to be greater than 75%.

    Percentage and Text

    CC_TREE
    Percent canopy cover in the tree stratum. (Source: Zion National Park)

    ValueDefinition
    N/AThis attribute was not applicable for this vegetation or land-cover type.
    0-5%Canopy cover of the tree stratum is estimated to be greater than 0 but less than 5%.
    5-25%Canopy cover of the tree stratum is estimated to be greater than 5% but less than 25%.
    25-50%Canopy cover of the tree stratum is estimated to be greater than 25% but less than 50%.
    50-75%Canopy cover of the tree stratum is estimated to be greater than 50% but less than 75%.
    75-100%Canopy cover of the tree stratum is estimated to be greater than 75%.

    Percentage and Text

    CLASS
    NVCS Class Name(s) and Code(s) (Source: National Vegetation Classification System)

    Text

    COMMENT1
    General description of the map unit. (Source: USBR Remote Sensing and GIS Group)

    Text

    COMMENT2
    General comment describing how the map unit relates to other map units. (Source: USBR Remote Sensing and GIS Group)

    Text

    ECO_CODE
    Ecological Systems Classification Code (Source: NatureServe Ecological Classification)

    Numeric

    ECO_NAME
    Ecological Systems Classification Name (Source: NatureServe Ecological Classification)

    Text

    ECOLOGY
    Ecological description of the polygon (Source: USBR Remote Sensing and GIS Group)

    ValueDefinition
    Coniferous ForestThis type is dominated by conifer trees forming a closed canopy.
    Coniferous WoodlandThis type is dominated by conifer trees forming an open or discontinous canopy.
    Deciduous ForestThis type is dominated by deciduous trees forming a closed canopy.
    Floodplain WoodlandThis type is dominated by deciduous trees forming an open or discontinous canopy alongside rivers and streams.
    Land-useThis type contains obvious human-disturbed lands, natural streams and water bodies, and other non-vegetation lands.
    Mesic GrasslandThis type contains herbaceous graminoids and forbs found on wet soils.
    Riparian ShrublandThis type contains shrubs common on mesic soils associated with floodplains and waterways.
    Unvegetation SurfaceThis type represents all of the barren rock and geologic formations that support very little, if any vegetation.
    Upland GrasslandThis type is dominated by graminoids common to arid and semi-arid soils.
    Upland ShrublandThis type contains shrubs common to dry slopes, plains, and mesa tops.
    Wetland Herbaceous VegetationThis type is dominated by herbaceous plants common on saturated soils in and around bodies of water.
    Xeric ShrublandThis type is dominated by shrubs common to very arid slopes and other desert areas.

    Text

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    FORMATION
    NVCS Formation Name(s) (Source: National Vegetation Classification System)

    Text

    GROUP
    NVCS Group Name(s) and Code(s) (Source: National Vegetation Classification System)

    Text

    HGT_CLASS
    Height class (range) of the upper strata. (Source: USBR Remote Sensing and GIS Group and Zion National Park)

    ValueDefinition
    N/AThis attribute was not applicable for this vegetation or land-cover type.
    0-2 metersHeight of the tallest stratum is estimated to be greater than 0 but less than 2 meters.
    2-5 metersHeight of the tallest stratum is estimated to be greater than 2 but less than 5 meters.
    5-10 metersHeight of the tallest stratum is estimated to be greater than 5 but less than 10 meters.
    10-20 metersHeight of the tallest stratum is estimated to be greater than 10 but less than 20 meters.
    > 20 metersHeight of the tallest stratum is estimated to be greater than 20 meters.

    Text

    LOCATION
    Location of the polygon in relation to Zion National Park and the project's environs buffer). (Source: USBR Remote Sensing and GIS Group)

    Text

    LUC_II
    Land use and land cover classification system name for the polygon. (Source: Anderson, J.R., E.E. Hardy, J.T. Roach, R.E. Witmer. 1976. Land use and land cover classification system for use with remote sensor data. Geological Survey Professional Paper 964. Washington, D.C.: US Government Printing Office.)

    Text

    NVCS_CODE
    NVCS Code(s) to the formation level (Source: National Vegetation Classification System)

    Text

    NWI_CLASS
    National Wetlands Inventory Classification Class Name (Source: Cowardian et al. 1979. Classification of Wetlands and Deepwater Habitats of the United States. US Fish and Wildlife Service National Wetlands Inventory.)

    Text

    NWI_SPEC-M
    National Wetlands Inventory Classification Sub-system Label (Source: Cowardian et al. 1979. Classification of Wetlands and Deepwater Habitats of the United States. US Fish and Wildlife Service National Wetlands Inventory.)

    Text

    NWI_SUB-S
    National Wetlands Inventory Classification Sub-system Label (Source: Cowardian et al. 1979. Classification of Wetlands and Deepwater Habitats of the United States. US Fish and Wildlife Service National Wetlands Inventory.)

    Text

    NWI_SYS
    National Wetlands Inventory Classification System Label (Source: Cowardian et al. 1979. Classification of Wetlands and Deepwater Habitats of the United States. US Fish and Wildlife Service National Wetlands Inventory.)

    Text

    PERIMETER
    Perimeter of feature in internal units (meters). (Source: ESRI)

    Positive real numbers that are automatically generated.

    PHOTO
    Corresponding Ortho-photo Sheet Number (Source: USBR Remote Sensing and GIS Group and Horizon's Inc.)

    Text

    PHYSIO
    Physiographic description of the polygon (Source: USBR Remote Sensing and GIS Group)

    ValueDefinition
    AgriculturalThis type represents areas with obvious evidence of current or past agricultural activity.
    BarrenThis type represents very sparse or completely unvegetated areas.
    ForestThis type represents areas that are dominated by trees forming a closed canopy.
    Herbaceous VegetationThis type includes all areas that are graminoid or forb dominated.
    ImpoundmentsThis represents ponds, lakes, and other standing bodies of water.
    Land-UseThis type represents areas that have been obviously altered by human activity.
    ShrublandThis type represents areas dominated by shrubs.
    StreamsThis type represents canals, intermittent streams, perennial streams, and other moving bodies of water.
    WoodlandThis type represents areas that are dominated by trees forming an open or discontinuous canopy.

    Text

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    SUBCLASS
    NVCS Subclass Name(s) and Code(s) (Source: National Vegetation Classification System)

    Text

    SUBGROUP
    NVCS Subgroup Name(s) and Code(s) (Source: National Vegetation Classification System)

    Text

    VEG_CNAME
    Map Unit Common Name (Source: USBR Remote Sensing and GIS Group)

    Text

    VEG_CODE
    Map Unit Code (Source: USBR Remote Sensing and GIS Group)

    Positive real numbers assigned by USBR Remote Sensing and GIS Group

    VEG_NAME
    Map Unit Scientific Name (Source: USBR Remote Sensing and GIS Group)

    Text

    VEG_PAT
    Vegetation pattern within the polygon (Source: USBR Remote Sensing and GIS Group and Zion National Park)

    ValueDefinition
    Clumpled/patchyThe general pattern of the vegetation was considered to occur in obvious stands/clumps/patches with irregular openings between each stand.
    HomogeneousThe general pattern of the vegetation was considered to be consistent and continuous across the entire polyon.
    LinearThe general pattern of the vegetation was considered to occur along a line and/or in descrete rows.
    N/AThis attribute was not applicable for this vegetation or land-cover type.

    Text

    ZION_VEG#
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    ZION_VEG-ID
    User-defined feature number. (Source: ESRI)

    Sequential whole numbers

  8. What biological taxa does this data set concern?

    Taxonomy:
    Keywords/Taxon:
    Taxonomic_Keyword_Thesaurus: None
    Taxonomic_Keywords: Standardized National Vegetation Classification System
    Taxonomic_Keywords: vegetation classification
    Taxonomic_Keywords: alliance
    Taxonomic_Keywords: community association
    Taxonomic_Classification:
    Taxon_Rank_Name: Kingdom
    Taxon_Rank_Value: Plantae


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

    • USBR Remote Sensing and GIS Group, Denver, Colorado

  2. Who also contributed to the data set?

    USBR, Denver, Colorado: Daniel Cogan, Janet Coles, Doug Crawford, Trudy Meyer, and Mike Pucherelli.

  3. To whom should users address questions about the data?

    Bureau of Reclamation
    c/o Dan Cogan
    Physical Scientist
    P.O. Box 25007 Bldg. 56 Denver Federal Center M.S. D-8260
    Denver, Colorado 80225
    U.S.A

    303-445-2291 (voice)
    303-445-6337 (FAX)
    dcogan@do.usbr.gov

    Hours_of_Service: 8 am - 5 pm


Why was the data set created?

The purposes of the mapping effort are varied and include the following: Provides support for NPS Resources Management; Promotes vegetation-related research for both NPS and USGS/CSS; Provides support for NPS Planning and Compliance; Adds to the information base for NPS Interpretation; and Assists in NPS Operations. The NPS I&M goals are, among others, to consistently map and document the vegetation of all National Park Service units with a resource component, thereby creating a baseline vegetation inventory.


How was the data set created?

  1. From what previous works were the data drawn?

    Zion Ortho-photo (source 1 of 1)
    Horizons, Inc., 19991217, Zion National Park, Utah Orthophotos.

    Type_of_Source_Media: AGFA N400 photographic film
    Source_Scale_Denominator: 40000
    Source_Contribution: Unknown

  2. How were the data generated, processed, and modified?

    Date: 2002 (process 1 of 1)
    MAP CLASSES: Vegetation classification was in accordance with the standards developed under the USGS/NPS Vegetation Mapping Program using the National Vegetation Classification Standard. Field work (collecting plot data) aided in the development of the vegetation classes. In addition, the Park had specific types that were also mapped. PHOTO INTERPRETATION: All map classes were interpreted from 1:12,000-scale, true color aerial photography and 1:12,000-scale true color ortho-rectified photography (ortho-photos). Photo-interpretation used the standard identification features such as tone, texture, color, pattern, topographic position, and shadow. In addition, field sample locations and their vegetation descriptions aided in assigning a map class to each polygon. Photographs were examined using a stereoscope as needed. Linework was created on mylars placed over both the aerial photos and the ortho-photos. GIS PROCEDURES: The linework on the mylar ortho-photo overlays were transferred into the GIS database by one of two methods, either heads-up digitizing or scanning. METHOD I: Heads-up digitizing is a procedure whereby the operator digitizes by hand and eye on a computer terminal screen showing a digital image of an ortho-rectified photo. By looking at similar features on both the aerial photograph and on the orthophoto, the line drawn on the aerial photo overlay is manually transferred to the digital image. METHOD II: The majority of the linework at Zion was transferred via scanning the ortho-photo mylar overlays using a large-format color scanner. Before the mylar was scanned, it was marked with control points that correspond to the 1000-meter grid embossed on the hard-copy ortho-photos. GIS software was then used to convert the scanned files from a raster to vector base using centerline commands. Extensive cleaning, edge matching, and general editing of the digital vectors was completed before polygon topology was created. Labels were created for each polygon and they were attributed with the necessary vegetation information. The entire transfer and editing sequence was automated via in-house Arc/INFO AML programs. OTHER DATA: The mapping project (proj_bndry) and park boundary (park_bndry) coverages were acquired from the Park. A flight line coverage (zion_flight) was obtained from the photography vendor. Field Observation, Plot, and Accuracy Assessment data point coverages (zion_obs, zion_plots, and zion_aa) were created by entering points with the 'generate' command using a text file of points and x-y coordinates.

    Person who carried out this activity:

    Dan Cogan
    Bureau of Reclamation
    Physical Scientist
    P.O. Box 25007 Bldg. 56 Denver Federal Center M.S. D-8260
    Denver, Colorado 80225
    U.S.A

    303-445-2291 (voice)
    303-445-6337 (FAX)
    dcogan@do.usbr.gov

    Hours_of_Service: 8 am - 5 pm
  3. What similar or related data should the user be aware of?


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    The thematic accuracy is approximately 81%. Please read the accompanying report or check with Zion National Park for the latest accuracy assessment values.

  2. How accurate are the geographic locations?

    (Unknown, Zion ortho-photo basemap, reference Zion ortho-photo metadata.)

  3. How accurate are the heights or depths?

    (Unknown, Zion ortho-photo basemap, reference Zion ortho-photo metadata.)

  4. Where are the gaps in the data? What is missing?

    All data that could be interpreted from the aerial photos were digitized in accordance with the minimum mapping unit (MMU) of 1/2 hectare. This included selected features that fell into the National Vegetation Classification and the Anderson Level II land use classification. Some classes below the MMU were included, especially water and wetland features and those at the edge of the study area (i.e. cut off by other features and borders). Roads (to visible right-of-way or fence line) and streams/drainages wider than 10 meters were digitized as polygons and attributed accordingly.

  5. How consistent are the relationships among the observations, including topology?

    All polygon features were checked for topology, existence of label points, and label point uniqueness. The labels were checked for correct and complete attributing. All nodes where checked for unintentional lines and to ensure that the polygons were closed. All steps preformed using ESRI ArcInfo commands.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:
Acknowledgment of the USGS and U.S. Bureau of Reclamation Remote Sensing and GIS Group would be appreciated in products derived from these data. Any person using the information presented here should fully understand the data collection and compilation before beginning analysis. The burden for determining fitness for use lies entirely with the user.

  1. Who distributes the data set? (Distributor 1 of 1)

    USGS/CSS/Core Science Analytics and Synthesis
    c/o USGS-NPS Vegetation Mapping Program Coordinator
    Denver Federal Center, Building 810, Room 8000, MS 302
    Denver, Colorado 80225

    (303) 202-4220 (voice)
    303-202-4219 (FAX)
    gs-b-npsveg@usgs.gov

  2. What's the catalog number I need to order this data set?

    NPS Vegetation Mapping Program: Vegetation Map of Zion National Park

  3. What legal disclaimers am I supposed to read?

    The U.S. Geological Survey and the National Park Service shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics (if available) are not legal documents and are not intended to be used as such.

    The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. Any related graphics (if available) are intended to aid the data user in acquiring relevant data; it is not approriate to use the related graphics as data.

    The U.S. Geological Survey and the National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an U.S. Geological Survey and National Park Service servers and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data. It is also strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. Mention of trade names or commercial products in this metadata report does not constitute endorsement or recommendation for use by the U. S. Department of the Interior, U. S. Geological Survey and National Park Service.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 24-Feb-2004
Last Reviewed: 21-Jun-2010
Metadata author:
USGS/CSS/Core Science Analytics and Synthesis
c/o USGS-NPS Vegetation Mapping Program Coordinator
Denver Federal Center, Building 810, Room 8000, MS 302
Denver, Colorado 80225

(303) 202-4220 (voice)
303-202-4219 (FAX)
gs-b-npsveg@usgs.gov

Metadata standard:
FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata (FGDC-STD-001.1-1999)
Metadata extensions used:


Generated by mp version 2.9.12 on Mon Jun 21 15:33:36 2010

Return to USGS Vegetation Characterization Program at Zion National Park
USGS Home :: Geology :: Geography :: Water
Accessibility FOIA Privacy Policies and Notices
Take Pride in America logo USA.gov logo U.S. Department of the Interior | U.S. Geological Survey
URL: biology.usgs.gov/npsveg/zion/metazionspatial.faq.html
Page Contact Information:gs-b-npsveg@usgs.gov
Page Last Modified: Sunday, 29-Jan-2012 15:06:18 MST