20190617 14132000 1.0 ISO 19139 Metadata Implementation Specification FALSE SPIS1416 002 7487464.467848 7626227.751312 616743.343504 775476.207021 1 Projected GCS_North_American_1983_HARN Linear Unit: Foot (0.304800) NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.6'><WKT>PROJCS["NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",8202099.737532808],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-120.5],PARAMETER["Standard_Parallel_1",44.33333333333334],PARAMETER["Standard_Parallel_2",46.0],PARAMETER["Latitude_Of_Origin",43.66666666666666],UNIT["Foot",0.3048],AUTHORITY["EPSG",2913]]</WKT><XOrigin>-111333600</XOrigin><YOrigin>-98152500</YOrigin><XYScale>3048</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808398950131233</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2913</WKID><LatestWKID>2913</LatestWKID></ProjectedCoordinateSystem> 20190628 16335500 20190628 16342800 150000000 5000 ISO19139 Esri ArcGIS 10.6.1.9273 SPIS1416 1 -123.300536 -122.739819 45.771638 45.324639 Intersections ranked by Safety Priority Index System (SPIS) score to help identify potential safety problems. Officially adopted 6/28/2019. <DIV STYLE="text-align:Left;"><DIV><DIV>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).See the SPIS score field metadata definition for the full SPIS calculation equation.There is a model builder model within the following folder that outlines and details most of the process: Saftey priority index system SPIS ODOT intersection crash washington county Feature Class dataset EPSG 6.13(9.0.0) 359 Simple FALSE 359 TRUE FALSE SPIS1416 Feature Class 359 OBJECTID OBJECTID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Shape Geometry 4 0 0 Feature geometry. Esri Coordinates defining the features. Xsect_ID Xsect_ID String 12 0 0 Unique intersection ID that is from the distribution.STREETS.XsectID feature class on NUTSDE. The value from the MIN_XsectID field within the distribution.STREETS.XsectID feature class is the value used in the SPIS table. It is based off the street centerline segment local ID (with a 1 or 2 added to the end to create a unique integer). Washington County Road_Name ROAD String 255 0 0 This is the main road name for the intersection. The road name has been modified from the street centerline legal name to conform to the SPIS report format. The prefix (quadrant) has been stripped as well. If the road also has a Oregon route number (e.g.10) then it has been added as a parenthesized suffix (e.g. Farmington Rd (OR 10)). Generally, when there is a County road intersecting with a non-County road, the County road name will go into this field and the non-County road name will go into the [X_Road_Name] field. Washington County X_Road_Name XSECT String 255 0 0 This is the intersecting road name for the intersection. This road name has been modified from the street centerline legal name to conform to the SPIS report format. The prefix (quadrant) has been stripped as well. If the road also has a Oregon route number (e.g.10) then it has been added as a parenthesized suffix (e.g. Farmington Rd (OR 10)). Generally, when there is a County road intersecting with a non-County road, the County road name will go into the [Road_Name] field and the non-County road name will go into this field. Washington County Rank Rank Integer 4 10 0 This is the rank of the intersection in this 50% list of all SPIS-eligble intersections involving a County jurisdication road. The rank is sorted by the SPIS score in decending order. Generally, the lower the score the more potenial safety issues. Washington County SPIS_Score SPIS_Score Double 8 38 8 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 of 3 separate calculations (portions) for frequency, rate, and severity. The crashes around an intersection are summarized into 5 categories (Fatal, Level A Injuries, Level B Injuries, Level C Injuries, and Property Damage only) and then totaled (Total crashes). The traffic volume is calculated by totaling the traffic counts for all road sections ENTERING an intersection. A 2-way road would only have 50% the ADT value to approximate the traffic entering the intersection. A 1-way street that enters the intersection would get 100% the ADT value and conversely a 1-way exiting an intersection would not have any ADT value considered. The equations (in excel) are as follows: Frequency: =MIN(25,LOG([Total Crashes]+1)/LOG(151)*25) Rate: =MIN(25,LOG(([Total Crashes]*1000000)/(1095*[Intersection Total Volume])+1)/LOG(8)*25) Severity: =MIN(50,(([Total Fatal Crashes]+[Total Level A Crashes])*100+([Total Level B Crashes]+[Total Level C Crashes])*10+[Total Property Damage Only Crashes])/300*50) SPIS Score: =[Frequency Portion] + [Rate Portion] + [Severity Portion] Washington County RankPrior1 RankPrior1 Integer 4 10 0 This is the previous ranked SPIS score this intersection recieved in the prior SPIS calculation from last year. This SPIS score was from the calcuation using crashes in 2013-2015. Washington County RankPrior2 RankPrior2 Integer 4 10 0 This is the previous SPIS score this intersection recieved in the prior SPIS calculation performed 2 years ago. This SPIS score was from the calcuation using crashes in 2012-2014. Washington County RankPrior3 RankPrior3 Integer 4 10 0 This is the previous SPIS score this intersection recieved in the prior SPIS calculation performed 3 years ago. This SPIS score was from the calcuation using crashes in 2011-2013. Washington County DataYear DataYear String 10 0 0 This is the years of crash data this SPIS score and SPIS rank was determined from. For this data it is 2014-2016 crash data. Washington County SPIS_PointX SPIS_PointX Double 8 38 8 This is the X coordinate for the intersection location in feet (based on NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl WKID: 2913). Note: maybe this was meant to be Longitude in decimal degrees? Washington County SPIS_PointY SPIS_PointY Double 8 38 8 This is the Y coordinate for the intersection location in feet (based on NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl WKID: 2913). Note: maybe this was meant to be Latitude in decimal degrees? Washington County Color Color String 9 0 0 This is the symbology color of the SPIS point as seen in the Operations and Maintenance Asset Browser web mapping applciation. Red: for ranks less than 50 Blue: for ranks from 50 to 150 Green: for ranks over 150 Washington County 20190628 Traffic Engineering GIS Analyst Washington County, Department of Land Use & Transportation, Traffic Engineering GIS Analyst