# Presentation: 948590

## Data Management:

**GPS for Fire Management & ICS Course ****and Incident Standard**

**Notes:**
Its important to have a plan for saving your GPS and GIS data.  In other words, how will you manage your data on the computer?  
We are going to review the directory structure and naming convention used for this class.  We will also talk briefly about the GIS Standard Operating Procedures on Incidents

## Objectives 

** ****Class Data Management ****Incident Standards**

## Data Management 

**Directory Structure**
**File Names**

**Notes:**
Data Management comes in two parts...
1.)  The directory structure or files on the computer
2.) The way we name our files and which folders we put them in.

## GPS for Fire Management & ICS Directory Structure

**raster   **(images)
**vector   **(points, lines, polygons)
**YYYYMMDD_Restoration  **
**YYYYMMDD_RxWUI  **
**	****YYYYMMDD_Oops   **

**2008_Incidents**** **
**	****	****	****	****	****	****	****	**
** **

**base_data**
**incident_data **(gps .txt, waypoints & points, lines, polygons)
**	**
** **

_***GPS for Fire Management & ICS***_** Directory Structure**

**Notes:**
Here is the basic structure developed for this course...

Main folder is called 2008_Incidents
Inside that folder are two sub-folders or directories.  One is base_data
Base_data contains all permanent or static data.  It usually contains the data from the local units GIS data library.  Those data are separated by data types, raster and vector.  The raster folder contains grid and image data.  Examples would include digital USGS topos, also called DRGs, and aerial photos.  The vector folder contains point line and polygon data such as roads, trails, ownership boundaries, structures, etc.

Incident Data is where you would store all data that was collected or created during the incident.  This includes all GPS data and GIS data created from the GPS data.  There are subfolders or directories by date and incident name within this folder.

## GPS for Fire Management & ICS Naming Convention

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

**20080318_rest_allwpts.shp**
**20080318_rest_dzline.shp**
**20080318_rest_perim.shp**
**	**
** **

_***GPS for Fire Management & ICS***_** ****Naming Convention**

**Notes:**
Here is how files should be named within the incident folders.  They should be named by date, incident name or abbreviation of incident name, feature identifier of some sort.  You may also add military time if time is important for some reason.  An example would be fire perimeters collected 2 or 3 times a day.  In this case you should add military time just after date.

## Example

**Example**

- Incident Name

- Feature Identifier

- Date: YYYYMMDD

## Incident Directory Structure

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

**base_data**
**incident_data **(gps .txt, waypoints & points, lines, polygons)

**	****raster   **(images)
**vector   **(points, lines, polygons)
**YYYYMMDD  **
**	****YYYYMMDD   **

**2008_Incidents**** **

_**Incident**_** Directory Structure**

**Notes:**
The standard incident directory is very close to what we will be using but they just build a base_data and incident_data under each incident.  We have our individual incidents under the incident data because all three will use the same base data.

## IncidentFileNameStandard

***...******Translation:  On ******5/16/2005****** a file was started at ******2230****** hrs for the ******RXWUII****** fire to collect a fire ******per******imeter by the ******field observer******.  It was saved as a ******polygon****** in ******UTM, Zone15, NAD83****** in ******shapefile****** format... ***

_**Incident**_**File****Name****Standard**

**yyyymmdd_**
**Time_**
**IncidentName_**
**FeatureIdentifier_**
**Source_**
**GISType_**
**ProjectionDatum**

**Notes:**
Here is where what we are doing and what is standard differs greatly.  They name files with so much information that its like having built in metadata. ...Translation:  On 5/16/2005 a file was started at 2230 hrs for the RXWUII fire to collect a fire perimeter by the field observer.  It was saved as a polygon in UTM, Zone15, NAD83 in shapefile format... This is VERY helpful when working on an incident because everything you need to know about the file is obvious without even having to open it up in ArcMap.  BUT...  it very time consuming and tedious naming all the files like this.  You don’t get the hang of it until you have worked 3-4 15 hour days!!!!  We have decided not to ask you to follow the SOP but as an FYI, you may see this on your next large incident.

## Example

**Example**

- Incident Name

- Date: YYYYMMDD

- Time: 2400 clock

- Feature Identifier

- GIS Type

- Projection & Datum

- Source (Collector)

**Notes:**
Here is an example of the directory and files within.

## Source of Standards - GSTOP

**G****IS **
**ST****andard **
**O****perating **
**P****rocedures **
**	****on Incidents ****  **** **

**http://**
**gis.nwcg.gov/**
**gstop_sop.htm**

## Questions?

**Questions?**