District of Columbia boundary. The dataset is a polygon representing the District of Columbia boundary, 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. The boundary was identified from public records and heads-up digitized using a combination of the 1995 orthophotographs, planimetric roads features, and the USGS digital raster graphic quad sheets, and 1999 planimetrics for the Potomac River boundary.Also see the District's Boundary Stone markers.

Property and parcel data is a critical layer to any city or statewide data holdings. In our city's complex urban environment, this includes numerous geographies that identify federal government lands, reservations, District lands, personal property and so much more. Use this application to query and identify boundaries including,Property LotsLot DimensionsCondo DataTax AssessmentsZoningSquaresThe District's Vector Property Mapping (VPM) project works daily to capture property lot transactions so that city planners, business development leaders and residents stay current.

The DC Basemap provides a reference map for the District of Columbia projected in Web Mercator. Access the ArcGIS Rest endpoint. The basemap utilizes the most current planimetric and reference data available and represents the real world with foundation map layers derived from base data collection done in 2023.The service is provided by the Office of the Chief Technology Officer.

This dataset contains points representing Metro Stations within the District of Columbia. Station centroids were identified from visual observation of orthophotography and extracted from the planimetric data.

The dataset contains location and attributes of traffic signals, a power-operated traffic control device by which traffic is warned or directed to take some specific action, located at each intersection in the District of Columbia. These devices do not include power-operated signs, steadily-illuminated pavement markers, warning lights, or steady burning electric lamps. The dataset is related to the traffic pole data.

The dataset contains locations and attributes of address points, created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and Department of Buildings (DOB). It contains the addresses in the District of Columbia which are typically placed on the buildings. Visit opendata.dc.gov/pages/addressing-in-dc#documentation for more information on the MAR.

The dataset contains polygons representing boundaries of District of Columbia 2022 election Wards. Boundaries include Census 2020 demographic data for population, age, race and housing. In the United States Census, Wards are the area name-Legal Statistical Area Description (LSAD) Term-Part Indicator for the District of Columbia.

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.

Historical Data on the Buildings of Washington DC, collected over 15 years by Brian Kraft, with support from JMT Inc., for the DC Historic Preservation Office. Most of the data comes from the building permits issued by the city, especially from 1877 to 1949. Sources are named for all buildings and other sources include real estate maps, tax assessments, newspaper reports, and the DC Office of Tax and Revenue, mostly for buildings after 1949. Work on this data is ongoing but we feel that this will be a valuable and enjoyable research tool as it is.

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.

A generalized dataset of existing land use in the District of Columbia as existed during its most recent extract of the common ownership lots. This dataset is different from the Comprehensive Plan - Future Land Use, which shows land use as envisioned in the latest version of DC’s Comprehensive Plan. The primary land use categories used in this dataset are similar, but not identical. The Office of the Chief Technology Officer (OCTO) compared two datasets to create this generalized existing land use data. The data source identifying property use is the Property Use Code Lookup from the Office of Tax and Revenue (OTR). An index provided by the Office of Planning assigns each OTR property use code with a “primary land use” designation. Through an automated process, the common ownership lots were then joined with this index to create the Existing Land Use. Only properties with an assigned use code from OTR are categorized. Other properties without a use code were left as NULL. Many of these tend to be public lands such as national parks. Refer to https://opendata.dc.gov/pages/public-lands.This dataset has no legal status and is intended primarily as a resource and informational tool. The Office of the Chief Technology Officer anticipates replicating this work annually.

Census Year 1970 Census Tracts. The dataset contains polygons representing CY 1970 census tracts, created as part of the D.C. Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Census tracts were identified from maps provided by the U.S. Census Bureau and the D.C. Office of Planning. The tract polygons were created by selecting street arcs from the WGIS planimetric street centerlines. Where necessary, polygons were also heads-up digitized from 1995/1999 orthophotographs.

Map of Washington DC from 1792

Alley Street Changes Lines. The dataset contains locations and attributes of Alley Street Changes Lines, 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.

The Light Gray DC Basemap provides a reference map for the District of Columbia projected in Web Mercator. Access the ArcGIS Rest endpoint. The basemap utilizes the most current planimetric and reference data available and represents the real world with foundation map layers derived from base data collection done in 2023. The service is provided by the Office of the Chief Technology Officer.

Proposed boundaries of the State of Washington DC and Federal District as approved by DC Council on October 18, 2016. Read the complete testimony from the DC Office of Planning at: Office of Planning Proposed New Columbia Boundaries. A revised version of this boundary was created by legislation passed by the US House of Representatives in 2020.

Roads. The dataset contains polygons representing planimetric roads, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO). These features were originally captured in 2015 and updated in 2017. The following planimetric layers were updated: - Barrier Lines- Building Polygons- Bridge and Tunnel Polygons- Curb Lines- Grate Points- Horizontal and Vertical Control Points- Hydrography Lines- Obscured Area Polygons- Railroad Lines- Recreational Areas- Road, Parking, and Driveway Polygons- Sidewalk and Stair Polygons- Swimming Pools- Water Polygons

The Washington DC boundary was created by connecting all of the boundary stone locations into a single polygon.

This layer is a component of Transportation_WebMercator.

Provided by the Office of the Chief Technology Officer

© DC GIS