Name: Airport Areas (Runway, taxiway, airports or helipad)
Display Field: FEATURECODE
Type: Feature Layer
Geometry Type: esriGeometryPolygon
Description: Taxiway, Apron: Delineate footprint of the following features. A taxiway connects aircraft to other areas and facilities of an airport. The apron is an area of an airport where aircraft are parked, unloaded or loaded, refueled, or boarded. Airport/Heliport Perimeter: Delineate the full perimeter of the airport or heliport. Helipad: Delineate clearly marked hard surface landing area or platform for helicopters.
Copyright Text: Office of the Chief of Technology Officer
Description: Heliport locations. The dataset contains locations and attributes of DC Heliports, 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. The National Transportation Atlas Database (NTAD) provided by the Bureau of Transportation Statistics, US Department of Transportation identified DC Heliport and Airport locations.
Copyright Text: US Department of Transportation - Bureau of Transportation Statistics (BTS)
Description: The dataset contains locations and attributes of Signed Bike Routes, created as part of the District of Columbia, Department of Transportation (DDOT) Street Spatial Database (SSD). A database provided by the District of Columbia, Department of Transportation identified StreetSegment locations.
Copyright Text: District Department of Transportation
Description: Bridges: All bridges are digitized as polygons. Bridges carry roads or railroads over water. Outside edges of all bridges delineated. Also bridge deck locations or clear spans where deck is not visible. This includes all overpasses (bridges that carry traffic over roads or railroads) and underpasses. Outside edge of all overpasses delineated. Bridges overlap road polygons. Pedestrian bridges are not captured. Tunnel Entrances: Entire tunnels are not captured, but all entrances to a tunnel are captured as polygons illustrating the width of the tunnel. Polygons plotted around tunnel openings and any abutments or walls which identify the tunnel entrance. Hidden Bridges: Hidden bridges are features that run under other features such as other bridges, overpasses, or tunnels and are not fully visible in an aerial photograph. The locations are interpreted based on the information visible on either side of the bridge.
Copyright Text: Office of the Chief of Technology Officer
Description: Inventory of alleys within the District including data for alley condition, status, material, and other alley-related information. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.
Copyright Text: District of Columbia, Department of Transportation. Operational Support and Applied Technology (OSAT) - Spatial Data Systems
Description: Interstate Highway Shield symbology locations. The dataset contains locations and attributes to cartographically mark interstates in DC, 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.
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: The dataset contains locations and attributes of intersections created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and participating DC government agencies. The intersection points - MAR is primarily derived from DC Department of Transportation's (DDOT) intersection table in their Street Spatial Database (SSD). Regular at-grade intersections (TYPE = 'REGULAR') as well as overpasses (TYPE = 'OVERPASS'), underpasses (TYPE = 'UNDERPASS') and ramps (TYPE = 'RAMP') are included. The overpasses, underpasses, and ramps are based on street centerlines from DDOT. More information on the MAR can be found at https://opendata.dc.gov/pages/addressing-in-dc. The data dictionary is available: https://opendata.dc.gov/documents/2a4b3d59aade43188b6d18e3811f4fd3/explore. In the MAR 2, the IntersectionPt is called INTERSECTIONS_PT and is primarily based off of street data from DC Department of Transportation's Roads & Highways database. It also features additional useful information such as created date, last edited date, begin date, and more.
Copyright Text: Office of the Chief Technology Officer
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
FHWAFUNCTIONALCLASS
(
type: esriFieldTypeSmallInteger, alias: FHWA Functional Class
, Coded Values:
[1: Interstate]
, [2: Principal Arterial - Other Freeways or Expressways]
, [3: Principal Arterial - Other]
, ...4 more...
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
FHWAFUNCTIONALCLASS
(
type: esriFieldTypeSmallInteger, alias: FHWA Functional Class
, Coded Values:
[1: Interstate]
, [2: Principal Arterial - Other Freeways or Expressways]
, [3: Principal Arterial - Other]
, ...4 more...
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
FHWAFUNCTIONALCLASS
(
type: esriFieldTypeSmallInteger, alias: FHWA Functional Class
, Coded Values:
[1: Interstate]
, [2: Principal Arterial - Other Freeways or Expressways]
, [3: Principal Arterial - Other]
, ...4 more...
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
FHWAFUNCTIONALCLASS
(
type: esriFieldTypeSmallInteger, alias: FHWA Functional Class
, Coded Values:
[1: Interstate]
, [2: Principal Arterial - Other Freeways or Expressways]
, [3: Principal Arterial - Other]
, ...4 more...
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
FHWAFUNCTIONALCLASS
(
type: esriFieldTypeSmallInteger, alias: FHWA Functional Class
, Coded Values:
[1: Interstate]
, [2: Principal Arterial - Other Freeways or Expressways]
, [3: Principal Arterial - Other]
, ...4 more...
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
Description: Road edges are defined as the edge of the improved surface including the improved shoulder but do not include the unimproved shoulder, only the travel part of the road. The road network is compiled to include all open intersections. Features do not overlap sidewalks, but have the sidewalk area cut out of the road polygons. Overlapping features are acceptable if one of the features is hidden. Road: A generally named thoroughfare, that is usually paved and can be public or private. Unimproved thoroughfares are excluded. Road polygons are formed by a combination of road edge, curb, sidewalk, street intersection closure line, and map sheet edge. Paved Median Island: Perimeter of non-traffic paved areas that separate traffic lanes in opposing directions. Unpaved Median Island: Perimeter of non-traffic grassy, unpaved areas that separate traffic lanes in opposing directions. Paved Traffic Island: Perimeter of non-traffic concrete areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Unpaved Traffic Island: Perimeter of non-traffic unpaved, grassy areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Alley: Perimeter of alleys first plotted photogrammetrically from other indicators such as building footprints, fence lines, curb lines, walls, paved or unpaved drives, and map sheet edge. Alley polygons are closed along the lines where they intersect with road polygons. Paved Drive: A paved driveway for a building or entranceway for a parking lot. Driveways are neither streets nor alleys, but provide access to public facilities, such as a drive to a monument, museum, hotel, large estate, sports field or golf course, grounds of the U.S. Capitol, etc. If a driveway is less than 200 feet and leads to a parking lot, the entire paved area is captured as Parking Lot. Driveways are photogrammetrically compiled as polygons and not compiled from individual vectors on different levels. Parking Lot: Generally paved surfaces used for cars to park on. Paved drives usually form entrances to these features, if the drive is more than 200 feet. If the driveway is less than 200 feet leading into the parking lot, the entire paved area is captured as Parking Lot. Parking lots sharing a common boundary with linear features must have the common segment captured once, but coded as both polygon and line. Small parking areas, where individuals park their cars in the middle of a block off a public alley, are not captured as parking lots. These are either public space (e.g., alleys) or private space where owners permit parking to occur. Intersection: A location where more than one road comes together. For standard cross streets, intersection polygons are bounded by curbs and four closure lines at street intersection crosswalks (outer line) or placed arbitrarily where crosswalks could logically be placed. For "T" intersections, the polygons are bounded by curbs and three such closure lines. Complex intersections can have more closure lines. Entire traffic circles are coded as intersections. Hidden Road: A section of a road that passes underneath a bridge or overpass and is not visible in an aerial photograph, but the location can be interpreted based on the road on either side of the bridge. Hidden Median: A road median that exists underneath a bridge or overpass and is not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge.
Copyright Text: Office of the Chief of Technology Officer
Description: Bridges: All bridges are digitized as polygons. Bridges carry roads or railroads over water. Outside edges of all bridges delineated. Also bridge deck locations or clear spans where deck is not visible. This includes all overpasses (bridges that carry traffic over roads or railroads) and underpasses. Outside edge of all overpasses delineated. Bridges overlap road polygons. Pedestrian bridges are not captured. Tunnel Entrances: Entire tunnels are not captured, but all entrances to a tunnel are captured as polygons illustrating the width of the tunnel. Polygons plotted around tunnel openings and any abutments or walls which identify the tunnel entrance. Hidden Bridges: Hidden bridges are features that run under other features such as other bridges, overpasses, or tunnels and are not fully visible in an aerial photograph. The locations are interpreted based on the information visible on either side of the bridge.
Copyright Text: Office of the Chief of Technology Officer
Description: Road edges are defined as the edge of the improved surface including the improved shoulder but do not include the unimproved shoulder, only the travel part of the road. The road network is compiled to include all open intersections. Features do not overlap sidewalks, but have the sidewalk area cut out of the road polygons. Overlapping features are acceptable if one of the features is hidden. Road: A generally named thoroughfare, that is usually paved and can be public or private. Unimproved thoroughfares are excluded. Road polygons are formed by a combination of road edge, curb, sidewalk, street intersection closure line, and map sheet edge. Paved Median Island: Perimeter of non-traffic paved areas that separate traffic lanes in opposing directions. Unpaved Median Island: Perimeter of non-traffic grassy, unpaved areas that separate traffic lanes in opposing directions. Paved Traffic Island: Perimeter of non-traffic concrete areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Unpaved Traffic Island: Perimeter of non-traffic unpaved, grassy areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Alley: Perimeter of alleys first plotted photogrammetrically from other indicators such as building footprints, fence lines, curb lines, walls, paved or unpaved drives, and map sheet edge. Alley polygons are closed along the lines where they intersect with road polygons. Paved Drive: A paved driveway for a building or entranceway for a parking lot. Driveways are neither streets nor alleys, but provide access to public facilities, such as a drive to a monument, museum, hotel, large estate, sports field or golf course, grounds of the U.S. Capitol, etc. If a driveway is less than 200 feet and leads to a parking lot, the entire paved area is captured as Parking Lot. Driveways are photogrammetrically compiled as polygons and not compiled from individual vectors on different levels. Parking Lot: Generally paved surfaces used for cars to park on. Paved drives usually form entrances to these features, if the drive is more than 200 feet. If the driveway is less than 200 feet leading into the parking lot, the entire paved area is captured as Parking Lot. Parking lots sharing a common boundary with linear features must have the common segment captured once, but coded as both polygon and line. Small parking areas, where individuals park their cars in the middle of a block off a public alley, are not captured as parking lots. These are either public space (e.g., alleys) or private space where owners permit parking to occur. Intersection: A location where more than one road comes together. For standard cross streets, intersection polygons are bounded by curbs and four closure lines at street intersection crosswalks (outer line) or placed arbitrarily where crosswalks could logically be placed. For "T" intersections, the polygons are bounded by curbs and three such closure lines. Complex intersections can have more closure lines. Entire traffic circles are coded as intersections. Hidden Road: A section of a road that passes underneath a bridge or overpass and is not visible in an aerial photograph, but the location can be interpreted based on the road on either side of the bridge. Hidden Median: A road median that exists underneath a bridge or overpass and is not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge.
Copyright Text: Office of the Chief of Technology Officer
Description: All public walkways are captured. Sidewalks do not overlap other feature classes unless they are hidden under a bridge or overpass. Cement pads around public swimming pools are captured. Walkways in common areas of apartments, college campuses, and business parks are captured as sidewalks. Individual resident sidewalks are not captured. Sidewalk: Sidewalks either compiled photogrammetrically as polygons or derived from a combination of vectors including: curbs, buildings, walls, driveways, or other features. Any stair feature that is less than 5 stairs is coded as sidewalk to maintain continuity. Hidden Sidewalk: Sidewalks that are obscured by overpasses or tunnels. They are not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge. Stairs: Groups of 5 or more stairs outside of major buildings or monuments, as well as part of sidewalks. Individual stairs are not captured. If landings exist within stairs, they are captured as sidewalk, not stairs. Crosswalk: Marked crosswalks that are fully visible in an aerial photograph.
Copyright Text: Office of the Chief of Technology Officer
Description: All public walkways are captured. Sidewalks do not overlap other feature classes unless they are hidden under a bridge or overpass. Cement pads around public swimming pools are captured. Walkways in common areas of apartments, college campuses, and business parks are captured as sidewalks. Individual resident sidewalks are not captured. Sidewalk: Sidewalks either compiled photogrammetrically as polygons or derived from a combination of vectors including: curbs, buildings, walls, driveways, or other features. Any stair feature that is less than 5 stairs is coded as sidewalk to maintain continuity. Hidden Sidewalk: Sidewalks that are obscured by overpasses or tunnels. They are not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge. Stairs: Groups of 5 or more stairs outside of major buildings or monuments, as well as part of sidewalks. Individual stairs are not captured. If landings exist within stairs, they are captured as sidewalk, not stairs. Crosswalk: Marked crosswalks that are fully visible in an aerial photograph.
Copyright Text: Office of the Chief of Technology Officer
Description: All public walkways are captured. Sidewalks do not overlap other feature classes unless they are hidden under a bridge or overpass. Cement pads around public swimming pools are captured. Walkways in common areas of apartments, college campuses, and business parks are captured as sidewalks. Individual resident sidewalks are not captured. Sidewalk: Sidewalks either compiled photogrammetrically as polygons or derived from a combination of vectors including: curbs, buildings, walls, driveways, or other features. Any stair feature that is less than 5 stairs is coded as sidewalk to maintain continuity. Hidden Sidewalk: Sidewalks that are obscured by overpasses or tunnels. They are not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge. Stairs: Groups of 5 or more stairs outside of major buildings or monuments, as well as part of sidewalks. Individual stairs are not captured. If landings exist within stairs, they are captured as sidewalk, not stairs. Crosswalk: Marked crosswalks that are fully visible in an aerial photograph.
Copyright Text: Office of the Chief of Technology Officer
Description: All public walkways are captured. Sidewalks do not overlap other feature classes unless they are hidden under a bridge or overpass. Cement pads around public swimming pools are captured. Walkways in common areas of apartments, college campuses, and business parks are captured as sidewalks. Individual resident sidewalks are not captured. Sidewalk: Sidewalks either compiled photogrammetrically as polygons or derived from a combination of vectors including: curbs, buildings, walls, driveways, or other features. Any stair feature that is less than 5 stairs is coded as sidewalk to maintain continuity. Hidden Sidewalk: Sidewalks that are obscured by overpasses or tunnels. They are not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge. Stairs: Groups of 5 or more stairs outside of major buildings or monuments, as well as part of sidewalks. Individual stairs are not captured. If landings exist within stairs, they are captured as sidewalk, not stairs. Crosswalk: Marked crosswalks that are fully visible in an aerial photograph.
Copyright Text: Office of the Chief of Technology Officer
Description: Curb: The edge of roads, alleys, ramps or parking lots, other than those for which polygons can be formed. Curbs are rims, usually made of concrete, along a roadway, forming an edge for a sidewalk. Curbs do not occur where the sidewalk meets the road, such as at wheelchair or access ramps, and driveways. Hidden Curb: Hidden curbs are depicted where curbs cross beneath underpasses or through tunnels. The location of these features are inferred.
Copyright Text: Office of the Chief of Technology Officer
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.
Copyright Text: 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.
Copyright Text: DC District Department of Transportation
Description: Intersection Approach Segments are short segments of the route that approach an intersection, in other words, a short section of the road leading up to an intersection.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.
Copyright Text: DC District Department of Transportation
TOTALTRAVELLANES
(
type: esriFieldTypeSmallInteger, alias: Total # Travel Lanes
)
TOTALPARKINGLANES
(
type: esriFieldTypeSmallInteger, alias: Total # Parking Lanes
)
TOTALRAISEDBUFFERS
(
type: esriFieldTypeSmallInteger, alias: Total # Raised Buffers
)
TOTALTRAVELLANEWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of Travel Lanes
)
TOTALCROSSSECTIONWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of All Cross-sections
)
TOTALPARKINGLANEWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of Parking Lanes
)
TOTALRAISEDBUFFERWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of Buffer/Barriers
)
TOTALTRAVELLANESINBOUND
(
type: esriFieldTypeSmallInteger, alias: Total Inbound Travel Lanes
)
TOTALTRAVELLANESOUTBOUND
(
type: esriFieldTypeSmallInteger, alias: Total Outbound Travel Lanes
)
TOTALTRAVELLANESBIDIRECTIONAL
(
type: esriFieldTypeSmallInteger, alias: Total BiDirectional Travel Lanes
)
TOTALTRAVELLANESREVERSIBLE
(
type: esriFieldTypeSmallInteger, alias: Total Reversible Travel Lanes
)
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
BIKELANE_PARKINGLANE_ADJACENT
(
type: esriFieldTypeString, alias: Parking Lane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_THROUGHLANE_ADJACENT
(
type: esriFieldTypeString, alias: Throughlane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_POCKETLANE_ADJACENT
(
type: esriFieldTypeString, alias: Pocket Turnlane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_CONTRAFLOW
(
type: esriFieldTypeString, alias: Bikelane is Contraflow, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_CONVENTIONAL
(
type: esriFieldTypeString, alias: Conventional Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_DUAL_PROTECTED
(
type: esriFieldTypeString, alias: Protected Dual Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_DUAL_BUFFERED
(
type: esriFieldTypeString, alias: Buffered Dual Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_PROTECTED
(
type: esriFieldTypeString, alias: Protected Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_BUFFERED
(
type: esriFieldTypeString, alias: Buffered Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
DOUBLEYELLOW_LINE
(
type: esriFieldTypeString, alias: Double Yellow Line on Segment, length: 255
)
FHWAFUNCTIONALCLASS
(
type: esriFieldTypeSmallInteger, alias: FHWA Functional Class
, Coded Values:
[1: Interstate]
, [2: Principal Arterial - Other Freeways or Expressways]
, [3: Principal Arterial - Other]
, ...4 more...
)
HPMSSECTIONTYPE
(
type: esriFieldTypeSmallInteger, alias: HPMS Section Type
)
ID
(
type: esriFieldTypeString, alias: Overlay Identifier, length: 255
)
IRI
(
type: esriFieldTypeInteger, alias: IRI
)
IRI_DATE
(
type: esriFieldTypeDate, alias: IRI Date, length: 8
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
RIGHTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Rightturn Lane on Segment, length: 255
, 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, length: 255
, 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), length: 255
, 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), length: 255
, 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...
)
FROMSTREET
(
type: esriFieldTypeString, alias: From Street, length: 150
)
TOSTREET
(
type: esriFieldTypeString, alias: To Street, length: 150
)
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.
Copyright Text: District Department of Transportation
TOTALTRAVELLANES
(
type: esriFieldTypeSmallInteger, alias: Total # Travel Lanes
)
TOTALPARKINGLANES
(
type: esriFieldTypeSmallInteger, alias: Total # Parking Lanes
)
TOTALRAISEDBUFFERS
(
type: esriFieldTypeSmallInteger, alias: Total # Raised Buffers
)
TOTALTRAVELLANEWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of Travel Lanes
)
TOTALCROSSSECTIONWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of All Cross-sections
)
TOTALPARKINGLANEWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of Parking Lanes
)
TOTALTRAVELLANESINBOUND
(
type: esriFieldTypeSmallInteger, alias: Total Inbound Travel Lanes
)
TOTALTRAVELLANESOUTBOUND
(
type: esriFieldTypeSmallInteger, alias: Total Outbound Travel Lanes
)
TOTALTRAVELLANESBIDIRECTIONAL
(
type: esriFieldTypeSmallInteger, alias: Total BiDirectional Travel Lanes
)
TOTALTRAVELLANESREVERSIBLE
(
type: esriFieldTypeSmallInteger, alias: Total Reversible Travel Lanes
)
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
BIKELANE_PARKINGLANE_ADJACENT
(
type: esriFieldTypeString, alias: Parking Lane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_THROUGHLANE_ADJACENT
(
type: esriFieldTypeString, alias: Throughlane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_POCKETLANE_ADJACENT
(
type: esriFieldTypeString, alias: Pocket Turnlane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_CONTRAFLOW
(
type: esriFieldTypeString, alias: Bikelane is Contraflow, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_CONVENTIONAL
(
type: esriFieldTypeString, alias: Conventional Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_DUAL_PROTECTED
(
type: esriFieldTypeString, alias: Protected Dual Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_DUAL_BUFFERED
(
type: esriFieldTypeString, alias: Buffered Dual Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_PROTECTED
(
type: esriFieldTypeString, alias: Protected Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_BUFFERED
(
type: esriFieldTypeString, alias: Buffered Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
DOUBLEYELLOW_LINE
(
type: esriFieldTypeString, alias: Double Yellow Line on Segment, length: 255
)
HPMSSECTIONTYPE
(
type: esriFieldTypeSmallInteger, alias: HPMS Section Type
)
ID
(
type: esriFieldTypeString, alias: Overlay Identifier, length: 255
)
IRI
(
type: esriFieldTypeInteger, alias: IRI
)
IRI_DATE
(
type: esriFieldTypeDate, alias: IRI Date, length: 8
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
TOTALRAISEDBUFFERWIDTH
(
type: esriFieldTypeSmallInteger, alias: Width of Buffer/Barriers
)
AADT_YEAR
(
type: esriFieldTypeInteger, alias: AADT Year
)
RIGHTTURN_EXCLUSIVE
(
type: esriFieldTypeString, alias: Excl Right turn Lane on Segment, length: 255
, 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, length: 255
, 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), length: 255
, 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), length: 255
, 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...
)
FROMSTREET
(
type: esriFieldTypeString, alias: From Street, length: 150
)
TOSTREET
(
type: esriFieldTypeString, alias: To Street, length: 150
)
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.
Copyright Text: District Department of Transportation
TOTALTRAVELLANESBIDIRECTIONAL
(
type: esriFieldTypeSmallInteger, alias: Total BiDirectional Travel Lanes
)
TOTALTRAVELLANESREVERSIBLE
(
type: esriFieldTypeSmallInteger, alias: Total Reversible Travel Lanes
)
SUMMARYDIRECTION
(
type: esriFieldTypeString, alias: General Directionality for Segment, length: 255
, Coded Values:
[BD: Bi-directional]
, [OB: Oneway in Outbound Direction]
, [IB: Oneway in Inbound Direction]
)
BIKELANE_PARKINGLANE_ADJACENT
(
type: esriFieldTypeString, alias: Parking Lane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_THROUGHLANE_ADJACENT
(
type: esriFieldTypeString, alias: Throughlane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_POCKETLANE_ADJACENT
(
type: esriFieldTypeString, alias: Pocket Turnlane Adjacent to Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_CONTRAFLOW
(
type: esriFieldTypeString, alias: Bikelane is Contraflow, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_CONVENTIONAL
(
type: esriFieldTypeString, alias: Conventional Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_DUAL_PROTECTED
(
type: esriFieldTypeString, alias: Protected Dual Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_PROTECTED
(
type: esriFieldTypeString, alias: Protected Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
BIKELANE_BUFFERED
(
type: esriFieldTypeString, alias: Buffered Bikelane, length: 255
, Coded Values:
[BD: Both Sides of Roadway]
, [IB: Inbound Side of Roadway]
, [OB: Outbound Side of Roadway]
)
DOUBLEYELLOW_LINE
(
type: esriFieldTypeString, alias: Double Yellow Line on Segment, length: 255
)
HPMSSECTIONTYPE
(
type: esriFieldTypeSmallInteger, alias: HPMS Section Type
)
ID
(
type: esriFieldTypeString, alias: Overlay Identifier, length: 255
)
IRI
(
type: esriFieldTypeInteger, alias: IRI
)
IRI_DATE
(
type: esriFieldTypeDate, alias: IRI Date, length: 8
)
NHSCODE
(
type: esriFieldTypeSmallInteger, alias: NHS Code
, Coded Values:
[0: Not on the NHS]
, [1: Is on the NHS]
, [2: Major Airport]
, ...7 more...
)
BIKELANE_DUAL_BUFFERED
(
type: esriFieldTypeString, alias: Buffered Dual Bikelane, length: 255
, 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, length: 255
, 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, length: 255
, 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), length: 255
, 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), length: 255
, 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...
)
FROMSTREET
(
type: esriFieldTypeString, alias: From Street, length: 500
)
TOSTREET
(
type: esriFieldTypeString, alias: To Street, length: 150
)
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 DDOT's wiki page.
Copyright Text: District Department of Transportations (DDOT)
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/