When viewing data in the Crash Query application, filters aid in narrowing down the information users have to sort through. The information below shows how each of the filters is displayed for the state of Oklahoma and which are recommended for use, not recommended for use, and which should be used with caution.

The filters in this category center around specific highways in Oklahoma and are utilized to narrow down the data per the user’s preference. Some filters may have the same results as others. For more information, please see the filters laid out in more detail below.

Using the Highway filter narrows down the data based on which highway in Oklahoma users would like to view. This filter is recommended because its results are identical to that of the ODOT Route filter.

Using the ODOT Route filter produces results identical to that of the Highway filter.

Using the Highway Related (non-OTA) filter will function similarly to the Highway Class filter, though it does not include crashes that occurred on OTA Highway, City Street, or County Road. Crashes on Interstate Turnpikes (such as I-44/Turner Turnpike) will not be included if Highway Related (non-OTA) is set to “Yes.”

The Highway Class filter does not include crashes on Interstate Turnpikes (such as I-44 Turner Turnpike).

The Route ID and milepoint may be more precise than a polygon, particularly in scenarios where a polygon is difficult to place. To identify a roadway's Route ID, please see the Master Roadway & Bridge Data Viewer at the ODOT ArcGIS Spotlight (https://spotlight-okdot.hub.arcgis.com/). The Route ID (Location) filter interacts with the Line Tool in Crash Query.

The filters in this category center around Turnpike Queries in Oklahoma and are used to narrow down the data per the user’s preference. For more information, please see the filters below.

Both the Turnpike Related filter and Highway Class = OTA Highway filter have the same results.

Both the Turnpike Related filter and the Highway Class = OTA Highway filter have the same results.

This filter is not recommended for use when filtering for turnpike-related crashes. Both the Highway = T000 filter and the ODOT Route = Turnpike 0 filter do not return turnpike crashes statewide. Highway = T000 will appear to return crashes that occurred on the Kilpatrick Turnpike but does not return crashes exclusively on the Kilpatrick Turnpike.

ODOT Route is also not recommended for use in filtering for turnpike-related crashes.

Street Name (Segments) contains filter options for specific turnpikes, but a given route may be associated with multiple names. For instance, a highway may also include named memorial bridges that have crashes attributed to the bridge as a Street Name. This approach is generally not recommended.

The filters in this category center around Intersections in Oklahoma and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

If Intersection Type = No, it yields the same results as Intersection Related = No. If the Intersection Type = Unknown, it yields the same results as the Intersection Related = Unknown.

If Intersection Related = No, it yields the same results as Intersection Type = Not an Intersection. If the Intersection Related filter = Yes, it includes all Intersection Types except for Not An Intersection and Unknown. If the filter is Intersection Related = Unknown, it will yield the same result as the Intersection Type filter = Unknown.

Every Intersection is given a numerical ID. One way to find the ID for a particular intersection is to visit Crash Query. When in the application, navigate on the map to the intersection needed. Select the "Filter to view" button on the right side of the map view, or draw a polygon around the intersections. Show the Intersection ID in the Metrics tab by clicking Manage Metrics in the upper right corner of the righthand panel.

The filters in this category center around Streets in Oklahoma and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

The Route ID and milepoint may be more precise than drawing a polygon, particularly in scenarios where a polygon is difficult to place. Using the Route ID filter will help avoid issues that may be present when filtering using the Street Name (Segments) flter. This filter also interacts with the Line Tool. To identify a roadway's Route ID, please see the Master Roadway & Bridge Data Viewer at the ODOT ArcGIS Spotlight (https://spotlight-okdot.hub.arcgis.com/).

Street Name (Segments) contains filter options for specific streets, but names may be inconsistent or listed under multiple versions of some names. Using Street Name (Segments) to filter for crashes is generally not recommended, but may be possible for small-scale query areas and the data may provide context for local locations.

Street 1 and Street 2 appear to show cross streets associated with a crash or the nearest cross street. The names in Street 1 and Street 2 do not necessarily match Street Name (Segments). Streets may be better identified through Route ID (Collision), or using Route ID with a polygon may be more intuitive.

The names in Street 1 and Street 2 do not necessarily match Street Name (Segments).

The filters in this category center around Cities in Oklahoma and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

City (Geo) is available in the filter bar, but not in the Raw Table. Crashes with missing latitude/longitude coordinates will not be included when using this filter.

City (Mapped) is available in the filter bar and the Raw Table. City is identical to City (Geo), but does not apply a geo-polygon filter on the map window. Crashes with missing latitude/longitude coordinates will not be included when using this filter.

City (From Crash Report) is an incomplete dataset containing blanks and missing data. When working with this filter it is important to remember that city names may be repeated under various spellings or abbreviations.

The filters in this category center around Counties in Oklahoma and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

Crashes with missing latitude/longitude coordinates will not be included when using this filter.

County Name (Mapped) is available on the filter bar and in the Raw Table. Crashes with missing latitude/longitude coordinates will not be included when using this filter. It is identical to County (Geo), but does not place a polygon boundary on the Crash Query map. This may be useful for editing a polygon filter when querying within a county (or counties), as polygon filters cannot be edited when a County (Geo) filter is active.

County (Mapped) and County (Crash Report) are available in the filter bar and in the Raw Table. If a crash has a value under County (Mapped), this field contains County (Mapped). If a crash has no County (Mapped) value, but does have a County (from Crash Report) value, the data from the crash report is filled into this field. As a result, this field is more complete than County (Mapped), but it may contain inconsistent entries such as different spellings or abbreviations. This field may be useful, especially if dealing with multiple crashes without location (and County (Mapped)) data, but the user should be aware of limitations.

The filters in this category center around the Severity of collisions in Oklahoma and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

Each filter in this category is based on the highest level of Injury Severity that occurred per crash event. For example, a crash resulting in one individual with a level A injury and one with a level C injury will have "Crash Severity = A". The filters KA Collisions and KAB Collision return records with the listed crash severities (like a "shortcut" filter). All filters behave as expected.

Will display all K (fatal) and A (suspected serious injury) crashes.

Will display all K (fatal) and A (suspected serious injury), and B (suspected minor injury) crashes.

The Injury Severity filter returns all crashes where at least one person sustained the filtered level of injury severity; other individuals involved may have sustained the same, lower, or higher levels of injury severity. This may result in Crash Severities differing from the Injury Severity filter. For example, filtering "Injury Severity = (O) No Injury" may produce results that include a Crash Severity of Suspected Serious Injury, where at least one individual involved in the crash sustained No Injury.

The filters in this category center around Unsafe/Unlawful traffic conditions and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

The Unsafe/Unlawful (Consolidated) filter groups similar Unsafe/Unlawful tags. For example, Followed too Closely (for): Traffic Condition and Followed too Closely (for): Human Element will both be included under the Consolidated group Followed too Closely.

The Unsafe/Unlawful Related filter will categorize a crash as "Unsafe/Unlawful Related = True" if at least one unit has an Unsafe/Unlawful action, other than "Not Known or No Improper Act.” Crashes marked "Unsafe/Unlawful Related = False" mean that every unit(s) involved had an Unsafe/Unlawful action of "Not Known or No Improper Act."

Unsafe/Unlawful filter will provide specific filtering and can be a more reliable option for documentation and replication compared to Unsafe/Unlawful (Consolidated).

The filters in this category center around Harmful Events and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

This filter compiles data from fields Event 1, Event 2, Event 3, and Event 4 into one array field. For example, "Any Event = FO-Fence" will return crashes where "FO-Fence" was listed under any (or multiple) fields within Event 1/Event 2/Event 3/Event 4.

The First Harmful Event filter is not always identical to Event 1. This is a collision-level dataset derived from C Fst Harm Event Cde.

The First Harmful Event (V1) filter is not always identical to Event 1 or First Harmful Event. This is a unit dataset derived from Event Cde 1.

The Most Harmful Event filter is not always the same as the First Harmful Event or Event 1.

These fields may contain more than one event. For example, "Event 2" may contain the values: "FO-Curb, Motor Vehicle in Transport.” Filtering for only one event may cause crashes to be erroneously excluded from the query, as an event may fall under Events 1-4 depending on the crash.

The filters in this category center around Driver Age and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

In many situations, the Driver Age filter may be best used with specific age ranges, like “Driver Age between 15 to 21” in place of “Driver Age < 21.” When using this filter, be aware that many crash records have a Driver Age of 0.

This field has been created based on Driver Age. Any blank ages, ages less than 5, and greater than 104 are classified as Unknown. Because this is a text field to include the Unknown result, it is not possible to filter by range (such as Driver Age > 25).

Setting specific ranges with the Driver Age filter is suggested when needing a more detailed age range.

The Younger Driver Related, through ODOT Crash Summary and as a standalone filter, includes all crashes with at least one driver involved (not necessarily all drivers involved) and has a Driver Age between 5 and 21.

The Older Driver Related, through ODOT Crash Summary and as a standalone filter, includes collisions with at least one driver involved (not necessarily all drivers involved) and has a Driver Age between 65 and 104.

The filters in this category center around the involvement of a DUI/DWI and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

The Alcohol Related filter is a Person level column and contains multiple Yes/No designations per crash. For a crash, Alcohol Related may indicate Yes while tags like Unsafe/Unlawful and DUI/DWI Related do not show DUI of Alcohol for the same crash. Alcohol Related is consistent with Driver Condition (Drinking - Ability Impaired, Odor of Alcoholic Beverage). Please check the Driver Condition column for additional information.

The Alcohol Related Driver filter is not available in the filter bar, but in the Raw Table and Chart Builder. If the Alcohol Related Driver = Yes, then it correlates to the Driver Condition = Drinking - Ability Impaired, and the Driver Condition = Odor of Alcoholic Beverage.

The Drug Related data at the crash level contains multiple Yes/No designations. Drug Related = Yes is based on Unsafe/Unlawful = Driving Under Influence of Drugs. Drug Related = Yes does not match the Driver Condition for every record.

The DUI/DWI Related data at the crash level contains multiple Yes/No designations. DUI/DWI Related is based on Unsafe/Unlawful involving alcohol. Crashes where "DUI/DWI Related = No" may also have "Alcohol Related = Yes" and Driver Condition = [alcohol-related result].

The Unsafe/Unlawful filter will provide specific filtering options and may be more consistent for documentation and replication. Please be advised to check other filters for greater context.

This filter may provide greater context when searching for DUI/DWI-involved crashes.

The filters in this category center around Seatbelt Usage and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

These filters may be best viewed in the Raw Table tab, in the "People" data level. A suggestion to easily determine individuals involved in the same crash is to add the Document ID column to the view. The Restraint Use filter describes the type of restraint but is not a complete dataset.

Results for "Yes" return crashes where at least one individual had Restraint Use = None Used (other individuals in the crash may have used a restraint). "No" returns crashes where no person had None Used or Unknown as Restraint Use. "Unknown" returns crashes where any person had Restraint Use = Unknown, but no person had Restraint Use = None Used. As Restraint Use is not a complete dataset, Unrestrained Occupant Present is also not a complete dataset.

The crash-level data is available in the Raw Table and includes the number of unrestrained occupants involved in a given crash.

The filters in this category center around Pedestrians and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

This filter will return the total number of pedestrians involved in each crash.

This filter includes data for crashes that have Pedestrian Related = Yes, but may also include crashes that have Bicycle Related = Yes. Some crashes have a non-motorist action listed but are not labeled as Pedestrian Related or Bicycle Related.

This filter includes data for bicyclists as well as pedestrians. Using this filter with the Unit Type = Pedestrian filter may help ensure the data only includes pedestrians.

The Unit Type = Pedestrian filter feeds into the Pedestrian Related = Yes. Using this filter with the Non-motorist Action filter may help ensure the data only includes pedestrians if that is the query target.

The Pedestrian Related = Yes filter is based on the Unit Type = Pedestrian and the Unit Type = Pedestrian Conveyance.

The filters in this category center around Bicyclists and are utilized to narrow down the data per the user’s preference. For more information, please see the filters laid out in more detail below.

This filter includes data for crashes that have Bicycle Related = Yes, but may also include crashes where Pedestrian Related = Yes.

This filter includes data for pedestrians as well as bicyclists. Using this filter with the Bicycle Related = Yes or Unit Type = Bicyclist filter may help ensure the data only includes bicyclists.

The Unit Type = Bicyclist filter feeds into the Bicycle Related = Yes.

The Bicycle Related = Yes is based on the Unit Type = Bicyclist.