DCGIS.SquaresPLY

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
Department of Consumer of Regulatory Affairs (DCRA) - Office of the Surveyor (OS)
Originator:
Office of Tax and Revenue (OTR) - Real Property Tax Administration (RPTA)
Originator: Office of Chief Technology Officer (OCTO) - DC GIS
Publication_Date: Weekly
Title: DCGIS.SquaresPLY
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publisher: DC GIS
Larger_Work_Citation:
Citation_Information:
Originator: DC GIS
Title: DC Geographic Information System
Geospatial_Data_Presentation_Form: vector digital data
Description:
Abstract:
Square polygons. The dataset contains locations and attributes of square 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. Please visit <http://vpm.dc.gov/> for additional information. All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.
Purpose:
This data is used for the planning and management of Washington, D.C. by local government agencies.
Supplemental_Information:
Introduction:
The Vector Property data was developed with the oversight of the Office of Chief Technology Officer (OCTO) - DC GIS, Department of Consumer of Regulatory Affairs (DCRA) - 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.
Definitions:
Squares (point, line, poly) - 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 4867 active squares. A Square is similar to a city block. Squares are numbered starting at 1 and are currently in the 6000 series. Not all squares are active. A common cause of inactive squares is 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.
Record Lots (point, line, poly) - RecordLotsPT, RecordLotsLN, RecordLotsPLY
Record lots are defined by the Department of Consumer of Regulatory Affairs (DCRA) - Office of the Surveyor (OS) - DC Surveyor. They are official, platted, and recorded subdivision lots created "by" the....."(must have public street frontage, be at least 30ft wide etc). Typically, these lots are numbered 1 through 799 with no number being used more than one time in a Square. There are a few exceptions to this rule. When 1-799 has been exhausted within a square, the Surveyor's Office assigns numbers from 1200 or may even use 8000 and above. Additionally, in most case scenario's, 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 the Office of the Surveyor are Office of Zoning, Office of Planning, the Department of Public Works, Historic Preservation and District Department of Transportation. 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. There are roughly 151,000 active record lots. These lots are located within squares, which usually correspond to one or two city blocks.
Tax Lots (point, line, poly) - 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. RPTA normally defines tax lots under two circumstances: 1) when property owners request for their real property tax bills to be consolidated because they have several contiguous lots and want one tax bill or if an alley/street has been closed and the owner wants the residual portion that abuts their lot (this is called a combine); and 2) when part of a record lot is sold, but no new record lot is yet defined (this is called a split request). There are roughly 32,000 tax lots. Tax lots are not determined by survey, and are therefore not official lots. These lots are normally numbered between 800 and 1999 within a square to differentiate them from record lots on the 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. 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. In addition to the previously described tax lots, there are two special types of tax lots: condo tax lots and air right tax lots. 1.) Condo Lots Condo tax 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 record lot or tax lot that has one or more condo buildings within it. A condo regime number is assigned to each 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. RPTA then establishes individual accounts for each condominium unit and assigns a tax lot number to that account. RPTA maintains the master list of Regime numbers and there relationship to approved condo numbers. There are roughly 39,000 condo tax lots situated over 1000+ record lots.
2.) Air Rights Lots (point, line, poly) - 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. These tax lot numbers start at 7000. There are approximately 60 of these air right tax lots. Air rights are taxed in DC.
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 and T lots were only created by the Tax Assessor out of lands that had been previously Record Lots at some point in there 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 and 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 and T lots though no underlying record lot exists. There is often little or no historical source information about there types of transactions therefore vectorizing them often required vast amounts of research. There are approximately 85 of these air right tax lots.
Record Lot "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 (described earlier), 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 overlapping them since it is a piece or remainder of a Record Lot. There are approximately 11,500 "of-lots". Once a record lot has had anything added to it or subtracted to it by deed, both it an all its various pieces receive tax assessors A&T lot numbers. It does not cease being an official Record Lot, however, when it also becomes a Tax Lot. It will carry dual lot numbers thereafter. Only when it is subdivided into a new Record Lot will the old record lot cease to exist.
Parcels (point, line, poly) - 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 outconveyance from original Parcel 117. The tracking of parcels was started in 1905 when, by an 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 OS. 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. * This data layer is not finalized; efforts are underway to complete.
Alleys (line, ply) - 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 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.
Building Restriction Lines (line) - BuildingRestrictionsLN
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.
**These features were captured only if they appeared on subdivision plats of active record lots. It is known that not all building restriction lines were capture during this effort.
Highway Planning Lines (line) - HighwayPlanLN
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.
**These features were captured only if they appeared on subdivision plats of active record lots. It is known that not all highway planning lines were captured during this effort and their accuracy can not be verified.
Public Easements (lines) - PublicEasementsLN These are not to be confused with utility or private easements. They are often placed after an alley closing for traffic or access.
**These features were captured only if they occurred on subdivision plats of active record lots. It is known that very few of these were captured during this effort and their accuracy can not be verified.
Square-Suffix-Lot number (SSL) - Each lot of land is identified by Square-Suffix-Lot number (SSL) as described below:
Suffix can be one of the N (North), S (South), E (East), or W (West) letters referring to directions. Most squares do not have suffixes. However, small areas near other squares were given the same number as the nearby square with a suffix. For example a small land south of square 6002 was identified as square 6002S. Although these squares use a number from a nearby square, they have no dependencies on other squares and can have RL and TL of their own. The suffix is also used to identify parcels. See the previous paragraph on Parcels. Lot numbers start from 1 for record lots (800 for A&T lots, 2000 for condo lots, and 7000 for air right lots) in each square. When a lot number is killed it is never used again in that square. There are rare occurrences of existing duplicated Record Lots numbers within a square. ITS uses unique Tax Lot numbers for each in order to uniquely identify them.
Exceptions
-Despite the fact that Lot numbers "800 and up" are reserved for use by the Tax Assessor, there are known recorded Subdivision Plats that create Record Lots numbered in the 800s.
- Even though Lot numbers are supposedly never duplicated within a Square, there are numerous instances of this occurring on early plats.
- There are also examples of Tax Lots being numbered lower than 800
- In most case scenarios, condo's lots should only occur and have been built on records lots. There are several exceptions to this statement where condo's were erected on Tax Lots.
Tax Lot/Recors Lot Precedence Rules:
Tax Lots and Record Lots are the primary means to identify property within the District. Frequently, both may occupy the same area. However, these are two different entities with different Lot numbers and administered by different DC Agencies. Confusion occurs in determining which Lot is to take precedence when selection of a given property lot is required.
As a rule, Tax Lots will take precedence over Record Lots when both are present for a given address.
The Lot Precedence Rules for a given address are:
1) If a Record Lot Exists, but no Tax Lot, use the existing Record Lot 2) If a Tax Lot Exists, but no Record Lot, use the existing Tax Lot 3) If both a Record Lot and a Tax Lot exist, use the Tax Lot 4) If neither Record Lots or Tax Lots exist, a. If a Parcel exists, use the Parcel designation b. If a Reservation exists, use the Reservation designation c. If an Appropriation exists, use the Appropriation
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: Weekly
Currentness_Reference: ground condition
Status:
Progress: In work
Maintenance_and_Update_Frequency: Weekly
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.114193
East_Bounding_Coordinate: -76.909546
North_Bounding_Coordinate: 38.995969
South_Bounding_Coordinate: 38.810329
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: Land
Theme_Keyword: Cadastral
Theme_Keyword: Square
Theme_Keyword: Property
Theme_Keyword: location
Theme_Keyword: Lot
Theme_Keyword: planningCadastre
Place:
Place_Keyword: Washington, D.C.
Place_Keyword: District of Columbia
Place_Keyword: DC
Place_Keyword: DC GIS
Place_Keyword: DCGIS
Use_Constraints:
For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 441 4th St NW, Suite 930 South
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: 202-727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30am - 5:30pm
Data_Set_Credit:
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
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.2.6.1500

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report: Validated by source and/or responsible agency
Logical_Consistency_Report:
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.
3.) Topology Checks and Rules
ParcelsLn - Must Be Covered By Boundary Of - ParcelsPly SquaresLn - Must Be Covered By Boundary Of - SquaresPly TaxLotsLn - Must Be Covered By Boundary Of - TaxLotsPly RecordLotsLn - Must Be Covered By Boundary Of - RecordLotsPly ParcelsLn - Must Not Have Dangles RecordLotsLn - Must Not Have Dangles SquaresLn - Must Not Have Dangles TaxLotsLn - Must Not Have Dangles TaxLotsLn - Must Not Self-Intersect SquaresLn - Must Not Self-Intersect RecordLotsLn - Must Not Self-Intersect ParcelsLn - Must Not Self-Intersect AlleyLn - Must Not Self-Intersect TaxLotsLn - Must Be Single Part SquaresLn - Must Be Single Part RecordLotsLn - Must Be Single Part ParcelsLn - Must Be Single Part AlleyLn - Must Be Single Part TaxLotsPly - Must Not Overlap SquaresPly - Must Not Overlap RecordLotsPly - Must Not Overlap ParcelsPly - Must Not Overlap RecordLotsPly - Must Be Covered By - SquaresPly TaxLotsPly - Boundary Must Be Covered By - TaxLotsLn SquaresPly - Boundary Must Be Covered By - SquaresLn RecordLotsPly - Boundary Must Be Covered By - RecordLotsLn ParcelsPly - Boundary Must Be Covered By - ParcelsLn TaxLotsPly - Contains Point - TaxLotsPt SquaresPly - Contains Point - SquaresPt RecordLotsPly - Contains Point - RecordLotsPt ParcelsPly - Contains Point - ParcelsPt TaxLotsPt - Must Be Properly Inside - TaxLotsPly SquaresPt - Must Be Properly Inside - SquaresPly RecordLotsPt - Must Be Properly Inside - RecordLotsPly ParcelsPt - Must Be Properly Inside - ParcelsPly AlleyLn - Must Be Covered By Feature Class Of - SquaresLn AlleyLn - Must Be Covered By Boundary Of - SquaresPly
Completeness_Report:
Data is mostly complete thru April 2009.
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.) Not all Parcels that reside outside of a Square(s) boundary have been processed/created. 3.) Not all Reservations have been processed/created.
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.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
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.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report: N/A
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Department of Consumer and Regulatory Affairs - Office of Surveyor
Publication_Date: 2006
Title: subdivision map
Geospatial_Data_Presentation_Form: map
Online_Linkage: <http://dcra.dc.gov>
Type_of_Source_Media: hardcopy
Source_Citation_Abbreviation: subdivision maps
Source_Contribution: location
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Office of the Chief Financial Officer - Real Property Tax Administration
Publication_Date: 2006
Title: Assessment and Taxation plats
Geospatial_Data_Presentation_Form: map
Online_Linkage: <http://ocfo.dc.gov>
Type_of_Source_Media: hardcopy map
Source_Citation_Abbreviation: Assessment and Taxation plats
Source_Contribution: location
Process_Step:
Process_Description:
1.) Scan all index cards in the Office of the Surveyor The index cards show lot history and indicate which subdivision (Book and Page) or Assessment and Taxation (A&T) plat the lot was recorded.
2.) Digitally image all source material. Plats that were needed and necessary to construct active lots (Subdivisions, A&T etc) were digitally imaged and indexed for easy retrieval.
3.) Build "Comp Sheet" of each square. Comp sheets are a paper representation of each square with lots and dimensional information, lot number, and other specifications. Since each square contains multiple source documents, comp sheets allow staff to see the sqaure as one, pasted together map. This expedited the COGO stage.
4.) COGO Lots. Using customized COGO application, build linear features for each square that maintain much of the attribution seen on the plats.
5.) Post Process the data Customized process to dissolve on duplicate lines, build poly's and point, attach attribution, topology, and other attributes.
Source_Used_Citation_Abbreviation: C:\OCTOGIS\Data\Metadata\TemplateDCStat
Process_Date: 09/31/05
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: <The city of the process Contact Person.>
State_or_Province: <The state or province of the process Contact Person.>
Postal_Code: <The ZIP or other postal code of the process Contact Person.>
Country: <The country of the process Contact Person.>
Contact_Facsimile_Telephone: 202-727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30am - 5:30pm
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: E:\DCGISDATA_WORKSPACE\Metadata\TemplateDCGIS.shp.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation:
W:\DCGISDATA_WORKSPACE\Metadata\Metadata_Template_Open_DCGIS.shp.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: W:\DCGISDATA_WORKSPACE\OTR\RecordLotsPly.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: W:\DCGISDATA_WORKSPACE\OTR\VPMTemplatePoly.xml
Process_Step:
Process_Description:
-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
Process_Date: 06/27/07
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: 202-727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30am - 5:30pm
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: W:\DCGISDATA_WORKSPACE\OTR\VPMTemplatePoly.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: W:\DCGISDATA_WORKSPACE\OTR\VPMPoly.xml
Process_Step:
Process_Description:
- Appropriations: 10 of the 17 have been captured
- Parcels: 81 new parcels.
- Air Rights Lots: several additional lots retired and captured
- Hundreds of new and retired record and tax lots (retired lots located in history layers)
- Improved best fits around Grant Circle, parkland and railroads.
Process_Date: 20070831
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: 202-727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30am - 5:30pm
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: W:\DCGISDATA_WORKSPACE\OTR\VPMPoly_template.xml
Process_Step:
Process_Description:
Recent updates include:
- 122 new tax lots - 248 new record lots - 128 new Parcel Lots - 10 new Air Rights Lots - Corrections to several data anomalies. - COL feature class now has all the requested fields from John Codd. - Moved 16 Squares:
0393 0078 3113 1832 2850 1067 1080 5598 5999N 1300 3189 1065 1859 1815 1321 1292
Process_Date: 20071101
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: OCTO
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: W:\DCGISDATA_WORKSPACE\OTR\VPMPoly_template.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\DC\VectorProperty\Metadata\SquaresPly.xml
Process_Step:
Process_Description:
Metadata updated. Slightly adjusted or moved the following squares placement: 0552, 0554, 0553, 0620, 1785, 3251, 2363, 3576 (updated east piece), 3710 (small piece), 5865, 4222, 1778 (B/t Grant, Wisconsin and Nebraska), 1779 (B/t Grant, Wisconsin and Nebraska), 5630, 5629, 5628, 2508.
Process_Step:
Process_Description:
Metadata updated. Slightly adjusted or moved the following squares placement: 0361 0736 0765 0836 1818 2607 2967 3365
Process_Step:
Process_Description:
Metadata updated. Slightly adjusted or moved the following squares placement: 0344 0514 0699 0701 0767 0768 0769 3848 5807
Process_Step:
Process_Description:
Updating of Metadata 6 Squares and their lots have been slightly adjusted to better fit planimetrics. The square numbers are: 1672, 1673, 2287, 2219, 3768, and 5319
Process_Step:
Process_Description:
- 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
Source_Used_Citation_Abbreviation: C:\DC\VectorProperty\Metadata\SquaresPly.xml
Process_Date: 08/01/08
Process_Step:
Process_Description:
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).
Process_Date: 10/03/08
Process_Step:
Process_Description:
7 Squares and their contained features have been adjusted to better fit planimetrics. (0759, 1006, 1282, 3303, 3735, 4327, and 0516-S).
4 Squares boundaries have been altered significantly because of incoming subdivisions or street closing (0737, 0737-N, 0739, 0853, and 5052).
1 new Square (0953-W)
Process_Date: 11/20/08
Process_Step:
Process_Description:
7 Squares and their contained features have been adjusted to better fit planimetrics or have changed because of incoming subdivisions. (0881, 0973, 1026-N, 1361-N, 1387, 1388-E, 3620).
Process_Date: 01/23/2009
Process_Step:
Process_Description:
7 Squares and their contained features have been adjusted to better fit planimetrics or have changed because of incoming subdivisions. (0421, 1004, 1179, 1431, 1447, 1459, 2827).
Process_Date: 03/27/2009
Process_Step:
Process_Description:
0 Squares and their contained features have been adjusted to better fit planimetrics or have changed because of incoming subdivisions.
Process_Date: 05/01/09
Process_Step:
Process_Description:
18 Squares and their contained features have been adjusted to better fit planimetrics, have changed because of incoming subdivisions or public lands. They are: 0015, 0031, 0038, 0101, 0487, 0488, 0489, 0763, 0813, 0821, 1001, 1524, 4021, 5969, 6172, 6264 Additionally, 2 new squares SQ 6264 - for DC Village (previously a parcel), SQ1067-S along waterfront
Process_Date: 05/29/09
Process_Step:
Process_Description:
15 Squares and their contained features have been adjusted to better fit planimetrics, have changed because of incoming subdivisions or public lands. They are: 0053, 0473, 0502, 0503, 0515, 0525, 0526, 0556, 0558, 0762, 0819-S, 0843-S, 0901-S, 0924-S, 2941, 3766
Process_Date: 06/30/09
Process_Step:
Process_Description:
7 Squares and their contained features have been adjusted to better fit planimetrics or have changed because of incoming subdivisions or public lands. They are: 0403-N, 0624, 0624-W, 0707, 0708, 0708-E, 1935
Process_Date: 08/14/09
Process_Step:
Process_Description:
7 Squares and their contained features have been adjusted to better fit planimetrics. Typically these are moved because of incoming subdivisions or public lands. They are: 0952, 1005, 2608, 2613-E, 3131-W, 3235, 5955
Process_Date: 10/02/09
Process_Step:
Process_Description:
5 Squares and their contained features have been adjusted to better fit planimetrics. These are moved because of incoming subdivisions or public lands. They are: 0088, 0251, 0333, 0661 and 0986
Process_Date: 10/30/09
Process_Step:
Process_Description:
5 Squares and their contained features have been adjusted to better fit planimetrics. These are moved because of incoming subdivisions or public lands. They are: 0771, 0826, 2967, 3369 and 3514-S
Process_Date: 12/04/09
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: E:\DataLoad\SquaresPly.xml

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 4895

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name: State Plane Coordinate System
State_Plane_Coordinate_System:
SPCS_Zone_Identifier: 1900
Lambert_Conformal_Conic:
Standard_Parallel: 38.300000
Standard_Parallel: 39.450000
Longitude_of_Central_Meridian: -77.000000
Latitude_of_Projection_Origin: 37.666667
False_Easting: 400000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000011
Ordinate_Resolution: 0.000011
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: DCGIS.SquaresPLY
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: GIS_ID
Attribute_Definition: OCTO GIS Identifier
Attribute:
Attribute_Label: CREATION_DT
Attribute_Definition:
Timestamp for when the record was created (posted to the database). The initial vectorization has the same creation date and recordation date of roll out for all feature classes.
Attribute:
Attribute_Label: RECORDATION_DT
Attribute_Definition:
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.
Attribute:
Attribute_Label: NARRATIVE
Attribute_Definition: This attribute stores general comments about the feature.
Attribute:
Attribute_Label: EXPIRATION_DT
Attribute_Definition: Lot Expiration Date
Attribute:
Attribute_Label: STATUS
Attribute_Definition:
The status value is always set to 1 which is the only value in the STATUS_CURRENT coded value domain. The value of this attribute is constant for a class. It denotes whether the information is considered current or historical. This attribute is primarily used by applications.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: Feature is part of active layer
Attribute:
Attribute_Label: SQUARE
Attribute_Definition: Square value from the SSL identifier.
Attribute:
Attribute_Label: SUFFIX
Attribute_Definition: Suffix value from the SSL identifier.
Attribute:
Attribute_Label: COMPUTED_AREA_SF
Attribute_Definition: The area computed by the system.
Attribute:
Attribute_Label: SURVEYED_AREA_SF
Attribute_Definition: The area from a survey plat.
Attribute:
Attribute_Label: SQUAREPLYID
Attribute_Definition: Square Polygon Identifier
Attribute:
Attribute_Label: KILL_DT
Attribute:
Attribute_Label: FIT_ROTATION_DD
Attribute:
Attribute_Label: FIT_ROTATION_X
Attribute:
Attribute_Label: FIT_ROTATION_Y
Attribute:
Attribute_Label: SW_CORNER_X
Attribute:
Attribute_Label: SW_CORNER_Y
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: SHAPE.AREA
Attribute:
Attribute_Label: SHAPE.LEN
Detailed_Description:
Entity_Type:
Entity_Type_Label: VPM_OWNER.SquaresContainRecordLots
Detailed_Description:
Entity_Type:
Entity_Type_Label: VPM_OWNER.SquaresContainAppropriationLots
Detailed_Description:
Entity_Type:
Entity_Type_Label: VPM_OWNER.SquaresContainReservationLots
Detailed_Description:
Entity_Type:
Entity_Type_Label: VPM_OWNER.SquaresHaveSquareLines
Detailed_Description:
Entity_Type:
Entity_Type_Label: VPM_OWNER.SquaresHaveCentroidPoint
Detailed_Description:
Entity_Type:
Entity_Type_Label: VPM_OWNER.SquaresContainTaxLots
Detailed_Description:
Entity_Type:
Entity_Type_Label: VPM_OWNER.SquaresContainAirRightsLots

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: DC Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5:30 pm
Resource_Description: Downloadable Data
Distribution_Liability:
For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.040
Ordering_Instructions: All data is available at <http://opendata.dc.gov>

Metadata_Reference_Information:
Metadata_Date: 20100125
Metadata_Review_Date: 01/15/2010
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.9.12 on Thu Jun 25 15:16:18 2015