Rocky Mountain National Park: Spatial Vegetation Data Metadata

USGS Home
Contact USGS
Search USGS

Biology - Biological Informatics Program - Vegetation Characterization Program

USGS:Biology

Biological Informatics Program

Vegetation Characterization Program

Rocky Mountain National Park

Spatial Vegetation Data Metadata

Metadata also available as - [Questions & Answers] - [Text] - [Adobe Acrobat pdf file]

Identification_Information:

Citation:

Citation_Information:

Originator: National Park Service
Originator: U.S. Bureau of Reclamation
Originator: Colorado Natural Heritage Program/Colorado State University
Publication_Date: 2009
Title:: Rocky Mountain National Park Vegetation Mapping Project - Spatial Vegetation Data
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage:: <http://biology.usgs.gov/npsveg/ftp/vegmapping/romo/romogeodata.zip>

Description:

Abstract:: High resolution vegetation polygons mapped by the National Park Service. This file represents the vegetation at Rocky Mountain National Park (RMNP) as interpreted from October 2001 1:12,000-scale aerial photography. This effort is a part of the National Vegetation Mapping Program of the National Park Service.
Purpose:: Vegetation maps of National Parks and National Monuments were developed to support natural resources management, planning, research and interpretation.
Supplemental_Information:: Data were imported to a file geodatabase by the Colorado Natural Heritage Program/Colorado State University. Parks had the flexibility to map vegetation down to the map class or to the association. Users of this particular dataset and all other datasets of the USGS-NPS Vegetation Monitoring Program Rocky Mountain National Park project are advised to read the report: "Rocky Mountain National Park, Colorado, 2001-2005 VEGETATION CLASSIFICATION AND MAPPING, Final Report - August, 2005, Technical Memorandum 8260-05-02, USBR/RSGIS". This report is available as either a single compiled PDF document, romorpt.pdf, or broken down as a series of PDF documents, and should have been included with these datasets. If not, request a copy from the contact listed in the Distribution_Information section of this metadata. It is the responsibility of any users of these data to actually READ the documentation.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 2001-2005

Currentness_Reference: ground condition

Status:

Progress: Complete
Maintenance_and_Update_Frequency: None planned

Spatial_Domain:

Description_of_Geographic_Extent: Rocky Mountain National Park and environs

Bounding_Coordinates:

West_Bounding_Coordinate: -105.933549
East_Bounding_Coordinate: -105.416952
North_Bounding_Coordinate: 40.567749
South_Bounding_Coordinate: 40.139505

Keywords:

Theme:

Theme_Keyword_Thesaurus: None
Theme_Keyword: Vegetation

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

Access_Constraints:

It is strongly recommended that these data are directly acquired from U.S. Geological Survey and National Park Service servers and not indirectly through other sources which may have changed the data in some way.

Use_Constraints:

This vegetation dataset does NOT include any changes to RMNP vegetation that have occurred due to the large and ongoing mountain pine beetle (Dendroctonus ponderosae) infestation or any other changes to vegetation that may have occured since the October 2001 aerial photo acquisition.

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 tables 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.

The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. Although these data have been processed successfully on a computer system, 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.

Data_Set_Credit:

The U.S. Bureau of Reclamation Remote Sensing and Geographic Information Group (USBR/RSGIG), Denver, CO: David Salas. The acquisition and quality checking of the aerial photos and digital imagery was overseen by Alan Bell of USBR/RSGIG. Acknowledgment of the USBR/RSGIG would be appreciated in products derived from these data.

Native_Data_Set_Environment:

Microsoft Windows Vista Version 6.0 (Build 6002) Service Pack 2; ESRI ArcCatalog 9.3.1.1850

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:: This project received an accuracy assessment in the summer of 2004. 1207 accuracy assessment points are recorded. The results were subject to a fuzzy accuracy assessment. Fuzzy accuracies are reported for overall map accuracy and individual map unit accuracy. Overall map accuracy for fuzzy classes five, four and three are 50.3%, 74.7% and 86.7%. We refer the reader to the vegetation mapping report for information about individual map unit accuracies and more specifics with regard to methods.

Logical_Consistency_Report:

All polygon features are checked for topology and existence of attributed label points. Coverage checked for un-intentional dangling arcs.

Completeness_Report:

All data with a minimum mapping unit of 1/2 hectare that can be interpreted from the aerial photographs are entered into the digital database. This includes features defined by the NVCS. Some classes under the MMU are included due to its ease of interpretation and due to the specialty of the class. Road and utility corridors and streams/canals wider that 10 meters are included as polygons in this vegetation coverage.

Lineage:

Process_Step:

Process_Description:: 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. PHOTO INTERPRETATION: All map classes were interpreted from 1:12,000-scale, true color aerial photography. 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. The linework was subsequently transferred to a mylar overlaying the color 1:12,00 scale DOQ's acquired for this project. GIS PROCEDURES: The linework on the mylar ortho-photo overlays were transferred into the GIS database by scanning. METHOD : The all of the linework at ROMO 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 park boundary coverages were acquired from the Park. A flight line coverage was obtained from the photography vendor.
Process_Date: Unknown

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 36158

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Grid_Coordinate_System:

Grid_Coordinate_System_Name: Universal Transverse Mercator

Universal_Transverse_Mercator:

UTM_Zone_Number: 13

Transverse_Mercator:

Scale_Factor_at_Central_Meridian: 0.999600
Longitude_of_Central_Meridian: -105.000000
Latitude_of_Projection_Origin: 0.000000
False_Easting: 500000.000000
False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.000100
Ordinate_Resolution: 0.000100

Planar_Distance_Units: meters

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222

Vertical_Coordinate_System_Definition:

Altitude_System_Definition:

Altitude_Datum_Name: National Geodetic Vertical Datum 1983
Altitude_Encoding_Method:: Explicit elevation coordinate included with horizontal coordinates
Altitude_Resolution: 0.000100
Altitude_Distance_Units: Unknown

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: ROMO_VegPolys
Entity_Type_Definition: GDB
Entity_Type_Definition_Source: National Park Service

Attribute:

Attribute_Label: OBJECTID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI