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?

   Virginia Department of Conservation and Recreation, Division of Natural Heritage, 200802, Vegetation Map for Richmond National Battlefield Park 2002.

   Online Links:

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

   This is part of the following larger work.

   Patterson, Karen, 200806, Patterson, K.D. 2008. Vegetation Classification and Mapping at Richmond National Battlefield Park, Virginia. Technical Report NPS/NER/NRTR2008/128. National Park Service. Philadelphia, PA..

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -77.433229

   East_Bounding_Coordinate: -77.234395

   North_Bounding_Coordinate: 37.602360

   South_Bounding_Coordinate: 37.347199

   Description_of_Geographic_Extent: Richmond National Battlefield Park and environs

3. What does it look like?

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

   Calendar_Date: 28-Feb-2002

   Currentness_Reference: Date of aerial photography

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 (185)

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

      Grid_Coordinate_System_Name: Universal Transverse Mercator

      Universal_Transverse_Mercator:

      UTM_Zone_Number: 18

      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.999600

      Longitude_of_Central_Meridian: -75.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.000064
      Ordinates (y-coordinates) are specified to the nearest 0.000064
      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.257222.
      

7. How does the data set describe geographic features?

   rich_veg_map_association_2002

   attribute table from shapefile table (Source: Virginia Department of Conservation and Recreation, Division of Natural Heritage)

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   POLYGON_ID

   Unique identifer for each of the 185 polygons. Identifers are sequential whole numbers. (Source: Karen Patterson, Vegetation Ecologist, Virginia Dept. of Conservation and Recreation, Division of Natural Heritage, Richmond, VA.)

   Range of values
   Minimum:	1
   Maximum:	185

   LOCAL_NAME

   A common or colloquial name for the map class. These names follow the Natural Communities of Virginia (Fleming et al 2006) or, if no appropriate name exists in Fleming et al (2006), the Association common name from the U.S. National Vegetation Classification (NVC) was used, or a park-specific common name was assigned. Nonstandard, park-specific units representing disturbed, cultural, or exotic vegetation were defined by Ecologists at the Division of Natural Heritage. Names for map classes not representing natural or semi-natural vegetation follow the Anderson level II land use and land cover classification scheme (Anderson et. al 1976). (Source: Patterson, K.D. February 2008. Vegetation Classification and Mapping at Richmond National Battlefield Park. Technical Report NPS/NER/NRTR--2008/XXX. National Park Service. Philadelphia, PA.)

   Value	Definition
   Acidic Oak - Hickory Forest	Acidic Oak - Hickory Forest
   Beaver Wetland Complex	Beaver Wetland Complex
   Coastal Plain / Piedmont Acidic Seepage Swamp	Coastal Plain / Piedmont Acidic Seepage Swamp
   Coastal Plain / Piedmont Small-Stream Floodplain Forest	Coastal Plain / Piedmont Small-Stream Floodplain Forest
   Cultural Meadow	Cultural Meadow
   Forested Earthworks	Forested Earthworks
   Loblolly Pine - Hardwood Forest	Loblolly Pine - Hardwood Forest
   Loblolly Pine Plantation	Loblolly Pine Plantation
   Mesic Mixed Hardwood Forest	Mesic Mixed Hardwood Forest
   Coastal Plain Mixed Oak / Heath Forest	Coastal Plain Mixed Oak / Heath Forest
   Open Earthworks	Open Earthworks
   Other Urban or Built-up Land	Other Urban or Built-up Land
   Successional Mixed Scrub	Successional Mixed Scrub
   Successional Tuliptree Forest	Successional Tuliptree Forest
   Transportation, Communications, and Utilities	Transportation, Communications, and Utilities
   Non-Riverine Saturated Forest	Non-Riverine Saturated Forest
   Non-Riverine Saturated Forest - pine subtype	Non-Riverine Saturated Forest - pine subtype
   Residential	Residential
   Successional Red-cedar Forest	Successional Red-cedar Forest
   Successional Black Walnut Forest	Successional Black Walnut Forest
   Successional Shrub Swamp	Successional Shrub Swamp

   COMMENT

   Comments that make distinctions between polygons of a map class. (Source: Karen Patterson, Vegetation Ecologist, Virginia Dept. of Conservation and Recreation, Division of Natural Heritage, Richmond, VA.)

   No domain defined.

   FORM_CODE

   Code for Formation level of the vegetation classification standard (U.S. National Vegetation Classification) (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Formation Code
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   FORM_NAME

   Formation Name from the vegetation classification standard (U.S. National Vegetation Classification) (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Formation Name
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   ALLIA_CODE

   Code for the Alliance level of the vegetation classification standard (U.S. National Vegetation Classification) (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Alliance Key
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   ALLIAN_SCI

   Alliance name from the vegetation classification standard (U.S. National Vegetation Classification) (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Alliance Name
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   ALLIAN_ENG

   Alliance name with Latin names translated to English from the vegetation classification standard (U.S. National Vegetation Classification) (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Alliance Translated Name
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   ASSOC_CODE

   A unique identifier code for the Association level of the vegetation classification standard (U.S. National Vegetation Classification). Code is standard Global Element Code from Natureserve Central databases (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Elcode
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   ASSOC_ENG

   Association Name with Latin names translated to English from the vegetation classification standard (U.S. National Vegetation Classification) (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Association Translated Name
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   ASSOC_SCI

   Association Name from the vegetation classification standard (U.S. National Vegetation Classification) (Source: NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A. Data current as of 27 September 2007.)

   Formal codeset
   Codeset Name:	Global Name
   Codeset Source:	NatureServe. 2007. International Ecological Classification Standard: Terrestrial Ecological Classifications. NatureServe Central Databases. Arlington, VA. U.S.A.

   WETLAND

   Field to indicate what USFWS System level is represented by the map class. (Source: Cowardin, L.M., V. Carter, F.C. Golet, and E.T. LaRoe. 1979. Classification of wetlands and deepwater habitats of the United States. U.S. Fish and Wildlife Service. FWS/OBS-79/31. 103 pp.)

   Formal codeset
   Codeset Name:	System
   Codeset Source:	Cowardin, L.M., V. Carter, F.C. Golet, and E.T. LaRoe. 1979. Classification of wetlands and deepwater habitats of the United States. U.S. Fish and Wildlife Service. FWS/OBS-79/31. 103 pp.

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)
   • Virginia Department of Conservation and Recreation, Division of Natural Heritage

2. Who also contributed to the data set?

3. To whom should users address questions about the data?
   Virginia Department of Conservation and Recreation, Division of Natural Heritage
   Ecologist
   217 Governor Street
   Richmond, Virginia 23219
   USA
   

   804-786-5990 (voice)
   

Why was the data set created?

This data set was created for Richmond National Battlefield Park for use in natural resource management.

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: 18-Jul-2006 (process 1 of 1)

   A preliminary vegetation map was created by viewing leaf-on (data captured 10-23-2001) and leaf-off (data captured 02-28-2002) digital photo mosaics, both in two and three dimensions. Areas of homogenous vegetation, land cover, and land use were delineated using ArcMaps onscreen digitizing tools. The minimum mapping unit was 0.5 hectares (1.25 acres). Polygons were attributed to the formation-level of the USNVC Level II and Anderson's land use and land cover classification. The preliminary vegetation map served as a guide for field reconnaissance during the summers of 2002-2006. Data were collected from 11 quantitative vegetation plots and qualitative observations throughout the park. Data were combined with data from other areas of the Mid-Atlantic Piedmont and Coastal Plain to refine the USNVC for the region. The draft formation-level vegetation map was extensively revised to better reflect vegetation units based on field information and using the following ancillary data layers; topographic maps and digital raster graphics (DRGs), National Wetland Inventory maps, County soil surveys, and the digital soil survey data (SSURGO). The edited polygons were reattributed with the association names from the refined USNVC. Seventy-one thematic accuracy assessment points were randomly placed within the vegetation map, following a stratified random sampling plan. The Kappa Index for the final vegetation map was 84.5 ± 10.2%, with an overall accuracy of 85.9%.

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 of the vegetation map was assessed using a stratified random sampling approach, stratifying 71 samples among USNVC map classes. Sample size was determined by class abundance and frequency as recommended in section 4.4.2 of the USGS/NPS Vegetation Mapping Program standards, with one regional modification to accommodate the vegetation pattern seen in the park. Polygons were validated in the field by VADNH staff. Three cultural map classes, Cultural Meadow, Forested Earthworks, and Open Earthworks, and all Anderson II land use classes were excluded from the accuracy assessment. Successional Black Walnut Forest and Successional Shrub Swamp were also excluded since they each were represented by a single, very small polygon that was thoroughly surveyed during the mapping phase of the project. The Kappa index for the vegetation map was 84.4% +/- 10.2%, with the overall percent accuracy calculated as 85.9%. Examination of the errors associated with each observation shows that they can be attributed to below minimum mapping unit inclusions of other vegetation types within the target polygons or to the difficulty of assigning a vegetation classification to very disturbed, transitional vegetation. Additionally some of the mapping errors may have been due to the difficulty of distinguishing deciduous types on aerial photography, since many deciduous signatures are virtually identical.

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?

   Shapefile covers entire park area

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

   Polygon geometry and topology were validated with ESRI ArcGIS v. 9.2 to find and correct any voids, slivers, overlapping polygons, or self-intersections.

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: None

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/rich/index.html>

   • Cost to order the data: None

Who wrote the metadata?

Dates:

Last modified: 29-Feb-2008
Last Reviewed: 08-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>