Developing an Interagency Standard for the Transfer and Documentation of
GIS Fire Perimeters

**ABSTRACT**

One of the most important pieces of information collected on any
wildland fire incident is the incident's fire perimeter. This Geographic
Information System (GIS) layer is vital to the management of the
incident itself. In addition, it is often transferred to a number of
groups including neighboring incidents, incoming incident management
teams, the home unit, the public as well as regional and national
coordinating groups and applications. In order to correctly use and
display transferred fire perimeter GIS data, information pertaining to
the methods of collection and projection parameters must also be
transferred. Without information describing when the perimeter was
collected, how it was collected, who collected it, and in what
coordinate system/datum it finally resides, the fire perimeter GIS layer
is all but useless except to the individuals who collected it. At this
time, there is no standard for the transfer of fire perimeters and their
attributes between incidents, agencies, and national/regional groups and
applications. Because of the importance of GIS fire perimeter layers at
all levels of incident management, because of the need to transfer GIS
fire perimeter layers between incidents and any number of outside
government and non-government bodies, and because of the inherent
uncertainty of all variables involved in the collection of fire
perimeters, an interagency transfer standard for ongoing wildland fire
perimeter GIS data should be developed, approved and implemented.
Outlined in this white paper are recommendations from the Geospatial
Task Group (GTG). The GTG recommends that the National Wildfire
Coordinating Group (NWCG) adopt fire perimeter transfer standards for
ongoing fires. Specifically, the GTG recommends a transfer strategy in
which fire perimeter collection information is transferred by embedding
it as a set of standardized attributes within the fire perimeter GIS
layers.

**INTRODUCTION**

The current fire perimeter is one of the most important pieces of
information collected on any wildland fire incident. This single piece
of information answers questions such as:

-   Where is the fire now?

-   How big is it?

-   How close is it to values at risk?

-   How has the fire size changed since its last measure?

As information technology evolves and spreads to the incident management
of wildland fire, this valuable piece of information more often than not
resides as a dataset in a Geographic Information System (GIS). When
combined with the power of GIS, fire perimeter data gathered using
Global Positioning Systems (GPS), or other means, can be displayed on
incident maps and the Internet only minutes after collection. Fire
perimeter GIS data can be overlayed on numerous other GIS layers such as
agency boundaries, topography and fuels in order to create dynamic maps
that can be used by incident management teams for decision making and
communication needs.

For many years, wildland fire perimeter data has been collected on large
fires in a digital format and incorporated into a GIS. Daily fire
perimeter GIS layers were created for the 1988 fires in Yellowstone
National Park. For the past five years, the Bureau of Land Management
(BLM) has specified that GIS fire perimeters be created for wildland
fires greater than 10 acres in the conterminous United States, and 100
acres in Alaska. Once fire perimeters were separated from the paper map
and incorporated into a GIS, efforts began to establish means for
communicating important information about the fire perimeter such as
time of collection, method of collection, map projection, etc. Recently,
California, through the organization of the FIRESCOPE GIS Specialist
Group, created an exchange format that uses file naming conventions to
transfer information about the fire perimeter. The BLM has created a
standard that relates fire perimeters back to the DI-1202 fire
occurrence database. In 2001, GeoMAC (www.geomac.gov) created another
data standard for the transfer of ongoing fire perimeters. In the GeoMac
standard, an upload form was used to populate a fire perimeter shapefile
or coverage data table with relevant collection and attribute
information. Finally, during the summer of 2001, the National Park
Service Alaska Support Office also developed a standard list of
attributes for ongoing fire perimeters. In addition, a tool was
developed for ArcView 3.2 that allows users to enter data capture and
projection information into onscreen forms. Once entered, this
information is immediately added as attributes to the fire perimeter GIS
layer.

While an individual fire perimeter is a relatively simple GIS layer to
create and display, a number of unknown variables are involved in its
creation. Unfortunately, information about the methods used to create
and process the fire perimeter can be just as important as the fire
perimeter data itself. A given fire perimeter can be collected in a
number of ways: GPS, digitized from aerial-hand drawn sketches, IR
interpretation, satellite imagery, etc. Various levels of accuracy and
data quality are implicitly associated with each of these collection
methods. Even within the confines of perimeters collected using GPS
units, a number of additional variables arise which directly pertain to
the accuracy and appropriate use of the data in question:

-   What type of GPS unit was used in collection?

-   What travel method was used in navigating the fire perimeter?

-   Was the data differentially processed?

Information about when the perimeter was collected is also required for
appropriate use of the data. Oftentimes, fire perimeters are transferred
to neighboring incidents with no explicit statement about when the fire
was mapped. It is important to know if a fire perimeter from a nearby
incident was collected this morning or three days ago. Fire perimeter
projection information is also vital. The Arc/Info and Arcview ESRI GIS
products support a total of 48 different map projections. This number
dramatically increases when one considers complexities introduced by UTM
zones, State Plane projection FIPS zones and individual projection
parameters. In addition, four different datums are commonly used
throughout North America: NAD27 Alaska, NAD27 CONUS, NAD83 and WGS84.
Even if the projection and datum of a fire perimeter are known,
different units can be used to characterize location (feet vs. meters).
Truly, a multitude of potential projection parameters exist for any
single undocumented fire perimeter. A fire perimeter that is used in the
wrong projection by individuals outside the incident may be worse than
useless. In order to correctly use and display fire perimeter data,
collection information must also be transferred in a consistent and
understandable format.

With new fire perimeters collected daily (or more frequently) fire
perimeter management becomes a challenge in and of itself for the
incident GIS Technical Specialist (GIST) or Display Processor (DPRO).
Each fire perimeter has numerous characteristics related to the methods
used in collection and GIS processing parameters such as projection and
datum. Currently, GISTs and DPROs across the country use a variety of
means to document the attributes of an individual fire perimeter
including the name of the fire, the date the perimeter was collected,
who collected the perimeter, the methods that were used to collect the
perimeter and the perimeter's final projection information. This data
about data, or metadata, is of vital importance to incident management.
Without information describing when the perimeter was collected, how it
was collected, who collected it, and in what coordinate system/datum it
finally resides, fire perimeter GIS layers are all but useless except to
the individuals involved in collection. Information about fire perimeter
collection becomes even more important when incident management
transitions between teams or between a team and the home unit. Many
fruitless hours have been wasted by GISTs and DPROs in an effort to
determine from a pile of GIS datasets, which is the current fire
perimeter, when it was collected and in what projection it should it be
displayed. This information is also vital to the home unit for the
creation of accurate fire progression and fire history GIS layers with
FGDC Compliant Metadata.

The importance and value of current-fire perimeter GIS layers extends
well beyond the geographic and temporal scope of the fire incidents from
which they arise. Current fire perimeters are transferred between
neighboring incidents and agencies and also between incidents and
regional/national bodies such as Geographic Area Coordination Centers
and Multi-Agency Coordination Groups. Beginning in 2000, fire perimeter
GIS layers have also been transferred from incidents to national
fire-mapping applications like GeoMAC (www.geomac.gov). Again,
information pertaining to the capture and display characteristics of the
fire perimeter are vital for correct use, display and analysis by
neighboring incidents, national/regional applications and the public.

Currently, there is no standard for the transfer of fire perimeters and
their attributes between incidents, agencies, and national/regional
groups and applications. Because of the importance of GIS fire perimeter
layers at all levels of incident management, because of the need to
transfer GIS fire perimeter layers between incidents and any number of
outside government and non-government bodies, and because of the
inherent uncertainty of all variables involved in the collection of fire
perimeters, an interagency transfer standard for ongoing wildland fire
perimeter GIS data should be developed, approved and implemented.

For the purposes of this paper, an interagency transfer standard
encompasses both the file format of the fire perimeter as well as
necessary information about the fire perimeter. The dominance of ESRI
software products in the GIS market has all but insured the default
adoption of the shapefile (.shp) and arc export coverage format (.e00)
as standard data types for the transfer of fire perimeters. The true
scope of this paper lies in the realm of the transfer of fire perimeter
metadata (information about the data) between incidents, agencies,
management teams, and national/regional groups and applications.

A case example from the 2000 fire season will help illustrate the need
for a transfer standard for wildland fire perimeters. In August 2000,
hundreds of fires were active across the West and had consumed all
available resources. During this time of unprecedented activity, the
Eastern Great Basin Geographic Area was faced with the challenge in
which each fire was screaming for resources with only limited resources
to be found. As a solution, an application was created that allowed the
Eastern Great Basin managers to view each fire's location, its
perimeter, and its proximity to values at risk in an effort to
prioritize where their limited resources should be placed. This was a
great idea in theory and was also the idea that created GeoMAC. However,
the GIS specialists that were inputting daily perimeters from many
different fires in multiple states soon realized that each perimeter had
it own set of attributes and its own unique projection that were
different from fires that were only miles away. This created chaos at
individual fires that were burning towards each other, at complexes and
at area command centers. Soon perimeter boundaries were being mixed up
and portrayed incorrectly.

An additional local example from the 2000 fire season highlights the
need for the transfer of collection information along with fire
perimeters. In August of 2000, a Type II Incident Management Team was
assigned to manage the Glade fire burning immediately south of
Yellowstone National Park in the John D. Rockefeller Memorial Parkway.
Prior to signing a limited Delegation of Authority, negotiations
occurred between the incoming team and Yellowstone staff regarding the
nature and extent of suppression actions within Yellowstone should the
Glade fire cross the park boundary. While negotiations were ongoing, a
current fire perimeter for the Glade fire was transferred to Yellowstone
fire management staff. The projection information for the perimeter was
unspecified but was assumed to be UTM zone 12, datum unknown. When
displayed using the NAD83 datum, the Glade fire appeared to have already
crossed into Yellowstone. When displayed using the NAD27 datum, the
northern edge of the fire was still located hundreds of meters south of
the boundary. With an incident management team on hold, the critical
location of the Glade fire in relation to the Yellowstone boundary could
not be determined. The chaos of August 2000 has led the GTG to write
this white paper on fire perimeter data transfer standards.

# 

# 

# PROBLEM STATEMENT

#  

While wildland fires are actually occurring, there is a need to transfer
fire perimeter data in a consistent format to local and National
applications. Currently no standard exists for the transfer of fire
perimeters and, more importantly, the transfer of information about fire
perimeters.

# PROPOSED SOLUTION

## Introduction of solution

In an effort to simplify, there are three general approaches that can be
used to transfer fire perimeters and fire perimeter metadata.

> 1\. Create FGDC Compliant Metadata for all fire perimeters gathered on
> incidents at the time of collection. Transfer FGDC Compliant Metadata
> along with the perimeters.
>
> 2\. Specify data collection parameters in a standardized file-naming
> convention
>
> 3\. Specify data collection parameters in attributes residing within
> the data itself

While options one and two are viable, neither presents a preferred
approach. Simply stated, it is unrealistic to recommend or expect that
FGDC Compliant Metadata be created for all fire perimeters at the time
they are collected. Specifying data collection parameters in a
standardized file-naming convention is also unrealistic. As the names of
files become long and cumbersome the file-naming convention standard
becomes impractical.

## Application of Solution

The authors recommend the adoption of a fire perimeter transfer standard
in which data collection parameters are embedded as attributes within
the shapefile or coverage .DBF or INFO tables. This method permanently
attaches the vital collection information to the perimeter itself. By
default, attribute information about the fire perimeter will
effortlessly be transferred with the fire perimeter.

A solution which calls for the specification of metadata in dataset
attributes requires a standard list of robust attributes that capture
the numerous potential methods of capture and GIS processing steps. In
2001, the National Park Service Alaska Support Office developed a
standard list of attributes for ongoing fire perimeters. In addition, a
tool was developed for ArcView 3.2 that allows users to quickly and
efficiently enter data capture and projection information into onscreen
forms. Once entered, this information is immediately added as attributes
to the fire perimeter GIS layer. The details of this solution are
explained in Appendix A. The US Forest Service and National Park Service
have adopted this solution as a standard means for attributing daily
fire perimeters with data collection and processing information for the
2002 fire season. The authors recommend that the set of attributes
outlined in Appendix A be added to ongoing fire perimeter GIS data prior
to transfer to bodies outside the scope of the individual incident.

# Future Direction/Long-Term Focus

Application of the proposed solution is fully operational for those
using Arcview 3.2 GIS software. An extension is available that
automatically adds the attributes listed in Appendix A to a fire
perimeter shapefile or coverage data table and populates those
attributes with user input to a Fire Perimeter Attributes form. Using
the extension, fire perimeter attributes can easily be added to a
shapefile or coverage in Arcview 3.2 with less than one minute of
processing time. A similar application is not yet available for those
using other ESRI GIS software products for fire perimeter processing:
ArcMap and command line Arc/Info. Many agencies are beginning to phase
out of the Arcview 3.x application in favor of ArcGIS 8.1 software.
While the recommended attribute structure can still be added and
populated manually in ArcMap or command-line Arc/Info, efforts should be
made to create data entry devices which enable users to efficiently
apply the recommended standard to fire perimeter data processed outside
of the Arcview 3.2 environment.

This solution should be viewed as an interim approach to the fire
perimeter transfer problem. With recent advances in geospatial
technology, the authors expect that proposed solution 1, ("Create FGDC
Compliant Metadata for all fire perimeters gathered on incidents at the
time of collection. Transfer FGDC Compliant Metadata along with
perimeters.") will eventually be able to be reached within the next 10
years. It is also felt that there should be one interagency repository
for this GIS fire perimeter data at NIFC so that GIS specialists can
upload perimeters to this database via the Internet. This database would
also have a user friendly interface that the GIS specialist could
extract fire perimeter data from. This data could then be used to update
other GIS layers like condition classes, fuel models, and vegetation
classes and it could also be used to improve empirical wildfire models.

**Conclusion**

One of the most important datasets for the wildland fire community is
the actual GIS fire perimeter. Many wildland fire managers, researchers,
the media, and the public have needs to see fire perimeter data. The GTG
recommends that Solution 3 be adopted by the NWCG as the wildland fire
perimeter transfer standard.

# Appendix A -- The Detailed Solution

The recommended solution suggests that the information in Table 1 be
added as attributes to the .dbf or INFO tables of all wildland fire
perimeter shapefiles and coverages at the time of collection.

Table 1: Recommended attribute information

+---------------+------------------------------------------------------+
| **Attribute   | **Definition**                                       |
| Name**        |                                                      |
+---------------+------------------------------------------------------+
| Agency        | The code to identify the agency where the fire is    |
|               | occurring                                            |
+---------------+------------------------------------------------------+
| Unit ID       | The agency code used to identify the unit in which   |
|               | the fire is occurring                                |
+---------------+------------------------------------------------------+
| Fire Name     | The name of the fire                                 |
+---------------+------------------------------------------------------+
| Fire Number   | The local number assigned by the relevant land       |
|               | management agency to the fire                        |
+---------------+------------------------------------------------------+
| Collection    | The date the fire perimeter was collected in         |
| Date          | YYYYMMDD format                                      |
+---------------+------------------------------------------------------+
| Collection    | The time the fire perimeter was collected in HHMM    |
| Time          | format                                               |
+---------------+------------------------------------------------------+
| Collection    | The method of collection: GPS vs. digitized          |
| Method        |                                                      |
+---------------+------------------------------------------------------+
| Source        | If the fire perimeter was collected using GPS, the   |
|               | GPS unit that was used for collection. If the fire   |
|               | perimeter was digitized, the source of the map used. |
+---------------+------------------------------------------------------+
| Travel Method | If the fire perimeter was collected using GPS, the   |
|               | method of travel that was used to circumnavigate the |
|               | fire                                                 |
+---------------+------------------------------------------------------+
| Differential  | If the fire perimeter was collected using GPS, the   |
| Correction    | type of differential processing that was completed   |
| Methods       |                                                      |
+---------------+------------------------------------------------------+
| Mapscale      | If the fire perimeter was digitized the mapscale at  |
|               | which it was digitized.                              |
+---------------+------------------------------------------------------+
| Contact Name  | The name of the individual who should be contacted   |
|               | regarding questions about the fire perimeter,        |
|               | usually the individual who collected the fire        |
|               | perimeter or the GIS Technical Specialist on the     |
|               | incident                                             |
+---------------+------------------------------------------------------+
| Contact Phone | The phone number of the individual who should be     |
| Number        | contacted regarding questions about the fire         |
|               | perimeter, usually the individual who collected the  |
|               | fire perimeter or the GIS Technical Specialist on    |
|               | the incident                                         |
+---------------+------------------------------------------------------+
| Contact email | The email of the individual who should be contacted  |
|               | regarding questions about the fire perimeter,        |
|               | usually the individual who collected the fire        |
|               | perimeter or the GIS Technical Specialist on the     |
|               | incident                                             |
+---------------+------------------------------------------------------+
| Projection    | The projection of the fire perimeter GIS layer       |
+---------------+------------------------------------------------------+
| Units         | The map units used to create the GIS layer           |
+---------------+------------------------------------------------------+
| Datum         | The datum used to create the GIS layer               |
+---------------+------------------------------------------------------+
| Comments      | Comments pertaining to any relevant aspect of the    |
|               | fire perimeter or fire perimeters described in the   |
| ## Acres      | GIS layer                                            |
|               |                                                      |
| ## Per        | ## Fire Size in Acres                                |
| imeter Length |                                                      |
|               | ## Length of Perimeter in Miles                      |
+---------------+------------------------------------------------------+

Table 2: Detailed List of Attributes

  ---------------- ----------- ------------ -------------------- ----------------- -------------------
  **Attribute**    **Data      **Length**   **Description**      **Domain**        **Examples**
                   Type**                                                          

  ** **            ** **       ** **        ** **                ** **             ** **

  **Agency**       Character   15           The agency           ** **             FS, BLM, NPS, FWS
                                            administering the                      
                                            land on                                

  ** **                                     which the fire is    ** **             ** **
                                            burning                                

  ** **            ** **       ** **        ** **                ** **             ** **

  **UnitID**       Character   15           The administrative   n/a               YELL, EVER, DENA
                                            unit in which the                      
                                            fire                                   

  *** ***                                   is burning                              

  *** ***                                                                           

  **Firename**     Character   30           Name of fire         n/a               Hellroaring, Big
                                                                                   Bar

  *** ***                                                                           

  **Firenum**      Character   14           Fire Number          n/a               B242, 0001,
                                                                                   MT-NCD-0003

  ** **                                                                             

  **Date**         Character   8            Date fire perimeter  YYYYMMDD          20000820, 19990704
                                            was collected                          

  ** **                                                                             

  **Time**         Character   4            Military time fire   HHMM              1100, 1630
                                            perimeter was                          
                                            collected                              

  ** **                                                                             

  **Method**       Character   50           Method of            GPS, Digitized    GPS, Digitized
                                            collection: GPS or                     
                                            Digitized                              

  ** **                                                                             

  **Source**       Character   24           Source of                               
                                            collection;                            

                                            if *method* =        Garmin GPS III+,   
                                            \'GPS\', *source*                      
                                            identifies                             

                                            type of GPS unit     Garmin V, Garmin   
                                                                 etrex             

                                                                 Garmin etrex,      
                                                                 PLUGR GPS,        

                                                                 Trimble            
                                                                 GeoExplorer       
                                                                 II/III            

                                                                 Trimble            
                                                                 Pathfinder Pocket 

                                                                 Trimble ProXR,     

                                                                 Other (identify)   

                                            if *method* =        Aerial Hand Drawn  
                                            \'Digitized\',                         
                                            *source*                               

                                            identifies map       IR                 
                                            source               Interpretation,   
                                                                 IKONOS            

                                                                 Landsat, Landsat   
                                                                 DeltaNBR          

                                                                 Other (identify)   

                                                                                    

  **Travel**       Character   24           if *method* =        Helicopter, Fixed  
                                            \'GPS\', *travel*    Wing              
                                            identifies                             

  ** **                                     means of travel      ATV, Foot, Other   
                                            around fire          (identify)        

  ** **                                                                             

  **Differentl**   Character   24           if *method* =        No Correction,     
                                            \'GPS\',                               
                                            *differentl*                           
                                            identifies                             

  ** **                                     means of             Real-time WAAS,    
                                            differential                           

  ** **                                     correction           Real-time CORS,    

  ** **                                                          Post-Processing    

  ** **                                                          Other (identify)   

  ** **                                     if *method* =                           
                                            \'Digitized\',                         
                                            *travel* = null                        

  ** **                                                                             

  **Mapscale**     Character   24           if *method* =        24,000, 63,360,    
                                            \'Digitized\',       100,000           
                                            *mapscale*                             

  ** **                                     identifies the scale 250,000, Other     
                                            at which             (identify)        

  ** **                                     the perimeter was                       
                                            digitized                              

  ** **                                     if *method* =                           
                                            \'GPS\', *mapscale*                    
                                            = null                                 

  ** **                                                                             

  **Contact**      Character   50           Incident contact     n/a               Jane Doe, Bob
                                            person for fire                        Marley
                                            perimeter                              

  ** **                                                                             

  **Phone**        Character   30           Contact person\'s    n/a               \(612\) 545-2701
                                            phone number                           ext. 12345

  ** **                                                                             

  **Email**        Character   50           Contact person\'s    n/a               <sbear@fs.fed.us>
                                            email                                  

  ** **                                                                            [ ]{.underline}

  **Projection**   Character   24           Projection of fire   Geographic, UTM    
                                            perimeter shapefile/ Zone x,           

  ** **                                     coverage             Alaska Albers,     

  ** **                                                          Other (identify)   

  ** **                                                                             

  **Units**        Character   24           Projection units of  Decimal Degrees,   
                                            fire perimeter       Meters            

  ** **                                     shapefile/coverage   Feet, Other        
                                                                 (Identify)        

  ** **                                                                             

  **Datum**        Character   24           Datum of fire        WGS84, NAD27,      
                                            perimeter shapefile/ NAD83             

  ** **                                     coverage             Other (identify)   

  ** **                                                                             

  **Comments**     Character   255          Comments             n/a               Fire perimeter was
                                                                                   smokey

  ** **                                                                            on west side; could
                                                                                   not map

  ** **                                                                            accurately on west
                                                                                   side

                                                                                   

  **Acres**        Number      16           Calculated size in                      
                                            acres                                  

                                                                                   

  **Perim_mile**   Number      16           Calculated perimeter                    
                                            length in miles                        
  ---------------- ----------- ------------ -------------------- ----------------- -------------------

Figure 1: Screen 1 of ArcView 3.2 Fire Perimeter Attributes Function

![](media/image1.jpeg){width="3.384027777777778in"
height="3.7402777777777776in"}

Figure 2: Screen 2 of ArcView 3.2 Fire Perimeter Attributes function

![](media/image2.jpeg){width="3.316666666666667in"
height="3.6743055555555557in"}

# Appendix B -- Past Efforts

# 1) FireScope Data Standards

For the name of the shape file, the following items are linked together
to create the name of the shape file:

Fire Name

Date

Time

Projection

# 

# 2) BLM Data Standards for Fire Perimeters

Number range CHAPTER**Goal:** In 1998, BLM created a Bureauwide
Geographic Information System (GIS) polygon theme for wildland fires,
prescribed fires, and mechanical treatments that use activity codes 2821
or 2823 and are 10 acres or greater in size. Less than 10 acres, the
fire's point of origin was to continue to be recorded on the DI-1202
database on SACS. (The polygon database is in addition to the DI-1202
database for fires of 10 acres and greater in size, except for Alaska
which was to be fires 100 acres or greater).

**Benefits:** The Fire Polygon Database is of benefit to all natural
resource programs in BLM. Historic fire perimeter locations are an
important element of baseline information that is useful in integrating
fire strategies with the larger land management picture and with BLM\'s
Phase I fire planning efforts, as well as fire rehabilitation and
monitoring efforts. Tactically and strategically, a fire perimeter
database has many benefits.

**Procedures**: There are two recommended approaches to initiating the
fire perimeter database at a field office. The two approaches are GPS
and on-screen digitizing in ArcView or Arc/Info using a 1:24,000 DRG (a
7.5 min. USGS Topographic in digital format) as a back image.

**Data Elements**:

Number range CHAPTER**FIRE_NUMBER -** Enter same Fire-Number that you
entered in the DI-1202.

**UNIT_ID -** Enter the two-letter State Office code followed by the
three-letter Field Office code for the office reporting the incident.

**YEAR-** Current year.

**FWS Data Standards** -- FWS has a process in place for establishing
data standards. The website is located at: <http://www.fws.gov/stand/>

# 3) 2001 Data Elements for GeoMAC

event_num -- Follows the format for the National Situation Report
Database with the format of (State-Unit ID-Fire Number).

event_name -- Given name of event

event_type -- This is the type of event:

a.  Wildland Fire

b.  Complex

c.  Area Command

c_date -- The date that the perimeter was collected

c_time -- The military time that the data was collected

c_method -- The methodology of how the perimeter was collected

a.  GPS-Air

b.  GPS-Vehicle

c.  GPS-ATV

d.  GPS-Walked

e.  GPS-Combo

f.  IR-NIRP --National Infrared Program

g.  IR-Other

h.  Satellite -- Units (e.g. For LandStat TM data this would be filled
    out as Satellite -- 30m

i.  Hand Digitized -- Scale of Map, DOQQ, etc. That perimeter is
    digitized from (e.g. Hand Digitized -- 24K)

poc_name -- The point of contact name

poc_email -- The point of contact email

poc_ophone -- The point of contact office phone number

poc_cphone -- The point of contact cell phone number

poc_ephone -- The point of contact event phone number

# Appendix C -- Authors

Brian Sorbel

National Park Service

2525 Gambell St., Rm 107

Anchorage, AK 99501

Email: <brian_sorbel@nps.gov>

Phone: (907) 257-2559

Susan Goodman

Bureau of Land Management

Denver Federal Center

Building 50 (ST-134)

Denver, CO 80225

Email: <susan_goodman@blm.gov>

Phone: (303) 236-4242

Sue McLellan

Division of Forestry

3125 Conner Blvd.

Tallahassee, FL 32399-1650

Email: <mclells@doacs.state.fs.us>

Phone: (850) 414-8554