Unit 8 – Deliverables

Unit Objectives List the IR products delivered to the incident by the IRIN Discuss the mode of delivery in different scenarios Identify key communication issues

Outline Products Directory and File Structure/Naming Maps/Logs/KMZs Communication/coordination with SITL and GISS Product delivery Briefing/Documentation/Feedback

Deliverables The primary duty of the IRIN is to “Interpret imagery and post findings on.. maps”. A base map with interpretation overlay is the primary product. This has evolved from a hardcopy map with mylar overlay to a digital or paper map produced in GIS.

IR Products IR GIS layers - shapefiles Map(s) – hardcopy and/or PDFs IR log KMZ file for viewing in Google Earth

IR GIS Products Heat Perimeter (polygon) Isolated Heat Sources (points) Intense Heat (polygon) Scattered Heat (polygon)

IR GIS Products Shapefiles Works in all versions of ArcGIS Managing directories and files takes time – do prior to receiving imagery Standardizing directory/file names and structure saves time, reduces stress, and simplifies communication and handoffs to other IRINs/SITLs/GISSs

IR GIS Products Some layers will not always be applicable (e.g. no intense heat during mop up)…..but every applicable layer should be produced regardless of what an individual SITL might request. Need consistency for documentation and changes in SITLs.

File names Examples: _2025_Pigeon_IsolatedHeatSources.shp _2025_Pigeon_HeatPerimeter.shp _2025_Pigeon_ScatteredHeat.shp _2025_Pigeon_IntenseHeat.shp Collection date Collection time* Incident name Data type *Time stamp on imagery is always Mountain Time regardless of where data is collected. Time in shapefile name and on map should be local time at incident.

Recommended Directory Structure (Single Incident) Note: Date is always given as YYYY/MM/DD. Directory date is always date of the morning briefing. Year_Incident Name_IR (Example: 2006_pigeon_ir) base_data products ir_data projects raster temp Delivery Due Date (Example: ) vector Delivery Due Date (Example: ) from_fire Contains what you “produce” – interpreted shapefiles, maps, logs Contains what you get from the flight -.tif files, raw data shapefiles, etc.

The Map – Remember… Scale/Scale Bar Title Author North Arrow Date/Time* STAND(GL) Grid/Graticule Legend *Of the imagery, not the map

The Map – Remote Interpretation Responsibility of hardcopy production switches to Incident/GISS (communication about delivery is key) SITL may only want GIS layers and no map but…...always produce a.pdf of the map for documentation and a “quick look” that doesn’t require ArcGIS Agree on size of layout (file size may be an issue) Our standard is 11x17

IR Log This should be filled out every night after interpreting and included with the products delivered to the SITL. Calculated acres are always entered here and put on map if SITL requests it. The IR log acts as a briefing – issues with imagery, fire activity, trigger points, etc.

IR Log - examples

Partial coverage Complete coverage of fire is assumed If not, need to explicitly show that on the map and state it in the daily log Cloud cover, not flown, problems w/ imagery, etc.

Partial Coverage – another example

NIROPS KMZ Tool Tool developed by RSAC to generate GE KMZ from standard NIROPS datasets Heat Perimeter Intense Heat Scattered Heat Isolated Heat No need for admin access Tool is available from NIROPS website Now can include no data areas

IR Product Naming Conventions Document is posted in IRIN area on NIROPS website Also included in course notebook

PDFs Should be able to keep under 10MB 300 dpi and normal quality is usually sufficient Reduced pdfs can be created if you have full Adobe license Geocoded pdfs are the default in ArcGIS export

Communication with SITL Exchange contact info, best times/way to get a hold of them (text message, , phone) What/how to deliver products Additional products as time permits Zoomed maps, smaller handouts, KMZs Stress the time imagery was collected Be accessible – PM briefing if possible, provide cell #

Communication with SITL Remember – The IRIN works for the SITL! Do not distribute digital or hardcopy products without the approval of the SITL Once data is posted to NIFC ftp site it becomes responsibility of the incident

Coordination with GISS Good source of base imagery, intel and updates Exchange contact info Agree on projections, data exchange protocol (posting of new perimeter) Set up schedule or communication protocol

Image Time Stamp is Mountain time Be sure you know the local incident time!

Delivery Date vs. Collection Date Delivery date refers to date of morning briefing – used for naming folders, logs, maps Collection date refers to date of collection – used for naming shapefiles (along with collection time) Can have same collection date for different deliver dates – Imagery collected at 0120hrs on 9/25 used for 9/25 morning briefing Imagery collected at 2025hrs on 9/25 used for 9/26 morning briefing

Example – 2 flights on same day Data shapefiles always have date and time of acquisition. Data folders have date of morning briefing. Why? Because users of products don’t always know when the flight occurred. They’re just looking for “this morning’s IR”.

ArcGIS versions Geodatabases are not always backward compatible We deliver shapefiles Supposedly 10.2 mxd files are compatible with 10.1 mxd files are not always backward compatible but you can “save a copy” as an earlier version mxd

Data Delivery NIFC ftp site ftp://ftp.nifc.gov Password needed to upload data One username/password for all GACCs Not the same username/password as NIROPS folder Can products if problems with NIFC ftp site access

NIFC ftp file structure (for products) IR folder is outside GIS folder

NIFC ftp file structure (for products) Folders labeled with date of morning briefing If flight is UTF’d, place readme file in folder Zip all shapefiles together Keep log and pdf map separate Non-GIS user can access these quickly PDFs can take time to download

Briefing Remote – by phone, contact info Establish a schedule Many GISS now look for this data at ~0430 hrs Your daily log acts as a briefing document when you are not there! At camp, face to face Briefing for SITL at ~0530 hrs

Documentation Products posted to NIFC ftp site and archived by incident Imagery archived by IR Techs Keep copies of your work

Feedback – the Forgotten Deliverable Feedback to Air crews (pilots and technicians) Box size, coverage, overlap Imagery issues – quality, orthocorrection Uploading data Changes in fire since scanner order Positive feedback appreciated! Feedback to IRCN/IRCR Issues that need daytime follow-up Priorities Transmit your feedback and that of IMT

Unit Objectives - Review List the IR products delivered to the incident by the IRIN Discuss the mode of delivery in different scenarios Identify key communication issues

Questions?