{"id":45338,"date":"2022-03-22T19:18:14","date_gmt":"2022-03-22T19:18:14","guid":{"rendered":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/?p=45338"},"modified":"2022-03-23T14:34:59","modified_gmt":"2022-03-23T14:34:59","slug":"using-mcidas-v-to-display-goes-16-fdca-fields","status":"publish","type":"post","link":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/archives\/45338","title":{"rendered":"Using McIDAS-V to display GOES-16 FDCA fields"},"content":{"rendered":"\n

The image below shows GOES-16 Fire Power, a Fire Detection\/Characterization Algorithm (FDCA) output field (along with Fire Temperature and Fire Area), on a day when strong southerly winds helped support multiple fires over Texas (as shown in this animation<\/a>, from this blog post<\/a>). If you do not have access to AWIPS, as below (or in the linked-to animation), are there other ways to access and display FDCA output? This blog post shows how to do that with McIDAS-V<\/a>.<\/p>\n\n\n\n

\"\"<\/a>
GOES-16 Fire Power, 2101 UTC on 20 March 2022 (click to enlarge)<\/figcaption><\/figure>\n\n\n\n

Where can you get the FDCA data to display? The NOAA CLASS<\/a> data respository is one place. The toggle below outlines the products to choose in the drop-down menu (“GOES-R Series ABI Products (GRABIPRD) partially restricted L1b and L2+ Data Products”) near the top of the CLASS home page (then click on the >>GO), and then shows how to select the data wanted. In the example below, I’ve chosen the ABI L2+ GOES-16 CONUS files of Fire\/Hot Spot Characterization on 20 March 2022 between 21:00 and 21:04. After making those selections, click on ‘Search’ and then order. When the files are queued up for retrieval, you’ll receive an email with instructions.<\/p>\n\n\n\n

\"\"
NOAA CLASS website, and GOES-R L2 Products data selection (Click to enlarge)<\/figcaption><\/figure>\n\n\n\n

You can also access GOES-R data through this website below hosted at the University of Utah<\/a>. (Kudos to Brian Blaylock, its developer!) Note in the animation below how you choose the satellite, the product and the time, and then receive a list of downloadable files.<\/p>\n\n\n\n

\"\"<\/a>
Amazon Web Services portal showing data selection and files retrieved (Click to enlarge)<\/figcaption><\/figure>\n\n\n\n
\n\n\n\n

You can start up McIDAS-V to view the data once you have downloaded to your machine the data file:<\/p>\n\n\n\n

OR_ABI-L2-FDCC-M6_G16_s20220792101168_e20220792103541_c20220792104155.nc<\/code><\/pre>\n\n\n\n
FDCC<\/span> in the filename signifies F<\/span>ire D<\/span>etection C<\/span>haracterization in the C<\/span>ONUS domain, created with Mode 6 scanning (M6) and GOES-16 data (G16).  The data s<\/span>tarts at 21:01:16.8 on 20 March (Julian Day 79) in 2022, i.e., 20220792101168 and e<\/span>nds at 21:03:54.1 on the same day.  It was c<\/span>reated at 21:04:15.5.  Once you start McIDAS-V, you must input the data, via the Data Sources tab within the Data Explorer.  The satellite data we’re using are gridded data, and they’re local.  Select the file needed for display and click ‘Add Source’.  When you do that, you’ll see a different window (‘Field Selector’) brought to the front.<\/p>\n\n\n\n
\"\"<\/a>
McIDAS-V Data Explorer (Click to enlarge)<\/figcaption><\/figure>\n\n\n\n
\"\"<\/a>
Steps under ‘Field Selector’ in the Data Explorer to find the data to display (Click to enlarge)<\/figcaption><\/figure>\n\n\n\n
Note in this example that 5 different fields are present in the file:  Fire + Hot Spot Characterization  Fire Area, Fire Temperatures, Fire Mask, Fire Radiative Power and Data Quality Flags.  In this example, I’ve selected ‘Data Quality Flags’ — to be presented as ‘Value Plots’;  those are shown below in a region zoomed in over Texas and annotated.<\/p>\n\n\n\n
\"\"<\/a>
FDCA Data Quality Flags, 2101 UTC, 20 March 2022 (Click to enlarge)<\/figcaption><\/figure>\n\n\n\n
Rather than Data Quality Flags, one can show ‘Fire Mask’ — these data values are available in AWIPS files, but aren’t generally shown.  So, I recreated the ‘Value Plots’ but selected ‘Fire Mask’ rather than ‘data quality Flags’;  Next, I created a ‘Color-Shaded Plan View’ (the Data Explorer for that is shown here<\/a>, created with ‘Match Display Region’ chosen).  The animation below steps through the plotted values, the color-shaded plan view with default enhancement, and the color-shaded plan view with a McIDAS Enhancement Table appropriate to the Fire Mask (clouds, for example, are grey, and fires stand out against the background).  (This pdf<\/a> describes what the file mask values mean).<\/p>\n\n\n\n
\"\"<\/a>
Plotted FDCA Fire Mask values, and color-enhanced gridded values, 2101 UTC on 20 March 2022 (click to enlarge)<\/figcaption><\/figure>\n\n\n\n
This toggle<\/a> compares Fire Mask, and Fire Power.  A zoom in on Fire Power to north Texas, below, shows the same data as the AWIPS screen grab at the top of this blog post.  They are nearly identical.<\/p>\n\n\n\n
\"\"<\/a>
GOES-16 FDCA Fire Power, 2101 UTC on 20 March 2022 (click to enlarge)<\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
Use McIDAS-V to display Level 2 products if it is difficult to find them online.<\/p>\n","protected":false},"excerpt":{"rendered":"
The image below shows GOES-16 Fire Power, a Fire Detection\/Characterization Algorithm (FDCA) output field (along with Fire Temperature and Fire Area), on a day when strong southerly winds helped support multiple fires over Texas (as shown in this animation, from this blog post). If you do not have access to AWIPS, as below (or in […]<\/p>\n","protected":false},"author":19,"featured_media":45356,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[6,51],"tags":[],"class_list":["post-45338","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fire-detection","category-mcidas-v"],"acf":[],"_links":{"self":[{"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/posts\/45338","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/comments?post=45338"}],"version-history":[{"count":13,"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/posts\/45338\/revisions"}],"predecessor-version":[{"id":45397,"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/posts\/45338\/revisions\/45397"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/media\/45356"}],"wp:attachment":[{"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/media?parent=45338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/categories?post=45338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cimss.ssec.wisc.edu\/satellite-blog\/wp-json\/wp\/v2\/tags?post=45338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}