AndreaBozzo/ceres-open-data-index huggingface dataset:
BLM AZ Travel Management Areas and Plans

Travel management is an approach to establishing networks of roads for travel and transportation including areas for both motorized and non-motorized uses. Travel management planning is necessary for designating and providing appropriate access to and across public lands for a variety of uses. Travel management plans (TMPs) and off-highway vehicle (OHV) areas are developed as part of the Land Use Planning process. Travel Management Area (TMA) polygons are used for planning purposes only and can exist without a Travel Management Plan or Resource Management Plan (RMP).
Operational Data Archive 2024

This is an export of the data archived from the 2024 National Incident Feature Service (NIFS). Sensitive fields and features have been removed. Each edit to a feature is captured in the Archive. The GDB_FROM and GDB_TO fields show the date range that the feature existed in the National Incident Feature Service. The National Incident Feature Service is based on the National Wildfire Coordinating Group (NWCG) data standard for Wildland Fire Event. The Wildland Fire Event data standard defines the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting the [NWCG Standards for Geospatial Operations (PMS 936)].
DFFM Districts

[Arizona Department of Forestry and Fire Management] ([DFFM]) Fire Division and Forestry Division [Districts] as established in 2016. The Department's mission is to manage and reduce fire risk to protect Arizona’s people, communities and wildland areas and to champion the health of Arizona natural resources. The Department provides services through strategic implementation of cooperative natural resource and fire assistance programs, development and support of statewide fire policies, and coordination of resources across all‐lands and jurisdictions. * Northern District - A1S * Northeast District - A2S * Southeast District - A3S * Central District - A4S * Northwest District - A5S DFFM Official: [https://dffm.az.gov/] DFFM District Information: [https://dffm.az.gov/about] DFFM GIS Hub: [https://gis-dffm.hub.arcgis.com/] GIS Contact: [GIS@dffm.az.gov] Disclaimer The Arizona Department of Forestry and Fire Management gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. This disclaimer applies both to the direct use of the data and any derivative products produced with the data. Any type of boundary, linear or point locations contained within this data or displayed within this product are approximate, and should not be used for authoritative or legal location purposes. Users should independently research, investigate, and verify all information to determine if the quality is appropriate for their intended purpose. If legally-defensible boundaries or locations are required, they should first be established by an appropriate state-registered professional. Per A.R.S. 37-178: A public agency that shares geospatial data of which it is the custodian is not liable for errors, inaccuracies or omissions and shall be held harmless from and against all damage, loss or liability arising from any use of geospatial data that is shared. The information contained in these data is dynamic and may change over time. It is the responsibility of the data user to use the data appropriately and consistent with the intent stated in the metadata.
Green Valley Topo from CMG Drainage

Two foot interval contour lines created by CMG Drainage as part of the 2014 Green Valley Basin Management Study. Ground surface was derived from 2008 and 2011 PAG LiDAR. Known Errors/Qualifications: Topo elevations are +- 1 foot accuracy. Spatial Domain: Eastern Pima County Maintenance Format: Shape Primary Source Organization: CMG Drainage Primary Source Date: 20141101 Primary Source Format: DWG Secondary Source Organization: RFCD Secondary Source Contact: Kenneth Maits Secondary Source Format: Shape GIS Contact: Kenneth Maits, Two foot interval contour lines created by CMG Drainage as part of the 2014 Green Valley Basin Management Study. Ground surface was derived from 2008 and 2011 PAG LiDAR. Known Errors/Qualifications: Topo elevations are +- 1 foot accuracy. Spatial Domain: Eastern Pima County Library Input: Shape Std Primary Source Organization: CMG Drainage Primary Source Date: 20141101 Primary Source Format: DWG Secondary Source Organization: RFCD Secondary Source Contact: Kenneth Maits Secondary Source Format: Shape GIS Contact: Kenneth Maits
IMSR_Incident_Locations View: Final Occurrence Year-to-Date

This layer contains "LAST" or "ONLY" incident locations for the current calendar year (year-to-date) listed in the publicly available [Incident Management Situation Reports] and provided periodically by the NICC (usually daily during fire season). This dataset is refreshed/updated in January of every year. Some delay for the current calendar year"s data may happen as the refresh takes place. The purpose of this dataset is to provide the final occurrence of the [IMSR] incident locations for the current calendar year to the present to the public in a readily accessible data download and feature service. For years, the [NICC ]maintained a large fire text file that fed a static map showing a visual representation of large fires on the IMSR. A similarly structured public facing "[IMSR Incident Locations View: Final Occurrence Historical]" dataset for the calendar years 2004 to last calendar year are available from the NIFC Open Data Site. Detailed attribute definitions and domains are provided in the "Data" tab under the "Fields" option. The NICC classifies large wildland fires as 100 acres or larger in timber and slash fuel models; 300 acres or larger in grass or brush fuel models; or when a Complex Incident Management Team is assigned. For full details on what constitutes a large fire, please refer to the [Predictive Services Mob Guide.] Currently maintained by the DOI, BLM, NOC, Fire Program. Contact BLM_OC_Fire_Geospatial@blm.gov or josterkamp@blm.gov for questions or comments.
IMSR_Incident_Locations View: Final Occurrence Historical

A filtered subset of the "LAST" or "ONLY" historical incident locations (its final occurrence) and attributes from the IMSR incident locations (points) provided by the National Interagency Coordination Center (NICC) for the published IMSR PDF documents for previous calendar years (as they become available and are appended to the data). The purpose of this dataset is to provide the final occurrence of the [IMSR] incident locations to the public discovered in calendar year 2004 to the last full calendar year in a readily accessible data download and feature service. For years, the [NICC ]maintained a large fire text file that fed a static map showing a visual representation of large fires on the IMSR. This dataset begins in calendar year 2004 and will be appended every year in January/February to incorporate the data of incidents discovered in the previous calendar year. This layer contains "LAST" or "ONLY" incident locations from May 2004 to last calendar year listed in the Incident Management Situation Reports and provided periodically by the NICC (usually daily during fire season). Detailed attribute definitions and domains are provided in the "Data" tab under the "Fields" option. The NICC classifies large wildland fires as 100 acres or larger in timber and slash fuel models; 300 acres or larger in grass or brush fuel models; or when a Complex Incident Management Team is assigned. For full details on what constitutes a large fire, please refer to the [Predictive Services Mob Guide.] Currently maintained by the DOI, BLM, NOC, Fire Program. Contact BLM_OC_Fire_Geospatial@blm.gov or josterkamp@blm.gov for questions or comments.
IMSR_Incident_Locations View: Current

A filtered subset of the most recent (current) incident locations and attributes from the IMSR incident locations (points) provided by the National Interagency Coordination Center (NICC) for their published [IMSR PDF documents]. This dataset is refreshed/updated in January of every year. Some delay for the current calendar year"s data may happen as the refresh takes place. The purpose of this dataset is to provide the current (most recent) of the [IMSR] incident locations to the public in a readily accessible data download and feature service. For years, the [NICC ]maintained a large fire text file that fed a static map showing a visual representation of large fires on the IMSR. This layer contains the current (most recent) IMSR incident locations listed in the Incident Management Situation Reports and provided periodically by the NICC (usually daily during fire season). Detailed attribute definitions and domains are provided in the "Data" tab under the "Fields" option. The NICC classifies large wildland fires as 100 acres or larger in timber and slash fuel models; 300 acres or larger in grass or brush fuel models; or when a Complex Incident Management Team is assigned. For full details on what constitutes a large fire, please refer to the [Predictive Services Mob Guide.] Currently maintained by the DOI, BLM, NOC, Fire Program. Contact BLM_OC_Fire_Geospatial@blm.gov or josterkamp@blm.gov for questions or comments.
Yavapai County Justice of the Peace Boundary

Justice of the Peace boundary polygons within Yavapai County created to share as Open Data. The boundaries for Bagdad/Yarnell, Mayer, Prescott, Seligman, Verde Valley are created when redistricting once and are not updated until the next redistricting occurs. This is being hosted on gis.yavapaiaz.gov as a feature web service is in WGS 1984 Web Mercator Auxiliary Sphere (WKID 3857). This data was intended for general location mapping purposes and is not suitable for legal, engineering, or surveying purposes. Using a Map Service to share for Open Data.
ADOT 2023 Carriageway

ADOT created the carriageway event layer to help track specific information about a rodway, including the roadway type, whether the road is divided or undivided, cardinality, direction of travel, and more. This layer is a custom layer developed specifically by ADOT and is not part of the Highway Performance Monitoring System (HPMS) federal report. However, this layer is used to help calculate values required for HPMS. IMPORTANT: The Facility Type event layer should continue to be used to identify the inventory direction of a roadway (e.g. one-way or two-way roadway). Reported Extent: All public roads.
Arizona American Community Survey 2023

This geodatabase contains statistical geographies from the U.S. Census Bureau and have had selected attributes from the 2018-2022 American Community Survey (ACS) 5-Year Estimates attached. A list of fields contained in each feature class' attribute table is also included in this geodatabase. ACS data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate is represented through the use of a margin of error (MOE). In addition to sampling variability, the ACS estimates are subject to nonsampling error. The MOE and effect of nonsampling error is not represented in these tables. Supporting documentation on subject definitions, data accuracy, and statistical testing can be found on the American Community Survey [website ]in the Data and Documentation section. Sample size and data quality measures (including coverage rates, allocation rates, and response rates) can be found on the American Community Survey [website ]in the Methodology section. The MOE for individual data elements can be found on the [Census website]. Note: Although the ACS produces population, demographic and housing unit estimates, the 2020 Census provides the official counts of the population and housing units for the nation, states, counties, cities and towns.
Projections of Population, Housing, & Employment for Maricopa and Pinal Counties, AZ, 2023

These data represent Socioeconomic Projections for the MAG Region by municipal planning area (MPA)*,adopted June 28, 2023, by the MAG Regional Council. An official set of projections is required to be used in transportation, air quality, and water quality management plans, as well as providing the base for all other regional planning activities. Current projections, therefore, are integral for managing future growth. The development of socioeconomic projections requires the collection and merging of a substantial amount of data from varying sources with differing data quality and resolution. These data include the following: * Population and Housing: American Community Survey 5-year data (2017-2021),MAG Residential Completions database, County Property Assessment data, MAG/Arizona Department of Administration (ADOA) Annual Population Estimates. * Group Quarters (Institutional and Non-institutional): MAG group quarters inventory. * Detailed Population Characteristics: American Community Survey (ACS) Public Use Microdata Sample (PUMS) - 5-year data (2017-2021). * Employment: MAG Employer Database, county level control totals developed from the Quarterly Census of Employment and Wages and Bureau of Labor Statistics (QCEW/BLS) data. * Residential Completions: Current through 2022Q4, submitted and reviewed by MAG member agencies. * Existing Land Use: Land use current as of December 2022, reviewed by MAG Population Technical Advisory Committee (POPTAC). * Built Space: Maricopa County Assessor’s data current as of July 2022. * Future Plans: General Plans current as of December 2022 or later, reviewed by MAG POPTAC. * Development Data: data current as of 2023Q2 or later, reviewed by MAG POPTAC. * TAZ system: TAZ2021b supplied by MAG Transportation Division. * Educational institutions: Inventory of schools from Arizona Department of Education and post high school institutions. * Mobile Home and RV Parks: Inventory of mobile home and RV parks. * Retirement Areas: Age restricted communities reviewed by MAG POPTAC. * Hotels/Motels/Resorts: Inventory of hotels/motels. For full documentation on the model process, please consult the Socioeconomic Projections Documentation: Data, Models, Methods, and Assumptions in the MAG Socioeconomic Projections 2023 on the MAG website at https://www.azmag.gov. These projections were adopted by the MAG Regional Council on June 28, 2023 for the MAG planning area. Areas outside of the MAG planning area are not adopted by the MAG Regional Council, but are prepared on behalf of Central Arizona Governments (CAG) and adopted separately. *Municipal planning areas are determined by the MAG member agencies in consultation with MAG staff. The MPAs identify the anticipated future corporate limits of a city or town.
Existing Land Use for Maricopa and Pinal Counties, Arizona, 2024

The Existing Land Use (EXLU) dataset represents land use in Maricopa and Pinal Counties, Arizona. This dataset was created as a joint effort of MAG and MAG member agency staff. This dataset serves as a land use inventory and is used for a variety of planning purposes including socioeconomic forecasting and air quality modeling. Because of the level of generalization involved in creating this dataset, land use boundaries may not be accurate representations of ground conditions if used at small scales.
Job Centers, 2017

Job Centers are areas of high intensity employment concentration featuring multiple large employers clustered in close proximity to each other. Job Center boundaries are defined by MAG Member Agencies, but are generally recommended to reach a threshold of at least 10 acres and at least 500 employees. The number of jobs is supplied per job center in total and by industry cluster. Total jobs include only those employers who have five or more employees per location sourced from the 2015 MAG Employer Database.
Employers Having Five or More Employees, Maricopa and Pinal Counties, Arizona, 2023

The Maricopa Association of Governments (MAG) Employer Database is a spatial database that provides the number of employees, industry, and location data for every employer within the MAG region with five or more employees. It is a joint effort between the MAG and MAG member agency staff. The Employer Database is used for a variety of planning purposes such as socioeconomic projection modeling, microeconomic analysis and other special projects. In 2012, a cluster and subcluster designation was created based on NAICS 6-digit industry codes to enable the analysis of specialty industries within Arizona. These clusters and subclusters were coded into subsequent Employer Databases for each employer. Each employer only has one cluster and subcluster classification. The clusters and subclusters are subject to change and feedback is always welcome from our member agencies. Starting with the 2016 Employer Database, with the help of MAG member agencies, we identified employers that are within key industries that we have found to be of particular interest based on input received from member agencies. The 6 key industries are aerospace, finance, healthcare, information technology, manufacturing, and warehouse/distribution. Employers may have multiple key industry classifications. Just like the clusters, sectors are subject to change, and feedback on the classifications is welcome.
Arizona Urbanized Areas, Adjusted, 2023

These data contain the Urbanized Areas (UZA) as adjusted by ADOT to include additional territory. These are created from the original Census-defined urbanized areas to smooth irregular boundaries. The smoothed boundary must encompass the entire Urbanized Area or Urban Cluster as designated by the Census, should be one contiguous area, should include areas outside of municipal boundaries that have urban characteristics with residential, commercial, industrial, or military land uses that are related to the development patterns within the boundary, and should encompass all large traffic generators that are within a reasonable distance from the urban area.
MAG Planning Area Boundary

In 1967, the original Maricopa Association of Governments (MAG) boundaries were established to encompass the urban area of Maricopa County. These initial boundaries were established primarily for transportation planning purposes to identify the area known as the “Primary Planning Area.” In 1980, the MAG Regional Council voted to expand the boundaries of MAG to include all of Maricopa County. In 2002, the MAG Regional Council voted to extend the MAG membership to local governments in the contiguous urbanized areas. In 2013, the MAG Planning Area Boundary was expanded due to the 2010 Census urbanized area boundary updates. For transportation planning and programming purposes, the Federal Highway Administration (FHWA) states that the Metropolitan Planning Area must encompass the entire urbanized area boundary as well as the contiguous geographic area(s) likely to become urbanized within the next 20 years. The updated urbanized area boundary for the MAG region included areas within Pinal County.
Vote Precincts '22-'23

The Vote Precincts '22-'23 dataset outlines the official electoral precinct boundaries within Navajo County, Arizona, during the designated period. These precincts played a vital role in voter registration, election planning, and jurisdictional organization, ensuring structured electoral processes within the county. This dataset serves as a reference for government agencies, election officials, researchers, and public users, supporting efforts in electoral analysis, precinct management, and historical election data tracking. It is designed for public accessibility, offering a clear and accurate representation of precinct boundaries as they existed during the 2022-2023 election cycle.
TrafficReportingLayers

Traffic sections define segments of roadway where traffic volume is homogeneous along each segment length, and the specific breakpoints where traffic volumes change. This segmentation of the roadway network is necessary for the assignment of point level traffic count information to GIS roadway segments and serve to support HPMS annual reporting and other planning purposes. The relationship between traffic count stations and traffic sections is defined in the traffic sections, and this link is critical in the creation, management, and use of all network traffic statistics and information. The spatial location of each traffic section and station is defined in ADOT’s GIS linear reference system. Traffic counts are generally collected at a single point along a section of roadway, and are commonly referred to as Count Locations, Sites, or Stations.Ideally, counts are taken at the same location (or nearby) periodically. The MS2 Traffic Count Database System (TCDS) allows traffic collection agencies to create or contribute to a database of traffic data, including count locations. ADOT also maintains a database of traffic count stations, which is reconciled with the TCDS. Traffic Count Stations are assigned to a Traffic Section through the Traffic Section ID. The Station"s ID can also be used in the calculation of traffic statistics for that Traffic Section, which is how it is utilized in analysis and reporting (such as HPMS).
Arizona Imagery 2021 (NAIP)

The National Agriculture Imagery Program (NAIP) is a federal program which acquires aerial imagery during the agricultural growing seasons in the continental U.S. A primary goal of the NAIP program is to make digital ortho photography available to governmental agencies and the public within a year of acquisition. NAIP projects are contracted each year based upon available funding and the FSA imagery acquisition cycle. Beginning in 2003, NAIP was acquired on a 5-year cycle. 2008 was a transition year, and a three-year cycle began in 2009. Use the following link for an interactive status map of NAIP acquisitions from 2002 - 2023: https://www.fsa.usda.gov/programs-and-services/aerial-photography/imagery-programs/naip-imagery/ NAIP is administered by the USDA's Farm Service Agency (FSA) through the Aerial Photography Field Office in Salt Lake City. This "leaf-on" imagery is used as a base layer for GIS programs in FSA's County Service Centers, and is used to maintain the Common Land Unit (CLU) boundaries.