Street Right of Way (RightOfWay)

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: District Department of Transportation

Publication_Date: 20081002

Title: Street Right of Way (RightOfWay)

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publisher: DC GIS

Online_Linkage:

Server=10.1.11.144; Service=5151; User=dcgis; Version=SDE.DEFAULT

Description:

Abstract:

Street Centerlines - Right of Way Information. A single line, segmented at all intersections (alley and others), representing each street in the District. They follow the general trend of the street and do not deviate due to parking lanes, turning lanes, etc. and contain address ranges for geocoding. The street GIS database includes five different street road types: street centerline, alley, drive, ramp and service road.
All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters. This layer contains complete theoretical address ranges.
METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

Purpose:

This data set was created to act as a basis for public and private institutions to improve their policy and decision making; promote economic development; and enhance the quality of life for residents and businesses.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 20081002

Currentness_Reference: publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -77.116734

East_Bounding_Coordinate: -76.909401

North_Bounding_Coordinate: 38.995255

South_Bounding_Coordinate: 38.793168

Keywords:

Theme:

Theme_Keyword_Thesaurus: None

Theme_Keyword: transportation

Theme_Keyword: Street Centerline

Theme_Keyword: right of way

Place:

Place_Keyword_Thesaurus: None

Place_Keyword: Washington, DC

Place_Keyword: District of Columbia

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: D.C. 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:30 am - 5:00 pm

Data_Set_Credit: DC District Department of Transportation

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.2.5.1450

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

Validated by source and/or responsible agency. The original centerline attribute accuracy was tested by manual comparison of the digital orthos/aerial photography with the hard copy plots. In addition, several computer quality control programs were run on the accompanying digital data.

Logical_Consistency_Report: Validated by source and/or responsible agency.

Completeness_Report: Validated by source and/or responsible agency.

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:

Validated by source and/or responsible agency. The original centerlines, as part of the photogrammetric mapping effort, are captured to a planimetric base that meets National Map Accuracy standards for digital mapping at a 1 inch equals 83.33'.

Vertical_Positional_Accuracy:

Vertical_Positional_Accuracy_Report: N/A

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Publication_Date: Unknown

Publication_Time: Unknown

Title: Washington DC GIS project

Geospatial_Data_Presentation_Form: map

Type_of_Source_Media: CD-ROM

Source_Citation_Abbreviation: DD1

Source_Contribution: SIS data

Source_Information:

Source_Citation:

Citation_Information:

Originator:

District Department of Transportation (DDOT) - Spatial Database System Division

Publication_Date: 2005

Title: Street Spatial Database

Geospatial_Data_Presentation_Form: vector digital data

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

Type_of_Source_Media: Database

Source_Citation_Abbreviation: Street Spatial Database

Source_Contribution: location and attributes

Process_Step:

Process_Description:

RIGHT OF WAY Proceedure
Road attributes were updated using the scanned distribution cards and the scanned paper maps, are the street total, roadway total, the sidewalk widths and the parking area widths. In some cases a street segment contains a service road or a median. These attributes are collected when they exist. The median is given a directional value when it lies to the North or the South of the main roadway. Often times the median will lie in the middle of the street. In these cases the median is not given a directional value. A short description of the steps followed are given below.
1. In order to populate the road attributes, our first step was always to gather information from the distribution card and to use the raster map as a backup source for attribute information. If attribute information were not found on the distribution card, then we collected from the raster map.
2. We combined the sidewalk and the tree space areas as distribution card. We continued to combine the sidewalk and tree space areas from the map when we took data from the map, in the absence of information on the distribution cards.
3. Sometimes, the values on the distribution cards and/or raster map would change mid way through a street segment. In these cases we would collect the higher values for each attribute from the two sets of values, on the street segment. We then marked that street segment's "Variable" attribute as "Yes". Another case when we would mark the variable attribute as "Yes" was when the distribution card had a value listed as "Var.". In these cases we would leave the attribute with the "Var." value as "Null", and mark the "Variable" attribute as "Yes".
4. Additional fields named "Issue" and "Issue_Desc" were added to the database table. We used these columns to flag street segments whose values were missing or unclear on both the distribution card and the raster map including missing raster map for the area of the segment in question.

Process_Date: 2008

Process_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: New Light Technologies

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

Hours_of_Service: Regular office hours

Process_Step:

Process_Description:

District Department of Transportation (DDOT) Spatial Database System Division street database system moved into an enterprise environment, namely the Transportation Enterprise Asset Management System (TEAMS), in which GIS is a key component. The street spatial database is designed based on an enterprise database management system (Oracle and ArcSDE), using ESRI's geodatabase technology. The new street spatial data model adopts object-oriented data modeling methodology, and follows guidelines of ESRI's UNETRANS data model (ArcGIS Transportation Data Model). The new data model integrates GIS with transportation asset management and business processes within DDOT by making asset data spatial enabled using linear referencing system (LRS) and implements the new topology technology in ArcGIS 8.3 for maintaining the spatial database with shared geometries.
DDOT constructed a public, readable version of the full Street Spatial Database containing various views for the centerlines and related data. OCTO staff related the centerline view feature class (RoadwaySegView) with the following tables (keys): streetcode_view (stcode), streetnamelist_view (streetid), streettype_view (sttypeid), and quadrant_view (quadcode). This pulled over the street names, types, and quadrants. Staff then related the roadway segments to the streetsegment_view feature class, on sourceid, to pull over the ownership, functional class, and national highway system (nhs) attributes. Then, staff created the ST_NAME attribute which combines street name with type into one field for labelling. Various visual checks were done on functional class, street name, quadrant, and other items to ensure the relates worked using the key fields.

Source_Used_Citation_Abbreviation: C:\OCTOGIS\MetadataData\SDE.SISSCLN.xml

Process_Date: 12/13/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: 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 - 5pm

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: C:\temp\metadata.xml

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation:

F:\DCGISDATA_WORKSPACE\DDOT\Street Centerlines\StreetCenterlineLn.shp.xml

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation:

E:\DCGISDATA_WORKSPACE\DDOT\Street Centerlines\StreetCenterlineLn.xml

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: c:\temp\scl.xml

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: C:\temp\StreetCenterlineLn_old.xml

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: C:\temp\StreetCenterlineLn_old.xml

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: C:\temp\StreetCenterlineLn_old.xml

Process_Step:

Process_Description: Dataset copied.

Source_Used_Citation_Abbreviation:

Server=dcgiscentral.in.dc.gov; Service=5151; User=dcgis_user; Version=SDE.DEFAULT

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: F:\DC_SSL_metadata.xml

Cloud_Cover: 0

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: String

Point_and_Vector_Object_Count: 0

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Grid_Coordinate_System:

Grid_Coordinate_System_Name: State Plane Coordinate System 1983

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

Ordinate_Resolution: 0.000125

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_Datum_Name: North American Vertical Datum of 1988

Altitude_Resolution: 1.000000

Altitude_Distance_Units: Meters

Altitude_Encoding_Method:

Explicit elevation coordinate included with horizontal coordinates

Depth_System_Definition:

Depth_Datum_Name: Mean sea level

Depth_Resolution: .01

Depth_Distance_Units: Meters

Depth_Encoding_Method: Implicit coordinate

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: DCGIS.RightOfWay

Attribute:

Attribute_Label: ROADWAYSEGID

Attribute_Definition: Roadway Segment identifier

Attribute:

Attribute_Label: OWNERSHIP

Attribute_Definition: Entity responsible for street maintenance

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: Unknown

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: Unknown

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Unknown

Enumerated_Domain:

Enumerated_Domain_Value: DDOT

Enumerated_Domain:

Enumerated_Domain_Value: National Park Service

Enumerated_Domain:

Enumerated_Domain_Value: Architect of the Capitol

Enumerated_Domain:

Enumerated_Domain_Value: Military Reservation

Enumerated_Domain:

Enumerated_Domain_Value: Private

Enumerated_Domain:

Enumerated_Domain_Value: WMATA-METRO

Enumerated_Domain:

Enumerated_Domain_Value: Other DC Agencies

Enumerated_Domain:

Enumerated_Domain_Value: Other Federal Agencies

Attribute:

Attribute_Label: FUNCTIONALCLASS

Attribute_Definition: Functional Class

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Unknown

Enumerated_Domain:

Enumerated_Domain_Value: Interstate

Enumerated_Domain:

Enumerated_Domain_Value: Other Freeways and Expressway

Enumerated_Domain:

Enumerated_Domain_Value: Principal Arterial

Enumerated_Domain:

Enumerated_Domain_Value: Minor Arterial

Enumerated_Domain:

Enumerated_Domain_Value: Collector

Enumerated_Domain:

Enumerated_Domain_Value: Local

Attribute:

Attribute_Label: LIFECYCLESTATUS

Attribute_Definition: Status Code

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 1

Enumerated_Domain_Value_Definition: Active

Enumerated_Domain:

Enumerated_Domain_Value: 2

Enumerated_Domain_Value_Definition: Retired

Enumerated_Domain:

Enumerated_Domain_Value: 3

Enumerated_Domain_Value_Definition: Paper

Enumerated_Domain:

Enumerated_Domain_Value: 4

Enumerated_Domain_Value_Definition: Derived

Enumerated_Domain:

Enumerated_Domain_Value: 5

Enumerated_Domain_Value_Definition: Open

Enumerated_Domain:

Enumerated_Domain_Value: 6

Enumerated_Domain_Value_Definition: Close

Enumerated_Domain:

Enumerated_Domain_Value: 7

Enumerated_Domain_Value_Definition: On Hold

Enumerated_Domain:

Enumerated_Domain_Value: 8

Enumerated_Domain_Value_Definition: Changed

Enumerated_Domain:

Enumerated_Domain_Value: 9

Enumerated_Domain_Value_Definition: New

Enumerated_Domain:

Enumerated_Domain_Value: 10

Enumerated_Domain_Value_Definition: Old

Enumerated_Domain:

Enumerated_Domain_Value: 11

Enumerated_Domain_Value_Definition: Deleted

Enumerated_Domain:

Enumerated_Domain_Value: 12

Enumerated_Domain_Value_Definition: Completed

Enumerated_Domain:

Enumerated_Domain_Value: 13

Enumerated_Domain_Value_Definition: Budgeted

Enumerated_Domain:

Enumerated_Domain_Value: 14

Enumerated_Domain_Value_Definition: Under Construction

Enumerated_Domain:

Enumerated_Domain_Value: 15

Enumerated_Domain_Value_Definition: Planned

Enumerated_Domain:

Enumerated_Domain_Value: 16

Enumerated_Domain_Value_Definition: Under Design

Attribute:

Attribute_Label: DIRECTIONALITY

Attribute_Definition: DIrectionality of road segment

Attribute:

Attribute_Label: OBJECTID

Attribute_Definition: Object ID

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: ST_NAME

Attribute_Definition: Street Name and Type

Attribute:

Attribute_Label: SHAPE

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: STCODE

Attribute_Definition: Street Code

Attribute:

Attribute_Label: QUADRANT

Attribute_Definition: Quandrant Name

Attribute:

Attribute_Label: NHSTYPE

Attribute:

Attribute_Label: ROW_TOTAL

Attribute_Definition: Total width (in feet) of road right of way

Attribute:

Attribute_Label: ROW_ROADWAY

Attribute_Definition: Width (in feet) of the roadway - all lanes

Attribute:

Attribute_Label: ROW_SIDEWALK1

Attribute_Definition:

Direction of the location of the sidewalk either East or North depending on the orientation of the road

Attribute:

Attribute_Label: ROW_SIDEWALK1_FT

Attribute_Definition:

Width (in feet) of the sidewalk including tree spaces either on East or North side

Attribute:

Attribute_Label: ROW_SIDEWALK2

Attribute_Definition:

Direction of the location of the sidewalk either West or South depending on the orientation of the road

Attribute:

Attribute_Label: ROW_SIDEWALK2_FT

Attribute_Definition:

Width (in feet) of the sidewalk including tree spaces on either West or South side

Attribute:

Attribute_Label: ROW_PARKING1

Attribute_Definition:

Direction of the location of the parking either East or North depending on the orientation of the road

Attribute:

Attribute_Label: ROW_PARKING1_FT

Attribute_Definition:

Width (in feet) of the parking space either on East or North side

Attribute:

Attribute_Label: ROW_PARKING2

Attribute_Definition:

Direction of the location of the parking either West or South depending on the orientation of the road

Attribute:

Attribute_Label: ROW_PARKING2_FT

Attribute_Definition: Width (in feet) of parking space either West or South side

Attribute:

Attribute_Label: ROW_SERVRD1

Attribute_Definition:

Direction of the location of the Service road either North or East depending on the orientation of the road

Attribute:

Attribute_Label: ROW_SERVRD1_FT

Attribute_Definition:

Width (in feet) of the Service road located either on the East or North side depending on the orientation of the road

Attribute:

Attribute_Label: ROW_SERVRD2

Attribute_Definition:

Direction of the location of the Service road either West or South side depending on the orientaion of the road

Attribute:

Attribute_Label: ROW_SERVRD2_FT

Attribute_Definition:

Width (in feet) of the Service road located eithr on the West or the South side of the road

Attribute:

Attribute_Label: ROW_TREESPACE1

Attribute_Definition:

Direction of the location of the tree spaces including sidewalk either on the North or the East side depending on the orientation of the road

Attribute:

Attribute_Label: ROW_TREE1_FT

Attribute_Definition:

Width (in feet) of tree spaces including sidewalk located on either side East or North

Attribute:

Attribute_Label: ROW_TREESPACE2

Attribute_Definition:

Direction of the location of the tree spaces including sidewalk either side West or South depending on the orientation of the road

Attribute:

Attribute_Label: ROW_TREE2_FT

Attribute_Definition:

Width (in feet) of tree spaces including sidewalk located on either side West or South

Attribute:

Attribute_Label: ROW_ISLAND1

Attribute_Definition:

Direction of Island located on either side East or North depending on the orientation of the road

Attribute:

Attribute_Label: ROW_ISLAND1_FT

Attribute_Definition: Width (in feet) of Island located on either side East or North

Attribute:

Attribute_Label: ROW_ISLAND2

Attribute_Definition:

Direction of Island located on either side West or South depending on the orientation of the road

Attribute:

Attribute_Label: ROW_ISLAND2_FT

Attribute_Definition: Width (in feet) of Island located on either side West or South

Attribute:

Attribute_Label: Issue_Desc

Attribute_Definition: A short description of issue if 1 is noted in the Issue field

Attribute:

Attribute_Label: ISSUE

Attribute:

Attribute_Label: VARIABLE

Attribute_Definition:

Variable in width of road attributes (YES if present, NO if fixed) for any of the attributes such as Road Total, Roadway, Sidewalk, Parking space, Tree spaces, Service road and Island

Attribute:

Attribute_Label: ISSUE_DESC

Attribute:

Attribute_Label: HYPERLINK

Attribute:

Attribute_Label: Issue

Attribute_Definition:

Isues (0 meaning no problem with attributes of the segment, and 1 meaning existance of some kind of problem such as no index card for the street, card description or map info not clear, or too many variable attributes, missing raster image (geotif), presence of Island, missing name of the road in the Wright_Of_Way feature segment, and info not present either on index card or rater map-geotif

Attribute:

Attribute_Label: SHAPE.LEN

Distribution_Information:

Distributor:

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:00 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: 10.249

Ordering_Instructions: All data is available at <http://opendata.dc.gov>

Metadata_Reference_Information:

Metadata_Date: 20081020

Metadata_Review_Date: 10/02/08

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:00 pm

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Access_Constraints: None

Metadata_Use_Constraints: None

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