Street Centerlines

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: District Department of Transportation
Publication_Date: 20131226
Title: Street Centerlines
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher: DC GIS
Online_Linkage:
Server=10.1.11.144; Service=5151; User=dcgis; Version=SDE.DEFAULT
Description:
Abstract:
Street Centerline Segments. A single line representing each street in the District, segmented at major blocks to preserve geocoding integrity. 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 only the major road types: street centerline.
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: 20131226
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: Planimetrics
Theme_Keyword: road
Theme_Keyword: Interstate
Theme_Keyword: location
Theme_Keyword: Street Centerline
Theme_Keyword: Street
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Washington, DC
Place_Keyword: District of Columbia
Use_Constraints:
Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.
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.3.1.4000

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:
Originator: Dewberry Davis, LLC
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:
SIS Automation
This methodology describes the original centerline capture as part of the 1999 planimetrics:
Step 1 EDMD, D&D, NCPC and designated representatives of DC DPW will meet to accomplish the presentation of the listing of government furnished material that are needed by D&D. Then, set up conventions for the creation of intersection nodes, for attribution, for reporting of omissions, errors, or other QC issues in the SIS data to DC DPW and NCPC. These conventions will be tested and validated during the pilot project.
Step 2 For each contiguous block of centerlines, D&D will extend curb lines through street intersections and generate intersection nodes consistent with DPW guidance established in step 1.
Step 3 Where two or more nodes are present that comprise a single intersection (e.g., two multi-street centerlines that intersect with four nodes), D&D will cluster those nodes and identify an intersection centroid for linking SIS files of street names, address ranges, etc.
Step 4 D&D will overlay the SIS files and conflate them to match the centerlines, nodes, and multi-node centroids. Because of anticipated SIS shortcomings, such as identified in D&D's Washington GIS, Pilot Project Final Report, dated June 30, 1997, this conflation will normally be performed manually.
Step 5 D&D will overlay the georeferenced SIS files over 1995 digital orthophotos and copies of the 1999 planimetric mapping provided by EDI to ensure that the new SIS files satisfy positional accuracy requirements.
Step 6 D&D will deliver one set of ARC/INFO export files (.e00) on CD-ROM to NCPC and will conduct a demonstration, on DPW equipment (PC ArcView), that the current INFO attributes work with the revised streetcenterline file coverage.
Step 7 D&D will conduct on-site field verification surveys (1) direction (2) street name, (3) address ranges for each street segment between cross-streets, (4) number of lanes, (5) directionality of lane, and (6) lane usage.
Step 8 Addition of streets not digitized by EDMD.
Step 9 Correction of address ranges where streets are bisected by added streets.
Step 10 Correction of other SIS data errors observable from "windshield surveys."
Step 11 Provision of discrepancy lists, to NCPC, where SIS street names differ from those posted on street signs. D&D will not change the SIS files to match street signs that are verified in the field.
Process_Date: 1999
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Dewberry Davis, LLC
Contact_Address:
Address_Type: mailing and physical address
Address: 8401 Arlington Blvd.
City: Fairfax
State_or_Province: VA
Postal_Code: 22031
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: 441 4th St NW, Suite 930S
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\streetsegmentln.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\DCGIS.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\streetsegment.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\streetsegment.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\streetsegmentln.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_Date: 20100518
Process_Time: 11112600
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
\\ojsfile1\octodata$\GIS\DistributedData_DVD\DistributedDVD_May2010\DCGIS_CENTRAL_052010.gdb
Process_Date: 20100804
Process_Time: 12570000
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\StreetSegmentLn.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\StreetSegmentLn.xml
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
Server=dcgiscentral.in.dc.gov; Service=5151; Database=dcgis_user; User=dcgis_user; Version=SDE.DEFAULT
Process_Date: 20101124
Process_Time: 12002000
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\StreetSegmentLn.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\StreetSegmentLn.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\streetsegmentln.xml
Process_Date: 20110506
Process_Time: 15453000
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
Server=dcgiscentral.in.dc.gov; Service=5151; User=dcgis_user; Version=SDE.DEFAULT
Process_Date: 20110607
Process_Time: 13254300
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\StreetSegmentLn.xml
Process_Date: 20111110
Process_Time: 09524100
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\StreetSegmentLn.xml
Process_Date: 20111110
Process_Time: 10131400
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
Server=dcgiscentral.in.dc.gov; Service=5151; User=dcgis_user; Version=SDE.DEFAULT
Process_Date: 20111110
Process_Time: 15031300
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\DOCUME~1\fieldm\LOCALS~1\Temp\xml80D.tmp
Process_Date: 20120131
Process_Time: 16272400
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\streetsegment.xml
Process_Date: 20120406
Process_Time: 11375100
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
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.000063
Ordinate_Resolution: 0.000063
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.StreetSegmentLn
Attribute:
Attribute_Label: FROMADDRESSRIGHTTHEO
Attribute_Definition: From address low right theoretical range
Attribute:
Attribute_Label: TOADDRESSRIGHTTHEO
Attribute_Definition: To address high theoretical range
Attribute:
Attribute_Label: ENDMEASURE
Attribute_Definition: end measure
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: SEGMENTTYPE
Attribute_Definition: street centerline type
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Attribute:
Attribute_Label: REGISTEREDNAME
Attribute_Definition: Registered Name of the centerline
Attribute:
Attribute_Label: STREETTYPE
Attribute_Definition: Street Type
Attribute:
Attribute_Label: SOURCEID
Attribute_Definition: Source Identifier
Attribute:
Attribute_Label: QUADRANT
Attribute_Definition: Quandrant Name
Attribute:
Attribute_Label: STREETSEGID
Attribute_Definition: Street Segment unique identifier
Attribute:
Attribute_Label: TOADDRESSLEFTTHEO
Attribute_Definition: to address high left theoretical range
Attribute:
Attribute_Label: UPDATETIMESTAMP
Attribute_Definition: update time stamp for the feature
Attribute:
Attribute_Label: DIRECTIONALITY
Attribute_Definition: directionality of street centerline
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: FROMADDRESSLEFTTHEO
Attribute_Definition: from address low left theoretical range
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
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: FROMNODEID
Attribute_Definition: from node id
Attribute:
Attribute_Label: TONODEID
Attribute_Definition: to node id
Attribute:
Attribute_Label: STREETID
Attribute_Definition: Street identifier for street name
Attribute:
Attribute_Label: BEGINMEASURE
Attribute_Definition: being measure
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: 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
Resource_Description: Downloadable Data
Distribution_Liability:
Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 10.249
Ordering_Instructions:
Most DC GIS datasets can be downloaded from "<http://dcgis.dc.gov>" on the data center page. Orders can also be made by contacting OCTO GIS at "[email protected]", especially for datasets not available for download.

Metadata_Reference_Information:
Metadata_Date: 20131227
Metadata_Review_Date: 05/09/05
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: 441 4th St NW, Suite 930 South
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: [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

Generated by mp version 2.9.12 on Thu Jun 25 15:28:39 2015