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.

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.

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.

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.

0.6 meter contours. This dataset contains locations and attributes of 0.6 meter (1.9685 feet) interval topography data, created using bare earth points from the lidar point cloud data.Voids exist in the data due to data redaction conducted under the guidance of the United States Secret Service. All lidar data returns and collected data were removed from the dataset based on the redaction footprint shapefile generated in 2017.

To create this layer, OCTO staff used ABCA's definition of “Full-Service Grocery Stores” (https://abca.dc.gov/page/full-service-grocery-store#gsc.tab=0)– pulled from the Food System Assessment below), and using those criteria, determined locations that fulfilled the categories in section 1 of the definition.Then, staff reviewed the Office of Planning’s Food System Assessment (https://dcfoodpolicycouncilorg.files.wordpress.com/2019/06/2018-food-system-assessment-final-6.13.pdf) list in Appendix D, comparing that to the created from the ABCA definition, which led to the addition of a additional examples that meet, or come very close to, the full-service grocery store criteria. The explanation from Office of Planning regarding how the agency created their list:“To determine the number of grocery stores in the District, we analyzed existing business licenses in the Department of Consumer and Regulatory Affairs (2018) Business License Verification system (located at https://eservices.dcra.dc.gov/BBLV/Default.aspx). To distinguish grocery stores from convenience stores, we applied the Alcohol Beverage and Cannabis Administration’s (ABCA) definition of a full-service grocery store. This definition requires a store to be licensed as a grocery store, sell at least six different food categories, dedicate either 50% of the store’s total square feet or 6,000 square feet to selling food, and dedicate at least 5% of the selling area to each food category. This definition can be found at https://abca.dc.gov/page/full-service-grocery-store#gsc.tab=0. To distinguish small grocery stores from large grocery stores, we categorized large grocery stores as those 10,000 square feet or more. This analysis was conducted using data from the WDCEP’s Retail and Restaurants webpage (located at https://wdcep.com/dc-industries/retail/) and using ARCGIS Spatial Analysis tools when existing data was not available. Our final numbers differ slightly from existing reports like the DC Hunger Solutions’ Closing the Grocery Store Gap and WDCEP’s Grocery Store Opportunities Map; this difference likely comes from differences in our methodology and our exclusion of stores that have closed.”Staff also conducted a visual analysis of locations and relied on personal experience of visits to locations to determine whether they should be included in the list.

This layer is a component of Transportation_WebMercator.

Provided by the Office of the Chief Technology Officer

© DC GIS

The District of Columbia’s Data program is pleased to offer the enterprise GIS geodatabase archive. This product offers a historic snapshot of the DC GIS data. The data consists of the GIS mapping layers and are exported as shapefiles. The date format in the named is "Archive_YYYYMMDD."

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

This application, HistoryQuest DC, is an interactive GIS map that provides historical data on approximately 193,000 extant buildings in Washington, D.C. The map offers several operational layers of information for the user including historic data on individual buildings and historic districts, links to documentation on properties listed in the National Register of Historic Places, information on historic residential subdivisions, and the identification and boundaries of the L’Enfant Plan, and the city’s Squares, and Wards. The featured layer in the map—the Historical Data on DC Buildings—provides information from a variety of sources on original dates of construction, architects, owners and builders of the city’s historic buildings. The application also includes a Query tool that allows the user to analyze the historic data within a specified geographic area or city-wide.This application has evolved out of the DC Historical Building Permits Database, begun in 2002, is on-going. Requests to correct or add new information can be made using the “Propose Data Change” drop-down form located on the banner at the top of the map. For questions or concerns, contact the Historic Preservation Office at historic.preservation@dc.gov.

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.

The interactive zoning map allows users to determine the zoning classification for any property in the District. Users can search zoning by specific address, square and lot, parcel, Zoning Commission (ZC) case, or Planned Unit Development (PUD), where applicable. Users can select different layers of data to display on the map, and can print reports for any selected property. Users should note that when searching for a PUD, the ZC case name and ZC case number reflect the most recent case name and case number associated with the PUD. If you have questions, comments, or suggestions regarding the zoning map, contact the Office of Zoning at (202) 727-6311 or dcoz@dc.gov.

Generalized Policy from the Comprehensive Plan Amendment Act of 2010, effective April 8, 2011.This data set is part of the Comprehensive Plan of the District of Columbia. It categorizes how different parts of the District may change by 2025. It highlights areas where more detailed Comprehensive Plan policies have been provided to manage this change. These policies may generally be found in the ten Area Elements. This dataset should be used to guide land use decision-making in conjunction with the Comprehensive Plan text, the Future Land Use Map, and other Comprehensive Plan maps. Boundaries within the dataset are to be interpreted in conjunction with these other resources in addition to the information shown here.

Embassy locations. The dataset contains locations and attributes of Embassies, 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 Office of the Chief Technology Officer (OCTO) identified Embassy locations and DC GIS staff geo-processed the data to the Master Address Repository (MAR). All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.