Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This data was created for the inclusion in DC’s computer aided dispatch (CAD) system’s basemap. It was digitized using DC imagery and attributed by OCTO GIS staff with the assistance of DC Fire and Emergency Service’s Fireboat team.
Description: Roads and Highways manages intersections, however they are not singular points; RH creates a series of points - one for each intersecting road at that intersection. For DDOT, it is more useful to have a single intersection point representing the intersection. Through a custom DDOT script,the series of intersection points is reduced into a single representative point.For more information please visit DDOT's wiki page at https://wiki.ddot.dc.gov/display/public/GIS/Roadway+Characteristics
Copyright Text: DC District Department of Transportation
Description: Roads and Highways manages intersections, however they are not singular points; RH creates a series of points - one for each intersecting road at that intersection. For DDOT, it is more useful to have a single intersection point representing the intersection. Through a custom DDOT script,the series of intersection points is reduced into a single representative point.For more information please visit DDOT's wiki page at https://wiki.ddot.dc.gov/display/public/GIS/Roadway+Characteristics
Copyright Text: DC District Department of Transportation
Description: Roads and Highways manages intersections, however they are not singular points; RH creates a series of points - one for each intersecting road at that intersection. For DDOT, it is more useful to have a single intersection point representing the intersection. Through a custom DDOT script,the series of intersection points is reduced into a single representative point.For more information please visit DDOT's wiki page at https://wiki.ddot.dc.gov/display/public/GIS/Roadway+Characteristics
Copyright Text: DC District Department of Transportation
RIGHTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Rightturn Lane on Segment, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Rightturn_exclusive
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
LEFTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Leftturn Lane on Segment, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Leftturn_exclusive
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BUSLANE_OUTBOUND
(
type: esriFieldTypeString, alias: Bus Lane (Outbound), editable: true, nullable: true, length: 255, defaultValue: null, modelName: BUSLANE_OUTBOUND
, Coded Values:
[L1: Dedicated Bus Lane in the curblane]
, [L2: Dedicated Bus Lane in lane adjacent to the curblane (usually a parking lane is the curblane for these cases)]
, [L3: Dedicated Bus Lane in both curblane and next lane over.]
, ...4 more...
)
BUSLANE_INBOUND
(
type: esriFieldTypeString, alias: Bus Lane (Inbound), editable: true, nullable: true, length: 255, defaultValue: null, modelName: BUSLANE_INBOUND
, Coded Values:
[L1: Dedicated Bus Lane in the curblane]
, [L2: Dedicated Bus Lane in lane adjacent to the curblane (usually a parking lane is the curblane for these cases)]
, [L3: Dedicated Bus Lane in both curblane and next lane over.]
, ...4 more...
)
Description: SubBlock represent the near-full extent of our centerline network (only driveways are excluded). SubBlock is the finest grained, 'base' segments from which all other segmentation patterns can be constructed (including Blocks). SubBlock is the original source features for our DDOT Street Centerlines data. Road types include streets, Alleys, Ramps, Service Roads, and Trails. Previously called Roadway Segments. For more information please visit DDOT's wiki page at https://wiki.ddot.dc.gov/display/public/GIS/Roadway+Characteristics
Copyright Text: DC District Department of Transportation
RIGHTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Excl Right turn Lane on Segment, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Rightturn_exclusive
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
LEFTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Excl Left turn Lane on Segment, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Leftturn_exclusive
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BUSLANE_INBOUND
(
type: esriFieldTypeString, alias: Bus Lane (Inbound), editable: true, nullable: true, length: 255, defaultValue: null, modelName: BUSLANE_INBOUND
, Coded Values:
[L1: Dedicated Bus Lane in the curblane]
, [L2: Dedicated Bus Lane in lane adjacent to the curblane (usually a parking lane is the curblane for these cases)]
, [L3: Dedicated Bus Lane in both curblane and next lane over.]
, ...4 more...
)
BUSLANE_OUTBOUND
(
type: esriFieldTypeString, alias: Bus Lane (Outbound), editable: true, nullable: true, length: 255, defaultValue: null, modelName: BUSLANE_OUTBOUND
, Coded Values:
[L1: Dedicated Bus Lane in the curblane]
, [L2: Dedicated Bus Lane in lane adjacent to the curblane (usually a parking lane is the curblane for these cases)]
, [L3: Dedicated Bus Lane in both curblane and next lane over.]
, ...4 more...
)
Description: For a city, street blocks are a very common way in which to organize and relate work (e.g. 'I need to fix a pothole on the 1600 Block of Pennsylvania Ave'). Although driveways or alleys may intersect streets, this representation requires that the segment remain unbroken. Road types include streets. Previously Called Street Segments. Note that there are no from/to address fields. We will not be maintaining them in our data. There also will be no generating a 'streetname' list.For more information please visit DDOT's wiki page at https://wiki.ddot.dc.gov/display/public/GIS/Roadway+Characteristics
Copyright Text: DC District Department of Transportation
BIKELANE_DUAL_BUFFERED
(
type: esriFieldTypeString, alias: Buffered Dual Bikelane, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Bikelane_dual_buffered
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
RIGHTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Excl Rightturn Lane on Segment, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Rightturn_exclusive
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
LEFTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Excl Leftturn Lane on Segment, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Leftturn_exclusive
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BUSLANE_INBOUND
(
type: esriFieldTypeString, alias: Bus Lane (Inbound), editable: true, nullable: true, length: 255, defaultValue: null, modelName: BUSLANE_INBOUND
, Coded Values:
[L1: Dedicated Bus Lane in the curblane]
, [L2: Dedicated Bus Lane in lane adjacent to the curblane (usually a parking lane is the curblane for these cases)]
, [L3: Dedicated Bus Lane in both curblane and next lane over.]
, ...4 more...
)
BUSLANE_OUTBOUND
(
type: esriFieldTypeString, alias: Bus Lane (Outbound), editable: true, nullable: true, length: 255, defaultValue: null, modelName: BUSLANE_OUTBOUND
, Coded Values:
[L1: Dedicated Bus Lane in the curblane]
, [L2: Dedicated Bus Lane in lane adjacent to the curblane (usually a parking lane is the curblane for these cases)]
, [L3: Dedicated Bus Lane in both curblane and next lane over.]
, ...4 more...
)
Description: Blockface Segments are unbroken sections of the curb. A blockface can be made up of several subblocks, or just one subblock. There are blockfaces on both sides of the road, each dependent on an unbroken length of curb. For more information please visit https://wiki.ddot.dc.gov/display/public/GIS/Roadway+Characteristics.
Copyright Text: District Department of Transportations (DDOT)
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field:
Fields:
ROUTEID
(
type: esriFieldTypeString, alias: Unique identifier of the route that this blockface is on, editable: true, nullable: true, length: 500, defaultValue: null, modelName: ROUTEID
)
SIDE
(
type: esriFieldTypeString, alias: Which side of the route is this blockface on, when looking in digitizing direction, editable: true, nullable: true, length: 255, defaultValue: null, modelName: SIDE
)
MEAS_FROM
(
type: esriFieldTypeDouble, alias: measure along the route does this blockface begin, editable: true, nullable: true, defaultValue: null, modelName: MEAS_FROM
)
MEAS_TO
(
type: esriFieldTypeDouble, alias: measure along the route does this blockface end, editable: true, nullable: true, defaultValue: null, modelName: MEAS_TO
)
OFFSET
(
type: esriFieldTypeSmallInteger, alias: Offset value to be able to visualize the blockfaces on a map, editable: true, nullable: true, defaultValue: null, modelName: Offset
)
Description: Locations of Symbolic Street Names otherwise known as Honorary Streetnames. The dataset contains locations and attributes of Symbolic Street Names, 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. Each block which has an symbolic streetname will have one record. Data is sourced from field research and DC Government's Legislative Information Management System (LIMS) database. https://lims.dccouncil.gov/