Description: In 2011, the District of Columbia government commissioned a project to survey the Washington D.C. historic boundary stones set in 1791 and 1792 that define the Maryland and (then Virginia) border with the new Federal District. The majority of the stones were located using a field survey which employed a GPS-RTK. Surveyed accuracy is +/- 5cm horizontal and +/- 9cm vertical. The Washington D.C. Historic Boundary Stones were then connected to form the Washington D.C. Historic Boundary. However, this is not used for the planning, administration, or management of Washington D.C. The boundary stones do not form a perfect 10 mile by 10 mile square of DC, and are not perfectly aligned on each side. Given that they were placed over 200 years ago the survey is impressive, however they do not accurately reflect today's DC Administrative Boundary which was produced with more advanced methods and data.Excerpts from Boundarystone.org:The Residence Act of July 16, 1790, as amended March 3, 1791, authorized President George Washington to select a 100-square-mile site for the national capital on the Potomac River between Alexandria, Virginia, and Williamsport, Maryland. President Washington selected the southernmost location within these limits so that the capital would include all of present-day Old Town Alexandria, then one of the busiest ports in the country. Acting on instructions from Secretary of State Thomas Jefferson, Major Andrew Ellicott began his initial observations for a rough survey of the ten-mile square on Friday, February 11, 1791.Ellicott, a prominent professional surveyor, hired Benjamin Banneker, an astronomer and surveyor from Maryland, to make the astronomical observations and calculations necessary to establish the south corner of the square at Jones Point in Alexandria. According to legend, "Banneker fixed the position of the first stone by lying on his back to find the exact starting point for the survey ... and plotting six stars as they crossed his spot at a particular time of night." From there, Ellicott's team embarked on a forty-mile journey, surveying ten-mile lines first along the southwest line, then along The northwest line, next along the northeast line, and finally along the southeast line. The team completed this rough survey in April 1791.Ellicott's team then began the formal survey by clearing twenty feet of land on both sides of each boundary line and placing other stones, made of Aquia Creek sandstone, at one-mile intervals. The boundary stones are the oldest federal monuments. Although several stones have been moved or severely damaged, thirty-six stones from the 1790s are in or near their original locations, including all fourteen in the land that was returned to Virginia in the 1846-1847 retrocession. Three other locations have substitute stones (SW2, SE4, and SE8), and one location (NE1) is marked only by a plaque.Learn more at boundarystone.org.
Copyright Text: Office of the Chief Technology Officer
Description: District addresses for the District Land. The dataset contains of addresses for the District land (Owned, Operated, and Maintained), 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. Databases researched by the DC Office of the Chief Technology Officer (OCTO) identified DC Agency locations and DC GIS staff geo-processed the data.
Copyright Text: Office of the Chief Technology Officer
Description: Affordable housing production and preservation projects are managed by the Department of Housing and Community Development (DHCD), the Deputy Mayor for Planning and Economic Development (DMPED), the DC Housing Authority, the DC Housing Finance Agency and DC's Inclusionary Zoning program. This dataset comprehensively covers affordable housing projects which started (i.e. reached financial closing and/or started construction) or completed since January of 2015. The data includes affordable housing projects (production and preservation, rental and for-sale) which were subsidized by DMPED, DHCD, DCHFA, or DCHA, and those which were produced as a result of Planned Unit Development (PUD) proffers or Inclusionary Zoning (IZ) requirements.
Copyright Text: Office of the Deputy Mayor for Planning and Economic Development
Description: The Office of the Deputy Mayor for Planning and Economic Development (DMPED) is charged with executing the Mayor's economic development strategy. DMPED manages a portfolio of real estate projects located across the District of Columbia. More information is available on the Project Pipeline Database (PPD) Public Access Dashboard.
Description: The Washington DC Economic Partnership (WDCEP) is a non-profit, public-private organization whose core purpose is to actively position, promote, and support economic development and business opportunities in Washington, DC. The data here were used to create the DC Development Report. Check Report Edition Year to filter publications. Visit www.wdcep.com for PDF publications. Although every attempt is made to ensure the quality of the information contained in the DC Development Report, WDCEP makes no warranty or guarantee as to its accuracy, completeness, or usefulness for any given purpose.WDCEP Data Notes:WDCEP data is provided "as is" and WDCEP makes no warranty or guarantee to its accuracy or usefulness for any given purpose. All data are estimates.projects include new construction & major renovationsnew construction does not necessarily mean "net new"estimated delivery dates may reference a first phase delivery or final phase deliverygroundbreaking & delivery dates are only valid for the year (months/days are estimates)pipeline data is subject to changepipeline projects may still need DC Government approval (zoning, DC Council, historic preservation, etc.)
Copyright Text: Washington DC Economic Partnership
Description: All applicants for a Basic Business License operating from a commercial location in the District of Columbia must provide a Certificate of Occupancy (C of O) for the premise address from which the business activity is conducted in order to demonstrate the activity does not conflict with building and zoning codes. A certificate of occupancy is needed to occupy any structure other than a single family dwelling. To include the following uses: two family flat, apartment house, and all commercial uses.
Description: This layer is a subset of ITSPE and and UBIDs representing vacant and blighted property building addresses which are directly correlated with 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.
Copyright Text: Office of the Chief Financial Officer
Description: Alley widths, street frontages, were captured during the vector property effort and reside in their own feature class. 99% of the time, these features should be coincident with the square boundary. The exceptions to this are internal alley’s that might be overlaid by a tax lot. They were captured largely to enable continuity within each square. Alley Polygon does not exist. They could be created with this data by using an automated routine which searches linear feature of the Record, Tax and Parcel Lots feature classes where Line_Classification = 3, 4 and 6, then turning these selected lines into poly’s, another method would be clipping a square boundary with the tax and record lots.
Description: These are lines beyond which property owners or others have no legal or vested rights to extend a building or any part thereof without approval of the proper authorities; ordinarily a line of demarcation between public and private property, but also applied to a building restriction line, when recorded in the records of the Surveyor.
Description: These are not to be confused with utility or private easements. They are often placed after an alley closing for traffic or access. Very few of the actual lines have been captured in this data set.
Description: These are lines that occurred on the city’s 1901-1905 set of master plans for all proposed roads. If a highway planning line crosses a particular property, that land cannot become a Record Lot by subdivision, even if the proposed street is no longer needed or will never be built. However there is a procedure through which a proposed road can be removed from the Highway Plan freeing up affected land for subdivision or development.
Description: Alley Street Changes Lines. The dataset contains locations and attributes of Alley Street Changes Lines, 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. Please visit http://vpm.dc.gov/ for additional information. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.
Copyright Text: Department of Consumer of Regulatory Affairs (DCRA) - Office of the Surveyor (OS), and Office of Tax and Revenue (OTR) - Real Property Tax Administration (RPTA) Office of Chief Technology Officer (OCTO) - DC GIS
Description: District Government Land Line Dimensions. The dataset contains locations and attributes of District properties (Owned, Operated, and Maintained), 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. Databases researched by the DC Office of the Chief Technology Officer (OCTO) identified DC Agency locations and DC GIS staff geo-processed the data. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.
Copyright Text: Department of General Services (DGS)
Description: The dataset contains locations and attributes of owner lines with dimensions. The tax information (attribution) comes from the Office of Tax and Revenue's Public Extract file. The creation of this layer is automated, occurs weekly, and uses the most currently available tax information. The date of the extract can be found in the EXTRACTDAT field in this layer.
Description: A layer showing the District of Columbia government related structures. The dataset contains polygons representing District Government related structures on Government property created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) using the Department of Energy and Environment’s Unique Building Identifier (UBID) data. 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.
Copyright Text: Office of the Chief Financial Officer, Department of Energy and Environment’s, Office of the Chief Technology Officer
Description: This dataset contains polygons that represent the boundaries of assessment subneighborhoods as defined by the DC Office of Tax and Revenue (OTR) Real Property Tax Administration (RPTA). For analysis purposes, RPTA delineates assessment neighborhoods to group properties that are affected by similar economic, political, governmental, and environmental factors. Assessment subneighborhoods are defined by the environment of a subject property that has a direct and immediate effect on its value. The assessment subneighborhood is a geographic area (in which there are typically fewer than several thousand properties) defined for some useful purpose, such as to ensure for later multiple regression modeling that the properties are homogeneous and share important locational characteristics. Assessment neighborhoods boundaries typically follow street centerlines, hydrological boundaries, and boundaries of major properties such as parks and monuments.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.
Description: This dataset contains polygons that represent the boundaries of assessment neighborhoods as defined by the DC Office of Tax and Revenue (OTR) Real Property Tax Administration (RPTA). For analysis purposes, RPTA delineates assessment neighborhoods to group properties that are affected by similar economic, political, governmental, and environmental factors. Assessment neighborhoods are defined by the environment of a subject property that has a direct and immediate effect on its value. The assessment neighborhood is a geographic area (in which there are typically fewer than several thousand properties) defined for some useful purpose, such as to ensure for later multiple regression modeling that the properties are homogeneous and share important locational characteristics. Assessment neighborhoods boundaries typically follow street centerlines, hydrological boundaries, and boundaries of major properties such as parks and monuments.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.
Description: 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.
Copyright Text: Office of the Chief Financial Officer
Description: 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.
Description: This data is used for the planning and management of Washington, D.C. by local government agencies. Alley Street Changes polygons. The dataset contains locations and attributes of Alley Street Changes polygons, 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.
Description: Owner polygons. The dataset contains locations and attributes of owner polygons, 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 tax information (attribution) comes from OTR's Public Extract file. The creation of this layer is automated, occurs weekly, and uses the most currently available tax information. The date of the extract can be found in the EXTRACTDAT field in this layer.
Copyright Text: Department of Consumer of Regulatory Affairs (DCRA) - Office of the Surveyor (OS), and Office of Tax and Revenue (OTR) - Real Property Tax Administration (RPTA) Office of Chief Technology Officer (OCTO) - DC GIS
Description: Military Facilities. The dataset contains locations and attributes of Military Facilities, 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. Information researched by the DC Office of the Chief Technology Officer identified Military Facilities and DC GIS staff geo-processed the data.
Copyright Text: Office of the Chief Technology Officer
Description: When Condos are approved for ground lots, those lots remain in the production (active) layer and attributes updated to reflect Condominium dwelling. 1.) Approved for Ground (Record Lots)When condos are approved for ground lots, the following fields are updated and the“Condo_Lot”field populated with a “Y” valueUNDERLIES_CONDO = 1 CONDO_BOOK_NUMCONDO_PAGE_NUMCONDO_REGIME_NUMCONDOLOT = Y 2.) Approved for Ground (History Record Lots). As some have been replaced (killed) by another Record Lot, that's also a condo lot.When condos are approved for ground lots, the following fields are updated and the “Condo_Lot”field populated with a “Y” valueUNDERLIES_CONDO = 1 CONDO_BOOK_NUMCONDO_PAGE_NUMCONDO_REGIME_NUMCONDOLOT = YWhen Condos are approved for overlay lots, those lots are killed (retired / dead lots) and archived to their respective history layer. 3.) Approved for Overlays (Air Rights & Tax Lots). In the future, Parcels may be used. The following fields are updated and the “Condo_Lot” field populated with a “Y” value UNDERLIES_CONDO = 1 CONDO_BOOK_NUMCONDO_PAGE_NUMCONDO_REGIME_NUMCONDOLOT = YCondo dwellings can also be queried city-wide via the individual VPM layers (active Record lots, dead Air Rights & Tax lots) where the value in the “UNDERLIES_CONDO” field is equal to 1.The following fields are populated once Condo Lots have been approved:Condo_Book_NumCondo_Page_NumCondo_Regime_Num
Description: A layer showing District of Columbia government related properties (owned, operated, and or managed) to be used by many DC Government agencies, private companies and the public. It supports the daily business process of District agencies that originate and manage land records. Transfers of Jurisdiction (TOJ) are also in this layer. This map should not be considered comprehensive as District agencies continuously work to update properties as transactions occur.
Copyright Text: Department of General Services (DGS)
Mayor’s Office for Economic Development (DMPED)
Office of the Chief Technology Officer, Geospatial & BI Program
Office of the Chief Financial Officer, Real Property Tax Administration (RPTA)
Description: Air Right Lots reflect a party’s right to construct an improvement above an existing area of land that is not owned by the constructor. They are a type of development right in real estate referring to the empty space above a property. These are numbered 7000-7999. Non-contiguous Air Rights Lots numbered in 8000 series can either be District owned Multifamily rental units or Existing Development Mixed (residential and commercial).Multifamily 8000 series lots can be proposed development projects that are inclusive of the Mayor’s Office Affordable/Public Housing Initiatives. Additionally, they can either be development sites that are owned by the District and the site is leased to developers. Due to financing and legal requirements, each set of government funded units are required to have separate Parcel ID’s (SSL’s). All the units are rentals, none of the units will be for sale.Existing Development Mixed Use 8000 series lots are residential owner(s) that own both residential and commercial portions. The Lot split is done to ensure each party pays the appropriate real estate taxes assessed to each specific use. There is a master covenant lease outlining property access-rights-use between residential and commercial owner and lease holders. There is also a master lease related to the commercial space where the residential owner is the lease holder.
Description: A history of Tax lots. They are not determined by survey and are therefore not official lots in the same way record lots are. These lots are normally numbered between 800 and 1999 within a square to differentiate them from record lots on the property tax maps. When a tax lot is established by RPTA, an A&T Plat is generated by RPTA and forwarded to the surveyor’s office. These A&T Plats are not reviewed but simply filed by the Surveyor; they do not comply with the standards required of subdivision plats and are not recorded. Tax Lots are not normally acceptable when applying for building permits and must be converted to Record Lots through the normal subdivision process involving the D.C. Surveyor’s Office before permits will be issued. The only exception is if the lot does not face a public street. Furthermore, at the time of their creation and plating, there is no review made of tax lots for compliance with D.C. Zoning, Subdivisions or any other ordinances. These lots are simply pieces of property, owned by somebody, described in deeds, for which tax bills are sent and real estate taxes are collected by the city. Some Record Lots also function in this capacity. Geographically, tax lots typically overlay layers such as record lots or sometimes reservations. There are known instances where tax lots do not overlay these types of layers. Up until approximately 1972, A&T lots were only created by the Tax Assessor out of lands that had been previously Record Lots at some point in their history. For a short period of time in the early to mid-1970s, a decision was made to start eliminating fractional parcels (see definition below) and make them all into A&T lots. The intent was to do away with Parcels altogether and have all properties in the city be either tax lots or record lots. By doing this, they converted unsubdivided parcels into A&T lots where no underlying record lot exists. There is often little or no historical source information about these types of transactions, therefore vectorizing them often requires vast amounts of research.
Description: A history of Parcel Lots. There is still land within the District of Columbia that has never been subdivided into either Record or Tax Lots through the two offices that manage land records (Office of the Surveyor & Real Property Tax Administration). The 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 DOB'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.
Description: In most case scenarios, a piece of property must be a Record Lot before a building permit will be issued for that site in the District of Columbia, and all proposed Record Lots are carefully reviewed by Zoning Administration officials for compliance with the city’s Zoning Ordinances. Other agencies that review new record lots besides OS are Office of Zoning, Office of Planning, the Dept. of Public Works, Historic Preservation, and DDOT.Record lots are defined only when requested by property owners, normally when they are seeking a building permit. Record lots are recorded in Plat Books and Subdivision Books in the Office of the Surveyor. These documents are bound volumes of historical representations of the locations of property lines, and they include record dimensions, though typically no bearings of lines. These lots are located within squares, which usually correspond to one or two city blocks. Certain record lots can also be classified as “of-lots”. An "Of-Lot" is the D.C. Surveyor’s Office term for describing “Remaining/Part of Original Lot X”In the record lots (ply) layer, if a domain value of 1 exist in the “OF_LOT” field, the original lot was modified and should have a corresponding Subdivision. All “of-lots” will also have a tax lot overlaying them since it is a piece or remainder of an original Record Lot.
Color: [104, 104, 104, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 7 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: A history of U.S. Reservations. Lands acquired for use by the Federal Government after the original founding of the city. These were all acquired by the Federal Government through purchase, condemnation, dedication, or gift and almost all the U.S. Reservations in Washington are under the Jurisdiction of the National Park Service. Unlike Appropriations, U.S. Reservations are found throughout the city. The National Park Service also has information for every U.S. Reservation and Appropriation in addition to DOB Office of the Surveyor having some detailed information on transactional history. It should be noted that RPTA has converted some reservations to tax lots for land tracking purposes however the federal government still maintains ownership in many of these cases.
Description: Air Right Lots reflect a party’s right to construct an improvement above an existing area of land that is not owned by the constructor. They are a type of development right in real estate referring to the empty space above a property. These are numbered 7000-7999. Non-contiguous Air Rights Lots numbered in 8000 series can either be District owned Multifamily rental units or Existing Development Mixed (residential and commercial).Multifamily 8000 series lots can be proposed development projects that are inclusive of the Mayor’s Office Affordable/Public Housing Initiatives. Additionally, they can either be development sites that are owned by the District and the site is leased to developers. Due to financing and legal requirements, each set of government funded units are required to have separate Parcel ID’s (SSL’s). All the units are rentals, none of the units will be for sale.Existing Development Mixed Use 8000 series lots are residential owner(s) that own both residential and commercial portions. The Lot split is done to ensure each party pays the appropriate real estate taxes assessed to each specific use. There is a master covenant lease outlining property access-rights-use between residential and commercial owner and lease holders. There is also a master lease related to the commercial space where the residential owner is the lease holder.
Description: DC's Real Property Tax Administration defines assessment and taxation lots, often referred to as A&T lots or simply tax lots. These lots are strictly for real estate taxation purposes and normally defined under two circumstances: When property owners ask for their real property tax bills to be consolidated, after they have bought several contiguous record lots; this is called a combine;When part of a record lot is sold, but no new record lot is yet defined; this is called a split request. Tax lots are not determined by survey, and are therefore not official lots in the same way record lots are. These lots are normally numbered between 800 and 1999within a square to differentiate them from record lots on the property tax maps. When a tax lot is established by RPTA, an A&T Plat is generated by RPTA and forwarded to the surveyor’s office. These A&T Plats are not reviewed but simply filed by the Surveyor; they do not comply with the standards required of subdivision plats, and are not recorded. Tax Lots are not normally acceptable when applying for building permits and must be converted to Record Lots through the normal subdivision process involving the D.C. Surveyor’s Office before permits will be issued. The only exception is if the lot does not face a public street. Furthermore, at the time of their creation and platting, there is no review made of tax lots for compliance with D.C. Zoning, Subdivisions or any other ordinances. These lots are simply pieces of property, owned by somebody, described in deeds, for which tax bills are sent and real estate taxes are collected by the city. Some Record Lots also function in this capacity. Geographically, tax lots typically overlay layers such as record lots or sometimes reservations. There are known instances where tax lots do not overlay these types of layers. Up until approximately 1972, A&T lots were only created by the Tax Assessor out of lands that had been previously Record Lots at some point in their history. For a short period of time in the early to mid 1970’s, a decision was made to start eliminating fractional parcels (see definition below) and make them all into A&T lots. The intent was to do away with Parcels altogether and have all properties in the city be either tax lots or record lots. By doing this, they converted unsubdivided parcels into A&T lots where no underlying record lot exists. There is often little or no historical source information about these types of transactions therefore vectorizing them often required vast amounts of research.
Description: There is still land within the District of Columbia that has never been subdivided into either Record or Tax Lots through the two offices that manage land records (Office of the Surveyor & Real Property Tax Administration). The 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 DOB'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.
Description: In most case scenarios, a piece of property must be a Record Lot before a building permit will be issued for that site in the District of Columbia, and all proposed Record Lots are carefully reviewed by Zoning Administration officials for compliance with the city’s Zoning Ordinances. Other agencies that review new record lots besides OS are Office of Zoning, Office of Planning, the Dept. of Public Works, Historic Preservation, and DDOT.Record lots are defined only when requested by property owners, normally when they are seeking a building permit. Record lots are recorded in Plat Books and Subdivision Books in the Office of the Surveyor. These documents are bound volumes of historical representations of the locations of property lines, and they include record dimensions, though typically no bearings of lines. These lots are located within squares, which usually correspond to one or two city blocks. Certain record lots can also be classified as “of-lots”. An "Of-Lot" is the D.C. Surveyor’s Office term for describing “Remaining/Part of Original Lot X”In the record lots (ply) layer, if a domain value of 1 exist in the “OF_LOT” field, the original lot was modified and should have a corresponding Subdivision. All “of-lots” will also have a tax lot overlaying them since it is a piece or remainder of an original Record Lot.
Description: U.S. Reservations are lands acquired for use by the Federal Government after the original founding of the city. These were all acquired by the Federal Government through purchase, condemnation, dedication, or gift and almost all the U.S. Reservations in Washington are under the Jurisdiction of the National Park Service. Unlike Appropriations, U.S. Reservations are found throughout the city. The National Park Service also has information for every U.S. Reservation and Appropriation in addition to DOB Office of the Surveyor having some detailed information on transactional history. It should be noted that RPTA has converted some reservations to tax lots for land tracking purposes however the federal government still maintains ownership in many of these cases.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: U.S Appropriations are lands set aside at the time of the original founding and platting of the city for use by the U.S. Federal Government. The White House, for instance, Treasury Building, Ellipse and LaFayette Park all sit on Appropriation No. 1. D.C General Hospital is on Appropriation No.13 (with the consent of the Federal Government). Appropriations are often confused with U.S Reservations but the two terms are not interchangeable. There are 17 U.S Appropriations in Washington, D.C., all of which are located within the limits of the Original City and, by definition; there can never be any more.
Copyright Text: Department of Buildings
Default Visibility: false
MaxRecordCount: 2000
MaxSelectionCount: 0
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 0.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports ValidateSQL: true
Supports Calculate: true
Supports Datum Transformation: true
Extent:
XMin: NaN
YMin: NaN
XMax: NaN
YMax: NaN
Spatial Reference: 102100
(3857)
LatestVCSWkid(0)
Description: Squares are calculated by the outer extents of the record or tax lots within a defined area (typically a city block). There are roughly 4896 active squares. A Square is similar to a city block. Squares were numbered starting at 1 and are currently in the 6000 series. Not all squares are active. A common cause of squares becoming inactive has been through street closing and combining squares. When the squares are combined usually the lower square number is killed and the higher square number is used for the combined square. For example if squares 1 and 2 are combined, square 1 is killed and the combination becomes square 2.Spatial locations:Each Square is an Island, alone unto itself. There is not now, and has never been, any citywide Survey Coordinate System in D.C. Most squares are unrelated to other Squares by “Measured.” They are related by Record. Street width is approximate. You cannot rely on the published official street widths to set up property lines or determine right-of-way. There is digital scan information available from DDOT regarding Right-of-Way. Some Squares are divided by streets. That is, the same Square continues on the other side of the street. Since there is no citywide Survey Coordinate System, squares were placed in their approximate location. This process is known as “best fit”.
Description: 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). It should be noted that not all record lots have a direct 1:1 relationship to information in this database. The most obvious examples would be when a tax lot was created from existing record lots. In this case, only the tax lot would have linkage to the ITSPE, not the underlying record lots (though they still exist). Reservations that have been converted into tax lots are an additional example where the reservation still exists, however for taxation purposes the tax lot (overlay) supersedes and has corresponding linkage to ITS. The same is true for most Condominiums and the ground surface lot (Record) which still exist (common space) or the previous overlay (Air Right or Tax lot), only the Condo lot would have linkage to (ITSPE).
Copyright Text: Office of the Chief Financial Officer
Description: This table is a subset of ITSPE and represents vacant and blighted property. 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). It should be noted that not all record lots have a direct 1:1 relationship to information in this database. The most obvious examples would be when a tax lot was created from existing record lots. In this case, only the tax lot would have linkage to the ITSPE, not the underlying record lots (though they still exist). Reservations that have been converted into tax lots are an additional example where the reservation still exists, however for taxation purposes the tax lot (overlay) supersedes and has corresponding linkage to ITS. The same is true for most Condominiums and the ground surface lot (Record) which still exist (common space) or the previous overlay (Air Right or Tax lot), only the Condo lot would have linkage to (ITSPE).
Copyright Text: Office of the Chief Financial Officer
CAREOFNAME
(
type: esriFieldTypeString, alias: Name to whom the tax bill is sent, editable: true, nullable: true, length: 40, defaultValue: null, modelName: CAREOFNAME
)
LOWNUMBER
(
type: esriFieldTypeString, alias: Base House Number of the property address, editable: true, nullable: true, length: 4, defaultValue: null, modelName: LOWNUMBER
)
STREETNAME
(
type: esriFieldTypeString, alias: Street name portion of the property address, editable: true, nullable: true, length: 40, defaultValue: null, modelName: STREETNAME
)
MIX1CLASS
(
type: esriFieldTypeString, alias: Tax class of first mix, editable: true, nullable: true, length: 3, defaultValue: null, modelName: MIX1CLASS
)
MIX1RATE
(
type: esriFieldTypeDouble, alias: Tax rate for first mix, editable: true, nullable: true, defaultValue: null, modelName: MIX1RATE
)
MIX1LNDPCT
(
type: esriFieldTypeDouble, alias: Percentage of the land affected by the first use type, editable: true, nullable: true, defaultValue: null, modelName: MIX1LNDPCT
)
MIX1LNDVAL
(
type: esriFieldTypeDouble, alias: Value of the land affected by the first use type, editable: true, nullable: true, defaultValue: null, modelName: MIX1LNDVAL
)
MIX1BLDPCT
(
type: esriFieldTypeDouble, alias: Percentage of the improvements affected by the first use code, editable: true, nullable: true, defaultValue: null, modelName: MIX1BLDPCT
)
MIX1BLDVAL
(
type: esriFieldTypeDouble, alias: Value of the improvements affected by the first use code, editable: true, nullable: true, defaultValue: null, modelName: MIX1BLDVAL
)
MIX2CLASS
(
type: esriFieldTypeString, alias: Tax class of second mix, editable: true, nullable: true, length: 3, defaultValue: null, modelName: MIX2CLASS
)
MIX2RATE
(
type: esriFieldTypeDouble, alias: Tax rate for second mix, editable: true, nullable: true, defaultValue: null, modelName: MIX2RATE
)
MIX2LNDPCT
(
type: esriFieldTypeDouble, alias: Percentage of the land affected by the second use type, editable: true, nullable: true, defaultValue: null, modelName: MIX2LNDPCT
)
MIX2LNDVAL
(
type: esriFieldTypeDouble, alias: Value of the land affected by the second use type, editable: true, nullable: true, defaultValue: null, modelName: MIX2LNDVAL
)
MIX2BLDPCT
(
type: esriFieldTypeDouble, alias: Percentage of the improvements affected by the second use code, editable: true, nullable: true, defaultValue: null, modelName: MIX2BLDPCT
)
MIX2BLDVAL
(
type: esriFieldTypeDouble, alias: Value of the improvements affected by the second use code, editable: true, nullable: true, defaultValue: null, modelName: MIX2BLDVAL
)
OWNOCCT
(
type: esriFieldTypeInteger, alias: Number of occupied co-op units, editable: true, nullable: true, defaultValue: null, modelName: OWNOCCT
)
COOPUNITS
(
type: esriFieldTypeInteger, alias: Number of available co-op units, editable: true, nullable: true, defaultValue: null, modelName: COOPUNITS
)
SALETYPE
(
type: esriFieldTypeString, alias: Type of property sale, editable: true, nullable: true, length: 30, defaultValue: null, modelName: SALETYPE
)
DEEDDATE
(
type: esriFieldTypeDate, alias: Date of deed, editable: true, nullable: true, length: 8, defaultValue: null, modelName: DEEDDATE
)
ASSESSMENT
(
type: esriFieldTypeDouble, alias: Current Assessed Value Total, editable: true, nullable: true, defaultValue: null, modelName: ASSESSMENT
)
ANNUALTAX
(
type: esriFieldTypeDouble, alias: Current amount of annual tax, editable: true, nullable: true, defaultValue: null, modelName: ANNUALTAX
)
DUEDATE1
(
type: esriFieldTypeString, alias: First due date for bill, editable: true, nullable: true, length: 10, defaultValue: null, modelName: DUEDATE1
)
AMTDUE1
(
type: esriFieldTypeDouble, alias: Bill amount due at first due date, editable: true, nullable: true, defaultValue: null, modelName: AMTDUE1
)
DUEDATE2
(
type: esriFieldTypeString, alias: Second due date for bill, editable: true, nullable: true, length: 10, defaultValue: null, modelName: DUEDATE2
)
AMTDUE2
(
type: esriFieldTypeDouble, alias: Bill amount due at second due date, editable: true, nullable: true, defaultValue: null, modelName: AMTDUE2
)
DUEDATE3
(
type: esriFieldTypeString, alias: Third due date for bill, editable: true, nullable: true, length: 10, defaultValue: null, modelName: DUEDATE3
)
AMTDUE3
(
type: esriFieldTypeDouble, alias: Bill amount due at third due date, editable: true, nullable: true, defaultValue: null, modelName: AMTDUE3
)
TOTDUEAMT
(
type: esriFieldTypeDouble, alias: Total of all liabilities, editable: true, nullable: true, defaultValue: null, modelName: TOTDUEAMT
)
TOTCOLAMT
(
type: esriFieldTypeDouble, alias: Total of all collections, editable: true, nullable: true, defaultValue: null, modelName: TOTCOLAMT
)
TOTBALAMT
(
type: esriFieldTypeDouble, alias: Total balance due for property, editable: true, nullable: true, defaultValue: null, modelName: TOTBALAMT
)
EXTRACTDAT
(
type: esriFieldTypeDate, alias: Date of last extraction from database, editable: true, nullable: true, length: 8, defaultValue: null, modelName: EXTRACTDAT
)
CAPCURR
(
type: esriFieldTypeDouble, alias: Cap assessment for current year, editable: true, nullable: true, defaultValue: null, modelName: CAPCURR
)
CAPPROP
(
type: esriFieldTypeDouble, alias: Cap assessment for proposed year, editable: true, nullable: true, defaultValue: null, modelName: CAPPROP
)
Description: This table is a subset of ITSPE and represents vacant property. 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). It should be noted that not all record lots have a direct 1:1 relationship to information in this database. The most obvious examples would be when a tax lot was created from existing record lots. In this case, only the tax lot would have linkage to the ITSPE, not the underlying record lots (though they still exist). Reservations that have been converted into tax lots are an additional example where the reservation still exists, however for taxation purposes the tax lot (overlay) supersedes and has corresponding linkage to ITS. The same is true for most Condominiums and the ground surface lot (Record) which still exist (common space) or the previous overlay (Air Right or Tax lot), only the Condo lot would have linkage to (ITSPE).
Copyright Text: Office of the Chief Financial Officer
Description: 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). It should be noted that not all record lots have a direct 1:1 relationship to information in this database. The most obvious examples would be when a tax lot was created from existing record lots. In this case, only the tax lot would have linkage to the ITSPE, not the underlying record lots (though they still exist). Reservations that have been converted into tax lots are an additional example where the reservation still exists, however for taxation purposes the tax lot (overlay) supersedes and has corresponding linkage to ITS. The same is true for most Condominiums and the ground surface lot (Record) which still exist (common space) or the previous overlay (Air Right or Tax lot), only the Condo lot would have linkage to (ITSPE). This table has fewer fields than the ITSPE and clarifies the abbreviated column names from the Data Dictionary.
Copyright Text: Office of the Chief Financial Officer
Description: A table with tax rate codes for the Integrated Tax System Public Extract (ITSPE) data layers. The ITS database also processes notices and tax bills. Public extract of the database used for sending tax bills, also known as tax assessment roll. ITS stores comprehensive tax information such as ownership, mailing addresses etc., of record lots, tax lots, parcels, condominiums, and federally owned lands such as reservations and appropriations.
Description: A table with mix tax type codes for the Integrated Tax System Public Extract (ITSPE) data layers. Public extract of the database used for sending tax bills, also known as tax assessment roll. ITS stores comprehensive tax information such as ownership, mailing addresses etc., of record lots, tax lots, parcels, condominiums and federally owned lands such as reservations and appropriations. This database also processes notices and tax bills.
Description: The Regimes are how Office of Tax and Revenue (OTR) quantifies units in a given condo development, grouping of condos. A condo regime number is assigned to each residential condo application or Article of Confederation regardless of how many buildings there are at any one site. The regime number starts with a 1, 2, or 3 depending upon where the condo is located and where they fall in the assessment process of Real Property Tax Assessment (RPTA). All numbers after the first are consecutive. RPTA maintains the master list of Regime numbers for residential properties. Commercial condos are not associated with a Regime number.Condo lots are individual lots for each condominium. The lot numbers normally range from 2000-6999. These condo lots are not geographically defined other than being within a air rights, record, tax or a combination of lots that has one or more condo buildings within it.
Description: Data source is the Office of Tax and Revenue’s Computer-Assisted Mass Appraisal (CAMA) system. The CAMA system is used by the Assessment Division (AD) within the Real Property Tax Administration to value real estate for ad valorem real property tax purposes. The intent of this data is to provide a sale history for active properties listed among the District of Columbia’s real property tax assessment roll. This data is updated daily. The AD constantly maintains sale data, adding new data and updating existing data. Daily updates represent a “snapshot” at the time the data was extracted from the CAMA system, and data is always subject to change.
Copyright Text: Office of the Chief Financial Officer
Description: Data source is the Office of Tax and Revenue’s Computer-Assisted Mass Appraisal (CAMA) system. The CAMA system is used by the Assessment Division (AD) within the Real Property Tax Administration to value real estate for ad valorem real property tax purposes. The intent of this data is to provide a sale history for active properties listed among the District of Columbia’s real property tax assessment roll. This data is updated daily. The AD constantly maintains sale data, adding new data and updating existing data. Daily updates represent a “snapshot” at the time the data was extracted from the CAMA system, and data is always subject to change.
Copyright Text: Office of the Chief Financial Officer
Description: Data source is the Office of Tax and Revenue’s Computer-Assisted Mass Appraisal (CAMA) system. The CAMA system is used by the Assessment Division (AD) within the Real Property Tax Administration to value real estate for ad valorem real property tax purposes. The intent of this data is to provide a sale history for active properties listed among the District of Columbia’s real property tax assessment roll. This data is updated daily. The AD constantly maintains sale data, adding new data and updating existing data. Daily updates represent a “snapshot” at the time the data was extracted from the CAMA system, and data is always subject to change.
Copyright Text: Office of the Chief Financial Officer
Description: The table represents documentation (Book & Page) approved for condominium development. Projects can be built in multiple phases and thus the potential for several condo subdivisions per on dwelling. Users can join this table with the following map and table layers:Common Ownership LotsVector Property Map LayersCondo Approval Lots Condo Relate Table to view all related condo subdivsions
Copyright Text: Office of the Chief Technology Officer
Description: The Washington DC Economic Partnership (WDCEP) is a non-profit, public-private organization whose core purpose is to actively position, promote, and support economic development and business opportunities in Washington, DC. The data here were used to create the DC Development Report. Check Report Edition Year to filter publications. Visit www.wdcep.com for PDF publications. Although every attempt is made to ensure the quality of the information contained in the DC Development Report, WDCEP makes no warranty or guarantee as to its accuracy, completeness, or usefulness for any given purpose.WDCEP Data Notes:WDCEP data is provided "as is" and WDCEP makes no warranty or guarantee to its accuracy or usefulness for any given purpose. All data are estimates.projects include new construction & major renovationsnew construction does not necessarily mean "net new"estimated delivery dates may reference a first phase delivery or final phase deliverygroundbreaking & delivery dates are only valid for the year (months/days are estimates)pipeline data is subject to changepipeline projects may still need DC Government approval (zoning, DC Council, historic preservation, etc.)
Copyright Text: Washington DC Economic Partnership
Description: Exemption From DC Real Property Tax is for use by nonprofit organizations who wish to apply for exemption from the District of Columbia real property tax, must own the real property for which the request is made, and qualify under DC Official Code § 47-1002. The applicant must specify the subsection of § 47-1002, detailing the major categories of exempt property, pursuant to which the exemption is sought. Current and proposed use of the property must be indicated, and a physical inspection of the property by this office is required. If any part of the property is leased, the tenant must supply the same types of documents that the owner must furnish with this application. Applications for exemption for property owned by foreign governments must be made through the US Department of State, Office of Foreign Missions. The exemption, if approved, will commence the first full month following the date the application is approved, provided the requirements for exemption are met. The tax type values for properties are: DC, E0-E9 and US.
ASSESSMENT_LAND
(
type: esriFieldTypeDouble, alias: Assessed land value by fiscal year, editable: true, nullable: true, defaultValue: null, modelName: ASSESSMENT_LAND
)
ASSESSMENT_IMP
(
type: esriFieldTypeDouble, alias: Assessed improvement value by fiscal year, editable: true, nullable: true, defaultValue: null, modelName: ASSESSMENT_IMP
)
TOT_ASSESSMENT
(
type: esriFieldTypeDouble, alias: Assessed value of land and building by fiscal year, editable: true, nullable: true, defaultValue: null, modelName: TOT_ASSESSMENT
)
CREATE_DATE
(
type: esriFieldTypeDate, alias: Date when lot was created, editable: true, nullable: true, length: 8, defaultValue: null, modelName: CREATE_DATE
)
Description: Table defining the fields for the attribute table of the owner points feature. It reflects the new table structure OTR adopted in Tax Year 2005 reflecting the systems update to the public release file.
Description: The Property Use Code table contains a code, brief description and long description of DC's property use code system. It provides a complete set of the currently available use codes (with their descriptions) that are applicable to various categories of property. A property use code identifies the predominant use of a parcel of real property (and in certain limited instances, other property characteristics are also identified). Visit http://otr.cfo.dc.gov/publication/real-property-use-code-listing for more info.
Description: The Condo Relate table contains attributes of air rights, record, and tax lots approved for active condos. Condominium documentation (Condo Book & Page) is approved and recorded by the DC's Surveyors Office (OS) for the DC's Department of Buildings (DOB) . Real Property Tax Administration's (RPTA) Maps & Title division receives copies of the approved Condominium documents from OS and reviews, records, and then ties the Condo book & page information to the Lot(s) of interest, i.e., (Air Rights, Record, Tax, or a combination) for the Office of Tax and Revenue (OTR).