Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Black Font Style: normal Font Weight: normal Font Decoration: none
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]
)
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]
)
DOUBLEYELLOW_LINE
(
type: esriFieldTypeString, alias: Double Yellow Line on Segment, length: 255
)
HPMSSECTIONTYPE
(
type: esriFieldTypeSmallInteger, alias: HPMS Section Type
)
ID
(
type: esriFieldTypeString, alias: Overlay ID, 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...
)
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: This dataset contains 3D rooftops for the District of Columbia in ESRI multipatch format. It includes structures originally captured from 2005 aerial imagery together with updates based on 2010 aerial imagery. It was produced under contract to the District of Columbia by CyberCity3D, Inc. using stereo imagery and a proprietary extraction process that identifies roof polygon points and then creates entire structures from them to form roof polygons.Attributes containing roof height, slope and orientation are included. This dataset is an update to a previous 3D dataset produced in 2006 using 2005 imagery. It specifically includes updates to building rooftops identified in the course of the District of Columbia’s separate planimetric update effort, which noted structures known that were added, modified between or deleted between 2008 and 2010. Although it was intended to capture all new buildings irrespective of whether or not they were identified through the planimetric update process, it is likely that building rooftop changes not identified through the planimetric update process may not have been captured. This dataset contains full rooftops, including protrusions such as gabled windows, chimneys, elevator utility rooms, etc.. There were also additional datasets delivered which broke out those roof elements into separate files, as well as deliveries which included complete 3D buildings with rooftops and facades. In many instances, row-houses and other contiguous building rooftops could not be broken apart using the process methodology and appear as a single structure. In some cases, entire blocks of row houses are represented as a single feature, though visually they can be distinguished easily. Additionally, the process captured small features, such as canopy umbrellas and other structures as building rooftops and these features may exist at various locations in the dataset.Many data gaps in the earlier dataset (largely due to missing or reduced-resolution source imagery) are corrected in this product. Based on comparison to DC’s available planimetric datasets, there are still instances where particular structures are omitted or not updated in the current product, but we believe that upwards of 99% of the District’s buildings are reflected in this dataset.All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.
Copyright Text: District of Columbia Office of Planning
CyberCity 3D
Description: This dataset contains 3D rooftops for the District of Columbia in ESRI multipatch format. It includes structures originally captured from 2005 aerial imagery together with updates based on 2010 aerial imagery. It was produced under contract to the District of Columbia by CyberCity3D, Inc. using stereo imagery and a proprietary extraction process that identifies roof polygon points and then creates entire structures from them to form roof polygons.Attributes containing roof height, slope and orientation are included. This dataset is an update to a previous 3D dataset produced in 2006 using 2005 imagery. It specifically includes updates to building rooftops identified in the course of the District of Columbia’s separate planimetric update effort, which noted structures known that were added, modified between or deleted between 2008 and 2010. Although it was intended to capture all new buildings irrespective of whether or not they were identified through the planimetric update process, it is likely that building rooftop changes not identified through the planimetric update process may not have been captured. This dataset contains full rooftops, including protrusions such as gabled windows, chimneys, elevator utility rooms, etc.. There were also additional datasets delivered which broke out those roof elements into separate files, as well as deliveries which included complete 3D buildings with rooftops and facades. In many instances, row-houses and other contiguous building rooftops could not be broken apart using the process methodology and appear as a single structure. In some cases, entire blocks of row houses are represented as a single feature, though visually they can be distinguished easily. Additionally, the process captured small features, such as canopy umbrellas and other structures as building rooftops and these features may exist at various locations in the dataset.Many data gaps in the earlier dataset (largely due to missing or reduced-resolution source imagery) are corrected in this product. Based on comparison to DC’s available planimetric datasets, there are still instances where particular structures are omitted or not updated in the current product, but we believe that upwards of 99% of the District’s buildings are reflected in this dataset.All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.
Copyright Text: District of Columbia Office of Planning
CyberCity 3D