{
 "culture": "en-US",
 "name": "",
 "guid": "",
 "catalogPath": "",
 "snippet": "Intersections ranked by Safety Priority Index System (SPIS) score to help identify potential safety problems.\n\nOfficially adopted 6/28/2019.",
 "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>",
 "summary": "Intersections ranked by Safety Priority Index System (SPIS) score to help identify potential safety problems.\n\nOfficially adopted 6/28/2019.",
 "title": "distribution.TRANSPOR.SPIS1416",
 "tags": [
  "Saftey",
  "priority",
  "index",
  "system",
  "SPIS",
  "ODOT",
  "intersection",
  "crash",
  "washington",
  "county"
 ],
 "type": "",
 "typeKeywords": [],
 "thumbnail": "",
 "url": "",
 "minScale": 150000000,
 "maxScale": 5000,
 "spatialReference": "",
 "accessInformation": "",
 "licenseInfo": ""
}