DCGIS.ReservationsPT

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

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.ReservationsPT

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:

Reservation points. The dataset contains locations and attributes of reservation points, 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.
U.S. Reservations are lands acquired for use by the Federal Government after the original founding of the city and managed by the National Park Service (NPS). There are presently more than 1150 U.S Reservation in Washington, D.C due to the original Reservations being subdivided for Public Safety and Transfers of Jurisdiction since inception. These were all acquired by the Federal Government through purchase, condemnation, dedication or gift and the majority of U.S. Reservations in Washington are under the Jurisdiction of (NPS). U.S. Reservations are found throughout the city. The National Park Service also has information for every U.S. Reservation in addition to The District of Columbia Government, Department of Consumer & Regulatory Administration (DCRA), Office of the Surveyor (OS) having some detailed information on transactional history. It should be noted that The District of Columbia Government, Office of Tax & Revenue (OTR), Real Property Tax Administration (RPTA) has converted reservations (mostly Transfers of Jurisdiction) to tax lots for land tracking purposes although the federal government may still retain ownership.

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.115508

East_Bounding_Coordinate: -76.931481

North_Bounding_Coordinate: 38.984805

South_Bounding_Coordinate: 38.804443

Keywords:

Theme:

Theme_Keyword_Thesaurus: none

Theme_Keyword: Land

Theme_Keyword: Cadastral

Theme_Keyword: Square

Theme_Keyword: Property

Theme_Keyword: location

Theme_Keyword: Lot

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: dcgis@dc.gov

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:

This data layer is currently in its infancy. Efforts are underway in 2009 to bring it up to date.

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: 2008

Title: subdivision and survey maps

Geospatial_Data_Presentation_Form: map

Online_Linkage: <http://dcra.dc.gov>

Type_of_Source_Media: hardcopy

Source_Citation_Abbreviation: subdivision and survey 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: dcgis@dc.gov

Hours_of_Service: 8:30am - 5:30pm

Process_Step:

Process_Description:

U.S. Reservations captured to date are mostly based on source material (Subdivisions, Assessment and Taxation (A&T) plats, and some Surveys) obtained from DCRA's Office of the Surveyor (OS) and OTR's, Real Property Tax Administration (RPTA). In cases where the source material lacked the level of detail necessary for capture additional geospatial layers, rasters, and NPS's Reservation listing were referenced. They are as follows: VPM features since the majority of Reservations are covered by Tax Lots, Baist Book and Public Space counter maps, Planimetric features (Curbln, SidewalkPly, Structureln), and NPS's Reservation listing with location descriptions.

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: C:\DC\VectorProperty\Metadata_export_central\ReservationsPT.xml

Process_Step:

Process_Description: Creation of 19 new Reservation Lots

Process_Date: 10/03/08

Process_Step:

Process_Description: Creation of 7 new Reservations

Process_Date: 01/23/2009

Process_Step:

Process_Description: Creation of 3 new Reservations

Process_Date: 03/27/2009

Process_Step:

Process_Description: Creation of 35 new Reservations

Process_Date: 05/01/09

Process_Step:

Process_Description: Creation of 34 new Reservations

Process_Date: 05/29/09

Process_Step:

Process_Description:

Creation of 40 new Reservations (primarily triangle parks along Pennsylvania Ave SE, North and South Carolina Ave SE)

Process_Date: 06/30/09

Process_Step:

Process_Description:

Creation of 46 new Reservations (includes triangle parks along Virginia Ave NW, Massachusetts Ave NW/SE, SE Water Front, Fort Totten Park)

Process_Date: 08/14/09

Process_Step:

Process_Description:

Creation of 90 new Reservations (primarily along New Hampshire Ave NW, Virginia Ave SW/SE, Minnesota Ave SE, Kentucky Ave SE and Potomac Ave and Town Center Park area)

Process_Date: 10/02/09

Process_Step:

Process_Description:

Creation of 59 new Reservations (primarily along Vermont Ave NW, Mass Ave NW, New York Ave NW, and New Jersey Ave NW

Process_Date: 10/30/09

Process_Step:

Process_Description:

Creation of 63 new Reservations** (primarily along Maryland Ave NE, Florida Ave NE/NW, Delaware Ave SW)

Process_Date: 12/04/09

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: E:\DataLoad\ReservationsPT.xml

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Entity point

Point_and_Vector_Object_Count: 644

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.ReservationsPT

Attribute:

Attribute_Label: Shape

Attribute_Definition: Feature geometry

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

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: SHAPE

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

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: 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: NARRATIVE

Attribute_Definition: This attribute stores general comments about the feature.

Attribute:

Attribute_Label: KILL_DT

Attribute:

Attribute_Label: LOT

Attribute:

Attribute_Label: LOT_TYPE

Attribute:

Attribute_Label: EXPIRATION_DT

Attribute_Definition: Lot Expiration Date

Attribute:

Attribute_Label: RESERVATIONSPTID

Attribute:

Attribute_Label: SUFFIX

Attribute_Definition: Suffix value from the SSL identifier.

Attribute:

Attribute_Label: RES

Attribute:

Attribute_Label: RESERVATIONSPLYID

Attribute:

Attribute_Label: SSL

Detailed_Description:

Entity_Type:

Entity_Type_Label: VPM_OWNER.ReservationsHavePoints

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: dcgis@dc.gov

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_Voice_Telephone:

REQUIRED: The telephone number by which individuals can speak to the organization or individual.

Contact_Facsimile_Telephone: (202) 727-5660

Contact_Electronic_Mail_Address: dcgis@dc.gov

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

Metadata_Extensions:

Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>

Profile_Name: ESRI Metadata Profile