National Park Service, <PARK NAME>, <PARK DIVISION> <YYYYMMDD> vector digital data http://www.nps.gov/gis/ <EXAMPLE - EDIT WORDING TO FIT YOUR FIRE SITUATION> This vector data depicts the daily fire progress of the <Wildland Fire name> fire in <Park Name> of <State>. The fire started on <Date> by lightning and was classified as a 'Wildland Fire' to be managed for resource benefits. Data was collected on an 'as needed' basis, i.e. when significant change to the fireline occurred. To show the location of the <Wildland Fire Name> at <Park Name>. The data was collected to support planning and fire management efforts while the fire was ongoing. 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. <YYYYMMDD> <YYYYMMDD> ground condition Complete None planned None Fire progression, wildland fire, fire perimeter, <Wildland Fire Name> Fire <PARK NAME>, <PARK4LETTERCODE>, National Park Service, NPS, United States, US, USA, North America, <STATE>, <COUNTY or COUNTIES>, <ECOREGION> 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>_<Wildland Fire Name>_fire_progression.jpg A graphic display of the <Wildland Fire Name> fire 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 Attributes were created as the features were digitized from daily field information using firepak.avx (the National Park Service fire attributing extension) to ensure more consistent attributes and to minimize data entry errors. The attributes were verified daily upon creation. There are no duplicate features present. Polygon features begin and end at the same point. <ARCINFO USERS NEED TO STATE WHETHER THE BUILD OR CLEAN COMMAND WAS USED TO UPDATE TOPOLOGY>. This dataset is considered to be 100% complete for the <Wildland Fire Name> fire. Data was digitized from hand drawn fire perimeter lines on a 7.5 min, paper topographic quadrangle. The hand drawn lines can be considered no more accurate than within 10 - 20 meters of the actual position of the fire perimeter and in some cases the line may only be within one-quarter mile of the actual fire perimeter. This is dependent on the skill of the interpreter in determining the position of the fire on the map while flying above it. A digital version of the topo map was used as a backdrop during 'heads-up' digitizing to recreate the original lines. 24000 paper ground condition U.S. Geological Surveymap<LIST QUADS AND (PUBLICATION DATES) THEN ADJUST SOURCE_TIME_PERIOD_OF_CONTENT TO CONFORM WITH PUB DATE(S)> <THE FOLLOWING STATEMENT IS AN EXAMPLE OF DIGITIZED DATA, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Data was created daily or as needed when significant change had occurred to the fire. Fire perimeter was created by hand drawing a line on a 7.5 minute topographic map as the perimeter was flown in a helicopter or fixed wing airplane. This line was then digitized 'heads-up' on a digital raster graph backdrop in a shapefile format. The DRG was in a UTM, zone <XX> projection with a NAD<XX> datum so the digitized fire perimeter is in the same projection. Data was attributed using the NPS Fire Boundary Editing and Attributing Toolkit (Firepak) ArcView Extension. <YYYYMMDD> <THE FOLLOWING STATEMENT IS AN EXAMPLE, PLEASE EDIT/UPDATE TO APPLY TO YOUR SITUATION> Daily additions to the fire were digitized in ArcView using the 'Append Polygon' digitizing tool <YYYYMMDD> <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. <YOUR NAME>National Park Service, <PARK NAME>, <PARK DIVISION>> XXX-XXX-XXXXXXX-XXX-XXXXfirstname_lastname@nps.gov<YOUR POSITION TITLE>8:00am-4:00pm MST <YYYYMMDD> Vector coordinate pair SHAPE, ID are software generated fields. UNITID is a text field that describes the location of the fire such as the park name or 4 letter park code. FIRENAME and FIRENUM are text fields containing the name of the fire and the fire number as assigned to the incident. DATE is a text field in the format <YYYYMMDD> and TIME is 24 hour military time <HHMM>. These fields represent the time that the fire perimeter was collected for that date. METHOD is a text field representing how the data was collected. Values are 'GPS' or 'Digitized' as a choice in the Firepak extension. SOURCE is a text field that represents the source of the perimeter. If the METHOD of collection is 'GPS', SOURCE will be the type of GPS unit used to collect the data. If the METHOD is 'Digitized', the SOURCE will be the data source the perimeter is drawn on or derived from. Values are chosen from pull down menus in the Firepak extension. TRAVEL is a text field representing the method of travel for GPS Data collection. Valid values are 'Helicopter', 'Fixed Wing', 'ATV', 'Foot', 'Other' as chosen from Firepak. DIFFERENTL is a text field that is only populated if the SOURCE is 'GPS'. Valid values are 'None', 'WAAS', 'CORS' or 'Post Processing'. MAPSCALE is a text field that is only populated when the METHOD is 'Digitized'. This represents the scale of the map that the perimeter was drawn on or scale of the imagery that it was derived from. CONTACT, PHONE, EMAIL are text field representing the name of the person who collected the data and their contact information. PROJECTION is a text field representing the projection of the data. If the projection is 'UTM', the field will include the Zone. UNITS is a text field describing the coordinate units that describe the theme's spatial information. The UNITS will vary according to the projection. Values available through the Firepak extension are; 'Decimal Degrees', Meters', 'Feet' or 'Other'. DATUM is a text field describing the datum used for the PROJECTION of the data. Values available are; 'WGS84', 'NAD83', 'NAD27' or 'Other'. COMMENTS is a text field that is any additional information regarding the data as noted by the CONTACT. ACRES is the area of the polygon in acres and is generated by Firepak as a 3 decimal number field once attributing is completed. PERIM_MILES is the length of the perimeter of the polygon in miles and is generated by Firepak as a 3 decimal number field once attributing is completed. The user-defined items and values are decribed in detail above.Contact ESRI (Environmental Systems Research Institute, Inc.) for detailed explanations of their internal file structure at "http://www.esri.com". 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>_<Wildland Fire Name>_fire_progression.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 (i.e. "GIF or JPG" format files) 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. zip Data available on NPS GIS spatial data clearinghouse at http://www.nps.gov/gis/ <YYYYMMDD> <WHOEVER WROTE THE METADATA> National Park Service, <PARK NAME>, <PARK DIVISION> <POSITION TITLE> mailing and physical address XXX-XXX-XXXX XXX-XXX-XXXX firstname_lastname@nps.gov M-F 8:00-4:00 (Mountain) FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile 200606121512570020060612