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
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Contents: This is an ArcGIS Pro zip file that you can download and use for creating map books based on United States National Grid (USNG). It contains a geodatabase, layouts, and tasks designed to teach you how to create a basic map book.Version 1.0.0 Uploaded on May 24th and created with ArcGIS Pro 2.1.3 - Please see the README below before getting started!Updated to 1.1.0 on August 20thUpdated to 1.2.0 on September 7thUpdated to 2.0.0 on October 12thUpdate to 2.1.0 on December 29thBack to 1.2.0 due to breaking changes in the templateBack to 1.0.0 due to breaking changes in the template as of June 11th 2019Updated to 2.1.1 on October 8th 2019Audience: GIS Professionals and new users of ArcGIS Pro who support Public Safety agencies with map books. If you are looking for apps that can be used by any public safety professional, see the USNG Lookup Viewer.Purpose: To teach you how to make a map book with critical infrastructure and a basemap, based on USNG. You NEED to follow the steps in the task and not try to take shortcuts the first time you use this task in order to receive the full benefits. Background: This ArcGIS Pro template is meant to be a starting point for your map book projects and is based on best practices by the USNG National Implementation Center (TUNIC) at Delta State University and is hosted by the NAPSG Foundation. This does not replace previous templates created in ArcMap, but is a new experimental approach to making map books. We will continue to refine this template and work with other organizations to make improvements over time. So please send us your feedback admin@publicsafetygis.org and comments below. Instructions: Download the zip file by clicking on the thumbnail or the Download button.Unzip the file to an appropriate location on your computer (C:\Users\YourUsername\Documents\ArcGIS\Projects is a common location for ArcGIS Pro Projects).Open the USNG Map book Project File (APRX).If the Task is not already open by default, navigate to Catalog > Tasks > and open 'Create a US National Grid Map Book' Follow the instructions! This task will have some automated processes and models that run in the background but you should pay close attention to the instructions so you also learn all of the steps. This will allow you to innovate and customize the template for your own use.FAQsWhat is US National Grid? The US National Grid (USNG) is a point and area reference system that provides for actionable location information in a uniform format. Its use helps achieve consistent situational awareness across all levels of government, disciplines, and threats & hazards – regardless of your role in an incident.One of the key resources NAPSG makes available to support emergency responders is a basic USNG situational awareness application. See the NAPSG Foundation and USNG Center websites for more information.What is an ArcGIS Pro Task? A task is a set of preconfigured steps that guide you and others through a workflow or business process. A task can be used to implement a best-practice workflow, improve the efficiency of a workflow, or create a series of interactive tutorial steps. See "What is a Task?" for more information.Do I need to be proficient in ArcGIS Pro to use this template? We feel that this is a good starting point if you have already taken the ArcGIS Pro QuickStart Tutorials. While the task will automate many steps, you will want to get comfortable with the map layouts and other new features in ArcGIS Pro.Is this template free? This resources is provided at no-cost, but also with no guarantees of quality assurance or support at this time. Can't I just use ArcMap? Ok - here you go. USNG 1:24K Map Template for ArcMapKnown Limitations and BugsZoom To: It appears there may be a bug or limitation with automatically zooming the map to the proper extent, so get comfortable with navigation or zoom to feature via the attribute table.FGDC Compliance: We are seeking feedback from experts in the field to make sure that this meets minimum requirements. At this point in time we do not claim to have any official endorsement of standardization. File Size: Highly detailed basemaps can really add up and contribute to your overall file size, especially over a large area / many pages. Consider making a simple "Basemap" of street centerlines and building footprints.We will do the best we can to address limitations and are very open to feedback!
Notice: this is not the latest Heat Anomalies image service.This layer contains the relative degrees Fahrenheit difference between any given pixel and the mean heat value for the city in which it is located, for every city in the contiguous United States, Alaska, Hawaii, and Puerto Rico. The Heat Anomalies is also reclassified into a Heat Severity raster also published on this site. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2023.To explore previous versions of the data, visit the links below:Full Range Heat Anomalies - USA 2022Full Range Heat Anomalies - USA 2021Full Range Heat Anomalies - USA 2020Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter or cooler than the average temperature for that same city as a whole. This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at The Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so The Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). The Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This layer features special areas of interest (AOIs) that have been contributed to Esri Community Maps using the new Community Maps Editor app. The data that is accepted by Esri will be included in selected Esri basemaps, including our suite of Esri Vector Basemaps, and made available through this layer to export and use offline. Export DataThe contributed data is also available for contributors and other users to export (or extract) and re-use for their own purposes. Users can export the full layer from the ArcGIS Online item details page by clicking the Export Data button and selecting one of the supported formats (e.g. shapefile, or file geodatabase (FGDB)). User can extract selected layers for an area of interest by opening in Map Viewer, clicking the Analysis button, viewing the Manage Data tools, and using the Extract Data tool. To display this data with proper symbology and metadata in ArcGIS Pro, you can download and use this layer file.Data UsageThe data contributed through the Community Maps Editor app is primarily intended for use in the Esri Basemaps. Esri staff will periodically (e.g. weekly) review the contents of the contributed data and either accept or reject the data for use in the basemaps. Accepted features will be added to the Esri basemaps in a subsequent update and will remain in the app for the contributor or others to edit over time. Rejected features will be removed from the app.Esri Community Maps Contributors and other ArcGIS Online users can download accepted features from this layer for their internal use or map publishing, subject to the terms of use below.
Last Update: 9/5/2024, Requires ArcGIS Pro 3.2.xThis is a file structure with ArcGIS Pro project and layout templates for supporting Urban Search and Rescue Teams in 2024. It points to the latest feature layers and is based on the NWCG Wildfire GIS templates.Updates to this project can be found in the Read Me text document in the root folder of the template after downloading. Some patch notes can also be found below in the comments.Special thanks to NIFC and the Wildfire GIS Community for the starting template. For more documentation see NWCG Standards for Geospatial Operations, PMS 936 | NWCGYOU WILL NOT BE ABLE TO ACCESS any incident data unless you are a member of the NSARGC Group.If the template brings you to a screen saying "Invalid Token", you may need to try downloading it again. How to deploy templateThis template is not a traditional ArcGIS Pro template. When you download this template, you are downloading the full folder structure, pre-made map projects, layouts, databases, and tools that have been designed to work alongside SARCOP. This "template" does not use the "Create a project from a template" workflow within Pro, rather you are downloading the full project, and it can be modified as you see fit from there. Below are the recommended steps to take to deploy the template.Download the template anywhere on your PC by clicking the Download button on the top right below Sign In and Overview. This will download as a Zipped folder, likely to your Downloads folder.Go to the C drive of your computer and create a new folder called "Incidents", then create another folder within that Incidents folder with the name of the incident you are using the template for. For example, if the incident name is "Hurricane Lisa", the folder path should look something like "C:\Incidents\2024xxxx_HurricaneLisa".Extract the zipped folder contents from step 1 to that new incident folder you created in step 2. In the Hurricane Lisa example, data would be extracted to C:\Incidents\2024xxxx_HurricaneLisa.Go to the newly extracted folders and find the Projects folder. Open that and double click on any APRX file to begin work.
Notice: this is not the latest Heat Island Anomalies image service. For 2023 data visit https://tpl.maps.arcgis.com/home/item.html?id=e89a556263e04cb9b0b4638253ca8d10.This layer contains the relative degrees Fahrenheit difference between any given pixel and the mean heat value for the city in which it is located, for every city in the contiguous United States. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2021, with patching from summer of 2020 where necessary.Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter or cooler than the average temperature for that same city as a whole. This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at The Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so The Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). The Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Regions_(December_2018)_Full_Extent_EN/MapServer
Last Update: 06/18/2025 with v10 launch and Reverse Geocode HotfixRequires ArcGIS Pro 3.3.xThis is a file structure with ArcGIS Pro project and layout templates for supporting Urban Search and Rescue Teams in 2024. It points to the latest feature layers and is based on the NWCG Wildfire GIS templates.Updates to this project can be found in the Read Me text document in the root folder of the template after downloading. Some patch notes can also be found below in the comments.Special thanks to NIFC and the Wildfire GIS Community for the starting template. For more documentation see NWCG Standards for Geospatial Operations, PMS 936 | NWCGYOU WILL NOT BE ABLE TO ACCESS any incident data unless you are a member of the NSARGC Group.If the template brings you to a screen saying "Invalid Token", you may need to try downloading it again. How to deploy templateThis template is not a traditional ArcGIS Pro template. When you download this template, you are downloading the full folder structure, pre-made map projects, layouts, databases, and tools that have been designed to work alongside SARCOP. This "template" does not use the "Create a project from a template" workflow within Pro, rather you are downloading the full project, and it can be modified as you see fit from there. Below are the recommended steps to take to deploy the template.Download the template anywhere on your PC by clicking the Download button on the top right below Sign In and Overview. This will download as a Zipped folder, likely to your Downloads folder.Go to the C drive of your computer and create a new folder called "Incidents", then create another folder within that Incidents folder with the name of the incident you are using the template for. For example, if the incident name is "Hurricane Lisa", the folder path should look something like "C:\Incidents\2024xxxx_HurricaneLisa".Extract the zipped folder contents from step 1 to that new incident folder you created in step 2. In the Hurricane Lisa example, data would be extracted to C:\Incidents\2024xxxx_HurricaneLisa.Go to the newly extracted folders and find the Projects folder. Open that and double click on any APRX file to begin work.
https://academictorrents.com/nolicensespecifiedhttps://academictorrents.com/nolicensespecified
Contains results of full FeatureServer crawl of the US Fisheries and Wildlife Open Data site (). Each dataset contains an item.json with basic metadata, though many do not expose direct GIS file downloads through their ArcGIS data sources. For those that do, a GeoJSON file has been downloaded for each layer, as that is the only format available through USFW FeatureServers. Datasets are sorted by category if available, if not they are within the Misc folder, and are then sorted by tag. Includes US Fish and Wildlife Service Open Data.csv, a record of all datasets present.
This FREE extension enables discovering and using GIS resources available in a GEOSS Clearinghouse directly from ArcGIS Desktop and ArcGIS Explorer. The CS-W Client for ArcGIS can search many implementations of CS-W implementing CS-W 2.0.0, 2.0.1, 2.0.2 and a number of Application Profiles (OGCCORE, APISO, EBRIM). Providers can extend the CS-W Client by creating a profile of their CS-W service and including that in the CS-W client configuration. View the title, abstract, or footprints of search results or view and download the full metadata. Add referenced live map services (ArcGIS Server, ArcIMS, WMS) to an ArcMap document or ArcGIS Explorer globe. ArcGIS Desktop 9.3 is required to install the ArcMap component of the CS-W Clients for ArcGIS. The CS-W Clients for ArcGIS component for ArcGIS Explorer requires ArcGIS Explorer 380 or higher.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Regions_(December_2019)_FEB_EN/MapServer
Data on the true and full value determination (FVD) of all personal and real property in Alaska municipalities. The FVD is utilized in calculating the require local contributions that some municipalities have to pay in order to fund their local school districts.Source: Alaska Department of Commerce, Community, and Economic Development Division of Community and Regional Affairs, Office of the State Assessor
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Wards_(December_2019)_FCB_EW/MapServerREST URL of ArcGIS for INSPIRE Feature DownloadService – https://dservices1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/services/Wards_December_2019_Full_Clipped_Boundaries_EW/WFSServer?service=wfs&request=getcapabilities
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Wards_(December_2019)_FEB_EW/MapServer
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Registration_Districts_(April_2019)_FEB_EW/MapServer
https://www.ons.gov.uk/methodology/geography/licenceshttps://www.ons.gov.uk/methodology/geography/licences
This file contains the digital vector boundaries for Regions, in England, as at 31 December 2018. The BFE boundaries are full resolution - extent of the realm (usually this is the Mean Low Water mark but in some cases boundaries extend beyond this to include off shore islands). Contains both Ordnance Survey and ONS Intellectual Property Rights.REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Regions_(December_2018)_Full_Extent_EN/MapServerREST URL of ArcGIS for INSPIRE Feature DownloadService – https://dservices1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/services/Regions_December_2018_Full_Extent_EN/WFSServer?service=wfs&request=getcapabilitiesREST URL of Feature Access Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Regions_December_2018_Full_Extent_EN_2022/FeatureServer
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Cancer_Alliances_(July_2019)_FCB_EN/MapServerREST URL of ArcGIS for INSPIRE Feature DownloadService – https://dservices1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/services/Cancer_Alliances_July_2019_Full_Clipped_Boundaries_EN/WFSServer?service=wfs&request=getcapabilities
24K Hydro File Geodatabase, including bank lines, flow lines, junction points, hydro lines, water bodies, hydro points, and a network. Access the user guide, data dictionaries, and metadata below.The DNR Hydrography database was developed statewide using several 1:24,000-scale sources. This data layer includes information about surface water features represented on the USGS 1:24,000-scale topographic map series such as perennial and intermittent streams, lakes, etc. Because the sources of the Hydrography data span many years and originate from several sources, the data may reflect areas of transition from one source to another. As a result, the water features as represented in the Hydrography data may not always match what you see on a particular USGS quad or Digital Raster Graphic (DRG). General source information is presented on this map: Wisconsin Hydrography Source Information. Note: Wetlands delineations are not included in the DNR Hydrography data layer. For information about DNR Wetlands data, see the Wisconsin Wetland Inventory web page.Report errors in this data to Dennis Wiese (dennis.wiese@wisconsin.gov) with the following information:HYDROID of the feature in question; OR if the feature is missing, a location coordinate or description (e.g. latitude/longitude, Public Land Survey System Township, Range, and Section identifier) that identifies the area in question.Optional but very helpful: a screen capture of the area in question, or the Water Body Identification Code (WBIC) of the feature in question.DNR staff can access the hydrography database in the agency's central GIS data repository. The hydrography feature classes are stored in the feature dataset "W23324.WD_HYDRO_DATA_24K".USER GUIDES AND DOCUMENTATION: WDNR_HYDRO_24k_GETTING STARTED WDNR HYDRO 24K UPDATES DOCUMENT 24K HYDRO DECISION RULESData Dictionaries and Metadata WDNR_HYDRO_24k_waterbody_data_dict WDNR_HYDRO_24k_waterbody_metadata WDNR_HYDRO_24k_flowline_data_dict WDNR_HYDRO_24k_flowline_metadata WDNR_HYDRO_24k_bank_data_dict WDNR_HYDRO_24k_bank_metadata WDNR_HYDRO_24k_junction_data_dict WDNR_HYDRO_24k_junction_metadata WDNR_HYDRO_24k_line_data_dict WDNR_HYDRO_24k_line_metadata WDNR_HYDRO_24k_flowline_wbic_data_dict WDNR_HYDRO_24k_flowline_wbic_metadata WDNR_HYDRO_24k_waterbody_wbic_data_dict WDNR_HYDRO_24k_waterbody_wbic_metadataArcMap Layer (.lyr) Files 24k Hydro Flowline Duration 24k Hydro Bank Lines 24k Hydro Flowline Streams 24k Hydro Waterbody Open Water
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The BUE boundaries are generalised to 500m - extent of the realm (usually this is the Mean Low Water mark but in some cases boundaries extend beyond this to include off shore islands).Contains both Ordnance Survey and ONS Intellectual Property Rights. REST URL of WFS Server – https://dservices1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/services/CAL_APR_2020_EN_BUE/WFSServer?service=wfs&request=getcapabilities REST URL of Map Server – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/CAL_APR_2020_EN_BUE/MapServer REST URL of Feature Access Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/CAL_APR_2020_EN_BUE/FeatureServer
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