Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 7 Next »

Intro

Informal Opening Discussion

Crash DB Systems Review

TraCS Systems and Crash Form development

Dave Malisch / Geri Polster

TOPS Database and WisTransPortal

Steven Parker / Andi Bill

Maintenance Updates and System Stability

  • Completed Maintenance Windows:

    • March 24 – Monthly server maintenance window.

    • April 21 – Monthly server maintenance window.

Prioritized JIRA Issues and Enhancements

  • In Progress

    • 2022 RP Re-Finalization

      • CRASHDB-1559 - Getting issue details... STATUS

      • Re-Finalization Completed on April 24

        • RP Records merged into final 2022 dataset

        • Final extracts provided to the CRU

      • Next Steps:

        • RP Crash File for GIS RP Crash Map

        • Update WisTransPortal Crash Data

        • Generate Public Extracts

    • 2023 Finalization

      • CRASHDB-1558 - Getting issue details... STATUS

      • Reviewing Process Documentation, Edit Checks

    • CRASHDB-989 - RP Coding - Implement Omit List Functionality in the Crash DB

Purge and Archiving Processes

  • Purge and Archive processes continuing to run smoothly.

  • 1,092,921 total archived crashes of which 498,269 represent purged crashes (the archive adds approximately 13K crashes per month).  This includes 2,045,165 total image files.

HWYCLASS Working Group

  • Continuing analysis of the LINK-LINK method for highway crash roadway attribute assignments in comparison to a route-milepoint method based on spatial analysis.

WisTransPortal / Community Maps

  • CRASHDB-1607 – WisTransPortal - Crash Reports Retrieval - Customer Number Search:

  • CRASHDB-1607 - Getting issue details... STATUS

Crash Records Unit

Polly Ebbinger / Mike Satteson

Issue Type

New since 3/22

Resolved since 3/22

Remaining

Document # Reuse*

45

36

16

Retransmissions

19

19

0

Potential Duplicate

10

11

17

LE Questions

4

4

0

*NOTE: The Document Reuse issues are trending up over last year.

LEA Questions since last workgroup meeting:

  • Hit & Run - LE requested clarification as to why LE can submit a H&R report with very little information but a DROC requires at least some identifying information about the H&R unit.

  • Amendments - LE wanted to know how to change information on a crash report. They were provided with basic instructions for creating the amended report.

  • Reporting Threshold - LE wanted to know how to change the Reporting Threshold (FMCSA) field. They were given the information that this field is calculated based on whether the crash report meets the threshold criteria so there is no way to manually change it.

  • Snowplow – LE asked how to get a report involving a snow plow and a parked car to validate. They were given the direction to submit as non-reportable.

Miscellaneous:

We received several requests from Citations & Withdrawals for purged crash reports. We worked with the TOPS Lab to add the Customer Number to the existing WisTransPortal Data Retrieval feature in an effort to provide more efficient self-service for these types of requests.

DMV Systems and SR

Ken Matthews

Reference Point Coding

Ben Rouleau / Asadur Rahman

Crash Data Analysis and Reporting

Valerie Payne

Scheduled Topics and Briefing documents

Close

Informal Closing Discussion

  • No labels