United States of America GIS data

Intended for searching and web map display in Portal web maps and web applications or in ArcGIS Pro. Source of feature class that published this web service is from enterprise geodatabase LotNumberPointsWk & LotDimensionPointsWk2 (yes that is a number 2 at the end). Key words are standardized for ArcGIS Pro users to be able to search through the County's Geo Portal web services without being logged in. Key words use the same standards of Category.

The STIP is a multi-year capital improvement document which denotes the scheduling and funding of construction projects across the state over a minimum 4 year time period as required by Federal law. North Carolina’s STIP covers a 10 year period, with the first six years referred to as the delivery STIP and the latter four years as the developmental STIP. Per 23 CFR 450.216 & 23 U.S. Code § 135 STIP’s must also: Be submitted to Federal Highway Administration (FHWA) & Federal Transit Administration (FTA) for approval at least every 4 years Be fiscally constrained by year Include all capital and non-capital projects using Title 23 USC or Title 49 USC funds, other than certain safety, planning, and research funds Include metropolitan TIPs (Transportation Improvement Projects) from Metropolitan Planning Organizations Provide public comment opportunity on STIP document And include the following information: Project description and termini Estimated total cost (NCDOT includes Utility, R/W, and Construction costs) Federal funds to be obligated Responsible agency (such as municipality) The STIP contains funding information and schedules for transportation modes and programs including: Highways, Aviation, Bicycle and Pedestrian, Ferry, Public Transportation, Rail, Governor’s Highway Safety and statewide related programs. The transportation program in the STIP is organized by the 14 transportation divisions. Each Division section includes a funding source reference table and is divided between highway and non-highway project schedules. Projects are also listed by county within each division. This results in some duplication since transportation projects frequently extend across county and division lines. When this duplication occurs, a project is listed in each county in which it is found. Projects are further subdivided by category: interstate, rural, urban, bridge, municipal bridge, bicycle and pedestrian, congestion mitigation, highway safety improvement program, ferry, passenger rail, and roadside environmental. Interstate, rural, urban, bridge, and ferry projects are described by route number. Municipal bridge, bike and pedestrian projects are listed by city or county. Congestion mitigation and passenger rail projects are listed alphabetically by city or county. Highway safety improvement program projects may be listed by route, city, or county. The Public Transportation program list projects first by the transportation partners and providers then by identification numbers. Projects are also listed by the STI category they are funded from, i.e., by Statewide Mobility, Regional Impact, or Division Needs. The phases of projects (such as Right of Way (R), Utility relocation (U), and Construction (C) are listed by Fiscal Year along with their costs and anticipated funding sources. All projects require extensive planning, environmental impact and design studies. The location and exact type of improvements are subject to refinement and modification during the planning and design phases. North Carolina’s STIP is updated every two years and developed in concert with federal and state revenue forecasts, North Carolina Department of Transportation’s (NCDOT’s) Strategic Prioritization process, preconstruction and project development timetables, and in adherence with federal and state laws. North Carolina state law requires Board of Transportation (BOT) action to approve the STIP. For complete information: https://connect.ncdot.gov/projects/planning/STIPDocuments1/NCDOT%20Current%20STIP.pdf

Railroad line features in Utah, with attributes describing railroad and operator names, type, passenger and commuter flags, abandoned status, electrification, FIPS code and line length. Published by UtahAGRC.

Point features labeling Micropolitan Statistical Areas in the United States, published by the US Census Bureau. Each feature represents one micropolitan statistical area, identified by its name in the BASENAME column, such as Liberal, KS or Mexico, MO.

This dataset indicates whether the City of Tempe met its groundwater production capacity to meet the projected average for future annual daily demand.  Currently, Tempe has approximately 24 million gallons per day (MGD) of existing recovery well production capacity and an average annual daily demand of around 43 MGD.  Over the next five years, capital projects are planned to design and construct wells that will add or recapture about 10 MGD of additional capacity to the system.  Some of these projects include the addition of wellhead treatment to existing wells that were removed from service due to water quality concerns.  As this program develops, additional new wells will be sited and added to the overall system to bring us closer to reaching this goal.  The performance measure dashboard is available at 4.16 Groundwater Supply     Data Dictionary   Additional Information   Source: Arizona Department of Water Resources Contact:  Tara Ford Contact E-Mail: Tara_Ford@tempe.gov Data Source Type:  Excel Preparation Method:  The permitted capacity for each well site is added together. Publish Frequency:  Annual Publish Method: Manual

Census Current (2020) Physical Features Web Map Service; January 1, 2020 vintage

The dataset contains locations and attributes of above ground permits applied for and approved by the District Department of Transportation. They are newly occupied constructions and events. Examples include: moving truck, roll off debris container, moving storage container, construction staging area, mobile crane work zone, other reserved parking. The public space permit process is described on the DDOT website https://ddot.dc.gov. These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC. Use the MAR Geocoderto help complete this.

uav imagery by WebODM, acquired 2025-05-28 to 2025-05-28, 5.0 cm per pixel, published on OpenAerialMap.

County Subdivisions, Subbarrios, Consolidated Cities, Incorporated Places, and Census Designated Places; January 1, 2015 vintage; Generalized

ACS 2025 Legal and Statistical Entities Web Map Service; January 1, 2025 vintage

Budgeted and actual expenses divided by fun, department, business unit, and account with details for each fiscal year.  This dataset is updated annually. Source Link: https://www.nashville.gov/departments/finance/management-and-budget/citizens-guide-budgetMetadata Document: Metro Budget to Actual Expenses (FY2010 - Present) Metadata.pdfContact Data Owner: opendata@nashville.gov

The dataset contains a subset of locations and attributes of incidents reported in the ASAP (Analytical Services Application) crime report database by the District of Columbia Metropolitan Police Department (MPD). Visit crimecards.dc.gov for more information. This data is shared via an automated process where addresses are geocoded to the District's Master Address Repository and assigned to the appropriate street block. Block locations for some crime points could not be automatically assigned resulting in 0,0 for x,y coordinates. These can be interactively assigned using the MAR Geocoder. On February 1 2020, the methodology of geography assignments of crime data was modified to increase accuracy. From January 1 2020 going forward, all crime data will have Ward, ANC, SMD, BID, Neighborhood Cluster, Voting Precinct, Block Group and Census Tract values calculated prior to, rather than after, anonymization to the block level. This change impacts approximately one percent of Ward assignments.

Age, Sex, Race, Ethnicity, Total Housing Units, and Voting Age Population. This service is updated annually with American Community Survey (ACS) 1-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: District-wide. Current Vintage: 2024. ACS Table(s): DP05. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: March 11, 2026. National Figures: data.census.gov. 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. Boundaries come from the US Census TIGER geodatabases. 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 clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

Legal and Statistical Entities Web Map Service; January 1, 2020 vintage

ACS 2019 Legal and Statistical Entities Web Map Service; January 1, 2019 vintage

Legal and Statistical Entities Web Map Service; January 1, 2020 vintage

This data represents metrics displayed on the 2040 Plan Implementation Dashboard along with select Variable data form Quality of Life (QOL) data that

ACS 2023 Legal and Statistical Entities Web Map Service; January 1, 2023 vintage

ACS 2026 Legal and Statistical Entities Web Map Service; January 1, 2026 vintage

Legal and Statistical Entities Web Map Service; January 1, 2010 vintage

ACS 2016 Legal and Statistical Entities Web Map Service; January 1, 2016 vintage

Legal and Statistical Entities Web Map Service; January 1, 2010 vintage

ACS 2017 Legal and Statistical Entities Web Map Service; January 1, 2017 vintage

CWHR Predicted Habitat Models represent areas of predicted suitable habitat for each species within its range. These models are built from the following principal inputs: 1) a statewide, best-available vegetation map (FVEG); 2) GIS data representing a species’ range; 3) the CWHR database of habitat suitability values for over 700 terrestrial vertebrate species. Habitat suitability ranks of Low (non-zero values less than 0.34), Medium (0.34-0.66), and High (greater than 0.66) are based on the maximum suitability value across the 3 species life requisites: reproduction, feeding, and cover. Note that previous versions of these Predicted Habitat Models used an average across the 3 life requisites in order to obtain an overall suitability score for each habitat type and stage class. Habitat suitability scores were developed based on habitat patch sizes greater than 40 acres in size and are best interpreted for habitat patches greater than 200 acres in size. The FVEG landcover dataset is an aggregation of multiple statewide landcover and regional vegetation mapping efforts, conducted at different points in time (approximately 1990 up to time of publishing) and at various resolutions, compiled by the California Department of Forestry and Fire Protection (CALFIRE). FVEG uses the most current and consistent data available for each region of the state. Decision rules were developed that controlled which layers were given priority in areas of overlap. Crosswalks were used to attribute the various data sources according to the CWHR habitat-type classification system. Attributing FVEG with CWHR habitat types allows for the extraction of areas with non-zero suitability values for each species within the bounds of its range, creating a series of maps of predicted suitable habitat which are species-specific. Because FVEG is an amalgam of disparate landcover assessment efforts across the state, the predictive power for determining suitable habitat will vary between species, and possibly even regionally for species which are widely distributed. While these maps represent CDFW’s best estimate of the presence of suitable habitat for any given species in the CWHR system, these maps are also limited by several factors: 1) the accuracy and resolution of vegetation maps in a given region; 2) the dynamic nature of the landscape in which fire and other disturbance events alter conditions at a greater frequency than mapping efforts can track; 3) the currency of expert knowledge, particularly as species adapt to changing land and climate conditions and the shifting of other species’ ranges; 4) the frequency of species-specific surveys across a representative sample of a species’ entire range; 5) metapopulation dynamics, which describes the shifting of populations within their environment as result of numerous types of interactions and responses. CWHR GIS data representing predicted suitable habitat should not be used to indicate the presence or absence of a particular species at any specific site. CWHR predicted habitat models are named according to the 4-character alpha-numeric CWHR ID assigned to each species (5 characters in the case of subspecies or other sub-taxa). There is also a “CWHR Revision Tracking Table” containing a record for each species, its CWHR ID, scientific name, common name, and range and habitat model data revision history. CWHR species range models, predicted habitat models, and GIS data of the statewide distribution of all CWHR habitat types, along with the CWHR revision tracking table, are available for download at https://www.wildlife.ca.gov/Data/CWHR.

Census Current (2020) Physical Features Web Map Service; January 1, 2020 vintage

Employment, Commuting, Occupation, Income, Health Insurance, Poverty, and more. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: District-wide. Current Vintage: 2019-2023. ACS Table(s): DP03. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 2, 2025. National Figures: data.census.gov. 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. Boundaries come from the US Census TIGER geodatabases. 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 clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

Employment, Commuting, Occupation, Income, Health Insurance, Poverty, and more. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: Census Tracts. Current Vintage: 2019-2023. ACS Table(s): DP03. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 2, 2025. National Figures: data.census.gov. 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. Boundaries come from the US Census TIGER geodatabases. 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 clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

Census Current (2020) Physical Features Web Map Service; January 1, 2020 vintage

Point label features for current census blocks, giving the block identifier and name for each block. Published by the US Census Bureau for the United States.

Dates of Images: Post-Event: May 19, 2026 Pre-Event: May 11, 2026 Date of Next Image: Unknown Summary: These pre-fire and post-fire images pair were analyzed for normalized burn ratio (NBR). The input images were generated from the Landsat datasets at 30m resolution. NBR is defined mathematically as (NIR – SWIR)/(NIR + SWIR) where NIR is near-infrared and SWIR is short-wave infrared. dNBR is computed by the difference between the pre-fire NBR and the post-fire NBR. More information on dNBR can be found here: https://un-spider.org/advisory-support/recommended-practices/recommended-practice-burn-severity/in-detail/normalized-burn-ratio. dNBR data may be computed while the fire is in progress. This is intentionally done to prioritize rapid data availability for proactive disaster response but means data can change over the course of the fire. Check fire containment and image dates for further context on image timing. Suggested Use: NBR is commonly used as a proxy to indicate areas which have charred vegetation. Darker areas (more negative values) in the NBR image more strongly represent the presence of burned vegetation. Since the dNBR considers the condition of the scene before the fire occurred, the resulting value has been used as a proxy for burn severity. Higher dNBR values represent a proxy for greater burn severity. Negative dNBR values may represent a re-greening of or growth of vegetation in between pre and post imagery. The use of this dNBR product as a quantitative metric of burn severity at the time of posting this dataset should be strongly caveated. This is due to several dNBR limitations: The spectral band selections used for dNBR calculations, and the implication of changes observed following fire in those wavelengths, primarily pertain to how vegetation spectral signatures change in NIR and SWIR wavelengths following charring. Because of this, dNBR may not accurately describe burned surfaces that are not vegetation (e.g. human built infrastructure). This dataset has not been validated by independent burn severity assessments. The degree to which dNBR is accurately determined depends on careful selection of pre and post event imagery. An effort was made to use the highest quality imagery (i.e. cloud free) with representative conditions for each scene; however, it is unknown at the time of this posting how selection of different pre/post image pairs could affect the derived dNBR values. Satellite/Sensor: Landsat 9 Operational Land Imager (OLI) Resolution: 30 meters Credits: NASA/MSFC, USGS Service URL: See individual Layers. WMS Endpoint: https://gis.earthdata.nasa.gov/portal/services/DISASTERS_202605_FIRE_KS/202608_landsat_dnbr/ImageServer/WMSServer

Dates of Images: Post-Event: May 16, 2026 Pre-Event: May 11, 2026 Date of Next Image: Updated images are expected to be available for additional analysis as needed up to every 6 days. For lower-latency information regarding fire extent and estimated burn area, please see the Fire Events Data Suite (FEDS) web map. Summary: These pre-fire and post-fire images pair were analyzed for normalized burn ratio (NBR). The input images were generated from the Sentinel-2 dataset at 10m resolution. NBR is defined mathematically as (NIR – SWIR)/(NIR + SWIR) where NIR is near-infrared and SWIR is short-wave infrared. dNBR is computed by the difference between the pre-fire NBR and the post-fire NBR. More information on dNBR can be found here: https://un-spider.org/advisory-support/recommended-practices/recommended-practice-burn-severity/in-detail/normalized-burn-ratio. dNBR data may be computed while the fire is in progress. This is intentionally done to prioritize rapid data availability for proactive disaster response but means data can change over the course of the fire. Check fire containment and image dates for further context on image timing. Suggested Use: dNBR is commonly used as a proxy to identify fire-affected areas. Higher dNBR value are statistically correlated with greater burn severity, where negative dNBR values may represent a re-greening of or growth of vegetation in between pre and post-vegetation. The use of this dNBR product as a quantitative metric of burn severity at the time of posting this dataset should be strongly caveated. This is due to several dNBR limitations: The spectral band selections used for dNBR calculations, and the implication of changes observed following fire in those wavelengths, primarily pertain to how vegetation spectral signatures change in NIR and SWIR wavelengths following charring. Because of this, dNBR will not accurately describe burned surfaces that are not vegetation (e.g. human built infrastructure), and the interpretation of dNBR values may vary widely based on the type of vegetation burned. This dataset has not been validated by independent burn severity assessments. The degree to which dNBR is accurately determined depends on careful selection of pre and post event imagery. An effort was made to use the highest quality imagery (i.e. cloud free) with representative conditions for each scene; however, it is unknown at the time of this posting how selection of different pre/post image pairs could affect the derived dNBR values. Satellite/Sensor: Copernicus Sentinel-2 Resolution: 10 meters Credits: NASA/MSFC, ESA Copernicus Service URL: See URL to the bottom right. WMS Endpoint: https://gis.earthdata.nasa.gov/portal/services/DISASTERS_202605_FIRE_KS/202608_sentinel2_dnbr/ImageServer/WMSServer

ACS 2018 Legal and Statistical Entities Web Map Service; January 1, 2018 vintage

ACS 2019 Legal and Statistical Entities Web Map Service; January 1, 2019 vintage

CWHR Predicted Habitat Models represent areas of predicted suitable habitat for each species within its range. These models are built from the following principal inputs: 1) a statewide, best-available vegetation map (FVEG); 2) GIS data representing a species’ range; 3) the CWHR database of habitat suitability values for over 700 terrestrial vertebrate species. Habitat suitability ranks of Low (non-zero values less than 0.34), Medium (0.34-0.66), and High (greater than 0.66) are based on the maximum suitability value across the 3 species life requisites: reproduction, feeding, and cover. Note that previous versions of these Predicted Habitat Models used an average across the 3 life requisites in order to obtain an overall suitability score for each habitat type and stage class. Habitat suitability scores were developed based on habitat patch sizes greater than 40 acres in size and are best interpreted for habitat patches greater than 200 acres in size. The FVEG landcover dataset is an aggregation of multiple statewide landcover and regional vegetation mapping efforts, conducted at different points in time (approximately 1990 up to time of publishing) and at various resolutions, compiled by the California Department of Forestry and Fire Protection (CALFIRE). FVEG uses the most current and consistent data available for each region of the state. Decision rules were developed that controlled which layers were given priority in areas of overlap. Crosswalks were used to attribute the various data sources according to the CWHR habitat-type classification system. Attributing FVEG with CWHR habitat types allows for the extraction of areas with non-zero suitability values for each species within the bounds of its range, creating a series of maps of predicted suitable habitat which are species-specific. Because FVEG is an amalgam of disparate landcover assessment efforts across the state, the predictive power for determining suitable habitat will vary between species, and possibly even regionally for species which are widely distributed. While these maps represent CDFW’s best estimate of the presence of suitable habitat for any given species in the CWHR system, these maps are also limited by several factors: 1) the accuracy and resolution of vegetation maps in a given region; 2) the dynamic nature of the landscape in which fire and other disturbance events alter conditions at a greater frequency than mapping efforts can track; 3) the currency of expert knowledge, particularly as species adapt to changing land and climate conditions and the shifting of other species’ ranges; 4) the frequency of species-specific surveys across a representative sample of a species’ entire range; 5) metapopulation dynamics, which describes the shifting of populations within their environment as result of numerous types of interactions and responses. CWHR GIS data representing predicted suitable habitat should not be used to indicate the presence or absence of a particular species at any specific site. CWHR predicted habitat models are named according to the 4-character alpha-numeric CWHR ID assigned to each species (5 characters in the case of subspecies or other sub-taxa). There is also a “CWHR Revision Tracking Table” containing a record for each species, its CWHR ID, scientific name, common name, and range and habitat model data revision history. CWHR species range models, predicted habitat models, and GIS data of the statewide distribution of all CWHR habitat types, along with the CWHR revision tracking table, are available for download at https://www.wildlife.ca.gov/Data/CWHR.

Urbanized Areas, Urban Clusters; 2010 Census - January 1, 2010 vintage; Generalized

Label features for economic places, giving the place identifier and name for each place in the January 1, 2012 vintage. Published by the US Census Bureau for the United States.