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.

This data shows planned multiuse trails in the District. The map shows trails that are both funded and unfunded, and in various phases of design or study.

Hydro-Flattened Bare Earth DTM. The dataset was created using the lidar bare earth points and 3D hydro breaklines to a resolution of 1 m (April 2018). 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.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/WashingtonDC/MD_washingtonDC_aspect_m/ImageServer

Welcome to the Office of Planning Demographic Data Hub - your one-stop shop for data, analyses and resources covering District of Columbia residents. Please explore the five main sections below and print, share or download your selections.

Census Year 1930 Census Tracts. The dataset contains polygons representing CY 1930 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. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

Data has been updated to include agency budget code, name, and acronym attributes. Budget codes were used to assign the agency name and acronym to each record. Agencies that share the same budget code, such as those under the Executive Office of the Mayor, were left blank in PASS records. For questions regarding details within the data, contact the Office of Contracting and Procurement at https://contracts.ocp.dc.gov/contact.

Here is a description of the DC boundary

The dataset contains locations and attributes of Vehicle Detection Systems, created from a database provided by the District Department of Transportation.

If a business or unregistered entity (sole proprietor, general partnership etc.) wishes to do business under a name that is different than their registered name or true legal name, they may register a trade name. A trade name or a “Doing Business As” name is optional and is not required in order to conduct business in DC. However, if a sole proprietor, general partnership or registered entity is using a trade name, it must be registered and on record with Corporations Division.The dataset contains the following columns: trade names, effective date, trade name status, file number, trade name expiration date, and initial file number. More information can be found at https://dlcp.dc.gov/node/1619191

Create your own initiative by combining existing applications with a custom site. Use this initiative to form teams around a problem and invite your community to participate.

Polygons in this layer represent Census Tracts in the DMV (DC, Maryland, and Virginia). Data are included for each tract which estimate hunger and food insecurity. Data were compiled by the CAFB through internal tracking, and the layer was shared with the DC government as a courtesy. Fields include (all available for 2015 and 2014):15_FI_Rate: The estimated portion of the population in the census tract experiencing food insecurity (by CAFB standards). 15/14 indicates year measured.15_FI_Pop: The estimated number of people in the census tract experiencing food insecurity (by CAFB standards). 15/14 indicates year measured.15_LB_Need: The estimated pounds of food needed by the food insecure population in the census tract. 15/14 indicates year measured.15_Distrib: The number of pounds of food distributed by CAFB and partners in the census tract. 15/14 indicates year in which the distribution took place.15_LB_Unme: The difference between the estimated pounds of food needed and the real pounds of food distributed by CAFB and partners, representing the unmet need for food assistance in the census tract. 15/14 indicates year.The layer was shared with the DC government in May 2016 and is based on 2015 and 2014 data.

Barbershops that participate CFMB’s Books and Barbershops program. Barbershops have always been a culturally significant place for men to gather and discuss current events, politics, and sports. It’s a place where fathers spend time with their children and where boys learn to become men. Now it is a place for reading and learning too. Books and Barbershops is a community visibility program that raises awareness on the value of academic mentoring, specifically in the area of early childhood literacy.

2019 Orthophoto - 3 inch resolution imagery service. Data produced for the District of Columbia from 2019 digital aerial photography. Flight took place on April 23rd, 2019. Further details included in download XML file. The aerial imagery acquisition was flown to support the creation of 4-band digital orthophotography with a 3 inch/0.08 meter pixel resolution over the full project area covering the District of Columbia which is approximately 69 square miles. The contractor received waivers to fly in the Flight Restricted Zone (FRZ) and P-56 areas. The ortho imagery was submitted to the District's Chief Technology Office (OCTO) in GeoTiff/TFW format tiles following the tile scheme provided by OCTO. MrSID and JPEG2000 compressed mosaics were delivered as well using a 50:1 compression ratio. All District geospatial data is stored and exported in Maryland State Plane coordinates NAD 83 meters. 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 compressed MrSID or JPEG2000 mosaic raster datasets are available under additional options when viewing downloads. Requests for the individual GeoTIFF set of images should be sent to open.data@dc.gov.

HUBZone is a United States Small Business Administration (SBA) program for small companies that operate and employ people in Historically Underutilized Business Zones (HUBZones). The HUBZone program was created in response to the HUBZone Empowerment Act created by the US Congress in 1998. These areas offer incentives to new small businesses.

The District Department of Transportation (DDOT) launched DC Streetcar in February 2016 after more than 50 years. The rebirth of the streetcar emerged out of a mid-2000s planning effort to shape the future of transit in the city. The comprehensive District of Columbia Transit Improvements Alternatives Analysis  studied gaps in transit and identified ways to better meet the needs of residents. From there, DDOT focused on expanding transit service with the DC Circulator, express Metrobus routes, bus rapid transit, Capital Bike Share, and DC Streetcar. The streetcar offers an array of benefits. A fully envisioned streetcar system makes it easier for residents to move between neighborhoods and spurs economic development. Unlike buses, fixed rail lines attract long-term community investments in housing, retail, and commercial properties.

The dataset contains locations and attributes of car sharing locations. The points are the general locations where the Car Sharing currently exist. A database provided by the District Department of Transportation identified Car sharing locations.

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