Analysis of ‘2018 CT Data Catalog (Non GIS)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/fe457197-5afe-4a20-a131-1bdcf9bd8ace on 26 January 2022.

--- Dataset description provided by original source is as follows ---

Catalog of high value data inventories produced by Connecticut executive branch agencies and compiled by the Office of Policy and Management. This catalog does not contain information about high value GIS data, which is compiled in a separate data inventory at the following link: https://data.ct.gov/Government/CT-Data-Catalog-GIS-/p7we-na27

As required by Public Act 18-175, executive branch agencies must annually conduct a high value data inventory to capture information about the high value data that they collect.

High value data is defined as any data that the department head determines (A) is critical to the operation of an executive branch agency; (B) can increase executive branch agency accountability and responsiveness; (C) can improve public knowledge of the executive branch agency and its operations; (D) can further the core mission of the executive branch agency; (E) can create economic opportunity; (F) is frequently requested by the public; (G) responds to a need and demand as identified by the agency through public consultation; or (H) is used to satisfy any legislative or other reporting requirements.

This dataset was last updated 3/4/2019 and will continue to be updated as high value data inventories are submitted to OPM.

--- Original source retains full ownership of the source dataset ---

Deprecation notice: This tool is deprecated because this functionality is now available with out-of-the-box tools in ArcGIS Pro. The tool author will no longer be making further enhancements or fixing major bugs.Use Add GTFS to a Network Dataset to incorporate transit data into a network dataset so you can perform schedule-aware analyses using the Network Analyst tools in ArcMap.After creating your network dataset, you can use the ArcGIS Network Analyst tools, like Service Area and OD Cost Matrix, to perform transit/pedestrian accessibility analyses, make decisions about where to locate new facilities, find populations underserved by transit or particular types of facilities, or visualize the areas reachable from your business at different times of day. You can also publish services in ArcGIS Server that use your network dataset.The Add GTFS to a Network Dataset tool suite consists of a toolbox to pre-process the GTFS data to prepare it for use in the network dataset and a custom GTFS transit evaluator you must install that helps the network dataset read the GTFS schedules. A user's guide is included to help you set up your network dataset and run analyses.Instructions:Download the tool. It will be a zip file.Unzip the file and put it in a permanent location on your machine where you won't lose it. Do not save the unzipped tool folder on a network drive, the Desktop, or any other special reserved Windows folders (like C:\Program Files) because this could cause problems later.The unzipped file contains an installer, AddGTFStoaNetworkDataset_Installer.exe. Double-click this to run it. The installation should proceed quickly, and it should say "Completed" when finished.Read the User's Guide for instructions on creating and using your network dataset.System requirements:ArcMap 10.1 or higher with a Desktop Standard (ArcEditor) license. (You can still use it if you have a Desktop Basic license, but you will have to find an alternate method for one of the pre-processing tools.) ArcMap 10.6 or higher is recommended because you will be able to construct your network dataset much more easily using a template rather than having to do it manually step by step. This tool does not work in ArcGIS Pro. See the User's Guide for more information.Network Analyst extensionThe necessary permissions to install something on your computer.Data requirements:Street data for the area covered by your transit system, preferably data including pedestrian attributes. If you need help preparing high-quality street data for your network, please review this tutorial.A valid GTFS dataset. If your GTFS dataset has blank values for arrival_time and departure_time in stop_times.txt, you will not be able to run this tool. You can download and use the Interpolate Blank Stop Times tool to estimate blank arrival_time and departure_time values for your dataset if you still want to use it.Help forum

This dataset is a compilation of address point data for the City of Tempe. The dataset contains a point location, the official address (as defined by The Building Safety Division of Community Development) for all occupiable units and any other official addresses in the City. There are several additional attributes that may be populated for an address, but they may not be populated for every address. Contact: Lynn Flaaen-Hanna, Development Services Specialist Contact E-mail Link: Map that Lets You Explore and Export Address Data Data Source: The initial dataset was created by combining several datasets and then reviewing the information to remove duplicates and identify errors. This published dataset is the system of record for Tempe addresses going forward, with the address information being created and maintained by The Building Safety Division of Community Development.Data Source Type: ESRI ArcGIS Enterprise GeodatabasePreparation Method: N/APublish Frequency: WeeklyPublish Method: AutomaticData Dictionary

Analysis of ‘2019 CT Data Catalog (GIS)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/168eaac6-5f52-4015-be99-93031db2fd0d on 26 January 2022.

--- Dataset description provided by original source is as follows ---

Catalog of high value data inventories produced by Connecticut executive branch agencies and compiled by the Office of Policy and Management, updated in 2019. This catalog contains information on high value GIS data only. A catalog of high value non-GIS data may be found at the following link: https://data.ct.gov/Government/2019-CT-Data-Catalog-Non-GIS-/f6rf-n3ke

As required by Public Act 18-175, executive branch agencies must annually conduct a high value data inventory to capture information about the high value data that they collect.

High value data is defined as any data that the department head determines (A) is critical to the operation of an executive branch agency; (B) can increase executive branch agency accountability and responsiveness; (C) can improve public knowledge of the executive branch agency and its operations; (D) can further the core mission of the executive branch agency; (E) can create economic opportunity; (F) is frequently requested by the public; (G) responds to a need and demand as identified by the agency through public consultation; or (H) is used to satisfy any legislative or other reporting requirements.

This dataset was last updated 2/3/2020 and will continue to be updated as high value data inventories are submitted to OPM.

The 2018 high value data inventories for Non-GIS and GIS data can be found at the following links: CT Data Catalog (Non GIS): https://data.ct.gov/Government/CT-Data-Catalog-Non-GIS-/ghmx-93jn/ CT Data Catalog (GIS): https://data.ct.gov/Government/CT-Data-Catalog-GIS-/p7we-na27 Less

--- Original source retains full ownership of the source dataset ---

Greater Sage Grouse managment zones based on CDOW GrSG_PopRangeZones20120609.shp. Modified and renumbered by BLM 06/09/2012. The zones were modified again by the BLM in August 2012. The BLM discovered areas where PPH and PGH were not included within the zones. Several discrepancies between the zones and PPH and PGH dataset were discovered, and were corrected by the BLM. Zones 18-21 are linkages added as zones by the BLM. In addition to these changes, the zones were adjusted along the UT-CO boundary and WY-CO boundary to be coincident with the county boundaries dataset. This was requested by Karin Eichhoff, GIS Specialist at the CPW. She provided the county boundaries dataset to the BLM. Greater sage grouse GIS data set identifying occupied, potential and vacant/unknown habitats in Colorado. The data set was created by mapping efforts of the Colorado Division of Wildlife biologist and district officers during the spring of 2004, and further refined in the winter of 2005. Occupied Habitat: Areas of suitable habitat known to be used by sage-grouse within the last 10 years from the date of mapping. Areas of suitable habitat contiguous with areas of known use, which do not have effective barriers to sage-grouse movement from known use areas, are mapped as occupied habitat unless specific information exists that documents the lack of sage-grouse use. Mapped from any combination of telemetry locations, sightings of sage grouse or sage grouse sign, local biological expertise, GIS analysis, or other data sources. Vacant or Unknown Habitat: Suitable habitat for sage-grouse that is separated (not contiguous) from occupied habitats that either: 1) Has not been adequately inventoried, or 2) Has not had documentation of grouse presence in the past 10 years Potentially Suitable Habitat: Unoccupied habitats that could be suitable for occupation of sage-grouse if practical restoration were applied. Soils or other historic information (photos, maps, reports, etc.) indicate sagebrush communities occupied these areas. As examples, these sites could include areas overtaken by pinyon-juniper invasions or converted rangelandsUpdate October 10, 2012: NHD water bodies greater than 100 acres were removed from GrSG habitat and management zones, as requested by Jim Cagney, BLM CO Northwest District Manager. 6 water bodies in total were removed (Hog Lake, South Delaney, Williams Fork Reservoir, North Delaney, Wolford Mountain Reservoir (2 polygons)). There were two “SwampMarsh” polygons that resulted when selecting polygons greater than 100 acres; these polygons were not included. Only polygons with the attribute “LakePond” were removed from GrSG habitat.

PurposeThis map is designed to be loaded into ArcGIS Pro projects to give users easy access to sanitary sewer utility data.BackgroundPrior to the creation of this map, non-GIS users would only be able to access static copies of utility data in the ArcGIS Online utility web maps/apps. This basemap allows power users to access a live feed of the data, which is updated on a nightly basis. This map can be opened in ArcGIS Pro to give users more flexibility to analyze and explore the data. The map and the data within are for internal use only.ProcessThe GIS Analyst updates this dataset on a continuous basis using As-Builts and CAD files submitted during the development review process, as well as field staff verification

Historic Fire Perimeter Dataset Feedback (arcgis.com)

Current criteria for data collection are as follows:

CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.

All cooperating agencies submit perimeters ≥10 acres.

Version update:

Firep24_1 was released in April 2025. Five hundred forty-eight fires from the 2024 fire season were added to the database (2 from BIA, 56 from BLM, 197 from CAL FIRE, 193 from Contract Counties, 27 from LRA, 8 from NPS, 55 from USFS and 8 from USFW). Six perimeters were added from the 2025 fire season (as a special case due to an unusual January fire siege). Five duplicate fires were removed, and the 2023 Sage was replaced with a more accurate perimeter. There were 900 perimeters that received updated attribution (705 removed “FIRE” from the end of Fire Name field and 148 replaced Complex IRWIN ID with Complex local incident number for COMPLEX_ID field). The following fires were identified as meeting our collection criteria but are not included in this version and will hopefully be added in a future update: Addie (2024-CACND-002119), Alpaugh (2024-CACND-001715), South (2024-CATIA-001375). One perimeter is missing containment date that will be updated in the next release.

Cross checking CALFIRS reporting for new CAL FIRE submissions to ensure accuracy with cause class was added to the compilation process. The cause class domain description for “Powerline” was updated to “Electrical Power” to be more inclusive of cause reports.

Includes separate layers filtered by criteria as follows:

California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale.

Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2020-January 2025), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.

California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-January 2025. Symbolized by decade, and display starting at country level scale.

Detailed metadata is included in the following documents:

Wildland Fire Perimeters (Firep24_1) Metadata

See more information on our Living Atlas data release here:

CAL FIRE Historical Fire Perimeters Available in ArcGIS Living Atlas

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

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

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

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

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

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

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

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

BSUs were revised in May 2016. New data submitted by Montana and Oregon was used to update the earlier version of this feature class. The biologically significant unit (BSU) is a geographical/spatial area within Greater Sage-Grouse habitat that contains relevant and important habitats which is used as the basis for comparative calculations to support evaluation of changes to habitat. This BSU unit, or subset of this unit is used in the calculation of the anthropogenic disturbance threshold and in the adaptive management habitat trigger. BSU feature classes were submitted by individual states/EISs and consolidated by the Wildlife Spatial Analysis Lab. They are sometimes referred to as core areas/core habitat areas in the explanations below, which were consolidated from metadata submitted with BSU feature classes. These data provide a biological tool for planning in the event of human development in sage-grouse habitats. The intended use of all data in the BLM's GIS library is to support diverse activities including planning, management, maintenance, research, and interpretation. While the BSU defines the geographic extent and scale of these two measures, how they are calculated differs based on the specific measures to reflect appropriate assessment and evaluation as supported by scientific literature.There are 10 BSUs for the Idaho and Southwestern Montana GRSG EIS sub-region. For the Idaho and Southwestern Montana Greater Sage-Grouse Plan Amendment FEIS the biologically significant unit is defined as: a geographical/spatial area within greater sage-grouse habitat that contains relevant and important habitats which is used as the basis for comparative calculations to support evaluation of changes to habitat. Idaho: BSUs include all of the Idaho Fish and Game modeled nesting and delineated winter habitat, based on 2011 inventories within Priority and/or Important Habitat Management Area (Alternative G) within a Conservation Area. There are eight BSUs for Idaho identified by Conservation Area and Habitat Management Area: Idaho Desert Conservation Area - Priority, Idaho Desert Conservation Area - Important, Idaho Mountain Valleys Conservation Area - Priority, Idaho Mountain Valleys Conservation Area - Important, Idaho Southern Conservation Area - Priority, Idaho Southern Conservation Area - Important, Idaho West Owyhee Conservation Area - Priority, and Idaho West Owyhee Conservation Area - Important. Raft River : Utah portion of the Sawtooth National Forest, 1 BSU. All of this areas was defined as Priority habitat in Alternative G. Raft River - Priority. Montana: All of the Priority Habitat Management Area. 1 BSU. SW Montana Conservation Area - Priority. Montana BSUs were revised in May 2016 by the MT State Office. They are grouped together and named by the Population in which they are located: Northern Montana, Powder River Basin, Wyoming Basin, and Yellowstone Watershed. North and South Dakota BSUs have been grouped together also. Within Colorado, a Greater Sage-Grouse GIS data set identifying Preliminary Priority Habitat (PPH) and Preliminary General Habitat (PGH) was developed by Colorado Parks and Wildlife. This data is a combination of mapped grouse occupied range, production areas, and modeled habitat (summer, winter, and breeding).PPH is defined as areas of high probability of use (summer or winter, or breeding models) within a 4 mile buffer around leks that have been active within the last 10 years. Isolated areas with low activity were designated as general habitat.PGH is defined as Greater sage-grouse Occupied Range outside of PPH.Datasets used to create PPH and PGH:Summer, winter, and breeding habitat models. Rice, M. B., T. D. Apa, B. L. Walker, M. L. Phillips, J. H. Gammonly, B. Petch, and K. Eichhoff. 2012. Analysis of regional species distribution models based on combined radio-telemetry datasets from multiple small-scale studies. Journal of Applied Ecology in review. Production Areas are defined as 4 mile buffers around leks which have been active within the last 10 years (leks active between 2002-2011). Occupied range was created by mapping efforts of the Colorado Division of Wildlife (now Colorado Parks and Wildlife –CPW) biologists and district officers during the spring of 2004, and further refined in early 2012. Occupied Habitat is defined as areas of suitable habitat known to be used by sage-grouse within the last 10 years from the date of mapping. Areas of suitable habitat contiguous with areas of known use, which do not have effective barriers to sage-grouse movement from known use areas, are mapped as occupied habitat unless specific information exists that documents the lack of sage-grouse use. Mapped from any combination of telemetry locations, sightings of sage grouse or sage grouse sign, local biological expertise, GIS analysis, or other data sources. This information was derived from field personnel. A variety of data capture techniques were used including the SmartBoard Interactive Whiteboard using stand-up, real-time digitizing atvarious scales (Cowardin, M., M. Flenner. March 2003. Maximizing Mapping Resources. GeoWorld 16(3):32-35). Update August 2012: This dataset was modified by the Bureau of Land Management as requested by CPW GIS Specialist, Karin Eichhoff. Eichhoff requested that this dataset, along with the GrSG managment zones (population range zones) dataset, be snapped to county boundaries along the UT-CO border and WY-CO border. The county boundaries dataset was provided by Karin Eichhoff. In addition, a few minor topology errors were corrected where PPH and PGH were overlapping. Update October 10, 2012: NHD water bodies greater than 100 acres were removed from GrSG habitat, as requested by Jim Cagney, BLM CO Northwest District Manager. 6 water bodies in total were removed (Hog Lake, South Delaney, Williams Fork Reservoir, North Delaney, Wolford Mountain Reservoir (2 polygons)). There were two “SwampMarsh” polygons that resulted when selecting polygons greater than 100 acres; these polygons were not included. Only polygons with the attribute “LakePond” were removed from GrSG habitat. Colorado Greater Sage Grouse managment zones based on CDOW GrSG_PopRangeZones20120609.shp. Modified and renumbered by BLM 06/09/2012. The zones were modified again by the BLM in August 2012. The BLM discovered areas where PPH and PGH were not included within the zones. Several discrepancies between the zones and PPH and PGH dataset were discovered, and were corrected by the BLM. Zones 18-21 are linkages added as zones by the BLM. In addition to these changes, the zones were adjusted along the UT-CO boundary and WY-CO boundary to be coincident with the county boundaries dataset. This was requested by Karin Eichhoff, GIS Specialist at the CPW. She provided the county boundaries dataset to the BLM. Greater sage grouse GIS data set identifying occupied, potential and vacant/unknown habitats in Colorado. The data set was created by mapping efforts of the Colorado Division of Wildlife biologist and district officers during the spring of 2004, and further refined in the winter of 2005. Occupied Habitat: Areas of suitable habitat known to be used by sage-grouse within the last 10 years from the date of mapping. Areas of suitable habitat contiguous with areas of known use, which do not have effective barriers to sage-grouse movement from known use areas, are mapped as occupied habitat unless specific information exists that documents the lack of sage-grouse use. Mapped from any combination of telemetry locations, sightings of sage grouse or sage grouse sign, local biological expertise, GIS analysis, or other data sources. Vacant or Unknown Habitat: Suitable habitat for sage-grouse that is separated (not contiguous) from occupied habitats that either: 1) Has not been adequately inventoried, or 2) Has not had documentation of grouse presence in the past 10 years Potentially Suitable Habitat: Unoccupied habitats that could be suitable for occupation of sage-grouse if practical restoration were applied. Soils or other historic information (photos, maps, reports, etc.) indicate sagebrush communities occupied these areas. As examples, these sites could include areas overtaken by pinyon-juniper invasions or converted rangelandsUpdate October 10, 2012: NHD water bodies greater than 100 acres were removed from GrSG habitat and management zones, as requested by Jim Cagney, BLM CO Northwest District Manager. 6 water bodies in total were removed (Hog Lake, South Delaney, Williams Fork Reservoir, North Delaney, Wolford Mountain Reservoir (2 polygons)). There were two “SwampMarsh” polygons that resulted when selecting polygons greater than 100 acres; these polygons were not included. Only polygons with the attribute “LakePond” were removed from GrSG habitat.California and Nevada's BSUs were developed by Nevada Department of Wildlife's Greater Sage-Grouse Wildlife Staff Specialist and Sagebrush Ecosystem Technical Team Representative in January 2015. Nevada's Biologically Significant Units (BSUs) were delineated by merging associated PMUs to provide a broader scale management option that reflects sage grouse populations at a higher scale. PMU boundarys were then modified to incorporate Core Management Areas (August 2014; Coates et al. 2014) for management purposes. (Does not include Bi-State DPS.) Oregon submitted updated BSU boundaries in May 2016, which were incorporated into this latest version. In Oregon, Core Areas were defined by the Oregon Department of Fish and Wildlife (ODFW) to be used by BLM to map Oregon PACs, Priority Areas of Conservation for the Greater Sage-grouse RMP Amendments. The data was projected to R6 Albers and will be used as is. Core Area Approach to Habitat Mitigation for Greater Sage-Grouse in Oregon: The goal of these recommendations is to protect essential habitats to meet habitat and population objectives identified in this Plan. The objective of these

The Sheeprocks (UT) was revised to resync with the UT habitat change as reflected in the Oct 2017 habitat data, creating the most up-to-date version of this dataset. Data submitted by Wyoming in February 2018 and by Montana and Oregon in May 2016 were used to update earlier versions of this feature class. The biologically significant unit (BSU) is a geographical/spatial area within Greater Sage-Grouse habitat that contains relevant and important habitats which is used as the basis for comparative calculations to support evaluation of changes to habitat. This BSU unit, or subset of this unit is used in the calculation of the anthropogenic disturbance threshold and in the adaptive management habitat trigger. BSU feature classes were submitted by individual states/EISs and consolidated by the Wildlife Spatial Analysis Lab. They are sometimes referred to as core areas/core habitat areas in the explanations below, which were consolidated from metadata submitted with BSU feature classes. These data provide a biological tool for planning in the event of human development in sage-grouse habitats. The intended use of all data in the BLM's GIS library is to support diverse activities including planning, management, maintenance, research, and interpretation. While the BSU defines the geographic extent and scale of these two measures, how they are calculated differs based on the specific measures to reflect appropriate assessment and evaluation as supported by scientific literature.There are 10 BSUs for the Idaho and Southwestern Montana GRSG EIS sub-region. For the Idaho and Southwestern Montana Greater Sage-Grouse Plan Amendment FEIS the biologically significant unit is defined as: a geographical/spatial area within greater sage-grouse habitat that contains relevant and important habitats which is used as the basis for comparative calculations to support evaluation of changes to habitat. Idaho: BSUs include all of the Idaho Fish and Game modeled nesting and delineated winter habitat, based on 2011 inventories within Priority and/or Important Habitat Management Area (Alternative G) within a Conservation Area. There are eight BSUs for Idaho identified by Conservation Area and Habitat Management Area: Idaho Desert Conservation Area - Priority, Idaho Desert Conservation Area - Important, Idaho Mountain Valleys Conservation Area - Priority, Idaho Mountain Valleys Conservation Area - Important, Idaho Southern Conservation Area - Priority, Idaho Southern Conservation Area - Important, Idaho West Owyhee Conservation Area - Priority, and Idaho West Owyhee Conservation Area - Important. Raft River : Utah portion of the Sawtooth National Forest, 1 BSU. All of this areas was defined as Priority habitat in Alternative G. Raft River - Priority. Montana: All of the Priority Habitat Management Area. 1 BSU. SW Montana Conservation Area - Priority. Montana BSUs were revised in May 2016 by the MT State Office. They are grouped together and named by the Population in which they are located: Northern Montana, Powder River Basin, Wyoming Basin, and Yellowstone Watershed. North and South Dakota BSUs have been grouped together also. California and Nevada's BSUs were developed by Nevada Department of Wildlife's Greater Sage-Grouse Wildlife Staff Specialist and Sagebrush Ecosystem Technical Team Representative in January 2015. Nevada's Biologically Significant Units (BSUs) were delineated by merging associated PMUs to provide a broader scale management option that reflects sage grouse populations at a higher scale. PMU boundarys were then modified to incorporate Core Management Areas (August 2014; Coates et al. 2014) for management purposes. (Does not include Bi-State DPS.) Within Colorado, a Greater Sage-Grouse GIS data set identifying Preliminary Priority Habitat (PPH) and Preliminary General Habitat (PGH) was developed by Colorado Parks and Wildlife. This data is a combination of mapped grouse occupied range, production areas, and modeled habitat (summer, winter, and breeding). PPH is defined as areas of high probability of use (summer or winter, or breeding models) within a 4 mile buffer around leks that have been active within the last 10 years. Isolated areas with low activity were designated as general habitat. PGH is defined as Greater sage-grouse Occupied Range outside of PPH. Datasets used to create PPH and PGH: Summer, winter, and breeding habitat models. Rice, M. B., T. D. Apa, B. L. Walker, M. L. Phillips, J. H. Gammonly, B. Petch, and K. Eichhoff. 2012. Analysis of regional species distribution models based on combined radio-telemetry datasets from multiple small-scale studies. Journal of Applied Ecology in review. Production Areas are defined as 4 mile buffers around leks which have been active within the last 10 years (leks active between 2002-2011). Occupied range was created by mapping efforts of the Colorado Division of Wildlife (now Colorado Parks and Wildlife –CPW) biologists and district officers during the spring of 2004, and further refined in early 2012. Occupied Habitat is defined as areas of suitable habitat known to be used by sage-grouse within the last 10 years from the date of mapping. Areas of suitable habitat contiguous with areas of known use, which do not have effective barriers to sage-grouse movement from known use areas, are mapped as occupied habitat unless specific information exists that documents the lack of sage-grouse use. Mapped from any combination of telemetry locations, sightings of sage grouse or sage grouse sign, local biological expertise, GIS analysis, or other data sources. This information was derived from field personnel. A variety of data capture techniques were used including the SmartBoard Interactive Whiteboard using stand-up, real-time digitizing atvarious scales (Cowardin, M., M. Flenner. March 2003. Maximizing Mapping Resources. GeoWorld 16(3):32-35). Update August 2012: This dataset was modified by the Bureau of Land Management as requested by CPW GIS Specialist, Karin Eichhoff. Eichhoff requested that this dataset, along with the GrSG managment zones (population range zones) dataset, be snapped to county boundaries along the UT-CO border and WY-CO border. The county boundaries dataset was provided by Karin Eichhoff. In addition, a few minor topology errors were corrected where PPH and PGH were overlapping. Update October 10, 2012: NHD water bodies greater than 100 acres were removed from GrSG habitat, as requested by Jim Cagney, BLM CO Northwest District Manager. 6 water bodies in total were removed (Hog Lake, South Delaney, Williams Fork Reservoir, North Delaney, Wolford Mountain Reservoir (2 polygons)). There were two “SwampMarsh” polygons that resulted when selecting polygons greater than 100 acres; these polygons were not included. Only polygons with the attribute “LakePond” were removed from GrSG habitat. Colorado Greater Sage Grouse managment zones based on CDOW GrSG_PopRangeZones20120609.shp. Modified and renumbered by BLM 06/09/2012. The zones were modified again by the BLM in August 2012. The BLM discovered areas where PPH and PGH were not included within the zones. Several discrepancies between the zones and PPH and PGH dataset were discovered, and were corrected by the BLM. Zones 18-21 are linkages added as zones by the BLM. In addition to these changes, the zones were adjusted along the UT-CO boundary and WY-CO boundary to be coincident with the county boundaries dataset. This was requested by Karin Eichhoff, GIS Specialist at the CPW. She provided the county boundaries dataset to the BLM. Greater sage grouse GIS data set identifying occupied, potential and vacant/unknown habitats in Colorado. The data set was created by mapping efforts of the Colorado Division of Wildlife biologist and district officers during the spring of 2004, and further refined in the winter of 2005. Occupied Habitat: Areas of suitable habitat known to be used by sage-grouse within the last 10 years from the date of mapping. Areas of suitable habitat contiguous with areas of known use, which do not have effective barriers to sage-grouse movement from known use areas, are mapped as occupied habitat unless specific information exists that documents the lack of sage-grouse use. Mapped from any combination of telemetry locations, sightings of sage grouse or sage grouse sign, local biological expertise, GIS analysis, or other data sources. Vacant or Unknown Habitat: Suitable habitat for sage-grouse that is separated (not contiguous) from occupied habitats that either: 1) Has not been adequately inventoried, or 2) Has not had documentation of grouse presence in the past 10 years Potentially Suitable Habitat: Unoccupied habitats that could be suitable for occupation of sage-grouse if practical restoration were applied. Soils or other historic information (photos, maps, reports, etc.) indicate sagebrush communities occupied these areas. As examples, these sites could include areas overtaken by pinyon-juniper invasions or converted rangelandsUpdate October 10, 2012: NHD water bodies greater than 100 acres were removed from GrSG habitat and management zones, as requested by Jim Cagney, BLM CO Northwest District Manager. 6 water bodies in total were removed (Hog Lake, South Delaney, Williams Fork Reservoir, North Delaney, Wolford Mountain Reservoir (2 polygons)). There were two “SwampMarsh” polygons that resulted when selecting polygons greater than 100 acres; these polygons were not included. Only polygons with the attribute “LakePond” were removed from GrSG habitat. Oregon submitted updated BSU boundaries in May 2016 and again in October 2016, which were incorporated into this latest version. In Oregon, the Core Area maps and data were developed as one component of the Conservation Strategy for sage-grouse. Specifically, these data provide a tool in planning and identifying appropriate mitigation in the event of human development in sage-grouse habitats. These maps will assist in making

Historic Fire Perimeter Dataset Feedback (arcgis.com)

Current criteria for data collection are as follows:

CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.

All cooperating agencies submit perimeters ≥10 acres.

Version update:

Firep24_1 was released in April 2025. Five hundred forty-eight fires from the 2024 fire season were added to the database (2 from BIA, 56 from BLM, 197 from CAL FIRE, 193 from Contract Counties, 27 from LRA, 8 from NPS, 55 from USFS and 8 from USFW). Six perimeters were added from the 2025 fire season (as a special case due to an unusual January fire siege). Five duplicate fires were removed, and the 2023 Sage was replaced with a more accurate perimeter. There were 900 perimeters that received updated attribution (705 removed “FIRE” from the end of Fire Name field and 148 replaced Complex IRWIN ID with Complex local incident number for COMPLEX_ID field). The following fires were identified as meeting our collection criteria but are not included in this version and will hopefully be added in a future update: Addie (2024-CACND-002119), Alpaugh (2024-CACND-001715), South (2024-CATIA-001375). One perimeter is missing containment date that will be updated in the next release.

Cross checking CALFIRS reporting for new CAL FIRE submissions to ensure accuracy with cause class was added to the compilation process. The cause class domain description for “Powerline” was updated to “Electrical Power” to be more inclusive of cause reports.

Includes separate layers filtered by criteria as follows:

California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale.

Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2020-January 2025), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.

California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-January 2025. Symbolized by decade, and display starting at country level scale.

Detailed metadata is included in the following documents:

Wildland Fire Perimeters (Firep24_1) Metadata

See more information on our Living Atlas data release here:

CAL FIRE Historical Fire Perimeters Available in ArcGIS Living Atlas

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

Historic Fire Perimeter Dataset Feedback (arcgis.com)

Current criteria for data collection are as follows:

CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.

All cooperating agencies submit perimeters ≥10 acres.

Version update:

Firep24_1 was released in April 2025. Five hundred forty-eight fires from the 2024 fire season were added to the database (2 from BIA, 56 from BLM, 197 from CAL FIRE, 193 from Contract Counties, 27 from LRA, 8 from NPS, 55 from USFS and 8 from USFW). Six perimeters were added from the 2025 fire season (as a special case due to an unusual January fire siege). Five duplicate fires were removed, and the 2023 Sage was replaced with a more accurate perimeter. There were 900 perimeters that received updated attribution (705 removed “FIRE” from the end of Fire Name field and 148 replaced Complex IRWIN ID with Complex local incident number for COMPLEX_ID field). The following fires were identified as meeting our collection criteria but are not included in this version and will hopefully be added in a future update: Addie (2024-CACND-002119), Alpaugh (2024-CACND-001715), South (2024-CATIA-001375). One perimeter is missing containment date that will be updated in the next release.

Cross checking CALFIRS reporting for new CAL FIRE submissions to ensure accuracy with cause class was added to the compilation process. The cause class domain description for “Powerline” was updated to “Electrical Power” to be more inclusive of cause reports.

Includes separate layers filtered by criteria as follows:

California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale.

Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2020-January 2025), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.

California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-January 2025. Symbolized by decade, and display starting at country level scale.

Detailed metadata is included in the following documents:

Wildland Fire Perimeters (Firep24_1) Metadata

See more information on our Living Atlas data release here:

CAL FIRE Historical Fire Perimeters Available in ArcGIS Living Atlas

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

Initial attack frequency zones are used by pilots and dispatchers for purposes of response to incidents such as wildland fires. Initial attack frequency zones are agreed upon annually by the Communications Duty Officer at the National Interagency Fire Center (NIFC), other frequency managers, and the FAA, and can't be changed during the year without required approval from the CDO at NIFC. Each zone has assigned to it FAA-issued frequencies that are to be used only within the zone boundary. The initial attack frequency zones are delineated to help ensure that frequencies used do not "bleed" over into other incident areas and causing issues for incident communications. The data contains no actual frequencies, but does contain the zones in which they are used. 01/12/2023 - Tabular changes only. Oregon Initial Attack Frequency Zones renumbered per Kim Albracht, Communications Duty Officer, with input from other Northwest personnel. Edits by JKuenzi, USFS. Changes are as follows:OR09 changed to OR02OR02 changed to OR03OR03 changed to OR04OR04 changed to OR05OR05 changed to OR07OR07 changed to OR08OR08 changed to OR09OR01 and OR06 remained unchanged.01/10/2023 - Geospatial and tabular changes made. Two islands on west side of OR05 absorbed into OR03. Change made to both Initial Attack Frequency Zones-Federal and to Dispatch Boundaries per Kaleigh Johnson (Asst Ctr Mgr), Jada Altman (Dispatch Ctr Mgr), and Jerry Messinger (Air Tactical Group Supervisor). Edits by JKuenzi, USFS. 01/09/2023 - Geospatial and tabular changes to align Federal Frequency Zones to Dispatch Area boundaries in Northwest GACC. No alignments made to USWACAC, USWAYAC, or USORWSC. Changes approved by Ted Pierce (NW Deputy Coordination Ctr Mgr), Kaleigh Johnson (Assistant Ctr Mgr), and Kim Albracht (Communications Duty Officer). Edits by JKuenzi, USFS. Specific changes include: WA02 changed to WA04. New WA02 carved out of WA01 and OR01. OR09 carved out of OR01 and OR02. Boundary adjustments between OR07, OR05, and OR03.11/8/2022 - Geospatial and tabular changes. Boundary modified between Big Horn and Rosebud Counties of MT07 and MT08 per KSorenson and KPluhar. Edits by JKuenzi, USFS. 09/06/2022-09/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada. Boundary modified between CA03 and NV03, specifically between Queen Valley and Mono Valley. The team making the changes is made up of Southern Calif (JTomaselli) and Great Basin (GDingman) GACCs, with input from Ian Mills and Lance Rosen (BLM). Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of GACC boundaries and Dispatch boundaries in the area described. Initial edits provided by Ian Mills and Daniel Yarborough. Final edits by JKuenzi, USFS. A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area.Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270.East through Bodie to the CA/NV state line.Follows the CA/NV State Line south to HWY CA 167/NV 359.East on NV359 to where the HWY intersects the corner of FS/BLM land.Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary. 09/07/2022 - 09/08/2022 - Tabular and geospatial changes. Multiple boundaries modified in Northern Rockies GACC to bring Dispatch Boundaries and Initial Attack Frequency Zone lines closer in accordance with State boundaries. Information provided by Don Copple, State Fire Planning & Intelligence Program Manager for Montana Dept of Natural Resources & Conservation (DNRC), Kathy Pipkin, Northern Rockies GACC Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi, USFS. The following changes were made:Initial Attack Frequency Zone changes made to the following: Dillon Interagency Dispatch Ctr (USMTDDC) (MT03), Helena Interagency Dispatch Ctr (USMTHDC) (MT04), Lewistown Interagency Dispatch Ctr (USMTLEC) (MT06), and Missoula Interagency Dispatch Ctr (USMTMDC) (MT02).Talk was also directed to removing the Initial Attack Frequency Zone line between MT05 and MT07, but that currently remains unchanged until Telecommunications (Kimberly Albracht) can get approval from the Frequency Managers and the FAA.10/15/2021 - Geospatial and tabular changes. Boundary alignments for the Duck Valley Reservation in southern Idaho along the Nevada border. Changes impacting ID02 and NV01. The Duck Valley Reservation remains within NV01. The only change was to the alignment of the physical boundary surrounding the Reservation in accordance with the boundary shown on the 7.5 minute quadrangle maps and data supplied by CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Center Manager. Edits by JKuenzi, USFS. 9/30/2021 - Geospatial and tabular changes. Boundary alignments for Idaho on Hwy 95 NE of Weiser between Boise Dispatch Center and Payette Interagency Dispatch Center - per CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Center Manager. Edits by JKuenzi, USFS. Boundary changes at: Weiser (T11N R5W Sec 32), (T11N, R5W, Sec 3), (T12N R5W, Sec 25), and Midvale.9/21/2021 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southwestern and Southern GACCs where a portion of Texas, formerly under Southwestern GACC direction was moved to the Southern GACC. Changes to Federal Initial Attack Frequency Zones by Kim Albracht, Communications Duty Officer (CDO) include the following: State designation TXS06 changed to federal TX06.State designation TXS05 changed to federal TX05.State designation TXS04 changed to federal TX04.State designation TXS03 changed to federal TX03.State designation TXS02 changed to federal TX02.State designation TXS01 changed to federal TX01.The Oklahoma Panhandle, formerly TXS01 changed to OK04.All changes proposed for implementation starting in January 2022. Edits by JKuenzi, USFS. See also data sets for Geographic Area Coordination Centers (GACC), and Dispatch Boundary for related changes.8/17/2021 - Tabular changes only. As part of GACC realignment for 2022, area changed from state designation TXS01 to federal TX01 per Kim Albracht, Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC). Edits by JKuenzi, USFS. 2/19/2021 - Geospatial and tabular changes. Boundary changes for Idaho originally submitted in 2016 but never completed in entirety. Changes between Initial Attack Zones ID01 and ID02 and with Dispatch Boundaries - per Chris Clay-BLM Boise, DeniseTolness-DOI/BLM ID State Office GIS Specialist, and Gina Dingman-USFS Great Basin Coordination Center (GBCC) Center Manager. Edits by JKuenzi, USFS. Boundary changes at: (T13N R3E Sec 25), (T15N R3E Sec 31), (T16N R3E Sec 18-20, and 30), and (T16N R2E Sec 13) all from ID02 to ID01. (T10N R4E Sec 4-9,17-18, 20) and (T11N R4E Sec15-16, 21-22, 27-29, 34-31) from ID01 to ID02. 11/10/2020 - Michigan split from MI01 only, to MI01(Upper Penninsula) and MI02 in the south, per Kim Albracht, Communications Duty Officer. No change made to Dispatch Zone Boundary. Edits by JKuenzi. 11/4/2020 - Oregon OR07 divided into OR07 and OR08 per Kim Albracht, Communications Duty Officer. Edits by JKuenzi.10/26/2020 - Multiple boundary changes made to Federal Initial Attack Zones, but without any change to Dispatch Zone Boundaries: Raft River District of Sawtooth National Forest changed from UT01 to ID04; land east of Black Pine District of Sawtooth National Forest changed from ID05 to ID04. Direction from Denise Tolness, DOI/BLM GIS Specialist, and Gina Dingman, Great Basin Coordination Center Manager. Parts of Craters of the Moon National Monument changed from ID04 to ID05; Sheep Mountain (Red Rocks) area changed from MT03 to ID05, per Denise Tolness, Gina Dingman, and Kathryn "Kat" Sorenson, R1 Assistant Aircraft Coordinator. Edits for all changes made by JKuenzi.4/2/2020 - State owned land added and a portion of the boundary modified between MT01 and MT02 per Mike J Gibbons, Flathead Dispatch Center Mgr, and Kathryn "Kat" Sorenson, R1 Assistant Aircraft Coordinator. Edits by JKuenzi.2/21/2020 - Existing boundaries are updated, where possible, to a uniform base layer using the August 2019 Census State & County boundaries, along with Geographic Area Command Center boundaries, Dispatch Zone Boundaries, and Initial Attack State Zones. Edits by JKuenzi.2019-2020 - Initial Attack Frequency Zone data was provided by Kim Albracht, Acting and Permanent Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC), and maintained by Jill Kuenzi, USFS Fire & Aviation Mgt Geospatial Coordinator, NIFC, Boise, ID. Efforts made to tie changes with the Initial Attack Frequency Zones to other closely related datasets such as Geospatial Area Command Centers (GACCs),and Dispatch Areas, Major work completed to bring all the datasets up to date on consistent base data (8/2019 Census data), into alignment where possible, and to establish a scheduled update cycle for the nation. 2017-2019 - Initial Attack Frequency Zone data was provided by Gary Stewart, Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC), and maintained by Jill Kuenzi, USFS Fire & Aviation Mgt Geospatial Coordinator, NIFC, Boise, ID.2015-2016 - Initial Attack Frequency Zone data was provided by Gary Stewart, Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC), and maintained by Dianna Sampson, BLM Geospatial Data Analyst, NIFC, Boise, ID.

The physical location covered by an interagency, dispatch center for the effective coordination, mobilization and demobilization of emergency management resources. A dispatch center actively supports incidents within its boundaries and the resources assigned to those incidents. 1/11/2023 - Tabular and geospatial changes. USMTBFAC (Blackfeet Reservation) merged into USMTGDC (Great Falls Interagency Dispatch Center). USMTBFAC remains as 4th Tier Dispatch. USMTFHA (Flathead Reservation) merged into USMTMDC (Missoula Interagency Dispatch Center). USMTFHA remains as 4th Tier Dispatch. Changes made by Kat Sorenson, R1 Asst Aircraft Coordinator, and Kara Stringer, IRWIN Business Lead. Edits by JKuenzi. 1/10/2023 - Tabular and geospatial changes. Two islands on west edge of John Day Dispatch area (USORJDCC) absorbed into USORCOC Dispatch per direction from Kaleigh Johnson (Asst Ctr Mgr), Jada Altman (Central Oregon Center Mgr), and Jerry Messinger (Air Tactical Group Supervisor). Update made to Dispatch and Initial Attack Frequency Zone boundaries. Edits by JKuenzi, 11/08/2022 - Tabular and geospatial changes. Update made to Dispatch and Initial Attack Frequency Zone boundaries between Miles City Interagency Dispatch Center (USMTMCC) and Billings Interagency Dispatch Center (USMTBDC), along Big Horn and Rosebud County line near Little Wolf Mountains, per Kat Sorenson, R1 Asst Aircraft Coordinator, and Kelsey Pluhar, DNRC Asst. Center Manager at Miles City Interagency Dispatch Center. Area in Big Horn County is dispatched by MTMCC. Edits by JKuenzi, 09/06/2022-09/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada. Boundary modified between CAOVCC (Owens Valley Interagency Communications Center) and NVSFC (Sierra Front Interagency Dispatch Center), specifically between Queen Valley and Mono Valley. The team making the change is made up of Southern Calif (JTomaselli) and Great Basin (GDingman) GACCs, with input from Ian Mills and Lance Rosen (BLM). Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of Initial Attack Frequency Zone boundaries and GACC boundaries in the area described. Initial edits provided by Ian Mills and Daniel Yarborough. Final edits by JKuenzi, USFS. A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area. Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270. East through Bodie to the CA/NV state line. Follows the CA/NV State Line south to HWY CA 167/NV 359. East on NV359 to where the HWY intersects the corner of FS/BLM land. Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary. 09/22/2022 - Tabular changes only. The DispLocation value of "Prineville, OR", was updated to "Redmond, OR", and the ContactPhone value was updated for Central Oregon Interagency Dispatch Ctr (USORCOC) per direction from Desraye Assali, Supervisory GIS Specialist in Region 6. The original correction had been made 9/30/2020, in the National Dispatch Office Location dataset, but had been missed in the National Dispatch Boundary dataset. Edits by JKuenzi, USFS. 09/07/2022 - 09/08/2022 - Tabular and geospatial changes. Multiple boundaries modified in Northern Rockies GACC to bring lines closer in accordance with State boundaries. Information provided by Don Copple, State Fire Planning & Intelligence Program Manager for Montana Dept of Natural Resources & Conservation (DNRC), Kathy Pipkin, Northern Rockies GACC Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi, USFS. The following changes were made:Boundary changes made to the following: Bitterroot Interagency Dispatch Ctr (USMTBDC), Dillon Interagency Dispatch Ctr (USMTDDC), Flathead Dispatch (USMTFHA), Great Falls Interagency Dispatch Ctr (USMTGDC), Helena Interagency Dispatch Ctr (USMTHDC), Kalispell Interagency Dispatch Ctr (USMTKIC), Lewistown Interagency Dispatch Ctr (USMTLEC), and Missoula Interagency Dispatch Ctr (USMTMDC).9/7/2022 - Tabular and geospatial changes. Completed change of Dispatch Boundary started 4/4/2022, USMTBZC (Bozeman Interagency Dispatch) was absorbed into USMTBDC (Billings Dispatch Center). This information for use in 2023. Change to the Initial Attack Frequency Zone Boundary will be dependent on FAA and frequency manager input which will be given by 2/28/2023. Information provided by Kathy Pipkin, Northern Rockies Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi. 07/08/2022 - Tabular change only. DispName corrected from "Columbia Cascades Communication Center" to "Columbia Cascade Communication Center" , per Desraye Assali, R6 Fire and Aviation GIS Coordinator. Edits by JKuenzi, USFS. 04/04/2022 - Tabular changes only. USCAMVIC (Monte Vista Interagency Center) changed to USCASDIC (San Diego Interagency Center). Information provided by James Tomaselli, R5 GACC Center Mgr, and Kara Stringer, Wildland Fire Data Management Business Operations Lead. Edits by JKuenzi. Tabular change only. Following discussion between NRCC (Northern Rockies Geographic Area Coordination Center), USMTBZC in Bozeman, MT, and USMTBDC in Billings, MT, plans to merge Bozeman into Billings anticipated to start 4/18/2022, but will transition throughout 2022 year and be finalized on or near January 2023. The Dispatch Boundary between USMTBZC (Bozeman Interagency Dispatch) and USMTBDC in Billings, MT, will remain in place on the map until January 2023. Tabular change made to show that MTBDC was doing dispatch duty for MTMCC. Information provided by Kathy Pipkin, Northern Rockies Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi. 03/24/2022 - Geospatial and tabular changes. Update made to 2 small polygons along the Rio Grande near a National Recreation Area and the Amistad Reservoir, which were changed from USNMADC to USTXTIC as a result of 2022 GACC Boundary change per Calvin Miller, Southern Area Coordination Center Deputy Manager, and Kenan Jaycox, Southwest Coordination Center Manager 01/05/2022 - Geospatial and tabular changes. USMTFPAC (Fort Peck Dispatch) was found to have been closed/stopped as of 03/09/2020 per WFMI (Wildland Fire Management Information) application. USMTFPAC polygon was merged into USMTLEC per USMTLEC Center Manager. Edits by JKuenzi, USFS.10/27/2021 - Geospatial and tabular changes. The area of USWASAC is merged into USWANEC per Ted Pierce, Deputy Northwest Geographic Area Coordination Center Manager, and Jill Jones, Interagency Dispatch Center Manager NE Washington Interagency Communications Center. Edits by JKuenzi, USFS.10/15/2021 - Geospatial and tabular changes. Boundary alignments for the Duck Valley Reservation in southern Idaho along the Nevada border. Changes impacting USIDBDC and USNVEIC. The Duck Valley Reservation remains under the Dispatch authority of USNVEIC. The only change was to the alignment of the physical boundary surrounding the Reservation in accordance with the boundary shown on the 7.5 minute quadrangle maps and data supplied by CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Manager. Edits by JKuenzi, USFS.9/30/2021 - Geospatial and tabular changes. Boundary alignments for Idaho on Hwy 95 NE of Weiser between Boise Dispatch Center and Payette Interagency Dispatch Center - per CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Manager. Edits by JKuenzi, USFS. Boundary changes at: Weiser (T11N R5W Sec 32), (T11N, R5W, Sec 3), (T12N R5W, Sec 25), and Midvale.9/21/2021 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southwestern and Southern GACCs where a portion of Texas, formerly under Southwestern GACC direction was moved to the Southern GACC. Changes to Dispatch Boundary include the following: Lake Meredith National Recreation Area changed from TXLAP to NMABC.Buffalo Lake NWR changed from TXBFR to NMABC.Amarillo BLM changed from TXAMD to NMABC.Muleshoe NWR changed from TXMLR to NMABC.Optima NWR changed from TXOPR to NMABC.Big Bend National Park changed from TXBBP to NMADC.Chamizal National Memorial changed from TXCHP to NMADC.Fort Davis Historic Site changed from TXFDP to NMADC.Amistad National Recreation Area changed from TXAMP to NMADC.All changes proposed for implementation starting 1/10/2022. Edits by JKuenzi, USFS. See also data sets for Geographic Area Coordination Centers (GACC), and Initial Attack Frequency Zones Federal for related changes.3/30/2021 - Geospatial and tabular changes. Boundary changes for Washington, Columbia Cascades Communication Center per Ted Pierce, acting NW GACC Deputy Center Mgr, and Justin Ashton-Sharpe, Fire Planner on the Gifford Pinchot and Mt Hood National Forests. North edge of USWACCC modified to include Mt Ranier National Park. West edge modified slightly to include more of Washington (Burke Island, Bachelor Island, Martin Island, Mt Pleasant, Green Mtn, and the eastern three quarters of Silver Lake. No changes made to Oregon side of USWACCC. Edits by JKuenzi, USFS. 2/19/2021 - Geospatial and tabular changes. Boundary changes for Alaska. Fairbanks Area Forestry Dispatch, Delta Area Forestry Dispatch, and Tok Area Forestry Dispatch merged into Northern Forestry Dispatch Center (USAKNFDC) per Jennifer L Jenkins - BLM GIS Specialist, and Ray Crowe - BLM Alaska Interagency Coordination Center (AICC) Center Manager, Dan Labarre - DNR, and Gabriella Branson - DNR. Edits by JKuenzi, USFS. 2/18/2021 - Geospatial and tabular changes. Boundary changes for Idaho originally submitted in 2016 but never completed in entirety. Changes between Boise Dispatch Center and Payette Interagency Dispatch Center - per

This feature class was derived from the GIS polygon dataset BLM Grazing Allotments which was downloaded from the Geospatial Gateway in April 2025. Fields were added to the feature classes and calculated as needed to allow the Rangeland Administration System (RAS) tabular data to be joined to the GIS datasets. RAS tabular data for Authorized allotments and pastures (as of April 2025) was provided by BLM Rangeland Management Specialist Josh Robbins in April 2025 and processed as dbfs, with fields added and calculated as needed to match the BLM GIS Grazing Allotments feature class. RAS tables and BLM GIS data for allotments were joined using the State Allotment Number, a concatenation of allotment number and BLM Administrative State for allotments (ST_ALLOT_NUM). RAS records for Authorized Allotments that did not match during a join operation were tracked in a separate excel sheet from the matching records. Matching records were then joined back to the BLM GIS Allotments grazing feature class and Allotment name fields were edited as necessary. A Status field was added to indicate if the data are either Billed or Authorized and a Source field was added to indicate that the data came from Allotments or Trailing Allotments. An additional field, TR_ALLOT_NUM, was added to designate any Trailing Allotments in the data. Trailing allotments were identified and processed separately for Nevada, since these allotments overlap portions of other allotments. Any overlaps in the data were removed via dissolve and Spatial Join.Input BLM GIS Grazing data:BLM Grazing Pastures and BLM Grazing Allotments are areas of land designated and managed for grazing of livestock. It may include private, state, and public lands under the jurisdiction of the Bureau of Land Management and/or other federal agencies. An allotment is derived from its pastures, where the grazing of livestock is occurring. The attributes of the BLM Grazing Allotment features may be duplicated in RAS, but are considered to be minimum information for unique identification and cartographic purposes.Input RAS Data:The Rangeland Administration System (RAS) provides grazing administrative support and management reports for the BLM and the public. The Rangeland Administration system serves as an electronic calendar for issuance of applications and grazing authorizations, including Permits, Leases, and Exchange-of-Use Agreements. The Authorized data is current as of April 2025 and was provided by BLM Rangeland Management Specialist Josh Robbins in April 2025.

Bathymetry is the measurement of water depth in lakes. From the 1940s to the 1990s, the Ministry of Natural Resources and Forestry produced bathymetry maps for over 11,000 lakes across Ontario. The data can be used by the general public and GIS specialists for: * climate change modelling * fish monitoring and other ecological applications * hydrologic cycle modelling * recreational fishing maps * watershed-based water budgeting The maps were created using simple methods to determine lake depths. They were meant for resource management purposes only. Little effort was made to identify shoals and other hazards when creating these bathymetric maps. Since this data was collected, many constructed and naturally occurring events could mean that the depth information is now inaccurate, so these maps should not be used for navigational purposes. In many cases, these maps still represent the only authoritative source of bathymetry data for lakes in Ontario. Technical information These maps are being converted to digital GIS line data which can be found in the Bathymetry Line data class. The Bathymetry Index data class identifies if GIS vector lines have been created and the location of mapped lakes. The historic paper maps have been scanned into digital files. We will add new digital files to this dataset if they become available. The digital files have been grouped and packaged by regions into 13 compressed (zipped) files for download. Note: package 99 contains scanned maps where the location shown on the map could not be determined.

Abstract

The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

Receptor impact models (RIMs) use inputs from surface water and groundwater models. For a given node, there is a value for each combination of hydrological response variable, future, and replicate or run number. RIMs are developed for specific landscape classes. The hydrological response variables that a RIM within a landscape class requires are organised by the R script RIM_Prediction_CreateArray.R into an array. The formatted data is available as an R data file format called RDS and can be read directly into R. The R script IMIA_XXX_RIM_predictions.R applies the receptor model functions (RDS object as part of Data set 1: Ecological expert elicitation and receptor impact models for the XXX subregion) to the HRV array for each landscape class (or landscape group) to make predictions of receptor impact varibles (RIVs). Predictions of a receptor impact from a RIM for a landscape class are summarised at relevant AUIDs by the 5th through to the 95th percentiles (in 5% increments) for baseline and CRDP futures. These are available in the XXX_RIV_quantiles_IMIA.csv data set. RIV predictions are further summarised and compared as boxplots (using the R script boxplotsbyfutureperiod.R) and as (aggregated) spatial risk maps using GIS.

Dataset History

Receptor impact models (RIMs) are developed for specific landscape classes. The hydrological response variables that a RIM within a landscape class requires are organised by the R script RIM_Prediction_CreateArray.R into an array. The formatted data is available as an R data file format called RDS and can be read directly into R.

The R script IMIA_XXX_RIM_predictions.R applies the receptor model functions (RDS object as part of Data set 1: Ecological expert elicitation and receptor impact models for the XXX subregion) to the HRV array for each landscape class (or landscape group) to make predictions of receptor impact varibles (RIVs). Predictions of a receptor impact from a RIM for a landscape class are summarised at relevant AUIDs by the 5th through to the 95th percentiles (in 5% increments) for baseline and CRDP futures. These are available in the XXX_RIV_quantiles_IMIA.csv data set. RIV predictions are further summarised and compared as boxplots (using the R script boxplotsbyfutureperiod.R) and as (aggregated) spatial risk maps using GIS.

Dataset Citation

Bioregional Assessment Programme (2018) GAL Ecological expert elicitation and receptor impact models v01. Bioregional Assessment Derived Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/60772948-7354-453c-bffa-37b3f2063083.

Dataset Ancestors

• Derived From Queensland wetland data version 3 - wetland areas.

• Derived From Geofabric Surface Cartography - V2.1

• Derived From Landscape classification of the Galilee preliminary assessment extent

• Derived From Geofabric Surface Cartography - V2.1.1

• Derived From GAL Landscape Class Reclassification for impact and risk analysis 20170601

• Derived From GEODATA TOPO 250K Series 3, File Geodatabase format (.gdb)

• Derived From Queensland groundwater dependent ecosystems

• Derived From GEODATA TOPO 250K Series 3

• Derived From Multi-resolution Valley Bottom Flatness MrVBF at three second resolution CSIRO 20000211

• Derived From Landscape classification of the Galilee preliminary assessment extent

• Derived From Biodiversity status of pre-clearing and remnant regional ecosystems - South East Qld

Please help improve this dataset by filling out this survey with feedback:Historic Fire Perimeter Dataset Feedback (arcgis.com)Current criteria for data collection are as follows:CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.All cooperating agencies submit perimeters ≥10 acres.Version update:Firep23_1 was released in May 2024. Two hundred eighty four fires from the 2023 fire season were added to the database (21 from BLM, 102 from CAL FIRE, 72 from Contract Counties, 19 from LRA, 9 from NPS, 57 from USFS and 4 from USFW). The 2020 Cottonwood fire, 2021 Lone Rock and Union fires, as well as the 2022 Lost Lake fire were added. USFW submitted a higher accuracy perimeter to replace the 2022 River perimeter. Additionally, 48 perimeters were digitized from an historical map included in a publication from Weeks, d. et al. The Utilization of El Dorado County Land. May 1934, Bulletin 572. University of California, Berkeley. Two thousand eighteen perimeters had attributes updated, the bulk of which had IRWIN IDs added. A duplicate 2020 Erbes perimeter was removed. The following fires were identified as meeting our collection criteria, but are not included in this version and will hopefully be added in the next update: Big Hill #2 (2023-CAHIA-001020). YEAR_ field changed to a short integer type. San Diego CAL FIRE UNIT_ID changed to SDU (the former code MVU is maintained in the UNIT_ID domains). COMPLEX_INCNUM renamed to COMPLEX_ID and is in process of transitioning from local incident number to the complex IRWIN ID. Perimeters managed in a complex in 2023 are added with the complex IRWIN ID. Those previously added will transition to complex IRWIN IDs in a future update.Includes separate layers filtered by criteria as follows:California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale. Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2019-2023), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-present. Symbolized by decade, and display starting at country level scale.Detailed metadata is included in the following documents:Wildland Fire Perimeters (Firep23_1) Metadata For any questions, please contact the data steward:Kim Wallin, GIS Specialist

Analysis of ‘PLACES: Census Tract Data (GIS Friendly Format), 2020 release’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/36454ff3-3bd6-4626-8607-ed62ff3f4619 on 12 February 2022.

--- Dataset description provided by original source is as follows ---

This dataset contains model-based census tract level estimates for the PLACES project 2020 release in GIS-friendly format. The PLACES project is the expansion of the original 500 Cities project and covers the entire United States—50 states and the District of Columbia (DC)—at county, place, census tract, and ZIP Code tabulation Areas (ZCTA) levels. It represents a first-of-its kind effort to release information uniformly on this large scale for local areas at 4 geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. The project was funded by the Robert Wood Johnson Foundation (RWJF) in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates include Behavioral Risk Factor Surveillance System (BRFSS) 2018 or 2017 data, Census Bureau 2010 population estimates, and American Community Survey (ACS) 2014-2018 or 2013-2017 estimates. The 2020 release uses 2018 BRFSS data for 23 measures and 2017 BRFSS data for 4 measures (high blood pressure, taking high blood pressure medication, high cholesterol, and cholesterol screening). Four measures are based on the 2017 BRFSS data because the relevant questions are only asked every other year in the BRFSS. These data can be joined with the census tract 2015 boundary file in a GIS system to produce maps for 27 measures at the census tract level. An ArcGIS Online feature service is also available at https://www.arcgis.com/home/item.html?id=8eca985039464f4d83467b8f6aeb1320 for users to make maps online or to add data to desktop GIS software.

--- Original source retains full ownership of the source dataset ---