Condo One to Many
About this dataset
Columns (14)
Sample rows
| MISC | BK_PG | O_LOTS | REGIME | SQUARE | SUFFIX | MAT_SSL | REC_LOT | TAX_LOT | CONDO_BK | CONDO_PG | DOC_DATE |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 38/34 | 1056 | 0098 | 0098 0013 | 0013 | 38 | 34 | |||||
| 38/35 | 1207 | 2565 | 2565 0017 | 0017 | 38 | 35 | |||||
| 38/36 | 2252 | 0279 | 0279 0023 | 0023 | 38 | 36 | |||||
| 38/38 | 1167 | 2551 | 2551 0079 | 0079 | 38 | 38 | |||||
| 38/39 | 2207 | 0194 | 0194 0057 | 0057 | 38 | 39 | |||||
| 38/40 | 2259 | 0362 | 0362 0111 | 0111 | 38 | 40 | |||||
| 38/41 | 1222 | 2596 | 2596 1059 | 1059 | 38 | 41 | 622699200000 | ||||
| 38/42 | 3043 | 4327 | 4327 0001 | 0001 | 38 | 42 |
A sample of the data. The full table and an interactive map open with a free account.
Related datasets
✦ Suggested by OrionAIWhen 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” value UNDERLIES_CONDO = 1 CONDO_BOOK_NUM CONDO_PAGE_NUM CONDO_REGIME_NUM CONDOLOT = 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” value UNDERLIES_CONDO = 1 CONDO_BOOK_NUM CONDO_PAGE_NUM CONDO_REGIME_NUM CONDOLOT = Y When 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_NUM CONDO_PAGE_NUM CONDO_REGIME_NUM CONDOLOT = Y 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.The following fields are populated once Condo Lots have been approved: Condo_Book_Num Condo_Page_Num Condo_Regime_Num
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.
This layer is derived from the Common Ownership Lots and represents property transactions as they’ve occurred since the implementation of the Vector Property Mapping program in September 2006. A property transaction entails new geometry (split/combination of Lot(s) or property type conversion (from Air Rights, Record, or Tax Lots to Condo lots). The layer contains locations and attributes of archived features (inactive lots – dead lots) and corresponds with Office of Tax and Revenue's Public Extract files (ITSPE). It occurs weekly for the current calendar year and geometry updated when a transaction occurs.
The dataset contains locations and attributes of building construction and alteration permits applied for and approved by the District of Columbia Department of Buildings. These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC.
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.
This data set contains data related to the following information of a business entity: business name, model type, locale, initial file number, status, name, and address. More information can be found at https://dlcp.dc.gov/page/corporations.
Indexed by OrionGIS from ArcGIS Online public items (authoritative). Data is loaded from the publisher's own server when you use it. Permanent link