Includes links to various GIS events and conferences

Outreach pop up events. Programs are held by Minnesota Valley National Wildlife Refuge's Community Outreach and Engagement Team and community/non-profit partners. All programs hosted by Minnesota Valley National Wildlife Refuge's Community Outreach and Engagement Team are completely free for all community members to enjoy. Programs can be advertised on our Facebook or official website. The Minnesota Valley National Wildlife Refuge's Community Outreach and Engagement Team may even do free programming as a pop-up event in a local park or lake! Not everyone may be able to come to the refuge, so this is one way the Minnesota Valley National Wildlife Refuge's Community Outreach and Engagement Team is able to reach into the community in their own neighborhood.

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

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

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

The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee. Use the metadata link, http://nhdgeo.usgs.gov/metadata/nhd_high.htm, for additional information. Purpose: The NHD is a national framework for assigning reach addresses to water-related entities, such as industrial discharges, drinking water supplies, fish habitat areas, wild and scenic rivers. Reach addresses establish the locations of these entities relative to one another within the NHD surface water drainage network, much like addresses on streets. Once linked to the NHD by their reach addresses, the upstream/downstream relationships of these water-related entities--and any associated information about them--can be analyzed using software tools ranging from spreadsheets to geographic information systems (GIS). GIS can also be used to combine NHD-based network analysis with other data layers, such as soils, land use and population, to help understand and display their respective effects upon one another. Furthermore, because the NHD provides a nationally consistent framework for addressing and analysis, water-related information linked to reach addresses by one organization (national, state, local) can be shared with other organizations and easily integrated into many different types of applications to the benefit of all.

The dataset is made publicly available as a GIS at nominal 1:5 000 000 scale, and shows the time-space-event distribution of mafic-ultramafic magmatism in Australia from the early Archean to the present day. Development of this GIS has been a multi-year project and earlier released extracts (in viewable pdf form with accompanying Geoscience Australia Records) included compilations for the Archean magmatic record, the Proterozoic magmatic record, and the Australian Large Igneous Provinces (LIPs). Publication of the GIS completes the series with addition of the Phanerozoic magmatic record, and formalisation of the complete record of Archean-Phanerozoic magmatic events as a single series. The chronology of Australian mafic-ultramafic magmatism resolves into 74 magmatic events within, predominately, resolvable bands of ±10 million years. Each event is identified by geological units grouped by similar age - this coeval magmatism may or may not be genetically related and may be in response to different geodynamic environments. These magmatic events range in age from the Eoarchean ~3730 Ma ME 1 - Manfred Event, confined within a small remnant domain within the Yilgarn Craton, to the widespread record of Cenozoic magmatism in eastern Australia (ME 72 to ME 74). The magmatic events range in magnitude from the giant volumes of magma in Large Igneous Provinces, to events whose only known occurrence is an isolated record of dated mafic igneous rock in a single drillhole. The GIS makes it possible to focus on the location of any one of these magmatic events, or groups of magmatic events that may be of interest, and overlay context from any other information that users may have available. The delineation of magmatic events for this study is based on several hundred published ages of mafic and ultramafic igneous rocks from different isotopic systems and minerals. In addition to their ages and extents, primary recorded aspects of each magmatic event include the presence or absence of ultramafic components. Further to this, the presence or correlation of known magmatic-related mineralisation is highlighted in Time-Space-Event Charts of Australia (Appendix D, figures D1 and D2). The basis for mapping has been regional solid geology, interpreted basement geology and surface geology base maps made available by the State and Northern Territory geological surveys, providing insight into the total areal extent of the magmatic systems under cover. Also available to complement the Event GIS are the domains and element boundaries from the Australian Crustal Elements map. These boundaries which are which are based on geophysical extrapolation of crustal elements under the cover of continental basins, provide a framework of the shallow crustal structure of the continent, and are used in this guide. The Crustal Elements digital dataset is available for download from the Geoscience Australia website. Insight into the geodynamic development of the continent is provided by the magmatic event structure through time. The compilation draws attention to concentrations of mafic-ultramafic magmatism in the Archean from ~2820-2665 Ma, in the Proterozoic from ~1870-1590 Ma, and in the late Neoproterozoic-Phanerozoic from ~530-225 Ma. These three time spans contain 39 of the 74 magmatic events, 53% of the entire mafic-ultramafic magmatic event record of the continent. The periods in between have mafic-ultramafic magmatic records that are more dispersed in time. Other features of interest include the shared geographic and crustal element locations of Large Igneous Provinces and numerous events with smaller magma volumes. Read the rest of the Executive Summary in the document.

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

These datasets represent a systematic collection of harmonized data concerning geological events. GIS layers display data on the Portal at a resolution of 1:100,000 and 1:250,000 scale concerning earthquakes, submarine landslides, volcanoes, tsunamis, fluid emissions and Quaternary tectonics, subdivided according to their geometry (polygons, points and lines). They provide information on the type of events which have taken place in the past and might potentially occur again. Where available, details include dimensions, state of activity, morphological type and lithology. The elaboration of guidelines to compile GIS layers was aimed at identifying parameters to be used to thoroughly characterize each event. Particular attention has been devoted to the definition of the Attribute tables in order to achieve the best degree of harmonization and standardization complying with the European INSPIRE Directive. Shapefiles can be downloaded from the Portal and used locally in order to browse through the details of the different features, consulting their Attribute tables. Information contained therein provide an inventory of available data which can be fruitfully applied in the management of coastal areas and support planning of further surveys. By combining the diverse information contained in the different layers, it might be possible to elaborate additional thematic maps which could support further research. Moreover, they potentially represent a useful tool to increase awareness of the hazards which might affect coastal areas. Data sources include detailed information held by the Project Partners plus any further publicly available third-party data (last update Sep. 2021). All products delivered by Partners have been collated, verified and validated in order to achieve the best degree of harmonization and INSPIRE compliance. Each layer is complemented by an Attribute table which provides, in addition to the location, type of geological event and its references (mandatory), further information for each occurrence (where available). Since features considered within WP6 have a scattered distribution, the additional layer “Geological events distribution” provides basic information on areas of occurrences, no occurrences and no data for the marine areas surrounding European countries.

The National Wildfire Coordinating Group's Wildland Fire Event Point data standard defines the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting GIS Standard Operating Procedures on Incidents (GSTOP) guidance.

This feature class will use a specific symbol set. The symbol set is defined by the GIS Standard Operating Procedures for Incidents (GSTOP). For additional information follow this link: http://gis.nwcg.gov/gstop_about.html

This feature class will be part of a Incident Geodatabase that will contain Fire Point, Fire Line, and Fire Polygon feature classes.

This standard is for incident based data collection, storage and exchange. The intent of this standard is to update existing data formats and provide a common set of attributes for use on wildland fires starting fire season 2016.

This standard should not be confused with the NWCG geospatial data standard for Wildland Fire Location Point, which is for the representation of the final spatial location of the fire occurrence ignition.

Events are symbolized by their Seismic Magnitude regardless of age.

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

The National Wildfire Coordinating Group's Wildland Fire Event Polygon data standard defines the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting GIS Standard Operating Procedures on Incidents (GSTOP) guidance.

This feature class will use a specific symbol set. The symbol set is defined by the GIS Standard Operating Procedures for Incidents (GSTOP). For additional information follow this link: http://gis.nwcg.gov/gstop_about.html

This feature class will be part of a Incident Geodatabase that will contain Fire Point, Fire Line, and Fire Polygon feature classes.

This standard is for incident based data collection, storage and exchange. The intent of this standard is to update existing data formats and provide a common set of attributes for use on wildland fires starting fire season 2016.

This standard is for incident based data collection, storage and exchange. This standard should not be confused with the NWCG geospatial data standard for Wildland Fire Perimeters (polygon), which is intended daily and final wildfire and prescribed fire perimeters data exchange.

The layer depicts data for 100-Year Storm Surge [under current conditions], 100-Year Storm Surge Plus One Foot of Sea Level Rise, 100-Year Storm Surge Plus Three Feet of Sea Level Rise, 100-Year Storm Surge Plus Five Feet of Sea Level Rise, and 100-Year Storm Surge Plus Seven Feet of Sea Level Rise. These scenarios, and all attendant modeling, originated with CRMC. This layer was created by the Rhode Island Statewide Planning Program (RISPP) as part of the 2016 Municipal Transportation Assets Vulnerable to Sea Level Rise and Storm Surge Project using inundation data from the STORMTOOLS Dataset prepared by the Coastal Recourses Management Council (CRMC). Five storm surge inundation scenarios from STORMTOOLS were brought together such that each polygon would depict one inundation scenario.

Feature service generated by Hub for public Hub events. DO NOT DELETE THIS SERVICE. It stores the public Hub events for your organization.

After a clean up event by our block adopters, event organizers record their clean up data. This includes items such as how many trash bags were used. The number of volunteers that joined. By sharing this information the Office of Clean city can better engage with all communities. This layer is used in the Group Spotlights section of the Adopt a Block hub site, https://adopt-a-block-dcgis.hub.arcgis.com/.

Interagency Wildland Fire Perimeter History (IFPH) Overview This 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 2024 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 (WFIGS pull for updates began 2022)USDA FS Regional Fire History Data (WFIGS pull for updates began 2024)BLM Fire Planning and Fuels (WFIGS pull for updates began 2020)National Park Service - Includes Prescribed Burns (WFIGS pull for updates began 2020)Fish and Wildlife Service (WFIGS pull for updates began 2024)Bureau of Indian Affairs (Incomplete, 2017-2018 from BIA, WFIGS pull for updates began 2020)CalFire FRAS - Includes Prescribed Burns (CALFIRE only source, non-fed fires)WFIGS - updates included since mid-2020, unless otherwise noted Data 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.Attributes This 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 maintained by IrWIN. (This unique identifier may NOT replace the GeometryID core attribute) FORID - Unique identifier assigned to each incident record in the Fire Occurence Data Records system. (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; Other GIS_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.9 UNQE_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-000001 LOCAL_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: CORMP COMMENTS - 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 Unknown GEO_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 (4,781 Records thru 2021), other federal sources for AK data removed. No RX data included.CA: GEOID = OBJECT ID of downloaded file geodatabase (8,480 Records, federal fires removed, includes RX. Significant cleanup occurred between 2023 and 2024 data pulls resulting in fewer perimeters).FWS: GEOID = OBJECTID of service download combined history 2005-2021 (2,959 Records), includes RX.BIA: GEOID = "FireID" 2017/2018 data (382 records). No RX data included.NPS: GEOID = EVENT ID 15,237 records, includes RX. In 2024/2023 dataset was reduced by combining singlepart to multpart based on valid Irwin, FORID or Unique Fire IDs. RX data included.BLM: GEOID = GUID from BLM FPER (23,730 features). No RX data included.USFS: GEOID=GLOBALID from EDW records (48,569 features), includes RXWFIGS: GEOID=polySourceGlobalID (9724 records added or replaced agency record since mid-2020)Attempts to repair Unique Fire ID not made. Attempts to repair dates not made. Verified all IrWIN IDs and FODRIDs present via joins and cross checks to the respective dataset. Stripped leading and trailing spaces, fixed empty values to

This map contains continuously updated U.S. tornado reports, wind storm reports and hail storm reports. Click each feature to receive information about the specific location and read a short description about the issue. Now contains ALL available Incident Report types, for a total of 15, not just Hail; Wind; and Tornados.See new layer for details or Feature Layer Item with exclusive Past 24-Hour ALL Storm Reports Layer. Each layer is updated 4 times hourly from data provided by NOAA’s National Weather Service Storm Prediction Center. A full archive of storm events can be accessed from the NOAA National Centers for Environmental Information. SourceNOAA Storm Prediction Center https://www.spc.noaa.gov/climo/reportsNOAA ALL Storm Reports layer https://www.spc.noaa.gov/exper/reports Sample DataSee Sample Layer Item for sample data during inactive periods! Update FrequencyThe service is updated every 15 minutes using the Aggregated Live Feeds Methodology Area CoveredCONUS (Contiguous United States) What can you do with this layer? This map service is suitable for data discovery and visualization.Change the symbology of each layer using single or bi-variate smart mapping. For instance, use size or color to indicate the intensity of a tornado.Click each feature to receive information about the specific location and read a short description about the issue.Query the attributes to show only specific event types or locations. RevisionsAug 10, 2021: Updated Classic Layers to use new Symbols. Corrected Layer Order Presentation. Updated Thumbnail.Aug 8, 2021: Update to layer-popups, correcting link URLs. Expanded length of 'Comment' fields to 1kb of text. New Layer added that includes ALL available Incident Types and Age in 'Hours Old'. 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.