National Park Service, <PARK NAME>, <PARK DIVISION> <YYYYMMDD> vector digital data gunnisonhttp://www.nps.gov/gis/ This is a vector <...point, line, or polygon> <SHAPEFILE OR COVERAGE> file showing the <FEATURE TYPE> at <PARK NAME>. The coordinates for this dataset were heads up digitized at a scale of 1:XXX off of a <FILE ie. USGS 7.5 minute DRG or USGS DOQQ> using <GIS SOFTWARE>. To show the location of <LIST FEATURES> at <PARK NAME>. The intended use of all data in the park's GIS library is to support diverse park activities including planning, management, maintenance, research, and interpretation. <CAN PUT SHORT HISTORIC SPIEL ABOUT PARK HERE> en <YYYYMMDD> ground condition Complete None planned 325589.576031336772.9658554262753.6040974276858.248662 None <list terms seperated by commas> None <PARK NAME>, <PARK4LETTERCODE>, <STATE>, <ECOREGION>, <COUNTY>, NPS, National Park Service, USA, US, United States, North America None None. <PUT IN SCALE USE CONSTRANTS> National Park Service, Intermountain Geographic Resource Information Management TeamGIS Coordinator/GIS Specialistmailing and physical address

12795 West Alameda Parkway

LakewoodCO80228USAimro_gis_coordinator@nps.gov8:00 a.m. to 4:00 p.m. MST, Monday through FridayPlease contact through email. <PARK4LETTERCODE>_XXXX.jpg JPEG The graphic shows the <FEATURE NAME> in relation to park's boundary. Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.0.0.535 <ARCINFO COVERAGE OR ARCVIEW SHAPEFILE> <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> The attribute accuracy was tested by interactively querying and verifying on screen with the source materials. In addition, the attributes were compared against a master set of valid attributes. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Topologically clean dataset. There are no duplicate features. Polygonal features begin and end at the same point, contain no overshoots or undershoots, and contain a single label. Initial topology was created by running a CLEAN command in ArcInfo at a fuzzy tolerance of 0.00000000001 and dangle tolerance of 0. ArcInfo commands, NODEERRORS and LABELERRORS, were used to find any missing or deviant data. Dataset then reviewed manually with ArcInfo's ArcEdit module, deleting overshoot arcs and verifying complete closure off all intended polygons. After ArcEdit session, topology was rebuilt using the ArcInfo BUILD command. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Dataset is complete. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Estimated accuracies in the X and Y direction of 1 to 20 meters from the true location. The horizontal positional accuracy was tested by verifying the location of the data on-screen relative to the corresponding 1:24000 USGS DRG (digital raster graph) in the same projection and datum. The relative positions between the two datasets onscreen was compared to the hardcopy map used as the base for digitizing. U.S. Geological Survey 1998 remote-sensing image <EXAMPLE> Digital Orthophoto Quarter Quad <EXAMPLE> <QUAD NAME> Quadrangle <NE, NW, SE, OR SW> <EXAMPLE> U.S. Geological Survey <EXAMPLE> Reston, VA <LIST QUADS AND (PUBLICATION DATES) THEN ADJUST SOURCE_TIME_PERIOD_OF_CONTENT TO CONFORM WITH PUB DATE(S)> <EXAMPLE> 12000 <EXAMPLE> digital raster file 1998 ground condition <EXAMPLE> DOQQ <SOURCE EXAMPLE!!! UPDATE/EDIT ALL SOURCE INFORMATION FIELDS TO YOUR SITUATION> Used as a background image onscreen to help establish relative positions for heads up digiting new features. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION.> Added the <BACKGROUND DIGITAL DATA> into <SOFTWARE AND MODULE>. Created a new <POINT, LINE, or POLYGON> dataset. Using the graphics drawing tools available, sketched new features into the dataset based on prior knowledge of the area shown in the background. Created user defined fields in the feature's attribute table. Interactively populated the fields based on prior knowledge of the features. All features and attributes were verified onscreen.<WHO EVER DID THE PROCESSING>National Park Service, <PARK NAME>, <PARK DIVISION><POSITION TITLE>mailing address

<STREET OR P.O. ADDRESS>

<CITY><STATE><ZIP>USAXXX-XXX-XXXXXXXX_XXXXX@nps.gov9AM to 5PMXXX-XXX-XXXX<YYYYMMDD>DOQQ<EXAMPLE2> 24000<EXAMPLE2> digitial raster dataset<EXAMPLE2> DRGUnited States Geological Survey<YYYY>raster digital data7.5-Minute Series (Topographic)<QUAD NAME> QuadrangleReston,VAUnited States Geological Survey<LIST QUADS AND (PUBLICATION DATES) THEN ADJUST SOURCE_TIME_PERIOD_OF_CONTENT TO CONFORM WITH PUB DATE(S)><SOURCE EXAMPLE!!! UPDATE/EDIT ALL SOURCE INFORMATION FIELDS TO YOUR SITUATION> Used as a background image onscreen to help establish relative positions for heads up digiting new features.<YYYY> Vector SimpleArcFALSE2005FALSEFALSESimpleLabelFALSE840FALSEFALSESimplePolygonTRUE840FALSEFALSESimpleTicFALSE4FALSEFALSE <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> All fields except for the ATTRIBUTE field in the polygon and arc attribute tables were created and maintained by ArcInfo software. The ATTRIBUTE field was added in order to hold the wetland classification type specified on the hardcopy digitized source map. Information about the codes in the ATTRIBUTE field can be found online at ftp://www.nwi.fws.gov/maps/mapcodes.txt and further explained in the following book: Cowardin et al., December 1979, Reprinted 1992, "Classification of Wetlands and Deepwater Habitats of the United States," U.S. Department of the Interior, Fish and Wildlife Service, Washington D.C..none National Park Service, Intermountain Geographic Resource Information Management TeamGIS Coordinator/GIS Specialistmailing and physical address

12795 West Alameda Parkway

LakewoodCO80228USAimro_gis_coordinator@nps.gov8:00 a.m. to 4:00 p.m. MST, Monday through FridayPlease contact through email. <file name here as will be delivered to NCSU> [ie. <PARK4LETTERCODE>_xxxxxx.zip OR PARK4LETTERCODE>_xxxxxx.e00] 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. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. 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 NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on computer systems at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on other systems 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. <Software used to export the data that will reside on the clearinghouse> <Version of your software> <(e.g. .e00, .dbf, .shp, .shx)> no compression applied 1 MB ftp.ncsu.edu/pub/unity/lockers/ftp/npsftp/pub/data/<PARK4LETTERCODE> See NPS Clearinghouse at http://www.nps.gov/gis/data_info/clearinghouse.html None <YYYYMMDD> National Park Service, <PARK NAME>, <PARK DIVISION> <WHOEVER WROTE THE METADATA> <POSITION TITLE> mailing address <CITY> <STATE> <ZIP>

<STREET ADDRESS>

USA XXX-XXX-XXXX XXXX_XXXXXX@nps.gov 9 AM - 5 PM, Monday through Friday XXX-XXX-XXXX FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time enhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile 200606121445230020060612133033002002010217385100{86B43236-2314-464B-89FC-62BD907EA37D}TRUE20060612