The Network Screening - Intersections application is designed to help users rank all intersections in their roadway network in an easy-to-use interface. The Network Screening - Intersections application has 5 key features: Attribute Search, Intersection Flyout, Intersection Ranking, Contextual Data, and the Network Screening - Intersections report. Each feature is discussed in more detail below.

Use Numetric’s powerful text-to-search feature to run custom intersection network screening requests. Search by recommended countermeasure, crash type, or any other crash or roadway attribute, and generate instant intersection rankings that tell you which intersections require your attention.

(A network analysis ranking all intersections that would benefit from a left turn phasing change in a given county.)

Intersection Flyout

Clicking on any intersection in your network displays the Intersection flyout, which contains current, and historical intersection rankings, a summary  of crash statistics (including number of crashes and fatal (critical) crashes, crash rate), a summary of the roadway details for all intersecting routes (including AADT, function classes, and any other roadway datapoint present in your data), and a list of recommended countermeasures for that intersection. 

(The Intersection Flyout illustrating the Intersection rank crashes by Route, the summary, and part of the roadway details section.)

Intersection Ranking

Rank your selected intersections by Crashes, Fatalities, or Crash Ratio, and see instant ranking results.

Note: When the application is loaded, only state intersections will be loaded, locally owned and/or maintained intersections will not appear in the ranking until a county or city-specific geofilter is applied. When displayed, locally owned intersections will not receive a state-wide ranking.

(The Intersection ranking table, with all intersections ranked by Crash Rate.
Users can sort and rank their intersections by any listed column of data.)

Contextual Data

With photos and Google Streetview, users can explore selected intersections, and even see how each intersection has changed over time, all without leaving the app.

(Examining an intersection through the built-in google Streetview explorer in the Intersection sidebar)

Limiting Values

Each ranking criteria can be modified to include a limited ranking value. When defined, only intersections with a value that meets or exceeds the defined minimum value will be displayed in the ranking table, and screening map. By default each value is set to 0, meaning that every intersection will be displayed. To modify the limiting value, click the Settings button located in the top right corner of the screen, next to the Save button, and enter the minimum value for the desired ranking criteria.

(The Settings flyout with the Limiting Values displayed. In this example, a minimum number of crashes is being defined as 3, meaning only intersections with 3 or more crashes will display.)

Intersection Flyout

Clicking on any intersection in your network displays the Intersection flyout, which contains current, and historical intersection rankings, a summary of crash statistics (including number of crashes and fatal (critical) crashes, crash rate), a summary of the roadway details for all intersecting routes (including AADT, function classes, and any other roadway datapoint present in your data), and a list of recommended countermeasures for that intersection.

(The Intersection Flyout of a selected intersection.)

Network Screening - Intersection Report

Generate a downloadable network screening - Intersection report which contains the intersection ranking, and a breakdown of each intersection, including the crash rate, fatality rate, and serious rate, as well as a stacked bar chart indicating the severity of crash and the route on which it occurred for each intersection.

(Sample Network Screening - Intersection Report displaying the Intersection rankings of roads that would benefit from left turn phasing changes in a given county, ranked by Crash Rate.)

Did this answer your question?