Zoning Cases

The dataset contains locations and attributes of building construction and alteration permits applied for and approved by the District of Columbia Department of Buildings. These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC.

Campus plans defines University Areas. The dataset contains locations and attributes of University Areas, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of Zoning (DCOZ) and participating D.C. government agencies.

This layer is derived from the Common Ownership Lots and represents property transactions as they’ve occurred since the implementation of the Vector Property Mapping program in September 2006. A property transaction entails new geometry (split/combination of Lot(s) or property type conversion (from Air Rights, Record, or Tax Lots to Condo lots). The layer contains locations and attributes of archived features (inactive lots – dead lots) and corresponds with Office of Tax and Revenue's Public Extract files (ITSPE). It occurs weekly for the current calendar year and geometry updated when a transaction occurs.

These resources offer support to individuals with dementia and their families and/or caregivers, including assistance with education, connection to resources, coordination of services, and coordination of healthcare.

The dataset contains locations and attributes of above ground permits applied for and approved by the District Department of Transportation. They are newly occupied constructions and events. Examples include: moving truck, roll off debris container, moving storage container, construction staging area, mobile crane work zone, other reserved parking. The public space permit process is described on the DDOT website https://ddot.dc.gov. These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC. Use the MAR Geocoderto help complete this.

The dataset contains locations and attributes of blocks, created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and participating DC government agencies. The blocks used street centerlines information from DDOT. Blocks include named alleys in DC (such as 'WALTER ALLEY NE'). A block represents a street segment which usually has two bordering streets. The coordinates for the blocks are located at the midpoint of the street segment. More information on the MAR can be found at https://opendata.dc.gov/pages/addressing-in-dc. The data dictionary is available: https://opendata.dc.gov/documents/2a4b3d59aade43188b6d18e3811f4fd3/explore. In the MAR 2, the BlocksPt is called BLOCKS_PT and is primarily based off of street data from DC Department of Transportation's Roads & Highways database, it also features additional useful information such as created date, last edited date, begin date, and more.