National Park Service, <PARK NAME>, <PARK DIVISION> <YYYYMMDD> vector digital datahttp://www.nps.gov/gis/ This is a vector (...point, line, or polygon) file showing the <FEATURE TYPE> at <PARK NAME>. The coordinates for this dataset were collected using a <LIST GPS RECEIVER MANUFACTURER AND MODELS ie ....Trimble ProXR, Trimble ProXL, and a GeoExplorer2>. 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 SPEEL IN ABOUT PARK HERE> <YYYYMMDD> <YYYYMMDD> ground condition Complete As needed none gps, global positioning system, <LIST FEATURES IN DATASET> none <PARK NAME>, <PARK4LETTERCODE>, National Park Service, NPS, United States, US, USA, North America, <STATE>, <COUNTY or COUNTIES> none 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. <PARK4LETTERCODE>_xxxxx.jpg A graphic display of the <FEATURE TYPE> in relation to the park's legislative boundary. JPEG National Park Service, <PARK NAME>, <PARK DIVISION> 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> Data collection was streamlined through use of data dictionaries attribute menus installed in the Global Positioning System (GPS) data logger. This procedure enhances attribute accuracy by reducing attribute related decision-making in the field and minimizing keying errors. Park staff have ground checked and verified all features to the best of their knowledge. GIS personnel verified all features and attributes. There are no duplicate features present. Polygon features (if present) begin and end at the same point. <ARCINFO USERS NEED TO STATE WHETHER THE BUILD OR CLEAN COMMAND WAS USED TO UPDATE TOPOLOGY>. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> The data only includes features shown to the GPS collection team by a park staff member while on site. Additional features may exist at Fort Laramie NHS. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> The data were collected according to an accuracy standard of maintaining a maximum PDOP (Position Dilution of Precision) of 6, while tracking a minimum of 4 SV (satellite vehicles). These data were differentially corrected and have estimated accuracies in the X and Y direction of 0 to 5 meters, using the above standards while SA (selective availability) is set to zero. No tests were done to confirm this. In Trimble Pathfinder Office software, accuracy is not represented. Instead, precision is an estimation of the positional error (closeness to truth) available as feature attributes. To estimate precisions the software uses: receiver type (for noise), baseline length, Dilution of Precision, covariance and reference variance components. It is a repeatability measure not an accuracy measure. Horizontal Precision for line and area features looks at all the individual points that make up the line/area feature and a mean value is computed by the software. United States Geological Survey <YYYY> raster digital data 7.5-Minute Series (Topographic) <QUAD NAME> Quadrangle United States Geological Survey Reston,VA <EXAMPLE1> 24000 <EXAMPLE1> digital raster dataset <YYYY> publication date <EXAMPLE1> DRG <EXAMPLE1> Provided an image of area features for comparison to GPS data. National Park Service, <PARK NAME>, <PARK DIVISION> Unpublished Material vector digital data <EXAMPLE2> 2400 <EXAMPLE2> digital data file <YYYYMMDD> <YYYYMMDD> ground condition <EXAMPLE2> GPS data <EXAMPLE2> Provided coordinates for features U.S. Geological Survey <YYYYMMDD> remote-sensing image Reston,Va U.S. Geological Survey Digital Orthophoto Quarter Quad<QUAD NAME> Quadrangle <NE, NW, SE, OR SW> <EXAMPLE3> 12000 <EXAMPLE3> digital raster dataset <YYYYMMDD> ground condition <EXAMPLE3> Doqq_<NE, NW, SE, OR SW> <EXAMPLE3> Provided an image of area features for comparison to GPS data. <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> The transportation theme was included as road and trail features in the data dictionary attribute menu for use in the GPS data logger. GPS based coordinates were collected at Fort Laramie NHS during June of 2002 using Trimble ProXR and GeoExplorer3 receivers in datum NAD83, UTM - zone 13, meters coordinates. A maximum Position Dilution of Precision (PDOP) of 6 was maintained for each set while tracking a minimum of 4 satellite vehicles. GPS data <YYYYMMDD> <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> The GPS processing software was Trimble Pathfinder Office Version 2.51. GPS files were differentially corrected using Trimble Community Base Station data from the University of Wyoming site. The corrected GPS files were edited for known deviant and duplicate data. The Pathfinder Office Combine utility was used to merge features collected with identical data dictionaries by different GPS collection teams throughout the 2 day collection period. The combined features were then exported into ESRI ArcView version 3.2 shapefile format. GPS data <YYYYMMDD> GPS data <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Feature data was compared to features in the digital raster graph and digital orthophoto quarter quads for accuracy. GIS personnel verified all features and attributes. GPS data, DRG, DOQQ_XX <YYYYMMDD> National Park Service, <PARK NAME>, <PARK DIVISION> <WHO EVER DID THE PROCESSING> <POSITION TITLE> XXX-XXX-XXXX XXX-XXX-XXXX XXXXX@nps.gov 9AM - 5PM MST, Monday through Friday mailing address <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> The first 2 items in the attribute table are the default attribute information found in the ArcView shapefile format. The next 2 items, TYPE & COMMENTS were user-defined attributes from the GPS's datalogger data dictionary user input. The last item, MARKINGS, was created while in ArcView to add additional field note information. The remaining items had Pathfinder software produced values: PDOP_MAX, CORR_TYPE, RCVR_TYPE, GPS_DATE, GPS_TIME, DATAFILE, UNFILT_POS, FILT_POS, UPDATE_STA, STD_DEV, GPS_HEIGHT, HORZ_PREC, VERT_PREC. The user-defined items and values are described in detail above. Contact ESRI (Environmental Systems Research Institute, Inc.) for detailed explanations of their internal file structure at "http://www.esri.com". Contact Trimble at http://www.trimble.com" for a more detailed explanation of generated attributes that can be exported for feature type. 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>_xxxxxx.zip 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 be 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 a computer system at the National Park Service, 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. ArcView shapefile 3.2 WinZip 1MB http://www.nps.gov/gis/ none <YYYYMMDD> <POSITION TITLE> physical address XXX-XXX-XXXX XXX-XXX-XXXX XXX_XXXXX@nps.gov 9AM - 5PM MST, Monday through Friday none National Park Service, <PARK NAME>, <PARK DIVISION><WHOEVER WROTE THE METADATA> FGDC Content Standards for Digital Geospatial Metadata 1998 none none 200606121519560020060612