82 datasets found
  1. d

    Street Right of Way Polygons

    • catalog.data.gov
    • opendata.dc.gov
    • +1more
    Updated Feb 4, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    D.C. Office of the Chief Technology Officer (2025). Street Right of Way Polygons [Dataset]. https://catalog.data.gov/dataset/street-right-of-way-polygons
    Explore at:
    Dataset updated
    Feb 4, 2025
    Dataset provided by
    D.C. Office of the Chief Technology Officer
    Description

    Street right of way polygons are public spaces along the DC managed street segments. A database provided by DDOT identified ROW locations from authoritative source documentation including DDOT surface maps, ROW distribution cards, Subdivision Books in the DC Surveyor's Office, Survey Books, King Plats, Record Books, Street Extension Maps, County Maps, AT Map Books, Wall Books and Wall Reports.

  2. TIGER/Line Shapefile, Current, County, District of Columbia, DC, All Roads

    • catalog.data.gov
    Updated Aug 9, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division (Point of Contact) (2025). TIGER/Line Shapefile, Current, County, District of Columbia, DC, All Roads [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-current-county-district-of-columbia-dc-all-roads
    Explore at:
    Dataset updated
    Aug 9, 2025
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Washington, District of Columbia
    Description

    This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

  3. d

    ACS 5-Year Demographic Characteristics DC Census Tract

    • catalog.data.gov
    • datasets.ai
    • +3more
    Updated Apr 30, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Washington, DC (2025). ACS 5-Year Demographic Characteristics DC Census Tract [Dataset]. https://catalog.data.gov/dataset/acs-5-year-demographic-characteristics-dc-census-tract
    Explore at:
    Dataset updated
    Apr 30, 2025
    Dataset provided by
    City of Washington, DC
    Area covered
    Washington
    Description

    Age, Sex, Race, Ethnicity, Total Housing Units, and Voting Age Population. 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): DP05. 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.

  4. a

    COUNTIES

    • hub.arcgis.com
    • mce-data-uscensus.hub.arcgis.com
    • +1more
    Updated Feb 4, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    US Census Bureau (2024). COUNTIES [Dataset]. https://hub.arcgis.com/maps/USCensus::counties-47
    Explore at:
    Dataset updated
    Feb 4, 2024
    Dataset authored and provided by
    US Census Bureau
    Area covered
    Description

    This layer shows Health Insurance Coverage. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the 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 to show Percent of Population with No Health Insurance Coverage. 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: 2018-2022ACS Table(s): B27010, DP03Data downloaded from: Census Bureau's API for American Community SurveyDate of API call: January 18, 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. 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:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, 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 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). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. 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.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

  5. a

    COUNTIES

    • covid19-uscensus.hub.arcgis.com
    • hub.arcgis.com
    • +2more
    Updated Feb 5, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    US Census Bureau (2024). COUNTIES [Dataset]. https://covid19-uscensus.hub.arcgis.com/datasets/USCensus::households-by-type-2018-2022-states?layer=2
    Explore at:
    Dataset updated
    Feb 5, 2024
    Dataset authored and provided by
    US Census Bureau
    Area covered
    Description

    This layer shows Households by Type. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the 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 to show Average Household Size and the Total Households in a bi-variate map. 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: 2018-2022ACS Table(s): B11001, B25010, B25044, DP02, DP04Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 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. 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:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, 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 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). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. 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.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

  6. d

    Census Blocks in 2020

    • opdatahub.dc.gov
    • opendata.dc.gov
    • +4more
    Updated Aug 27, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Washington, DC (2021). Census Blocks in 2020 [Dataset]. https://opdatahub.dc.gov/maps/census-blocks-in-2020
    Explore at:
    Dataset updated
    Aug 27, 2021
    Dataset authored and provided by
    City of Washington, DC
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    Census blocks are statistical areas bounded on all sides by visible features (e.g., streets, roads, streams, and railroad tracks), and by non-visible boundaries (e.g., city, town, township, county limits, and short line-of-sight extensions of streets and roads). Generally, census blocks are small in area (e.g., a block in a city). Census blocks in suburban and rural areas may be large, irregular, and bounded by a variety of features (e.g., roads, streams, and/or transmission line rights-of-way). In remote areas, census blocks may encompass hundreds of square miles. Census blocks cover all territory in the United States, Puerto Rico, and the Island areas. Blocks do not cross the boundaries of any entity for which the Census Bureau tabulates data.Census Block Numbers—Census blocks are numbered uniquely within the boundaries of each state, county, census tract with a 4-character census block number. The first character of the tabulation block number identifies the block group. A block number can only be unique by using the decennial census state (STATEFP

  7. a

    COUNTIES

    • hub.arcgis.com
    • covid19-uscensus.hub.arcgis.com
    Updated Feb 2, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    US Census Bureau (2024). COUNTIES [Dataset]. https://hub.arcgis.com/maps/USCensus::counties-51
    Explore at:
    Dataset updated
    Feb 2, 2024
    Dataset authored and provided by
    US Census Bureau
    Area covered
    Description

    This layer shows data related to Grandparents. This is shown by state and county boundaries. This service contains 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 to show 'Total grandchildren in care of Grandparents.' 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: 2018-2022ACS Table(s): DP02Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 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. 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:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, 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 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). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. 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.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

  8. d

    ACS 1-Year Social Characteristics DC

    • opendata.dc.gov
    • opdatahub.dc.gov
    • +3more
    Updated Feb 28, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Washington, DC (2025). ACS 1-Year Social Characteristics DC [Dataset]. https://opendata.dc.gov/datasets/DCGIS::acs-1-year-social-characteristics-dc
    Explore at:
    Dataset updated
    Feb 28, 2025
    Dataset authored and provided by
    City of Washington, DC
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    Household type, Education, Disability, Language, Computer/Internet Use, and more. 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: 2023. ACS Table(s): DP02. 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.

  9. H

    Texas-Harvey Basemap - Addresses and Boundaries

    • hydroshare.org
    • beta.hydroshare.org
    • +1more
    zip
    Updated Nov 9, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    David Arctur; David Maidment (2023). Texas-Harvey Basemap - Addresses and Boundaries [Dataset]. http://doi.org/10.4211/hs.3e251d7d70884abd928d7023e050cbdc
    Explore at:
    zip(703.5 MB)Available download formats
    Dataset updated
    Nov 9, 2023
    Dataset provided by
    HydroShare
    Authors
    David Arctur; David Maidment
    Area covered
    Description

    This site provides access to download an ArcGIS geodatabase or shapefiles for the 2017 Texas Address Database, compiled by the Center for Water and the Environment (CWE) at the University of Texas at Austin, with guidance and funding from the Texas Division of Emergency Management (TDEM). These addresses are used by TDEM to help anticipate potential impacts of serious weather and flooding events statewide. This is part of the Texas Water Model (TWM), a project to adapt the NOAA National Water Model [1] for use in Texas public safety. This database was compiled over the period from June 2016 to December 2017. A number of gaps remain (towns and cities missing address points), see Address Database Gaps spreadsheet below [4]. Additional datasets include administrative boundaries for Texas counties (including Federal and State disaster-declarations), Councils of Government, and Texas Dept of Public Safety Regions. An Esri ArcGIS Story Map [5] web app provides an interactive map-based portal to explore and access these data layers for download.

    The address points in this database include their "height above nearest drainage" (HAND) as attributes in meters and feet. HAND is an elevation model developed through processing by the TauDEM method [2], built on USGS National Elevation Data (NED) with 10m horizontal resolution. The HAND elevation data and 10m NED for the continental United States are available for download from the Texas Advanced Computational Center (TACC) [3].

    The complete statewide dataset contains about 9.28 million address points representing a population of about 28 million. The total file size is about 5GB in shapefile format. For better download performance, the shapefile version of this data is divided into 5 regions, based on groupings of major watersheds identified by their hydrologic unit codes (HUC). These are zipped by region, with no zipfile greater than 120mb: - North Tx: HUC1108-1114 (0.52 million address points) - DFW-East Tx: HUC1201-1203 (3.06 million address points) - Houston-SE Tx: HUC1204 (1.84 million address points) - Central Tx: HUC1205-1210 (2.96 million address points) - Rio Grande-SW Tx: HUC2111-1309 (2.96 million address points)

    Additional state and county boundaries are included (Louisiana, Mississippi, Arkansas), as well as disaster-declaration status.

    Compilation notes: The Texas Commission for State Emergency Communications (CSEC) provided the first 3 million address points received, in a single batch representing 213 of Texas' 254 counties. The remaining 41 counties were primarily urban areas comprising about 6.28 million addresses (totaling about 9.28 million addresses statewide). We reached the GIS data providers for these areas (see Contributors list below) through these emergency communications networks: Texas 9-1-1 Alliance, the Texas Emergency GIS Response Team (EGRT), and the Texas GIS 9-1-1 User Group. The address data was typically organized in groupings of counties called Councils of Governments (COG) or Regional Planning Commissions (RPC) or Development Councils (DC). Every county in Texas belongs to a COG, RPC or DC. We reconciled all counties' addresses to a common, very simple schema, and merged into a single geodatabase.

    November 2023 updates: In 2019, TNRIS took over maintenance of the Texas Address Database, which is now a StratMap program updated annually [6]. In 2023, TNRIS also changed its name to the Texas Geographic Information Office (TxGIO). The datasets available for download below are not being updated, but are current as of the time of Hurricane Harvey.

    References: [1] NOAA National Water Model [https://water.noaa.gov/map] [2] TauDEM Downloads [https://hydrology.usu.edu/taudem/taudem5/downloads.html] [3] NFIE Continental Flood Inundation Mapping - Data Repository [https://web.corral.tacc.utexas.edu/nfiedata/] [4] Address Database Gaps, Dec 2017 (download spreadsheet below) [5] Texas Address and Base Layers Story Map [https://www.hydroshare.org/resource/6d5c7dbe0762413fbe6d7a39e4ba1986/] [6] TNRIS/TxGIO StratMap Address Points data downloads [https://tnris.org/stratmap/address-points/]

  10. a

    ACS Median Household Income Variables - Boundaries

    • umn.hub.arcgis.com
    Updated Apr 25, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    University of Minnesota (2021). ACS Median Household Income Variables - Boundaries [Dataset]. https://umn.hub.arcgis.com/datasets/dab218ee6f9f4421a2c96477abee6f30
    Explore at:
    Dataset updated
    Apr 25, 2021
    Dataset authored and provided by
    University of Minnesota
    Area covered
    Description

    This layer shows median household income by race and by age of householder. 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. Median income and income source is based on income in past 12 months of survey. This layer is symbolized to show median household income. 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: 2015-2019ACS Table(s): B19013B, B19013C, B19013D, B19013E, B19013F, B19013G, B19013H, B19013I, B19049, B19053Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 10, 2020National 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. 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. 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 2010 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). 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.

  11. D

    County Boundaries (line)

    • catalog.dvrpc.org
    • dvrpc-dvrpcgis.opendata.arcgis.com
    • +1more
    api, geojson, html +1
    Updated Nov 4, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    DVRPC (2025). County Boundaries (line) [Dataset]. https://catalog.dvrpc.org/dataset/county-boundaries-line
    Explore at:
    xml, geojson, html, apiAvailable download formats
    Dataset updated
    Nov 4, 2025
    Dataset provided by
    Delaware Valley Regional Planning Commissionhttps://www.dvrpc.org/
    Authors
    DVRPC
    Description

    County boundaries (linear features) for Pennsylvania, New Jersey, Delaware, Maryland, New York, Connecticut, and the District of Columbia. Original Sources: PA - PennDOT NJ - NJOIT DE - DE Geological Survey MD, NY, CT, DC - ESRI Linework has been adjusted using the following methodology. NJ's boundaries overrode PA, since NJ's were highly accurate. PA overrode MD since PennDOT's were more accurate than ESRI's, and DE overrode PA & MD, since the "arc" of northernmost DE was a bit more accurate than PennDOT's or our original county boundaries. County boundaries in the DVRPC region have been adjusted to align with parcel data (where appropriate). NOTE: Use the following definition query if only need one county in DVRPC Region "Co_Name" LIKE '%Bucks%'

  12. TIGER/Line Shapefile, 2022, State, District of Columbia, DC, Census Tract

    • catalog.data.gov
    Updated Jan 27, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Spatial Data Collection and Products Branch (Point of Contact) (2024). TIGER/Line Shapefile, 2022, State, District of Columbia, DC, Census Tract [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-2022-state-district-of-columbia-dc-census-tract
    Explore at:
    Dataset updated
    Jan 27, 2024
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Washington, District of Columbia
    Description

    The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

  13. g

    Database for the geologic map of the Washington West 30' x 60' quadrangle,...

    • gimi9.com
    Updated Mar 11, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2025). Database for the geologic map of the Washington West 30' x 60' quadrangle, Maryland, Virginia, and Washington D.C. | gimi9.com [Dataset]. https://gimi9.com/dataset/data-gov_database-for-the-geologic-map-of-the-washington-west-30-x-60-quadrangle-maryland-virginia-/
    Explore at:
    Dataset updated
    Mar 11, 2025
    Area covered
    Maryland, Virginia, Washington
    Description

    The database for the Washington West 30- by 60-minute quadrangle covers an area of approximately 4,884 square kilometers (1,343 square miles) in and west of the Washington, D.C., metropolitan area. The eastern part of the area is highly urbanized, and more rural areas to the west are rapidly being developed. The area lies entirely within the Chesapeake Bay drainage basin and mostly within the Potomac River watershed. It contains part of the Nation's main north-south transportation corridor east of the Blue Ridge Mountains, consisting of Interstate Highway 95, U.S. Highway 1, and railroads, as well as parts of the Capital Beltway and Interstate Highway 66. Extensive Federal land holdings in addition to those in Washington, D.C., include the Marine Corps Development and Education Command at Quantico, Fort Belvoir, Vint Hill Farms Station, the Naval Ordnance Station at Indian Head, the Chesapeake and Ohio Canal National Historic Park, Great Falls Park, and Manassas National Battlefield Park. The quadrangle contains most of Washington, D.C.; part or all of Arlington, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, and Stafford Counties in northern Virginia; and parts of Charles, Montgomery, and Prince Georges Counties in Maryland. The Washington West quadrangle spans four geologic provinces. From west to east these provinces are the Blue Ridge province, the early Mesozoic Culpeper basin, the Piedmont province, and the Coastal Plain province. There is some overlap in ages of rocks in the Blue Ridge and Piedmont provinces. The Blue Ridge province, which occupies the western part of the quadrangle, contains metamorphic and igneous rocks of Mesoproterozoic to Early Cambrian age. Mesoproterozoic (Grenville-aged) rocks are mostly granitic gneisses, although older meta-igneous rocks are found as xenoliths. Small areas of Neoproterozoic metasedimentary rocks nonconformably overlie Mesoproterozoic rocks. Neoproterozoic granitic rocks of the Robertson River Igneous Suite intruded the Mesoproterozoic rocks. The Mesoproterozoic rocks are nonconformably overlain by Neoproterozoic metasedimentary rocks of the Fauquier and Lynchburg Groups, which in turn are overlain by metabasalt of the Catoctin Formation. The Catoctin Formation is overlain by Lower Cambrian clastic metasedimentary rocks of the Chilhowee Group. The Piedmont province is exposed in the east-central part of the map area, between overlapping sedimentary units of the Culpeper basin on the west and those of the Coastal Plain province on the east. In this area, the Piedmont province contains Neoproterozoic and lower Paleozoic metamorphosed sedimentary, volcanic, and plutonic rocks. Allochthonous mélange complexes on the western side of the Piedmont are bordered on the east by metavolcanic and metasedimentary rocks of the Chopawamsic Formation, which has been interpreted as part of a volcanic arc. The mélange complexes are unconformably overlain by metasedimentary rocks of the Popes Head Formation. The Silurian and Ordovician Quantico Formation is the youngest metasedimentary unit in this part of the Piedmont (Pavlides and others, 1980). Igneous rocks include the Garrisonville Mafic Complex, transported ultramafic and mafic inclusions in mélanges, monzogranite of the Dale City pluton, and Ordovician tonalitic and granitic plutons. Jurassic diabase dikes are the youngest intrusions. The fault boundary between rocks of the Blue Ridge and Piedmont provinces is concealed beneath the Culpeper basin in this area but is exposed farther south (Mixon and others, 2000). Early Mesozoic rocks of the Culpeper basin unconformably overlie those of the Piedmont and Blue Ridge provinces in the central part of the quadrangle. The north-northeast-trending extensional basin contains Upper Triassic to Lower Jurassic nonmarine sedimentary rocks. Lower Jurassic sedimentary strata are interbedded with basalt flows, and both Upper Triassic and Lower Jurassic strata are intruded by diabase of Early Jurassic age. The Bull Run Mountain fault, a major Mesozoic normal fault characterized by down-to-the-east displacement, separates rocks of the Culpeper basin from those of the Blue Ridge province on the west. On the east, the contact between rocks of the Culpeper basin and those of the Piedmont province is an unconformity which has been locally disrupted by normal faults. Sediments of the Coastal Plain province unconformably overlie rocks of the Piedmont province along the Fall Zone and occupy the eastern part of the quadrangle. Lower Cretaceous deposits of the Potomac Formation consist of fluvial-deltaic gravels, sands, silts, and clays. Discontinuous fluvial and estuarine terrace deposits of Pleistocene and middle to late Tertiary age flank the modern Potomac River valley unconformably capping these Cretaceous strata and the crystalline basement where the Cretaceous has been removed by erosion. East of the Potomac River, the Potomac Formation is onlapped and unconformably overlain by a westward thinning wedge of marine sedimentary deposits of Late Cretaceous and early and late Tertiary age. Basement rooted Coastal Plain faults of Tertiary to Quaternary age occur along the Fall Zone and this part of the inner Coastal Plain. These Coastal Plain faults have geomorphic expression that appear to influence river drainage patterns (Mixon and others, 1972; Seiders and Mixon, 1981; Fleming and others, 1994).

  14. d

    ACS 5-Year Housing Characteristics DC Ward

    • datasets.ai
    • opendata.dc.gov
    • +4more
    0, 15, 21, 25, 3, 57 +1
    Updated Apr 30, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    District of Columbia (2024). ACS 5-Year Housing Characteristics DC Ward [Dataset]. https://datasets.ai/datasets/acs-5-year-housing-characteristics-dc-ward
    Explore at:
    0, 57, 15, 21, 25, 3, 8Available download formats
    Dataset updated
    Apr 30, 2024
    Dataset authored and provided by
    District of Columbia
    Area covered
    Washington
    Description

    Occupancy status, Units, Rooms, Year built, Owner/Renter (Tenure), Mortgage/Rent costs, 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: 2022 Wards (State Legislative Districts [Upper Chamber])Current Vintage: 2019-2023 ACS Table(s): DP04. 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.

  15. State

    • anrgeodata.vermont.gov
    • atlas-connecteddmv.hub.arcgis.com
    • +4more
    Updated Feb 4, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri (2022). State [Dataset]. https://anrgeodata.vermont.gov/datasets/esri::acs-specific-asian-groups-boundaries?layer=0
    Explore at:
    Dataset updated
    Feb 4, 2022
    Dataset authored and provided by
    Esrihttp://esri.com/
    Area covered
    Description

    This layer shows Asian alone or in any combination by selected groups. 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. The numbers by detailed Asian groups do not add to the total population. This is because the detailed Asian groups are tallies of the number of Asian responses rather than the number of Asian respondents. Responses that include more than one race and/or Asian group are counted several times. 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): B02001, B02011, B02018 (Not all lines of ACS table B02001 are available in this 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.

  16. a

    COUNTIES

    • mce-data-uscensus.hub.arcgis.com
    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • +1more
    Updated Feb 4, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    US Census Bureau (2024). COUNTIES [Dataset]. https://mce-data-uscensus.hub.arcgis.com/maps/USCensus::counties-31
    Explore at:
    Dataset updated
    Feb 4, 2024
    Dataset authored and provided by
    US Census Bureau
    Area covered
    Description

    This layer shows Language Spoken at Home. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the 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 to show the percentage of households with Limited English Speaking Status. 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: 2018-2022ACS Table(s): B16004, DP02, S1601, S1602Data downloaded from: CensusBureau's API for American Community Survey Date of API call: January 18, 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. 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:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, 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 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). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. 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.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

  17. d

    Parcel Lots (Historical)

    • catalog.data.gov
    • opendata.dc.gov
    • +3more
    Updated May 21, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Department of Buildings (2025). Parcel Lots (Historical) [Dataset]. https://catalog.data.gov/dataset/parcel-lots-historical
    Explore at:
    Dataset updated
    May 21, 2025
    Dataset provided by
    Department of Buildings
    Description

    These are lands still within the District of Columbia that has never been subdivided into either Record or Tax Lots through the two offices that manage land records (OS & RPTA), this land is referred to as Parcels, expressed as fractions (Ex Parcel 117/36). In this example, the number “36” would be the 36th out conveyance from original Parcel 117. The tracking of parcels was started in 1905 when, by Act of Congress, all the District’s unsubdivided properties which were mostly rural farms at the time were given parcel numbers. Their boundaries were also depicted (in many cases approximated), in large books in DCRA's Office of the Surveyor. Until the late 1960s, building permits were routinely issued by the city for new construction on Parcels, but today all Parcels, like Tax Lots, must be converted into subdivision Lots of Record before permits will be issued for exterior work. Parcels are only found in the old “County of Washington,” north of Florida Ave and east of the Anacostia River. There are no Parcels found within the original city limits or Georgetown. Parcels are not in Squares. There are examples where parcel land may be physically located in the middle of a city Square, but Parcels are not considered part of a Square until they are duly subdivided by the D.C. Surveyor’s Office.

  18. b

    Demographics By County: United States

    • geo.btaa.org
    Updated Mar 10, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri (2020). Demographics By County: United States [Dataset]. https://geo.btaa.org/catalog/9b15b7ac4e2e4ef7b70ed53a205beff2_1
    Explore at:
    Dataset updated
    Mar 10, 2020
    Authors
    Esri
    Time period covered
    2020
    Area covered
    United States
    Description

    This layer shows demographic context for emergency response efforts.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 to show the percentage of households who do not have access to internet. 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: 2015-2019ACS Table(s): B01001, B08201, B09021, B16003, B16004, B17020, B18101, B25040, B25117, B27010, B28001, B28002 Data downloaded from:Census Bureau's API for American Community SurveyDate of API call: December 12, 2020National 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. 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, seeAccuracy 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 hereto learn more about ACS data releases.Boundaries come from theUS Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintageas 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 2010 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500kTIGER Cartographic Boundary Shapefiles. 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 specificationsdefined by the American Community Survey.Field alias names were created based on the Table Shells file available from theAmerican 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.

  19. g

    PLACES: County Data (GIS Friendly Format), 2021 release

    • gimi9.com
    • data.virginia.gov
    • +3more
    Updated Dec 8, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). PLACES: County Data (GIS Friendly Format), 2021 release [Dataset]. https://gimi9.com/dataset/data-gov_places-county-data-gis-friendly-format-2021-release/
    Explore at:
    Dataset updated
    Dec 8, 2020
    License

    Open Database License (ODbL) v1.0https://www.opendatacommons.org/licenses/odbl/1.0/
    License information was derived automatically

    Description

    This dataset contains model-based county-level estimates for the PLACES 2021 release in GIS-friendly format. PLACES is the expansion of the original 500 Cities Project and covers the entire United States—50 states and the District of Columbia (DC)—at county, place, census tract, and ZIP Code Tabulation Area (ZCTA) levels. It represents a first-of-its kind effort to release information uniformly on this large scale for local areas at 4 geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. Project was funded by the Robert Wood Johnson Foundation (RWJF) in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates include Behavioral Risk Factor Surveillance System (BRFSS) 2019 or 2018 data, Census Bureau 2019 or 2018 county population estimates, and American Community Survey (ACS) 2015–2019 or 2014–2018 estimates. The 2021 release uses 2019 BRFSS data for 22 measures and 2018 BRFSS data for 7 measures (all teeth lost, dental visits, mammograms, cervical cancer screening, colorectal cancer screening, core preventive services among older adults, and sleeping less than 7 hours a night). Seven measures are based on the 2018 BRFSS data because the relevant questions are only asked every other year in the BRFSS. These data can be joined with the census 2015 county boundary file in a GIS system to produce maps for 29 measures at the county level. An ArcGIS Online feature service is also available for users to make maps online or to add data to desktop GIS software. https://cdcarcgis.maps.arcgis.com/home/item.html?id=024cf3f6f59e49fe8c70e0e5410fe3cf

  20. d

    Nation

    • disasterpartners.org
    • partners-arc-nhq-gis.hub.arcgis.com
    • +1more
    Updated May 26, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri (2023). Nation [Dataset]. https://www.disasterpartners.org/datasets/esri::nation-5
    Explore at:
    Dataset updated
    May 26, 2023
    Dataset authored and provided by
    Esri
    Area covered
    Description

    This layer shows total population counts by sex, age, and race groups data from the 2020 Census Demographic and Housing Characteristics. This is shown by Nation, State, County, Census Tract, Block Group boundaries. Each geography layer contains a common set of Census counts based on available attributes from the U.S. Census Bureau. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis.   To see the full list of attributes available in this service, go to the "Data" tab above, and then choose "Fields" at the top right. Each attribute contains definitions, additional details, and the formula for calculated fields in the field description. Vintage of boundaries and attributes: 2020 Demographic and Housing Characteristics Table(s): P1, H1, H3, P2, P3, P5, P12, P13, P17, PCT12 (Not all lines of these DHC tables are available in this feature layer.)Data downloaded from: U.S. Census Bureau’s data.census.gov siteDate the Data was Downloaded: May 25, 2023Geography Levels included: Nation, State, County, Census Tract, Block GroupNational Figures: included in Nation layer The United States Census Bureau Demographic and Housing Characteristics: 2020 Census Results 2020 Census Data Quality Geography & 2020 Census Technical Documentation Data Table Guide: includes the final list of tables, lowest level of geography by table and table shells for the Demographic Profile and Demographic and Housing Characteristics.News & Updates This layer is ready to be used in ArcGIS Pro, ArcGIS Online and its configurable apps, Story Maps, dashboards, Notebooks, Python, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the U.S. Census Bureau when using this data. Data Processing Notes: These 2020 Census boundaries come from the US Census TIGER geodatabases. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For Census tracts and block groups, 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 and block group boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are unchanged and available as attributes within the data table (units are square meters).  The layer contains all US states, Washington D.C., and Puerto Rico. Census tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99). Block groups that fall within the same criteria (Block Group denoted as 0 with no area land) have also been removed.Percentages and derived counts, are calculated values (that can be identified by the "_calc_" stub in the field name). Field alias names were created based on the Table Shells file available from the Data Table Guide for the Demographic Profile and Demographic and Housing Characteristics. Not all lines of all tables listed above are included in this layer. Duplicative counts were dropped. For example, P0030001 was dropped, as it is duplicative of P0010001.To protect the privacy and confidentiality of respondents, their data has been protected using differential privacy techniques by the U.S. Census Bureau.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
D.C. Office of the Chief Technology Officer (2025). Street Right of Way Polygons [Dataset]. https://catalog.data.gov/dataset/street-right-of-way-polygons

Street Right of Way Polygons

Explore at:
Dataset updated
Feb 4, 2025
Dataset provided by
D.C. Office of the Chief Technology Officer
Description

Street right of way polygons are public spaces along the DC managed street segments. A database provided by DDOT identified ROW locations from authoritative source documentation including DDOT surface maps, ROW distribution cards, Subdivision Books in the DC Surveyor's Office, Survey Books, King Plats, Record Books, Street Extension Maps, County Maps, AT Map Books, Wall Books and Wall Reports.

Search
Clear search
Close search
Google apps
Main menu