Methodology

This page explains how the Victorian Road Harm Intelligence site turns public crash, signal-site and freight-corridor data into council reports, maps, rankings, graph packs and downloadable public-interest analysis outputs.

Short version: this is a screening and prioritisation system. It helps identify patterns and candidate locations for closer review. It is not an engineering safety audit, an official government priority list, or a legal finding about fault.

Crash harm Council summaries Vulnerable road users Heavy vehicles SCATS signal-site exposure TIRTL freight-corridor exposure Maps and rankings

Contents

Official source data

Official crash data source

The crash records used in this project come from the Victorian Government's public Victoria Road Crash Data dataset.

The files published on this site are derived public-interest analysis outputs, rankings, maps and summaries built from that crash data and, where specified, SCATS signal-site and TIRTL freight-corridor exposure layers.

Readers who want the original official crash dataset should use the Victorian Government source link above.

LayerPurpose in this siteImportant caveat
Victoria Road Crash Data Provides the underlying crash records, severity fields, road-user information, location fields and crash attributes used to calculate harm, council totals, maps and rankings. This site does not replace the official dataset. It is a derived analysis and presentation layer.
SCATS signal-site data Used as a signalised-intersection and signal-site exposure/proximity layer where crash locations can be matched to nearby signal sites. A SCATS match is not a causation claim. It means the crash record is close enough to a signal-site layer to support closer review.
TIRTL freight/traffic sensor data Used as a freight-corridor and heavy-vehicle exposure/proximity layer where available. TIRTL coverage is not uniform. Low TIRTL-matched harm can mean low coverage as well as low measured corridor conflict.
Council boundaries and local report metadata Used to group records and outputs into council-level pages, maps, charts and ranking tables. Council totals are not the same as council responsibility. Many roads and intersections are managed by state agencies.

What this site does and does not do

What it does

It turns large public datasets into readable council-by-council intelligence: crash harm summaries, maps, top locations, statewide comparisons, vulnerable-road-user analysis, freight-conflict indicators and signalised-intersection screening.

What it does not do

It does not assign legal fault, prove causation, replace site inspections, replace crash-diagram analysis, or make official funding recommendations.

Best use

Use it to identify candidate locations, patterns and questions for further review by councils, DTP, road-safety engineers, councillors, journalists and community advocates.

Core harm metrics

The site uses simple, transparent metrics so readers can understand what each table and graph is showing.

MetricMeaningInterpretation
crash_recordsNumber of crash records in the selected grouping.A volume measure. It does not distinguish minor from severe outcomes.
fatalitiesNumber of recorded deaths.The highest-severity component of harm.
serious_injuriesNumber of recorded serious injuries.Major road-trauma burden.
other_injuriesRecorded injury outcomes below serious injury.Included in total harm, but weighted less heavily than fatal and serious injuries.
fatal_serious_injuriesFatalities plus serious injuries.Useful for focusing on the outcomes that matter most for road-safety policy.
harm_scoreWeighted harm score.Gives more weight to deaths and serious injuries than lower-severity injuries.
vulnerable_road_user_crashesCrash records involving pedestrians, bicycle riders or motorcyclists.Highlights road users with less physical protection.
heavy_vehicle_crashesCrash records involving at least one heavy vehicle.Shows where heavy vehicles appear in crash records. It does not mean the heavy vehicle was at fault.

Weighted harm formula

harm_score = fatalities × 100 + serious_injuries × 10 + other_injuries × 1
Why use a weighted harm score? Crash counts alone treat a minor injury record and a fatal crash record as equal. The weighted harm score keeps crash volume visible while giving greater emphasis to the most serious outcomes.

Council-level processing

The site aggregates crash records and derived indicators into council-level outputs so each council can be viewed locally and compared statewide.

1. Crash records are loaded and cleaned. The project reads the official crash data tables and keeps the fields required for location, severity, road-user, vehicle, crash-type and council-level analysis.
2. Records are grouped geographically. Crash records are summarised into council outputs using location/council fields and supporting spatial/report metadata where available.
3. Metrics are calculated. Crash counts, fatalities, serious injuries, other injuries, weighted harm, VRU counts and heavy-vehicle counts are calculated for councils and selected locations.
4. Outputs are published. The results are presented as council pages, statewide graphs, maps, CSV/JSON downloads and public explanation pages.
Road ownership caveat: a crash located inside a council boundary does not automatically mean the council owns or controls that road. Many major roads, arterials, freeways and signalised intersections require state-agency involvement.

Combined council priority score

The combined council priority score is a triage ranking. It is designed to help readers identify councils with broad road-harm pressure across several dimensions.

ComponentWhy it is included
Total weighted harmCaptures overall burden, weighted toward serious outcomes.
Fatal and serious injuriesFocuses on deaths and serious trauma.
Vulnerable road-user crashesHighlights pedestrian, cyclist and motorcyclist exposure to harm.
Heavy-vehicle crashesHighlights councils where heavy vehicles appear frequently in crash records.
SCATS-matched harmIdentifies signalised-intersection and signal-site-adjacent harm where SCATS matching is available.
TIRTL freight-conflict harmIdentifies freight-corridor harm where TIRTL matching is available.
Important: the priority score is not a formal risk model, not population-adjusted, not road-length-adjusted, and not a government funding formula. It is a public-interest screening score designed to put multiple signals in one place.

SCATS signal-site proximity and exposure layer

SCATS is Victoria’s traffic signal system. In this project, SCATS is used to help identify crash harm near signalised intersections and signal-adjacent locations.

Nearest-site matching: crash records are matched to the nearest SCATS signal site within the selected radius, usually 250 metres.
Signal-site summaries: matched crash records are aggregated by SCATS site to calculate harm, fatal/serious injuries, crash counts, VRU crashes and heavy-vehicle crashes.
Exposure adjustment: where SCATS movement totals are available, harm can be compared against observed signal-site movement volume to produce measures such as harm per million movements.
Causation caveat: a nearby SCATS site did not necessarily cause a crash. The match indicates proximity to a signalised-intersection monitoring layer and should be treated as a prompt for closer review.

Common SCATS-derived measures

MeasureMeaning
matched_crash_recordsCrash records matched to a nearby SCATS site.
harm_per_million_movementsWeighted harm divided by observed movement volume, scaled to one million movements.
fatal_serious_per_million_movementsFatal and serious injuries divided by observed movement volume, scaled to one million movements.
exposure_confidenceIndicator of how usable the available exposure denominator appears for interpretation.

TIRTL freight-corridor proximity layer

TIRTL is used as a freight/traffic sensor layer. In this project it helps identify where heavy-vehicle crash harm overlaps with monitored freight corridors.

Corridor-style matching: heavy-vehicle crash records are matched to the nearest TIRTL monitoring site within the selected radius, usually 1000 metres.
Freight-conflict summaries: matched records are aggregated to identify councils and locations where freight corridors, heavy vehicles and road harm overlap.
Coverage caveat: TIRTL sites are sparser and more corridor-based than SCATS sites. Absence of a match may reflect sensor coverage rather than absence of freight risk.
Attribution caveat: a TIRTL match does not mean the sensor, corridor or heavy vehicle caused a crash. It is an exposure/proximity indicator.

Dangerous signalised-intersection screening layer

The dangerous-intersections layer uses SCATS-matched crash harm to identify signalised-intersection candidates for further review.

Ranking dimensionWhy it matters
Total weighted harmShows the overall harm burden near the site.
Fatal and serious injuriesPrioritises serious trauma outcomes.
Matched crash recordsShows total crash volume near the site.
Vulnerable road-user crashesHighlights pedestrian, cyclist and motorcyclist conflicts.
Heavy-vehicle crashesHighlights locations where heavy vehicles appear in crash records.
Harm per million movementsHelps separate pure traffic volume from unusually high harm per movement where exposure data is usable.
How to read the ranking: these are the strongest priority signals in a public screening layer. They should be used to ask better questions, not to claim that a site has already failed an engineering audit.

Vulnerable Road User Atlas

The Vulnerable Road User Atlas focuses on people outside cars or with less physical protection.

Included road users

Pedestrians, bicycle riders and motorcycle riders are grouped as vulnerable road users for this public screening analysis.

Main outputs

Statewide VRU locations, council summaries, top VRU locations, pedestrian/cyclist/motorcyclist patterns and selected age-group indicators where available.

Best use

Use this layer for pedestrian safety, cycling safety, motorcycle safety, local street design, speed management, crossings, tram corridors and bike corridors.

Freight Conflict Index

The Freight Conflict Index is designed to identify places where heavy-vehicle crash harm, vulnerable-road-user overlap and freight-corridor exposure coincide.

Heavy-vehicle crash harm: identifies councils and locations where heavy vehicles appear in crash records.
VRU overlap: highlights where freight movement and vulnerable road users may be sharing constrained road environments.
TIRTL corridor layer: adds sensor-corridor context where TIRTL matching is available.
Fault caveat: heavy-vehicle involvement in a crash record does not mean the heavy vehicle was at fault.

Emerging road-harm hotspots

The emerging-hotspots layer looks for places, councils and crash patterns where recent harm appears worse compared with the long-run baseline.

Output typePurpose
Council worseningIdentifies councils with worsening recent road-harm indicators.
Location worseningIdentifies specific locations where recent crash harm appears to be rising.
VRU worseningHighlights vulnerable-road-user locations or patterns that appear to be worsening.
Heavy-vehicle worseningHighlights heavy-vehicle crash-harm locations or patterns that appear to be worsening.
Mechanism/speed-zone worseningHelps identify whether worsening is concentrated in particular crash types, speed environments or road contexts.
Interpretation caveat: emerging-hotspot analysis is sensitive to small counts, reporting delays and short-term variation. It is best used as an early-warning layer, not proof of a permanent trend.

Council safety diagnosis layer

The safety-diagnosis layer helps explain what kind of road-harm problem a council appears to have, rather than only ranking how much harm it has.

Crash mechanisms

Uses available crash-type and DCA-style fields to highlight recurring crash mechanisms.

Severity profile

Compares fatal, serious and other injury patterns.

Road-user profile

Highlights pedestrian, cyclist, motorcyclist, heavy-vehicle and other road-user patterns where available.

Road environment

Uses available speed-zone, geometry, lighting and road-condition fields to support local diagnosis.

Maps, candidate locations and Street View

Maps are used to help readers move from abstract rankings to real places.

Council maps: show local crash patterns and candidate locations for each council report.
Statewide maps: show council-level road harm and selected statewide candidate locations.
Street View links: help readers inspect the road environment, but they are not a substitute for site visits or engineering review.
Location caveat: crash coordinates and matching locations can have uncertainty. Mapped points should be treated as screening locations, not exact legal determinations.

Downloads and reproducibility

The public data downloads are provided so readers can inspect the generated outputs behind the site.

Download catalog

The data notes page provides featured CSV downloads, JSON/catalog files and topic ZIP packages.

Derived outputs

The downloadable files are generated analysis products, not the raw official crash-data tables.

Raw data source

Readers seeking the original official crash dataset should use the Victorian Government source link on the data notes page and on this methodology page.

Limitations

Responsible use

Use the site to ask better questions. The strongest use is to identify where further investigation may be justified.
Compare multiple indicators. A site with high crash count, high harm, high VRU involvement and high exposure-adjusted harm is more compelling than a site that only ranks high on one measure.
Check local context. Formal review should consider crash diagrams, signal phasing, road geometry, turning movements, speed environment, traffic volumes, pedestrian activity, cycling routes, truck routes, public transport and land use.
Do not overclaim. Do not use these rankings alone to claim fault, negligence, legal liability or final engineering priority.

Glossary

TermMeaning on this site
FSIFatal and serious injuries combined.
VRUVulnerable road users: pedestrians, bicycle riders and motorcycle riders.
Heavy vehicleA crash record involving at least one heavy vehicle field/classification as represented in the underlying data outputs.
SCATSTraffic signal system layer used here for signal-site and signalised-intersection proximity/exposure analysis.
TIRTLTraffic/freight sensor layer used here for corridor-style freight and heavy-vehicle exposure analysis.
Harm scoreWeighted score: fatality ×100, serious injury ×10, other injury ×1.
Priority scoreA combined public-interest triage score based on multiple harm and exposure indicators.
Candidate locationA place that appears important enough for further review, not a final finding.

Version note

This expanded methodology page documents the public-facing v0.2 Road Harm Intelligence workflow, including council reports, statewide graphs, dangerous-intersection briefings, SCATS exposure, TIRTL freight conflict, vulnerable-road-user analysis, emerging hotspots, safety diagnosis and downloadable data outputs.

Generated by TrafficAnalytics Road Harm Intelligence. Last methodology page expansion prepared: 2026-06-29 06:15.