This dataset contains polygons that represent the boundaries of statistical neighborhoods as defined by the DC Department of Health (DC Health). DC Health delineates statistical neighborhoods to facilitate small-area analyses and visualization of health, economic, social, and other indicators to display and uncover disparate outcomes among populations across the city. The neighborhoods are also used to determine eligibility for some health services programs and support research by various entities within and outside of government. DC Health Planning Neighborhood boundaries follow census tract 2010 lines defined by the US Census Bureau. Each neighborhood is a group of between one and seven different, contiguous census tracts. This allows for easier comparison to Census data and calculation of rates per population (including estimates from the American Community Survey and Annual Population Estimates). These do not reflect precise neighborhood locations and do not necessarily include all commonly-used neighborhood designations. There is no formal set of standards that describes which neighborhoods are included in this dataset. Note that the District of Columbia does not have official neighborhood boundaries. Origin of boundaries: each neighborhood is a group of between one and seven different, contiguous census tracts. They were originally determined in 2015 as part of an analytical research project with technical assistance from the Centers for Disease Control and Prevention (CDC) and the Council for State and Territorial Epidemiologists (CSTE) to define small area estimates of life expectancy. Census tracts were grouped roughly following the Office of Planning Neighborhood Cluster boundaries, where possible, and were made just large enough to achieve standard errors of less than 2 for each neighborhood's calculation of life expectancy. The resulting neighborhoods were used in the DC Health Equity Report (2018) with updated names. HPNs were modified slightly in 2019, incorporating one census tract that was consistently suppressed due to low numbers into a neighboring HPN (Lincoln Park incorporated into Capitol Hill). Demographic information were analyzed to identify the bordering group with the most similarities to the single census tract. A second change split a neighborhood (GWU/National Mall) into two to facilitate separate analysis.

The dataset contains locations and attributes of Neighborhood Planning Areas provided by the Office of Planning (DCOP). These do not reflect precise neighborhood locations and do not necessarily include all commonly-used neighborhood designations. There is no formal set of standards that describes which neighborhoods are included in this dataset. Note that the District of Columbia does not have official neighborhood boundaries.

This data set describes Neighborhood Clusters that have been used for community planning and related purposes in the District of Columbia for many years. It does not represent boundaries of District of Columbia neighborhoods. Cluster boundaries were established in the early 2000s based on the professional judgment of the staff of the Office of Planning as reasonably descriptive units of the City for planning purposes. Once created, these boundaries have been maintained unchanged to facilitate comparisons over time, and have been used by many city agencies and outside analysts for this purpose. (The exception is that 7 “additional” areas were added to fill the gaps in the original dataset, which omitted areas without significant neighborhood character such as Rock Creek Park, the National Mall, and the Naval Observatory.) The District of Columbia does not have official neighborhood boundaries. The Office of Planning provides a separate data layer containing Neighborhood Labels that it uses to place neighborhood names on its maps. No formal set of standards describes which neighborhoods are included in that dataset.Whereas neighborhood boundaries can be subjective and fluid over time, these Neighborhood Clusters represent a stable set of boundaries that can be used to describe conditions within the District of Columbia over time.

This dataset was created by the DC Office of Planning and provides a simplified representation of the neighborhoods of the District of Columbia. These boundaries are used by the Office of Planning to determine appropriate locations for placement of neighborhood names on maps. They do not reflect detailed boundary information, do not necessarily include all commonly-used neighborhood designations, do not match planimetric centerlines, and do not necessarily match Neighborhood Cluster boundaries. There is no formal set of standards that describes which neighborhoods are represented or where boundaries are placed. These informal boundaries are not appropriate for display, calculation, or reporting. Their only appropriate use is to guide the placement of text labels for DC's neighborhoods. This is an informal product used for internal mapping purposes only. It should be considered draft, will be subject to change on an irregular basis, and is not intended for publication.

These are the ten planning areas created by the Office of Planning to serve as a static subdivision of the city and allow for analysis across long-term time scales. Unlike election ward boundaries or other political divisions, these areas are intended to remain unchanged and stable. The polygons first appeared in comprehensive plan documents to represent planning areas known as 'Area Elements.'

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: 2022 Wards (State Legislative Districts [Upper Chamber]). 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.

Number of residents who completed the vaccine regimen for COVID-19. Coverage is defined as the number of vaccinated individuals as a proportion of the number of residents living in each neighborhood. The proportion of fully vaccinated residents does not translate to population immunity. Residents who are partially vaccinated may have some level of immunity, immunity may change over time, and non-residents are not be included in the population. Vaccine administration data is reported by facilities and may not be complete.Data is updated on a weekly basis.

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.

This dataset contains areal locations for Major Area Pans as established by the DC Office of Planning. Below are brief descriptions about each area. 1. Benning Road: The study area starts at the Starburst intersection, where Florida Avenue, Bladensburg Road and BenningRoad NE meet, and continues to the Maryland border at Southern Avenue, passing through Wards 5, 6 and 7 along the way. 2. Brookland/CUA Metro Station Area Plan: The boundaries for the immediate Small Area Plan study area for Brookland generally are Taylor Street to the north, 13th street to the east, Rhode Island Avenue to the South and 7th Street to Michigan Avenue to John McCormack Road to the west. 3. Deanwood Strategic Development Plan: The project area consists of Eastern Avenue to the Northeast, 55th Street NE to the East, Marvin Gaye Park to the South, and Kenilworth Avenue/CSX railway to the West. 4. Georgia Avenue - Petworth Metro Station Area Corridor Plan: Project area includes all properties fronting Georgia Avenue, from Decatur Street to Euclid Street in Ward 1; and encompasses approximately 40 blocks. The 4 neighborhood areas are defined as follows: -Upshur (Decatur Street to Shepherd Street) -Petworth-Metro (Shepherd Street to Otis Place) -Park View/Park Morton (Otis Place to Irving Street) -Pleasant Plains (Irving Street to Euclid Street) 5. Kennedy Street: Properties fronting on Kennedy from Georgia to North Capitol Street N. 6. Pennsylvania Avenue SE Land Development Plan: The study area includes all properties fronting on Pennsylvania Avenue SE from Independence Avenue SE/2nd Street SE eastward to Southern Avenue. The study area is more than three miles long and runs through parts of Wards 6, 7, and 8 in the District of Columbia. There are six sub areas located along the study area including: -Southern Avenue to Alabama Avenue (Ward 7) -Alabama Avenue to Branch Avenue (Ward 7) -Branch Avenue to 28th Street (Ward 7) -28th Street to the Sousa Bridge (Ward 8) -Sousa Bridge to 11th Street (Ward 6) -11th Street to 2nd Avenue/Independence Avenue (Ward 6) 7. Riggs Road / South Dakota Avenue: The Office of Planning will undertake a community planning process with area stakeholders (including residents, ANCs, neighborhood organizations, Council staff, businesses, property owners, institutions and government agencies) to develop a Strategic Development Plan and Revitalization strategy for the properties within Wards 4 and 5 within a ¼ mile radius surrounding the Riggs Road and South Dakota Avenue NE intersection. This includes Fort Totten Metro Station. 8. Upper Georgia Avenue Land Development Plan: Project boundaries extends from Decatur Street on the south to Eastern Avenue on the north, including properties along Georgia Avenue from one block to the east and west. 9. St. Elizabeths East Redevelopment Framework Plan: Corner of MLK SE and the alley 1 block north of Lebaum St. SE. Go southeast until Alabama Ave, SE and follow Alabama Ave to just passed the Congress Heights Metro. Head north to corner of Hebrew Cemetery boundary then northeast until Bruce St, SE. Finally, go northwest to intersect with MLK, SE just south of Pomeroy Rd, SE. 10. Anacostia Transit Area Strategic Investment Redevelopment Plan: The study area for the Anacostia Transit Area Framework Plan extends between Fort Stanton Park and Anacostia Park on the east and west, and Good Hope Road and Stevens Road SE on the north and south. 11. Convention Center Area Strategic Development Plan: Bounded by New York Avenue, Massachusetts Avenue, 12th Street, Vermont Avenue, U Street, Florida Avenue, and New Jersey Avenue. The area includes Logan Circle, French Street, Westminster Street, Blagden Alley, O Street Market, East Central, and MountVernon Square. 12. Uptown Destination District Plan (DUKE): Project boundaries Barry Place NW to the north; 6th Street NW to the east; Rhode Island Avenue to the south; and 13th Street to the west. 13. H Street Revitalization Plan: The project boundaries extend along H Street NE from North Capitol Street to 17th Street NE. (13 blocks). 14. Takoma Central District Plan: Project boundaries are defined by the area between Chestnut Street to the north, Eastern Avenue to the east, 4th 5th Streets to the west, and Aspen Laurel Streets to the south.

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: 2022 Wards (State Legislative Districts [Upper Chamber]). 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.

DC 2050 presents an opportunity for the District to identify future challenges and opportunities and consider how to meet them in the next two decades. The DC Office of Planning (OP) will work with residents, community-based organizations, businesses, and elected officials to develop policies that guide how new buildings are added as the District's population and economy grow over the coming years. Through an inclusive and robust public process, the District’s diverse communities will be invited to imagine the kind of city they want for themselves, their neighbors, and their children. Our approach for DC 2050:

The Urban Planning Code defines two types of areas for municipal maps: construction sectors and inconstructible sectors. There are, however, special cases: graphical documents may define areas reserved for industrial or craft activities, in particular those incompatible with the neighbourhood of inhabited areas. They shall define, where appropriate, areas in which the reconstruction of a building destroyed by a disaster is not permitted. Installations necessary for public facilities, agricultural or forestry operations and the development of natural resources are not covered by the principle of inconstructibility resulting from classification. The areas of the communal map do not always cover the entire communal territory. The areas of the municipality not covered by a sector are represented by an object in order to cover the whole municipality. The data relates to all areas of communal maps after assembly. This layer is for informational use, the paper zoning plan remains the effective document.

The Urban Planning Code defines two types of areas for municipal maps: construction sectors and inconstructible sectors. There are, however, special cases: graphical documents may define areas reserved for industrial or craft activities, in particular those incompatible with the neighbourhood of inhabited areas. They shall define, where appropriate, areas in which the reconstruction of a building destroyed by a disaster is not permitted. Installations necessary for public facilities, agricultural or forestry operations and the development of natural resources are not covered by the principle of inconstructibility resulting from classification. The areas of the communal map do not always cover the entire communal territory. The areas of the municipality not covered by a sector are represented by an object in order to cover the whole municipality. The data relates to all areas of communal maps after assembly. This layer is for informational use, the paper zoning plan remains the effective document.

Household type, Education, Disability, Language, Computer/Internet Use, 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: 2018-2022. ACS Table(s): DP02. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 2, 2024. 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.

This downtown boundary was informed by prior defined boundaries of the District’s downtown including DC’s Comeback Plan, Urban Land Institute’s (ULI) Advisory Services Panel Report of the Central Business District Washington, D.C., Business Improvement Districts (BIDs), DC Department of Transportation’s (DDOT) Central Business District Boundary and central business activity. Geographically the area is 2 square miles, or approximately 3% of the District’s total land area. The Downtown boundary overlaps with Wards 2 and 6, and touches Advisory Neighborhood Commission boundaries 2A, 2B, 2C, 2F, 2G, 6C, and 6E.

District of Columbia COVID-19 positive cases reported by DC Health Planning Neighborhoods. Due to rapidly changing nature of COVID-19, data for March 2020 is limited. General Guidelines for Interpreting Disease Surveillance DataDuring a disease outbreak, the health department will collect, process, and analyze large amounts of information to understand and respond to the health impacts of the disease and its transmission in the community. The sources of disease surveillance information include contact tracing, medical record review, and laboratory information, and are considered protected health information. When interpreting the results of these analyses, it is important to keep in mind that the disease surveillance system may not capture the full picture of the outbreak, and that previously reported data may change over time as it undergoes data quality review or as additional information is added. These analyses, especially within populations with small samples, may be subject to large amounts of variation from day to day. Despite these limitations, data from disease surveillance is a valuable source of information to understand how to stop the spread of COVID19.

Occupancy status, Units, Rooms, Year built, Owner/Renter (Tenure), Mortgage/Rent costs, 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): 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.

Civic Initiatives is seeking bids for Project DC: Community Engagement and Master Plan due 2025-07-18T21:00:00.000Z

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: 2023. ACS Table(s): DP05. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 3, 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.