Spatial Vegetation Data FAQ Metadata

Metadata also available as - [Outline] - [Text] - [Adobe Acrobat pdf file]

Frequently-anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
  8. What biological taxa does this data set concern?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  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?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How should this data set be cited?

   Service, National Park , U.S. Bureau of Reclamation, and Colorado Natural Heritage Program/Colorado State University, 2009, Spatial Vegetation Data for Rocky Mountain National Park Vegetation Mapping Project.

   Online Links:

   • <http://biology.usgs.gov/npsveg/ftp/vegmapping/romo/romogeodata.zip>

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -105.933549

   East_Bounding_Coordinate: -105.416952

   North_Bounding_Coordinate: 40.567749

   South_Bounding_Coordinate: 40.139505

   Description_of_Geographic_Extent: Rocky Mountain National Park and environs

3. What does it look like?

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

   Calendar_Date: 2001

   Currentness_Reference: ground condition

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

   Geospatial_Data_Presentation_Form: 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):

      • G-polygon (36158)

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

      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 coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000100
      Ordinates (y-coordinates) are specified to the nearest 0.000100
      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.000000.
      The flattening of the ellipsoid used is 1/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

7. How does the data set describe geographic features?

   ROMO_VegPolys

   GDB (Source: National Park Service)

   OBJECTID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   SHAPE

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   SHAPE_Length

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

   Positive real numbers that are automatically generated.

   SHAPE_Area

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

   Positive real numbers that are automatically generated.

   Poly_ID

   Unique identifier for each polygon (Source: National Park Service)

   Unique plot code.

   NVC_Elcode

   National Vegetation Classification Code (Source: National Park Service)

   CEGL code.

   Association

   NVC Vegetation Association name (Source: National Park Service)

   Association scientific name.

   MapClass_CD

   Code used to represent the Map Class (Source: National Park Service)

   Map class code.

   MapClass

   Full Map Class name (Source: National Park Service)

   Map class association common name.

   X_Centroid

   X Coordinate (UTM Easting) of the centroid of the polygon (Source: National Park Service)

   Easting coordinate.

   Y_Centroid

   Y Coordinate (UTM Northing) of the centroid of the polygon (Source: National Park Service)

   Northing coordinate.

   rc_VegPolys_tVegMapInfo

   Defines relationship between Veg polygons and basic vegetation attributes (Source: National Park Service)

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)
   • National Park Service
   • U.S. Bureau of Reclamation
   • Colorado Natural Heritage Program/Colorado State University

2. Who also contributed to the data set?

   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.

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

Why was the data set created?

Vegetation maps of National Parks and National Monuments were developed to support natural resources management, planning, research and interpretation.

How was the data set created?

1. From what previous works were the data drawn?

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

   Date: Unknown (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. 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.

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?

   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.

2. How accurate are the geographic locations?

3. How accurate are the heights or depths?

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

   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.

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

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

How can someone get a copy of the data set?

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

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.

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?

   Downloadable Data

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?
   • Availability in digital form:

     Data format:	HTML
     Network links:	<http://biology.usgs.gov/npsveg/romo/index.html>

   • Cost to order the data: None

Who wrote the metadata?

Dates:

Last modified: 08-Dec-2009
Last Reviewed: 03-Aug-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:

• <http://www.nbii.gov/portal/server.pt/community/fgdc_metadata/255>