Dataset Factory★ EST. 2026 · BEST AT 800×600 ★
★ WELCOME TO THE DATASET FACTORY ★ PUBLIC DATA → CHECKED BUILDS → HONEST BASELINES ★ NO POP-UPS ★ NO COOKIES ★ NO TRACKERS ★ HAND-MADE HTML ★ UNDER CONSTRUCTION SINCE THE NINETIES ★
Release notes · 2026-10-22 · announcement

A casualty-prediction task from Canada's rail occurrence record

Suitability and evaluation

Retained for retrospective model-development research with documented timing limitations. No answer recovery was found in the bounded audit; historical forecasting validity remains unverified.

Supported uses: Retrospective train/validation model-development experiments under the documented timing and selection limitations; Final evaluation only under a protocol that isolates holdout data from development and prevents later rows influencing earlier predictions

Not supported: Claims of verified real-time or operational forecasting validity; Treating development/validation scores as untouched final-test results

Historical feature availability
assumed
Training-label timing
unverified
Data vintage
current snapshot
Row selection
unverified
Required evaluation access
chronological

Cross-row audit: bounded no recovery. Bounded attack search, 15 active minutes per repository, frozen plan; not a security proof Holdout recovery was not tested by this audit.

The labeled eval split is development/validation data. Isolate final holdout data from development and prevent later rows influencing earlier predictions. Published data is not a secure hidden test service.

  • The bounded leakage audit found no recovery path (0 covered by any tested join); a bounded search is not a proof. One calendar week straddles train/eval (5 eval rows).
  • Historical feature/label availability at the declared prediction instant is assumed from current snapshots, not verified against release vintages.
  • The current scorer passes the complete feature frame to predict_proba; prediction-time isolation is instructed but not mechanically enforced.
  • Features come from a finalized occurrence register; excluding outcome taxonomy does not prove each retained contextual field was available at occurrence onset.

Reviewed 2026-10-24. Applies to this artifact; original data and tags are preserved.

This release packages 13,732 recorded railway occurrences between January 2016 and August 2026, with temporal train, validation and holdout splits. Occurrence onset is the intended prediction instant, but the source is a later register snapshot: this release does not establish that each recorded context field was known at onset.

The label is the occurrence's injury outcome: at least one casualty, 11.1% of train rows, 12.1% of eval, 14.1% of holdout. It is drawn from the injury totals and corroborated against the separate injuries table, which agreed on all 1,624 positives.

The recorded XGBoost baseline achieved 0.8126 validation AUC under the original runner protocol, compared with a tested activity-type rule at 0.707 and a persistence-style reference at 0.527. These comparisons describe the tested references and protocol; they do not establish historical feature availability or optimal-model headroom.

→ Open the dataset page for numbers, files and checksums

★ THANKS FOR VISITING · BOOKMARK THIS PAGE · TELL A FRIEND ABOUT THE DATASET FACTORY · SIGN THE GUESTBOOK BEFORE YOU LEAVE ★