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 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 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

All data displayed on this map is near real-time. There are two ways in which this happens: Web service based data and a mobile mapping application called Field Maps. Web services are updated regularly ranging from every minute to once a month. All web services in this map are refreshed automatically to ensure the latest data being provided is displayed. Data collected through the use of Field Maps is done so by firefighters on the ground. The Field Maps application is consuming, creating, and editing data that are stored in ArcGIS Online. These data are then fed directly in to this map. To learn more about these web mapping technologies, visit the links below:Web ServicesArcGIS Field MapsArcGIS OnlineWeb Services used in this map:(visit link to learn more about each service)IRWIN - A central hub that orchestrates data between various fire reporting applications. When a new incident is created and/or updated by a dispatch center or other fire reporting system, it is then displayed on the map using the Integrated Reporting of Wildland-Fire Information (IRWIN) service. Automatically refreshes every five minutes:Fires by Cause - Any incident that has occurred year to date displayed by cause.ArcGIS Online/Field Maps - Part of the Esri Geospatial Cloud, ArcGIS Online and Collector enables firefighters to use web maps created in ArcGIS Online on mobile devices using the Collector application to capture and edit data on the fireline. Data may be captured and edited in both connected and disconnected environments. When data is submitted back to the web service in ArcGIS Online, it is then checked for accuracy and approved for public viewing.Fire Perimeter - Must be set to 'Approved' and 'Public' to be displayed on the map. Automatically refreshes every five minutes.

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.

Version InformationThe data is updated annually with fire perimeters from the previous calendar year.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. A duplicate 2020 Erbes fire was removed. 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. There were 2,132 perimeters that received updated attribution, the bulk of which had IRWIN IDs added. 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.If you would like a full briefing on these adjustments, please contact the data steward, Kim Wallin (kimberly.wallin@fire.ca.gov), CAL FIRE FRAP._CAL FIRE (including contract counties), USDA Forest Service Region 5, USDI Bureau of Land Management & National Park Service, and other agencies jointly maintain a fire perimeter GIS layer for public and private lands throughout the state. The data covers fires back to 1878. 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 damaged/ destroyed residential or commercial structures, and/or caused ≥1 fatality.All cooperating agencies submit perimeters ≥10 acres._Discrepancies between wildfire perimeter data and CAL FIRE Redbook Large Damaging FiresLarge Damaging fires in California were first defined by the CAL FIRE Redbook, and has changed over time, and differs from the definition initially used to define wildfires required to be submitted for the initial compilation of this digital fire perimeter data. In contrast, the definition of fires whose perimeter should be collected has changed once in the approximately 30 years the data has been in existence. Below are descriptions of changes in data collection criteria used when compiling these two datasets. To facilitate comparison, this metadata includes a summary, by year, of fires in the Redbook, that do not appear in this fire perimeter dataset. It is followed by an enumeration of each “Redbook” fire missing from the spatial data. Wildfire Perimeter criteria:~1991: 10 acres timber, 30 acres brush, 300 acres grass, damages or destroys three residence or one commercial structure or does $300,000 worth of damage 2002: 10 acres timber, 50 acres brush, 300 acres grass, damages or destroys three or more structures, or does $300,000 worth of damage~2010: 10 acres timber, 30 acres brush, 300 acres grass, damages or destroys three or more structures (doesn’t include out building, sheds, chicken coops, etc.)Large and Damaging Redbook Fire data criteria:1979: Fires of a minimum of 300 acres that burn at least: 30 acres timber or 300 acres brush, or 1500 acres woodland or grass1981: 1979 criteria plus fires that took ,3000 hours of California Department of Forestry and Fire Protection personnel time to suppress1992: 1981 criteria plus 1500 acres agricultural products, or destroys three residence or one commercial structure or does $300,000 damage1993: 1992 criteria but “three or more structures destroyed” replaces “destroys three residence or one commercial structure” and the 3,000 hours of California Department of Forestry personnel time to suppress is removed2006: 300 acres or larger and burned at least: 30 acres of timber, or 300 acres of brush, or 1,500 acres of woodland, or 1,500 acres of grass, or 1,500 acres of agricultural products, or 3 or more structures destroyed, or $300,000 or more dollar damage loss.2008: 300 acres and largerYear# of Missing Large and Damaging Redbook Fires197922198013198115198261983319842019855219861219875619882319898199091991219921619931719942219959199615199791998101999720004200152002162003520042200512006112007320084320093201022011020124201322014720151020162201711201862019220203202102022020230Total488Enumeration of fires in the Redbook that are missing from Fire Perimeter data. Three letter unit code follows fire name.1979-Sylvandale (HUU), Kiefer (AEU), Taylor(TUU), Parker#2(TCU), PGE#10, Crocker(SLU), Silver Spur (SLU), Parkhill (SLU), Tar Springs #2 (SLU), Langdon (SCU), Truelson (RRU), Bautista (RRU), Crocker (SLU), Spanish Ranch (SLU), Parkhill (SLU), Oak Springs(BDU), Ruddell (BDF), Santa Ana (BDU), Asst. #61 (MVU), Bernardo (MVU), Otay #20 1980– Lightning series (SKU), Lavida (RRU), Mission Creek (RRU), Horse (RRU), Providence (RRU), Almond (BDU), Dam (BDU), Jones (BDU), Sycamore (BDU), Lightning (MVU), Assist 73, 85, 138 (MVU)1981– Basalt (LNU), Lightning #25(LMU), Likely (MNF), USFS#5 (SNF), Round Valley (TUU), St. Elmo (KRN), Buchanan (TCU), Murietta (RRU), Goetz (RRU), Morongo #29 (RRU), Rancho (RRU), Euclid (BDU), Oat Mt. (LAC & VNC), Outside Origin #1 (MVU), Moreno (MVU)1982- Duzen (SRF), Rave (LMU), Sheep’s trail (KRN), Jury (KRN), Village (RRU), Yuma (BDF)1983- Lightning #4 (FKU), Kern Co. #13, #18 (KRN)1984-Bidwell (BTU), BLM D 284,337, PNF #115, Mill Creek (TGU), China hat (MMU), fey ranch, Kern Co #10, 25,26,27, Woodrow (KRN), Salt springs, Quartz (TCU), Bonanza (BEU), Pasquel (SBC), Orco asst. (ORC), Canel (local), Rattlesnake (BDF)1985- Hidden Valley, Magic (LNU), Bald Mt. (LNU), Iron Peak (MEU), Murrer (LMU), Rock Creek (BTU), USFS #29, 33, Bluenose, Amador, 8 mile (AEU), Backbone, Panoche, Los Gatos series, Panoche (FKU), Stan #7, Falls #2 (MMU), USFS #5 (TUU), Grizzley, Gann (TCU), Bumb, Piney Creek, HUNTER LIGGETT ASST#2, Pine, Lowes, Seco, Gorda-rat, Cherry (BEU), Las pilitas, Hwy 58 #2 (SLO), Lexington, Finley (SCU), Onions, Owens (BDU), Cabazon, Gavalin, Orco, Skinner, Shell, Pala (RRU), South Mt., Wheeler, Black Mt., Ferndale, (VNC), Archibald, Parsons, Pioneer (BDU), Decker, Gleason(LAC), Gopher, Roblar, Assist #38 (MVU)1986– Knopki (SRF), USFS #10 (NEU), Galvin (RRU), Powerline (RRU), Scout, Inscription (BDU), Intake (BDF), Assist #42 (MVU), Lightning series (FKU), Yosemite #1 (YNP), USFS Asst. (BEU), Dutch Kern #30 (KRN)1987- Peach (RRU), Ave 32 (TUU), Conover (RRU), Eagle #1 (LNU), State 767 aka Bull (RRU), Denny (TUU), Dog Bar (NEU), Crank (LMU), White Deer (FKU), Briceburg (LMU), Post (RRU), Antelope (RRU), Cougar-I (SKU), Pilitas (SLU) Freaner (SHU), Fouts Complex (LNU), Slides (TGU), French (BTU), Clark (PNF), Fay/Top (SQF), Under, Flume, Bear Wallow, Gulch, Bear-1, Trinity, Jessie, friendly, Cold, Tule, Strause, China/Chance, Bear, Backbone, Doe, (SHF) Travis Complex, Blake, Longwood (SRF), River-II, Jarrell, Stanislaus Complex 14k (STF), Big, Palmer, Indian (TNF) Branham (BLM), Paul, Snag (NPS), Sycamore, Trail, Stallion Spring, Middle (KRN), SLU-864 1988- Hwy 175 (LNU), Rumsey (LNU), Shell Creek (MEU), PG&E #19 (LNU), Fields (BTU), BLM 4516, 417 (LMU), Campbell (LNF), Burney (SHF), USFS #41 (SHF), Trinity (USFS #32), State #837 (RRU), State (RRU), State (350 acres), RRU), State #1807, Orange Co. Asst (RRU), State #1825 (RRU), State #2025, Spoor (BDU), State (MVU), Tonzi (AEU), Kern co #7,9 (KRN), Stent (TCU), 1989– Rock (Plumas), Feather (LMU), Olivas (BDU), State 1116 (RRU), Concorida (RRU), Prado (RRU), Black Mt. (MVU), Vail (CNF)1990– Shipman (HUU), Lightning 379 (LMU), Mud, Dye (TGU), State 914 (RRU), Shultz (Yorba) (BDU), Bingo Rincon #3 (MVU), Dehesa #2 (MVU), SLU 1626 (SLU)1991- Church (HUU), Kutras (SHF)1992– Lincoln, Fawn (NEU), Clover, fountain (SHU), state, state 891, state, state (RRU), Aberdeen (BDU), Wildcat, Rincon (MVU), Cleveland (AEU), Dry Creek (MMU), Arroyo Seco, Slick Rock (BEU), STF #135 (TCU)1993– Hoisington (HUU), PG&E #27 (with an undetermined cause, lol), Hall (TGU), state, assist, local (RRU), Stoddard, Opal Mt., Mill Creek (BDU), Otay #18, Assist/ Old coach (MVU), Eagle (CNF), Chevron USA, Sycamore (FKU), Guerrero, Duck1994– Schindel Escape (SHU), blank (PNF), lightning #58 (LMU), Bridge (NEU), Barkley (BTU), Lightning #66 (LMU), Local (RRU), Assist #22 & #79 (SLU), Branch (SLO), Piute (BDU), Assist/ Opal#2 (BDU), Local, State, State (RRU), Gilman fire 7/24 (RRU), Highway #74 (RRU), San Felipe, Assist #42, Scissors #2 (MVU), Assist/ Opal#2 (BDU), Complex (BDF), Spanish (SBC)1995-State 1983 acres, Lost Lake, State # 1030, State (1335 acres), State (5000 acres), Jenny, City (BDU), Marron #4, Asist #51 (SLO/VNC)1996- Modoc NF 707 (Ambrose), Borrego (MVU), Assist #16 (SLU), Deep Creek (BDU), Weber (BDU), State (Wesley) 500 acres (RRU), Weaver (MMU), Wasioja (SBC/LPF), Gale (FKU), FKU 15832 (FKU), State (Wesley) 500 acres, Cabazon (RRU), State Assist (aka Bee) (RRU), Borrego, Otay #269 (MVU), Slaughter house (MVU), Oak Flat (TUU)1997- Lightning #70 (LMU), Jackrabbit (RRU), Fernandez (TUU), Assist 84 (Military AFV) (SLU), Metz #4 (BEU), Copperhead (BEU), Millstream, Correia (MMU), Fernandez (TUU)1998- Worden, Swift, PG&E 39 (MMU), Chariot, Featherstone, Wildcat, Emery, Deluz (MVU), Cajalco Santiago (RRU)1999- Musty #2,3 (BTU), Border # 95 (MVU), Andrews,

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.

Historical FiresLast updated on 06/17/2022OverviewThe 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 perimeters in 2021.https://nifc.maps.arcgis.com/home/item.html?id=098ebc8e561143389ca3d42be3707caaFWS -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 email

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.

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.

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 contains free and open data layers from ArcGIS Living Atlas of the World that relate to improving situational awareness around wildland fires. It has been pre-configured to be used as is. The intention was to provide a clear and readable map for both fire staff or citizens in or near wildfire areas.Some of the features of this map are:All layers update automatically using Esri’s Aggregated Live Feed (ALF) methodologyUnit measurements are consistant across all layersPop-ups are informative and readable, and have been configured with ArcadeIntuitive palettes and map symbology are color-blind friendlyTime-enabled settings configured on Wind Speed and Gust, Smoke Forecast, and VIIRS layersBeaufort Wind Scale is used and have measurements in miles per hour

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!

Interagency Wildland Fire Perimeter History (IFPH)OverviewThis national fire history perimeter data layer of conglomerated agency perimeters was developed in support of the WFDSS application and wildfire decision support. The layer encompasses the 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 2023 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, links are provided where possible below. In addition, many agencies are now using WFIGS as their authoritative source, beginning in mid-2020.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 Authoritative 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/MapServer

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

Summary This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point location. GPS started being used in 1992 when the technology became available. Records from FMIS (Fire Management Information System) were reviewed and compared to refuge records. Polygon data in FMIS only occurs from 2012 to current and many acreage estimates did not match. This dataset includes ALL fires no matter the size. This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point location. GPS started being used in 1992 when the technology became available. Data origins include: Data origins include: 1) GPS Polygon-data (Best), 2) GPS Lat/Long or UTM, 3)TRS QS, 4)TRS Point, 6)Hand digitized from topo map, 7) Circle buffer, 8)Screen digitized, 9) FMIS Lat/Long. Started compiling fire history of CMR in 2007. This has been a 10 year process.FMIS doesn't include fires polygons that are less than 10 acres. This dataset has been sent to FMIS for FMIS records to be updated with correct information. The spreadsheet contains 10-15 records without spatial information and weren't included in either feature class. Fire information from 1964 - 1980 came from records Larry Eichhorn, BLM, provided to CMR staff. Mike Granger, CMR Fire Management Officer, tracked fires on an 11x17 legal pad and all this information was brought into Excel and ArcGIS. Frequently, other information about the fires were missing which made it difficult to back track and fill in missing data. Time was spent verifiying locations that were occasionally recorded incorrectly (DMS vs DD) and converting TRS into Lat/Long and/or UTM. CMR is divided into 2 different UTM zones, zone 12 and zone 13. This occasionally caused errors in projecting. Naming conventions caused confusion. Fires are frequently names by location and there are several "Soda Creek", "Rock Creek", etc fires. Fire numbers were occasionally missing or incorrect. Fires on BLM were included if they were "Assists". Also, fires on satellite refuges and the district were also included. Acreages from GIS were compared to FMIS acres. Please see documentation in ServCat (URL) to see how these were handled.