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: Fort Larned National Historic Site Vegetation Mapping Project - Spatial Vegetation Data
Abstract:
This metadata is for the vegetation and land-use geo-spatial database for Fort Larned National Historic Site and surrounding areas. This project is authorized as part of the USGS/NPS Vegetation Mapping Program. The program is being administered by the Core Science Systems (CSS) of the United States Geological Survey (USGS) in conjunction with the National Park Service (NPS) Inventory and Monitoring Program. 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).
Supplemental_Information: None
  1. How should this data set be cited?

    USBR Remote Sensing and GIS Group, Denver, Colorado, Unpublished Material, fols_veg: None None, None, None.

    Online Links:

    Other_Citation_Details: None

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -99.245760
    East_Bounding_Coordinate: -99.200417
    North_Bounding_Coordinate: 38.195387
    South_Bounding_Coordinate: 38.114445
    Description_of_Geographic_Extent: Fort Larned National Historic Site and environs

  3. What does it look like?

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

    Calendar_Date: 2005
    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):

      • Complete chain (612)
      • Label point (229)
      • GT-polygon composed of chains (229)
      • Point (4)

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

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 14
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -99.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.000001
      Ordinates (y-coordinates) are specified to the nearest 0.000001
      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.

  7. How does the data set describe geographic features?

    fols_veg.pat
    attributes from shapefile table (Source: Fort Larned National Historic Site)

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

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

    Positive real numbers that are automatically generated.

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

    Positive real numbers that are automatically generated.

    FOLS_VEG#
    Internal feature number. (Source: ESRI)

    ValueDefinition
    10 - 25%Sparse
    25 - 60%Open
    > 60%Dense

    Sequential unique whole numbers that are automatically generated.

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

    ValueDefinition
    HomogeneousEvenly Dispersed
    Bunched / ClumpedUneven Dispersed
    LinearStraight Vegetation

    MAP_CLASS
    Map Class Code (Source: USBR Remote Sensing and GIS Group)

    Map class code.

    MAP_DESC
    Map Class Name (Source: USBR Remote Sensing and GIS Group)

    Map class association common name.

    DENS_MOD
    Density Modifier (Source: USBR Remote Sensing and GIS Group)

    Coverage density physiognomic modifier. Applied to all vegetation map classes.

    PTRN_MOD
    Pattern Modifier (Source: USBR Remote Sensing and GIS Group)

    Coverage pattern physiognomic modifier. Applied to all vegetation map classes.

    HT_MOD
    Modifier - Height range of the dominant vegetation layer (Source: USBR Remote Sensing and GIS Group)

    ValueDefinition
    0 - 0.5 Meters0-0.5 m (0-1.6 ft)
    0.5 - 1 Meters0.5-1 m (1.6-3.3 ft)
    15 - 30 Meters15-30 m (50-98 ft)
    >30 meters
    30 m (>98 ft)
    

    DOM_MOD
    Physiognomic Modifier (Source: USBR Remote Sensing and GIS Group)

    Dominant physiognomic modifier. Applied to all vegetation map classes.

    CES_CODE
    NVC Ecological Systems Code (Source: NatureServe)

    National Vegetation Classification Ecological System code.

    CES_NAME
    NVC Name (Source: NatureServe)

    National Vegetation Classification Ecological System name.

    IDENTIFIER
    NVC Plant Association/Alliance Code (Source: NatureServe)

    CEGL code.

    ASSN_NAME
    Association scientific name. (Source: NatureServe)

    Textual Scientific association name.

    ASSN_CNAME
    Association common name. (Source: NatureServe)

    Textual common association name.

    NVCS_CODE
    NVC Idenification Code (Source: NatureServe)

    National Vegetation Classification System code.

    ALL_NAME
    NVC Alliance Name (Source: NatureServe)

    National Vegetation Classification System Alliances (scientific names).

    ALL_CNAME
    NVC Alliance Common Name (Source: NatureServe)

    National Vegetation Classification System Alliances (common names).

    FORMATION
    NVC Formation Name (Source: NatureServe)

    National Vegetation Classification System Formation name.

    SUBGROUP
    NVC Subgroup Name (Source: NatureServe)

    National Vegetation Classification System Subgroup name.

    GROUP
    NVC Group Name (Source: NatureServe)

    National Vegetation Classification System Group name.

    SUBCLASS
    NVC Subclass Name (Source: NatureServe)

    National Vegetation Classification System Subclass name.

    CLASS
    NVC Class Name (Source: NatureServe)

    National Vegetation Classification System Class name.

    LUC_II_GEN
    Anderson General Land Use Name (Source: USGS Anderson Land Cover Classification)

    Land Cover Classification System types.

    LUC_II_DET
    Anderson Specfic Land Use Name (Source: USGS Anderson Land Cover Classification)

    Land Use Classification System types.

    COMMENTS
    General Polygon Comments (Source: USBR Remote Sensing and GIS Group)

    Textual general decription comments.

    ACRES
    Polygon Area (Source: USBR Remote Sensing and GIS Group)

    Unique numbers - user defined

    Entity_and_Attribute_Overview:
    Attributes were either generated by ArcInfo, or assigned by the USBR Remote Sensing GIS Group.
    Entity_and_Attribute_Detail_Citation:
    Fort Larned National Historic Site Vegetation Mapping Project Final Report (DOI - USGS/USBR)

  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 Remote Sensing and GIS Group: Mike Pucherelli. Cogan Technology, Inc.: Dan Cogan (Cogan Technology Inc.)

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

    Bureau of Reclamation
    c/o Mike Pucherelli
    Group Manager
    P.O. Box 25007 Bldg. 56 Denver Federal Center M.S. D-8260
    Denver, Colorado 80225
    United States of America

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

    Hours_of_Service: 8 am - 5 pm
    Contact_Instructions: None


Why was the data set created?

The NPS Inventory and Management 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.

The purposes of this specfic mapping effort are varied and include the following: 1) provide support for NPS Resource Management, 2) promote vegetation-related research, 3) provide support for NPS Planning and Compliance, 4) add to the information base for NPS Interpretation, 5) provide a vegetation baseline inventory for the Park, 6) provide information needed for NPS Fire Program, and 7) assist in overall NPS Operations.


How was the data set created?

  1. From what previous works were the data drawn?

    GRTE Ortho_photo (source 1 of 1)
    U.S. Dept of Agriculture, Unknown, NAIP 2005 Orthophotography Pawnee County: None None, None, None.

    Type_of_Source_Media: CD-ROM
    Source_Scale_Denominator: 12000
    Source_Contribution: None

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

    Date: Unknown (process 1 of 6)
    All plant community data that could be interpreted from the NAIP imagery 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. Polygons were checked in the field and attributed accordingly.

    Date: Unknown (process 2 of 6)
    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.

    Date: Unknown (process 3 of 6)
    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 for this project 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.

    Date: Unknown (process 4 of 6)
    OTHER DATA: The mapping project and park boundary coverages were acquired from the Park. A flight line coverage was obtained from the photography vendor. Field Observation, Plot, and Accuracy Assessment data point coverages were created by entering points with the 'generate' command using a text file of points and x-y coordinates.

    Date: Unknown (process 5 of 6)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\Dan\LOCALS~1\Temp\xml1B.tmp

    Date: Unknown (process 6 of 6)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\Dan\LOCALS~1\Temp\xml1C.tmp

  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 92%. Please read the accompanying report or check with the park for the latest accuracy assessment values.

  2. How accurate are the geographic locations?

    Unknown: Assumed that the NAIP 2005 basemap met the National Map Accuracy Standards, reference the NAIP ortho-photo metadata.

  3. How accurate are the heights or depths?

    Unknown: Assumed that the NAIP 2005 basemap met the National Map Accuracy Standards, reference the NAIP ortho-photo metadata.

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

    All data that could be interpreted from the NAIP imagery 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: 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?


Who wrote the metadata?

Dates:
Last modified: 13-Mar-2008
Last Reviewed: 24-May-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 May 24 10:53:23 2010

Return to USGS Vegetation Characterization Program at Fort Larned National Historic Site
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/fols/metafolsspatial.faq.html
Page Contact Information:gs-b-npsveg@usgs.gov
Page Last Modified: Thursday, 12-Jan-2012 10:49:21 MST