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

Right of Way Scan. Right of Way Distribution Maps, 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. Scans provided by DDOT identified rights of way locations which were best fit to road planimetrics.

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.

This dataset includes all identifiable DCPS public elementary schools, middle schools, education campuses, high schools, and special education schools, as well as learning centers. This dataset does not include private or charter schools. School locations were identified from a database from the District of Columbia Public Schools, Office of Facilities Management.

Zip Codes (5-digit). The dataset polygons represent location and attributes of zip codes, 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. Zip Codes were identified from public records (US Postal Service) and created selecting arcs from the street centerlines and vector property map.

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.

This layer is a subset of ITSPE and and UBIDs representing vacant and blighted property building footprints. The tax assessment roll public extract (ITSPE) is used for assessment and property analysis, to send property tax bills and notices, and stores comprehensive tax information such as ownership, mailing addresses, non-contiguous Air Rights lots (Multifamily or Development), Air Rights lots, possessory interest lots, record lots, tax lots, parcels, condominiums, and federally owned lands such as reservations and appropriations. The linkage from the Vector Property layers to this database is SSL (Square, Suffix, and Lot). The UBID data was originally created by spatially joining the 2019 building footprints published in DC Open Data with the Common Ownership Lots. The UBIDs were coded using US DOE’s Implementation code. Search for UBID and ITSPE in Open Data DC for individual documentation.

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.

Dataset estimates location and size of trees in the District of Columbia that are not managed by the Urban Forestry Division (https://opendata.dc.gov/datasets/urban-forestry-street-trees/explore). Trees are modeled using an automated feature extraction process applied to 2022 LiDAR data. All data is an estimate, and intended for general representation purposes. DC 2022 LiDAR was used and processed using the “Extract Trees using Cluster Analysis” script which is included as part of Esri’s 3D Basemap solution. All LiDAR-derived trees within 2 meters of a Urban Forestry Division tree were removed as being duplicates. Tree diameter (DBH, in inches) was estimated for the LiDAR-derived trees from calculated tree height (in feet) based on the equation: DBH = 0.4003*height - 1.9557. This equation was derived from a statistical analysis of a detailed park inventory tree data set and has an R^2 = 0.7418. Extreme outliers were also modified, with any DBH larger than 80 inches being converted to a DBH of 80 inches.

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.

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.

The dataset contains locations and attributes of Hotels, 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. A database provided by the DC Taxi Commission (DCTC) and research at various commercial websites identified Hotels and DC GIS staff geo-processed the data.

For a city, street blocks are a very common way in which to organize and relate work (e.g. 'I need to fix a pothole on the 1600 Block of Pennsylvania Ave'). Although driveways or alleys may intersect streets, this representation requires that the segment remain unbroken. Road types include streets. Previously Called Street Segments. Note that there are no from/to address fields. We will not be maintaining them in our data. There also will be no generating a 'streetname' list.For more information please visit DDOT's wiki page.

The common ownership lots is a single polygon layer that is built from various polygon feature classes of the District's Vector Property Mapping database including the below. It represents all lands that are outside right-of-way.Record LotsTax LotsParcel LotsReservation LotsAir Rights LotsAll of which are found separately on https://opendata.dc.gov. The Office of Tax and Revenue maintains a database known as Information Tax System (ITS) that contains the accounts for the real property taxes. ITS records reference record lots, tax lots, parcels, condominiums and federally owned lands such as reservations. Information from ITS is conflated to Common Ownership Lot features by SSL (Square, Suffix and Lot). This layer does not include condo records. This layer is regenerated WEEKLY with an automated algorithm using the latest Pubic Extract information for attribution.

Primary care centers where residents can find available health care services in the District of Columbia. The dataset contains locations and attributes of Primary Care Centers, 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. A database provided by the DC Department of Health (DOH) identified Primary Care Centers and DC GIS staff geo-processed the data.

Digital version of the National Park Service Map A, indicating Park Service properties and other government-owned land.

DC Department of Parks and Recreation child care, administrative, maintenance, specialty and recreation centers identified as points. The dataset contains the addresses of these DPR centers, and 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 and contains the location and other information about centers under the jurisdiction of the DC Department of Parks and Recreation.

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://opendata.dc.gov/pages/edi-overview. Previous years of EDI can be found on Open Data DC.