Incident Command Type I Team
Suggestions for a GIS Data Structure on an Active Incident
written:  Summer 2003
(adapted from an email from Kerri Mich, NPS Intermountain GIS Program Office, Albuquerque)

-Active_incident
	-Fire_name
		-avprojects
		-basedata
			-fs
			-state
			-county
			-etc
		-gps_data  (dump site for raw gps stuff and working, editing gps files)
		-incident_data
			-line  (like dozer line, completed line, etc.  we name stuff with the dates, so dozer625, proposed630, etc.)
			-points (like helispots, dipsites, camps, etc.  same naming, raws701
			-perimeters  (this is IR data, and any GPS updates, could have subdirectories to reflect)
		-logos
		-plots (by date subdirectory)
		-photos
		-progression_perimeters (sometimes you have to edit the ir to fit the progression better, we keep those edited perimeters here)
		-whatever else, ie working, misc, whatever

we have a separate basedata directory on our server with statewide data for arizona and new mexico, the drgs, doqs, dems, etc so that is not in here, or would be in this basedata.  If we clip anything we put it in this basedata.