Forums

Back

RE: GOES-16 Hot Spots Help

RSS (Opens New Window)(Opens New Window)
SH
Stephen Harrison, modified 6 Years ago.

GOES-16 Hot Spots Help

Youngling Posts: 1 Join Date: 9/5/13 Recent Posts

Hello,

Here at WFO SGX, we are trying to create a way to monitor the GOES-16 fire temperature/power products for early fire detection. Does anyone know of a tool or script for AWIPS that will automatically detect when any pixel within our CWA gets a noteworthy fire temperature (say, 600 K or greater?) and then send an alarm (preferably Red Banner, but text workstation alarm would be good too) to the forecaster? We have radar alarms that can do this (such as TVS or "new cell" red banner alarms) so I figure it must be possible with GOES-16 too! This would be extremely helpful in detecting wildfires so that we can notify affected fire agencies as soon as possible.

Stephen Harrison

NWS San Diego, CA

Scott Lindstrom, modified 6 Years ago.

RE: GOES-16 Hot Spots Help

Youngling Posts: 7 Join Date: 6/29/15 Recent Posts
Stephen Harrison:

Hello,

Here at WFO SGX, we are trying to create a way to monitor the GOES-16 fire temperature/power products for early fire detection. Does anyone know of a tool or script for AWIPS that will automatically detect when any pixel within our CWA gets a noteworthy fire temperature (say, 600 K or greater?) and then send an alarm (preferably Red Banner, but text workstation alarm would be good too) to the forecaster? We have radar alarms that can do this (such as TVS or "new cell" red banner alarms) so I figure it must be possible with GOES-16 too! This would be extremely helpful in detecting wildfires so that we can notify affected fire agencies as soon as possible.

Stephen Harrison

NWS San Diego, CA


Hi Stephen.  Your question reminds me of the approach taken at OUN with GOES-14 SRSO-R data:   Text msgs were sent based on Hot Spot Detection, and the messaging was done from AWIPS (This is described in a paper:  http://nwafiles.nwas.org/jom/articles/2016/2016-JOM14/2016-JOM14.pdf , or here's the link)  But I think that required forecaster intervention, so not automatic as you are asking.  (And it was using 3.9, not the GOES-16 Baseline Fire Temperature Product you're talking about!)

You should be able to do this, however, using the Data Access Framework (DAF) -- it requires PyThon scripting.  Shoot an email to Jeremy Martin, the SOO in Goodland.  He can assist if you can't figure it out.  (i'll send a separate email to the both of you that has this entire message)

 

Scott
 

DB
Dan Bikos, modified 6 Years ago.

RE: GOES-16 Hot Spots Help (Answer)

Youngling Posts: 6 Join Date: 6/2/15 Recent Posts

Reply from Jeremy Martin:

Stephen,

 

I have been testing the script for the past week and it seems to work ok. Sorry for the no frills instructions, but the overall process is pretty simple.  To install the script:

 

1) Take the attached tar file and as user awips place it in /localapps/dev

2) cd /localapps/dev

3) As user awips  enter this command tar -xvf Fire_Wx.tar

4) cd /localapps/dev/Fire_Wx/scripts

5) There should be two files here : check4Fire.py and scan4fire.csh Using your favorite editor open the check4Fire.py file.

6)  There are three variables at the top of the file that need to be changed to suit your needs :

             SITEID = 'GLD'   - change this to your CWA

             THRESH = 600.0    - The default temperature from the Fire Temp algorithm to alert for a fire.

             time_THRESH = 45   - This is the number of minutes that have to go by without a detection before a banner is created.  Prevents multiple alarms for same fire.

 

7) Set up a cron that runs every 5 minutes that runs  scan4fire.csh.   If a new fire is detected you will get a red banner that says 'A potential fire has been detected by GOES-16'

 

This is a pretty basic script that will need to be updated once the satellite moves or the algorithm is adjusted.  But as a starting point it should do what you want.

-Jeremy

Attachments: