Placement
(
type: esriFieldTypeString, alias: Placement, length: 10
, Coded Values:
[L: Lefthand Side Of Road]
, [R: Righthand Side Of Road]
, [B: Both Sides of Road]
)
Description: This inventory was taken for the urban arterial and collector road network. Several exceptions were made to include non-arterial and collector roadways for improved connectivity. The project used the most recent aerial photos as they became available, from 2009 to 2016. Other revisions were made via public comments and field checking. Sections of road with funded projects scheduled to begin that year were inventoried as existing. Last updated 2018.
Service Item Id: 6cf9b948e2d549a399a47040b0a21881
Copyright Text: Washington County, Long Range Planning
CLASS
(
type: esriFieldTypeSmallInteger, alias: RoadClassification
, Coded Values:
[100: Freeway]
, [110: On Ramp (only)]
, [111: Off Ramp (only)]
, ...27 more...
)
DRCT
(
type: esriFieldTypeSmallInteger, alias: RoadDirection
, Coded Values:
[0: No data]
, [1: Two way street]
, [2: One way street (traffic with arc direction)]
, ...1 more...
)
LFacility
(
type: esriFieldTypeString, alias: Left Ped, length: 50
, Coded Values:
[Standard: Facility exists and is up to standard]
, [Suitable: Suitable conditions or substandard facility]
, [None: No facility]
)
RFacility
(
type: esriFieldTypeString, alias: Right Ped, length: 50
, Coded Values:
[Standard: Facility exists and is up to standard]
, [Suitable: Suitable conditions or substandard facility]
, [None: No facility]
)
Description: This inventory was taken for the urban arterial and collector road network. Several exceptions were made to include non-arterial and collector roadways for improved connectivity. The project used the most recent aerial photos as they became available, from 2009 to 2016. Other revisions were made via public comments and field checking. Sections of road with funded projects scheduled to begin that year were inventoried as existing. Last updated 2018.
Service Item Id: 6cf9b948e2d549a399a47040b0a21881
Copyright Text: Washington County, Long Range Planning
CLASS
(
type: esriFieldTypeSmallInteger, alias: RoadClassification
, Coded Values:
[100: Freeway]
, [110: On Ramp (only)]
, [111: Off Ramp (only)]
, ...27 more...
)
DRCT
(
type: esriFieldTypeSmallInteger, alias: RoadDirection
, Coded Values:
[0: No data]
, [1: Two way street]
, [2: One way street (traffic with arc direction)]
, ...1 more...
)
LFacility
(
type: esriFieldTypeString, alias: Left Bike, length: 50
, Coded Values:
[Standard: Facility exists and is up to standard]
, [Suitable: Suitable conditions or substandard facility]
, [None: No facility]
)
RFacility
(
type: esriFieldTypeString, alias: Right Bike, length: 50
, Coded Values:
[Standard: Facility exists and is up to standard]
, [Suitable: Suitable conditions or substandard facility]
, [None: No facility]
)
DIR
(
type: esriFieldTypeSmallInteger, alias: Line Angle
)
Name: Safety Priority Index System (SPIS) 2014-2016
Display Field: Road_Name
Type: Feature Layer
Geometry Type: esriGeometryPoint
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 0 0;"><SPAN>The SPIS score is determined by a weighted calculation based on summarized crashes over 3 years and traffic volume within 1/10 mile around intersections that have a Washington County jurisdiction road involved. The score is a total score considering frequency, rate, and severity. This is a 50% list of all SPIS-eligible intersections after the calculation was run. A SPIS eligible intersection either has 1) 3 or more crashes OR 2) 1 or more fatal crashes, over the 3 year period. The traffic volume is calculated based on the most recent traffic count data (from Washington County and other jurisdictions) of the 3 year crash data (i.e. the crash data is from 2014-2016 so the traffic volumes are from 2016 traffic counts).</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>See the SPIS score field metadata definition for the full SPIS calculation equation.</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>There is a model builder model within the following folder that outlines and details most of the process: \\emcgis\NAS\GISDATA\Workgroups\GISEngineering\Traffic\SPIS\2014_2016\model</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data represents locations of traffic signals, flashers, and intelligent transportation system (ITS) equipment that Washington County owns and/or maintains as well as some other jurisdiction's equipment within Washington County. It contains the following types of traffic control devices: traffic signals, school signals and flashers, fire signals and flashers, warning flashers, stop flashers, ramp meters, speed feedback signs, curve warnings, and flood gates.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 6cf9b948e2d549a399a47040b0a21881
Copyright Text: Washington County, Department of Land Use & Transportation, Engineering and Construction Services, Traffic Engineering