Spatial Vegetation Data FAQ Metadata

Metadata also available as - [Outline] - [Text] - [PDF Version]

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. What methods were used to collect the data?
  2. From what previous works were the data drawn?
  3. How were the data generated, processed, and modified?
  4. 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?

   Remote Sensing and GIS Group, Technical Service Center, US Bureau of Reclamation, MC-D8260, POB 25007, Denver CO 80225, 2000, Theodore Roosevelt NP Vegetation Database: USGS-NPS Vegetation Mapping Program Theodore Roosevelt NP, USGS/CSS, Denver, CO.

   Online Links:

   • <http://biology.usgs.gov/npsveg/ftp/vegmapping/thro/thro.zip>
   • <http://www.usbr.gov/pmts/rsgis/>

   Other_Citation_Details: Database created under contract to the USGS/CSS

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -103.75

   East_Bounding_Coordinate: -103.125

   North_Bounding_Coordinate: 47.75

   South_Bounding_Coordinate: 46.75

   Description_of_Geographic_Extent: Theodore Roosevelt NP and surrounding environs

3. What does it look like?

   <http://biology.usgs.gov/npsveg/thro/images/throvegmap.pdf> (PDF)

   Graphic of vegetation map.

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

   Calendar_Date: Jul-1996

   Currentness_Reference: Dates of aerial photography

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

   Geospatial_Data_Presentation_Form: map

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

      Indirect_Spatial_Reference:

      Theodore Roosevelt National Park, USGS 7.5 minute quadrangle names

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

   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:

      Longitude_of_Central_Meridian: -105

      Latitude_of_Projection_Origin: 0

      False_Easting: 0

      False_Northing: 0

      Scale_Factor_at_Central_Meridian: .9996

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 1
      Ordinates (y-coordinates) are specified to the nearest 1
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodedic 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:

   VEGETATION COVERAGES: Due to the large size of the database, vegetation coverages were named according to associated USGS 7.5m quads. Exception; the Elkhorn Ranch Unit coverage is named ranch_veg. Naming convention: <quadname>_veg# with # referring to the quarter quadrant as follows: 1 - Northwest quadrant; 2 - Northeast quadrant; 3 - Southeast quadrant; 4 - Southwest quadrant. Coding Information: Polygon coverage with labels in each polygon with the following custom items: (veg_code - 3 3 I)* coded with vegetation classification number. See Supplemental Info under Id Info above for complete listing of attribute codes and their descriptions; (photo - 6 6 I) coded with associated photo number; (location - 10 10 I) coded according to whether the polygon is in the park or environs (buffer) area; (pdog - 2 2 I) for prairie dog colonies coded with 0 (no pdog holes) or 1 (polygon has pdog holes); and (lspr - 2 2 I) for leafy spurge coded with 0 for none and 1 for polygon has leafy spurge. These last two itens were used to show areas that were not classified as prairie dog colonies or leafy spurge but had substantial pdog use or leafy spurge; Also, each arc was coded as follows: (digtype - 2 2 I)) coded to identify how the arc was transferred into the database or type of arc as follows: 1 = heads-up, on screen digitizing; 2 = scanned mylar; 3 = arc associated with GIS project border; 4 = arc associated with quarterquad border; 5 = arc associated with park border. (veg_code - 3 3 I) linear wetland features coded with vegetation classification number. Arcs attributed class 14 were extracted and put into a separate (line) coverage named drainage. Some of the class 14 arcs remained in the _veg coverage if it also delineated a unique polygon. BOUNDARY COVERAGES: bndrypark - Park boundary coverage. This coverage was obtained from Theodore Roosevelt National Park Headquarters. bndryproj - GIS mapping project area. bndryquad - Boundaries of all the 7.5m quads. bndrygrds - Grad-sect boundaries. Coding Information: bndrypark - line coverage - no custom attributing. bndryproj - line coverage - no custom attributing. bndryquad - polygon coverage with labels in each quad polygon with the following items: (quadname - 8 8 c) - abbreviated name for each quad; (fullname - 20 20 c) - full quadname. DATA COVERAGES: dataobsv - Point coverage of observation data points. dataplot - Point coverage of plot data points. Coding Information: Label points with items as follows: (plot_code - 3 3 n) coded with plot number from plot data sheets; (veg_code - 14 14 c) coded with veg class text; (type - 10 10 c) coded with broad vegetation class (eg: woodland). Note1: x-coord and y-coord added with ARC/INFO "addxy" command. Note2: Field data points were collected with GPS units set to datum NAD27. All coverages were re-projected into Datum NAD83 so the x- y- coordinates will not match those shown on the data sheets. OTHER COVERAGES: sec_roads - Line coverage of secondary roads digitized from USGS DOQQ. railroads - Line coverage of railroads digitized from USGS DOQQ. The parks projects will be using DOQQ's as the basemap for transfer of information from the photos to the GIS database. The DOQQ's are standard USGS product and are in datum of NAD83. (*) Item definition in the arc/info database.

   Entity_and_Attribute_Detail_Citation:

   Theodore Roosevelt National Park, USGS/NPS Vegetation Mapping Program, Techincial Memorandum No. 8260-00-04, USBR

8. What biological taxa does this data set concern?

   Taxonomy:

   Keywords/Taxon:

   Taxonomic_Keyword_Thesaurus: none

   Taxonomic_Keywords: vegetation

   Taxonomic_Keywords: plants

   Taxonomic_Keywords: National Vegetation Classification System

   Taxonomic_System:

   Classification_System/Authority:

   Classification_System_Citation:

   Citation_Information:

   Originator: Anderson, et al

   Publication_Date: 1976

   Title:

   A Land Use and Land Cover Classification System for Use with Remote Sensor Data

   Geospatial_Data_Presentation_Form: document

   Series_Information:

   Series_Name: Geological Survey Professional Paper

   Issue_Identification: No. 964

   Publication_Information:

   Publication_Place: Washington, DC

   Publisher: US GPO

   Other_Citation_Details: This project used the Level II Land Use Classes

   Online_Linkage:

   <http://www.fgdc.gov/standards/projects/FGDC-standards-projects/vegetation/NVCS_V2_FINAL_2008-02.pdf/>

   Taxonomic_Procedures:

   Sequence of field test data plots, observation plots, and photo-signature observations.

   General_Taxonomic_Coverage:

   Refer to complete listing of mapped plant alliances/associations under Supplemental Information above. Taxanomic_Classification:

   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)
   • Remote Sensing and GIS Group, Technical Service Center, US Bureau of Reclamation, MC-D8260, POB 25007, Denver CO 80225

2. Who also contributed to the data set?

   Dan Cogan, Doug Crawford, Jean Pennell, Trudy Meyer, Jim Von Loh

3. To whom should users address questions about the data?
   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
   

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 map the vegetation of all national parks and monuments and provide a baseline inventory of vegetation.

How was the data set created?

1. What methods were used to collect the data?

   Method 0 of 1

   Type: Field

   Refer to the steps outlined in Process Description below.

   Reference:

   From what previous works were the data drawn?

   None (source 1 of 2)

   USGS, Unknown, Digital Orthophoto Quarter Quadrangles. See other information below for list..

   Online Links:

   • <http://edcsns17.cr.usgs.gov/EarthExplorer/>

   Other_Citation_Details:

   List of DOQQs used as basemaps for this project (text in parenthesis indicates Arc/Info coverage filename): Bear Butte (bear_bt), Belfield (belfield), Belfield SW (blfld_sw), Buckskin Butte (bkskn_bt), Buffalo Gap Campground (bufgp_cp), Chimney Buttes (chmny_bt), Eagle Draw, Gorham SE & SW (gorhm_se, gorhm_sw), Fryburg, (fryburg), Fryburg NE & NW (frybr_ne, frybr_nw), Ice Box Canyon (icebx_cn), Hanks Gully, Lone Butte (lone_bt), Lone Butte NW (ln_bt_nw), Long X Divide (longx_dv), Medora, Red Wing Creek (rdwng_cr), Roosevelt Creek East & West, Sperati Point (sprti_pt), Stocke Butte (stck_bt), Tepee Buttes (tepe_bts), Tracy Mountain (tracy_mt), Wannagan Creek East & West (wna_cr_e, wna_cr_w), Wolf Coulee (wolf_cle)

   Type_of_Source_Media: CD-ROM

   Source_Scale_Denominator: 12000

   Source_Contribution: None

   None (source 2 of 2)

   USDA-FSA, Aerial Photography Field Office, 199608, 1:24k Color Aerial Photographs: Little Missouri National Grasslands 611089, USDA, Farm Service Agency, P.O. Box 30010, SLC, Utah 84130.

   Online Links:

   • <http://www.fsa.usda.gov/FSA/apfoapp?area=apfohome&subject=landing&topic=landing>

   Other_Citation_Details: See database for photographs used.

   Type_of_Source_Media: photographs

   Source_Scale_Denominator: 24000

   Source_Contribution: None

   How were the data generated, processed, and modified?

   Date: 1999 (process 1 of 1)

   PHOTO INTERPRETATION: All map classes were interpreted from 1:24,000 scale, color photography flown in July & August 1996. The photographs were acquired from the USDA and were enlarged to 1:12000. 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 map class to each polygon. Photographs were examined using a stereoscope as needed. Linework was created on mylars placed over the photos. GIS PROCEDURES: The linework on the mylar overlays were transfered into the GIS database by one of two methods, either heads-up digitizing or scanning. METHOD I: Heads-up digitizing will be used whenever the photo does not include many complicated grassland polygons as these are the most difficult to transfer using heads-up digitizing. This will usually mean photos with mostly badlands topography or agricultural lands (i.e., have boundaries that are easy to see on the digital orthophoto image) will be transferred using the heads-up method. Briefly, 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 from which the classification was made and on the orthophoto, the line drawn on the aerial photo overlay is transferred to the digital image, which is registered to coordinates on the earth. This technique should produce good results except where there is little feature contrast on the ortho, in which case the operator must estimate the shape and location of the line work. Using this technique, a curve on the photo may appear to be a series of short, differently-angled straight line segments, since it is easier to make a curve with a pencil or pen than it is with digitized discrete points. Depending on the density of digitized points, this may or may not be a problem. The analyst may set the digitizing software to calculate a pseudo-curve of many points by inputting as few as three points to define a curve. METHOD II: Photos that are too difficult to accurately transfer via heads-up will be scanned, ie, the mylars overlays will be scanned, not the actual photos. Before the mylar is scanned, it will be marked with control points that correspond to visible points on the DOQQ. The GIS software was used to convert the scanned mylar into a geo-referenced coverage which was then attributed and combined with the larger vegetation coverage associated with the quarter quad area. The entire transfer and editing sequence was automated via in-house Arc/INFO AML programs. The final vegetation coverages consist of (1) Quarter-quad, Park, and GIS project area boundary arcs, if applicable, and (2) vegetation polygons. Linear wetland features were put in a separate coverage called 'drainage'. Another step involved heads-up digitizing of roads and railroads visible on the DOQQ in accordance with the criteria discussed above. OTHER DATA: Coverages for the plot and observation data points were created from the plot and observation data sheets. The coordinates on the data sheets were in datum NAD27. Once the coverages were finalized they were reprojected into datum NAD83. The Drainage coverage was created by taking arcs attributed with veg_code = 14 out of the vegetation coverage and 'put' into the drainage coverage.

   Person who carried out this activity:
   

   Remote Sensing and Geographic Information Group, USBR
   P.O. Box 25007
   Denver, Colorado 80225
   USA
   

   303-445-2267 (voice)
   303-445-6337 (FAX)
   mpucherelli@do.usbr.gov
   

   Hours_of_Service:

   7:00 a.m. to 3:00 p.m. Monday Through Friday, Mountain Time

   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?

   These data have an overall accuracy of 74.3% (71.3% Kappa index) within a 90% confidence interval of 70.3 to 78.3%.

2. How accurate are the geographic locations?

   USGS DOQQ's were used as the basemap for this project. The attribute accuracy stated above may also reflect horizontal positional accuracy.

3. How accurate are the heights or depths?

   This database contains no vertical or elevation data.

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

   All data that can be photo-interpreted are digitized in accordance with the minimum mapping unit (MMU) of 1/2 hectare. This includes selected features that fall into the NVCS vegetation classification and the Anderson Level II land use classification. Some classes below the MMU are included such as wetlands and grasslands in badlands areas and polygons cut off by other features and borders. Roads (out to visible disturbed ground right-of-way or fence line) and streams/drainages wider than approx 10 meters were digitized as polygons and attributed accordingly. Roads visible on the orthophotos but thinner than 10 meters were digitized as lines. Wet drainages thinner than 10 meters were digitized as lines and attributed with code #14. Dry drainages thinner than 10 meters were not digitized.

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

   All polygon features are checked for topology and existence of label points using the ARC/INFO software. Each polygon begins and ends at the same point with the node feature. All nodes are checked for error so that there are no unintentional dangling features. There are no duplicate lines or polygons. All nodes will snap together and close polygons based on a specified tolerance. If the node is not with the tolerance it is adjusted manually. The tests for logical consistency are performed in ARC/INFO using certain 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/CSS and the USBR/RSGIS 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 procedures, as described in the metadata, 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
   

   Hours_of_Service: 7:30am to 4:00 pm Mon-Fri, Mountain Time

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

   Theodore Roosevelt National Park Vegetation Maps

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:	ARC/INFO
     Media you can order:	CD-ROM (format ISO 9660)

   • Cost to order the data: Media, Shipping, and Handling

   • Availability in digital form:

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

   • Cost to order the data: None

Who wrote the metadata?

Dates:

Last modified: Jan-2000
Last Reviewed: 16-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:

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