Intro

Informal Opening Discussion

Crash DB Systems Review

TraCS Systems and Crash Form development

Dave Malisch / Geri Polster

No report.

TOPS Database and WisTransPortal

Steven Parker / Andi Bill

Maintenance Updates and System Stability

• Completed Maintenance Windows:

  • June 23 – Monthly server maintenance window.

• Prioritized JIRA Issues and Enhancements

  • 2023 Finalization / 2022 RP Refinalization

    • Completed:

      • [CRASHDB-1623] 2023 Finalization - Crashes Having Late Fatality Withdrawals - Jira (atlassian.net)

      • https://wi-state-patrol.atlassian.net/browse/CRASHDB-1559

      • Published 2023 final and 2022 final RP on WisTransPortal and Community Maps (May 27).

    • Pending:

      • Generate Open Data Annual Extracts (July)

  • JIRA In Progress

    • https://wi-state-patrol.atlassian.net/browse/CRASHDB-989

      • User acceptance version on UAT server environment

    • https://wi-state-patrol.atlassian.net/browse/CRASHDB-1610

    • https://wi-state-patrol.atlassian.net/browse/CRASHDB-1637

• Purge and Archiving Processes

  • Purge and Archive processes continuing to run smoothly.

  • 1,118,373 total archived crashes of which 512,110 represent purged crashes (the archive adds approximately 13K crashes per month).  This includes 2,092,971 total image files.

• HWYCLASS Working Group

  • Working group meeting Tuesday, June 25

    • Comparison of 2022 LINK-LINK, Route-Milepoint, and RP

    • Analysis of missing / data quality issues

    • Focus on functional class for 2023 HSIP

• WisTransPortal / Community Maps

  • Final 2022 RP / 2023 data available since May 27

  • Community Maps “Virtual” Office Hours starting July 8 (second Monday)

  • WisTransPortal Advanced Download feature and upgrades

  • Working with BTO (AASHTOWare), City of Madison (Citian)

Crash Records Unit

Polly Ebbinger / Mike Satteson

Issue Resolution Summary

LE Question Summary

• Equipment – Several questions regarding how to indicate equipment on a crash report. The F2 Help does address this issue.

• Ambulance Info Requirement - On 6/25/24, Appleton PD notified us that the Office of Civil Liberties rendered an opinion that resulted in Gold Cross Ambulance service stating they will no longer provide medical records or ambulance run numbers without a subpoena.

FARS Update

Scott Starry our lead FARS analyst. who had been performing FARS work for 20 year, retired on 14 June. We expect to maintain continuity of operations for public facing reporting such as the Daily Fatality Reports and the Department fatal crash statistics web page.

NHTSA facing operations will be a challenge as we have lost at least half of our crash coding capacity. We will work closely with NHTSA to manage this shortfall in capabilities until we fill the vacancy and get a new coder trained and capable in this specialized and sophisticated work.

Thanks to Scot for his many years of work in this area.

DMV Systems and SR

Ken Matthews

There are no issues to report.

Reference Point Coding

Ben Rouleau

• Remaining 2023 Crashes (inclusive of deer crashes and auto-RP-coded crashes that have not been used): 14,000 (attached – 2023rpneeded_inclusive.xlsx)

  • Of these, about 5,500 are deer crashes

• Remaining 2023 Crashes (excluding deer crashes and auto-RP-coded crashes that have not been used): 1,718 (attached – 2023rpneeded.xlsx)

• I updated the Omit List for this run, and have a few comments:

  • Multiple RP coders are now excluding crashes with a note of “deer” or “deer crash” – that’s new, and I have created a separate code for it (“DEER” in OMITDESC, 5 in OMITCODE). If we’re not using my list of crashes that excluded deer and auto-RP-coded crashes, then we need to be coding deer crashes

  • Jack’s Omit List is empty, and Lukas’s has not been updated since April. That seems problematic – can you please look into that?

• RP Coding Report: 10,967 coded in 2023 for 5/23-6/26

  • Lukas: 4504

  • Jack: 1095

  • Jacob: 829

  • Tristan: 2452

  • Theresa: 1559

  • Justin: 528

• RP Coding Report notes:

  • Lukas continues to RP code at a really good clip

  • Has Jacob been coding in 2024? In his Omit List I see some 2024 crashes. We really have to wrap up 2023 before moving on to 2024 – this was a problem when closing out 2022 as well as 2021.

Crash Data Analysis and Reporting

Valerie Payne

Scheduled Topics and Briefing documents

2023 Open Crash Data

The 2023 crash year statistical analysis dataset has been available to department analysts for a month. Are there any concerns or objections to releasing the 2023 open data set when it becomes available in early July? The 2022 open data were released in late August of 2023.

Close

Informal Closing Discussion

Donald asked if it would be possible to designate construction workers on crash reports as this information is requested whenever something happens. The group discussed that there is a need to clearly define work zones which would help identify this situations. It might also be necessary to clearly define who is included in the construction worker category (surveyors, etc.). Randy indicated that LE will always know whether construction worker involved by the time the crash report is completed as that is part of the investigation. This will require further discussion but is important to keep in mind while making the changes for MMUCC 6.