Over-representation reports enable users to compare a specific geographic region (such as a city, county, or district) with the larger geographic region (county, district, or state) in which it resides.

Overrepresentation reports use geo-located crashes based on the reported location of the crash (as it appears in the crash report). Occasionally, a discrepancy may arise between the reported crash location and the geo-located crash location. If this is the case, crashes reported as being inside the selected boundary but geo-located outside the selected boundary will not appear in the report. This may lead to discrepancies in crash statistic reporting.

Over-representation reports highlight key differences in metrics between geographic regions, enabling users to quickly identify potential crash types or characteristics that may be overrepresented in the selected region.

The over-representation report displays all the metrics contained within the query, broken down into several columns. The first column, labeled "Filtered," displays the geographic region identified through the Geo Filter in the query (either a city, county, or district/region, if configured for your organization). The next column(s) will represent the same metrics for the county, district, and/or state in which the filtered geographic region resides.

In the example below, a city has been selected using the City (Geo) filter. The exact name of geo filters differs between organizations; however, they are typically labeled with “(Geo)” somewhere in the filter name.

The Filtered column contains the metrics for the filtered city. The next two columns, county and state, represent the county of the selected city and the statewide totals for each metric. The metrics are depicted as a percentage of total crashes, allowing for a meaningful comparison across different-sized regions.

In the example below, the selected city has 1,385 intersection-related crashes, accounting for 46.90% of all crashes in the city. For the county and the state, Intersection-related crashes account for 47.67% and 42.06% of total crashes, respectively.

Over-representation reports highlight key differences in metrics between geographic regions. Any change of +/- 5% or 2x a given metric between geographic regions will be highlighted by the over-representation report. In the example below, Straight Horizontal Alignment crashes account for 68.47% of total crashes, compared to the county, which only experiences 42.64% of the same crash type.

Because the number of Straight crashes is greater than 5% larger than the next lowest value, it has been highlighted. Additionally, the county has a significantly higher percentage of Unknown Horizontal Alignment crashes than the selected city and the state, which has also been highlighted.

To generate an Over-representation report, follow the steps outlined below:
​

1. Create the desired query, including customizing the Metrics sidebar to display the key crash metrics you would like to include in your report. Verify that you have a City, County, or District Geo filter on your desired query.
​

2. Click the Download icon, located in the top right corner of your query.
​

3. From the Report popup, select Over-representation (Note: if you are not able to select the Over-representation report, it is most likely because you do not have a valid Geo filter applied to your query).

4. Fill out the title and requestor field, and click Create Report.
​

5. The report preview will be displayed. Review the report and make any necessary changes to the initial query. To download the report, click the Save & Download button in the top right corner of the report.
​