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 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.

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.

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.

The Washington DC Area geologic map database (DCDB) provides geologic map information of areas to the NW, W, and SW of Washington, DC to various professionals and private citizens who have uses for geologic data. Digital, geographically referenced, geologic data is more versatile than traditional hard copy maps, and facilitates the examination of relationships between numerous aspects of the geology and other types of data such as: land-use data, vegetation characteristics, surface water flow and chemistry, and various types of remotely sensed images. The DCDB was created by combining Arc/Info coverages, designing a Microsoft (MS) Access database, and populating this database. Proposed improvements to the DCDB include the addition of more geochemical, structural, and hydrologic data.

Census tracts eligible for the Neighborhood Prosperity Fund (NPF), pursuant to DC Official Code §2-1225.21.

This map displays blocks that are part of the RPP program. This map does not necessarily display areas with available RPP parking. Some blocks where residents are eligible for an RPP Permit may have meters or other signage that restrict the usage of RPP Permits.

RPP Permits and Visitor Parking Permits (VPPs) allow parking at green and red RPP zone signs. Please review and follow on-street signage and parking regulations to avoid receiving a citation.

The dataset includes polygons representing the location and attributes of Central Employment Area (CEA). The CEA is the core area of the District of Columbia where the greatest concentration of employment in the city and region is encouraged, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Jurisdictions were identified from public records (map and written description created by the National Capital Planning Commission) and heads-up digitized from the 1995 orthophotographs.

The DC Office of the Chief Financial Officer (OCFO), Office of Tax and Revenue (OTR), Real Property Tax Administration (RPTA) values all real property in the District of Columbia. This public interactive Real Property Assessment map application accompanies the OCFO MyTax DC and OTR websites. Use this mapping application to search for and view all real property, assessment valuation data, assessment neighborhood areas and sub-areas, detailed assessment information, and many real property valuation reports by various political and administrative areas. View by other administrative areas such as DC Wards, ANCs, DC Squares, and by specific real property characteristics such as property type and/or sale date. If you have questions, comments, or suggestions regarding the Real Property Assessment Map, contact the Real Property Assessment Division GIS Program at (202) 442-6484 or maps.title@dc.gov.

Department of Parks and Recreation (DPR) properties identified as polygons. The dataset contains general locations and amenity information about the properties under the jurisdiction of the DC Department of Parks and Recreation. It has been created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. This data is provided by the Department of Parks and Recreation.

Strategic Neighborhood Investment Program (SNIP) - A targeted investment policy wherein priority District areas receive a series of comprehensive public actions or funds to complement and/or catalyze private sector investment. These are not neighborhood boundaries. The Government of the District of Columbia does not provide official neighborhood boundaries.

Data Source: Open Data DC and American Community Survey (ACS) 5-Year Estimates

Why This Matters

Urban green spaces provide an array of health benefits, including protection from extreme heat, reducing stress and anxiety, and offering a place to stay physically active.

Parks can serve as a social gathering space in neighborhoods, offering a location for residents to host events, play sports, and connect with their neighbors. This benefit can be particularly beneficial for elderly individuals as they are more likely to suffer from social isolation.

While the District is considered a national leader in park equity today, this has not always been the case. Until 1954, many DC parks and playgrounds were segregated, either prohibiting their use by Black residents or only allowing them to be used during certain hours.

The District Response

The District consistently ranks well nationally for park equity, receiving a higher Trust for Public Land ParkScore®rating than any other city for four consecutive years (2021-2024). Unlike most cities in the US, District residents have access to a similar amount of park space regardless of their neighborhood’s racial demographics.

The District Department of Transportation’s Urban Forestry Division is on track to reach a goal of tree canopy coverage for 40% of the District, promoting better air quality and cooling our neighborhoods. Residents can also request the planting of a new street tree near them.

The Department of Parks and Recreation and the Department of General Services are modernizing and renovating parks across the District to improve park services, safety, and utilization.

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.

This map shows areas where population and jobs growth will be concentrated in the District through the year 2045.

Wooded areas captured in 1999. Contract NCPC 93-02. This document describes the planimetric map production for the 350 tiles located in Washington DC and the surrounding states of MD and VA.

Obscure Areas captured in 1999. Contract NCPC 93-02. This document describes the planimetric map production for the 350 tiles located in Washington DC and the surrounding states of MD and VA.

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.

District of Columbia COVID-19 total tests 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.

Metropolitan Police Department (MPD) Police Service Areas (PSA). The dataset contains polygons representing of MPD PSA, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Police jurisdictions were initially created selecting street arcs from the planimetric street centerlines and street polygons, water polygons, real property boundaries and District of Columbia boundaries.2019 Boundary Changes:Periodically, MPD conducts a comprehensive assessment of our patrol boundaries to ensure optimal operations. This effort considers current workload, anticipated population growth, development, and community needs. The overarching goals for the 2019 realignment effort included: optimal availability of police resources, officer safety and wellness, and efficient delivery of police services. These changes took effect on 01/10/2019. On 03/27/2019, this boundary was modified to adjust dispatching of North Capitol Street’s northwest access roads to be more operationally efficient.