Description: A Milepoint represents the location along a CDOT highway where that highway's linear reference system indicates a whole number reference point (i.e., milepoints are whole number reference points, such as 57.000). Please note, mile posts are not necessarily found at milepoints. Milepoint features are represented by point geographic shapes. Bounding coordinates and feature counts reflect a statewide extent.
Color: [0, 0, 0, 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: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Features in this dataset represent public highways that are maintained by and under the jurisdiction of the Colorado Department of Transportation. These highways consist of Interstates, US Highways, and State Highways, and are represented by polyline (linear) geographic shapes. These shapes have been generalized (some vertices removed) for simpler cartography at small map scales.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: GIS dataset of intersections with identified crash patterns on the state and federal highway system in Colorado, from outputs generated in Vision Zero Suite. A cumulative probability threshold of 95th percentile and min number of 5 crashes was used to identify pattern types. Pattern types overlap in this dataset, resulting in up to 12 pattern types for the same intersection in certain instances. The patterns are categorized by type in the "SEV_PAT", "VEH_PAT", "LOC_PAT", "ACC_PAT", "LIGHT_PAT", "WEATH_PAT", "ROAD_PAT", "HCF_PAT", "DRV_PAT" fields. Other pattern types may be identified in any given record, so users should be careful in using key word searches in these fields. Fields include beginning/ending MPs from model, highway number, pattern type (by category), latitude/longitude, and intersection type. Pattern types identified included the following:APPROACH TURNBICYCLEBROADSIDECONCRETE BARRIERCRASH CUSHIONCURBDARK - LIGHTEDDARK - UNLIGHTEDDAWN OR DUSKDAYLIGHTDRIVER 1 - ALCOHOL INVOLVEDDRIVER 1 - DISTRACTED BY PASSENGERDRIVER 1 - DRIVER FATIGUEDRIVER 1 - DRIVER INEXPERIENCEDRIVER 1 - DRIVER PREOCCUPIEDDRIVER 1 - DRIVER UNFAMILIAR WITH AREADRIVER 1 - NO APPARENT CONTRIBUTING FACTORDRIVER 1 - NO IMPAIRMENT SUSPECTEDDRIVER 1 - UNKNOWN CONTRIBUTING FACTORDRY ROADFOGICY ROADINJURY (INJ)NO ADVERSE WEATHEROFF ROADOFF ROAD LEFTOFF ROAD RIGHTON ROADOTHER FIXED OBJECTOVERTAKING TURNPARKED MOTOR VEHICLEPEDESTRIANPROPERTY DAMAGE ONLYRAINREAR ENDSIDESWIPE (OPPOSITE DIRECTION)SIDESWIPE (SAME DIRECTION)SIGNSLUSHY ROADSNOW OR SLEET OR HAILSNOWY ROADTOTAL FIXED OBJECTSTRAFFIC SIGNAL POLEUNKNOWN ROAD CONDITIONUNKNOWN WEATHERWET ROADWILD ANIMAL
Copyright Text: Tabular data from VZS modeling provided by Bryan Allery with DiExSys. Spatial dataset generated by Evan Kirby, Associate with FHU - [email protected]
Description: GIS dataset of intersections with identified crash patterns on the state and federal highway system in Colorado, from outputs generated in Vision Zero Suite. A cumulative probability threshold of 95th percentile and min number of 5 crashes was used to identify pattern types. Pattern types overlap in this dataset, resulting in up to 12 pattern types for the same intersection in certain instances. The patterns are categorized by type in the "SEV_PAT", "VEH_PAT", "LOC_PAT", "ACC_PAT", "LIGHT_PAT", "WEATH_PAT", "ROAD_PAT", "HCF_PAT", "DRV_PAT" fields. Other pattern types may be identified in any given record, so users should be careful in using key word searches in these fields. Fields include beginning/ending MPs from model, highway number, pattern type (by category), latitude/longitude, and intersection type. Pattern types identified included the following:APPROACH TURNBICYCLEBROADSIDECONCRETE BARRIERCRASH CUSHIONCURBDARK - LIGHTEDDARK - UNLIGHTEDDAWN OR DUSKDAYLIGHTDRIVER 1 - ALCOHOL INVOLVEDDRIVER 1 - DISTRACTED BY PASSENGERDRIVER 1 - DRIVER FATIGUEDRIVER 1 - DRIVER INEXPERIENCEDRIVER 1 - DRIVER PREOCCUPIEDDRIVER 1 - DRIVER UNFAMILIAR WITH AREADRIVER 1 - NO APPARENT CONTRIBUTING FACTORDRIVER 1 - NO IMPAIRMENT SUSPECTEDDRIVER 1 - UNKNOWN CONTRIBUTING FACTORDRY ROADFOGICY ROADINJURY (INJ)NO ADVERSE WEATHEROFF ROADOFF ROAD LEFTOFF ROAD RIGHTON ROADOTHER FIXED OBJECTOVERTAKING TURNPARKED MOTOR VEHICLEPEDESTRIANPROPERTY DAMAGE ONLYRAINREAR ENDSIDESWIPE (OPPOSITE DIRECTION)SIDESWIPE (SAME DIRECTION)SIGNSLUSHY ROADSNOW OR SLEET OR HAILSNOWY ROADTOTAL FIXED OBJECTSTRAFFIC SIGNAL POLEUNKNOWN ROAD CONDITIONUNKNOWN WEATHERWET ROADWILD ANIMAL
Copyright Text: Tabular data from VZS modeling provided by Bryan Allery with DiExSys. Spatial dataset generated by Evan Kirby, Associate with FHU - [email protected]
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: LOSS is reported in this dataset only where crash patterns have been previously identified for highway segments and intersections. This product was produced in 2015 from crash data circa 2009 - 2013. LOSS is reported in levels 1 through 4 (1 = low potential for accident reduction, 2 = low to moderate potential for accident reduction, 3 = less moderate to high potential for accident reduction, 4 = high potential for accident reduction). LOSS values for total accidents may be the same as LOSS values for severity accidents, though the values can be different (e.g. LOSS total for a segment could be a 2 for Total LOSS and 3 for severity). LOSS values were determined using a cumulative probability threshold of 80th percentile and a minimum number of 5 crashes. Intersection locations were mapped using CDOT's 2013 linear referencing system. Approximately 927 out of 2457 records had no LOSS values reported. The database contains fields for LOSS Total and LOSS Severity (injury + fatal), and crash patterns by category.LOSS is calculated using DiExSys Vision Zero Suite (VZS). LOSS was generated using spreadsheets provided by David Swenka with CDOT. This dataset represents an interim product; new SPF models will soon be developed and will affect the LOSS. An additional task has already been identified to run LOSS statewide upon completion of the updated SPF models.
Copyright Text: DiExSys Visions Zero Suite (Jake Kononov & Bryan Allery), Evan Kirby, GISP with FHU, and David Swenka, Traffic Engineer with CDOT.
Description: Features in this dataset represent public highways that are maintained by and under the jurisdiction of the Colorado Department of Transportation. These highways consist of Interstates, US Highways, and State Highways, and are represented by polyline (linear) geographic shapes. These shapes have been generalized (some vertices removed) for simpler cartography at small map scales.Represents 2017 Routes.