This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire.Consumption Best Practices:

As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC). Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute.Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations.Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident Complex

Area Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed.Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed.Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires.Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives.Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities.IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers.

Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands.

Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.

Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created.

GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event.Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters)RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters.This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structuresFor more information about the wildfire response efforts, visit the CAL FIRE incident page.

The FinalFirePerimeter polygon layer represents final mapped wildland fire perimeters. This feature class is a subset of the FirePerimeters feature class. Incidents of 10 acres or greater in size are expected. Incidents smaller than 10 acres in size may also be included. Data are maintained at the Forest/District level, or their equivalent, to track the area affected by wildland fire. Records in FirePerimeter include perimeters for wildland fires that have corresponding records in FIRESTAT, which is the authoritative data source for all wildland fire reports. FIRESTAT, the Fire Statistics System computer application, required by the USFS for all wildland fire occurrences on National Forest System Lands or National Forest-protected lands, is used to enter and maintain information from the Individual Fire Report (FS-5100-29).National USFS fire occurrence final fire perimeters where wildland fires have historically occurred on National Forest System Lands and/or where protection is the responsibility of the US Forest Service. Knowing where wildland fire events have happened in the past is critical to land management efforts in the future.This data is utilized by fire & aviation staffs, land managers, land planners, and resource specialists on and around National Forest System Lands.*This data has been updated to match 2021 National GIS Data Dictionary Standards.Metadata and Downloads

This map contains live feed sources for US current wildfire locations and perimeters, VIIRS and MODIS hot spots, wildfire conditions / red flag warnings, and wildfire potential. Each of these layers provides insight into where a fire is located, its intensity and the surrounding areas susceptibility to wildfire.Find out more about the Esri Disaster Response Program: www.esri.com/disasterAbout the Data: Click on the links in the LAYERS section for details about each layerWildfire: This displays large active fire incidents and situation reports that have been entered into the National Interagency Fire Center (NIFC) database by local emergency response teams. The final official perimeter should be obtained from the host unit, which can be determined by looking at the Unit Id for any specific fire. The host unit is responsible for producing official and final perimeters for all incidents in their jurisdiction.Hot Spot: The MODIS and VIIRS thermal layers are created from the MODIS satellite detection system and represents hot spots that could be potential fire locations in the last 24 hour period at a horizontal resolution of 1 km and temporal resolution of 1 to 2 days.Wind Data (NOAA METAR): Typical METAR contains data for the temperature, dew point, wind speed and direction, precipitation, cloud cover and heights, visibility, and barometric pressure. A METAR may also contain information on precipitation amounts, lightning, and other information.Red Flag Warnings: Filtered from the Weather Watches and Warnings layer.

This ArcGIS Online hosted feature service displays perimeters from the National Incident Feature Service (NIFS) that meet ALL of the following criteria:

This is a copy of another layer - see original source: https://www.arcgis.com/home/item.html?id=e02b85c0ea784ce7bd8add7ae3d293d0OverviewThe national fire history perimeter data layer of conglomerated Agency Authoratative perimeters was developed in support of the WFDSS application and wildfire decision support for the 2021 fire season. The layer encompasses the final fire perimeter datasets of the USDA Forest Service, US Department of Interior Bureau of Land Management, Bureau of Indian Affairs, Fish and Wildlife Service, and National Park Service, the Alaska Interagency Fire Center, CalFire, and WFIGS History. Perimeters are included thru the 2021 fire season. Requirements for fire perimeter inclusion, such as minimum acreage requirements, are set by the contributing agencies. WFIGS, NPS and CALFIRE data now include Prescribed Burns. Data InputSeveral data sources were used in the development of this layer:Alaska fire history USDA FS Regional Fire History Data BLM Fire Planning and Fuels National Park Service - Includes Prescribed Burns Fish and Wildlife ServiceBureau of Indian AffairsCalFire FRAS - Includes Prescribed BurnsWFIGS - BLM & BIA and other S&LData LimitationsFire perimeter data are often collected at the local level, and fire management agencies have differing guidelines for submitting fire perimeter data. Often data are collected by agencies only once annually. If you do not see your fire perimeters in this layer, they were not present in the sources used to create the layer at the time the data were submitted. A companion service for perimeters entered into the WFDSS application is also available, if a perimeter is found in the WFDSS service that is missing in this Agency Authoratative service or a perimeter is missing in both services, please contact the appropriate agency Fire GIS Contact listed in the table below.AttributesThis dataset implements the NWCG Wildland Fire Perimeters (polygon) data standard.https://www.nwcg.gov/sites/default/files/stds/WildlandFirePerimeters_definition.pdfIRWINID - Primary key for linking to the IRWIN Incident dataset. The origin of this GUID is the wildland fire locations point data layer. (This unique identifier may NOT replace the GeometryID core attribute)INCIDENT - The name assigned to an incident; assigned by responsible land management unit. (IRWIN required). Officially recorded name.FIRE_YEAR (Alias) - Calendar year in which the fire started. Example: 2013. Value is of type integer (FIRE_YEAR_INT).AGENCY - Agency assigned for this fire - should be based on jurisdiction at origin.SOURCE - System/agency source of record from which the perimeter came.DATE_CUR - The last edit, update, or other valid date of this GIS Record. Example: mm/dd/yyyy.MAP_METHOD - Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality.GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; Digitized-Topo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; OtherGIS_ACRES - GIS calculated acres within the fire perimeter. Not adjusted for unburned areas within the fire perimeter. Total should include 1 decimal place. (ArcGIS: Precision=10; Scale=1). Example: 23.9UNQE_FIRE_ - Unique fire identifier is the Year-Unit Identifier-Local Incident Identifier (yyyy-SSXXX-xxxxxx). SS = State Code or International Code, XXX or XXXX = A code assigned to an organizational unit, xxxxx = Alphanumeric with hyphens or periods. The unit identifier portion corresponds to the POINT OF ORIGIN RESPONSIBLE AGENCY UNIT IDENTIFIER (POOResonsibleUnit) from the responsible unit’s corresponding fire report. Example: 2013-CORMP-000001LOCAL_NUM - Local incident identifier (dispatch number). A number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year. Field is string to allow for leading zeros when the local incident identifier is less than 6 characters. (IRWIN required). Example: 123456.UNIT_ID - NWCG Unit Identifier of landowner/jurisdictional agency unit at the point of origin of a fire. (NFIRS ID should be used only when no NWCG Unit Identifier exists). Example: CORMPCOMMENTS - Additional information describing the feature. Free Text.FEATURE_CA - Type of wildland fire polygon: Wildfire (represents final fire perimeter or last daily fire perimeter available) or Prescribed Fire or UnknownGEO_ID - Primary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature. Globally Unique Identifier (GUID).Cross-Walk from sources (GeoID) and other processing notesAK: GEOID = OBJECT ID of provided file geodatabase (4580 Records thru 2021), other federal sources for AK data removed. CA: GEOID = OBJECT ID of downloaded file geodatabase (12776 Records, federal fires removed, includes RX)FWS: GEOID = OBJECTID of service download combined history 2005-2021 (2052 Records). Handful of WFIGS (11) fires added that were not in FWS record.BIA: GEOID = "FireID" 2017/2018 data (416 records) provided or WFDSS PID (415 records). An additional 917 fires from WFIGS were added, GEOID=GLOBALID in source.NPS: GEOID = EVENT ID (IRWINID or FRM_ID from FOD), 29,943 records includes RX.BLM: GEOID = GUID from BLM FPER and GLOBALID from WFIGS. Date Current = best available modify_date, create_date, fire_cntrl_dt or fire_dscvr_dt to reduce the number of 9999 entries in FireYear. Source FPER (25,389 features), WFIGS (5357 features)USFS: GEOID=GLOBALID in source, 46,574 features. Also fixed Date Current to best available date from perimeterdatetime, revdate, discoverydatetime, dbsourcedate to reduce number of 1899 entries in FireYear.Relevant Websites and ReferencesAlaska Fire Service: https://afs.ak.blm.gov/CALFIRE: https://frap.fire.ca.gov/mapping/gis-dataBIA - data prior to 2017 from WFDSS, 2017-2018 Agency Provided, 2019 and after WFIGSBLM: https://gis.blm.gov/arcgis/rest/services/fire/BLM_Natl_FirePerimeter/MapServerNPS: New data set provided from NPS Fire & Aviation GIS. cross checked against WFIGS for any missing perimetersFWS -https://services.arcgis.com/QVENGdaPbd4LUkLV/arcgis/rest/services/USFWS_Wildfire_History_gdb/FeatureServerUSFS - https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_FireOccurrenceAndPerimeter_01/MapServerAgency Fire GIS ContactsRD&A Data ManagerVACANTSusan McClendonWFM RD&A GIS Specialist208-258-4244send emailJill KuenziUSFS-NIFC208.387.5283send email Joseph KafkaBIA-NIFC208.387.5572send emailCameron TongierUSFWS-NIFC208.387.5712send emailSkip EdelNPS-NIFC303.969.2947send emailJulie OsterkampBLM-NIFC208.258.0083send email Jennifer L. Jenkins Alaska Fire Service 907.356.5587 send emailLayers

The California Department of Forestry and Fire Protection's Fire and Resource Assessment Program (FRAP) annually maintains and distributes an historical wildland fire perimeter dataset from across public and private lands in California. The GIS data is developed with the cooperation of the United States Forest Service Region 5, the Bureau of Land Management, California State Parks, National Park Service and the United States Fish and Wildlife Service and is released in the spring with added data from the previous calendar year. Although the dataset represents the most complete digital record of fire perimeters in California, it is still incomplete, and users should be cautious when drawing conclusions based on the data. This data should be used carefully for statistical analysis and reporting due to missing perimeters (see Use Limitation in metadata). Some fires are missing because historical records were lost or damaged, were too small for the minimum cutoffs, had inadequate documentation or have not yet been incorporated into the database. Other errors with the fire perimeter database include duplicate fires and over-generalization. Additionally, over-generalization, particularly with large old fires, may show unburned "islands" within the final perimeter as burned. Users of the fire perimeter database must exercise caution in application of the data. Careful use of the fire perimeter database will prevent users from drawing inaccurate or erroneous conclusions from the data. This data is updated annually in the spring with fire perimeters from the previous fire season. This dataset may differ in California compared to that available from the National Interagency Fire Center (NIFC) due to different requirements between the two datasets. The data covers fires back to 1878. As of May 2024, it represents fire23_1. Please help improve this dataset by filling out this survey with feedback:Historic Fire Perimeter Dataset Feedback (arcgis.com)Current criteria for data collection are as follows:CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.All cooperating agencies submit perimeters ≥10 acres.Version update:Firep23_1 was released in May 2024. Two hundred eighty four fires from the 2023 fire season were added to the database (21 from BLM, 102 from CAL FIRE, 72 from Contract Counties, 19 from LRA, 9 from NPS, 57 from USFS and 4 from USFW). The 2020 Cottonwood fire, 2021 Lone Rock and Union fires, as well as the 2022 Lost Lake fire were added. USFW submitted a higher accuracy perimeter to replace the 2022 River perimeter. Additionally, 48 perimeters were digitized from an historical map included in a publication from Weeks, d. et al. The Utilization of El Dorado County Land. May 1934, Bulletin 572. University of California, Berkeley. Two thousand eighteen perimeters had attributes updated, the bulk of which had IRWIN IDs added. A duplicate 2020 Erbes perimeter was removed. The following fires were identified as meeting our collection criteria, but are not included in this version and will hopefully be added in the next update: Big Hill #2 (2023-CAHIA-001020). YEAR_ field changed to a short integer type. San Diego CAL FIRE UNIT_ID changed to SDU (the former code MVU is maintained in the UNIT_ID domains). COMPLEX_INCNUM renamed to COMPLEX_ID and is in process of transitioning from local incident number to the complex IRWIN ID. Perimeters managed in a complex in 2023 are added with the complex IRWIN ID. Those previously added will transition to complex IRWIN IDs in a future update.Includes separate layers filtered by criteria as follows:California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale. Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2019-2023), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-present. Symbolized by decade, and display starting at country level scale.Detailed metadata is included in the following documents:Wildland Fire Perimeters (Firep23_1) Metadata For any questions, please contact the data steward:Kim Wallin, GIS SpecialistCAL FIRE, Fire & Resource Assessment Program (FRAP)kimberly.wallin@fire.ca.gov

CAL FIRE's Fire and Resource Assessment Program (FRAP) annually maintains and distributes an historical fire perimeter dataset from across public and private lands in California. The GIS data is developed with the cooperation of the United States Forest Service Region 5, the Bureau of Land Management, the National Park Service and the United States Fish and Wildlife Service and is released in the spring with added data from the previous calendar year. Although the dataset represents the most complete digital record of fire perimeters in California, it is still incomplete, and users should be cautious when drawing conclusions based on the data.

This app contains three pages of maps and documentation of the historical fire perimeter metadata:

Historical Fire Perimeters: The landing page highlights the recent large fires (≥5,000 acres) on a backdrop of all of the dataset's documented fire perimeters dating back to 1878. This map includes perimeters symbolized by decade, county boundaries, California Vegetation, and NAIP imagery back to 2005. This page provides users the ability to add their own data or filter the fire perimeter data. It cleanly lists fire perimeters shown on the map with their name, year, and GIS calculated acreage. The user can navigate to the CAL FIRE current incident webpage or provide comments to the dataset's steward.

Times Burned: The second page provides a map showing an analysis performed annually on the fire perimeter dataset to show case burn frequency from 1950 to present for fires greater than one acre.

Fire Across Time: This third page provides a time enabled layer of the fire perimeter dataset, featuring a time slider to allow users to view the perimeter dataset across time.

The final page provides the user with the dataset's metadata, including its most current data dictionary.

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

This layer presents detectable thermal activity from MODIS satellites for the last 7 days. MODIS Global Fires is a product of NASA’s Earth Observing System Data and Information System (EOSDIS), part of NASA's Earth Science Data. EOSDIS integrates remote sensing and GIS technologies to deliver global MODIS hotspot/fire locations to natural resource managers and other stakeholders around the World.Consumption Best Practices:

As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.Source: NASA FIRMS - Active Fire Data - for WorldScale/Resolution: 1kmUpdate Frequency: 1/2 Hour (every 30 minutes) using the Aggregated Live Feed MethodologyArea Covered: WorldWhat can I do with this layer?The MODIS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.Additional InformationMODIS stands for MODerate resolution Imaging Spectroradiometer. The MODIS instrument is on board NASA’s Earth Observing System (EOS) Terra (EOS AM) and Aqua (EOS PM) satellites. The orbit of the Terra satellite goes from north to south across the equator in the morning and Aqua passes south to north over the equator in the afternoon resulting in global coverage every 1 to 2 days. The EOS satellites have a ±55 degree scanning pattern and orbit at 705 km with a 2,330 km swath width.It takes approximately 2 – 4 hours after satellite overpass for MODIS Rapid Response to process the data, and for the Fire Information for Resource Management System (FIRMS) to update the website. Occasionally, hardware errors can result in processing delays beyond the 2-4 hour range. Additional information on the MODIS system status can be found at MODIS Rapid Response.Attribute InformationLatitude and Longitude: The center point location of the 1km (approx.) pixel flagged as containing one or more fires/hotspots (fire size is not 1km, but variable). Stored by Point Geometry. See What does a hotspot/fire detection mean on the ground?Brightness: The brightness temperature measured (in Kelvin) using the MODIS channels 21/22 and channel 31.Scan and Track: The actual spatial resolution of the scanned pixel. Although the algorithm works at 1km resolution, the MODIS pixels get bigger toward the edge of the scan. See What does scan and track mean?Date and Time: Acquisition date of the hotspot/active fire pixel and time of satellite overpass in UTC (client presentation in local time). Stored by Acquisition Date.Acquisition Date: Derived Date/Time field combining Date and Time attributes.Satellite: Whether the detection was picked up by the Terra or Aqua satellite.Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel.Version: Version refers to the processing collection and source of data. The number before the decimal refers to the collection (e.g. MODIS Collection 6). The number after the decimal indicates the source of Level 1B data; data processed in near-real time by MODIS Rapid Response will have the source code “CollectionNumber.0”. Data sourced from MODAPS (with a 2-month lag) and processed by FIRMS using the standard MOD14/MYD14 Thermal Anomalies algorithm will have a source code “CollectionNumber.x”. For example, data with the version listed as 5.0 is collection 5, processed by MRR, data with the version listed as 5.1 is collection 5 data processed by FIRMS using Level 1B data from MODAPS.Bright.T31: Channel 31 brightness temperature (in Kelvins) of the hotspot/active fire pixel.FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).DayNight: The standard processing algorithm uses the solar zenith angle (SZA) to threshold the day/night value; if the SZA exceeds 85 degrees it is assigned a night value. SZA values less than 85 degrees are assigned a day time value. For the NRT algorithm the day/night flag is assigned by ascending (day) vs descending (night) observation. It is expected that the NRT assignment of the day/night flag will be amended to be consistent with the standard processing.Hours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.RevisionsJune 22, 2022: Added 'HOURS_OLD' field to enhance Filtering data. Added 'Last 7 days' Layer to extend data to match time range of VIIRS offering. Added Field level descriptions.This map is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structures.For more information about the wildfire response efforts, visit the CAL FIRE incident page.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structures.For more information about the wildfire response efforts, visit the CAL FIRE incident page.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structuresFor more information about the wildfire response efforts, visit the CAL FIRE incident page.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structuresFor more information about the wildfire response efforts, visit the CAL FIRE incident page.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structures.For more information about the wildfire response efforts, visit the CAL FIRE incident page.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structures.For more information about the wildfire response efforts, visit the CAL FIRE incident page.

This layer contains the fire perimeters from the previous calendar year, and those dating back to 1878, for California. Perimeters are sourced from the Fire and Resource Assessment Program (FRAP) and are updated shortly after the end of each calendar year. Information below is from the FRAP web site. There is also a tile cache version of this layer.About the Perimeters in this LayerInitially CAL FIRE and the USDA Forest Service jointly developed a fire perimeter GIS layer for public and private lands throughout California. The data covered the period 1950 to 2001 and included USFS wildland fires 10 acres and greater, and CAL FIRE fires 300 acres and greater. BLM and NPS joined the effort in 2002, collecting fires 10 acres and greater. Also in 2002, CAL FIRE’s criteria expanded to include timber fires 10 acres and greater in size, brush fires 50 acres and greater in size, grass fires 300 acres and greater in size, wildland fires destroying three or more structures, and wildland fires causing $300,000 or more in damage. As of 2014, the monetary requirement was dropped and the damage requirement is 3 or more habitable structures or commercial structures.In 1989, CAL FIRE units were requested to fill in gaps in their fire perimeter data as part of the California Fire Plan. FRAP provided each unit with a preliminary map of 1950-89 fire perimeters. Unit personnel also verified the pre-1989 perimeter maps to determine if any fires were missing or should be re-mapped. Each CAL FIRE Unit then generated a list of 300+ acre fires that started since 1989 using the CAL FIRE Emergency Activity Reporting System (EARS). The CAL FIRE personnel used this list to gather post-1989 perimeter maps for digitizing. The final product is a statewide GIS layer spanning the period 1950-1999.CAL FIRE has completed inventory for the majority of its historical perimeters back to 1950. BLM fire perimeters are complete from 2002 to the present. The USFS has submitted records as far back as 1878. The NPS records date to 1921.About the ProgramFRAP compiles fire perimeters and has established an on-going fire perimeter data capture process. CAL FIRE, the United States Forest Service Region 5, the Bureau of Land Management, and the National Park Service jointly develop the fire perimeter GIS layer for public and private lands throughout California at the end of the calendar year. Upon release, the data is current as of the last calendar year.The fire perimeter database represents the most complete digital record of fire perimeters in California. However it is still incomplete in many respects. Fire perimeter database users must exercise caution to avoid inaccurate or erroneous conclusions. For more information on potential errors and their source please review the methodology section of these pages.The fire perimeters database is an Esri ArcGIS file geodatabase with three data layers (feature classes):A layer depicting wildfire perimeters from contributing agencies current as of the previous fire year;A layer depicting prescribed fires supplied from contributing agencies current as of the previous fire year;A layer representing non-prescribed fire fuel reduction projects that were initially included in the database. Fuels reduction projects that are non prescribed fire are no longer included.All three are available in this layer. Additionally, you can find related web maps, view layers set up for individual years or decades, and tile layers here.Recommended Uses There are many uses for fire perimeter data. For example, it is used on incidents to locate recently burned areas that may affect fire behavior (see map left).Other uses include:Improving fire prevention, suppression, and initial attack success.Reduce and track hazards and risks in urban interface areas.Provide information for fire ecology studies for example studying fire effects on vegetation over time. Download the Fire Perimeter GIS data hereDownload a statewide map of Fire Perimeters hereSource: Fire and Resource Assessment Program (FRAP)

National burn probability (BP) and conditional fire intensity level (FIL) data were generated for the conterminous United States (US) using a geospatial Fire Simulation (FSim) system developed by the US Forest Service Missoula Fire Sciences Laboratory to estimate probabilistic components of wildfire risk (Finney et al. [2011]). The FSim system includes modules for weather generation, wildfire occurrence, fire growth, and fire suppression. FSim is designed to simulate the occurrence and growth of wildfires under tens of thousands of hypothetical contemporary fire seasons in order to estimate the probability of a given area (i.e., pixel) burning under current landscape conditions and fire management practices. The data presented here represent modeled BP and FIL for the conterminous US at a 270-meter grid spatial resolution. The six FILs correspond to flame-length classes as follows: FIL1 = < 2 feet (ft); FIL2 = 2 < 4 ft.; FIL3 = 4 < 6 ft.; FIL4 = 6 < 8 ft.; FIL5 = 8 < 12 ft.; FIL6 = 12+ ft. Because they indicate conditional probabilities (i.e., representing the likelihood of burning at a certain intensity level, given that a fire occurs), the FIL*_20160830 data must be used in conjunction with the BP_20160830 data for risk assessment.

Feature layer showing all the fires tracked by Cal OES GIS for the year to date.

In 2012, the CPUC ordered the development of a statewide map that is designed specifically for the purpose of identifying areas where there is an increased risk for utility associated wildfires. The development of the CPUC -sponsored fire-threat map, herein "CPUC Fire-Threat Map," started in R.08-11-005 and continued in R.15-05-006.

A multistep process was used to develop the statewide CPUC Fire-Threat Map. The first step was to develop Fire Map 1 (FM 1), an agnostic map which depicts areas of California where there is an elevated hazard for the ignition and rapid spread of powerline fires due to strong winds, abundant dry vegetation, and other environmental conditions. These are the environmental conditions associated with the catastrophic powerline fires that burned 334 square miles of Southern California in October 2007. FM 1 was developed by CAL FIRE and adopted by the CPUC in Decision 16-05-036.

FM 1 served as the foundation for the development of the final CPUC Fire-Threat Map. The CPUC Fire-Threat Map delineates, in part, the boundaries of a new High Fire-Threat District (HFTD) where utility infrastructure and operations will be subject to stricter fire‑safety regulations. Importantly, the CPUC Fire-Threat Map (1) incorporates the fire hazards associated with historical powerline wildfires besides the October 2007 fires in Southern California (e.g., the Butte Fire that burned 71,000 acres in Amador and Calaveras Counties in September 2015), and (2) ranks fire-threat areas based on the risks that utility-associated wildfires pose to people and property.

Primary responsibility for the development of the CPUC Fire-Threat Map was delegated to a group of utility mapping experts known as the Peer Development Panel (PDP), with oversight from a team of independent experts known as the Independent Review Team (IRT). The members of the IRT were selected by CAL FIRE and CAL FIRE served as the Chair of the IRT. The development of CPUC Fire-Threat Map includes input from many stakeholders, including investor-owned and publicly owned electric utilities, communications infrastructure providers, public interest groups, and local public safety agencies.

The PDP served a draft statewide CPUC Fire-Threat Map on July 31, 2017, which was subsequently reviewed by the IRT. On October 2 and October 5, 2017, the PDP filed an Initial CPUC Fire-Threat Map that reflected the results of the IRT's review through September 25, 2017. The final IRT-approved CPUC Fire-Threat Map was filed on November 17, 2017. On November 21, 2017, SED filed on behalf of the IRT a summary report detailing the production of the CPUC Fire-Threat Map(referenced at the time as Fire Map 2). Interested parties were provided opportunity to submit alternate maps, written comments on the IRT-approved map and alternate maps (if any), and motions for Evidentiary Hearings. No motions for Evidentiary Hearings or alternate map proposals were received. As such, on January 19, 2018 the CPUC adopted, via Safety and Enforcement Division's (SED) disposition of a Tier 1 Advice Letter, the final CPUC Fire-Threat Map.

Additional information can be found here.