Unit 8 – Deliverables

Unit ObjectivesList the IR products delivered to the incident by the IRIN

Discuss the mode of delivery in different scenarios

Identify key communication issues

OutlineProducts

Directory and File Structure/Naming

Maps/Logs/KMZs

Communication/coordination with SITL and GISS

Product delivery

Briefing/Documentation/Feedback

DeliverablesThe 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 ProductsIR GIS layers - shapefiles

Map(s) – hardcopy and/or PDFs

IR log

KMZ file for viewing in Google Earth

IR GIS ProductsHeat Perimeter (polygon)

Isolated Heat Sources (points)

Intense Heat (polygon)

Scattered Heat (polygon)

IR GIS ProductsShapefiles

Works in all versions of ArcGIS

Managing directories and files takes time – do prior to receiving imageryStandardizing directory/file names and structure saves time, reduces stress, and simplifies communication and handoffs to other IRINs/SITLs/GISSs

IR GIS ProductsSome 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 namesExamples:

20060925_2025_Pigeon_IsolatedHeatSources.shp

20060925_2025_Pigeon_HeatPerimeter.shp

20060925_2025_Pigeon_ScatteredHeat.shp

20060925_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: 20060926)

vector

Delivery Due Date (Example: 20060926)

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 BarTitleAuthorNorth ArrowDate/Time*

STAND(GL)

Grid/GraticuleLegend

*Of the imagery, not the map

The Map – Remote InterpretationResponsibility 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 ArcGISAgree 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 coverageComplete 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 ToolTool developed by RSAC to generate GE KMZ from standard NIROPS datasets

Heat PerimeterIntense HeatScattered HeatIsolated 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 http://nirops.fs.fed.us/

Also included in course notebook

PDFsShould 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 SITLExchange contact info, best times/way to get a hold of them (text message, email, phone)

What/how to deliver productsAdditional 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 GISSGood 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 DateDelivery 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 day2006_pigeon_ir base_data products 20060925 20060925_0122_Pigeon_IsolatedHeatSources.shp 20060926 20060925_2025_Pigeon_IsolatedHeatSources.shp

ir_data 20060925 20060926

projects 20060925

20060926

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 versionsGeodatabases 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 earlierversion mxd

Data DeliveryNIFC ftp site

ftp://ftp.nifc.gov

Password needed to upload data One username/password for all GACCsNot the same username/password as NIROPS

folder

Can e-mail 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 separateNon-GIS user can access these quickly

PDFs can take time to download

BriefingRemote – 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 faceBriefing 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 DeliverableFeedback 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/IRCRIssues that need daytime follow-up

Priorities

Transmit your feedback and that of IMT

Unit Objectives - ReviewList the IR products delivered to the incident by the IRIN

Discuss the mode of delivery in different scenarios

Identify key communication issues

Questions?