A follow-up companion to the Western Melbourne Freight Burden Evidence Brief

Freight Exposure &
Infrastructure Accountability

Where the freight burden was measured, what the overnight evidence establishes, and which pavement, maintenance, lighting and investment records government must still provide.

Read the 60-second brief Questions to ask government Open the main evidence brief

The follow-up questions

Where?Does a corridor metric describe one monitoring cross-section, several mapped points, or an entire road stretch?

How persistent?Is the overnight burden recurring, or driven by only a few unusually busy nights?

What is missing?Do pavement condition, resurfacing, lighting and maintenance expenditure match the measured freight exposure?

60 SEC

Political briefing

The case in one minute

Briefing corridor

Read this aloud or paste it into a briefing note

60-second brief

What the evidence proves

What it does not prove

What government must now produce

ASK

Questions to put directly to government

The accountability checklist

Download question list

These questions separate what the TIRTL evidence proves from the road-condition, maintenance and investment records that only government can provide.

Ask for the answer, the supporting document, the responsible agency, the reporting date and the road limits covered. A verbal assurance is not a substitute for the underlying asset or expenditure record.

Monitoring scope and plain-language burden

What exactly does the metric cover?

Selected corridor

Direct answer

Can this be described as a complete road stretch?

Safest public wording

Mapped evidence footprint

Monitoring positions

Loading map…

Mapped TIRTL source-site IDs—Distinct mapped source-site identifiers represented

Qualifying directional headings—Headings supporting the comparable night metric

Clustered monitoring positions—Source-site coordinates within 150 metres grouped as one cross-section

Maximum sensor span—Distance between the furthest contributing source-site coordinates

Contributing records

Exactly which monitoring headings support the result?

Download scope extract

Source-site ID	Base TIRTL ID	Heading	Site-heading ID	Site-heading key	Site label	Direction	Locality	Coordinates

MAP

Interactive political briefing map

Click the exact TIRTL locations behind the freight argument

Select a corridor and click a numbered TIRTL source-site marker. Each popup identifies the exact source-site ID and directional headings, explains the measured burden in plain language and provides a question that can be put directly to government.

Corridor Colour markers by Show only source sites with a heading used in the corridor metric

Selected evidence area——

Distinct source-site IDs—Clickable mapped source-site IDs

Exact headings used—Directional records behind the metric

Average monitored direction—Typical overnight frequency per used directional heading

Interactive TIRTL evidence mapClick a numbered source-site marker for exact IDs and evidence.

Loading Google Maps and exact TIRTL locations…

Markers identify available TIRTL source-site coordinates. They do not represent continuous measurement along an entire road. Counts are classified sensor passings, not unique trucks or complete journeys.

Download map data JSON Download mapped heading CSV Download map build information

Exact TIRTL identity and location register

Which sensors and headings are we discussing?

Every available identifier and source field for the physical TIRTL units associated with the selected corridor, with contributing valid-night headings clearly identified.

Important distinction:A source-site ID can contain more heading records than the number used in the valid-night metric. Green labels identify the exact contributing headings.

Distinct TIRTL source-site IDs—Distinct source-site identifiers

Heading records shown—All available headings at those source-site IDs

Used in night metric—Exact contributing headings

Source fields exposed—Non-empty values with provenance

263Source site ID

Source-unit identifier carried by imported TIRTL records.

TIRTL_263Base TIRTL site ID

Normalised ID for the source-site ID.

263_ESite-heading key

Composite key used by the freight analysis.

TIRTL_263_ESite-heading ID

Stable directional master-record identifier.

EHeading code

Source direction code; the readable direction is shown separately.

Search exact sensor details Heading status

Sensor register CSV Full register JSON All source fields ID dictionary Build/database information

Limits of the available metadata

This register shows fields present in the current report release and optional local DuckDB tables. Hardware serial numbers, lane-installation drawings, calibration certificates, maintenance logs and commissioning records are not implied unless explicitly displayed.

Exact-heading visual evidence

TIRTL sensor evidence graphs

These graphs pair each exact source-site and site-heading identifier with its monitoring-site label. Average-per-day graphs divide recorded passings by each heading's own available reporting days.

Semantic colour system:Time-mix graphs progress naturally from light sky blue for day, through twilight violet for evening, to midnight navy for overnight. Overnight-burden graphs also use midnight navy; truck-share graphs use burnt freight orange; all-day truck-rate graphs use transport teal. Deep teal marks selected headings and grey marks other headings at the same source-site ID. Grey does not mean defective or unreliable.

How to understand these graphs in under a minute Read the shape first, then the exact TIRTL ID

Longer barsUsually mean more truck passings. Percentage graphs instead show the share of traffic.

Light to dark time coloursLight blue is day, violet is evening and dark navy is overnight.

Deep teal and greyDeep teal means selected for comparison. Grey means another record, not a faulty sensor.

Exact IDs matterEvery claim can be traced to a TIRTL source-site and directional heading.

Every graph includes an At a glance explanation, what to look for, why it matters, a caution, a copy-ready briefing line and a question to put to government.

Cross-corridor evidence

All five source-scope and exact-heading graphs

Open complete sensor graph gallery

Selected corridor

Exact-heading graphs

Open technical coverage and heading-selection audit

Coverage is shown separately so short or incomplete reporting periods are not mistaken for differences in freight intensity. Grey headings are not selected for the metric; they are not labelled faulty.

Download graph source rows Download graph index Download graph manifest Download colour guide

Infrastructure accountability

Measured fact versus evidence government must supply

This matrix prevents the freight data being overstated while turning each missing infrastructure dataset into a specific accountability request.

Copy-ready briefing paragraph

Question for government

Supporting evidence

Publication-ready freight graphs

Open the complete graph gallery

Regional disparity

Reviewed monitored non-freeway comparison

These values compare qualifying monitored locations and disclose headings, sites and heading-days. They are not a census of every road in each region.

Region	Weighted truck share	Trucks per heading-day	Headings	Sites	Heading-days	Included areas

Download regional comparison extract

Interpretation and limitations

How to use the evidence safely

Sensor passings, not unique journeys

Vehicle and truck values are classified TIRTL sensor passings, not counts of unique vehicles, unique trucks or complete corridor journeys.

Night definition

A night runs from 22:00 on date D through 05:59 on the following date and is assigned to date D.

Monitoring points are not continuous coverage

Mapped sensor positions show where the evidence was collected. The page does not infer that every point between them was continuously measured.

Freight exposure is not pavement condition

The TIRTL evidence supports traffic-exposure findings. Asset condition, maintenance, lighting and expenditure require separate source records.

Corridor accountability metrics Monitoring-scope extract Companion page JSON Main report methodology