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.

DC celebrates International Open Data Day with events, sessions and activities that include Open Data into them. Open Data Day, or week, is typically observed in the first weeks of March. It is an annual celebration of open data all over the world.

Employment, Commuting, Occupation, Income, Health Insurance, Poverty, and more. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: Census Tracts. Current Vintage: 2019-2023. ACS Table(s): DP03. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 2, 2025. National Figures: data.census.gov. Please cite the Census and ACS when using this data. Data Note from the Census: Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables. Data Processing Notes: This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

The Office of the Chief Technology Officer (OCTO), within the District of Columbia (DC) government, manages the District’s data program. This includes open data, business intelligence, data curation, and Geographic Information Systems (GIS). The open data handbook explains the process and steps the OCTO data program undertakes when an agency submits an open dataset. More importantly, the handbook documents dataset rules, metadata requirements, and policies to make data consistent and standardized. This applies to any dataset submitted for publication on DC’s open data portal.

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.

Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall: maintain an inventory of its enterprise datasets; classify enterprise datasets by level of sensitivity; regularly publish the inventory, including the classifications, as an open dataset; and strategically plan and manage its investment in data.The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. For more information, please visit https://opendata.dc.gov/pages/edi-overview. Previous years of EDI can be found on Open Data.

Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall: maintain an inventory of its enterprise datasets; classify enterprise datasets by level of sensitivity; regularly publish the inventory, including the classifications, as an open dataset; and strategically plan and manage its investment in data.The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. For more information, please visit https://opendata.dc.gov/pages/edi-overview. Previous years of EDI can be found on Open Data.

This template covers section 2.5 Resource Fields: Entity and Attribute Information of the Data Discovery Form cited in the Open Data DC Handbook (2022). It completes documentation elements that are required for publication. Each field column (attribute) in the dataset needs a description clarifying the contents of the column. Data originators are encouraged to enter the code values (domains) of the column to help end-users translate the contents of the column where needed, especially when lookup tables do not exist.

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.

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.

These data represent detailed land cover in Washington, DC. The data were derived using remote sensing technologies on satellite imagery from the Pleiades satellite, flown in 2020 and 2020 DC LiDAR. This dataset provided as an ArcGIS Image service. Please note, the download feature for this image service in Open Data DC provides a compressed PNG, JPEG or TIFF. The full raster GeoTIFF dataset is available under additional options when viewing downloads.

You can use this page to explore Green Infrastructure (GI) practices throughout the District of Columbia. Use the filters to search for GI installed through specific DOEE programs or to search for GI of a specific type. You can also download GI data from the District's publicly-available layer of Best Management Practice (BMP) data.

Enterprise Dataset Inventory as of March 2018. Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall:Maintain an inventory of its enterprise datasets;Classify enterprise datasets by level of sensitivity;Regularly publish the inventory, including the classifications, as an open dataset; andStrategically plan and manage its investment in data.The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. For more information, please visit https://octo.dc.gov/page/district-columbia-data-policy. The latest EDI can be found on Open Data.

Crashes on the roadway blocks network of Washington, DC maintained by the District Department of Transportation (DDOT). In addition to locations, a related table consisting of crash details is available for each crash. This table provides some anonymized information about each of the persons involved in the crash (linked by CRASHID). These crash data are derived from the Metropolitan Police Department's (MPD) crash data management system (COBALT) and represent DDOT's attempt to summarize some of the most requested elements of the crash data. Further, DDOT has attempted to enhance this summary by locating each crash location along the DDOT roadway block line, providing a number of location references for each crash. In the event that location data is missing or incomplete for a crash, it is unable to be published within this dataset. Location points with some basic summary statistics,The DC ward the crash occurredSummary totals for: injuries (minor, major, fatal) by type (pedestrian, bicycle, car), mode of travel involved (pedestrian, bicycle, car), impaired participants (pedestrian, bicyclist, car passengers)If speeding was involvedNearest intersecting street nameDistance from nearest intersectionCardinal direction from the intersectionRead more at https://ddotwiki.atlassian.net/wiki/spaces/GIS0225/pages/2053603429/Crash+Data. Questions on the contents of these layers should be emailed to Metropolitan Police Department or the DDOT Traffic Safety Division. Questions regarding the Open Data DC can be sent to @OpenDataDC

This dataset is a digital hydrologic unit boundary layer for the District of Columbia only - to the watershed (10-digit) 6th level at 1:24,000 scale. It is a clipped version of the regional dataset using the DC Boundary. This data set consists of geo-referenced digital data and associated attributes created in accordance with the FGDC Proposal, Version 1.0 - Federal Standards For Delineation of Hydrologic Unit Boundaries 3/01/02 (https://www.nrcs.usda.gov). The hydrologic unit boundaries provide a uniquely identified and uniform method of subdividing large drainage areas. Polygons are attributed with hydrologic unit codes, names, downstream hydrologic unit, flow modifications, and hydrologic unit type for 4th level (8-digit) sub-basin, 5th level (10-digit) watershed, 6th level (12-digit) subwatershed, and acres for subwatershed.

The Contracts and Procurement Transparency Portal was created by the Office of Contracting and Procurement (OCP) as a public clearinghouse for all information related to the District Government’s contracting and procurement efforts.This portal is broken down into 6 modules, they are as follows: Forecast, Solicitations, Contracts, Purchase Orders, Payments and Independent Agencies. Each of these can be individually download via filters in the application and also in Open Data DC.

Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall:Maintain an inventory of its enterprise datasets;Classify enterprise datasets by level of sensitivity;Regularly publish the inventory, including the classifications, as an open dataset; andStrategically plan and manage its investment in data.The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. For more information, please visit https://octo.dc.gov/page/district-columbia-data-policy. Previous years of EDI can be found on Open Data.

Open Data Handbook Curation Detailed Diagram. DC’s data submission process involves four steps as depicted in this diagram. Overall, the data analysts guide the data owner and other analysts as needed to run the data through the submission process, with different groups leading each part (see all caps in diagram above). Their application occurs in a unified database infrastructure consisting of a data warehouse and geospatial database. While there are specific processes and guidelines for each database, they share an overall setting where consistency and standardization are promoted and supported for their individual data curation processes.

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.

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.