The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.Download the National Hydrography Dataset file geodatabase v2.2.1.

A Land Use Planning Area is defined as the geographic area within which the BLM will make decisions during a planning effort. A planning area boundary includes all lands regardless of jurisdiction; however, the BLM will only make decisions on lands that fall under the BLM’s jurisdiction (including subsurface minerals). Unless the State Director determines otherwise, the planning area for a RMP is the geographic area associated with a particular field office (43 CFR 1610.1(b)). State Directors may also establish regional planning areas that encompass several field offices and/or states, as necessary. Page 14 of the BLM Planning Handbook.

The geospatial data reflected in the protected area layer mostly pertain to natural and wilderness areas where development of utility-scale renewable energy is prohibited and were heavily based on RETI 1.0 blackout areas.1 The protected area layer is distinguished for solar PV technology by the BLM greater sage grouse habitat management area which provides separate exclusion areas for the different technology types. Tables 1 and 2 below lists the data sources and precise selection query for each dataset, if applicable, that make up the protected area layer.Table 1: Datasets used in the Protected Area Layer

Dataset

Example Designations

Citation or hyperlink

PAD-US (CBI Edition)

National Parks, GAP Status 1 and 2, State Parks, Open Spaces, Natural Areas

“PAD-US (CBI Edition) Version 2.1b, California”. Conservation Biology Institute. 2016. https://databasin.org/datasets/64538491f43e42ba83e26b849f2cad28.

Conservation Easements

California Conservation Easement Database (CCED), 2022a. 2022. www.CALands.org. Accessed December 2022.

Inventoried Roadless Areas

“Inventoried Roadless Areas.” US Forest Service. Dec 12, 2022. https://www.fs.usda.gov/detail/roadless/2001roadlessrule/maps/?cid=stelprdb5382437

BLM National Landscape Conservation System

Wilderness Areas, Wilderness Study Areas, National Monuments, National Conservation Lands, Conservation Lands of the California Desert, Scenic Rivers

https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-areas

https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-study-areas

https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-national-monuments-nca-forest-reserves-other-poly/

Greater Sage Grouse Habitat Conservation Areas (BLM)

For solar technology: BLM_Managm IN (‘PHMA’, ‘GHMA’, ‘OHMA’) For wind technology: BLMP_Managm = ‘PHMA’

“Nevada and Northeastern California Greater Sage-Grouse Approved Resource Management Plan Amendment.” US Department of the Interior Bureau of Land Management Nevada State Office. 2015. https://eplanning.blm.gov/public_projects/lup/103343/143707/176908/NVCA_Approved_RMP_Amendment.pdf

Other BLM Protected Areas

Areas of Critical Environmental Concern (ACECs), Recreation Areas (SRMA, ERMA, OHV Designated Areas), including Vinagre Wash Special Recreation Management Area, National Scenic Areas, including Alabama Hills National Scenic Area

https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-off-highway-vehicle-designations

https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-areas-of-critical-environmental-concern

BLM, personal communication, November 2, 2022.

Mono Basin NFSA

https://pcta.maps.arcgis.com/home/item.html?id=cf1495f8e09940989995c06f9e290f6b#overview

Terrestrial 30x30 Conserved Areas

Gap Status 1 and 2

CA Nature. 30x30 Conserved Areas, Terrestrial. 2021. https://www.californianature.ca.gov/datasets/CAnature::30x30-conserved-areas-terrestrial/ Accessed September 2022.

CPAD

Open Spaces and Parks under city or county level

California Protected Areas Database (CPAD), 2022b. 2022. https://www.calands.org/cpad/. Accessed February 22, 2023.

USFS Special Interest Management Areas

Research Natural Areas, Recreation Areas, National Recreational Trail, Experimental Forest, Scenic Area

https://data-usfs.hub.arcgis.com/datasets/usfs::special-interest-management-areas-feature-layer/about

Proposed Protected Area

Molok Luyuk Extension (Berryessa Mtn NM Expansion)

CalWild, personal communication, January 19, 2023.

Table 2: Query Definition for Components of Protected Areas Dataset SQL Query PAD-US (CBI Edition) p_des_tp IN ('Wild, Scenic and Recreation River', 'Area of Critical Environmental Concern', 'Ecological Reserve', 'National Conservation Area', 'National Historic Site', 'National Historical Park', 'National Monument', 'National Park General Public Land', 'National Preserve', 'National Recreation Area', 'National Scenic Area', 'National Seashore', 'Wilderness Study Area', 'Wilderness Area', 'Wildlife Management Area', 'State Wildlife Management Area', 'State Park', 'State Recreation Area', 'State Nature Preserve/Reserve', 'State Natural Area', 'State Ecological Reserve', 'State Cultural/Historic Area', 'State Beach', 'Special Management Area', 'National Wildlife Refuge', 'Natural Area', 'Nature Preserve', 'Research Natural Area') Or s_des_tp IN ('Natioanal Monument', 'National Monument', 'National Park General Public Land', 'National Preserve', 'National Recreation Area', 'National Scenic Area', 'National Seashore', 'National Conservation Area', 'Area of Critical Environmental Concern', 'National Wildlife Refuge', 'State Park', 'State Wildlife Area', 'State Wildlife Management Area', 'State Wildlife Refuge', 'State Ecological Reserve', 'Wild, Scenic and Recreation River', 'Wilderness Area', 'Wildlife Management Area') Or t_des_tp IN ('National Monument', 'National Park General Public Land', 'National Recreation Area', 'Area of Critical Environmental Concern', 'National Conservation Area', 'State Wildlife Management Area', 'Wild, Scenic and Recreation River', 'Wildlife Management Area') Or p_loc_ds IN ('Ecological Reserve', 'Research and Educational Land') Or gap_sts IN ('1', '2') Or own_type = 'Private Conservation Land' Or (own_type = 'Local Land' And (p_des_tp LIKE '%"Open Space"%' Or p_des_tp LIKE '%Park%' Or p_des_tp LIKE '%Recreation Area%' Or p_des_tp LIKE '%Natural Area%')) Or (p_des_tp = 'Other State Land' And (p_loc_ds IN ('State Vehicular Recreation Area', 'BLM Resource Management Area', 'Resource Management Area') And gap_sts <> '2')) CPAD AGNCY_LEV IN ('City', 'County') And ACCESS_TYP = 'Open Access' And (UNIT_NAME LIKE '%Park%' OR UNIT_NAME LIKE '%Open Space%' OR UNIT_NAME LIKE '%park%' OR UNIT_NAME LIKE '%Recreation Area%' OR UNIT_NAME LIKE '%Natural Area%' OR GAP2_acres > 0 OR GAP1_acres >0) Greater Sage- Grouse Habitat Conservation Areas (BLM) For Solar Technology: BLM_Managm IN (‘PHMA’, ‘GHMA’, ‘OHMA’) For Wind Technology: BLM_Managm = ‘PHMA’ This layer is featured in the CEC 2023 Land-Use Screens for Electric System Planning data viewer.For a complete description of the creation of this layer and its use in electric system planning, please refer to the Land Use Screens Staff Report in the CEC Energy Planning Library.[1] Final RETI Phase 2A report, available at https://ww2.energy.ca.gov/2009publications/RETI-1000-2009-001/RETI-1000-2009-001-F-REV2.PDF.

Change Log: Version 1.1 (January 22, 2024 10:29 AM) Layer revised to allow for gaps to remain when combining all components of the protected area layer.

"Due to the size of this dataset, both Shapefile and Spreadsheet download options will not work as expected. The File Geodatabase is an alternative option for this data download"This is SCAG's 2019 Annual Land Use (ALU v. 2019.1) at the parcel-level, updated as of February 2021. This dataset has been modified to include additional attributes in order to feed SCAG's Housing Element Parcel Tool (HELPR), version 2.0. The dataset will be further reviewed and updated as additional information is released. Please refer to the tables below for data dictionary and SCAG’s land use classification.Field NameData TypeField DescriptionPID19Text2019 SCAG’s parcel unique IDAPN19Text2019 Assessor’s parcel numberCOUNTYTextCounty name (based on 2016 county boundary)COUNTY_IDDoubleCounty FIPS code (based on 2016 county boundary)CITYTextCity name (based on 2016 city boundary)CITY_IDDoubleCity FIPS code (based on 2016 city boundary)MULTIPARTShort IntegerMultipart feature (the number of multiple polygons; '1' = singlepart feature)STACKLong IntegerDuplicate geometry (the number of duplicate polygons; '0' = no duplicate polygons)ACRESDoubleParcel area (in acreage)GEOID20Text2020 Census Block Group GEOIDSLOPEShort IntegerSlope information1APN_DUPLong IntegerDuplicate APN (the number of multiple tax roll property records; '0' = no duplicate APN)IL_RATIODoubleRatio of improvement assessed value to land assessed valueLU19Text2019 existing land useLU19_SRCTextSource of 2019 existing land use2SCAGUID16Text2016 SCAG’s parcel unique IDAPNText2016 Assessor’s parcel numberCITY_GP_COText2016 Jurisdiction’s general plan land use designationSCAG_GP_COText2016 SCAG general plan land use codeSP_INDEXShort IntegerSpecific plan index ('0' = outside specific plan area; '1' = inside specific plan area)CITY_SP_COText2016 Jurisdiction’s specific plan land use designationSCAG_SP_COText2016 SCAG specific plan land use codeCITY_ZN_COText2016 Jurisdiction’s zoning codeSCAG_ZN_COText2016 SCAG zoning codeLU16Text2016 existing land useYEARLong IntegerDataset yearPUB_OWNShort IntegerPublic-owned land index ('1' = owned by public agency)PUB_NAMETextName of public agencyPUB_TYPETextType of public agency3BF_SQFTDoubleBuilding footprint area (in square feet)4BSF_NAMETextName of brownfield/superfund site5BSF_TYPETextType of brownfield/superfund site5FIREShort IntegerParcel intersects CalFire Very High Hazard Local Responsibility Areas or State Responsibility Areas (November 2020 version) (CalFIRE)SEARISE36Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)1 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)SEARISE72Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)2 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)FLOODShort IntegerParcel intersects with a FEMA 100 Year Flood Plain data from the Digital Flood Insurance Rate Map (DFIRM), obtained from Federal Emergency Management Agency (FEMA) in August 10, 2017EQUAKEShort IntegerParcel intersects with an Alquist-Priolo Earthquake Fault Zone (California Geological Survey; 2018)LIQUAFAShort IntegerParcel intersects with a Liquefaction Susceptibility Zone (California Geological Survey; 2016)LANDSLIDEShort IntegerParcel intersects with a Landslide Hazard Zone (California Geological Survey; 2016)CPADShort IntegerParcel intersects with a protected area from the California Protected Areas Database(CPAD) – www.calands.org (accessed April 2021)RIPARIANShort IntegerParcel centroid falls within Active River Areas(2010)or parcel intersects with a Wetland Area in the National Wetland Inventory(Version 2)WILDLIFEShort IntegerParcel intersects with wildlife habitat (US Fish & Wildlife ServiceCritical Habitat, Southern California Missing Linkages, Natural Lands & Habitat Corridors from Connect SoCal, CEHC Essential Connectivity Areas,Critical Coastal Habitats)CNDDBShort IntegerThe California Natural Diversity Database (CNDDB)includes the status and locations of rare plants and animals in California. Parcels that overlap locations of rare plants and animals in California from the California Natural Diversity Database (CNDDB)have a greater likelihood of encountering special status plants and animals on the property, potentially leading to further legal requirements to allow development (California Department of Fish and Wildlife). Data accessed in October 2020.HCPRAShort IntegerParcel intersects Natural Community & Habitat Conservation Plans Reserve Designs from the Western Riverside MHSCP, Coachella Valley MHSCP, and the Orange County Central Coastal NCCP/HCP, as accessed in October 2020WETLANDShort IntegerParcel intersects a wetland or deepwater habitat as defined by the US Fish & Wildlife Service National Wetlands Inventory, Version 2.UAZShort IntegerParcel centroid lies within a Caltrans Adjusted Urbanized AreasUNBUILT_SFDoubleDifference between parcel area and building footprint area expressed in square feet.6GRCRY_1MIShort IntegerThe number of grocery stores within a 1-mile drive7HEALTH_1MIShort IntegerThe number of healthcare facilities within a 1-mile drive7OPENSP_1MIShort IntegerQuantity of open space (roughly corresponding to city blocks’ worth) within a 1-mile drive7TCAC_2021TextThe opportunity level based on the 2021 CA HCD/TCAC opportunity scores.HQTA45Short IntegerField takes a value of 1 if parcel centroid lies within a 2045 High-Quality Transit Area (HQTA)JOB_CTRShort IntegerField takes a value of 1 if parcel centroid lies within a job centerNMAShort IntegerField takes a value of 1 if parcel centroid lies within a neighborhood mobility area.ABS_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within an absolute constraint area. See the Sustainable Communities Strategy Technical Reportfor details.VAR_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within a variable constraint area. See the Sustainable Communities Strategy Technical Reportfor details.EJAShort IntegerField takes a value of 1 if parcel centroid lies within an Environmental Justice Area. See the Environmental Justice Technical Reportfor details.SB535Short IntegerField takes a value of 1 if parcel centroid lies within an SB535 Disadvantaged Community area. See the Environmental Justice Technical Reportfor details.COCShort IntegerField takes a value of 1 if parcel centroid lies within a Community of Concern See the Environmental Justice Technical Reportfor details.STATEShort IntegerThis field is a rudimentary estimate of which parcels have adequate physical space to accommodate a typical detached Accessory Dwelling Unit (ADU)8.SBShort IntegerIndex of ADU eligibility according to the setback reduction policy scenario (from 4 to 2 feet) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SMShort IntegerIndex of ADU eligibility according to the small ADU policy scenario (from 800 to 600 square feet ADU) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)PKShort IntegerIndex of ADU eligibility according to parking space exemption (200 square feet) policy scenario (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SMShort IntegerIndex of ADU eligibility according to both the setback reduction and small ADU policy scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_PKShort IntegerIndex of ADU eligibility according to both the setback reduction and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SM_PKShort IntegerIndex of ADU eligibility according to both the small ADU policy and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SM_PKShort IntegerIndex of ADU eligibility according to the setback reduction, small ADU, and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)1. Slope: '0' - 0~4 percent; '5' - 5~9 percent; '10' - 10~14 percent; '15' = 15~19 percent; '20' - 20~24 percent; '25' = 25 percent or greater.2. Source of 2019 existing land use: SCAG_REF- SCAG's regional geospatial datasets;ASSESSOR- Assessor's 2019 tax roll records; CPAD- California Protected Areas Database (version 2020a; accessed in September 2020); CSCD- California School Campus Database (version 2018; accessed in September 2020); FMMP- Farmland Mapping and Monitoring Program's Important Farmland GIS data (accessed in September 2020); MIRTA- U.S. Department of Defense's Military Installations, Ranges, and Training Areas GIS data (accessed in September 2020)3. Type of public agency includes federal, state, county, city, special district, school district, college/university, military.4. Based on 2019 building footprint data obtained from BuildingFootprintUSA (except that 2014 building footprint data was used for Imperial County). Please note that 2019 building footprint data does not cover the entire SCAG region (overlapped with 83% of parcels in the SCAG Region).5. Includes brownfield/superfund site whose address information are matched by SCAG rooftop address locator. Brownfield data was obtained from EPA's Assessment, Cleanup and Redevelopment Exchange System (ACRES) database, Cleanups in my community (CIMC), DTSC brownfield Memorandum of Agreement (MOA). Superfund site data was obtained from EPA's Superfund Enterprise Management System (SEMS) database.6. Parcels with a zero value for building footprint area are marked as NULL to indicate this field is not reliable.7. These values are intended as a rudimentary indicator of accessibility developed by SCAG using 2016 InfoUSA business establishment data and 2017 California Protected Areas data. See documentation for details.8. A detailed study conducted by Cal Poly Pomona (CPP) and available hereconducted an extensive review of state and local requirements and development trends for ADUs in the SCAG region and developed a baseline set of assumptions for estimating how many of a jurisdiction’s parcels

This Script audits all of the Items within a Geodatabase. The first step of the process is to accesses the GDB_ITEMS table, and export the table to a scratch gdb. Then Definition and Documentation fields are deleted because excel does not like them. Then the process accesses the GDB_ITEMTYPES table, and export the table to a scratch gdb. Then Join Field Management Geoprocessing tool is run to bring the two tables together then exported to excel.

Alaska's commercial fisheries are managed using various regulatory areas (i.e., districts, sections, statistical areas, etc...). District, subdistrict, and section polygons are delineated based on regulatory descriptions found in 5 AAC 21.200 (Cook Inlet Area). Alaska Fish and Game Regulations as described in 5 AAC 21.200 (last electronic update 6/15/2024) covers the May 2024 through May 2027 or until a new book is available following the Board of Fisheries meetings.Statistical areas are largely not defined in regulation, but internally defined within ADF&G. Statistical areas included are used for salmon fisheries for reporting harvest within Upper Cook Inlet. Statistical areas are polygons that divide the waters of the State of Alaska and the adjacent Exclusive Economic Zone (EEZ) into small units for the purpose of reporting and analyzing fishery harvest. Each statistical area is identified by a unique 5-digit number. Salmon statistical areas can be divided by lines defined in ADF&G regulations, and further subdivided based on prominent landmarks or points of land. Each statistical area has a geometry start date attribute which ranges in this dataset for Southeast Alaska from 1963 to 2024. Over the years, there have been changes to statistical area shapes , codes, and names. If a statistical area is not included in this file, it may have been used historically and exist in another GIS file version. Please note spring troll statistical areas DO NOT use these statistical areas for recording harvest, but are separately defined each spring in an ADF&G Advisory Announcement. Please contact the Troll Fishery Biologists for additional info on spring troll statistical areas.This data set should NOT be used for navigation or for determining compliance with ADF&G Commercial Fishing Regulations. Please consult the ADF&G Salmon Commercial Fisheries Regulations for the official definitions of regulatory boundaries. NOTE: These data attempt to depict boundaries as used for management during a specific time period. In some cases, boundaries used in practice may differ from those described in regulations, reports, maps, and other aids.Data last updated September 2024.

10-foot elevation contours for the extent of the state of Indiana, created from downloading, projecting and combining several datasets from USGS based on 7.5-minute quadrangle boundaries. These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale CONUS and Hawaii, 1:25,000-scale Alaska, and 1:20,000-scale Puerto Rico / US Virgin Island topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation. Description from the original source metadata: These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale CONUS and Hawaii, 1:25,000-scale Alaska, and 1:20,000-scale Puerto Rico / US Virgin Island topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation.Source files downloaded from The National Map on 11/18/2019:https://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Muncie_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Danville_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Vincennes_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Louisville_W_KY_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Cincinnati_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Indianapolis_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Fort_Wayne_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Chicago_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Indianapolis_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Danville_W_IL_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Vincennes_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Chicago_W_IL_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Cincinnati_E_OH_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Muncie_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Louisville_E_KY_1X1_GDB.zip https://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Fort_Wayne_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Evansville_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Evansville_W_IN_1X1_GDB.zip

WSA_ARC: This data set represents Wilderness Study Area (WSA) boundaries as inventoried in the mid1980's and defined in the October 1991 "Wilderness Study Report". Wilderness Study Areas are essentially roadless areas under BLM jurisdiction. Wilderness Study Areas have special management restrictions and priorities. They are a one-time designation and new WSA or additions to WSA are rare. For a complete description of this data consult the Wilderness Study Areas Spatial Data Standard. http://www.blm.gov/or/datamanagement/index.php

This layer shows workers' place of residence by mode of commute. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized by the percentage of workers who drove alone. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B08301 (Not all lines of this ACS table are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

These are areas of water that are defined from meander lines of the Public Land Survey System (PLSS) and General Land Office (GLO) surveys. These are not the official representations of coast or water lines and are representations of the lines marked by the survey along the boundaries of meandered water at the time of survey

This polygon coverage identifies corporate boundaries for all 45 municipal jurisdictions in Westchester County. Coverage originally obtained from New York State Office for Real Property Services (ORPS), and has been substantially modified to better align with current municipal tax parcel boundaries (WCparcels) based on a compilation of 2012 municipal tax parcel datasets. As all of Westchester's town's and cities compile their tax parcel databases independent of one another, there are situations were the tax parcels do not line up at the municipal borders, often resulting in gaps or overlaps of tax parcels at the border areas. This update sought to re-align boundaries to best follow the municipal boundaries as defined by the tax parcels, and often involved making the best possible spatial compromise where there were gaps or overlaps in tax map jurisdictions. It also reflects the 2011 municipal boundary change that resluted from the annexation of a tax parcel from the Town of Mount Pleasant to the Town of New Castle.

The geodatabase contains a single feature class that shows three (3) flooding categories. The "1-Nuisance Flooding" (ponding depths greater or equal to 4 in. and less than 1 ft.) and "2-Deep and Contiguous Flooding" (ponding depths 1 ft. and greater) categories were created using hydrologic and hydraulic computer models and represent flood risk due to extreme rainfall. The third category, "3-Future High Tides 2050", shows coastal tidal inundation based on the NYC Panel on Climate Change 90th percentile estimates for the 2050's and is sourced from the NYC Flood Hazard Mapper. Please refer to the New York City Stormwater Resiliency Plan for more information on the purpose of the study, how datasets were developed, applications for this data, and other details.A coded value domain is used for the "Flooding_Category" field. See Column Info tab of the Data Dictionary for definition of each code.

BLM Alaska PLSS Intersected: 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.

10-foot elevation contours for the extent of the state of Indiana, created from downloading, projecting and combining several datasets from USGS based on 7.5-minute quadrangle boundaries. These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale CONUS and Hawaii, 1:25,000-scale Alaska, and 1:20,000-scale Puerto Rico / US Virgin Island topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation. Description from the original source metadata: These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale CONUS and Hawaii, 1:25,000-scale Alaska, and 1:20,000-scale Puerto Rico / US Virgin Island topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation.Source files downloaded from The National Map on 11/18/2019:https://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Muncie_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Danville_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Vincennes_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Louisville_W_KY_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Cincinnati_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Indianapolis_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Fort_Wayne_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Chicago_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Indianapolis_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Danville_W_IL_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Vincennes_W_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Chicago_W_IL_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Cincinnati_E_OH_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Muncie_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Louisville_E_KY_1X1_GDB.zip https://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Fort_Wayne_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Evansville_E_IN_1X1_GDB.ziphttps://prd-tnm.s3.amazonaws.com/StagedProducts/Contours/GDB/ELEV_Evansville_W_IN_1X1_GDB.zip

GRA_ALLOTMENT: This is the feature dataset for the Livestock grazing allotments and associated attributes describing some basic characteristics of the allotments for allotments on BLM lands in Oregon and Washington.