National Park Service, <PARK NAME>, <PARK DIVISION> <YYYYMMDD> vector digital data http://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 digitized off of a <1:XXXX> scale hardcopy <PAPER/MYLAR) map using a <DIGITIZING MANUFACTURER AND MODEL> connected to a <UNIX OR PC> running <DIGITIZING 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> 198309 1998 <EXAMPLE> Aerial Photography done in September of 1983. Map finalized in 1998 Complete None planned 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. <FILENAME>.jpg The graphic shows the <FEATURE NAME> in relation to park's boundary. JPEG Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.0.0.535 <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. <EXAMPLE> United States Department of the Interior, Fish and Wildlife Service <EXAMPLE> 1998 <EXAMPLE> map <EXAMPLE> National Wetland Inventory <EXAMPLE> Gunnison Quadrangle <EXAMPLE> Denver, Colorado <EXAMPLE> United States Department of the Interior, Fish and Wildlife Service <EXAMPLE> 24000 <EXAMPLE> Mylar 198309 1998 <EXAMPLE> Aerial photography done in September, 1983. Finalized map published in 1998. <EXAMPLE> nwi_hardcopy <SOURCE EXAMPLE!!! UPDATE/EDIT ALL SOURCE INFORMATION FIELDS TO YOUR SITUATION> Used hardcopy map for digitzing wetlands data. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION. IT IS A SUMMARY OF THE NEXT FOUR STEPS, IF THE DIGITIZING DETAILS IN THE NEXT FOUR STEPS ARE UNKNOWN> Digitized the hardcopy <MYLAR or PAPER> map using <SOFTWARE NAME> software on a <DIGITIZER BOARD MAKE AND MODEL IF KNOWN> digitizing board. All features digitized in <STREAM or NONSTREAM> mode. Using <SOFTWARE NAME>, converted dataset from digitizer units to map units. Verified that all features were present and overlayed with data in the same projection to verify proper alignment. Added user defined fields to the attribute table and attributed the features. <SOURCE1> <YYYYMMDD> <WHO EVER DID THE PROCESSING> National Park Service, <PARK NAME>, <PARK DIVISION> <POSITION TITLE> mailing address

<STREET OR P.O. ADDRESS>

<CITY> <STATE> <ZIP> USA (999) 999-9999 (999) 999-9999 XXXX_XXXX@nps.gov 9AM to 5PM <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Digitized the hardcopy Mylar map using ArcInfo ver 7.1 software on a Unix machine and an Altek, model AC41 digitizing board. Map was digitized in digitizer units (inches) with a minimum of four tics. Before any features were digitized, ArcInfo TOLERANCE command set nodesnap at 0.05, weed at 0.00000001, grain at 0.00000001, and snap at 0.0005. A RMS error of 0.005 or less had to be achieved during map registration in order to digitize arc features. All features digitized in nonstream mode. <YYYYMMDD> <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Checked coverage for node errors and densified arcs. Moved coverage to another computer with ArcInfo ver. 8.0 and the Windows NT operating system. Ran a CLEAN command with 0.00000000001 fuzzy and 0 dangle tolerance. Opened coverage with ArcInfo's ArcEdit module and verified completeness of arcs and polygons, deleted sliver polygons, and compared for completeness against hardcopy source map. While still in ArcEdit, selected all arcs and ran the DENSIFY command to create extra verticies 0.025 digitizer inches apart. <YYYYMMDD> <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Converted coverage from digitizer units to map units. Used USGS 1:24K DRGs, which served as the basemap for the hardcopy source map, to lookup map coordinates (in UTM, NAD27, zone 13, meters) for each tic. Created a new, blank coverage in a different workspace with same tic ids and map coordinates. Ran the TRANSFORM command with the "affine" option. The RMS Error for the conversion was (input,output) = (0.003,2.011). <YYYYMMDD> <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Created labels for each closed polygon and attributed polygons. Used the ArcInfo CREATELABELS command to add label points to all closed polygons. Polygon topology was rebuilt with the BUILD command. Added item, ATTRIBUTE, to the polygon and arc attribute tables. Opened coverage in ArcView ver. 3.2 and attributed the new field in both the polygon attribute and arc attribute tables. While attributing, missing or deviant arcs and polygons are identified. Errors were corrected in ArcInfo's ArcEdit module. After all polygons and arcs were attributed and corrected, topology was reestablished with the BUILD command. <YYYYMMDD> <WHO EVER DID THE PROCESSING> National Park Service, <PARK NAME>, <PARK DIVISION> <POSITION TITLE> mailing address

<STREET OR P.O. ADDRESS>

<CITY> <STATE> <ZIP> USA (999) 999-9999 (999) 999-9999 XXXX_XXXX@nps.gov 9AM to 5PM Vector <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

<STREET ADDRESS>

<CITY> <STATE> <ZIP> USA XXX-XXX-XXXX XXX-XXX-XXXX XXXX_XXXXXX@nps.gov 9 AM - 5 PM, Monday through Friday FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile {B969F58F-C533-45FA-98DC-453DD0BDB870}2006061210464600TRUE200606121442360020060612