20260407
12180100
FALSE
20260414
15480700
20260414
15480700
1.0
OwnerPLY_PF
002
1278394.807728
1338186.693721
413346.350397
484118.378800
1
Projected
GCS_North_American_1983
Linear Unit: Foot_US (0.304801)
NAD_1983_StatePlane_Maryland_FIPS_1900_Feet
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.2.0'><WKT>PROJCS["NAD_1983_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1312333.333333333],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-77.0],PARAMETER["Standard_Parallel_1",38.3],PARAMETER["Standard_Parallel_2",39.45],PARAMETER["Latitude_Of_Origin",37.66666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2248]]</WKT><XOrigin>-120561100</XOrigin><YOrigin>-95444400</YOrigin><XYScale>3048.0060960121905</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.00328083333333333</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102685</WKID><LatestWKID>2248</LatestWKID></ProjectedCoordinateSystem>
150000000
5000
dataset
external
3cf56e1fc8cc8205cbc5981374be7a2dd7af6e10
Office of the Chief Technology Officer
(202) 727-2277
200 I Street SE
Washington
DC
20003
US
dcgis@dc.gov
8:30 am - 5 pm
GIS Data Coordinator
GIS Data Coordinator
True
Office of the Chief Technology Officer
20260414
ArcGIS Metadata
1.0
Department of Buildings
Chief Building Officer
Common Ownership Lots
2026-05-06T06:30:30
2005-01-01T00:00:00
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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.</SPAN></P><UL><LI><P><SPAN>Record Lots</SPAN></P></LI><LI><P><SPAN>Tax Lots</SPAN></P></LI><LI><P><SPAN>Parcel Lots</SPAN></P></LI><LI><P><SPAN>Reservation Lots</SPAN></P></LI><LI><P><SPAN>Air Rights Lots</SPAN></P></LI></UL><P><SPAN>All of which are found separately on </SPAN><A href="https://opendata.dc.gov:443/" STYLE="text-decoration:underline;"><SPAN>https://opendata.dc.gov</SPAN></A><SPAN>. 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.</SPAN></P></DIV></DIV></DIV>
A single polygon layer that is created from various polygon feature classes of the District's Vector Property Mapping database.
Department of Buildings
Cadastral
Land
Lot
Property
Square
DC
District of Columbia
Land
Lot
planning cadastre
Property
Square
vpmdata
Washington DC
DOB
parcel
tax
record
air right
reservations
DC Geographic Information System
DC GIS
vector digital data
The Vector Property data was developed with the oversight of the Office of the Chief Technology Officer (OCTO) - DC GIS, Department of Buildings (DOB) - Office of the Surveyor (OS), and Office of Tax and Revenue (OTR) - Real Property Tax Administration (RPTA). This effort was undertaken with 2 primary goals: - Support and improve the daily business processes of the two DC agencies that originate and manage land record in the District of Columbia. - Provide important GIS base layers which will be used extensively by many DC government agencies and private companies. Below are the responsibilities which DC agencies have provided throughout the Vector Property data creation and maintenance application lifecycle. Office of the Surveyor- subject matter expertise, provides access and understanding of source documents, extensive resource support, and assists with Vector Property GDB and Maintenance requirements. RPTA- subject matter expertise, provides access and understanding of source documents, extensive resource and IT support, and assists with Vector Property GDB and Maintenance requirements. OCTO- Assists with Geodatabase and Maintenance requirements, QC and Program Management staffing. Vector Property database and Citrix Support. Project oversight. Air Rights (AirRightsLotsPT, AirRightsLotsLN, AirRightsLotsPLY) - Air right lots are established by RPTA to 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 about a property. These tax lot numbers start at 7000. There are approximately 704 air rights lots. Air rights are taxed in DC.
Condo Approval Lots - 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. 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 tri-annual assessment process of 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 and in order to properly track all condos, a unique Regime number was created. RPTA then establishes individual accounts for each condominium unit and assigns a condo lot number to that account. RPTA maintains the master list of Regime numbers and their relationship to approved condos. There are roughly 66571 condo lots and there associations are as follows: 49486 condos were approved for record lots, 16867 were approved for tax lots, 2817 were approved for air rights lots, and 2600 were approved for both air rights and tax lots. The CondoPly layer was created to assist users in visualizing the relationship between ground surface lots (Record Lots), overlay lots (Air Rights & Tax Lots), and the associated Condos. When Condos are approved for ground lots, those lots remain in the production (active) layer and attributes updated to reflect the new condos. When Condos are approved for overlay lots, those lots are killed (dead lots) and archived to their respective history layer. Condo 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.
Parcel Lots (ParcelsLotsPT, ParcelsLotsLN, ParcelsLotsPLY) - 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 (OS & RPTA), this 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.
Record Lots - Record lots are defined by the Department of Buildings (DOB) – Office of the Surveyor (OS) - DC Surveyor. They are official, platted, recorded subdivision lots created by the D.C Surveyor’s Office in compliance with the Subdivision Ordinance of the District of Columbia (must have public street frontage, etc.). Typically, these lots are numbered 1 through 799 with no number being used more than once in a Square. Exceptions to this rule:
• When the 1-799 range has been exhausted within a square, the Surveyor’s Office assigns numbers from 1200 or may even use 8000 and above
• For reasons unknown, 42 Squares have record lot numbers greater than 799 but less than 1200 Additionally, 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 lot feature class, if a domain value of 1 resides in the “OF_LOT” field, you can assume that at one time the original lot was modified. Typically, any of these of-lots will also have a tax lot overlaying them since it is a piece or remainder of a Record Lot.
Tax Lots (TaxLotsPT, TaxLotsLN, TaxLotsPLY) - RPTA 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 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 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 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 required vast amounts of research.
Reservations - 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 of 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.
Squares (SquaresPT, SquaresLN, SquaresPLY) - 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 Location of Squares
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”.
Appropriations - 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 Square 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.
OwnerPly - Is a single polygon feature class that is built from various polygon feature classes of the Vector Property Mapping Program. The purpose of the layer is to represent all lands that are outside right-of-way. 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 OwnerPly features by SSL (Square, Suffix and Lot). This ownership layer has a point for all properties including condominiums and un-taxed federal properties with selected tax assessment information attached as attributes. NOTE: the OwnerPly does not include condo records. These can be found in condo relate tables. This layer is regenerated WEEKLY with an automated algorithm using the latest Pubic Extract information for attribution. In March and September, the ITS Public Extract file is frozen for 4-5 weeks for processing during billing periods.
AlleyLns (AlleyLN, AlleyPLY) - 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 alleys 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 polys, another method would be clipping a square boundary with the tax and record lots.
Building Restriction Lns - 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.
Highway Planning Lns - There 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.
Public Easement Lns (PublicEasementsLN) - These are not to be confused with utility or private easements. They are often placed after an alley closing for traffic or access.
Esri ArcGIS 13.2.0.49743
1
-77.119414
-76.909034
38.995977
38.801593
Washington DC
2005-01-01T00:00:00
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This work is licensed under a </SPAN><A href="https://creativecommons.org:443/licenses/by/4.0" STYLE="text-decoration:underline;"><SPAN>Creative Commons Attribution 4.0 International License</SPAN></A><SPAN>.</SPAN></P></DIV></DIV></DIV>
Department of Buildings
Chief Building Officer
Department of Buildings
external
3cf56e1fc8cc8205cbc5981374be7a2dd7af6e10
Office of the Chief Technology Officer
(202) 727-2277
200 I Street SE
Washington
DC
20003
US
dcgis@dc.gov
8:30 am - 5 pm
GIS Data Coordinator
GIS Data Coordinator
True
Office of the Chief Technology Officer
Last metadata review date: 09/21/2022
Vector Property Map QA/QC 1.) Specifications: Projection Parameters: Coord. System - NAD83, StatePlane, MD, FIPS 1900, meters. Correct Extent and Mapping Tolerances: Mapping tolerances implicitly define accuracy and precision of the vector feature datasets. Min X: 389000, Max X: 408000, Min Y: 124700, Max Y: 147900 Precision: 92563.95 (close to 5 decimals of precision) Cluster Tolerance: .003048006 2.) QA/QC Steps Attribute Verification - Database Structure, Domain Values, Field Population Topological Consistency - Verified Topology against a list of rules, as follows: Source Checks Squares were reviewed against their respective source documents (Record Lots- Subdivision Plats, Tax Lots- A&T Plats) and checked for the following: - Ensure all lots were captured for each square - Check all lot line dimensions and square footages - Check for missing building restriction lines on original source plats - Check for proper lot bearings - Insure correct units were captured Squares and Lots Best Fit - Check each squares best fit against the 2002 imagery and ground level features such as curb, sidewalk and buildings. Errors found during DC QC process were cycled back to vendor until all correction had been completed.
Data is mostly complete thru April 2008. There are approximately 80 squares with remaining transactions that need to be completed to bring the entire dataset current thru this date. The following issues exist in the property data: 1.) Some squares contain COGO linework entered using degress, minutes, and seconds, as opposed to decimal degrees. This causes spatial inaccuracies that grow as the length of the line gets longer. 2.) Squares with alley/street closings/dedication transactions are currently being processed. 3.) Not all Parcels that reside outside of a Square(s) boundary have been processed/created. 4.) Not all Reservations have been processed/created. 5.) Individual edits that still need to be made are contained in the transaction table (VPM_Updates) which is available on DC Central's geospatial database. Other 1.) Alleys, Building restriction lines, Highway Plans, and Easements are captured if they were on the source material. Source material is active as of November 2002. It is known that not all of these features were captured. 2.) Street width is approximate. Users should rely on the published official street widths to set up property lines or determine right-of-way (this is from the DC Land Surveyors Hand Book). Likewise this should be taking into consideration when doing certain types of GIS analysis utilizing the VP data. 3.) Some Squares are divided by streets. That is, the same Square continues on the other side of the street. 4.) Not all of the fields are currently populated. The remainder of the attribution will be populated once the servers are returned from the vendor containing the source files. 5.) Efforts are being made to bring all layers current.
Validated by source and/or responsible agency
Since squares are islands and not generated from ground features, staff "best fit" each square to the Earth. Since there is no citywide Survey Coordinate System, squares are placed in their approximate location. Once a square was COGO'ed/created it became a "floating islands" without geographic positioning. Because of this, captured property data had to be positioned relative to other geospatial files that themselves are geo-referenced. Thus, they were fit to the digital ortho's and planimetrics compiled at a scale of 1:100 or 1" ='s 83.3ft. Squares were visually positioned over the appropriate area in of the orthophoto and planimetrics (ground level feature were primary source). For the "best fit" to ortho, 95% of features are within 2 meters of their true position on the 2002 orthophoto. Within a square, the property map relative accuracy is approximately 2 feet. - Each Square is an Island, alone unto itself. - Street width is approximate. The published official street widths to set up property lines or determine right-of-way are correct. There is digital scan information available from DDOT regarding Right-of-Way widths.
N/A
Metadata imported. Updated with Jan 04, 2008 Vector Property data
Tax Assessment attribution for this layer was conflated from the most recent OTR Public Extract dated 06/28/09.
The Office of Tax and Revenue (OTR), RPTA division's public extract was compared against the COL layer once all features were appended. Similarly, staff ran topology rules (must not overlap self, must not have gaps, area boundary must be covered by boundary of) to detect spatial discrepancies/errors for OS or RPTA to correct, if any errors or omissions are found. 1.) Staff opened a blank Arcmap document (.mxd) and loaded Tax, Parcel, and Record polygons from the VPM production environment. 2.) Staff created an empty COL feature class (FC) with all fields identified in the participating VPM layers (Tax, Parcel, and Record) as well as the public extract. 3.) Staff used the Object Loader command in Arcmap to initially append Tax and Parcel polygon features to the COL feature class. 4.) Staff performed multiple spatial queries against the COL and Record lot polygons where the layers were selected based on their location (i.e. are contained by, completely contain, are completely within, and contain). 5.) Staff opened the attribute tables of the Record layer and reverse/switch the selection. 6.) Once the reverse and switch selection was made, staff created a temporary field to populate (1 = take). This is so that staff can query only Record layer features that should be appended to the COL layer (Tax & Parcel have already appended in step 3) by using the query builder inside of the Object Loader. 7.) Staff created an SSL field (12 character) to populate the SSL based on the truncation of the Square, Suffix, and Lot fields for Tax and Record. Reservations SSL should lead with "RES " + RESERVATION NUMBER + "0000". Parcels SSL should lead with "PAR " + PAR + LOT. SSL's in ITS are currently setup this way. 8.) Staff created a temporary field in OTR's ITS public extract so that non matches could be quantified (i.e. a user can select all records in the public extract that do not have a geospatial match. Similarly, an ITS Boolean field was also created in the COL layer so that ITS matches can be quantified, where 1 = true and 0 = false. 9.) Staff performed a random visual inspection to spot check and manually select omissions to append to the COL. This was also done to link the public extract to the various VPM layers to see if any new matches could be identified.
withheld
D.C. Office of the Chief Technology Officer
GIS Data Coordinator
(202) 727-5660
200 I Street SE, 5th Floor
Washington
DC
20003
US
dcgis@dc.gov
8:30 am - 5 pm
GIS Data Coordinator
Tax Assessment attribution for this layer was conflated from the most recent OTR Public Extract dated 08/14/09. In addition, 18 geometry issue were repaired on this layer.
Updated with October 3, 2008 Vector Property data using a 9/21/08 OTR Public Extract File - Creation of 514 new Record Lots, Retiring of 621 Record Lots - Creation of 201 new Tax Lots, Retiring of 188 Tax Lots - Creation of 16 new Air Rights Lots - Creation of 19 new Reservation Lots - Retiring of 8 Parcel Lots - Creation of 17 Alley or Street Closures - Corrections to data anomalies - Updated Metadata - 13 Squares and their contained features have been adjusted to better fit planimetrics. (0038, 0076, 0390, 0391, 0414, 0415, 0438, 0439, 0439-S, 0574, 5159, 5162, and 5643). - 6 Squares boundaries have been altered significantly because of incoming subdivisions (0705, 0767, 0768, 0769, 0771, and 0798). - 5 Squares and Lots have been retired do to incoming subdivisions (0702, 0703, 0704, 0706, and 0802).
Updated with January 23, 2009 Vector Property data using a 01/26/09 OTR Public Extract File
Tax Assessment attribution for this layer was conflated from the most recent OTR Public Extract dated 04/26/09.
Metadata imported. Updated with May 22, 2008 Vector Property data
Tax Assessment attribution for this layer was conflated from the most recent OTR Public Extract dated 05/23/09.
Another owner polygon was generated with the release of updated vector property map layers. The following items were done on the vector property map layers: -Corrections to some data anomalies -Approx. 283 of the 800 maintenance transactions completed to bring data current. This equates to the retiring of 614 tax and record lots (these are in the history feature classes) and the creation of 364 new tax and record lots. - 49 new Parcels -Updated Maintenance transaction table
GIS Data Coordinator
Office of the Chief Technology Officer
202-727-5660
200 I Street SE, 5th Floor
Washington
DC
20001
US
dcgis@dc.gov
8:30am - 5:30pm
Tax Assessment attribution for this layer was conflated from the most recent OTR Public Extract dated 10/02/09.
Tax Assessment attribution for this layer was conflated from the most recent OTR Public Extract dated 11/28/09.
Updated with March 27, 2009 Vector Property data using a 03/22/09 OTR Public Extract File
Metadata imported. Updated with August 01, 2008 Vector Property data Recent updates include: - Creation of 667 new Record Lots, Retiring of 202 Record Lots - Creation of 167 new Tax Lots, Retiring of 18 Tax Lots - Creation of 4 new Air Rights Lots, Retiring of 1 Air Rights Lot - Corrections to data anomalies. - Updated Metadata - 16 Squares and their lots have been adjusted to better fit planimetrics. (0374, 1194, 1195, 2852, 5318, 5320, 5880, 5881, 5882, 5883, 5885, 5890, and 5956) - Several squares boundaries have been altered significantly because of incoming subdivisions; they include 5880, 5881, 5882, 5883, 5885, and 5890 - 3 new squares have been created because of incoming subdivisions, they are - 5881S, 5882W, and 5882E
location
Assessment and Taxation plats
Assessment and Taxation plats
2006-01-01
Office of the Chief Financial Officer - Real Property Tax Administration
map
http://ocfo.dc.gov
location
subdivision map
subdivision maps
2006-01-01
Department of Consumer and Regulatory Affairs - Office of Surveyor
map
http://dcra.dc.gov
137775
EPSG
5.3(9.0.0)
OwnerPLY_PF
Feature Class
137775
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
MAR_ID
MAR ID
Double
8
38
8
Master Address Repository (MAR) Unique Identifier
OCTO
RECORDATION_DT
Recordation Date
Date
8
0
0
Recordation_DT is the date when a feature class were legally recorded. If the affected feature class is never recorded, this value should match the creation date. The initial vectorization has the same creation date and recordation date of roll out for all feature classes. Recordation date is meaningless for the feature classes that do not have a history such as all point features.
OCTO
SQUARE
Square Number
String
50
0
0
Square of property
RPTA
SUFFIX
Suffix Number
String
50
0
0
Suffix of property
RPTA
RES
Reservation Number
String
50
0
0
Reservation Number
RPTA
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 of the U.S. Reservations in Washington are under the Jurisdiction of the National Park Service.
PAR
Parcel Lot Number
String
50
0
0
Parcel Number
RPTA
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 (OS & RPTA), this land is referred to as Parcels, expressed as fractions (Ex Parcel 117/36).
LOT
Lot Number
String
40
0
0
Lot of Property
RPTA
LOT_TYPE
Lot Type
Integer
4
10
0
Denotes the type of lot.
1
Record Lot
2
Tax Lot
3
Air Rights
4
Reservation
5
Appropriation
6
Parcel Lot
RPTA
OF_LOT_SEQ
Of Lot Sequence Number
Integer
4
10
0
Of Lot Sequence Number
RPTA
BOOK_NUM
Book Number
String
40
0
0
Book Number
OCTO
PAGE_NUM
Page Number
String
40
0
0
Page Number
OCTO
UNDERLIES_CONDO
Underlies Condo
Integer
4
10
0
A positive (Yes=1) means that this record lot is an underlying lot for Condo(s).
0
No
1
Yes
OCTO
CONDO_REGIME_NUM
Condo Regime Number
String
50
0
0
Condo Regime Number
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 tri-annual assessment process of 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.
OCTO
CONDO_BOOK_NUM
Condo Book Number
String
40
0
0
Condo Book Number
OCTO
CONDO_PAGE_NUM
Condo Page Number
String
40
0
0
Condo Page Number
OCTO
EFFECTIVETAXYEAR
Effective Tax Year
Date
8
0
0
Effective tax year
OCTO
QUADRANT
Quadrant
String
40
0
0
DC Quadrant Value
OCTO
COL
Common Ownership
String
2
0
0
COL
OCTO
SSL
Square Suffix Lot
String
50
0
0
Square, Suffix and Lot of property
RPTA
ARN
Assessor ID Number
String
3
0
0
Assessor ID Number
RPTA
ASRNAME
Assessor Name
String
25
0
0
Assessor Name
RPTA
PROPTYPE
Property Type
String
30
0
0
Type of property, obtained from use code
RPTA
TRIGROUP
Triennial Group
String
1
0
0
Triennial Tax Assessment Group assignment
RPTA
USECODE
Usecode
String
3
0
0
Property Use Code
RPTA
Please visit the use code lookup table (http://opendata.dc.gov/datasets/integrated-tax-system-use-codes-lookup) for more information.
LANDAREA
Land Area
Double
8
38
8
Square footage of land per surveyor
RPTA
PRMSWARD
Premise Ward
String
3
0
0
Ward premise resides in
OCTO
PREMISEADD
Premise Address
String
50
0
0
Property address string excluding city and zip code
RPTA
NBHD
Neighborhood Assessment Code
String
3
0
0
Assessor's Neighborhood Code
RPTA
NBHDNAME
Neighborhood Assessment Name
String
30
0
0
Assessor's Neighborhood name
RPTA
SUBNBHD
Sub-Neighborhood Assessment Name
String
1
0
0
Sub-Neighborhood Assessment Name
RPTA
UNITNUMBER
Unit Number
String
6
0
0
Unit number, typically associated with condominiums
RPTA
OWNERNAME
Owner Name
String
70
0
0
Property Owner's Name
RPTA
CAREOFNAME
Care of Name
String
40
0
0
Name to whom the tax bill is sent
RPTA
ADDRESS1
Tax Billing Address
String
40
0
0
Tax billing address part 1
RPTA
ADDRESS2
Tax Billing Address 2
String
40
0
0
Tax billing address part 2
RPTA
CITYSTZIP
City State Zip (Tax Billing)
String
40
0
0
Tax billing address part 3
RPTA
OLDLAND
Old Land Value
Double
8
38
8
Old Land Value
RPTA
OLDIMPR
Old Improved Value
Double
8
38
8
Old Improved Value
RPTA
OLDTOTAL
Old Total Value
Double
8
38
8
Old total value - land and improved combined
RPTA
NEWLAND
New Land Value
Double
8
38
8
New Land Value
RPTA
NEWIMPR
New Improvement Value
Double
8
38
8
New Improvement Value
RPTA
NEWTOTAL
New Total Value
Double
8
38
8
New Total Value - new land and new improved combined
RPTA
PHASELAND
Phase Land
Double
8
38
8
Current Land
RPTA
PHASEBUILD
Phase (Current) Build
Double
8
38
8
Current Build
RPTA
PARTPART
Part Part
String
1
0
0
VACLNDUSE
Vacant Land Use (Yes/No)
String
1
0
0
Y = Vacant N= Improved
RPTA
LOWNUMBER
Low House Number
String
4
0
0
Base House Number of the property address
RPTA
STREETNAME
Street Name
String
40
0
0
Street name portion of the property address
RPTA
QDRNTNAME
Quadrant
String
30
0
0
Quadrant name spelled out: NE,NW,SE or SW
RPTA
DELCODE
Delete Code
String
1
0
0
Delete Code
OCTO
HSTDCODE
Historic District Code
String
1
0
0
Historic District Code
OCTO
CLASSTYPE
Class Type
String
3
0
0
Class Type
OCTO
TAXRATE
Tax Rate
Double
8
38
8
Tax Rate of the Class
RPTA
MIXEDUSE
Mixed Use (Yes/No)
String
1
0
0
Y= Mixed Use N= Single Class
RPTA
MIX1TXTYPE
Mixed 1 Tax Type
String
2
0
0
Tax type one, also displays if there are any types of exemptions
RPTA
MIX1CLASS
MIX1CLASS
String
3
0
0
Tax class of first mix
RPTA
MIX1RATE
MIX1RATE
Double
8
38
8
Tax rate for first mix, blank if not mixed use
RPTA
MIX1LNDPCT
MIX1LNDPCT
Double
8
38
8
Percentage of the land affected by the first use type
RPTA
MIX1LNDVAL
MIX1LNDVAL
Double
8
38
8
Value of the land affected by the first use type
RPTA
MIX1BLDPCT
MIX1BLDPCT
Double
8
38
8
Percentage of the improvements affected by the first use code
RPTA
MIX1BLDVAL
MIX1BLDVAL
Double
8
38
8
Value of the improvements affected by the first use code
RPTA
MIX2TXTYPE
MIX2TXTYPE
String
2
0
0
If mixed use or part and part , the second tax type of the mixed use, otherwise blank
RPTA
MIX2CLASS
MIX2CLASS
String
3
0
0
If mixed useor part and part , the second tax class of the mixed use, otherwise blank
RPTA
MIX2RATE
MIX2RATE
Double
8
38
8
If mixed use, the second tax rate of the mixed use, otherwise blank
RPTA
MIX2LNDPCT
MIX2LNDPCT
Double
8
38
8
If mixed use, the percentage of land affected by the second mixed use, otherwise blank
RPTA
MIX2LNDVAL
MIX2LNDVAL
Double
8
38
8
If mixed use, the value of land affected by the second mixed use, otherwise blank
RPTA
MIX2BLDPCT
MIX2BLDPCT
Double
8
38
8
If mixed use, the percentage of the improvements affected by the second mixed use, otherwise blank
RPTA
MIX2BLDVAL
MIX2BLDVAL
Double
8
38
8
If mixed use, the value of the improvements affected by the second mixed use, otherwise blank
RPTA
OWNOCCT
OWNOCCT
Double
8
38
8
COOPUNITS
COOPUNITS
Double
8
38
8
PCHILDCODE
PCHILDCODE
String
1
0
0
Refers to Child Lot: 2= Vacant 3= Garage otherwise blank
RPTA
ABTLOTCODE
Abutting Lot SSL
String
12
0
0
SSL of the abutting property
RPTA
SALEPRICE
Sale Price
Double
8
38
8
Most recent property sale price
RPTA
SALEDATE
Sale Date
Date
8
0
0
Most recent property sale date
RPTA
INSTNO
INSTNO
String
8
0
0
ACCEPTCODE
Acceptance Code
String
25
0
0
Property sale acceptance code
RPTA
SALETYPE
Sale Type
String
30
0
0
Type of property sale (single or multiple lot, etc.)
RPTA
MORTGAGECO
Mortgage Key Number
String
3
0
0
Mortgage key number
RPTA
ASSESSMENT
Assessment
Double
8
38
8
Current Assessed Value Total: Total of land and building
RPTA
ANNUALTAX
Annual Tax
Double
8
38
8
Current amount of annual tax
RPTA
EXTRACTDAT
Extract Date
Date
8
0
0
Date of last extraction from database
RPTA
CAPCURR
CAPCURR
Double
8
38
8
CAPPROP
CAPPROP
Double
8
38
8
CY1YEAR
CY1YEAR
String
50
0
0
Year Description
RPTA
CY1TXSALE
CY1TXSALE
String
2
0
0
CY1TAX
CY1TAX
Double
8
38
8
Tax for first half current year
RPTA
CY1PEN
CY1PEN
Double
8
38
8
Penalty for first half current year
RPTA
CY1INT
CY1INT
Double
8
38
8
Interest for first half current year
RPTA
CY1FEE
CY1FEE
Double
8
38
8
Fees for first half current year
RPTA
CY1TOTDUE
CY1TOTDUE
Double
8
38
8
Total due for first half current year
RPTA
CY1COLL
CY1COLL
Double
8
38
8
Collections for first half current year
RPTA
CY1BAL
CY1BAL
Double
8
38
8
Balance for first half current year
RPTA
CY1CR
CY1CR
Double
8
38
8
Credits Received from prior years
RPTA
CY2YEAR
CY2YEAR
String
50
0
0
Year Description
RPTA
CY2TXSALE
CY2TXSALE
String
50
0
0
CY2TAX
CY2TAX
Double
8
38
8
Tax for second half current year
RPTA
CY2PEN
CY2PEN
Double
8
38
8
Penalty for second half current year
RPTA
CY2INT
CY2INT
Double
8
38
8
Interest for second half current year
RPTA
CY2FEE
CY2FEE
Double
8
38
8
Fees for second half current year
RPTA
CY2TOTDUE
CY2TOTDUE
Double
8
38
8
Total due for second half current year
RPTA
CY2COLL
CY2COLL
Double
8
38
8
Collections for second half current year
RPTA
CY2BAL
CY2BAL
Double
8
38
8
Balance for second half current year
RPTA
CY2CR
CY2CR
Double
8
38
8
Credits Received from prior years
RPTA
PY1YEAR
PY1YEAR
String
50
0
0
Year Description
RPTA
PY1TXSALE
PY1TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY1TAX
PY1TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY1PEN
PY1PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY1INT
PY1INT
Double
8
38
8
Interest for prior year 1
RPTA
PY1FEE
PY1FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY1TOTDUE
PY1TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY1COLL
PY1COLL
Integer
4
10
0
Collections for prior year 1
RPTA
PY1BAL
PY1BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY1CR
PY1CR
Double
8
38
8
Credits Received from prior years
RPTA
PY2YEAR
PY2YEAR
String
50
0
0
Year Description
RPTA
PY2TXSALE
PY2TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY2TAX
PY2TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY2PEN
PY2PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY2INT
PY2INT
Double
8
38
8
Interest for prior year 1
RPTA
PY2FEE
PY2FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY2TOTDUE
PY2TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY2COLL
PY2COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY2BAL
PY2BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY2CR
PY2CR
Double
8
38
8
Credits Received from prior years
RPTA
PY3YEAR
PY3YEAR
String
50
0
0
Year Description
RPTA
PY3TXSALE
PY3TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY3TAX
PY3TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY3PEN
PY3PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY3INT
PY3INT
Double
8
38
8
Interest for prior year 1
RPTA
PY3FEE
PY3FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY3TOTDUE
PY3TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY3COLL
PY3COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY3BAL
PY3BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY3CR
PY3CR
Double
8
38
8
Credits Received from prior years
RPTA
PY4YEAR
PY4YEAR
String
50
0
0
Year Description
RPTA
PY4TXSALE
PY4TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY4TAX
PY4TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY4PEN
PY4PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY4INT
PY4INT
Double
8
38
8
Interest for prior year 1
RPTA
PY4FEE
PY4FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY4TOTDUE
PY4TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY4COLL
PY4COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY4BAL
PY4BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY4CR
PY4CR
Double
8
38
8
PY5YEAR
PY5YEAR
String
50
0
0
Year Description
RPTA
PY5TXSALE
PY5TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY5TAX
PY5TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY5PEN
PY5PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY5INT
PY5INT
Double
8
38
8
Interest for prior year 1
RPTA
PY5FEE
PY5FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY5TOTDUE
PY5TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY5COLL
PY5COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY5BAL
PY5BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY5CR
PY5CR
Double
8
38
8
Credits Received from prior years
RPTA
PY6YEAR
PY6YEAR
String
50
0
0
Year Description
RPTA
PY6TXSALE
PY6TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY6TAX
PY6TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY6PEN
PY6PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY6INT
PY6INT
Double
8
38
8
Interest for prior year 1
RPTA
PY6FEE
PY6FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY6TOTDUE
PY6TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY6COLL
PY6COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY6BAL
PY6BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY6CR
PY6CR
Double
8
38
8
Credits Received from prior years
RPTA
PY7YEAR
PY7YEAR
String
50
0
0
Year Description
RPTA
PY7TXSALE
PY7TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY7TAX
PY7TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY7PEN
PY7PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY7INT
PY7INT
Double
8
38
8
Interest for prior year 1
RPTA
PY7FEE
PY7FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY7TOTDUE
PY7TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY7COLL
PY7COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY7BAL
PY7BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY7CR
PY7CR
Double
8
38
8
Credits Received from prior years
RPTA
PY8YEAR
PY8YEAR
String
50
0
0
Year Description
RPTA
PY8TXSALE
PY8TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY8TAX
PY8TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY8PEN
PY8PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY8INT
PY8INT
Double
8
38
8
Interest for prior year 1
RPTA
PY8FEE
PY8FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY8TOTDUE
PY8TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY8COLL
PY8COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY8BAL
PY8BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY8CR
PY8CR
Double
8
38
8
Credits Received from prior years
RPTA
PY9YEAR
PY9YEAR
String
50
0
0
Year Description
RPTA
PY9TXSALE
PY9TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY9TAX
PY9TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY9PEN
PY9PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY9INT
PY9INT
Double
8
38
8
Interest for prior year 1
RPTA
PY9FEE
PY9FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY9TOTDUE
PY9TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY9COLL
PY9COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY9BAL
PY9BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY9CR
PY9CR
Double
8
38
8
Credits Received from prior years
RPTA
PY10YEAR
PY10YEAR
String
50
0
0
Year Description
RPTA
PY10TXSALE
PY10TXSALE
String
50
0
0
Tax sale flag for prior year 1
RPTA
PY10TAX
PY10TAX
Double
8
38
8
Tax for prior year 1
RPTA
PY10PEN
PY10PEN
Double
8
38
8
Penalty for prior year 1
RPTA
PY10INT
PY10INT
Double
8
38
8
Interest for prior year 1
RPTA
PY10FEE
PY10FEE
Double
8
38
8
Fees for prior year 1
RPTA
PY10TOTDUE
PY10TOTDUE
Double
8
38
8
Total due for prior year 1
RPTA
PY10COLL
PY10COLL
Double
8
38
8
Collections for prior year 1
RPTA
PY10BAL
PY10BAL
Double
8
38
8
Balance for prior year 1
RPTA
PY10CR
PY10CR
Double
8
38
8
Credits Received from prior years
RPTA
OWNNAME2
Owner Name 2
String
70
0
0
DEEDS
Deeds
Double
8
38
8
CONDOLOT
Condo Lot
String
1
0
0
Whether condos exist on a lot(s)
OCFO
SE_ANNO_CAD_DATA
SE_ANNO_CAD_DATA
Blob
0
0
0
CREATEDBYRECORD
Created By Record
GUID
38
0
0
RETIREDBYRECORD
Retired By Record
GUID
38
0
0
STATEDAREA
Stated Area
Double
8
38
8
STATEDAREAUNIT
Stated Area Unit
Integer
4
10
0
CALCULATEDAREA
Calculated Area
Double
8
38
8
CREATED_DATE
Created Date
Date
8
0
0
LAST_EDITED_DATE
Modified Date
Date
8
0
0
ISHISTORIC
Is Historice
Integer
4
10
0
RECORD
Record
String
255
0
0
RETIRING_RECORD
Retiring Record
String
255
0
0
GLOBALID
GLOBALID
GlobalID
38
0
0
SHAPE
SHAPE
Geometry
8
0
0
Feature geometry.
Esri
Coordinates defining the features.
SHAPE.AREA
SHAPE.AREA
Double
0
0
0
SHAPE.LEN
SHAPE.LEN
Double
0
0
0
Enterprise Geodatabase Feature Class
Simple
FALSE
137775
TRUE
FALSE