View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
ArcGIS Earth
ArcMap
ArcGIS Pro
View Footprint In:
ArcGIS Online Map Viewer
Service Description: This dataset is derived from the USGS Burned Area Products (Hawbaker et al. 2017). We used Burned Area (BA) version 2 products (USGS 2019). We evaluated the annualBAECV Burn Probability (BP) datasets –which are raster datasets – for evidence of burns. The annual datasets span an entire calendar year (e.g.,Jan 1 through Dec 31) and indicate the maximum BP within the year (0-100%). For each year between 1994 and 2020, we combined the annual datasets of interest within individual ARD Tiles into a single annual raster dataset (i.e., we mosaicked the tiles) for further processing. We performed all additional processing steps on the annual mosaicked datasets as this provided statewide consistency. We identified pixels as burned or unburned according to their probability value; initially, we retained all pixels with an annual BP between 85-100% based on Hawbaker et al. (2017). Values between 90-100% were then converted to presence/absence rasters and we used image processing methods to remove ‘speckling’ (e.g.,fill in small holes within a burned area and remove groups of pixels less than a specified size/amount). This process resulted in annual rasters and vectors indicating burn presence (with 90-100% probability) for groups of pixels greater than ~2.24 acres (e.g.,10 30m pixels, in any arrangement). We also assigned dates from the Burn Date (BD) dataset to these same pixels as a surrogate for seasonality. We evaluated these products against fire records for three pilot areas. For each area, we held a meeting with fire managers, either in person or via web conferencing methods. We invited managers to inspect the data with us to evaluate their thoughts on the products. Through this process, managers provided many explanations for why no burn was detected and where/why fire detection was performing very well, as well as some ideas and suggestions for moving forward (all of which we relayed to USGS). Many of these comments reflect known limitations previously documented (see Hawbaker et al. 2017, Vanderhoof et al. 2017). Based on these meetings, we have applied the processing “logic” across the entire state at 90-100%BP. Fire regime metrics such as number of times burned, year last burned, and time since previous fire (as measured from 2020) are included in the dataset upload, and were derived using these annual presence/absence rasters and vectors.
Map Name: Fire Occurrence in Florida
Legend
All Layers and Tables
Layers:
Description: This data represents fire occurrences (boundaries and areas, both Rx and wildland fires) between 1994-2019.
Copyright Text: Florida Fish and Wildlife Conservation Commission, Fish and Wildlife Research Institute, Center for Spatial Analysis
Spatial Reference:
102100
(3857)
Single Fused Map Cache: false
Initial Extent:
XMin: -1.0542683067218654E7
YMin: 3105363.335172542
XMax: -8200033.950481348
YMax: 3797798.799468053
Spatial Reference: 102100
(3857)
Full Extent:
XMin: -9833172.08
YMin: 2820045.5582000017
XMax: -8909544.9377
YMax: 3972617.688699998
Spatial Reference: 102100
(3857)
Units: esriMeters
Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP
Document Info:
Title:
Author:
Comments: This dataset is derived from the USGS Burned Area Products (Hawbaker et al. 2017). We used Burned Area (BA) version 2 products (USGS 2019). We evaluated the annualBAECV Burn Probability (BP) datasets –which are raster datasets – for evidence of burns. The annual datasets span an entire calendar year (e.g.,Jan 1 through Dec 31) and indicate the maximum BP within the year (0-100%). For each year between 1994 and 2019, we combined the annual datasets of interest within individual ARD Tiles into a single annual raster dataset (i.e., we mosaicked the tiles) for further processing. We performed all additional processing steps on the annual mosaicked datasets as this provided statewide consistency. We identified pixels as burned or unburned according to their probability value; initially, we retained all pixels with an annual BP between 85-100% based on Hawbaker et al. (2017). Values between 90-100% were then converted to presence/absence rasters and we used image processing methods to remove ‘speckling’ (e.g.,fill in small holes within a burned area and remove groups of pixels less than a specified size/amount). This process resulted in annual rasters and vectors indicating burn presence (with 90-100% probability) for groups of pixels greater than ~2.24 acres (e.g.,10 30m pixels, in any arrangement). We also assigned dates from the Burn Date (BD) dataset to these same pixels as a surrogate for seasonality. We evaluated these products against fire records for three pilot areas. For each area, we held a meeting with fire managers, either in person or via web conferencing methods. We invited managers to inspect the data with us to evaluate their thoughts on the products. Through this process, managers provided many explanations for why no burn was detected and where/why fire detection was performing very well, as well as some ideas and suggestions for moving forward (all of which we relayed to USGS). Many of these comments reflect known limitations previously documented (see Hawbaker et al. 2017, Vanderhoof et al. 2017). Based on these meetings, we have applied the processing “logic” across the entire state at 90-100%BP. Fire regime metrics such as number of times burned, year last burned, and time since previous fire (as measured from 2019) are included in the dataset upload, and were derived using these annual presence/absence rasters and vectors.
Subject: This data represents fire occurrences (boundaries and areas, both Rx and wildland fires) between 1994-2019.
Category:
Keywords: Florida,FWC,FWRI,Land,Statewide,Terrestrial,Upland,Fire Occurrence
AntialiasingMode: None
TextAntialiasingMode: Force
Supports Dynamic Layers: false
Resampling: false
MaxRecordCount: 1000
MaxImageHeight: 4096
MaxImageWidth: 4096
Supported Query Formats: JSON, geoJSON
Supports Query Data Elements:
Min Scale: 0
Max Scale: 0
Supports Datum Transformation: true
Child Resources:
Info
Supported Operations:
Export Map
Identify
QueryDomains
QueryLegends
Find
Return Updates