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 9 Next »

Intro

Informal Opening Discussion

Crash DB Systems Review

TraCS Systems and Crash Form development

David Malisch / Geraldine Polster

TOPS Database and WisTransPortal

Steven Parker / Andi BILL

Maintenance Updates and System Stability

  • February server maintenance window postponed until March

Prioritized JIRA Issues and Enhancements

  • 2022 Finalization

    • RP coding process for 2022 data is continuing and will be merged into the frozen data set once completed.

  • December / January JIRA Cases:

    • In Progress

      • CRASHDB-1349 - System Stability (Java 11 / Oracle 19c) Migration:

        • CRASHDB-1367 – Phase 1: Java Migration

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

        • Wednesday, February 7th production update was rolled back on Friday, February 9th after an issue was discovered with 24 crashes that were observed to have been created as duplicates.

      • CRASHDB-1536 - Resolve Pipeline Duplicate Crash Issue

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

        • JIRA case aggregator to investigate and clean up impacted crash records. Current theory is a configuration mismatch in the time zone settings between the new application server and the database that interfered with the integration process.  TOPS will schedule a new maintenance window once the issue has been thoroughly analyzed and resolved.

    • Under Development

      • CRASHDB-1465 - Resolve - CUSTNMBR Enhancements during Migration

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

          • Record history, modulation, assignment workflow

        • Prioritized JIRA improvements during Migration testing.

Purge and Archiving Processes

  • Purge and Archive processes both continuing to run smoothly.

  • 1,072,483 total archived crashes of which 472,826 represent purged crashes (the archive adds approximately 13K crashes per month).  This includes 2,005,543 total image files.

HWYCLASS Working Group

  • Next workgroup meeting: 2/27.  Will present roadway ownership query results.  These elements provide an opportunity to compare derived values to values from the police report.

  • General concurrence on merit to continue line of investigation.

  • Follow-up on TLT information in deer crash short form.

WisTransPortal / Community Maps

  • Community Maps:

    • User Preferences enhancement moved into production.

    • Desing for new training video page in progress

    • Tribal Area filter based on US Census boundaries in progress, along with a few new flags.

    • Crash flags technical documentation in progress.

WisTransPortal:

  • Data download enhancement in progress.

Crash Records Unit

Polly Ebbinger / Mike Satteson

Duplicate Crash Reports

75 Potential Duplicate Crashes

14 resolved in last 30 days

61 remaining to resolve

Transmission Failures

(since the 1/26/24)

52 total unique documents failures

40 reuse failures

34 retransmissions

3 reuse, agency fixed

3 reuse, solution provided – 2 outstanding

1 CJIS flag missing or empty

5 Police Report Image is missing or empty

1 Document Number and Crash document Number must be different

1 invalid EMS Agency ID

1 Hwy direction is missing

1 LastName is invalid

1 Airbag invalid

1 PhotosBy invalid

Issues Submitted

BTRSD-6984 Issue - Convert to Amended

BTRSD-6985 Issue - Secondary Crash / Primary Crash Agency

LE Questions

8 LE questions – all related to validation issues of crash reports

1 Bomgar session related to the CJIS flag error

FARS Work

For 2024, there are currently 41 fatalities (from 38 crashes) in our case management system

julia> combine(groupby(fatality, :jira_root), nrow=>:fatalities) |>
       x->freqtable(x, :fatalities)
3-element Named Vector{Int64}
fatalities  │
────────────┼───
1           │ 36
2           │  1
3           │  1

Of these 37 are in the crash database, and 4 are not:

julia> filter(x->ismissing(x[:INJSVR]), fatality)[!, [:jira_root, :case_status, :person_status]]

4×3 DataFrame
 Row │ jira_root      case_status         person_status
     │ String15?      String31?           String31?
─────┼──────────────────────────────────────────────────
   1 │ FARSCASE-4158  FARS Case           Fatality
   2 │ FARSCASE-4150  FARS Case           Fatality
   3 │ FARSCASE-4135  FARS Case           Fatality
   4 │ FARSCASE-4017  Not Yet Considered  Federal Only

  • FARSCASE-4158, This crash occurred in Monroe County on Monday February 19, 2024 at about 9:22 AM. There was 1 fatality associated with this crash, a 38 year-old male driver. (19 February Daily Fatality Report)

  • FARSCASE-4150, This crash occurred in Wood County on Friday February 16, 2024 at about 7:35 PM. There was 1 fatality associated with this crash, a 41 year-old male driver. (19 February Daily Fatality Report)

  • FARSCASE-4135, This crash occurred in Milwaukee County on Friday February 9, 2024 at about 1:41 PM. There was 1 fatality associated with this crash, a 93 year-old male pedestrian. (9 February Daily Fatality Report)

  • FARSCASE-4017, This crash occurred in Ashland County on Tuesday January 2, 2024. There was 1 fatality associated with this crash, a 43 year-old male driver (not reportable to WisDOT). This is a DNR ATV crash--Single operator/victim lost control on a curve and was ejected. We will not be able to evaluate it until we obtain case materials from the DNR,

Of the fatalities in the database

julia> filter(x->!ismissing(x[:INJSVR]), fatality) |>
       x->freqtable(x, :case_status, :person_status)
4×3 Named Matrix{Int64}
 case_status ╲ person_status │   Fatality       NMVTF  State Only
─────────────────────────────┼───────────────────────────────────
Dismissed from Consideration │          0           1           0
FARS Case                    │         32           0           1
Not Yet Considered           │          1           0           0
Under FARS Review            │          2           0           0

Of these the Not FARS Cases are

julia> filter(x->!ismissing(x[:INJSVR])&&x[:case_status]!="FARS Case", fatality)[!, [:jira_root, :case_number, :case_status, :person_status]]
4×4 DataFrame
 Row │ jira_root      case_number  case_status                   person_status
     │ String15?      String15?    String31?                     String31?
─────┼─────────────────────────────────────────────────────────────────────────
   1 │ FARSCASE-4167  240205335    Not Yet Considered            Fatality
   2 │ FARSCASE-4108  240200571    Dismissed from Consideration  NMVTF
   3 │ FARSCASE-4083  240110793    Under FARS Review             Fatality
   4 │ FARSCASE-4021  240105450    Under FARS Review             Fatality

  • FARSCASE-4167, This crash occurred in Grant County on Sunday February 11, 2024 at about 6:56 PM. There was 1 fatality associated with this crash, a 22 year-old male pedestrian. Crash report arrived late last night.

  • FARSCASE-4108, This crash occurred in Green County on Friday February 2, 2024 at about 2:54 PM. There was 1 fatality associated with this crash, a 28 year-old female pedestrian (not considered a traffic fatality). This was a parking lot aisle crash and so not a traffic crash.

  • FARSCASE-4083, This crash occurred in Dane County on Friday January 26, 2024 at about 10:22 PM. There was 1 fatality associated with this crash, a 23 year-old female pedestrian.

DMV Systems and SR

Ken Matthews

Reference Point Coding

Asadur Rahman

Crash Data Analysis and Reporting

Valerie Payne / Brian Porter

Scheduled Topics and Briefing documents

Close

Informal Closing Discussion

  • No labels