1. Data Management

2. Objectives – what does it mean? Standard Operating Procedures on Incidents Take Home Message?

3. Data Management – 2 parts: Directory Structure File Names (naming convention)

4. GSTOP – data management standards GIS STandard Operating Procedures on Incidents http://gis.nwcg.gov/gstop_sop.htm

5. 2010_Restoration base_data incident_data (gps.txt, waypoints & points, lines, polygons) raster (images) vector (points, lines, polygons) YYYYMMDD 2010_Incidents Incident Directory Structure

6. 20050516_2230_RXWUII_per_fobs_pl_u15n83.shp …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… Incident File Name Standard yyyymmdd_Time_IncidentName_FeatureIdentifier_Source_GISType_ProjectionDatum

7. GSTOP Example Incident Name Date: YYYYMMDD Time: 2400 clock Feature Identifier GIS Type Projection & Datum Source (Collector)

8. Data Management – Take Home Message Directory Structure? No spaces in folder namesNo spaces in folder names Keep it simple – not too many subfoldersKeep it simple – not too many subfolders Keep it informative – plain english but not verboseKeep it informative – plain english but not verbose Document it! (readme text file)Document it! (readme text file) File Names (Naming Convention)? No spaces in file namesNo spaces in file names Use date and time if appropriate (YYYYMMDD_HH:MM)Use date and time if appropriate (YYYYMMDD_HH:MM) Document it! (readme text file or metadata)Document it! (readme text file or metadata) Clean up after yourself! Delete old or intermediate files!Clean up after yourself! Delete old or intermediate files!

9. Example Incident Name Feature Identifier Date: YYYYMMDD

10. Questions?Questions?