AndreaBozzo/ceres-open-data-index huggingface dataset:
US 14-digit Hus

This file contains Hydrologic Unit (HU) polygon boundaries for the United States, Puerto Rico, and the U.S. Virgin Islands. The data is a seamless National representation of HU boundaries from 2 to 14 digits compiled from U.S. Geological Survey (USGS) National Hydrography Dataset (NHD) and U.S. Department of Agriculture (USDA) National Resources Conservation Service (NRCS) Watershed Boundary Dataset (WBD) sources
Streams _ Ephemeral and Perennial

Converted in the fall of 1988 from USGS 1:100,000 scale DLG data to ARC format. Since then, multiple and extensive corrections have taken place. Early on, several Arizona agencies were part of rectification including: attributes, features, edgematching and the re-tiling of the data into the USGS Hydrologic Unit Code (HUC) library tiling format. The Environmental Protection Agency (EPA) has since added critical attributes to the Arizona database, including: A nationally recognized management link code (the Reach Id), names, and hydrologic information. Arizona has enhanced the theme further by adding ergonomic Descriptive Attribute Codes, Cartographic Order, more Names, and intense Quality Assurance Controls.
Riparian Vegetation

This dataset was developed at the Arizona Game & Fish Department in 1993-1994. It identifies riparian vegetation associated with perennial waters mapped in response to the requirements of the Waters - Riparian Protection Program (Laws 1992, CH. 298). Maps were created using two major sources of imagery - Landsat Thematic Mapper digital satellite data and Multiple Resolution Aerial Videography. The dataset was distributed in June 1994. The data are created to serve as base information for use in GIS systems for a variety of planning and analysis purposes. These data do not represent a legal record.
US Zip Code Tabulation Areas - 2000

Zip Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) five-digit Zip Code service areas that the Census Bureau creates using whole blocks to present statistical data from censuses and surveys. The Census Bureau defines Zip Code Tabulation Areas by allocating each block that contains addresses to a single Code Tabulation Areas, usually to the ZCTA that reflects the most frequently occurring Zip Code for the addresses within that tabulation block. Blocks that do not contain addresses but are completely surrounded by a single Code Tabulation Areas (enclaves) are assigned to the surrounding ZCTA; those surrounded by multiple ZCTAs will be added to a single ZCTA based on limited buffering performed between multiple ZCTAs. The Census Bureau identifies five-digit Code Tabulation Areas using a five-character numeric code that represents the most frequently occurring USPS Zip Code within that ZCTA, and this code may contain leading zeros.
US State Boundaries - 2010

The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and census areas; the latter of which are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. All of the counties in Connecticut and Rhode Island and nine counties in Massachusetts were dissolved as functioning governmental entities; however, the Census Bureau continues to present data for these historical entities in order to provide comparable geographic units at the county level of the geographic hierarchy for these states and represents them as nonfunctioning legal entities in data products. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands.
Arizona Municipal and Fire District Annexations

This annexation data set is maintained by the Arizona Department of Revenue (AZDOR) to pinpoint where tax area code changes are happening. In almost all cases a tax area code change is associated with an annexation. By law Centrally Valued Property (CVP) taxpayers (utility companies) are mandated to report their property to AZDOR using tax area codes. By law AZDOR is required to notify CVP taxpayers regarding tax area code changes; thus the main reason why we map annexations. You can differentiate between city & fire district annexations by looking at the field 'AnnexType'. If the attribute in this field is 'CI' then it's a city annexation. If the attribute is 'FD' then it's a fire district annexation.
Operational Data Archive 2023

This is an export of the data archived from the 2023 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)].
Operational Data Archive 2023

This is an export of the data archived from the 2023 National Incident Feature Service. 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)].
BLM AZ Grazing Allotments and Pastures

This dataset is a multi-purpose data set that aids in the administration of grazing allotments under the AZ Bureau of Land Management (BLM) grazing program, and also in scientific, integrated land use planning or other activities that would affect, or be affected by, livestock grazing. An allotment is an area 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.
BLM AZ Surface Management Agency

The purpose of this dataset is to fulfill the public and Government’s need to know which agency is managing Federal land in a given area. For example, there may be a need to know what agency is managing a certain tract of land for the purpose of paying permit fees, obtaining licenses, or becoming informed about current laws, regulations, and restrictions governing access to and use of the land. This dataset serves as a tool to determine and illustrate the boundaries of a particular Federal agency’s “managing” area and to quantify these areas in terms of geographic acreage. These data are public information and may be used by various organizations, agencies, units of government (i.e., Federal, state, county, and city), and other entities. The geographic acreages contained in this dataset are not derived from legal documents associated with title documents or survey records. Rather, they are computed by mathematical programs and are described in detail in the supplemental section of the definition document referenced at the end of this section. The data can be used for small scale (1:24,000 and smaller) analysis and cartographic products. SMA was originally derived from the land dataset produced by the Arizona State Land Dept (ASLD), and the Arizona Land Resource Information System (ALRIS). The land dataset was initiated in 1984 and updated in the spring of 1988 by the State Land Department Forestry Division and ALRIS. The data was then projected into ARC/INFO format and edited using the procedures from the ASLD Land Status Map Digitizing Procedure guide. The land dataset covers the entire State of Arizona and includes surface management, public land survey system (PLSS) provided by the Department of Transportation (ADOT), and county and state boundaries.
BLM AZ Wild Horse and Burro Herd Areas and Herd Management Areas

The Wild Horse and Burro (WHB) Program manages Bureau of Land Management land designated as Herd Areas (HA) and Herd Management Area (HMA) as well as the horses, burros, and mules that roam on BLM land. These animals are considered cultural resources by law; therefore, the BLM must manage the animals that roam as a resource. The WHB Program also manages the data and tracks the animals on some land managed by other agencies under agreements with those agencies (e.g. Forest Service Herd Territories). Animal management includes monitoring the wild herds and their habitat, as well as removing some of the animals from the wild, caring for them, and finding responsible owners for them through adoptions and sales. Federal lands managed for wild horses and burros are called Herd Management Areas (HMAs). All HMAs need to be contained within an originally designated Herd Area (HA). Management status can change based on changing conditions. Specific laws and regulations pertaining to the management of wild horses and burros are applied. The BLM uses the term Herd Management Area; the Forest Service uses the term Wild Horse Territory.
BLM AZ Recreation Sites

This dataset includes point and polygons representing recreation sites located within the Bureau of Land Management (BLM) Arizona. The general types of recreation sites targeted by this dataset include information center sites, water-based sites, overnight sites, day use sites, restrooms, water access, recreational access, parking areas, airplane landing strips, campgrounds, off-highway vehicle (OHV) designated areas, recreation management areas and zones, and natural/endangered areas, etc.
Protected Lands of Pima County

[https://gis.pima.gov/data/contents/metadet.cfm?name=preserve] Values for PropInterest field (pop-ups & file downloads): 1 = Agricultural Lease; 2 = Conservation Easement; 3 = Federal Lands; 4 = Fee Simple; 5 = Fee Simple w/ Reversionary Clause; 6 = Grazing Lease; 7 = Perpetual ROW; 8 = Restricted Covenant; 9 = Rezoning Condition; 10 = Section 7/10 Mitigation; 11 = State Lands; 12 = Use Agreement w/ BLM Values for RestrictType field (pop-ups & file downloads): 1 = MRC: Conservation Land; 2 = MRC: MSCP; 3 = RC; 4 = Conservation Easement; 5 = N/A
BLM AZ Public Land Survey System CadNSDI

This dataset is part of the Cadastral National Spatial Data Infrastructure (CadNSDI) publication dataset for rectangular and non­‐rectangular Public Land Survey System (PLSS) data. This dataset represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non-rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-­‐ Attribute section of this metadata describes these components in greater detail. The CadNSDI or the Cadastral Publication Data Standard is the cadastral data component of the NSDI. This is the publication guideline for cadastral data that is intended to provide a common format and structure and content for cadastral information that can be made available across jurisdictional boundaries, providing a consistent and uniform cadastral data to meet business need that includes connections to the source information from the data stewards. The data stewards determine which data are published and should be contacted for any questions on data content or for additional information. The cadastral publication data is data provided by cadastral data producers in a standard form on a regular basis. Cadastral publication data has two primary components, land parcel data and cadastral reference data. It is important to recognize that the publication data are not the same as the operation and maintenance or production data. The production data is structured to optimize maintenance processes, is integrated with internal agency operations and contains much more detail than the publication data. The publication data is a subset of the more complete production data and is reformatted to meet a national standard so data can be integrated across jurisdictional boundaries and be presented in a consistent and standard form nationally.
Historic Perimeters Combined 2000-2018 GeoMAC

The Geospatial Multi-Agency Coordination Group, or GeoMAC, is an internet-based mapping tool originally designed for fire managers to access online maps of current fire locations and perimeters in the US. Perimeters are submitted to GeoMAC by field offices. The GeoMAC team attributes the perimeters using various sources, and then posts them on the GeoMAC website and to an HTTP site for downloading. This file contains all the latest fire perimeters that were processed by the GeoMAC team between 2000 and 2018. The projection is geographic and the datum is NAD83.
ADOT 2023 Junctions and Junction Legs

Locations of at-grade intersections, restricted crossovers on divided highways, and termini points for specific routes. This layer is used when identifying the number and type of intersection signals or stop signs as part of the Highway Performance Monitoring System (HPMS) federal report submittal (refer to the [HPMS field manual, items 31-33]). This layer is also used in statewide safety scoring and has been adjusted for MIRE requirements. Junction legs are 150 foot linear segments, or legs, on either side of a road intersection, or junction. They are used to support traffic safety analysis. Reported Extent: All paved public roads where an at-grade junction/intersection exists
ADOT 2023 National Highway System (NHS)

This dataset represents the roadway sections that comprise the Arizona portion of the National Highway System (NHS), as reported in the 2023 Highway Performance Monitoring System (HPMS) federal report. The NHS is designated by the Federal Highway Administration (FHWA) and consists of roadways important to the nation’s economy, defense, and mobility and include interstates, Strategic Highway Network (STRAHNET) routes and connectors, and other roads that connect major multimodal transportation hubs, such as airports, ports of entry, railroad stations, and other major transportation and business features. For more information, refer to the [ADOT Glossary - NHS page]. Reported Extent: All applicable roadways
ADOT 2023 Functional Classification

Federal Functional Classification (FFC) defines the level of service of a road to the state roadway system and is an integral part of the annual Highway Performance Monitoring System (HPMS) federal report. FFC allows state and local government agencies to classify roadways based on function, destination, design, context, topology, and quantitative mileage and essentially represents the overall importance of a roadway. FFC is especially important for determining federal funding distribution as only urban roads classified as minor collectors or above (FFC 1-6) and rural roads classified as major collectors or above (FFC 1-5) are eligible for federal aid. These roads are collectively known as the Federal Aid Network. The ADOT Functional Class layer categorizes roads into nineteen (19) different classifications, including interstates, freeways, other principal arterials, minor arterials, major collectors, minor collectors, and local roads, each separated by an urban or rural designation based on their location according to the [2013 adjusted urban area boundary]. The adjusted urban area boundary is an expansion of the 2010 urban areas identified by the U.S. Census Bureau but adjusted to suite transportation planning needs. Every public road in the state must be classified under one of these classes. IMPORTANT: The Federal Highway Administration (FHWA) uses a new seven-class system, referred to as Functional System, that removes the urban and rural separation. Before submitting their HPMS report, ADOT converts the functional classification codes (1-19) to FHWA function system codes (1-7). Refer to [Coding Changes] to learn more about the conversion. To read more about functional classification, review the [ADOT Functional Classification website]. Reported Extent: All federal-aid eligible roads, including ramps and frontage roads, and optional for all other roads. Federal aid-eligible roads include urban roads classified as minor collectors or above (functional system 1-6) and rural roads classified as major collectors or above (function system 1-5).
ADOT 2023 Pavement Conditions

The annual Highway Performance Monitoring System (HPMS) federal report requires states to collect data on pavement conditions on all state owned roads (i.e. the State Highway System) and a sample of additional roads selected by the Federal Highway Administration (FHWA), also known as sample panels. Each year, ADOT contracts vans equipped to measure the amount of cracking, faulting, rutting, and roughness across all required roadways. Per HPMS requirements, these data are summarized and reported in tenth of a mile sections, known as HPMS bins. In addition to reporting specific pavement conditions, ADOT also calculates the overall condition of the pavement within each bin and reports it on a good, fair, or poor rating scale. For more information about HPMS pavement collection and bin requirements, refer to the [HPMS Field Manual, Item 47 IRI] under the Guidance section. To learn more about how ADOT collects pavement condition data, refer to the storymap [Pavement Data: An Overview]. Reported Extent: State Highway System (i.e. all ADOT-owned roads) and all sample panel roads. Sample panel sections are any roadways, or parts of roadways, that were identified by the Federal Highway Administration (FHWA) as requiring additional data to be reported in the 2023 HPMS report.
ADOT 2023 Through Lanes

The number of through lanes on a roadway, which are lanes pass through at least two intersections and do not taper or turn into a turn lane. This event layer also includes the average lane width for the through lanes. To learn more about through lanes, refer to the [ADOT Glossary - Lanes] webpage. For undivided highways, where there is no physical barrier between opposing lanes of traffic, through lanes represent the total number of lanes on both sides of the road. For example, if there are 2 through lanes on the cardinal side of the road and 2 lanes on the non-cardinal side of the road, the number of through lanes reported is 4. Note, cardinality refers to the direction of increasing mileposts. For roadways that have no striping, such as in residential neighborhoods, the number of through lanes is reported as 2. For divided highways, through lanes are reported for the individual roadway. For example, if there are 2 through lanes on the cardinal highway, the value is reported as 2. Important: Many roadways have estimated values for the number of lanes and average lane widths. These values were based on the functional system of the road and the area characteristics. Reported Extent: All roads eligible for federal aid, including ramps, and optional for other roadways. Federal aid-eligible roads include urban roads classified as minor collectors or above (functional system 1-6) and rural roads classified as major collectors or above (function system 1-5).
Adjudicated Subwatersheds

Adjudications in Arizona are based on surface watersheds defined by the Adjudication Court, not to be confused with watersheds defined by ADWR (see LIB.surface_watershed_adj). This feature class displays the breakdown of adjudicated subwatersheds. This layer is based on the original (LIB.surfaceSubwatershedADJ) layer, but was adapted to better fit the USGS' HUC 6/8 boundaries where applicable. Please note that boundaries for the the San Pedro River, Silver Creek, and Verde River Watersheds/Subwatersheds differ from HUC boundaries. This was done to preserve boundaries to match existing reports. Also please note that although Aubrey Valley is included within the Verde River WS boundary it is not part of the Adjudication. Last revision date: November 7,2024.
ADOT 2023 All Roads Network

The Arizona Transportation Information System (ATIS), also referred to as the All Roads Network, is a spatial file that represents the centerlines of all roads in Arizona. All roads open to public travel are included but the file may also include administrative (i.e. service) roads, private roads, and other roads restricted from the public. This layer is submitted in the annual Highway Performance Monitoring System (HPMS) federal report in the All Roads Network of Linear Data (ARNOLD) spatial dataset. All event layers describing road designations and attributes, such as functional system and speed limit, refer to ATIS to identify the route ID and measure locations for the features on the road network. Reported Extent: All roads in Arizona
Operational Data Archive 2024

This is an export of the data archived from the 2024 National Incident Feature Service. 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)].