📊 Melbourne SCATS Traffic Analysis 2014–2026

Melbourne SCATS Traffic Analysis 2014–2026: Congestion, Volume, Interactive Maps and OOH Billboard Intelligence

A unified, deduplicated and cleaned Melbourne SCATS traffic intelligence platform covering 539+ billion cleaned vehicle movements, 12+ years of history, 15-minute behavioural analytics, interactive maps, suburb commute intelligence, OOH opportunity discovery, database diagnostics, data-quality evidence and reproducible open-source workflows.

Melbourne Traffic Data, Congestion Hotspots and Billboard Exposure Intelligence

This page brings together Department of Transport Melbourne SCATS traffic signal data , cleaned traffic-volume outputs, interactive maps, busiest-site rankings, congestion findings, yearly and daily movement intelligence, database diagnostics and OOH billboard exposure intelligence.

Melbourne traffic data SCATS analysis Congestion hotspots Busiest intersections OOH billboard exposure Vicmap parcel intelligence West Gate Bridge context Traffic intelligence 15-minute traffic analysis Suburb commute times Traffic intensity map
12+ years of Melbourne traffic intelligence · 539+ billion cleaned vehicle movements · 15-minute resolution · 97.95GB analytical environment · Open-source methodology · Interactive maps & OOH intelligence

Author: Clarke Towson, BCMS (Bachelor of Computer & Mathematical Science)
Manager — Spotswood Trailers
Linux Systems Specialist & Former DST Group High Performance Computing Specialist

Call: +61 432 359 166
or email: clarke@spotswoodtrailers.com.au
or Facebook: clarke.towson

Creator of The West Gate Bridge Live Stream (YouTube)

Open Source Project Repository: github.com/clarketowson/melbourne-scats-intelligence

The Melbourne SCATS Intelligence platform is fully reproducible, with analytical workflows, processing scripts, diagnostics, data-quality systems and supporting methodology being released publicly through the GitHub repository.
Found this platform useful?
Please consider sharing the Melbourne SCATS Intelligence Platform with journalists, transport planners, engineers, developers, OOH media professionals, freight/logistics observers, researchers or anyone interested in Melbourne traffic intelligence.

539+ billion cleaned vehicle movements, 12+ years of Melbourne traffic intelligence, interactive maps, diagnostics, data-quality evidence and a reproducible open-source analytical workflow.



MapsInsightsDataOOH / BusinessSystemsMedia / Downloads


Council Reports Platform Index Latest DTP Briefs Yearly Totals Popular Interactive Maps Suburb Traffic Intensity Map Commute + Traffic Pressure Map Commute Graphs V2 Post-Tunnel Change Map OOH Method Top 100 OOH Map Discovery Engine Corridor Dominance Top 100 Parcel Opportunity Map Top 10 Network Findings Top 10 Congestion Findings Top 10 Strategic Insights Supporters & Sponsors Page Statistics Headline Metrics Weather × Traffic Monthly Totals COVID Recovery Intelligence Seasonal Traffic Intelligence Daily Totals Second-Wave Charts Site-Month Charts Seasonal Intelligence Third-Wave Charts Traffic Archetypes Printed Scale Busiest Site Result Busiest Site Directory Interactive SCATS Map All SCATS Sites Map Busiest Day Result V3 Merge Status Busiest Time Bin Quietest Time Bin Peak Shares Weekday vs Weekend Day-of-Week Intelligence Time-of-Day Profile Reproducibility GitHub File Explorer and Script Search Vehicles vs Events Downloads Latest Briefs For Journalists Story Engine Question Index SCATS + TIRTL Questions Live vs Historical Movement Index Top Intersections Kepler.gl Visuals Executive Summary Architecture On-Site Compute Coverage Map Validation FAQ Technical Terms Schemas Site Intelligence OOH Media Top 100 OOH Opportunity Map OOH Buyer Pitch Pack OOH Build Roadmap Pipeline Registry Pipeline Status Methodology Database Diagnostics Top 10 Key Findings Project Timeline Performance Why It Matters Event Overlay Ethics Template Notes Media Insights Department Notes Public Dashboard Freight Insights Academic Research Data Transparency Statistical Confidence System Limitations Technology Stack

Council Traffic Intelligence Reports

🏛️ Open the 31-Council Traffic Intelligence Report Index
New council-level traffic intelligence section:
The Melbourne SCATS platform now includes a dedicated council traffic intelligence index covering all 31 council areas in the Greater Melbourne traffic report set. This section links directly to the council report index, where each council can be opened as an individual public traffic evidence page.

This council layer is designed for fast public understanding. Residents, councillors, MPs, council candidates, journalists, community groups and transport observers can start with a familiar boundary — the local council — and then inspect the traffic evidence for that area.

Council Areas

31

Evidence Types

SCATS + TIRTL

Report Format

HTML Index

Public Access

Open

Why the council reports matter:
Councils are the easiest civic boundary for most people to understand. The council reports turn public transport datasets into public traffic intelligence: visible, searchable, comparable and easier to share than internal GIS layers or one-off consultant reports.

The reports are not intended to replace council systems. They provide a public evidence layer built from open transport data, allowing traffic pressure, busy sites, freight signals and council-level patterns to be inspected from one public entry point.

Executive Summary

📄 Export Executive Summary as PDF
Executive summary — 17th May 2026:
This platform represents one of the largest independently processed open SCATS analytical environments publicly assembled in Australia. It converts more than 12 years of Melbourne traffic signal data into a reproducible transport intelligence platform covering cleaned 15-minute observations, yearly and monthly movement history, site rankings, corridor behaviour, OOH parcel opportunity discovery, cinematic movement visualisations, database diagnostics and data-quality evidence.

This is no longer simply a statistics page. It is a public analytical infrastructure layer for journalists, OOH media, freight/logistics observers, researchers, government readers, developers and the general public. The platform combines historical SCATS intelligence with an expanding TIRTL pathway for freeway speed, vehicle class, heavy-vehicle and corridor-performance analysis.

Unlike conventional dashboard-style summaries, this platform exposes the analytical process itself: structural diagnostics, database inventory, month-coverage auditing, duplicate-key evidence, interval-quality checks, processing-time transparency, downloadable CSV/JSON outputs and reproducible scripts.

Cleaned Observations

37.877B

Cleaned Movements

539.021B

Detector-Day Rows Audited

401.123M

Database Footprint

97.95GB

Coverage Window

2014–2026

Month Audit

148 expected / 0 unexplained missing

Duplicate Key Audit

0 duplicate detector-day keys

Time Resolution

15-minute intervals

Why this matters:
The public charts show Melbourne’s movement story; the diagnostics prove the machinery behind it. The project demonstrates that open government transport datasets, DuckDB, HPC-style chunked processing, reproducible scripts and independent infrastructure can produce city-scale transport intelligence previously associated with institutional environments.

The strongest current capability is historical SCATS intelligence: yearly totals, daily and monthly trends, time-of-day behaviour, weekday/weekend patterns, day-of-week and seasonal profiles, busiest-site rankings, site-month intelligence, OOH exposure analysis and interactive mapping. The next major expansion path is deeper SCATS + TIRTL integration for freight, freeway speed, vehicle class and corridor-performance intelligence.

Headline Metrics

New V5.2 site-month download set:
The following chart and CSV outputs support the new Site-Month Traffic Intelligence module, including named SCATS sites, network-node labels, fastest growth, volatility, seasonality, and top-site trends.

Cleaned Rows

37,877,397,311

Distinct Sites

4,907

Date Range Start

2014-01-01

Date Range End

2026-04-07

Total Cleaned Volume

539,020,710,239

Monthly Totals Status

148 / 148 complete

Highest Volume Month

2025-10

Highest Monthly Volume

4,513,402,918

Busiest Site ID

4415

Busiest Site Name

PRINCES NR CANNING

Busiest Site Total Volume

674,498,771

Peak Month at Busiest SCATS Site

2024-10

Peak-Month Volume

5,171,583

Busiest Time

17:15

Quietest Time

03:00

Busiest Day

2025-12-12

Busiest Day Volume

166,208,622

Daily Records

4,437

Quietest Non-Zero Day

2025-05-27

AM Peak Share

16.91%

PM Peak Share

20.54%

Template Status

Updated with busiest-site, busiest-day, busiest-time, quietest-time, peak-share, and V3 headline-merge findings

Database Footprint

102.7 GB on disk

Ranked Site Intelligence Sites

4,758

Top 1000 Portfolio Share

46.3%

Top 2000 Portfolio Share

71.9%

Sites Needed for 90% Traffic

~3,080

🧭 Explore the Melbourne SCATS Intelligence Platform

A guided index for journalists, transport planners, advertisers, researchers, councils, developers and the public. The page now follows a deliberate reading path: scale → latest updates → findings → maps → local intelligence → behavioural analytics → commercial value → media value → proof → technical appendix.

1. Start Here — Executive Summary & Key Findings

Understand the scale, headline numbers and why the work matters before going deeper.

Sections 1–7

Executive Summary Headline Metrics Key Findings Why It Matters

2. Headline Traffic Results

The confirmed macro results: yearly, monthly, daily, busiest sites, peak periods and weather-associated movement patterns.

Sections 8–17

Yearly Totals Monthly Totals Busiest Site Weather × Traffic

3. Maps & Spatial Intelligence

Jump straight to the visual layer: busiest sites, the full SCATS network, post-tunnel changes, coverage and cinematic animations.

Sections 18–25

Suburb Intensity Map Commute Map Commute Graphs Top 20 Map All Sites Map Post-Tunnel Map Animations

4. Suburb & Local Traffic Intelligence

Useful for councils, residents, journalists and anyone asking what the SCATS data says about a suburb or local intersection.

Sections 26–30

Suburb Traffic Map Commute Pressure Map Commute Graphs V2 Suburb Profiles Top 100 Suburbs Pressure Index Intersections

5. Behavioural Traffic Analytics

How Melbourne traffic behaves by time of day, day of week, weekday/weekend pattern, season, site-month trend and traffic archetype.

Sections 31–41

Time-Bin Behaviour Day-of-Week Archetypes Site-Month

6. OOH, Advertising & Commercial Opportunity

For billboard operators, property owners, advertisers and commercial decision-makers looking for exposure intelligence.

Sections 42–49

OOH Method Top 100 OOH Map Corridor Dominance Custom Reports

7. SCATS + TIRTL / Freight Intelligence

The bridge between signal-count intelligence, truck movement analysis, freight corridors, live comparison and historical events.

Sections 50–57

Latest DTP Briefs SCATS Questions SCATS + TIRTL Freight Insights COVID Recovery

8. Media, Public Interest & Institutional Relevance

Media story angles, public dashboard ideas, institutional observations, academic uses and open-source direction.

Sections 58–65

For Journalists Story Engine Department Notes Open Source

9. Downloads, Methodology & Reproducibility

The trust layer: downloadable outputs, validation, transparency, statistics, methodology, diagnostics and searchable files.

Sections 66–75

Downloads Reproducibility Methodology Diagnostics

10. Technical Appendix & System Build

The engineering appendix: registry, scripts, processing time, infrastructure, architecture, technology stack and build history.

Sections 76–88

Pipeline Status Script Registry Processing Time Architecture

11. Responsible Use, FAQ & Version History

Limitations, responsible use, plain-English terms, frequently asked questions and page/version history.

Sections 89–97

Responsible Use Limitations FAQ Version History

Tip: use this index as the main reader map, then use the quick-access buttons above for the most popular maps and commercial intelligence sections.

Latest DTP Open Data Intelligence Briefs

This section tracks new Department of Transport and Planning SCATS and TIRTL open-data releases as they become available. The purpose is simple: turn raw open-data releases into rapid, readable traffic and freight intelligence.

When new SCATS or TIRTL data is released, the update can be processed into headline movement totals, busiest SCATS signal locations, strongest SCATS movement increases, highest-volume TIRTL truck locations, truck-share hotspot tables, mapped report locations, anomaly and watchlist candidates, publication caveats, method notes and supporting CSV evidence.

Latest brief — Melbourne Traffic & Freight Intelligence Brief, June 2026 Open Data Update

This automated brief covers the newest data window not included in the earlier SCATS and TIRTL project outputs.

SCATS Window

8 Apr – 11 Jun 2026

TIRTL Window

23 May – 11 Jun 2026

SCATS Movements

9.15B

SCATS Sites

4,612

TIRTL Vehicles

326.2M

TIRTL Trucks

48.1M

What each monthly brief tracks

  • busiest SCATS signal sites;
  • strongest SCATS movement increases;
  • heaviest TIRTL truck locations;
  • highest truck-share hotspots;
  • SCATS and TIRTL anomaly / watchlist candidates;
  • map panels and clickable report locations; and
  • supporting CSVs, named tables, maps and methodology notes.

Why this matters

DTP open data is valuable, but raw data releases are difficult for most people to interpret. This reporting pipeline turns each release into a concise traffic and freight intelligence briefing with named sites, ranked tables, map panels and supporting evidence.

The important point is not only the individual report. It is now a repeatable monthly capability: from open data release to media-ready traffic intelligence in under 30 minutes once the data is available.

Responsible-use note: Watchlist and anomaly rows are useful story leads for review, but they should not be treated as automatic proof of cause. Public claims should check named locations, road-name text, map coordinates and any unusual movement changes before publication.
Release SCATS window TIRTL window Public links
June 2026 2026-04-08 to 2026-06-11 2026-05-23 to 2026-06-11 Release folder · Latest PDF · Evidence pack

The monthly brief archive is designed to grow as new DTP SCATS and TIRTL releases are processed. The stable latest links can be updated each month while the dated release folders preserve the historical archive.

Top 10 Key Findings

📄 Export Top 10 Key Findings as PDF

The completed V3 headline merge, monthly totals, daily totals, site-intelligence, time-bin, and peak-share workflows now provide enough confirmed data to support three public-facing Top 10 sections. These findings are designed for fast reading by journalists, public readers, transport analysts, government agencies, researchers, and out-of-home media planners.

Why this section matters: the page has moved from a technical database demonstration into a publishable Melbourne traffic intelligence briefing. It can now tell readers how much Melbourne moved, when it moved, where the heaviest signalised load was concentrated, and why the network behaves the way it does.

Top 10 Network Findings — What Melbourne Actually Does

These are the broadest confirmed findings from the unified SCATS archive. They explain the true scale of the dataset and the actual movement patterns visible across Melbourne's signalised road network.

1Melbourne generated more than 539 billion vehicle movements

The completed total-cleaned-volume process confirms 539,020,710,239 cleaned vehicle movements across 148 / 148 months.

2The archive contains nearly 38 billion cleaned observations

The unified cleaned archive contains 37,877,397,311 usable 15-minute observations.

3The system covers 4,907 SCATS sites

The archive confirms 4,907 distinct SCATS sites across the original, continuation, and recovery databases.

4The loaded archive spans more than 12 years

The unified date range runs from 2014-01-01 to 2026-04-07, giving the page long-run historical context.

5October 2025 was the highest-volume month

The completed monthly totals process identifies 2025-10 as the highest-volume month, with 4,513,402,918 cleaned vehicle movements.

6Friday 12 December 2025 was the busiest recorded day

The completed daily totals process identifies Friday 12 December 2025 as the busiest recorded day, with 166,208,622 cleaned movements.

7PRINCES NR CANNING is the busiest confirmed site

SCATS site 4415 — PRINCES NR CANNING is currently the busiest ranked site, with 674,498,771 total cleaned vehicle movements.

8The page has a complete daily record layer

The completed daily totals workflow confirms 4,437 daily records, enabling day-by-day comparisons and event discovery.

9The three DuckDB archives occupy about 102.7 GB

The SCATS analytical databases occupy approximately 102.7 GB on disk, explaining why chunked workflows were required.

10The V3 headline merge is complete

The final headline merge confirms all required sources are present and complete: total volume, busiest site, busiest day, busiest time bin, and peak shares.

Top 10 Congestion Findings — Where and When Pressure Builds

These findings explain the time-of-day and concentration patterns that define Melbourne's pressure points.

1Almost 40% of all traffic occurs in six peak hours

The combined AM and PM peak windows account for 37.45% of all cleaned vehicle movements.

2The afternoon peak is stronger than the morning peak

The PM peak accounts for 20.54% of all movements, compared with 16.91% for the AM peak.

317:15 is Melbourne's busiest 15-minute traffic interval

The busiest network-wide time bin is 17:15, averaging 2,283,898 movements per day across 4,437 dates.

403:00 is the quietest network interval

The quietest average daily time bin is 03:00, averaging 151,358 movements per day.

5The PM peak alone represents more than 110 billion movements

The afternoon peak window from 16:00–19:00 contains 110,696,055,470 cleaned vehicle movements.

6The AM peak alone represents more than 91 billion movements

The morning peak window from 07:00–10:00 contains 91,161,505,910 cleaned vehicle movements.

7Traffic load is highly concentrated

The top 100 ranked sites account for 7.8% of ranked traffic, while the top 500 account for 28.0%.

8The top 1,000 sites carry nearly half the ranked traffic

The top 1,000 sites account for 46.3% of total ranked traffic.

9About 1,120 sites carry half the traffic

The threshold analysis shows approximately 1,120 sites are required to capture 50% of ranked traffic.

10About 3,080 sites capture 90% of ranked traffic

The threshold analysis shows approximately 3,080 sites are required to capture 90% of ranked traffic.

Top 10 Strategic Infrastructure Insights — What Matters Long-Term

These findings translate the technical outputs into strategic value for government, media, researchers, advertisers, and infrastructure decision-makers.

1Melbourne's traffic backbone is measurable

The concentration analysis shows that a minority of sites carry a disproportionate share of traffic, making the city's practical movement backbone identifiable.

2The archive can support evidence-based corridor prioritisation

Site rankings, monthly volumes, daily totals, and time-bin profiles can help identify where infrastructure attention would have the greatest network effect.

3Peak-period policy can be tested against hard numbers

With 37.45% of traffic occurring in six peak hours, congestion policy can be assessed against quantified demand windows.

4OOH media planning can be ranked by actual movement load

The site-intelligence and portfolio-efficiency layers can help identify high-exposure traffic locations instead of relying only on broad assumptions.

5The system can generate journalist-ready public interest stories

The page now has named places, dates, totals, peaks, and trend layers that are understandable to the public and useful for news media.

6Monthly and daily trends allow disruption detection

Completed monthly and daily totals create a foundation for identifying COVID effects, seasonal surges, public-event spikes, and network disruptions.

7The system proves citizen-scale infrastructure analytics is possible

A privately built pipeline has processed a city-scale traffic archive using on-site computing, chunked analysis, and reproducible output files.

8The SCATS + TIRTL combination can move beyond intersection counts

SCATS provides signalised intersection volumes, while TIRTL can add freeway-grade speed, classification, and corridor behaviour.

9The platform can become a public traffic transparency layer

By publishing outputs, charts, methods, and downloads, the page can become an independent reference point for Melbourne movement analysis.

10The next breakthrough is interactive and predictive intelligence

The current foundation supports future live overlays, historical playback, incident comparison, corridor animations, predictive models, and natural-language querying.

Suggested reader takeaway: this is no longer just a statistics page. It is becoming an independent Melbourne traffic intelligence platform.

Why This Matters to Melbourne

📄 Export Why This Matters to Melbourne as PDF

This work gives Melbourne a rare independent view of its signalised traffic network across more than a decade. It helps explain congestion, recovery, behavioural change, commuter rhythm, seasonal pressure, commercial exposure, freight context and public infrastructure questions in a form journalists, executives and residents can inspect.

The public value is not just the charts. It is the combination of cleaned data, reproducible compute, interactive maps, visual storytelling, OOH/parcel intelligence and a question-to-answer index that turns raw traffic counts into a practical city movement intelligence platform.

Yearly Totals Intelligence — Melbourne's Macro Traffic History

📄 Export Yearly Totals Section as PDF
Yearly totals completed — 12 May 2026:
The yearly totals workflow is now complete across the full SCATS analysis window from 2014-01-01 to 2026-04-07, with 148/148 months processed. This gives the page a clean macro layer: long-term growth, the COVID-period collapse, the recovery phase, the 2025 record year, and the partial 2026 continuation period.

The yearly totals are one of the most important public-facing parts of the platform because they compress the entire 15-minute SCATS processing pipeline into a simple historical story. Viewers can immediately see Melbourne's traffic growth, the 2020 shock, and the post-COVID recovery into a new record year.

Cumulative movements

539B+

Running cumulative total across the available 2014–2026 dataset.

Record full year

2025

Approximately 50.5B movements and 139.2M average daily movements.

COVID-period low

2020

Approximately 37.0B movements and 102.1M average daily movements.

Recovery scale

+36.3%

2025 average daily movements compared with the 2020 low.

Coverage

148/148

All expected months in the reporting window were processed.

Partial year

2026

Shown separately as a partial year through 7 April 2026.
Data transparency note: One monthly ingest source was unavailable for 2018-12. The year is retained transparently in the charts and coloured orange where relevant. For fair trend comparisons, partial 2026 is excluded from year-over-year and indexed-growth charts.

1. Melbourne Total Vehicle Movements by Year

The flagship yearly chart. It shows the long-term traffic story: growth, COVID-period disruption, recovery, and 2025 emerging as the strongest full year.

Melbourne total vehicle movements by year, showing COVID-period low, 2025 record year, 2026 partial year and 2018 ingest-source disclosure

2. Average Daily Vehicle Movements by Year

Average daily movements make full-year comparisons easier and show the scale of the 2025 record year more clearly.

Average daily vehicle movements by year for Melbourne SCATS data

3. COVID Low vs Record Year

A direct comparison between the 2020 low and 2025 record year. This is one of the clearest media-facing recovery visuals.

COVID low versus record year comparison showing 2020 against 2025

4. Year-over-Year Change

Full-year-only percentage change. Partial 2026 is excluded to avoid implying a false traffic collapse.

Year-over-year change in Melbourne vehicle movements using full years only

5. Traffic Growth Index

Indexed to 2014 = 100, this chart shows long-term structural growth while excluding partial 2026.

Melbourne traffic growth index with 2014 as 100

6. Cumulative Vehicle Movements

The scale-shock chart: cumulative cleaned vehicle movements now exceed 539 billion across the available dataset.

Cumulative Melbourne vehicle movements from 2014 to 2026

7. Months Loaded Per Year

A coverage and transparency check showing full years, valid loaded months, the 2018 unavailable monthly ingest source, and partial 2026.

Months loaded per year showing 2018 as 11 valid months and 2026 as a partial year

Why this section matters

This section gives the platform an executive-summary layer. The daily, monthly, site-level and 15-minute charts prove technical depth; the yearly totals explain the historical story in seconds. For journalists, government readers, OOH media, freight/logistics observers and the public, these yearly charts are likely to be among the most understandable and most frequently reused outputs on the page.

Expected chart directory: charts/yearly_totals_v5/

Primary files: yearly_total_vehicle_movements_v5.png , yearly_average_daily_movements_v5.png , yearly_yoy_percentage_change_v5.png , yearly_index_growth_comparable_years_v5.png , yearly_cumulative_vehicle_movements_v5.png , yearly_covid_low_vs_record_year_v5.png , yearly_valid_months_loaded_v5.png .

Confirmed Monthly Totals Result

Confirmed result:
The completed monthly totals workflow confirms 539,020,710,239 cleaned vehicle movements across 148 / 148 months, covering the unified SCATS archive from 2014-01-01 to 2026-04-07. The run completed cleanly with 148 monthly CSV rows and the final JSON reports is_complete = true.

Total Cleaned Monthly Volume

539,020,710,239

Months Completed

148 / 148

Monthly CSV Rows

148

Date Range

2014-01-01 to 2026-04-07

Highest Volume Month

2025-10

Highest Monthly Volume

4,513,402,918

Lowest Month

2018-12

Lowest Monthly Volume

0 (missed/missing CSV file; not a true zero-traffic month)

Average Month

3,642,031,826

Median Month

3,704,917,910

Processing Time

4.54 hours

Workflow Status

Complete

This monthly result is now the backbone trend layer for the SCATS project. It gives the page a completed month-by-month time series that can feed the first major public charts: long-term monthly traffic, yearly totals, seasonal movement, pandemic-era disruption, post-pandemic recovery, and recent growth pressure.

Data-quality note: 2018-12 is confirmed as a zero-volume month in the monthly output. That should be treated as a visible data gap or source-coverage issue, not as a real-world month with no traffic. The next-lowest non-zero month is 2026-04 with 840,492,772 cleaned vehicle movements.
Media interpretation: The strongest full month is 2025-10 with 4,513,402,918 cleaned vehicle movements. The completed yearly series shows the archive rising from approximately 40.23 billion cleaned movements in 2014 to 50.52 billion in 2025, making the monthly totals section one of the clearest ways to communicate long-term growth in Melbourne traffic demand.

Generated Monthly and Yearly Traffic Charts

Monthly Total Traffic

Long-term monthly cleaned traffic movement trend across the full SCATS archive.

Melbourne SCATS traffic analysis chart showing Monthly Total Traffic from 2014 to 2026

Monthly Traffic with Rolling Average

Smoothed trend view designed to make long-term growth, disruptions, and recovery easier to see.

Melbourne SCATS traffic analysis chart showing Monthly Traffic With Rolling Average from 2014 to 2026

Yearly Total Traffic

Annual cleaned traffic movement totals derived from the completed monthly output.

Melbourne SCATS traffic analysis chart showing Yearly Total Traffic from 2014 to 2026

Yearly Growth Rate

Year-on-year percentage movement, useful for showing the COVID disruption and post-pandemic rebound.

Melbourne SCATS traffic analysis chart showing Yearly Growth Rate from 2014 to 2026

COVID Disruption and Recovery

Dedicated monthly chart showing the pandemic-era collapse and the later recovery pattern.

Melbourne SCATS traffic analysis chart showing Covid Disruption And Recovery from 2014 to 2026

Average Month / Seasonality

Seasonality view showing which calendar months tend to carry stronger or weaker traffic demand.

Melbourne SCATS traffic analysis chart showing Average Month / Seasonality from 2014 to 2026
Chart integration note: These images are loaded from the local charts/ folder created by generate_scats_charts_v3_9_colour.py. Keep this HTML file beside the charts directory when publishing or previewing the page.

Network monthly volume rebuilt from site-month totals

This V5.2 chart confirms the full network monthly trend from individual SCATS site-month rows, excluding the final partial month to avoid a misleading end-of-series drop.

Melbourne SCATS network monthly traffic volume rebuilt from site-month totals

Network seasonality heatmap from site-month totals

Shows monthly network intensity by year. Neutral grey indicates a known missing or zero-row month rather than measured low traffic.

Network seasonality heatmap from Melbourne SCATS site-month totals

Top 10 Months by Total Cleaned Volume

RankMonthTotal Cleaned Volume
12025-104,513,402,918
22026-034,414,536,971
32024-104,395,226,918
42025-084,387,186,136
52025-034,384,498,446
62025-114,306,927,842
72025-054,304,234,239
82024-054,296,752,485
92025-074,285,801,250
102024-084,285,525,933

Lowest 10 Months by Total Cleaned Volume

RankMonthTotal Cleaned Volume
12018-120
22026-04840,492,772
32020-082,027,518,150
42020-092,187,779,825
52020-042,226,937,680
62021-092,669,449,713
72021-082,818,955,482
82020-072,892,506,105
92020-102,921,382,593
102020-052,973,651,861

Yearly Totals Derived from Monthly Output

YearTotal Cleaned Volume
201440,230,427,435
201540,941,942,434
201642,605,388,596
201743,261,052,427
201840,213,378,631
201945,474,463,564
202037,004,227,171
202141,714,712,032
202246,254,562,684
202347,874,719,592
202449,477,917,898
202550,522,524,502
202613,445,393,273
Processing note: The final monthly totals JSON reports 148 / 148 months complete, 148 rows in the monthly CSV, and 16,326.969 total elapsed seconds. .

Confirmed Daily Totals Result

Confirmed result:
The completed daily totals workflow confirms 539,020,710,239 cleaned vehicle movements across 4,437 daily records, covering the unified SCATS archive from 2014-01-01 to 2026-04-07. The run completed cleanly with 148 / 148 months processed and is_complete = true.

Total Daily Volume

539,020,710,239

Daily Records

4,437

Months Completed

148 / 148

Date Range

2014-01-01 to 2026-04-07

Busiest Day

2025-12-12

Busiest Day Volume

166,208,622

Quietest Day

2025-05-27

Quietest Day Volume

7,556,689

Average Non-Zero Day

121,483,144

Median Non-Zero Day

124,567,849

Zero-Row Month

2018-12

Processing Time

4.39 hours

Daily totals are one of the most public-facing layers in the entire SCATS project. They allow the archive to move from technical database scale into clear city-history questions: Melbourne’s busiest traffic days, quietest disruption days, COVID-era collapse, holiday patterns, weekday/weekend behaviour, recovery curves, and the largest one-day shocks in the road network.

Important interpretation: 2025-05-27 is currently the quietest non-zero day at 7,556,689 cleaned movements. Because it is dramatically lower than surrounding days, it should be treated as a high-priority investigation candidate before being presented as a real-world traffic collapse. The next day rebounds by approximately 140.3 million cleaned movements, which strongly suggests either a serious data coverage issue or an exceptional event that deserves separate checking.
Public-interest finding: The top 9 busiest daily records are all late-2024 to early-2026 dates, and 9 of the top 10 are Fridays. This gives the page a very simple public story: Melbourne’s highest measured daily SCATS volumes are heavily concentrated in recent years and around the end-of-week traffic cycle.

Generated Daily Traffic Charts

Daily Traffic Over Time

A full date-by-date line chart showing the complete daily movement spine from 2014 to 2026.

Melbourne SCATS traffic analysis chart showing Daily Total Traffic from 2014 to 2026

Daily Traffic with 7-Day Rolling Average

A smoothed public-facing trend chart that makes weekly cycles, lockdown disruption, and recovery easier to read.

Melbourne SCATS traffic analysis chart showing Daily Traffic With Day Rolling Average from 2014 to 2026

Daily Traffic with 30-Day Rolling Average

A stronger smoothing layer that reveals long-term disruption, recovery, and seasonal traffic movement.

Melbourne SCATS traffic analysis chart showing Daily Traffic With Day Rolling Average from 2014 to 2026

Top 50 Busiest Days

A ranked bar chart for media use, showing Melbourne’s highest-volume traffic days in the SCATS archive.

Melbourne SCATS traffic analysis chart showing Top Busiest Days from 2014 to 2026

Bottom 50 Quietest Days

A ranked disruption chart for lockdowns, holidays, missing coverage checks, and abnormal network-wide collapses.

Melbourne SCATS traffic analysis chart showing Bottom Quietest Days from 2014 to 2026

Daily Traffic Distribution by Year

Boxplot view showing how the normal daily traffic range changes year by year, without over-emphasising outliers.

Melbourne SCATS traffic analysis chart showing Daily Traffic Distribution By Year from 2014 to 2026

Largest Single-Day Traffic Changes

Highlights the biggest day-to-day rises and falls, including the 2025-05-27 anomaly that needs separate validation.

Melbourne SCATS traffic analysis chart showing Largest Single Day Traffic Changes from 2014 to 2026
Chart integration note: These daily charts are loaded from the local charts/ folder created by generate_daily_totals_charts_v2_2_colour_annotated.py. Keep this HTML file beside the charts directory when publishing or previewing the page.

Top 10 Busiest Days by Total Cleaned Volume

RankDateDayTotal Cleaned Volume
12025-12-12Friday166,208,622
22025-12-05Friday165,491,991
32025-11-28Friday165,193,216
42025-11-14Friday163,377,630
52025-11-21Friday162,975,898
62024-11-29Friday162,766,167
72024-12-13Friday162,314,859
82026-02-20Friday162,167,735
92026-02-13Friday162,114,953
102025-12-11Thursday161,713,728

Lowest 10 Non-Zero Days by Total Cleaned Volume

RankDateDayTotal Cleaned Volume
12025-05-27Tuesday7,556,689
22020-08-09Sunday37,292,786
32020-08-16Sunday39,706,127
42020-04-10Friday40,210,106
52020-08-23Sunday41,090,426
62020-04-12Sunday41,621,250
72020-08-30Sunday43,273,397
82021-02-14Sunday45,418,017
92020-08-08Saturday45,858,809
102021-05-30Sunday46,547,102

Average Daily Volume by Day of Week

DayDaily RecordsAverage Cleaned Volume
Monday633119,397,506
Tuesday635125,719,289
Wednesday634129,360,318
Thursday634131,603,996
Friday632133,041,719
Saturday634114,018,602
Sunday63597,305,204
Processing note: The final daily totals JSON reports 15796.017 total elapsed seconds, equivalent to approximately 4.39 hours. The source CSV path recorded by the workflow is daily_totals.csv .

Supporting workflow metadata: daily_totals_final.json

Confirmed Busiest Day Result

Confirmed result:
The completed busiest-day process identifies 12 December 2025 as the busiest recorded traffic day in the unified SCATS archive, with 166,208,622 cleaned vehicle movements across the loaded network.

Busiest Day

2025-12-12

Busiest Day Volume

166,208,622

Daily Records

4,437

Quietest Non-Zero Day

2025-05-27

Day of Week

Friday

Total Volume

166,208,622

Date Range

2014-01-01 to 2026-04-07

Months Completed

148 / 148

Processing Time

31.5 hours

This is a simple, public-facing headline result: across more than twelve years of cleaned SCATS observations, the highest single-day network total currently observed was Friday 12 December 2025. The top-ranked days are strongly concentrated on Fridays, especially in late November and December, which points toward end-of-year commuter, retail, logistics, and holiday-movement pressure.

Generated Busiest-Day and Weekday Charts

Top 10 Busiest Days

Ranked daily chart showing the highest recorded traffic days in the archive.

Melbourne SCATS traffic analysis chart showing Top Busiest Days from 2014 to 2026

Busiest Day by Year

Year-by-year view showing the strongest daily traffic result for each year.

Melbourne SCATS traffic analysis chart showing Busiest Day By Year from 2014 to 2026

Average Daily Volume by Weekday

Weekday profile showing how traffic demand varies across the week.

Melbourne SCATS traffic analysis chart showing Average Daily Volume By Weekday from 2014 to 2026
Interpretation note: The top daily results are dominated by recent years, particularly 2024–2026, which suggests the system is now capturing very high post-pandemic traffic demand. April 2026 remains a partial edge month because the archive ends on 2026-04-07.

Top 10 Busiest Days by Total Cleaned Volume

RankDateDayTotal Volume
12025-12-12Friday166,208,622
22025-12-05Friday165,491,991
32025-11-28Friday165,193,216
42025-11-14Friday163,377,630
52025-11-21Friday162,975,898
62024-11-29Friday162,766,167
72024-12-13Friday162,314,859
82026-02-20Friday162,167,735
92026-02-13Friday162,114,953
102025-12-11Thursday161,713,728

Busiest Day by Year

YearBusiest DateDayTotal Volume
20142014-12-12Friday132,051,790
20152015-12-04Friday134,707,106
20162016-12-16Friday139,308,014
20172017-12-15Friday143,180,251
20182018-11-30Friday141,550,913
20192019-12-13Friday151,916,062
20202020-12-18Friday148,658,715
20212021-12-17Friday152,959,237
20222022-11-25Friday152,536,841
20232023-12-15Friday157,265,385
20242024-11-29Friday162,766,167
20252025-12-12Friday166,208,622
20262026-02-20Friday162,167,735
Processing note: The final busiest-day JSON reports the run as complete at 148 / 148 months. The V3 headline merge also confirms the busiest-day source as present and complete.

Confirmed Busiest Site Result

V5.2 site-month confirmation:
The busiest-site result is now supported by a friendly-named Top 20 total-volume chart and a Top 10 over-time chart generated from site-month totals.
Confirmed result:
The completed busiest-site process identifies PRINCES NR CANNING (SCATS site 4415) as the busiest loaded SCATS location in the current archive, with 674,498,771 total cleaned vehicle movements across the loaded period from 2014-01-01 to 2026-04-07.

SCATS Site ID

4415

Site Name

PRINCES NR CANNING

Total Volume

674,498,771

Recorded Months

147

Peak Month

2024-10

Peak-Month Volume

5,171,583

Average Monthly Volume

4,588,427

Share of Total Cleaned Volume

0.125%

This is the first confirmed location-level headline result produced by the chunked site-ranking workflow. It matters because it turns the project from a purely network-wide scale story into a place-specific intelligence story. Readers can now point to a named SCATS site and say: this location carried more total cleaned traffic than any other currently loaded site in the archive.

Generated Busiest-Site Charts

Top 20 Busiest SCATS Sites

Ranked location chart showing the strongest loaded SCATS sites by total cleaned movements.

Melbourne SCATS traffic analysis chart showing Top Busiest Scats Sites from 2014 to 2026

Busiest Site Monthly Trend

Monthly trend for the leading site, showing how the busiest site behaved across the archive.

Melbourne SCATS traffic analysis chart showing Busiest Site Monthly Trend from 2014 to 2026
Interpretation note: The monthly CSV indicates that PRINCES NR CANNING was the top monthly site in 29 of the archive’s 148 processed month labels, while its strongest recorded month was 2024-10 with 5,171,583 movements. The low point of 927,843 in 2026-04 is a partial-month edge case because the archive ends on 2026-04-07.
Processing note: The final JSON summary reports the busiest-site run as complete at 148 / 148 months, with a total elapsed processing time of approximately 41.6 hours.

Confirmed Busiest Time Bin Result

Confirmed result:
The completed busiest-time-bin process identifies 17:15 as the busiest average daily network-wide 15-minute interval in the unified SCATS archive, with 10,133,657,484 total cleaned vehicle movements across 4,437 distinct dates. On an average day, that 15-minute interval alone recorded approximately 2,283,898 cleaned vehicle movements across the loaded network.

Busiest Time Bin

17:15

Total Volume in Bin

10,133,657,484

Distinct Dates

4,437

Average Daily Volume

2,283,898

Months Completed

148 / 148

Processing Time

46.8 hours

This result is especially useful for journalists because it gives the archive a simple, human-readable answer to the question: when is Melbourne's signalized road network busiest? The answer from this completed run is not a vague “PM peak”; it is a precise 15-minute bin: 5:15pm to 5:30pm.

Generated Time-of-Day Charts

Average Daily Traffic by Time of Day

Full 24-hour movement curve showing AM rise, PM dominance, and overnight low demand.

Melbourne SCATS traffic analysis chart showing Average Daily Traffic By Time Of Day from 2014 to 2026

Top 24 Busiest Time Bins

Production-ranked time-bin chart highlighting the strongest 15-minute windows in the archive, using red intensity for peak pressure.

Melbourne SCATS traffic analysis chart showing Top Busiest Time Bins from 2014 to 2026
Method note: The ranking uses average daily volume per time bin, not raw total alone. That matters because it neutralises missed-day and partial-day distortion, especially around incomplete edge months such as April 2026.

Top 10 Time Bins by Average Daily Volume

RankTime BinTotal VolumeDistinct DatesAverage Daily Volume
117:1510,133,657,4844,4372,283,898
217:0010,082,970,2104,4362,272,987
315:309,905,230,2844,4372,232,416
416:309,869,364,7264,4352,225,336
516:159,859,910,7074,4352,223,204
616:009,855,576,4064,4352,222,227
716:459,849,659,4324,4362,220,392
815:459,828,534,7324,4362,215,630
917:309,778,795,1884,4372,203,920
1015:159,750,750,6214,4362,198,095

Monthly Winner Pattern

  • 17:15: monthly winner in 108 months
  • 17:00: monthly winner in 21 months
  • 15:30: monthly winner in 17 months
  • 15:15: monthly winner in 1 months

Interpretation

  • The top-ranked intervals cluster heavily around the afternoon peak.
  • 17:15 dominates the monthly winner count, appearing as the top monthly bin in 108 months.
  • The top 10 list is almost entirely between 3:00pm and 5:45pm, confirming the strength and breadth of the PM peak.

Strongest Monthly Time-Bin Results

MonthWinning Time BinMonthly VolumeDistinct DatesAverage Daily Volume
2026-0217:0076,006,729282,714,526
2025-1017:1583,961,729312,708,443
2025-0817:0082,444,199312,659,490
2024-0517:0082,236,304312,652,784
2025-0717:0082,124,813312,649,188
Processing note: The final JSON summary reports the busiest-time-bin run as complete at 148 / 148 months, generated at 2026-04-25 17:51:32 AEST, with a total elapsed processing time of approximately 46.8 hours.

Confirmed Quietest Time Bin Result

Confirmed result:
Using the completed monthly time-bin CSV, the quietest average daily network-wide 15-minute interval is 03:00, representing approximately 03:00–03:15. Across the loaded archive, this interval recorded 671,574,578 total cleaned vehicle movements across 4,437 distinct dates, averaging approximately 151,358 cleaned vehicle movements per day.

Quietest Time Bin

03:00

Approx. Time Window

03:00–03:15

Total Volume in Bin

671,574,578

Distinct Dates

4,437

Average Daily Volume

151,358

Source

Completed time-bin CSV

This result gives the page the natural counterpart to the confirmed busiest period. Together, the two results describe the daily movement envelope of Melbourne's signalized road network: the network is strongest around 17:15 and quietest around 03:00. That makes the story easier for a public audience to understand because it answers both ends of the same question: when does Melbourne move the most, and when does it move the least?

Generated Quietest-Time Chart

Top 24 Quietest Time Bins

Production-ranked overnight low-demand bins, using green intensity for quiet-network conditions.

Melbourne SCATS traffic analysis chart showing Top Quietest Time Bins from 2014 to 2026
Method note: No new heavy DuckDB chunked run was required for this result. The completed chunked_busiest_time_bin_monthly.csv already contains every valid time bin by month, including monthly volume and distinct-date counts. The quietest result is derived by aggregating those monthly rows and ranking by average daily volume per time bin in ascending order, excluding blank placeholder rows.

Top 10 Quietest Time Bins by Average Daily Volume

RankTime BinTotal VolumeDistinct DatesAverage Daily Volume
103:00671,574,5784,437151,358
202:45684,105,7624,434154,286
303:15685,751,3484,437154,553
403:30712,084,3014,437160,488
502:30714,253,4484,431161,195
603:45724,135,9964,437163,204
702:15746,959,1614,430168,614
804:00761,722,7804,437171,675
902:00790,996,2284,430178,554
1001:45838,489,7594,434189,105

Monthly Quietest Pattern

  • 03:00: monthly quietest bin in 127 months
  • 02:45: monthly quietest bin in 15 months
  • 02:30: monthly quietest bin in 4 months
  • 03:45: monthly quietest bin in 1 months

Interpretation

  • The quietest intervals cluster tightly in the early morning sleep period.
  • 03:00 is the lowest average daily interval across the full archive.
  • The top 10 quietest bins fall between roughly 2:00am and 4:15am, which is exactly the expected low-demand window for a metropolitan road network.
  • This result is a useful sanity check on the time-bin analysis because the quietest period lands where human behaviour predicts it should land.

Lowest Monthly Quietest Time-Bin Results

MonthQuietest Time BinMonthly VolumeDistinct DatesAverage Daily Volume
2020-0802:302,180,2593072,675
2020-0902:452,109,7502972,750
2021-0902:452,404,5753080,152
2021-0802:452,748,5963188,664
2020-0402:452,574,0042988,759
Processing note: This section was derived from the completed busiest-time-bin monthly CSV, which contains 14,112 valid month/time-bin rows across the processed archive. The result should be treated as a confirmed derived output from the completed V3 time-bin workflow.

Confirmed Peak Share Results

Confirmed result:
The completed peak-share process confirms that 20.54% of all cleaned vehicle movements occur during the afternoon peak window (16:00–19:00), while 16.91% occur during the morning peak window (07:00–10:00). Across the full archive, the PM peak carries 110,696,055,470 cleaned movements and the AM peak carries 91,161,505,910 cleaned movements.

AM Peak Window

07:00–10:00

PM Peak Window

16:00–19:00

AM Peak Volume

91,161,505,910

PM Peak Volume

110,696,055,470

AM Peak Share

16.91%

PM Peak Share

20.54%

Combined Peak Share

37.45%

Total Volume Analysed

539,020,710,239

Months Completed

148 / 148

Processing Time

45.6 hours

Generated Peak-Share Charts

AM vs PM Peak Share Over Time

Monthly comparison of morning and afternoon peak shares across the archive.

Melbourne SCATS traffic analysis chart showing Am Vs Pm Peak Share Over Time from 2014 to 2026

Peak vs Off-Peak Volume

Simple public-facing split showing how much movement occurs inside and outside the two peak windows.

Melbourne SCATS traffic analysis chart showing Peak Vs Off Peak Volume from 2014 to 2026

This result shows that Melbourne's signalised road network is heavily concentrated into short daily demand windows. The afternoon peak is materially stronger than the morning peak, with approximately 19,534,549,560 more cleaned vehicle movements recorded in the PM peak than the AM peak across the archive.

Interpretation: Combined AM and PM peak windows account for 37.45% of all cleaned vehicle movements, even though they cover only six hours of the day. In plain English, nearly four in every ten recorded traffic movements occur during the two main peak windows.
Processing note: The final JSON summary reports the peak-share run as complete at 148 / 148 months, generated at 2026-04-27 18:54:10 AEST, with a total elapsed processing time of approximately 45.6 hours.

🌦️ Melbourne Weather × SCATS Network Traffic Intelligence

Simplified public weather layer:
This section focuses on Melbourne-wide SCATS network behaviour rather than individual site-level weather rankings. That keeps the public interpretation clear: the results show observed weather-associated traffic patterns across the network, not proof that weather alone caused changes at specific intersections.

The analysis joins trusted daily SCATS network totals from 2014-01-01 to 2026-04-07 with Bureau of Meteorology daily weather observations for rainfall, maximum temperature, minimum temperature and solar exposure. Days are grouped into practical weather classes such as rain, heavy rain, extreme rain, hot days, very hot days, extreme heat, cold mornings, sunny days and low-solar days.

Important interpretation note:
These figures are weather-associated network differences, not single-cause weather impacts. Rain, heat and sunshine can overlap with seasonality, weekday mix, school terms, public holidays, major events, roadworks, COVID-era disruption, local activity patterns and long-term traffic growth. The bottom line is: Melbourne-wide traffic volumes were historically higher or lower on days with these weather characteristics, but the weather classification should not be treated as the only cause.

What the headline numbers show

Melbourne’s weather story is more interesting than a simple “rain equals traffic chaos” headline. At whole-network scale, ordinary rain is associated with only a modest traffic reduction, while heavier rain, extreme rain, very hot days and low-solar days show clearer movement suppression. In other words, Melbourne does not appear to shut down every time it rains — but the network does respond when weather becomes more severe, gloomy or uncomfortable.

The warm-weather pattern is also revealing. Hot days above 30°C show a small positive network difference, which may reflect stronger general activity, outdoor movement, retail activity, beach and recreation travel, or seasonal effects. But once temperatures move into very-hot territory, the pattern reverses: traffic volumes are lower than baseline. That suggests a practical behavioural threshold where ordinary warm weather may support activity, while oppressive heat begins to discourage or reshape travel.

Network-level weather response

The whole-network result suggests Melbourne traffic is resilient to ordinary weather but more sensitive to uncomfortable or disruptive conditions. Rain days are only slightly below baseline, but heavy rain and extreme rain show progressively larger reductions. Low-solar days also stand out, which may capture the combined effect of grey, wet, cold or low-activity conditions rather than sunshine alone.

This is useful because it separates everyday weather complaints from measurable network behaviour. The data suggests that normal rain is not the same thing as a citywide disruption. The larger movement changes appear when weather becomes severe enough to alter plans, reduce optional trips, shift travel times or discourage discretionary movement.

Melbourne SCATS network observed traffic difference by weather condition
Melbourne-wide SCATS movement difference by weather condition. These are observed network differences versus baseline, not proof that weather alone caused the change.

Rain severity matters

Melbourne talks about rain constantly, but the SCATS network does not treat all rain the same way. Light or ordinary rain is associated with a relatively small movement difference. As rainfall becomes heavier, the network-level reduction becomes more visible. That is the important public finding: the traffic story is not simply whether it rained, but how severe the rain was.

A likely explanation is that light rain changes comfort more than necessity. People still commute, go to school, make deliveries and move around the city. Heavier rain is different: visibility drops, roads become less comfortable, minor incidents become more likely, some discretionary trips are cancelled, and people may delay or consolidate travel. Extreme rain is where the citywide signal becomes much clearer.

Melbourne traffic difference by rainfall severity bucket
Rainfall bucket analysis showing how Melbourne-wide SCATS volumes differ as daily rainfall increases.

Temperature and heat behaviour

Heat behaves differently from rain. Warm and hot days can coincide with higher activity, especially when people are still willing to travel for work, shopping, recreation, events or beach-related movement. But very hot days appear to cross a behavioural threshold where movement falls below baseline.

The extreme-heat result should be read carefully. Days above 40°C are much rarer than days above 35°C, so that bucket is more sensitive to weekday mix, school holidays, summer timing, public holidays and unusual activity patterns. The safest interpretation is not that 40°C heat is “less disruptive” than 35°C heat, but that very-hot weather shows the clearest negative network signal in this version of the analysis, while extreme heat remains lower than baseline but is based on a smaller and more variable sample.

Melbourne traffic difference by maximum temperature bucket
Network traffic response by daily maximum temperature bucket, showing the difference between warm-day activity and very-hot-day suppression.

Why this matters

Melbourne has a cultural obsession with weather, but most weather-and-traffic discussion is based on anecdotes: “the rain made traffic terrible,” “everyone stayed home because it was too hot,” or “sunny days bring people out.” This analysis gives those claims a measured historical frame. It does not prove weather alone caused the movement changes, but it shows that Melbourne-wide SCATS volumes do vary in consistent, interpretable ways across different weather conditions.

The most useful finding is that weather response is graded, not binary. Ordinary rain is only modestly different from baseline. Extreme rain is much more visible. Warm weather can coincide with more activity. Very hot weather is associated with lower movement. Low-solar days also show a meaningful reduction, suggesting that gloomy or low-light conditions may be part of a broader low-activity weather pattern.

1. Weather data Bureau of Meteorology daily observations were prepared for Melbourne, including rainfall, temperature and solar exposure.
2. Trusted SCATS daily totals Network-level results use the existing trusted daily SCATS total file rather than re-summing site-level rows.
3. Weather classification Days were classified into rain, heavy rain, extreme rain, hot, very hot, extreme heat, cold morning, sunny and low-solar categories.
4. Public interpretation The public page now focuses on network-level weather-associated movement patterns, avoiding over-complex site-level claims that could be misread as direct causation.
Methodology note:
The network-level analysis uses trusted daily SCATS totals joined to daily Melbourne weather records. Results compare weather-classified days with the network baseline and should be interpreted as observed historical associations. Site-level V7 weather maps and charts were generated during analysis but are intentionally excluded from this public section because individual-site weather differences are more easily misunderstood without matched controls for weekday, month, season, events, holidays, roadworks, COVID-era disruption and local traffic changes.

Weather headline metrics

Daily Melbourne SCATS network volumes were joined with Bureau of Meteorology weather-classified days to identify broad, network-level traffic patterns associated with rain, heat, cold mornings, sunshine and low-solar conditions. These figures show observed network differences, not proof that weather alone caused the change.

🌧️
Rain days
−1.1%
Average network volume difference on rain-classified days versus the trusted SCATS daily baseline.
⛈️
Heavy rain
−2.5%
Heavier rain is associated with a larger observed drop in total Melbourne network movement.
🌊
Extreme rain
−6.1%
The strongest rain-classified days show the largest broad network traffic reduction.
☀️
Hot days 30°C+
+1.3%
Hot days show a small observed increase at the network level, likely mixed with season, activity, recreation and travel-pattern effects.
🔥
Very hot days 35°C+
−2.7%
Very hot conditions show the clearest negative heat-related network signal in this version of the analysis.
🥵
Extreme heat 40°C+
−2.0%
Extreme heat days show lower observed traffic, but the 40°C+ bucket is smaller and more sensitive to weekday mix, summer timing, holidays and unusual activity patterns.
❄️
Cold mornings
−1.0%
Cold-morning classified days are associated with a small reduction in network-wide daily movement.
🌤️
Sunny days
+0.8%
Sunny days show a small positive network difference, likely reflecting broader activity, seasonality and discretionary movement.
☁️
Low solar days
−2.9%
Low-solar days show one of the larger negative network-level differences outside extreme rain, possibly capturing gloomy, wet or low-activity conditions.
Interpretation note: These are weather-associated traffic patterns, not weather-only causal claims. Weather-classified days can also overlap with seasonality, weekday mix, school terms, public holidays, major events, roadworks, COVID-era disruption, local activity and long-term traffic growth.

Interactive Map — Melbourne's 20 Busiest SCATS Sites

Spatial view:
This interactive Google Map plots the top 20 busiest SCATS sites by total cleaned vehicle movements. Friendly public-facing names are shown first, while official SCATS labels and site IDs remain visible for auditability.

Mapped Sites

20

Busiest SCATS Site

4415

Top SCATS Site Volume

674.5M

Lowest SCATS Top-20 Volume

486.3M

Friendly names

Main road / cross road / local landmark, with direction added where it matters.

Official traceability

Each popup and table row keeps the SCATS site ID and official SCATS label.

Corridor grouping

Sites are grouped into readable arterial corridor categories for non-technical readers.

Traffic Intensity Legend

Red — Extreme traffic load
Orange — Very high traffic load
Yellow — High traffic load
Green — Lower within top 20
Circle size is scaled by total cleaned vehicle movements. Labels show rank order.
Key observation: The map shows strong clustering around the inner Melbourne, Hoddle, Eastern, Princes, Springvale, and north-eastern arterial corridors. This turns the ranked table into visible geographic traffic intelligence.

Interactive Map Site Directory

RankFriendly Location NameSCATS IDCorridor GroupTotal MovementsHeatGoogle Map
1 Princes Highway near Canning Street
Official SCATS label: PRINCES NR CANNING
4415 Princes Highway corridor 674.5M RED Open map
2 Eastern Freeway off-ramp at Hoddle Street
Official SCATS label: EASTERN FWY OFF RAMP/HODDLE
3380 Hoddle / Punt corridor 638.2M RED Open map
3 Princes Highway East at Park Street
Official SCATS label: PHE/PARK
2404 Princes Highway corridor 560.2M ORANGE Open map
4 Canterbury Road / Mitcham Road / Boronia Road
Official SCATS label: CANTERBURY/MITCHAM/BORONIA
849 Canterbury Road corridor 548.2M ORANGE Open map
5 Warrigal Road near Links Estate Access
Official SCATS label: WARRIGAL/LINKS ESTATE ACCESS
1359 Warrigal Road corridor 547.0M ORANGE Open map
6 Princes Highway East near Irving Road / Lansdowne Road
Official SCATS label: PHE NR IRVING (LANSDOWNE)
2487 Princes Highway corridor 544.7M ORANGE Open map
7 Hoddle Street / Albert Street / Elizabeth Street
Official SCATS label: HODDLE/ALBERT/ELIZABETH
3386 Hoddle / Punt corridor 544.0M ORANGE Open map
8 Princes Highway East at Albert Road
Official SCATS label: PHE/ALBERT
2405 Princes Highway corridor 518.6M ORANGE Open map
9 Mount Alexander Road near Lincoln Road
Official SCATS label: MT ALEXANDER NR LINCOLN
3519 North-west arterial corridor 513.9M ORANGE Open map
10 Springvale Road near Laughlin Avenue
Official SCATS label: SPRINGVALE NR LAUGHLIN AVE
416 Springvale Road corridor 506.0M ORANGE Open map
11 Eastern Highway / Queens Parade / Brunswick Street
Official SCATS label: EASTERN HWY/QUEENS/BRUNSWICK
2101 Eastern Freeway / inner east 497.4M ORANGE Open map
12 Canterbury Road at Heathmont Road
Official SCATS label: CANTERBURY/HEATHMONT
855 Canterbury Road corridor 497.0M ORANGE Open map
13 Metropolitan Ring Road / Greensborough Highway
Official SCATS label: MRR/GREENSBOROUGH HWY
3357 North-eastern arterial corridor 495.7M ORANGE Open map
14 Bulla Road near Holyrood Avenue
Official SCATS label: BULLA NR HOLYROOD
3516 North-west arterial corridor 494.1M ORANGE Open map
15 Bell Street at High Street
Official SCATS label: BELL/HIGH
3060 Bell Street corridor 492.4M ORANGE Open map
16 Diamond Creek Road / Greensborough Highway / Civic Drive
Official SCATS label: DIAMOND CREEK RD/GREENSBOROUGH HWY/CIVIC
2816 North-eastern arterial corridor 491.1M ORANGE Open map
17 Punt Road at Swan Street
Official SCATS label: PUNT/SWAN
3393 Hoddle / Punt corridor 489.6M ORANGE Open map
18 Hoddle Street near Studley Park Road — northbound
Official SCATS label: HODDLE NR STUDLEY (NORTHBOUND)
3376 Hoddle / Punt corridor 488.9M ORANGE Open map
19 Springvale Road near Walkers Road / Silver Grove
Official SCATS label: SPRINGVALE NR WALKERS/SILVER
415 Springvale Road corridor 488.7M ORANGE Open map
20 Springvale Road near Tunstall Avenue
Official SCATS label: SPRINGVALE NR TUNSTALL
414 Springvale Road corridor 486.3M ORANGE Open map

Top 20 Busiest SCATS Sites — Human-Readable Directory

Naming convention:
Each site is shown as a plain-English road location first, followed by the official SCATS site ID and original SCATS label. Slashes indicate intersecting roads or joined road approaches. Where the original label uses NR, the readable name converts it to near. Where the site has latitude/longitude coordinates, the map link opens directly at the mapped point; where coordinates are missing, the map link opens a Google Maps search using the SCATS ID and site name.
Why this matters: SCATS labels are useful to engineers but not ideal for public readers. This directory turns the top-ranked traffic sites into recognizable Melbourne locations while preserving the exact SCATS ID for auditability.
Rank Reader-friendly location name SCATS ID Official SCATS label Total movements Map target Google Map
1 Princes Street near Canning Street
Inner-north arterial hotspot
4415 PRINCES NR CANNING 674.5M -37.792825, 144.973731 Open map
2 Eastern Freeway off-ramp at Hoddle Street
Freeway-to-arterial ramp
3380 EASTERN FWY OFF RAMP/HODDLE 638.2M -37.795997, 144.993970 Open map
3 Princes Highway East at Park Street
Inner-south arterial junction
2404 PHE/PARK 560.2M -37.833437, 144.967764 Open map
4 Canterbury Road / Mitcham Road / Boronia Road
Eastern suburban arterial junction
849 CANTERBURY/MITCHAM/BORONIA 548.2M -37.836096, 145.195312 Open map
5 Warrigal Road / Links Estate access
South-east access pressure point
1359 WARRIGAL/LINKS ESTATE ACCESS 547.0M -37.922492, 145.082756 Open map
6 Princes Highway East near Irving Road / Lansdowne Road
Princes Hwy corridor
2487 PHE NR IRVING (LANSDOWNE) 544.7M -37.859989, 145.007416 Open map
7 Hoddle Street / Albert Street / Elizabeth Street
Inner-city Hoddle corridor
3386 HODDLE/ALBERT/ELIZABETH 544.0M -37.811248, 144.991117 Open map
8 Princes Highway East / Albert Road
Princes Hwy corridor
2405 PHE/ALBERT 518.6M -37.835130, 144.971089 Open map
9 Mount Alexander Road near Lincoln Road
North-west arterial corridor
3519 MT ALEXANDER NR LINCOLN 513.9M -37.744751, 144.910236 Open map
10 Springvale Road near Laughlin Avenue
Springvale Road corridor
416 SPRINGVALE NR LAUGHLIN AVE 506.0M -37.821450, 145.175440 Open map
11 Eastern Highway / Queens Parade / Brunswick Street
Inner-north gateway
2101 EASTERN HWY/QUEENS/BRUNSWICK 497.4M -37.793121, 144.979346 Open map
12 Canterbury Road / Heathmont Road
Outer-east arterial corridor
855 CANTERBURY/HEATHMONT 497.0M -37.829799, 145.244803 Open map
13 Metropolitan Ring Road / Greensborough Highway
Ring-road / arterial interface
3357 MRR/GREENSBOROUGH HWY 495.7M -37.695056, 145.092566 Open map
14 Bulla Road near Holyrood Avenue
Airport-side arterial corridor
3516 BULLA NR HOLYROOD 494.1M -37.738597, 144.906609 Open map
15 Bell Street / High Street
Northern arterial junction
3060 BELL/HIGH 492.4M -37.745172, 145.002817 Open map
16 Diamond Creek Road / Greensborough Highway / Civic Drive
Greensborough corridor junction
2816 DIAMOND CREEK RD/GREENSBOROUGH HWY/CIVIC 491.1M Lookup by site name Open map
17 Punt Road / Swan Street
Inner-city sports/river precinct
3393 PUNT/SWAN 489.6M -37.824602, 144.988855 Open map
18 Hoddle Street near Studley Park Road — northbound
Hoddle corridor northbound
3376 HODDLE NR STUDLEY (NORTHBOUND) 488.9M Lookup by site name Open map
19 Springvale Road near Walkers Road / Silver Grove
Springvale Road corridor
415 SPRINGVALE NR WALKERS/SILVER 488.7M -37.819786, 145.175764 Open map
20 Springvale Road near Tunstall Avenue
Springvale Road corridor
414 SPRINGVALE NR TUNSTALL 486.3M -37.815046, 145.176542 Open map
Manual name overrides used: SCATS site 2816 is shown as Diamond Creek Road / Greensborough Highway / Civic Drive, and SCATS site 3376 is shown as Hoddle Street near Studley Park Road — northbound. These two labels fill gaps left by the first coordinate lookup table.

Interactive Map — Full Melbourne SCATS Site Network

Full network explorer:
This section expands beyond the Top 20 sites and plots every mapped SCATS site with valid coordinates. Readers can search by SCATS ID, road name, municipality, or traffic band, then scroll through the full site directory without the page becoming dominated by thousands of rows.

Mapped Sites

4,427

Top SCATS Site

4415

Top SCATS Site Volume

674.5M

Traffic Bands

4

Reader use case: The Top 20 map is ideal for headline hotspots. This full-network map is better for suburb-by-suburb exploration, local reporting, OOH media planning, and letting readers find intersections they personally know.

Scrollable Full SCATS Site Directory

The full directory is intentionally contained in a scrollable box so readers can browse thousands of mapped sites without making the page unusably long.

Loading all sites…
Rank
SCATS Site
ID
Municipality
Total
Map

Traffic Intensity Legend

Red — Top 5% busiest sites
Orange — Top 20% busiest sites
Yellow — Middle-volume sites
Green — Lower-volume mapped sites
Circle size is scaled lightly by volume. Colours are based on percentile rank among sites in the cleaned archive.

Full Map Controls

Showing all mapped sites.

Interactive Map — Melbourne SCATS Site Changes After the West Gate Tunnel Opening Period

New citywide post-tunnel visual intelligence layer:
This embedded Google Map compares SCATS-detected vehicle movements at mapped signal sites for Jan–Mar 2025 versus Jan–Mar 2026. Red/orange markers indicate sites where detected traffic increased, blue markers indicate sites where detected traffic decreased, and grey markers indicate sites that were roughly flat.

Mapped Sites

4,343

Comparison Period

Jan–Mar

Net Change

+257.6M

Overall Change

+2.15%

Reader use case: This map is designed for journalists, councils, transport analysts and residents who want to visually inspect where monitored traffic volumes rose or fell after the West Gate Tunnel opening period. It is not a truck-only map; SCATS counts total detected movements at signalised sites.
How to read the map:
  • Red/orange = detected traffic increased between Jan–Mar 2025 and Jan–Mar 2026.
  • Blue = detected traffic decreased between Jan–Mar 2025 and Jan–Mar 2026.
  • Grey = roughly flat, within approximately ±3%.
  • Larger circles = larger traffic sites, scaled using the larger of the two Jan–Mar totals.
  • Click a site marker to see the SCATS site name, site ID, before/after totals, absolute change, percentage change, historical total and Google Maps link.
Method note: The map is a preliminary site-level SCATS comparison. It compares total SCATS-detected vehicle movements, not truck-classified movements. Individual site changes may reflect traffic redistribution, roadworks, detector configuration changes, signal changes, local network changes or genuine demand shifts. The map is best read as a powerful investigative layer showing where further analysis is needed.

Network Coverage Map

The coverage layer now spans full SCATS network coverage, ranked busiest SCATS sites, Top 20 mapping, temporal behaviour, site-month intelligence, corridor dominance, parcel/OOH opportunity mapping, Kepler movement visualisations, COVID/recovery intelligence and reproducibility evidence.

West Gate Bridge and freeway corridor references should be read together with the TIRTL analysis page: West Gate traffic analysis.

Strategic interpretation: this is now an independent Melbourne movement intelligence platform. SCATS explains the signalised network at scale, the parcel layer connects exposure to commercial land opportunity, and future TIRTL integration will deepen freeway, speed, class and heavy-vehicle intelligence.

Kepler.gl Spatial Traffic Intelligence Maps

New spatial intelligence layer:
The SCATS analysis now includes exported Kepler.gl WebGL maps built from the cleaned site-volume and coordinate dataset. These maps move the page beyond charts and tables by showing Melbourne traffic as a geographic intensity field: the full network, the arterial backbone, and the highest-ranked critical traffic nodes.

The exported map layers below form a progressive traffic-intelligence hierarchy. Readers can begin with the full SCATS network, zoom into the CBD, narrow to the top 5% busiest arterial backbone, then isolate the top 1% most critical traffic nodes. This turns the SCATS archive into a spatial tool for journalists, planners, councils, researchers, and commercial analysts.

Full network viewShows the complete mapped SCATS signal network and validates the geographic coverage of the dataset.
Top 5% arterial backboneRemoves lower-intensity noise and reveals Melbourne's major movement corridors.
Top 1% critical nodesIdentifies the highest-ranked traffic pressure points likely to matter most during incidents and disruptions.
Future animation baseThese maps establish the spatial foundation for future month-by-month and time-of-day Kepler.gl animations.

Static export set

Full Metro Traffic Intensity

The complete Melbourne SCATS network rendered as a weighted traffic intensity field. This is the baseline geographic view of the system.

Melbourne SCATS traffic analysis chart showing Melbourne Scats Traffic Intensity Full Metro from 2014 to 2026

CBD and Inner Melbourne Zoom

A detailed inner-city view showing the CBD grid, Docklands, Southbank, inner arterial links, and high-density signal clusters.

Melbourne SCATS traffic analysis chart showing Melbourne Scats Traffic Intensity Cbd Zoom from 2014 to 2026

Arterial Skeleton / Top Sites Layer

The filtered backbone view, designed to reveal the dominant traffic corridors and the structure of Melbourne's highest-volume movement network.

Melbourne SCATS traffic analysis chart showing Melbourne Scats Traffic Intensity Arterial Skeleton from 2014 to 2026

Top 5% Arterial Backbone Heatmap

This newer heatmap isolates the top 5% of SCATS sites to reveal Melbourne's main arterial movement skeleton with lower-volume noise removed.

Melbourne SCATS traffic map visualisation showing Melbourne Scats Top Percent Arterial Backbone Heatmap

Top 1% Critical Traffic Nodes

This highest-pressure node view isolates the most critical 1% of mapped SCATS sites, showing the locations most likely to matter during congestion, incidents, and network disruption.

Melbourne SCATS traffic analysis chart showing Melbourne Scats Top Percent Critical Traffic Nodes from 2014 to 2026
New critical-network exports: The Top 5% arterial backbone and Top 1% critical nodes maps show the difference between Melbourne's broad traffic structure and its highest-pressure failure points. Place both PNG files in the local charts/ directory beside the other generated charts.

Interactive Kepler.gl exports

All SCATS Sites Master Map

Interactive WebGL map showing all mapped SCATS sites with hover tooltips, volume scaling, and geographic coverage across Melbourne and surrounding regions.

Top 5% Busiest Sites

Filtered WebGL layer showing the primary arterial backbone of Melbourne's SCATS network.

Top 1% Critical Sites

The highest-ranked traffic nodes, suitable for bottleneck, incident-risk, and strategic-network discussions.

Embedded preview — All SCATS Sites Master Map

This embedded preview loads the exported Kepler.gl map. If it does not display when opened locally, open the linked HTML file directly or host all exported files in the same web directory as this page.

Publishing note: The exported Kepler.gl HTML files should be uploaded beside this page, along with the three PNG map exports. The Kepler.gl exports may include a Mapbox access token in plain text; restrict any production token by domain before publishing publicly.

Cinematic SCATS Traffic Animations

Playback note: Videos are embedded with standard browser controls and do not autoplay. Click play on any video to start it.

Melbourne Weekly Traffic Heartbeat

A cinematic day-of-week animation showing Melbourne’s weekly SCATS traffic rhythm: Monday’s weaker restart, the workweek build-up, Friday’s maximum movement intensity, and the sharp weekend fall into Sunday rest-state traffic.

Day-of-week intelligence Weekly heartbeat With music Download MP4

All SCATS sites: full-network reveal

A cinematic full-network reveal of Melbourne’s mapped SCATS signal sites, showing the geographic scale of the system before the page drills into daily, seasonal, time-bin and Top 100 intelligence.

Full SCATS network With music Download MP4

Local 7-day SCATS pulse animation

A locally rendered Python/ffmpeg animation of the 7-day Melbourne SCATS pulse, showing one frame per 15-minute bin across the full week without relying on Kepler.gl playback.

7-day pulse Local render Download MP4

Kepler.gl 24-hour 15-minute SCATS pulse

An OBS-recorded Kepler.gl animation of Melbourne’s SCATS network across a full 24-hour cycle, stepping through 15-minute time bins so viewers can watch the city wake, surge, peak, release and quieten again on the map.

Kepler.gl render 24-hour pulse 15-minute bins Download MP4

Daily total traffic animation

A longitudinal view of daily Melbourne SCATS traffic volume, showing large-scale movement, disruption, recovery and growth across the archive.

Daily totals With music Download MP4

Melbourne seasonal metabolism

A cinematic seasonal animation showing Melbourne’s month-of-year traffic rhythm, including the January trough and high-intensity February/November behaviour.

Seasonal intelligence Month-of-year Download MP4

Melbourne breathes: 15-minute time-bin rhythm

A 24-hour breathing-style animation of the city’s 15-minute traffic rhythm, from overnight quiet through commuter peaks and evening release.

Time-bin profile City pulse Download MP4

Top 100 OOH / SCATS reveal

A reveal-style animation of the highest-value SCATS traffic nodes and OOH opportunity locations, designed for commercial and media storytelling.

Top 100 sites OOH opportunity Download MP4

COVID recovery map animation

A cinematic citywide map animation showing Melbourne traffic moving from the 2019 baseline through lockdown shock, disruption, recovery, recent normal and the 2025 busiest detected day.

COVID recovery City map Download MP4

COVID 24-hour heartbeat

An animated 24-hour curve comparison showing how Melbourne’s daily traffic rhythm collapsed during lockdown and then rebuilt across later recovery periods.

24-hour rhythm Recovery curve Download MP4

COVID shock vs recovery scatter

A site-level resilience animation revealing which SCATS nodes collapsed hardest during lockdown and which later over-recovered beyond the 2019 baseline.

Site resilience Shock vs recovery Download MP4

Top 30 COVID traffic collapse leaderboard

An animated leaderboard of the SCATS sites with the largest absolute traffic-volume losses on the 2020 lockdown comparison day versus the 2019 baseline.

Top 30 collapse Site ranking Download MP4

Top 30 post-COVID growth leaderboard

An animated leaderboard showing which SCATS sites exceeded their 2019 baseline most strongly on the 2025 busiest detected comparison day.

Post-COVID growth Top 30 sites Download MP4

COVID traffic heartbeat heatmap reveal

A row-by-row reveal of the COVID comparison heatmap, showing how the 15-minute daily traffic signature changed from baseline to lockdown, recovery and overperformance.

Heartbeat heatmap COVID history Download MP4
Why this matters: The animations make the SCATS archive easier for journalists, policy readers, advertisers and the public to understand. Instead of presenting only numbers, the page now shows Melbourne as a living movement system across weekly heartbeat behaviour, full-network coverage, daily volume, seasonal behaviour, time-of-day rhythm, COVID collapse/recovery history and commercial-location dimensions.

Melbourne Suburb Traffic Intensity Map

The Melbourne Suburb Traffic Intensity Map adds a suburb-level visual layer to the SCATS project. Instead of only reading suburb tables and Top 100 rankings, users can now explore Melbourne geographically and see how traffic pressure varies across suburbs.

Red, yellow and green suburb traffic pressure Interactive suburb polygons joined to cleaned SCATS traffic-pressure scores

What it shows

Suburbs are colour-coded by observed traffic pressure so people can quickly see high, medium and lower traffic-intensity areas.

How it was built

Cleaned SCATS suburb traffic-pressure scores were joined to suburb-level GeoJSON boundary polygons and rendered as an interactive map layer.

Why it matters

The Top 100 list shows rankings; the map shows geography. It helps people visually understand where traffic pressure clusters across Melbourne.

Interpretation note: This is a signalised-traffic pressure map, not a count of every vehicle on every street. It is strongest where SCATS signal coverage is good. A suburb with fewer monitored signalised intersections may appear quieter than local experience suggests.

Melbourne Commute + Traffic Pressure Map

The Melbourne Commute + Traffic Pressure Map combines modelled CBD commute estimates with the existing SCATS suburb traffic-pressure layer. It is designed for people asking practical questions such as: how bad is my commute, how much worse is peak hour, and how does my suburb compare with nearby suburbs?

Commute estimates

Suburb-centroid estimates include AM peak commute to the CBD, PM return from the CBD, off-peak travel time and peak-delay penalty.

Traffic pressure

The commute layer is combined with SCATS suburb traffic-pressure scores, so the map does not only show travel time — it also reflects local traffic load.

Comparison metrics

The map supports practical comparison through traffic pain index and low-traffic / high-access scoring.

Interpretation note: Commute times are modelled suburb-centroid drive-time estimates. They are useful for comparing suburbs, but they are not exact driveway-to-work predictions. Individual addresses, incidents, roadworks and daily conditions will vary.

Melbourne Commute + Traffic Pressure Graphs — Version 2

These Version 2 graphs summarise the suburb commute intelligence output using a metro-style filter. They show the fastest and slowest CBD commutes, PM return pressure, peak-delay penalties, traffic pain, low-traffic / high-access scoring, commute-time distributions and scatter plots connecting commute time, traffic pressure and route distance.

Version 2 filter note: Public charts are metro-filtered by default to avoid regional Victorian localities appearing in Melbourne suburb rankings. The commute times are modelled suburb-centroid estimates and should be used for suburb comparison, not exact address-level trip prediction.

Graph 1 — Fastest suburbs to the CBD, AM peak

Graph 1 — Fastest suburbs to the CBD, AM peak

This graph shows the fastest modelled morning peak CBD commutes from suburb centroids. The inner suburbs dominate: Carlton, East Melbourne, Southbank, Fitzroy, Melbourne, South Wharf, Docklands and North Melbourne all sit close to the CBD and perform strongly.

Modelled suburb-centroid drive-time estimates; individual addresses and daily conditions will vary.

Graph 2 — Slowest suburbs to the CBD, AM peak

Graph 2 — Slowest suburbs to the CBD, AM peak

This is where the commute-pressure story becomes very clear. Clyde, Cranbourne East, Clyde North, Pakenham, Officer, Beaconsfield, Berwick and surrounding growth-corridor suburbs appear near the top.

The south-east growth corridor stands out strongly in the modelled AM peak commute data.

Graph 3 — Slowest CBD return commutes, PM peak

Graph 3 — Slowest CBD return commutes, PM peak

This graph looks at the afternoon return trip from the CBD back to each suburb. The outer growth areas again show up strongly, especially Clyde, Doreen, Wallan, Coldstream, Pakenham, Mernda, Donnybrook and the Cranbourne/Clyde corridor.

Commute pressure is not just about getting into the city — the trip home matters too.

Graph 4 — Biggest CBD peak-delay penalty

Graph 4 — Biggest CBD peak-delay penalty

This graph compares peak commute time with off-peak travel time. The higher the suburb appears, the more peak hour adds to the trip.

Clyde, Clyde North, Cranbourne East, Cranbourne North, Officer, Beaconsfield and Narre Warren South stand out as areas where peak conditions add substantial time.

Graph 5 — Best low-traffic / high-access score suburbs

Graph 5 — Best low-traffic / high-access score suburbs

This score combines better CBD access, lower SCATS suburb traffic pressure and lower peak delay. South Wharf, Cremorne, Princes Hill, Kooyong, Seddon, Burnley, Tottenham, Ashburton, Kingsville and Carlton North perform well on this combined score.

This does not mean a suburb is silent or free of traffic; it means it scores well on this particular low-traffic / high-access comparison.

Graph 6 — Highest traffic pain index suburbs

Graph 6 — Highest traffic pain index suburbs

This is one of the most important graphs. The traffic pain index combines local traffic pressure, slower CBD commute time and/or larger peak delay. Pakenham, Cranbourne, Cranbourne East, Cranbourne West, Berwick, Cranbourne North, Clyde North and Narre Warren South are all near the top.

The south-east growth corridor is very clearly visible here.

Graph 7 — Distribution of Melbourne suburb CBD commute times

Graph 7 — Distribution of Melbourne suburb CBD commute times

This graph shows the overall spread of modelled AM peak CBD commute times across the metro-filtered suburbs. The median is about 38 minutes, while the 90th percentile is about 57 minutes.

Rather than only looking at individual suburbs, this shows the overall shape of Melbourne’s CBD commute burden.

Graph 8 — Distribution of CBD peak-delay penalties

Graph 8 — Distribution of CBD peak-delay penalties

This graph shows how much extra time peak hour adds compared with off-peak travel. The median peak-delay penalty is about 5.7 minutes, while the 90th percentile is about 10.7 minutes.

Some suburbs are only slightly affected by peak hour, while others face a much larger delay penalty.

Graph 9 — Suburb traffic-pressure category distribution

Graph 9 — Suburb traffic-pressure category distribution

This graph counts how many suburbs fall into each SCATS traffic-pressure category. It shows that Melbourne is not evenly loaded: some suburbs sit in lower or moderate traffic-pressure bands, while a smaller but important group falls into high, very high and extreme traffic-pressure categories.

This is based on cleaned SCATS suburb traffic-pressure data.

Graph 10 — Best low-traffic / high-access suburbs under 45 minutes to the CBD

Graph 10 — Best low-traffic / high-access suburbs under 45 minutes to the CBD

This is a more practical version of the low-traffic / high-access score because it only includes suburbs under 45 minutes to the CBD in the modelled AM peak estimate.

Useful for people asking: where could I live with decent CBD access but less traffic pressure?

Graph 11 — Highest average-speed CBD commute routes, metro filtered

Graph 11 — Highest average-speed CBD commute routes, metro filtered

This graph shows AM peak route distance divided by modelled AM peak travel time. Outer suburbs with more freeway or arterial-style access can sometimes show higher average speeds, even if the total trip is longer.

This is not saying these are the best commutes — it shows route efficiency, not total convenience.

Graph 12 — Peak versus off-peak CBD commute comparison

Graph 12 — Peak versus off-peak CBD commute comparison

Each dot is a suburb. The further above the diagonal a suburb sits, the worse the AM peak commute is compared with off-peak.

The labelled suburbs near the upper right are where longer commute times and larger peak delays combine.

Graph 13 — Local traffic pressure versus CBD commute time

Graph 13 — Local traffic pressure versus CBD commute time

This graph combines two different things: local SCATS suburb traffic pressure and modelled AM peak CBD commute time. The most interesting suburbs are toward the upper right, where high local traffic pressure and longer CBD commute times combine.

That is where traffic pain becomes more than just distance from the city.

Graph 14 — CBD commute distance versus travel time

Graph 14 — CBD commute distance versus travel time

This graph shows the relationship between route distance and modelled AM peak travel time. Distance matters, but it is not the whole story.

Some suburbs at similar distances can have noticeably different travel times depending on road access, congestion, route structure and peak-hour delay.

Melbourne’s Top 100 Busiest Traffic Suburbs

A ranked suburb-level view of Melbourne traffic pressure, built from cleaned SCATS vehicle movement data. This section sits alongside the suburb profile search above: search for your suburb, then use this Top 100 table to see how it compares against Melbourne’s busiest traffic locations.

100 suburbs ranked in this table
328,222,558,357 vehicle movements across the Top 100
2,431 SCATS sites counted across these suburbs
Melbourne #1 suburb · 19,588,962,503 movements

Ranking basis: total vehicle movements aggregated by geocoded suburb. This is a traffic-load ranking, not a population ranking. The busiest-site column identifies the highest-volume SCATS site contributing to each suburb’s total.

Rank Suburb Sites Total movements Millions Avg / site Busiest SCATS site Links
#1 Melbourne Postcodes: 3000, 3002, 3004, 3139, 3141, 3168, 3205, 3206, 3337, 3429, 3751, 3757, 3775, 3777, 3797, 3799, 3812, 3915, 3980, 3981, 3984 170 19,588,962,503 19,589.0M 115,229,191 Princes Highway East / ALBERT SCATS 2405 · 518.6M Map Profile PDF
#2 Preston Postcodes: 3072, 3073 49 7,185,511,879 7,185.5M 146,643,099 Bell / High SCATS 3060 · 492.4M Map Profile PDF
#3 Bundoora Postcodes: 3083 28 6,142,552,470 6,142.6M 219,376,873 Plenty / Grimshaw SCATS 3735 · 407.5M Map Profile PDF
#4 Dandenong Postcodes: 3173, 3175 41 6,004,722,890 6,004.7M 146,456,655 Princes Highway East (LONSDALE) / WALKER SCATS 195 · 380.4M Map Profile PDF
#5 Richmond Postcodes: 3121 39 5,822,958,749 5,823.0M 149,306,634 Hoddle / Albert / Elizabeth SCATS 3386 · 544.0M Map Profile PDF
#6 Malvern East Postcodes: 3145, 3148 34 5,714,160,967 5,714.2M 168,063,557 Monash / Warrigal SCATS 3681 · 406.6M Map Profile PDF
#7 Ringwood Postcodes: 3134 36 5,536,913,940 5,536.9M 153,803,165 Maroondah / Mt Dandenong SCATS 126 · 332.8M Map Profile PDF
#8 St Kilda Postcodes: 3182, 3184 27 4,967,931,033 4,967.9M 183,997,445 Nepean / Fitzroy / Wellington SCATS 2302 · 364.9M Map Profile PDF
#9 Footscray Postcodes: 3011, 3012 43 4,939,975,838 4,940.0M 114,883,159 WESTERN Highway / TIERNAN / HOADLEY SCATS 2601 · 290.4M Map Profile PDF
#10 Epping Postcodes: 3076 44 4,925,988,433 4,926.0M 111,954,282 Hume Freeway / Cooper SCATS 2815 · 286.8M Map Profile PDF
#11 Collingwood Postcodes: 3066, 3067 20 4,699,505,268 4,699.5M 234,975,263 HODDLE near STUDLEY (NORTHBOUND) SCATS 3376 · 488.9M Map Profile PDF
#12 Coburg Postcodes: 3058 32 4,621,238,506 4,621.2M 144,413,703 Bell / Nicholson / Elizabeth SCATS 3056 · 354.9M Map Profile PDF
#13 Carlton Postcodes: 3052, 3053, 3065 39 4,618,683,374 4,618.7M 118,427,778 PRINCES near CANNING SCATS 4415 · 674.5M Map Profile PDF
#14 Kew Postcodes: 3101, 3102, 3103 34 4,439,113,684 4,439.1M 130,562,167 CHANDLER Highway / EASTERN Freeway WB SCATS 2821 · 278.6M Map Profile PDF
#15 Camberwell Postcodes: 3124, 3125 32 4,432,781,691 4,432.8M 138,524,427 Toorak / Summerhill / Camberwell SCATS 4046 · 281.2M Map Profile PDF
#16 Clayton Postcodes: 3168, 3169 26 4,393,127,179 4,393.1M 168,966,429 Princes Highway East / SPRINGVALE BYPASS / Westall SCATS 948 · 409.4M Map Profile PDF
#17 Dandenong South Postcodes: 3175, 3177 33 4,368,265,891 4,368.3M 132,371,693 Dandenong Southern Bypass / Dand_Franston SCATS 1121 · 292.1M Map Profile PDF
#18 Frankston Postcodes: 3199 33 4,314,892,772 4,314.9M 130,754,326 Cranbourne-Frankston / Penlink SCATS 1302 · 282.4M Map Profile PDF
#19 North Melbourne Postcodes: 3051, 3052 36 4,228,967,317 4,229.0M 117,471,314 Flemington / Racecourse / Elliot SCATS 4461 · 372.2M Map Profile PDF
#20 Cheltenham Postcodes: 3192, 3194, 3202 27 4,221,161,101 4,221.2M 156,339,300 Nepean / Bay / Karen SCATS 2326 · 444.6M Map Profile PDF
#21 Springvale Postcodes: 3171 28 4,150,689,579 4,150.7M 148,238,913 Princes Highway East / SPRINGVALE SCATS 185 · 323.7M Map Profile PDF
#22 Geelong Postcodes: 3218, 3220 43 4,001,287,200 4,001.3M 93,053,190 Corio-Waurn Ponds(Latrobe / Ryrie / Aberdeen SCATS 5018 · 239.7M Map Profile PDF
#23 Mount Waverley Postcodes: 3125, 3149, 3168 35 3,997,594,626 3,997.6M 114,216,989 BLACKBURN near MATTHEW SCATS 544 · 264.5M Map Profile PDF
#24 Keysborough Postcodes: 3173, 3195 27 3,978,707,799 3,978.7M 147,359,548 Springvale / Keylana SCATS 3151 · 304.0M Map Profile PDF
#25 West Melbourne Postcodes: 3003, 3051 32 3,922,671,355 3,922.7M 122,583,479 King / Dudley SCATS 4517 · 237.7M Map Profile PDF
#26 East Melbourne Postcodes: 3000, 3002 27 3,880,788,560 3,880.8M 143,732,909 Hoddle / Victoria SCATS 3385 · 449.2M Map Profile PDF
#27 Hoppers Crossing Postcodes: 3029 30 3,876,449,149 3,876.4M 129,214,971 Derrimut / Hogans SCATS 5313 · 276.3M Map Profile PDF
#28 South Yarra Postcodes: 3141, 3181 26 3,859,035,667 3,859.0M 148,424,448 TOORAK near OSBORNE SCATS 4742 · 411.1M Map Profile PDF
#29 Werribee Postcodes: 3024, 3029, 3030 43 3,852,248,367 3,852.2M 89,587,171 Phw / Old Geelong SCATS 5003 · 295.4M Map Profile PDF
#30 Berwick Postcodes: 3806, 3978 28 3,816,591,157 3,816.6M 136,306,827 Clyde / Greaves / O'Shea SCATS 508 · 271.9M Map Profile PDF
#31 Nunawading Postcodes: 3131, 3132 14 3,641,361,550 3,641.4M 260,097,253 SPRINGVALE near LAUGHLIN AVE SCATS 416 · 506.0M Map Profile PDF
#32 Wantirna South Postcodes: 3152 23 3,640,757,530 3,640.8M 158,293,805 BURWOOD Highway / STUD SCATS 170 · 253.1M Map Profile PDF
#33 Glen Waverley Postcodes: 3133, 3150, 3151 22 3,575,790,537 3,575.8M 162,535,933 Springvale / The Glen Shopping SCATS 408 · 351.7M Map Profile PDF
#34 Hawthorn Postcodes: 3122 26 3,570,545,971 3,570.5M 137,328,691 Monash / Toorak / Auburn SCATS 2843 · 410.2M Map Profile PDF
#35 Cranbourne Postcodes: 3977 19 3,559,909,922 3,559.9M 187,363,680 SOUTH GIPPSLAND Highway between STATION / LOCH SCATS 1156 · 377.1M Map Profile PDF
#36 South Melbourne Postcodes: 3006, 3205 27 3,533,428,909 3,533.4M 130,867,737 Princes Highway East / PARK SCATS 2404 · 560.2M Map Profile PDF
#37 Reservoir Postcodes: 3073, 3074 23 3,496,846,044 3,496.8M 152,036,784 High / Spring / Cheddar SCATS 3740 · 308.7M Map Profile PDF
#38 Bentleigh East Postcodes: 3165, 3167 21 3,409,936,545 3,409.9M 162,377,930 Warrigal / Links Estate Access SCATS 1359 · 547.0M Map Profile PDF
#39 Southbank Postcodes: 3000, 3006 25 3,379,813,182 3,379.8M 135,192,527 Montague / Normanby / Munro SCATS 3541 · 329.0M Map Profile PDF
#40 Docklands Postcodes: 3006, 3008 31 3,341,386,841 3,341.4M 107,786,672 WESTGATE Freeway WB / MONTAGUE SCATS 4901 · 325.6M Map Profile PDF
#41 Campbellfield Postcodes: 3048, 3061 15 3,303,703,686 3,303.7M 220,246,912 Sydney / Mahoneys / Camp SCATS 2157 · 389.7M Map Profile PDF
#42 Doncaster Postcodes: 3108 20 3,224,577,457 3,224.6M 161,228,872 Eastern Freeway / Doncaster SCATS 2828 · 283.7M Map Profile PDF
#43 Mulgrave Postcodes: 3150, 3170 18 3,206,797,145 3,206.8M 178,155,396 Springvale / Wellington SCATS 432 · 341.3M Map Profile PDF
#44 Rowville Postcodes: 3178 17 3,111,874,499 3,111.9M 183,051,441 Streetud / Bergins SCATS 2017 · 317.6M Map Profile PDF
#45 St Albans Postcodes: 3021 23 3,073,123,297 3,073.1M 133,614,056 Furlong / Street Albans SCATS 4935 · 212.1M Map Profile PDF
#46 Broadmeadows Postcodes: 3047 21 3,003,917,709 3,003.9M 143,043,700 CAMP near JOSEPH SCATS 3984 · 263.2M Map Profile PDF
#47 Thomastown Postcodes: 3074 19 3,001,484,597 3,001.5M 157,972,873 Metropolitan Ring Road / Dalton SCATS 3744 · 331.8M Map Profile PDF
#48 Croydon Postcodes: 3136, 3138 21 2,982,017,352 2,982.0M 142,000,826 Mt Dandenong / Bayswater / Wicklow SCATS 634 · 313.6M Map Profile PDF
#49 Northcote Postcodes: 3070, 3078 19 2,952,074,800 2,952.1M 155,372,357 Street Georges / Merri / Charles SCATS 3671 · 375.7M Map Profile PDF
#50 Brighton East Postcodes: 3162, 3187 16 2,907,895,563 2,907.9M 181,743,472 Nepean / Cummins / Patterson SCATS 2337 · 403.4M Map Profile PDF
#51 Deer Park Postcodes: 3021, 3023 15 2,791,263,308 2,791.3M 186,084,220 WESTERN Highway / STATION SCATS 2614 · 387.5M Map Profile PDF
#52 Narre Warren Postcodes: 3805 17 2,774,370,752 2,774.4M 163,198,279 Princes Highway East / NARRE WARREN-CRANBOURNE SCATS 604 · 340.7M Map Profile PDF
#53 Fitzroy Postcodes: 3053, 3065 17 2,744,956,477 2,745.0M 161,468,028 Eastern / Nicholson / Princes SCATS 2100 · 404.1M Map Profile PDF
#54 Caulfield North Postcodes: 3161, 3183 20 2,690,064,224 2,690.1M 134,503,211 Princes Highway East / NORMANBY / STATION SCATS 2416 · 391.2M Map Profile PDF
#55 Truganina Postcodes: 3029 41 2,679,578,012 2,679.6M 65,355,561 Palmers / Leakes SCATS 5279 · 177.3M Map Profile PDF
#56 Fitzroy North Postcodes: 3068 19 2,679,033,049 2,679.0M 141,001,739 EASTERN Highway / QUEENS / BRUNSWICK SCATS 2101 · 497.4M Map Profile PDF
#57 Greensborough Postcodes: 3088 14 2,613,905,694 2,613.9M 186,707,549 MRR / GREENSBOROUGH Highway SCATS 3357 · 495.7M Map Profile PDF
#58 Sunshine Postcodes: 3020 23 2,591,086,350 2,591.1M 112,655,928 WESTERN Highway / HARVESTER SCATS 2641 · 241.6M Map Profile PDF
#59 Wantirna Postcodes: 3152 12 2,541,760,752 2,541.8M 211,813,396 BORONIA near AMESBURY & ROXBURGH SCATS 1144 · 379.9M Map Profile PDF
#60 Mentone Postcodes: 3193, 3194, 3195 18 2,532,580,267 2,532.6M 140,698,903 Nepean / Warrigal / Balcombe SCATS 2329 · 415.1M Map Profile PDF
#61 Point Cook Postcodes: 3030 28 2,520,122,492 2,520.1M 90,004,374 POINT COOK near JAMIESON SCATS 3088 · 339.5M Map Profile PDF
#62 Burwood Postcodes: 3125 17 2,458,014,151 2,458.0M 144,589,067 BURWOOD Highway near PLC SCATS 2003 · 327.1M Map Profile PDF
#63 Thornbury Postcodes: 3071 16 2,451,633,713 2,451.6M 153,227,107 Street Georges / Normanby SCATS 4660 · 256.3M Map Profile PDF
#64 Glen Iris Postcodes: 3124, 3146 18 2,394,310,776 2,394.3M 133,017,265 Monash / Burke SCATS 2845 · 297.3M Map Profile PDF
#65 Hawthorn East Postcodes: 3123, 3126 18 2,391,343,206 2,391.3M 132,852,400 Burke / Barkers / Mont Albert SCATS 4035 · 478.7M Map Profile PDF
#66 Essendon Postcodes: 3040 18 2,387,046,448 2,387.0M 132,613,691 MT ALEXANDER near LINCOLN SCATS 3519 · 513.9M Map Profile PDF
#67 Shepparton Postcodes: 3630 35 2,372,969,977 2,373.0M 67,799,142 MIDLAND Highway / ST GEORGES SCATS 6093 · 123.3M Map Profile PDF
#68 Craigieburn Postcodes: 3064 30 2,260,144,313 2,260.1M 75,338,143 Hume / Craigieburn SCATS 2185 · 279.1M Map Profile PDF
#69 Prahran Postcodes: 3142, 3143, 3181 15 2,243,373,402 2,243.4M 149,558,226 Princes Highway East near CLOSEBURN SCATS 2985 · 431.2M Map Profile PDF
#70 Bendigo Postcodes: 3550 25 2,237,848,499 2,237.8M 89,513,939 Mc Ivor / View / Mitchell SCATS 6200 · 236.7M Map Profile PDF
#71 Elwood Postcodes: 3184 12 2,204,322,856 2,204.3M 183,693,571 Ormond Esp / Street Kilda / Head SCATS 3022 · 352.3M Map Profile PDF
#72 Vermont South Postcodes: 3133 9 2,186,022,144 2,186.0M 242,891,349 BURWOOD Highway / STANLEY / FORTESCUE SCATS 538 · 428.6M Map Profile PDF
#73 Port Melbourne Postcodes: 3207 29 2,120,150,971 2,120.2M 73,108,654 Todd Off Ramp / Prohasky / Service Centre SCATS 2898 · 170.7M Map Profile PDF
#74 Brunswick Postcodes: 3052, 3056 16 2,117,711,518 2,117.7M 132,356,969 Sydney / Brunswick SCATS 3112 · 265.2M Map Profile PDF
#75 Sunshine North Postcodes: 3020 12 2,074,049,041 2,074.0M 172,837,420 Wrr / Sunshine / Mcintyre SCATS 2628 · 418.5M Map Profile PDF
#76 Taylors Lakes Postcodes: 3038 12 2,063,210,412 2,063.2M 171,934,201 MELTON Highway / SUNSHINE SCATS 2701 · 402.9M Map Profile PDF
#77 Abbotsford Postcodes: 3067, 3121 15 2,062,332,633 2,062.3M 137,488,842 EASTERN Freeway OFF RAMP / HODDLE SCATS 3380 · 638.2M Map Profile PDF
#78 Belmont Postcodes: 3216 15 2,035,585,307 2,035.6M 135,705,687 Corio-Waurn Pond(Settlement / Barwon Heads SCATS 5079 · 322.6M Map Profile PDF
#79 Mill Park Postcodes: 3082 15 2,033,401,332 2,033.4M 135,560,088 Plenty / Childs SCATS 2763 · 257.2M Map Profile PDF
#80 Altona North Postcodes: 3025 18 2,030,740,835 2,030.7M 112,818,935 Millers / Duosa / Marigold SCATS 2882 · 237.3M Map Profile PDF
#81 Moonee Ponds Postcodes: 3039, 3040 16 1,992,631,693 1,992.6M 124,539,480 Mt Alexander / Kellaway / Taylors SCATS 3511 · 298.8M Map Profile PDF
#82 Burwood East Postcodes: 3151 12 1,986,078,381 1,986.1M 165,506,531 BURWOOD Highway / BLACKBURN SCATS 162 · 254.3M Map Profile PDF
#83 Doncaster East Postcodes: 3106, 3109 16 1,950,810,462 1,950.8M 121,925,653 DONCASTER near LEEDS SCATS 332 · 259.7M Map Profile PDF
#84 Ferntree Gully Postcodes: 3156 15 1,949,995,055 1,950.0M 129,999,670 BURWOOD Highway / DORSET SCATS 177 · 276.8M Map Profile PDF
#85 Surrey Hills Postcodes: 3124, 3125, 3127 15 1,921,294,120 1,921.3M 128,086,274 CANTERBURY near BALMORAL SCATS 2011 · 240.1M Map Profile PDF
#86 South Morang Postcodes: 3076, 3082, 3752 15 1,882,089,131 1,882.1M 125,472,608 Plenty / Mcdonalds / Gorge SCATS 3946 · 230.6M Map Profile PDF
#87 Balwyn North Postcodes: 3103, 3104 16 1,850,283,676 1,850.3M 115,642,729 Eastern Freeway / Bulleen / Thompsons SCATS 2827 · 370.6M Map Profile PDF
#88 Brunswick East Postcodes: 3056, 3057 16 1,833,717,133 1,833.7M 114,607,320 Brunswick / Lygon SCATS 3113 · 191.2M Map Profile PDF
#89 Pakenham Postcodes: 3809, 3810 22 1,832,053,192 1,832.1M 83,275,145 Cardinia / Henry / Rix SCATS 1211 · 175.4M Map Profile PDF
#90 Brooklyn Postcodes: 3012 11 1,803,182,288 1,803.2M 163,925,662 Phw / Federation Trail SCATS 5296 · 382.0M Map Profile PDF
#91 Ascot Vale Postcodes: 3032, 3039 20 1,794,985,282 1,795.0M 89,749,264 Mt Alexander / Ormond / Maribyrnong SCATS 4206 · 175.1M Map Profile PDF
#92 Fawkner Postcodes: 3060 7 1,794,950,466 1,795.0M 256,421,495 Sydney / Wrr SCATS 2173 · 416.4M Map Profile PDF
#93 Heidelberg Postcodes: 3084 10 1,784,746,677 1,784.7M 178,474,667 Banksia / Lwr Heidelberg SCATS 3360 · 452.4M Map Profile PDF
#94 Ballarat Central Postcodes: 3350 24 1,777,165,627 1,777.2M 74,048,567 Streeturt / Drummond SCATS 5820 · 219.5M Map Profile PDF
#95 Parkville Postcodes: 3052 13 1,767,986,408 1,768.0M 135,998,954 Royal / Cemetery / Macarthur SCATS 4384 · 319.0M Map Profile PDF
#96 Bayswater North Postcodes: 3153 9 1,755,964,470 1,756.0M 195,107,163 Dorset / Canterbury SCATS 631 · 253.2M Map Profile PDF
#97 Scoresby Postcodes: 3179 7 1,742,899,276 1,742.9M 248,985,610 Ferntree Gully / Streetud SCATS 456 · 335.6M Map Profile PDF
#98 Box Hill Postcodes: 3128 11 1,724,204,278 1,724.2M 156,745,843 Maroondah / Streetation SCATS 2206 · 271.2M Map Profile PDF
#99 Brighton Postcodes: 3186, 3187 19 1,689,496,552 1,689.5M 88,920,871 Nepean / Bay / Milroy / Hampton SCATS 2317 · 251.2M Map Profile PDF
#100 Tarneit Postcodes: 3029 26 1,684,369,199 1,684.4M 64,783,430 Derrimut / Leakes SCATS 5235 · 180.2M Map Profile PDF

HTML profile links use the existing suburbtraffic/ report folder; PDF links use suburbtraffic/pdfs/ and the same suburb-profile naming convention.

Melbourne Suburbs Where Traffic Has Gotten Worse Since 2014

A suburb-level growth view built by joining monthly SCATS site totals to the suburb lookup layer. The headline comparison uses full-year 2014 vs 2025. The 2026 figure is shown only as Jan–Apr year-to-date monitoring, not as a full-year comparison.

Loading… Melbourne metro suburbs analysed
Loading… biggest absolute increase
Loading… extra movements, 2014 to 2025
Loading… highest same-site percentage growth

The absolute-growth table answers: where has the total measured traffic burden grown most? The same-site table is more conservative because it only compares SCATS sites present in both 2014 and 2025.

Important caveat: raw suburb growth can be affected by new SCATS sites being added over time. Use the same-site table when you want the cleaner like-for-like comparison.
Loading suburb traffic growth data…

CSV source expected at: downloads/melbourne_metro_suburb_traffic_growth_2014_2025_with_2026_ytd.csv. HTML profile links use suburbtraffic/; PDF links use suburbtraffic/pdfs/.

Melbourne Traffic Pressure Index by Suburb

A combined suburb ranking showing where traffic is already heavy and still getting worse. The index blends 2025 traffic burden, absolute growth from 2014 to 2025, and same-site growth to identify the suburbs under the strongest measured traffic pressure.

Loading… Melbourne metro suburbs scored
Loading… #1 pressure suburb
Loading… highest pressure score
Loading… suburbs in extreme pressure category
Why this matters The busiest-suburbs table shows current traffic load. The growth table shows change over time. This index combines both to identify where traffic is already heavy and still worsening.
Index formula 45% current 2025 traffic burden percentile + 35% absolute growth percentile + 20% same-site growth percentile, adjusted by a confidence multiplier.
Interpretation note: this is a ranking index, not a government congestion model. It is designed to surface public-interest suburb pressure signals from the cleaned SCATS movement layer.
Rank Suburb Score Category / confidence 2025 movements Growth since 2014 % growth Same-site growth Sites 2026 YTD Links
Loading Melbourne Traffic Pressure Index…

CSV source expected at: downloads/melbourne_traffic_pressure_index_by_suburb.csv. HTML profile links use suburbtraffic/; PDF links use suburbtraffic/pdfs/.

Important Intersection Intelligence

The older “Top 50” concept has been consolidated into the richer intersection intelligence already present on the page. Importance is now assessed using multiple lenses: cumulative movement, busiest-site ranking, Top 20 mapping, full SCATS network coverage, corridor dominance, site-month volatility and OOH opportunity value.

How Melbourne Traffic Actually Behaves — Time-Bin Behavioural Analytics

📄 Export Behavioural Analytics Section as PDF Print-ready section using completed 96-bin time-of-day results.

New behavioural layer: the completed time-bin run does more than identify the busiest and quietest 15-minute intervals. It now allows the page to explain how Melbourne accumulates traffic during the day, how long the network stays near capacity, how sharply it ramps up and drops off, and whether peak demand is scattered or tightly concentrated.

The key finding is that Melbourne is not merely a short “rush-hour” city. It behaves like a sustained high-volume plateau system with a concentrated afternoon pressure spike embedded inside it.

Peak pressure: 17:15 Quiet baseline: 03:00 >70% of peak for 11.2 hours Morning ramp: 5.3× Top 10 bins: 15:15–17:30

50% of Daily Traffic Reached By

13:45

75% of Daily Traffic Reached By

17:15

Traffic Completed by 5PM

73.8%

Traffic Completed by 7PM

86.3%

Afternoon vs Morning Peak

1.18×

Top 10 Bin Cluster Span

2.2 hrs

1. Melbourne Uses Most of Its Daily Traffic Before Evening

By 5PM, approximately 73.8% of daily traffic has already occurred. By 7PM, the figure rises to about 86.3%.

2. The Day Is Plateau-Driven, Not Just Peak-Driven

The network remains above 70% of peak for about 11.2 hours, above 80% for 8.0 hours, and above 90% for 3.2 hours.

3. Afternoon Pressure Is Structurally Higher

The afternoon pressure window is about 1.18× the morning-window peak, showing that the PM period carries stronger sustained load than the morning build-up.

4. The Busiest Intervals Are Tightly Clustered

The top 10 busiest 15-minute intervals cluster between 15:15 and 17:30, making the strongest exposure period highly concentrated and commercially useful.

Behavioural Analytics Charts

Cumulative Daily Traffic Curve

Shows how quickly Melbourne accumulates its daily road-network activity and when major cumulative thresholds are reached.

Cumulative daily Melbourne SCATS traffic curve showing traffic share by time of day
Interpretation: this is the simplest public-facing way to show how quickly Melbourne “uses up” the day’s traffic volume.

Peak Window Share

Compares morning peak, midday plateau, afternoon peak, and overnight baseline as shares of total daily traffic volume.

Peak window share chart for Melbourne daily SCATS traffic

Morning vs Afternoon Traffic Shape

Compares equal six-hour windows to show the difference between the morning build-up and the stronger afternoon pressure pattern.

Morning versus afternoon Melbourne SCATS traffic shape comparison

How Long Melbourne Operates Near Capacity

Quantifies how many hours per day the network stays above 70%, 80%, and 90% of its maximum daily load.

Near capacity plateau duration chart for Melbourne SCATS traffic

Morning Ramp-Up and Evening Drop-Off

Shows how fast the network wakes up, reaches the afternoon high-pressure period, and then releases load into the evening.

Morning ramp-up and evening drop-off chart for Melbourne SCATS traffic

Top 10 Busiest Bins Cluster Analysis

Shows that the strongest 15-minute exposure intervals are not scattered through the day; they are concentrated in a narrow afternoon window.

Top 10 busiest Melbourne SCATS time bins cluster analysis
Commercial interpretation: this gives OOH and media planners a highly specific high-exposure window, rather than a generic “PM peak” label.
Story interpretation: Melbourne’s signalized-road activity is best described as a long high-volume operating plateau with an embedded afternoon pressure spike. The city does not simply “peak”; it stays busy for much of the business day, then concentrates its strongest 15-minute intervals into a narrow late-afternoon window.

Derived Behavioural Outputs

Output Path Status
Behaviour metrics CSV charts/time_bin_behaviour_v2/time_bin_behaviour_metrics.csv Generated
Behaviour summary JSON charts/time_bin_profile/time_bin_behaviour_summary.json Generated
Source CSV time_bin_profile.csv Complete 96-bin analytical source
Source JSON time_bin_profile_final.json 148 / 148 months complete

Production Time-of-Day Traffic Profile — When Melbourne Moves

Completed 96-bin daily rhythm model

The completed time-bin workflow now gives the page a full 15-minute profile of Melbourne's signalized road network across the archive. The strongest average daily interval is 17:15, while the quietest interval is 03:00. This turns the archive from a set of totals into a readable daily movement pattern: overnight quiet, morning build, business-day plateau, afternoon peak, and evening decline.

Red = peak pressure Orange = transition Yellow = daytime plateau Green = quiet network Blue = structural analysis Purple = anomaly / shifted peak

Archive Coverage

2014-01-01 → 2026-04-07

Months Completed

148 / 148

15-Minute Rows

14,112

Distinct Days Loaded

4,437

Busiest Bin

17:15

Peak Avg / Day

2,283,898

Quietest Bin

03:00

Peak vs Quiet

~15.1×

Public-facing interpretation: Melbourne does not simply have a generic “afternoon peak”. In this archive, the strongest network-wide 15-minute point is precisely 5:15pm to 5:30pm. The quietest point is around 3:00am to 3:15am. This is a simple, quotable finding for journalists and a direct exposure-timing signal for OOH media.

Main Chart — Melbourne Traffic Daily Rhythm

The headline chart showing the full 24-hour movement curve, with the 17:15 peak and 03:00 quietest point annotated.

Melbourne SCATS daily traffic rhythm 15-minute profile showing 17:15 peak and 03:00 quietest interval

Production Time-Bin Chart Suite

Day Segments

The same 96-bin profile coloured by behavioural period: overnight quiet, morning build, daytime plateau, afternoon peak, and evening decline.

Melbourne traffic day segments chart coloured by behavioural period

Broad Day Period Totals

Aggregated volume by broad traffic period, showing how much of the archive sits in each part of the day.

Melbourne traffic volume by broad day period

Top 24 Busiest 15-Minute Bins

Red-ranked chart of the busiest 15-minute intervals, making the afternoon peak cluster visually obvious.

Top 24 busiest Melbourne SCATS 15-minute traffic bins

Top 24 Quietest 15-Minute Bins

Green-ranked chart of the quietest intervals, confirming the overnight low-flow envelope around 03:00.

Top 24 quietest Melbourne SCATS 15-minute traffic bins

Peak vs Quietest Network Load

A simple media-facing comparison showing the peak interval is about 15.1 times the quietest interval.

Melbourne SCATS peak versus quietest network load chart

Monthly Peak-Time Stability

Shows whether the peak month-by-month stayed aligned with the dominant 17:15 archive peak or shifted to nearby bins.

Melbourne SCATS monthly peak time stability chart

What this now answers

  • When does Melbourne move most? 17:15.
  • When is the network quietest? 03:00.
  • How strong is the daily swing? The peak bin is about 15.1 times the quietest bin.
  • Is the PM peak real or vague? It is measurable, narrow, and strongly clustered around late afternoon.

Why this matters

  • Journalists get a precise headline rather than a vague “rush hour” claim.
  • OOH media gets an exposure-timing layer for audience-value analysis.
  • Transport analysts get a city-wide behavioural rhythm that can be compared with incidents, school terms, holidays, weather, and future infrastructure changes.

Source Outputs

The section is based on the completed time_bin_profile.csv and time_bin_profile_final.json outputs, plus the produced behavioural metrics and derived temporal analysis layers.

Day-of-Week Behavioural Traffic Intelligence

📄 Export Day-of-Week Section as PDF Print-ready section using the completed 148-month day-of-week profile output.

The completed day-of-week profile turns Melbourne's SCATS archive into a weekly behavioural model of the city. Across the cleaned and deduplicated period from 1 January 2014 to 7 April 2026, the script processed 148 / 148 months, produced 1,029 analytical rows, and completed in approximately 32.5 hours. The result is a clear weekly movement signature: traffic builds from Monday through the working week, reaches maximum intensity on Friday, then falls sharply into the Saturday and Sunday rest state.

Headline interpretation: Melbourne's strongest average day is Friday at approximately 133.0 million detected daily movements. The weakest is Sunday at approximately 97.3 million. That means Friday operates around 36.7% stronger than Sunday, while Friday is around 11.4% stronger than Monday.

This section is one of the most human-readable layers of the SCATS project. It does not merely count vehicles; it shows the rhythm of the working week, the weekend collapse, COVID-era behavioural disruption, recovery, seasonality, and the persistent structural weakness of Mondays relative to the later working week.

Coverage: 2014-01-01 to 2026-04-07 Months complete: 148 / 148 Strongest day: Friday, 133.0M / day Weakest day: Sunday, 97.3M / day Runtime: ~32.5 hours

Strongest Day

Friday

Friday Avg Daily Volume

133.0M

Weakest Day

Sunday

Sunday Avg Daily Volume

97.3M

Friday vs Sunday

+36.7%

Friday vs Monday

+11.4%

Weekday Share

75.13%

Weekend Share

24.87%

1. Melbourne has a weekly traffic heartbeat

The completed profile shows a smooth, intuitive pattern: Monday starts lower, Tuesday and Wednesday strengthen, Thursday nears saturation, Friday peaks, and the weekend drops sharply.

2. Friday is the structural peak

Friday is not merely a noisy outlier. It remains the strongest day across the full completed archive, combining commuting, freight, retail, hospitality, nightlife, and late-week discretionary movement.

3. Sunday is a true rest state

Sunday sits far below Friday and below Saturday, giving the city a clear weekly decompression signature that is highly visible in both bar charts and heatmaps.

4. Monday weakness is persistent

Monday is consistently weaker than the Tuesday-to-Friday working week, suggesting a real behavioural structure rather than random month-to-month variation.

5. COVID changed the weekly shape

The era comparison charts show the COVID-shock period compressing the entire weekly curve downward, followed by a recovery/new-normal profile that rises above the pre-COVID average.

6. Weekends are more volatile

Saturday and Sunday show higher month-to-month volatility than most weekdays, consistent with discretionary travel, events, holidays, weather sensitivity, and pandemic disruption.

Headline Day-of-Week Charts

These charts show the core weekly movement signature: Friday peak, Sunday rest state, workweek build-up, and the long-term day-of-week heat structure.

Melbourne Weekly Traffic Heartbeat

The core weekly rhythm chart: Monday starts lower, the workweek builds steadily, Friday reaches maximum average daily movement, then the network drops into the weekend.

Melbourne SCATS day-of-week traffic analysis chart showing Melbourne Weekly Traffic Heartbeat

Average Daily Traffic by Day of Week

Bar-chart version of the weekly hierarchy, designed for fast public interpretation and media use.

Melbourne SCATS day-of-week traffic analysis chart showing Average Daily Traffic by Day of Week

Friday vs Sunday Differential

Shows the gap between Melbourne at full weekly intensity and its Sunday rest state.

Melbourne SCATS day-of-week traffic analysis chart showing Friday vs Sunday Differential

Day-of-Week Strength Index

Indexes each day against Friday = 100, making the relative strength of each weekday immediately visible.

Melbourne SCATS day-of-week traffic analysis chart showing Day-of-Week Strength Index

Weekday vs Weekend Share

High-level split showing that Melbourne remains structurally weekday-driven while weekends still contribute a major movement economy.

Melbourne SCATS day-of-week traffic analysis chart showing Weekday vs Weekend Share

Day-of-Week Traffic Intensity by Year

Shows the weekly rhythm across every year, making COVID disruption, recovery, and long-term growth visible in one image.

Melbourne SCATS day-of-week traffic analysis chart showing Day-of-Week Traffic Intensity by Year

Friday–Sunday Traffic Gap Over Time

Tracks how much stronger Friday was than Sunday month by month, revealing behavioural volatility and lockdown-era disruption.

Melbourne SCATS day-of-week traffic analysis chart showing Friday–Sunday Traffic Gap Over Time

Melbourne Weekly Traffic Signature

A radar-style fingerprint of Melbourne’s weekly movement shape.

Melbourne SCATS day-of-week traffic analysis chart showing Melbourne Weekly Traffic Signature

Second-Wave Day-of-Week Behavioural Charts

These additional charts examine behavioural structure: Monday weakness, Friday dominance, COVID-era shape changes, seasonal day-of-week effects, cumulative contribution, and volatility.

Melbourne Workweek Build-Up

Quantifies the steady increase in movement intensity from Monday to the Friday peak.

Melbourne SCATS day-of-week traffic analysis chart showing Melbourne Workweek Build-Up

The Weekend Traffic Collapse

Shows how sharply traffic falls after Friday into Saturday and Sunday rest-state movement.

Melbourne SCATS day-of-week traffic analysis chart showing The Weekend Traffic Collapse

Day-of-Week Behaviour Before, During and After COVID

Compares the weekly traffic rhythm across pre-COVID, COVID-shock, and recovery/new-normal eras.

Melbourne SCATS day-of-week traffic analysis chart showing Day-of-Week Behaviour Before, During and After COVID

Weekly Shape Index Across Eras

Normalises each era against its own Friday peak to expose changes in the weekly behavioural shape.

Melbourne SCATS day-of-week traffic analysis chart showing Weekly Shape Index Across Eras

Friday Dominance Over Time

Tracks Friday’s annual premium compared with Monday and Sunday.

Melbourne SCATS day-of-week traffic analysis chart showing Friday Dominance Over Time

Monday Weakness Over Time

Shows whether Monday remains structurally weaker than the rest of the working week.

Melbourne SCATS day-of-week traffic analysis chart showing Monday Weakness Over Time

Weekday vs Weekend Share Over Time

Tracks whether Melbourne has become more weekday-driven or weekend-driven over time.

Melbourne SCATS day-of-week traffic analysis chart showing Weekday vs Weekend Share Over Time

Seasonal Day-of-Week Traffic Heatmap

Shows how weekly behaviour changes across the calendar year.

Melbourne SCATS day-of-week traffic analysis chart showing Seasonal Day-of-Week Traffic Heatmap

Cumulative Weekly Traffic Contribution

Shows how much of the weekly traffic total has accumulated by each day of the week.

Melbourne SCATS day-of-week traffic analysis chart showing Cumulative Weekly Traffic Contribution

Which Days Are Most Volatile?

Measures which weekdays fluctuate most month-to-month across the full archive.

Melbourne SCATS day-of-week traffic analysis chart showing Which Days Are Most Volatile?

Media interpretation

Simple headline: Melbourne builds toward Friday. The SCATS archive shows a clear weekly behavioural signature: the city intensifies through the workweek, peaks on Friday, and drops into a Sunday rest state.

Why it matters: this is useful for transport planning, OOH advertising, retail, events, freight, hospitality, journalism, and public understanding because it translates billions of detector observations into a familiar weekly rhythm.

Weekday vs Weekend Behavioural Traffic Intelligence

📄 Export Weekday / Weekend Section as PDF Print-ready section using the completed weekday/weekend split output.
Confirmed result:
Across the full cleaned Melbourne SCATS archive from 1 January 2014 to 7 April 2026, weekdays account for 404.9 billion detected movement events, while weekends account for 134.1 billion. That equals 75.13% weekday traffic and 24.87% weekend traffic across 539.0 billion total analysed movement events.

Behavioural interpretation: this section turns the SCATS archive from a pure volume count into a citywide behavioural model. It shows how much of Melbourne's movement economy is work-week driven, how resilient weekend traffic is, how the COVID disruption affected weekday and weekend patterns differently, and how strongly weekend daily intensity has recovered.

The key public-facing insight is simple: Melbourne is weekday-dominant, but not weekday-only. Even after normalising for the number of days, a typical weekend day still reaches around 82.7% of weekday daily traffic intensity.

Weekday share: 75.13% Weekend share: 24.87% Weekend daily intensity: 82.7% COVID-era disruption visible Archive total: 539.0B events

Total Analysed Volume

539,020,710,239

Weekday Volume

404,944,112,309

Weekend Volume

134,076,597,930

Weekday Share

75.13%

Weekend Share

24.87%

Average Weekday

127.8M / day

Average Weekend Day

105.7M / day

Weekend Daily Intensity

82.7% of weekday

Months Completed

148 / 148

Zero-Data Month

2018-12

Processing Runtime

~32.1 hours

Strategic Use

Behaviour, media, OOH and planning

1. Weekday dominance is structural

Three quarters of all detected SCATS movement events occur on weekdays, confirming the ongoing importance of work-week commuting, freight, school, services, and business activity.

2. Weekend traffic remains commercially significant

Weekends still contribute 134.1 billion detected movements. For retail, events, hospitality, tourism, and outdoor advertising, that is not a minor residual market.

3. Normalised weekend intensity is the surprise

After adjusting for weekday and weekend day counts, a typical weekend day reaches about 82.7% of weekday traffic intensity. Melbourne remains highly mobile outside the work week.

4. COVID altered the balance, then recovery lifted weekends

The rolling weekend-share and relative-intensity charts show a visible lockdown-era break, followed by a recovery period where weekend share trends higher than the pre-COVID baseline.

Weekday vs Weekend Dashboard Summary

A one-image overview of the entire weekday/weekend behavioural layer, suitable for media, internal briefings, and social sharing.

Melbourne SCATS weekday versus weekend behavioural traffic analytics dashboard infographic

Overall Traffic Share: Weekday vs Weekend

Simple headline split showing the proportion of all detected SCATS movement events occurring on weekdays and weekends.

Melbourne SCATS overall weekday versus weekend traffic share donut chart

Total Vehicle Movements: Weekday vs Weekend

Absolute scale comparison across the full archive: 404.9B weekday movements versus 134.1B weekend movements.

Melbourne SCATS total weekday versus weekend vehicle movement bar chart

Average Daily Traffic Intensity

Normalised daily comparison showing a typical weekend day reaches 82.7% of weekday daily intensity.

Melbourne SCATS average daily traffic intensity weekday versus weekend bar chart

Monthly Traffic Volumes Over Time

Monthly weekday and weekend movement totals showing long-term growth, disruption, and recovery patterns.

Melbourne SCATS monthly weekday and weekend traffic volumes over time chart

Weekend Share of Total Traffic Over Time

Monthly weekend share plus 12-month rolling average, useful for detecting long-term behavioural change.

Melbourne SCATS weekend share of total traffic over time chart

Weekend Daily Intensity Relative to Weekday

Normalised monthly ratio showing weekend daily traffic as a percentage of weekday daily traffic.

Melbourne SCATS weekend daily traffic intensity relative to weekday chart

Monthly Traffic Composition

Stacked monthly composition showing weekday and weekend share within each month.

Melbourne SCATS monthly traffic composition weekday versus weekend stacked chart

Weekend Share Heatmap by Year and Month

Year-by-month heatmap showing seasonal and disruption effects in weekend share.

Melbourne SCATS weekend share heatmap by year and month

Traffic Composition Across COVID Eras

Period comparison across pre-COVID, disruption, and recovery windows.

Melbourne SCATS weekday and weekend traffic composition across COVID eras chart

Cumulative Traffic Volumes Over Time

Cumulative weekday, weekend, and total movement lines showing the archive building toward 539.0B events.

Melbourne SCATS cumulative weekday weekend and total traffic volumes over time chart
Best media headline: Melbourne's traffic economy is overwhelmingly weekday-driven, but weekends still carry 134.1 billion detected vehicle movement events and a typical weekend day still reaches 82.7% of weekday daily intensity.
How to read this section: blue represents weekday movement, orange represents weekend movement, the pale red background marks the COVID disruption window used in the charts, and the rolling-average line smooths month-to-month calendar noise so the underlying behavioural trend is easier to see.

Month-of-Year Seasonal Traffic Intelligence

The completed month-of-year workflow converts the full deduplicated Melbourne SCATS archive into a seasonal citywide movement profile. Instead of asking only which individual month was largest, this section asks how Melbourne behaves across the calendar year: which months are structurally busiest, which months are quietest, how COVID reshaped seasonal behaviour, and where the strongest recovery-era traffic pressure now appears.

Busiest average month

FebruaryApproximately 128.5 million average daily vehicle movements.

Second strongest month

NovemberApproximately 128.3 million average daily vehicle movements.

Quietest month

JanuaryApproximately 114.4 million average daily vehicle movements.

Peak-to-trough gap

~14.1 million/dayThe February to January difference is large enough to be visible at whole-city scale.

Workflow runtime

34.3 hoursThe completed month-of-year process ran for 123,587 seconds across the full 2014–2026 archive.

February peak November peak January holiday trough March highest cumulative month Recovery era now above pre-COVID baseline 34.3 hour seasonal workflow
Interpretation: February appears to represent Melbourne returning to full operational intensity after the January holiday slowdown: schools, workforces, freight, universities, retail activity and commuting patterns all re-enter the network at once. November is almost as strong, likely reflecting late-year economic and retail activity before the Christmas/New Year slowdown.

Melbourne seasonal traffic curve

The flagship calendar-year curve showing the average daily SCATS movement profile from January to December.

Melbourne seasonal SCATS traffic curve showing average daily vehicle movements by calendar month

Busiest traffic months ranked

Calendar months ranked by average daily traffic intensity, with colour coding from quieter green to busier red.

Ranked Melbourne SCATS busiest traffic months by average daily volume

Seasonal traffic index

A normalized index where 100 represents the typical seasonal baseline. Values above 100 indicate stronger-than-average months.

Melbourne SCATS seasonal traffic index with 100 as baseline

Month-by-year heatmap

A compact visual history of seasonal traffic intensity from 2014 to 2026, including the COVID-era disruption and recovery period.

Month by year Melbourne SCATS traffic heatmap from 2014 to 2026

Seasonal traffic pattern by year

Each line shows one year’s monthly traffic rhythm, revealing how seasonal movement patterns shifted over time.

Melbourne SCATS seasonal traffic pattern by year overlay chart

Average share of annual traffic

Shows how much of each year’s SCATS traffic typically occurs in each calendar month.

Average share of annual Melbourne SCATS traffic by calendar month

Traffic volatility by month

Identifies months whose average daily traffic has varied most strongly from year to year.

Melbourne SCATS traffic volatility by month chart

Long-term monthly traffic growth

Tracks each calendar month across the full period, showing recovery, growth and long-term divergence by season.

Long-term Melbourne SCATS monthly traffic growth lines by calendar month

Busiest vs quietest month

A simple media-friendly comparison between February and January, showing the scale of Melbourne’s seasonal swing.

Melbourne SCATS busiest vs quietest traffic month comparison

Calendar-year intensity strip

A compact seasonal strip that can be used as a quick visual summary or media graphic.

Melbourne calendar year traffic intensity strip from January to December

Total SCATS volume by calendar month

Cumulative cleaned traffic volume grouped by calendar month across the archive. March leads on total cumulative volume because it has more days and full-month coverage across more years.

Total Melbourne SCATS volume by calendar month across all years

Seasonal traffic pattern by era

Compares pre-COVID, COVID-era and recovery/recent seasonal traffic behaviour in one chart.

Melbourne SCATS seasonal traffic pattern by era pre-COVID COVID and recovery
Media angle: The finished seasonal profile supports a simple public story: Melbourne does not move evenly through the year. January is the holiday trough; February and November are the strongest operational months; March is the largest cumulative calendar-month bucket; and the post-COVID recovery era now visibly exceeds the pre-COVID baseline across much of the year.
Processing note: The completed month-of-year workflow reports 148 / 148 months processed, is_complete = true, a date range from 2014-01-01 to 2026-04-07, and one known zero-row month: 2018-12. The 2026 row should be interpreted as partial because the available archive ends on 2026-04-07.

Traffic Archetype Intelligence — Melbourne Road Behaviour Classification

This new CSV-only intelligence layer classifies Melbourne SCATS sites into behavioural road archetypes using the already-computed site rankings, site-month totals, growth, volatility, stability, spike behaviour, and mapped site metadata. It does not require another DuckDB pass. Instead, it turns the hundreds of hours of completed CSV outputs into a reusable classification model for transport, OOH media, journalism, and infrastructure analysis.

Why this matters: the page now moves beyond “which sites are busiest” into “what kind of traffic environment is this?” The V4 model separates metropolitan backbone corridors, reliable exposure corridors, mature urban arterials, balanced metropolitan sites, secondary connectors, rising growth corridors, volatile sites, disruption-sensitive sites, and stable local roads.

Classified SCATS Sites

4,758

Traffic Archetypes

11

Largest Class

Balanced Metropolitan Site

Largest Traffic Share

26.2%

Backbone Traffic Share

15.7%

New Index

Traffic Transformation

What the archetype model reveals

  • Balanced Metropolitan Sites are the largest road class by traffic share, carrying about 26.2% of analysed movement.
  • Mature Urban Arterials carry about 20.2%, showing that established non-freeway arterial structure is a major part of Melbourne movement.
  • Metropolitan Backbone corridors remain the pure OOH exposure leaders because they combine scale and stability.
  • High-Volume Volatile Corridors and Rising Growth Corridors dominate the Traffic Transformation Index because they combine change, volatility, growth, and scale.

How to read these charts

  • Scale measures cumulative traffic importance.
  • Stability rewards predictable month-to-month behaviour.
  • Volatility highlights variable or disruption-sensitive sites.
  • Growth compares early-period and recent traffic levels.
  • OOH exposure score weights scale, stability, and growth for commercial visibility.
  • Traffic Transformation Index weights volatility, growth, scale, and spikes to surface changing corridors.

Traffic Share by Archetype

Shows which behavioural road classes carry the greatest share of analysed Melbourne movement.

Melbourne SCATS Traffic Share by Traffic Archetype chart

Number of Sites by Archetype

Shows the structure of the classified SCATS universe after splitting mixed sites into more useful behavioural road classes.

Melbourne SCATS number of sites by traffic archetype chart

Behavioural Score Heatmap

The heatmap gives each archetype a behavioural fingerprint across scale, stability, volatility, growth, OOH exposure, transformation, and strategic importance.

Melbourne SCATS traffic archetype behavioural score heatmap

Scale vs Volatility by Traffic Archetype

One of the strongest system charts: it separates reliable backbone/exposure corridors from high-volume volatile corridors and local disruption-sensitive sites.

Melbourne SCATS scale versus volatility by traffic archetype scatter plot

Scale vs Growth by Traffic Archetype

Separates mature high-scale corridors from emerging growth corridors and lower-scale local growth zones.

Melbourne SCATS scale versus growth by traffic archetype scatter plot

Pure OOH Exposure Score

Pure exposure ranking: the top sites remain dominated by Metropolitan Backbone corridors because the score rewards scale and stability.

Top 25 Melbourne SCATS sites by pure OOH exposure score

Diversified OOH Exposure Sites

Commercially useful diversified view that surfaces strong candidates across multiple behavioural road classes.

Top 25 diversified Melbourne SCATS OOH exposure sites by traffic archetype

Traffic Transformation Index

Highlights growth, volatility, spikes, and structural change rather than simple traffic volume.

Top 25 Melbourne SCATS sites by Traffic Transformation Index

Strategic Importance Score

Balances traffic scale, stability, growth, and volatility into one network-importance ranking.

Top 25 Melbourne SCATS sites by strategic importance score

Traffic Archetype Output Files

Method note: This is a derived intelligence layer, not a new raw-data query. It combines existing computed CSV outputs, including site rankings and site-month totals, to classify each SCATS site by traffic scale, stability, volatility, growth, spike behaviour, OOH exposure value, transformation intensity, and strategic importance.

Top 10 Behavioural Insights — What Melbourne Traffic Actually Does

This media-ready module turns the completed 15-minute time-bin analysis into clear, quotable findings. These are not just chart observations; they describe the operating personality of Melbourne’s signalized road network across a decade-plus archive.

1Melbourne’s strongest daily pressure point is 17:15

The archive identifies 17:15 as the busiest 15-minute interval, confirming that the strongest network load occurs in the late-afternoon commute rather than exactly on the hour.

2Melbourne is a plateau city, not just a peak-hour city

The network stays above 70% of peak for 11.2 hours, which means the city carries sustained high traffic for much of the day, not only during traditional commute windows.

3Half the day’s traffic has occurred by early afternoon

The cumulative curve shows that 50% of daily traffic is reached by about 13:45, revealing how much road activity is already complete before the evening peak begins.

4Nearly three-quarters of daily traffic is complete by 5PM

By 5PM, around 73.8% of the day’s traffic has already occurred. That makes the late afternoon not just a peak, but the final high-pressure phase of an already busy day.

5The top 10 busiest intervals cluster tightly in 2.2 hours

The strongest 15-minute bins are concentrated between 15:15 and 17:30. For media and OOH planning, that creates a precise high-exposure window rather than a vague “PM peak.”

6Afternoon pressure is structurally stronger than morning build-up

The afternoon peak window is about 1.18× the morning-window peak. Melbourne’s evening pressure is not simply the morning pattern repeated in reverse.

7Morning traffic ramps sharply from the overnight baseline

The morning ramp shows an approximate 5.3× increase from 05:00 to 08:00, capturing the network’s rapid transition from quiet baseline to commuter intensity.

8Evening traffic decays more gradually after peak

The 17:15 peak remains about 2.3× the 21:00 load, showing that pressure releases over several hours rather than disappearing immediately after the commute.

9The true quiet-network baseline is around 03:00

The archive identifies 03:00 as the quietest 15-minute interval. This gives the page a clear baseline for comparing how extreme daytime traffic load really is.

10Traffic value is time-dependent, not just location-dependent

The behavioural charts show that exposure quality changes dramatically by time of day. For commercial planning, a site’s value depends on when traffic passes as well as where it passes.

Media framing: Melbourne does not simply have “rush hour.” It operates as a long high-volume traffic plateau with a concentrated afternoon spike embedded inside it. That is a much more powerful and accurate story than a simple busiest-intersection ranking.

Top 10 Site-Month Insights — Named Sites and Hidden Network Nodes

This media-ready module turns the completed site-month charts into plain-English findings for journalists, advertisers, planners, and public readers.

  1. Melbourne traffic has grown steadily over 12 years. Despite short-term disruptions, total network volume shows a clear long-term upward trend.
  2. COVID caused the largest visible traffic collapse in the archive. The network monthly chart shows a dramatic 2020 drop followed by staged recovery.
  3. Traffic has exceeded pre-COVID levels. By 2023–2025, Melbourne traffic recovered and pushed above earlier highs.
  4. A small number of locations dominate the network. Sites such as Princes near Canning and Eastern Freeway / Hoddle carry enormous cumulative volume.
  5. Growth is concentrated in specific corridors. The fastest-growing site-month outputs point to structural changes in how Melbourne moves.
  6. Some of the most volatile records are network nodes, not named intersections. This exposes hidden traffic-control infrastructure in the SCATS network.
  7. Traffic patterns are strongly seasonal. The heatmap shows annual rhythms, quieter periods, and stronger high-volume months.
  8. Location value changes over time. A site’s importance is not only its total volume but how its monthly pattern changes across the archive.
  9. Melbourne is thousands of micro-systems. The overall network can look stable while individual sites and nodes behave very differently.
  10. The project now combines scale with human meaning. Friendly names, ranked sites, and network-node labels turn 539B movement events into a readable model of the city.
Media framing: This analysis captures both named signalised intersections and underlying SCATS network nodes, giving a broader picture of Melbourne traffic behaviour than a simple intersection ranking.

Site-Month Traffic Intelligence — Named Sites, Network Nodes, Growth and Volatility

Completed V5.2 site-month layer:
This module uses 595,054 site-month rows across 4,758 SCATS sites and joins the result to the SCATS metadata audit file so charts display friendly site names where available. Where no public friendly name exists, the chart labels the SCATS ID as a network node.

Note on “network node” labels: Some SCATS IDs are not listed in the public signalised-intersection register and do not have a friendly site name. These may represent detector stations, ramp meters, virtual/internal control points, or other SCATS network elements that still record real traffic movement and contribute to the network analysis.

Site-Month Rows

595,054

Distinct Sites

4,758

Total Movement Base

539.0B

Top SCATS Site

PRINCES NEAR CANNING

Top SCATS Site Volume

674M

Node Labelling

Friendly name or network node

Top 10 SCATS sites over time

Shows whether Melbourne’s busiest named sites remain dominant or shift across the archive.

Top 10 Melbourne SCATS sites over time by monthly vehicle movements

Top 20 SCATS sites by total volume

Highlights the highest-exposure SCATS locations using rank, readable name where available, site ID, and network-node status.

Top 20 Melbourne SCATS sites by total vehicle movements

Fastest growing sites / network nodes

Identifies locations where average monthly traffic volumes have increased most strongly between early and recent periods.

Fastest growing Melbourne SCATS sites and network nodes

Most volatile sites / network nodes

Surfaces locations with unusually variable month-to-month movement patterns. Several high-volatility items are network nodes rather than named intersections.

Most volatile Melbourne SCATS sites and network nodes
Interpretation insight: Some of the most volatile SCATS records are not named intersections but internal network nodes. This suggests that month-to-month variability is partly driven by hidden control infrastructure such as ramps, detectors, and adaptive network points, not only by major intersections.

Second-Wave Traffic Intelligence Charts

Site-month V5.2 addition:
The second-wave layer now includes site-month intelligence: top sites over time, top 20 cumulative sites, fastest-growing sites, most volatile sites, and network-node labelling where a SCATS ID has no public friendly name.
New chart layer:
The second-wave chart pass adds a deeper behavioural and seasonal view of Melbourne traffic using the completed daily and monthly totals outputs. These charts move beyond headline totals into calendar intensity, monthly heat structure, weekday/weekend behaviour, seasonality, percentile bands, year-on-year growth, and the busiest weeks in the archive.
Generated outputs: The chart index below provides direct access to the completed behavioural and seasonal visualisations. Each chart card links to the full-size PNG so readers can open, share or inspect the relevant evidence directly. Network time-of-day and peak-share visualisations are now treated as part of the broader completed temporal-intelligence layer rather than as internal reserved chart numbers.

Daily Calendar Heatmap

A year-by-year calendar heatmap showing cold, normal, and hot traffic days across the full archive. This is one of the most visually powerful ways to see lockdowns, holidays, weekly rhythm, and recent intensity.

Melbourne SCATS traffic map visualisation showing Daily Calendar Heatmap

Monthly Year Heatmap

A month-by-year heatmap showing seasonal and long-term traffic intensity. It makes high-volume recent months, COVID disruption, and partial/data-gap months immediately visible.

Melbourne SCATS traffic map visualisation showing Monthly Year Heatmap

Weekday vs Weekend Evolution

Shows how average weekday and weekend traffic evolved year by year, highlighting behavioural shifts, COVID-era disruption, and post-pandemic recovery.

Melbourne SCATS traffic analysis chart showing Weekday Vs Weekend Evolution from 2014 to 2026

Average Traffic by Weekday

Ranks the average traffic load for each day of the week. This is a simple public-facing chart for explaining which days carry the heaviest citywide movement.

Melbourne SCATS traffic analysis chart showing Average Traffic By Weekday from 2014 to 2026

Day-of-Year Seasonality Profile

Shows the average traffic rhythm across the calendar year, smoothing daily totals to reveal seasonal traffic behaviour, holiday effects, and recurring demand cycles.

Melbourne SCATS traffic analysis chart showing Day Of Year Seasonality Profile from 2014 to 2026

Yearly Daily Percentile Bands

A statistical view showing median daily traffic and the normal daily range by year. This is stronger than a simple average because it shows how the whole distribution moves over time.

Melbourne SCATS traffic analysis chart showing Yearly Daily Percentile Bands from 2014 to 2026

Monthly Year-on-Year Growth Rate

Shows whether each month was higher or lower than the same month one year earlier. Green indicates growth; red indicates contraction.

Melbourne SCATS traffic analysis chart showing Monthly Year On Year Growth Rate from 2014 to 2026

Top 20 Busiest Weeks

Ranks the highest-volume weeks in the SCATS archive. This is useful for identifying sustained pressure periods rather than one-day spikes.

Melbourne SCATS traffic analysis chart showing Top Busiest Weeks from 2014 to 2026

Network Time-of-Day Profile

Melbourne-wide 15-minute traffic profile showing how cleaned SCATS movement volume is distributed across a typical day.

Melbourne SCATS Network Time-of-Day Profile showing 15-minute traffic distribution across a typical day

Peak Window Share

Share of total cleaned Melbourne SCATS traffic volume occurring during the AM and PM peak windows.

Melbourne SCATS Peak Window Share bar chart showing AM and PM peak traffic share
Interpretation: This section is designed as the behavioural layer of the SCATS page. The first daily charts show the headline trend; these second-wave charts show how that traffic is distributed across the calendar, weekdays, seasons, and shock periods.

Third-Wave High-Impact Traffic Intelligence Charts

New high-impact analytics layer:
These charts are generated from the completed CSV outputs rather than re-querying the full DuckDB database. They convert the existing monthly, daily, site-total and site-month layers into decision-grade intelligence: momentum, shock detection, concentration, commercial value, weekday behaviour, seasonality, lifecycle clustering, growth and decline.

Chart Bundle

10 high-impact charts

Compute Type

CSV analytics layer

Best Media Chart

Shock detection timeline

Best Commercial Chart

Value ranking

Best Policy Chart

Concentration curve

Best Behaviour Chart

Weekday fingerprint

Interpretation note: this is the fast insight layer of the project. The heavy deduplication and aggregation work has already been completed; these charts show how the same materialised CSV outputs can be recombined into higher-level questions for journalists, advertisers, planners and researchers.

1. Melbourne Traffic Momentum Index

Shows whether Melbourne traffic is accelerating or slowing using a 3-month rolling month-to-month change index. This acts like a city-scale traffic pulse indicator.

Melbourne traffic momentum index chart

2. Top 20 Rising Sites / Network Nodes

Ranks the SCATS sites and network nodes with the strongest long-term growth by comparing the first 12 observed months with the latest 12 observed months.

Top 20 rising Melbourne SCATS sites and network nodes

3. Top 20 Declining Sites / Network Nodes

Shows where average monthly vehicle movement volumes have fallen most strongly, helping identify corridors whose role in the network may be changing.

Top 20 declining Melbourne SCATS sites and network nodes

4. Network Stability Index

Measures how variable traffic is across SCATS sites each month. This is a system-level stability metric rather than a single-location chart.

Melbourne SCATS network stability index

5. Traffic Concentration Curve

Shows how much of Melbourne’s total traffic is carried by the highest-volume share of SCATS sites. This is one of the clearest charts for infrastructure dependency and OOH planning.

Traffic concentration curve for Melbourne SCATS sites

6. Commercial Traffic Value Ranking

Combines total volume, growth and stability into an OOH-style commercial traffic value score. This is a decision-support chart, not official advertising pricing.

Commercial traffic value ranking for Melbourne SCATS sites

7. Weekday vs Weekend Traffic Fingerprint

Compares average daily network volume by day of week, making the work-week versus weekend behavioural structure immediately visible.

Weekday versus weekend Melbourne traffic fingerprint

8. Monthly Seasonality Fingerprint

Shows which months run hotter or cooler on average across the archive, turning monthly totals into a clean seasonal behaviour profile.

Monthly seasonality fingerprint for Melbourne traffic

9. SCATS Site Lifecycle Clusters

Classifies sites and network nodes into growth, stable, volatile and declining groups. This turns raw site-month data into a strategic network portfolio view.

SCATS site lifecycle clusters

10. Traffic Shock Detection Timeline

Flags months where Melbourne traffic broke sharply away from the rolling historical pattern. This is one of the strongest public-facing story charts on the page.

Traffic shock detection timeline for Melbourne SCATS traffic
High-value takeaway: these outputs show that the archive is no longer only a static historical dataset. It now behaves like a reusable traffic intelligence engine capable of producing policy, media, commercial and behavioural signals from the same validated analytical base.

OOH Parcel Intelligence Method

This section is designed for digital and traditional out-of-home advertising companies, media owners, property partners, and major advertisers. The current SCATS intelligence layer already supports a portfolio view of roadside exposure: ranked sites, traffic concentration, campaign portfolio sizing, commercial coverage thresholds, break-even CPM modelling, and tier-based revenue scenarios.

OOH intelligence status:
The OOH intelligence layer is now populated with real site-intelligence, parcel-opportunity, exposure-ranking and temporal scheduling outputs. The time-bin profile, weekday/weekend split, day-of-week profile and month-of-year profile are now available, giving the section campaign timing intelligence as well as portfolio and network intelligence. The remaining deeper upgrade is SCATS + TIRTL integration for speed, vehicle class and freeway corridor performance.

Ranked SCATS Sites

4,758

Top Advertising Intersection

4415 — PRINCES NR CANNING

Top 100 Traffic Share

7.8%

Top 500 Traffic Share

28.0%

Top 1000 Traffic Share

46.3%

Top 2000 Traffic Share

71.9%

Sites Needed for 50% Traffic

~1,120

Sites Needed for 90% Traffic

~3,080

Highest Exposure Window

17:15 network peak

Weekday / Weekend Value

75.13% weekday / 24.87% weekend

Premium Candidate Sites

Top 250–500 portfolio tier

Commercial Model

Scenario based, not claimed pricing

Commercial interpretation: The network is commercially tiered rather than purely concentrated. The elite Top 100 matters, but it does not dominate the whole network. The strongest OOH strategy suggested by the data is a staged portfolio: premium core, commercial backbone, broad metro reach, then selective long tail.

OOH Portfolio and Campaign Strategy Charts

Campaign Portfolio Size vs Traffic Captured

Shows how much total ranked traffic is captured as more top-ranked SCATS sites are selected.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Campaign Portfolio Size Vs Traffic Captured

Portfolio Efficiency Ratio

Traffic share divided by site share. Smaller portfolios punch far above their weight; larger portfolios become reach-driven.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Portfolio Efficiency Ratio

City-Level Traffic Concentration

Shows that site selection matters: traffic share rises faster than site share across the ranked network.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing City Level Traffic Concentration Curve

Sites Needed for Traffic Thresholds

Decision chart for portfolio planning: how many top-ranked sites are needed to reach 10%, 25%, 50%, 75%, 90%, and 95% traffic capture.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Sites Required For Traffic Thresholds

Commercial Portfolio Ladder

A sales-friendly view of traffic captured by different top-site portfolio sizes.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Commercial Portfolio Ladder

Break-Even CPM by Portfolio Size

Scenario model showing the CPM required to break even across utilisation levels and portfolio sizes.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Break Even Cpm By Portfolio

ROI Heatmap — 1,000-Site Portfolio

Scenario heatmap for a 1,000-site portfolio using CPM and utilisation assumptions.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Roi Heatmap For 1000 Site Portfolio

Tier-Based Revenue Model

Illustrative revenue model using tiered CPM assumptions across ranked traffic tiers.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Tier Based Revenue Model

OOH Source Files Now Wired Into This Section

PurposeFileStatus
Ranked site universesite_intelligence/site_rankings.csvAvailable
Network summarysite_intelligence/site_network_summary.jsonAvailable
Portfolio simulationsite_intelligence/campaign_charts/campaign_portfolio_simulation_summary.csvAvailable
Traffic thresholdssite_intelligence/concentration_charts/traffic_threshold_sites_required.csvAvailable
Rank-group densitysite_intelligence/concentration_charts/rank_group_density_summary.csvAvailable
Revenue scenariossite_intelligence/revenue_charts_v2/revenue_simulation_v2_scenarios.csvAvailable
Tier-based revenuesite_intelligence/revenue_charts_v2/tier_based_revenue_summary.csvAvailable
Final exposure windowstime_bin_profile_final.json and time_bin_profile.csvComplete — 148 / 148 months, 14,112 rows

Questions This Section Can Already Answer

  • How much traffic can the Top 100, 500, 1000, 2000, and 3000 sites capture?
  • How many sites are needed to capture 50%, 75%, 90%, or 95% of ranked traffic?
  • Where does portfolio efficiency begin to decay?
  • Which ranked tiers support premium, backbone, broad-reach, and long-tail strategies?
  • How sensitive are revenue outcomes to CPM and utilisation assumptions?

Pending After Final V3 Temporal Runs

  • Best 15-minute exposure windows for digital campaign scheduling. Completed via time-bin behavioural analytics.
  • Weekday vs weekend advertising value.
  • Day-of-week audience pressure.
  • Month-of-year seasonality for campaign timing.
  • Morning vs evening commuter exposure differences.
Scenario-modelling note: Revenue and ROI charts are planning models based on configurable assumptions such as CPM, utilisation, and cost per site. They should be presented as exploratory commercial modelling, not as claimed market pricing or guaranteed revenue.

Top 100 OOH Opportunity Map — Melbourne Traffic Intelligence Layer

This is now the single consolidated OOH intelligence module for the page. It keeps the Integrated Top 100 Parcel Opportunity Map as the core visual asset, and folds the former OOH Parcel Intelligence & Billboard Opportunity Discovery content into the map as supporting method, commercial value, opportunity-type, and action layers.

From traffic counts to land opportunity intelligence

The major opportunity is to connect long-term SCATS traffic intensity with Vicmap cadastral parcel discovery. That turns a high-volume intersection from a dot on a map into a commercial site-acquisition lead: measured exposure, location context, nearby land parcels, VicPlan lookup, Street View review, and a path toward planning, ownership and billboard feasibility checks.

For out-of-home media companies, the value is that the system identifies not just where traffic is heavy, but where physical roadside advertising opportunities may exist near verified long-term traffic demand.

Commercially Ranked SCATS Sites

4,758

Dataset Exposure Base

539B+ movements

Coverage Period

2014 → 2026

Top Candidate Site

4415 — PRINCES NR CANNING

Top Site Exposure

674,498,771 movements

Spatial Layer

Nearest Vicmap parcels

Commercial exposure definition: each traffic total represents cumulative recorded vehicle movements over the SCATS analysis period from 2014-01-01 to 2026-04-07. Annual, daily and peak-hour values are screening metrics for billboard site discovery, corridor dominance assessment and parcel-level opportunity review. These figures are traffic-intensity indicators, not guaranteed audience impressions.

How this map works

1. Rank TrafficUse cleaned SCATS totals to identify the highest-exposure monitored locations.
2. Locate SiteResolve each SCATS site to a latitude/longitude and road environment.
3. Query VicmapFind cadastral parcels around each high-volume traffic location.
4. Inspect ParcelReview parcel geometry, frontage, adjacency, access and potential visibility.
5. Filter FeasibilityLayer zoning, ownership, planning controls, road reserve constraints and sightlines.
6. Build Lead PackCreate a ranked billboard opportunity list for acquisition and commercial review.
Advertising interpretation:
A high-traffic SCATS location is an exposure signal. A nearby Vicmap parcel is a potential physical asset signal. Combining the two creates a practical billboard opportunity discovery workflow: find demand first, then identify land that may be capable of hosting roadside advertising infrastructure.

Commercial value layers

For billboard acquisition teams

Creates a ranked list of places to investigate, rather than relying on manual scouting, anecdotal corridor knowledge, or one-off traffic counts.

For media sales teams

Translates raw traffic into audience-exposure language: vehicle movements over 12 years, annualised exposure, daily average exposure, and peak-hour visibility.

For property partnerships

Helps identify parcels near major traffic flows where landowners, councils, utilities, or transport-adjacent property holders may be approached.

For network planning

Supports a portfolio view: premium top sites, commercial backbone sites, and broad long-tail locations that may suit lower-cost or local campaigns.

Opportunity types this map can reveal

Elite intersections

Top-ranked sites with sustained long-term exposure and premium roadside visibility potential.

Corridor dominance zones

Clusters of high-flow sites that can support repeated commuter exposure and campaign packaging.

Undervalued parcels

Land near strong traffic signals that may not currently be recognised as an advertising asset.

Future-growth candidates

Sites that can later be enriched with growth, weekday/weekend, daypart and yearly trend layers.

Integrated Top 100 parcel opportunity map

High-volume traffic locations are shown beside an interactive map so planners can move from measured exposure to nearby cadastral parcel discovery, VicPlan lookup, and Google Street View review without leaving the page.

Loading Top 100 OOH opportunity sites from top100_scats_ooh_map.json ...

Top 97 OOH Opportunity Sites
Rank Exposure Location & Advertising Metrics Parcel
Next step: after inspecting parcels and Street View, the discovery engine below converts the Top 100 locations into a ranked commercial shortlist.

OOH Site Discovery Engine & Commercial Intelligence

This section converts raw traffic intelligence into commercial decision intelligence. Each site is assigned a Billboard Opportunity Score derived from long-term exposure dominance and sustained corridor performance.

Billboard Opportunity Score (0–100)
Scores are calculated using relative ranking among the Top 100 Melbourne traffic sites, giving planners a rapid shortlist of commercially dominant billboard discovery zones.

Top Billboard Opportunity Candidates

Rank Site Score Exposure Tier

Example Billboard Discovery Workflow

Example Site: Rank #1 Candidate

Workflow:
  1. Identify top-ranked traffic exposure site
  2. Open parcel SPI from integrated parcel map
  3. Launch VicPlan and locate cadastral parcel
  4. Review zoning and planning overlays
  5. Inspect site visibility using Street View
  6. Evaluate feasibility for billboard placement
  7. Initiate landowner engagement or lease negotiation

Corridor Dominance Analysis

Individual sites reveal local exposure. Corridors reveal strategic market coverage. This section groups the Top 100 OOH opportunity sites into recognisable Melbourne traffic corridors and ranks them by combined long-term vehicle exposure.

Commercial purpose: corridor analysis helps OOH media planners think beyond one billboard location and identify repeat-exposure corridors, campaign clusters, commuter routes, and dominant roadside advertising zones.

Loading corridor intelligence...

Requires top100_scats_ooh_map.json in the same folder as this HTML file.

SCATS Site Intelligence, Portfolio Efficiency and Revenue Modelling

📄 Export Site Intelligence Section as PDF Charts load from site_intelligence/ under /var/www/html/live/SCATS.
New site-intelligence layer:
The completed site totals workflow confirms 4,758 ranked SCATS sites, 595,054 site-month rows, and a total site-volume base of 539,020,710,239 cleaned vehicle movements. The highest-ranked site is 4415 — PRINCES NR CANNING with 674,498,771 movements. This section turns the site ranking table into concentration curves, portfolio simulations, traffic-tier models, and revenue-scenario models.

Ranked Site Total

4,758

Site-Month Rows

595,054

Site Intelligence Volume

539,020,710,239

Top SCATS Site

4415 — PRINCES NR CANNING

Top SCATS Site Volume

674,498,771

Completed Site-Month Rows

595,054

Site-Month Date Range

2014-01 to 2026-04

Network Node Handling

Named sites + network nodes

Top 100 Share

7.8%

Top 500 Share

28.0%

Top 1000 Share

46.3%

Top 2000 Share

71.9%

Top 3000 Share

88.9%

Sites for 50% Traffic

~1,120 sites / 23.5%

Sites for 90% Traffic

~3,080 sites / 64.8%

Strategic interpretation: Melbourne's SCATS network is not flat. It behaves like a tiered, heavy-tailed infrastructure network: the very top sites are valuable, the first 500–1000 sites form the commercial backbone, and the 1001–2000 group is surprisingly important because it contributes the largest single rank-group share at about 25.6%.

1. Network Structure and Site Ranking

These charts show the structure of the ranked SCATS site network: concentration, rank decay, site activation, and the relationship between elite sites and the long tail.

Traffic concentration curve

Cumulative share by site rank. Shows the network is strongly hierarchical, with a minority of sites capturing a disproportionate share of total traffic.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Traffic Concentration Curve

Rank decay by total volume

Shows the steep high-volume head and long lower-volume tail of the SCATS network.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Rank Decay By Total Volume

Rank decay — log scale

Log-scale view confirming heavy-tailed, power-law-like structure rather than a flat or random distribution.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Rank Decay — Log Scale

Monthly network volume

Historical monthly traffic volume. The COVID-era collapse and recovery are clearly visible, validating the real-world sensitivity of the archive.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Monthly Network Volume

Active SCATS sites over time

Shows the active site count rising from roughly 3,400 to around 4,600, proving that coverage density increased materially over the archive.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Active Scats Sites Over Time

Traffic share by percentile band

Shows how traffic is distributed across percentile layers, proving that mid-tier and broad-network sites matter as well as the elite top sites.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Traffic Share By Percentile Band

Traffic share captured by top-ranked sites

Shows the Top 1000 sites capturing about 46.3% of the traffic, creating a clear portfolio planning threshold.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Traffic Share Captured By Top Ranked Sites

Top 25 SCATS sites

The strongest named site hierarchy, led by SCATS 4415 — PRINCES NR CANNING — with 674,498,771 movements.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Top Scats Sites

Average monthly volume per active site

Shows per-site average volume over time and highlights the same real-world traffic disruption visible in the network total.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Average Monthly Volume Per Active Site

2. Strategic Tiering and Coverage Efficiency

These charts translate rankings into strategy: how much traffic each tier captures, how efficiently each tier performs, and how quickly marginal gains decline.

Coverage efficiency curve

Site share vs traffic captured. This is the core optimisation curve: the red curve above the equality line proves selective portfolio design beats random coverage.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Coverage Efficiency Curve

Marginal traffic gain by rank

Shows how much each additional ranked site contributes. Early sites carry high marginal value; the long tail produces diminishing returns.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Marginal Traffic Gain By Rank

Marginal gain — log scale

A technical validation of diminishing marginal contribution across the full rank range.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Marginal Gain — Log Scale

Traffic share by strategic tier

Tiered share model showing that the long tail has the most sites, but the ranked tiers carry disproportionate strategic value.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Traffic Share By Strategic Tier

Site count by strategic tier

Shows the network footprint behind the tiering model: a small core, a major middle layer, and a large long tail.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Site Count By Strategic Tier

Efficiency ratio by tier

Traffic share divided by site share. Tier 1 punches roughly four times above its footprint, proving premium-site leverage.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Efficiency Ratio By Tier

Top 1000 vs remaining network

Top 1000 sites capture about 46.3% of total traffic while the remaining sites carry about 53.7%.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Top 1000 Vs Remaining Network

Top 500 / next 500 / remaining

Top 500 capture about 28.0%; ranks 501–1000 add about 18.3%; remaining sites add about 53.7%.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Top / Next / Remaining

3. Campaign Portfolio Simulation

These charts answer the practical question: if a campaign or infrastructure strategy selected the top N sites, how much of Melbourne's measured traffic would it capture?

Campaign portfolio size vs traffic captured

A decision chart showing how traffic share grows as more top-ranked SCATS sites are selected.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Campaign Portfolio Size Vs Traffic Captured

Campaign coverage efficiency

Portfolio site share against traffic share. Shows which portfolio sizes outperform a non-targeted coverage strategy.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Campaign Coverage Efficiency

Incremental traffic gained

Shows how each expansion step contributes extra traffic coverage, useful for campaign upsell or rollout staging.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Incremental Traffic Gained

Diminishing returns per added site

Shows the average incremental gain per added site falling as the portfolio expands.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Diminishing Returns Per Added Site

Portfolio efficiency ratio

Traffic share divided by site share. Small portfolios are extremely efficient; broad portfolios become coverage-driven.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Portfolio Efficiency Ratio

Traffic captured by portfolio size

Client-friendly bar chart showing milestones: Top 500 about 28%, Top 1000 about 46.3%, Top 2000 about 71.9%, Top 3000 about 88.9%.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Traffic Captured By Portfolio Size

Remaining network traffic

The inverse portfolio chart: after selecting 2000 sites, about 28% of traffic remains outside the selected group.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Remaining Network Traffic

4. Concentration Thresholds and Commercial Portfolio Ladder

These charts provide client-friendly threshold visuals: how many sites are needed for 10%, 25%, 50%, 75%, 90%, and 95% traffic coverage, and how the network breaks into rank groups.

Top 100 vs remaining network

Top 100 sites capture 7.8% of traffic; this proves elite sites matter, but most movement sits beyond the very top layer.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Top Vs Remaining Network

Top 500, next 500, remaining

Top 500 = 28.0%, ranks 501–1000 = 18.3%, remaining = 53.7%. This is one of the cleanest tier-structure visuals.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Top , Next , Remaining

City-level concentration curve

Signature concentration curve showing 20% of sites capture close to half of total traffic and 50% of sites capture roughly 80%.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing City Level Concentration Curve

Sites needed for traffic thresholds

Shows how many top-ranked sites are required to capture 10%, 25%, 50%, 75%, 90%, and 95% of traffic.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Sites Needed For Traffic Thresholds

Remaining traffic after selection

Shows how quickly the unselected traffic pool falls as portfolios expand.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Remaining Traffic After Selection

Average traffic volume per site group

Top 100 sites average about 419.4M movements each; 3001+ sites average about 34.0M each.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Average Traffic Volume Per Site Group

Traffic share by rank group

Ranks 1001–2000 form the largest single contribution group at about 25.6%, a non-obvious but important insight.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Traffic Share By Rank Group

Commercial portfolio ladder

Clear portfolio thresholds from 100 sites to full network, useful for packaging traffic coverage products.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Commercial Portfolio Ladder

5. Revenue Simulation V1 — Simple CPM and Cost Model

The first revenue model uses simple placeholder assumptions to convert measured traffic into impressions, revenue, cost, and profit. These are scenario assumptions, not asserted market prices.

Revenue vs portfolio size

Initial CPM model showing revenue rises quickly then flattens as lower-yield sites are added.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Revenue Vs Portfolio Size

Cost vs portfolio size

Linear cost model based on a configurable cost-per-site assumption.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Cost Vs Portfolio Size

Profit vs portfolio size

Initial profit model combining traffic-derived revenue and site costs.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Profit Vs Portfolio Size

Revenue per site

Shows high early yield and predictable decline as broader portfolios include lower-ranked sites.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Revenue Per Site

6. Revenue Simulation V2 — CPM, Utilisation and Tier Scenarios

The second revenue model stress-tests multiple CPM levels, utilisation levels, break-even CPM, ROI, and tier-based pricing assumptions. These charts are best treated as scenario modelling for OOH media, infrastructure planning, or market-sizing discussions.

Revenue by CPM scenario

Sensitivity model for $2, $4, $8, $12, and $16 CPM scenarios across portfolio sizes.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Revenue By Cpm Scenario

Profit by CPM scenario

Shows profitability under multiple CPM assumptions. This is a scenario model, not a claimed market price.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Profit By Cpm Scenario

Profit by utilisation

Stress-test of $8 CPM under 25%, 50%, 75%, and 100% utilisation.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Profit By Utilisation

ROI by utilisation

Shows ROI sensitivity across utilisation assumptions and portfolio sizes.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Roi By Utilisation

Break-even CPM required

Break-even CPM remains very low in this simplified model, indicating strong margin potential if assumptions hold.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Break Even Cpm Required

Revenue per site by CPM

Compares per-site yield under multiple CPM levels, reinforcing the importance of early high-ranked sites.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Revenue Per Site By Cpm

ROI heatmap — 1000-site portfolio

Heatmap showing ROI sensitivity across CPM and utilisation assumptions for the 1000-site portfolio.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Roi Heatmap — 1000 Site Portfolio

Tier-based revenue model

Tiered CPM model showing the 101–500 group as the largest revenue contributor under the sample assumptions.

Melbourne SCATS out-of-home advertising and billboard opportunity chart showing Tier Based Revenue Model
Key insight for OOH media and traffic intelligence:
The network appears commercially tiered rather than purely concentrated. The Top 100 sites are important but only capture 7.8%; the Top 500 capture 28.0%; the Top 1000 capture 46.3%; and the Top 2000 capture 71.9%. That means the strongest strategy is not just buying or analysing a tiny elite set — it is building a staged portfolio: premium core, commercial backbone, broad network, then selective long tail.

OOH Buyer Pitch Pack — Why Media Companies Should Care

This section reframes the SCATS analysis for out-of-home advertising executives. It explains the commercial buying logic in their language: exposure, site ranking, audience reliability, campaign coverage, and acquisition prioritisation.

1. It ranks real exposure

Sites are ordered by measured vehicle movements, not guesswork, generic suburb popularity, or manual traffic impressions.

2. It has unusual historical depth

The 2014–2026 coverage gives long-term confidence that a site is structurally busy, not merely busy during a short survey window.

3. It finds commercial concentration

The Top 500 and Top 1000 site shares show how a small portfolio can capture a large share of monitored traffic exposure.

4. It supports acquisition triage

Parcel matching can turn the highest-volume traffic nodes into a ranked land-investigation workflow.

5. It improves campaign packaging

Sites can be grouped into premium, corridor, commuter, CBD-fringe, freight, and local-retail audience products.

6. It creates defensible sales evidence

Advertisers can be shown the traffic basis behind each location rather than being asked to rely on vague “high exposure” claims.

Executive pitch:
This platform can become a Melbourne roadside media intelligence layer: a system that ranks traffic exposure, identifies the nearby land parcels, and helps media owners decide where the next billboard, digital screen, or roadside advertising partnership deserves investigation first.

Suggested commercial language for the page

Instead of saying...Say this...Why it works
Total: 674,498,771674,498,771 recorded vehicle movements over the 2014–2026 dataset periodTurns a raw number into an exposure claim with time context.
Busiest SCATS siteHighest measured long-term roadside exposure location in the ranked SCATS datasetSounds like a commercial opportunity, not just an engineering statistic.
Map nearby parcelsIdentify nearby cadastral parcels that may support billboard acquisition reviewConnects mapping to the real property workflow used by media companies.
Peak trafficPeak-hour audience densityUses advertising language rather than transport-only language.

Recommended Build Roadmap — Turning This Into a Commercial OOH Intelligence Product

📄 Export OOH Intelligence Roadmap as PDF

The analytical foundation for an OOH (Out-of-Home) intelligence product is now substantially complete. The platform already includes SCATS exposure rankings, temporal campaign intelligence, parcel opportunity discovery, corridor dominance analysis, site-month intelligence, interactive mapping, reproducibility evidence and downloadable diagnostics.

Current status — May 2026:
The core analytical layer is now effectively complete. Remaining product work is primarily commercial packaging, optional live data integration, TIRTL corridor enrichment, reporting automation and customer-facing UI refinement.

Exposure Rankings

Complete

Top intersections and cumulative movement intelligence.

Temporal Campaign Layer

Complete

Time-bin, weekday/weekend and seasonality analysis.

Parcel Opportunity Discovery

Complete

Spatial intelligence and mapping workflows operational.

OOH Intelligence Layer

Strong

High-value movement exposure now historically supportable.

Real-Time Layer

Future

Would require current SCATS/TIRTL ingestion.

Commercial Packaging

Remaining

UI, subscriptions, reports and enterprise delivery.

What is already commercially supportable?

Capability Status Commercial Use
Intersection exposure rankings Complete OOH site discovery and campaign prioritisation.
Time-of-day intelligence Complete Campaign timing and commuter targeting.
Seasonality analysis Complete Campaign planning and demand timing.
Site-month intelligence Complete Exposure growth and movement trend tracking.
Parcel opportunity mapping Complete Discovery of billboard and infrastructure opportunities.
Freeway / freight corridor intelligence Future TIRTL-enhanced corridor performance products.
Why this matters: The difficult engineering work is largely complete. The remaining steps are mostly commercialisation, packaging and optional live integrations rather than foundational analytics.

Custom SCATS Traffic Intelligence Reports

📄 Export Custom Reports Section as PDF
Custom SCATS reports now available:
Need a specific suburb, road, intersection, corridor, time period, traffic-change question, OOH exposure question, or local traffic issue analysed? Custom SCATS traffic intelligence reports are available on a fixed-fee, payment-upfront basis using the existing Melbourne SCATS analytical platform.

These reports use the independently processed SCATS signal-volume intelligence layer covering Melbourne traffic movement patterns across 15-minute intervals, daily and monthly trends, yearly totals, site rankings, suburb profiles, before/after comparisons, time-of-day behaviour, weekday/weekend patterns and public evidence outputs.

This service is designed for journalists, councils, community groups, OOH media, property analysts, transport observers, local businesses, researchers and organisations that need a fast, plain-English evidence brief from the available SCATS traffic data.

Rapid SCATS Evidence Brief

$495

One focused question. Typical turnaround: 3 business days.

Standard SCATS Intelligence Report

$1,495

Charts, tables, source references and caveats. Typical turnaround: 5 business days.

Priority / Commercial SCATS Report

$3,950

Priority analysis for media, OOH, property, planning or commercial users. Typical turnaround: 7 business days.

Enterprise / Complex Analysis

Quoted

For larger corridor, suburb portfolio, commercial exposure or multi-question analysis.
Why this service is different:
This is not a generic traffic-count request. The platform has already processed and organised years of SCATS signal-volume data into reusable analytical outputs, data dictionaries, charts, maps and evidence layers. That means many questions can be answered faster and more affordably than starting a conventional traffic-data analysis from scratch.

What a custom SCATS report can investigate

Suburb Traffic Profiles

Local movement evidence

Traffic totals, busiest sites, local rankings, daily/monthly trends and time-of-day patterns for a suburb or area.

Intersection Rankings

Site-level intelligence

Identify high-volume intersections, traffic-change sites, local pressure points and movement rankings.

Before / After Comparisons

Change detection

Compare available SCATS movement patterns before and after a road project, tunnel opening, event, restriction or local change.

Time-of-Day Analysis

15-minute intervals

Find busiest and quietest windows, peak periods, weekday/weekend differences and recurring time-bin patterns.

OOH Exposure Intelligence

Roadside audience proxy

Use SCATS movement volumes to support billboard, signage, roadside property and commercial exposure questions.

Community Evidence Briefs

Public issue support

Prepare a clear evidence pack for local traffic concerns, council discussions, media questions or public submissions.

Report packages

Package Fee Typical turnaround Includes Best suited to
Rapid SCATS Evidence Brief $495 AUD 3 business days One focused question, short written answer, relevant figures where available, source-file references, caveats and next-data-needed notes. Residents, community groups, journalists, small businesses.
Standard SCATS Intelligence Report $1,495 AUD 5 business days Deeper written analysis with charts, tables, site rankings, time-period comparisons, map references where available, downloadable evidence paths and public-safe wording. Councils, media, planning discussions, community campaigns, local commercial users.
Priority / Commercial SCATS Report $3,950 AUD 7 business days Priority review, broader SCATS evidence search, commercial framing, suburb/intersection/corridor analysis, public or internal summary, and optional follow-up discussion. OOH media, property, infrastructure, commercial strategy, legal/planning preparation.
Enterprise / Complex Analysis Quoted By scope Larger multi-suburb, corridor, portfolio, OOH exposure, property, media, council or commercial analysis requiring custom outputs beyond the standard report packages. Enterprise users, consultancies, major commercial users and large public-interest projects.
Payment and scope:
Payment is required upfront before work begins. Reports are scoped to available SCATS and derived analytical outputs. If the available data cannot support a requested conclusion, the report will clearly state that limitation and identify what further data would be required.

Every report is written in plain English and includes a clear distinction between what the data shows, what it suggests, what it does not prove, and what additional data would be required for a stronger conclusion.

Important limitation:
SCATS data is signal-volume data. It is excellent for movement totals, time patterns, intersection pressure and before/after comparisons, but it does not by itself classify vehicles as cars, trucks or buses. Heavy-vehicle and truck-classification questions may require TIRTL or other vehicle-classification datasets.

To request a custom SCATS report, describe the suburb, road, intersection, corridor, time period or traffic question you want analysed. Include any relevant dates, roads, screenshots, council issue, media article, planning question or commercial use case.

Request a Custom SCATS Report

Questions the SCATS Database Can Answer

📄 Export Questions the SCATS Database Can Answer as PDF
Traffic Intelligence Index:
The question bank below has been upgraded into a clickable index. Each listed question shows whether it is already answered, in progress, or a future/corridor-analysis capability, and links directly to the chart or dataset section that supports the answer.

Behind These Answers: What It Took

These answers and graphs are based on the full Melbourne SCATS dataset, processed at 15-minute resolution across more than a decade of network activity. This was not a sample or a small spreadsheet exercise — it required a custom chunked analytics pipeline and sustained compute time.

Total Data Processed

~37+ billion observations

Compute Time

~1+ month cumulative CPU work

Coverage

2014–2026, network-wide

Method

Python + DuckDB chunked pipeline

Raw SCATS CSVs
Cleaning & Dedup
Chunked Processing (Month-by-Month)
Unified Dataset
Analytics Scripts
Charts & Answers

The database was analysed month-by-month to avoid memory limits, progressively building cleaned, deduplicated outputs that support the charts and question answers below.

200+charts currently integrated into the page
Answereddaily, monthly, weekly, seasonal, 15-minute profile, peak-window, day-of-week, month-of-year, busiest-day, quietest-day, peak-share and map questions
In progressNil. All script runs complete
Futurecorridor propagation, route sequencing, congestion origin and recovery modelling
✔ Answered now⏳ Script/output pending🔬 Future corridor/spatial model

High-Value Questions Already Answered

StatusQuestionAnswered byJump
✔ AnsweredWhat was the busiest day in Melbourne traffic history?Top 50 Busiest Days; Busiest Day ResultChart 21
✔ AnsweredWhat was the quietest day in Melbourne traffic history?Bottom 50 Quietest Days; Daily Totals ResultChart 22
✔ AnsweredHow has Melbourne traffic changed since 2014?Daily traffic trend, monthly totals and yearly totals derived from monthly outputChart 18
✔ AnsweredHow did COVID lockdowns affect traffic?Daily trend, rolling averages, COVID disruption chart and bottom-50 quietest daysChart 19
✔ AnsweredWhich days were far above or below normal?Top/bottom 50 days and largest single-day changesChart 24
✔ AnsweredWhat does a normal daily traffic range look like each year?Daily distribution by year and yearly percentile bandsChart 30
✔ AnsweredWhich weeks were the busiest in the archive?Top 20 Busiest WeeksChart 32
✔ AnsweredHow does weekday traffic differ from weekend traffic?Weekday vs Weekend EvolutionChart 27
✔ AnsweredWhich day of the week has the highest traffic volumes?Average Traffic by WeekdayChart 28
✔ AnsweredHow does traffic differ through the calendar year?Day-of-Year Seasonality and Monthly Year HeatmapChart 29
✔ AnsweredWhich SCATS sites grew fastest over the archive?Site-Month Traffic Intelligence; Fastest Growing Sites chartSite-month charts
✔ AnsweredWhich SCATS sites or network nodes are most volatile month to month?Site-Month Traffic Intelligence; Most Volatile Sites / Network Nodes chartVolatility chart
✔ AnsweredWhy do some SCATS IDs appear without friendly intersection names?Network-node labels and System LimitationsNetwork nodes
✔ AnsweredWhich months have the highest and lowest traffic volumes?Confirmed Monthly Totals Result; Monthly Year HeatmapMonthly data
✔ AnsweredWhat is the busiest intersection currently identified?Busiest Site Result; Top 20 Busiest Site Directory; Interactive SCATS MapSite result
✔ AnsweredWhere are the busiest monitored SCATS sites located?Top 20 SCATS Map and full SCATS site network mapMap
✔ AnsweredHow much traffic occurs in the AM and PM peak windows?Peak Share ResultsPeak shares

Traffic Intelligence Questions — Answered vs Remaining

StatusQuestionSource / current basisJump / Chart
✔ AnsweredWhat is the busiest 15-minute period across the network?generate_time_bin_profile_chunkedV3.py — confirmed 96-bin profile now integratedCurrent result
✔ AnsweredWhat time does peak traffic actually begin and end?Time-bin profile + peak-window analysis now integratedPeak section
✔ AnsweredWhat is the average traffic volume by time of day?generate_time_bin_profile_chunkedV3.py — completed time-of-day profile chartsTime-bin charts
✔ AnsweredWhich SCATS sites or network nodes have experienced the fastest growth or decline?generate_site_month_chartsV5_2.py — completed site-month growth analysis using first 12 vs last 12 observed monthsGrowth charts
✔ AnsweredWhich SCATS sites or network nodes are most volatile or most stable?generate_site_month_chartsV5_2.py — completed coefficient-of-variation analysis from site-month totalsVolatility charts
✔ AnsweredWhich SCATS IDs behave like hidden traffic-system nodes rather than named intersections?V5.2 network-node labelling — unnamed SCATS IDs now displayed as network nodes where no public friendly name existsNode note
✔ AnsweredHow consistent is traffic at individual SCATS sites over time?Site-month coefficient-of-variation analysis — most volatile and most stable behaviour can now be identifiedVolatility charts
✔ AnsweredAre traffic increases concentrated in a few locations or spread across the network?Site-month growth rankings combined with the rebuilt network monthly volume trendGrowth + network charts
✔ AnsweredHow different are Mondays from Fridays and Saturdays from Sundays?generate_day_of_week_profile_chunkedV3.py — day-of-week profile now represented by current day chartsDay-of-week section
✔ AnsweredWhich calendar months are structurally hot or cold?generate_month_of_year_profile_chunkedV3.py — month/seasonality outputs now represented by current monthly chartsChart 26
✔ Answered What is the clean yearly total traffic trend? Dedicated yearly totals are now complete via generate_yearly_totals_chunkedV3.py, providing the final cleaned, deduplicated year-by-year SCATS traffic trend across the full observation window. Yearly trend

Future Corridor / Spatial Modelling Questions

StatusQuestionNeeded nextCurrent related section
🔬 FutureWhere does congestion begin along a route?Corridor definitions and ordered SCATS site sequencesFull map
🔬 FutureHow does congestion propagate along corridors?Time-lag analysis across ordered sitesSCATS + TIRTL
🔬 FutureWhich intersections limit overall corridor flow?Corridor grouping, bottleneck scoring and speed/volume pairingTop intersections
🔬 FutureWhich intersections recover from congestion fastest?Event windows and recovery-time modellingFuture model
🔬 FutureWhich intersections determine city-wide congestion patterns?Network centrality, correlation and propagation analysisArchitecture
How to read this index: ✔ items are already supported by charts or tables on this page. ⏳ items are now mainly packaging tasks, such as the final dedicated yearly totals chart. 🔬 items require a later corridor/spatial model, usually involving ordered site sequences, route definitions, or SCATS + TIRTL integration. Site-month growth, volatility and network-node questions are now answered by the V5.2 Site-Month Traffic Intelligence charts.

This section is based on the SCATS question bank and is intended to show the analytical range of the unified SCATS system once the database is fully populated and query-ready.

Questions the Combined SCATS + TIRTL System Can Answer

This section is based on the combined-system question bank. It is where the analysis shifts from intersection behaviour to true network behaviour.

The really big shift:
With SCATS alone, you understand intersection behaviour. With TIRTL alone, you understand corridor behaviour. With SCATS and TIRTL together, you begin to understand how Melbourne actually moves as a network.

Urban Movement Intelligence

Freight and Transport Company Intelligence

📄 Export Freight and Transport Company Intelligence as PDF

The SCATS layer now provides useful freight and transport-company intelligence through network rhythm, peak windows, weekday/weekend splits, day-of-week patterns, seasonal movement, corridor dominance and high-volume site rankings.

Current capability: the page can already help identify when Melbourne moves, where the strongest signalised-network pressure appears, which corridors and intersections dominate cumulative exposure, and how weekday, weekend and seasonal behaviour changes across the archive.

Useful Now

Peak windows, day-of-week behaviour, seasonal demand, corridor concentration

Best Current Evidence

Time-bin, weekday/weekend, day-of-week, month-of-year, site totals and corridor charts

Future TIRTL Layer

Speed, vehicle class, heavy vehicles and freeway corridor performance

Future integration: deeper freight intelligence will require adding TIRTL speed and classification outputs, especially for the West Gate Bridge and strategic freeway corridors.

Real-Time vs Historical Comparison

📄 Export Real-Time vs Historical Comparison as PDF

One of the strongest capabilities now completed by the Melbourne SCATS Intelligence platform is the historical baseline layer. The platform can now define what “normal” Melbourne movement looked like across multiple time scales using completed yearly totals, monthly totals, daily totals, time-bin profiles, weekday/weekend splits, day-of-week behaviour, month-of-year seasonality, busiest-site rankings, site-month intelligence and COVID-era recovery analysis.

Current status — May 2026:
The historical comparison framework is now effectively complete. The remaining future step is a real-time ingestion layer capable of comparing current SCATS or TIRTL readings against historical baselines to identify unusual congestion, behavioural shifts, recovery patterns, abnormal network pressure or transport disruptions.

Historical Coverage

2014–2026

Historical movement baselines established.

Resolution

15-minute

96 interval bins per day available for comparison.

Behavioural Baselines

Complete

Weekday/weekend, time-bin and seasonal baselines.

COVID Benchmarking

Complete

Collapse and recovery periods now quantified.

Site-Level Intelligence

Complete

Busiest-site and site-month baselines established.

Real-Time Layer

Future

Would require current SCATS/TIRTL ingestion.

What is now historically measurable?

Question Historical capability
Was Melbourne busier than normal today? Historically supportable by comparing current daily totals against daily and yearly baselines.
Is peak-hour congestion stronger than usual? Historically supportable through completed 15-minute time-bin profiles and peak-share analytics.
Is Melbourne behaving like a weekday city or weekend city? Historically supportable through weekday/weekend and day-of-week behavioural profiles.
How unusual is current movement? Historically supportable through anomaly comparison against 12+ years of movement history.
Are we seeing COVID-style suppression or recovery? Historically supportable using the completed collapse-and-recovery analytical layers.
Which corridors or sites are behaving unusually? Historically supportable using busiest-site rankings and site-month intelligence.

How a future live layer would work

A future real-time implementation would ingest current SCATS or TIRTL observations and immediately compare them against historical expectations at matching:

This would make it possible to describe movement conditions in plain language, for example:

Example future live interpretation:
“Melbourne traffic movement is currently operating at 112% of historical Friday expectations. PM peak pressure is unusually high, with freeway corridors showing conditions more consistent with pre-Christmas congestion than a normal weekday.”
Why this matters: Most transport reporting only describes what is happening now. Historical baselines allow the platform to explain whether current movement is actually unusual. This distinction turns raw traffic readings into genuine transport intelligence.

Melbourne Movement Index

📄 Export Melbourne Movement Index as PDF

The Melbourne Movement Index is a proposed public-facing composite indicator designed to summarise Melbourne’s transport activity using the completed SCATS historical analytics layer. It can now be supported from the finished yearly totals, monthly totals, daily totals, time-bin behaviour, weekday/weekend splits, day-of-week profiles, site rankings and database diagnostics.

Current status — May 2026:
The historical Melbourne Movement Index is now analytically supportable from completed SCATS outputs. A true live index would require current/streaming SCATS ingestion and later TIRTL integration for freeway speed, vehicle classification, heavy-vehicle and corridor-performance signals.

Historical Coverage

2014–2026

Supported by completed SCATS historical processing.

Base Resolution

15-minute

Derived from 96 daily SCATS interval columns.

Core Volume Signal

Daily totals

Suitable for daily index construction and anomaly detection.

Macro Signal

Yearly totals

Supports long-term growth, COVID collapse and recovery context.

Behavioural Signal

Time-bin profiles

Supports peak, overnight, weekday/weekend and day-of-week behaviour.

Network Signal

Site rankings

Supports spatial weighting and busiest-corridor emphasis.

Proposed Index Components

Component Input Purpose
Volume Index Daily and monthly cleaned movement totals Measures overall city movement intensity relative to a historical baseline.
Peak Pressure Index AM/PM peak-share outputs and time-bin profiles Tracks pressure during commuter peak windows and identifies changes in peak concentration.
Recovery / Shock Index COVID-era daily/monthly/yearly comparisons Captures large disruptions, collapses and recoveries in city movement patterns.
Behavioural Rhythm Index Weekday/weekend, day-of-week and 96-bin time-of-day profiles Measures whether Melbourne is behaving like a normal weekday city, weekend city, holiday city or disrupted city.
Network Exposure Index Busiest-site rankings and site-month totals Weights the index toward the highest-volume measured parts of the road network.
Future Corridor Index TIRTL speed, direction, classification and heavy-vehicle data Future layer for freeway, bridge, freight and corridor performance once integrated.

How the Historical Index Could Be Defined

A practical first version could use a baseline such as 2014 = 100, or a stronger pre-COVID baseline such as 2017–2019 average = 100. Each day, month or year can then be indexed against that baseline to show whether Melbourne movement is above or below historical normal.

Recommended first public version:
Use the completed historical daily and monthly totals to publish a Historical Melbourne Movement Index first. This avoids pretending the platform is live while still giving journalists, researchers and the public a powerful way to understand Melbourne’s movement history.

Suggested Public Interpretation

Index Reading Interpretation
Below 80 Major disruption or suppressed movement period.
80–95 Below-normal movement, consistent with partial disruption, seasonal lows or weaker activity.
95–105 Normal historical movement range.
105–115 Above-normal movement, indicating strong network activity or growth.
115+ Exceptional movement intensity relative to baseline.

The strongest immediate use is historical storytelling: Melbourne’s pre-COVID growth, 2020 movement collapse, post-COVID recovery, 2025 record year and partial 2026 continuation can all be explained through a single indexed movement signal.

Vehicle Population vs Vehicle Events — Understanding Scale

Why this comparison matters:
The number of vehicles registered in a state is a stock measure. The number of vehicle movements recorded in the SCATS archive is a flow measure. A single vehicle can generate thousands of separate network events over time as it passes through intersections again and again across days, months, and years.

Victoria Registered Motor Vehicles

5,514,720

Melbourne Households with 1 Vehicle

646,218

Melbourne Households with 2 Vehicles

635,953

Melbourne Households with 3+ Vehicles

291,965

Confirmed Vehicle Movement Events

539,020,710,239

Comparison Meaning

Events vastly exceed vehicles

Official BITRE statistics report 5,514,720 registered motor vehicles in Victoria as at 31 January 2024. Separate ABS 2021 Census data for Melbourne shows 646,218 occupied private dwellings with 1 motor vehicle, 635,953 with 2 motor vehicles, and 291,965 with 3 or more motor vehicles.

By comparison, this unified SCATS archive already contains a confirmed total of 539,020,710,239 cleaned vehicle movement events. That contrast helps explain why traffic-system analytics operate at a completely different scale from simple vehicle ownership statistics: the archive is measuring repeated interaction with the road network over time, not just the number of vehicles that exist.

Interpretation note: A “vehicle event” is not the same thing as a unique vehicle. The same vehicle may appear repeatedly in traffic counts across many intersections, many trips, and many years. This is why network-scale event totals can rise into the hundreds of billions even though the registered vehicle fleet is measured in the millions.

Historical Event Overlay

Future work: this section is reserved for overlaying major Melbourne events onto the completed traffic timelines. Candidate overlays include lockdowns, public holidays, major sporting events, weather disruptions, infrastructure works, incidents and other city-scale movement disruptions.

COVID Traffic Recovery Intelligence

This section compares six selected Melbourne SCATS network days across the COVID era: a 2019 pre-COVID baseline, 2020 lockdown shock, 2021 disruption, 2022 recovery, 2024 recent normal, and the 2025 busiest detected day.

The purpose is not just to show a historical dip. It shows how the daily shape of Melbourne movement changed, which hours collapsed hardest, which locations lost traffic, and which sites later over-recovered above the pre-COVID reference point.

2019 baseline: 129.9M movements 2020 lockdown: 86.7M movements 2025 busiest: 160.0M movements 2.29M chart rows • 4,278 mapped SCATS sites

Lockdown collapse

66.7 index

The selected 2020 lockdown day carried roughly two-thirds of the 2019 baseline movement.

Recovered above baseline

101.6 index

By the selected 2022 recovery day, network volume was slightly above the 2019 reference.

Recent normal

108.3 index

The 2024 comparison day sits materially above the pre-COVID baseline.

2025 busiest day

123.1 index

The busiest detected 2025 day was about 23.1% above the 2019 baseline comparison day.
Behavioural collapseThe lockdown day did not merely reduce volume; it flattened the daily rhythm, especially through the commuter and evening periods.
Recovery was unevenMany sites returned close to baseline, while selected growth-corridor and outer-suburban sites pushed well beyond 2019 levels.
Daily shape mattersThe 24-hour overlay and heartbeat heatmap show when the city was moving, not just how much it moved.
Location intelligenceThe site-level collapse and growth rankings convert citywide recovery into specific intersections, corridors, and commercial locations.

COVID Traffic Comparison Dashboard

Executive summary of the six comparison days, including the 2019 baseline, 2020 lockdown collapse, 2025 busiest day, and active mapped SCATS sites.

COVID traffic comparison dashboard showing baseline, lockdown, 2025 busiest day and active mapped sites

Total Volume Across COVID Comparison Days

Shows the raw citywide total vehicle movements for each selected historical day, making the 2020 drop and later recovery immediately visible.

Melbourne traffic volume across COVID comparison days

COVID Traffic Recovery Index

Normalises the comparison days against the 2019 baseline. Values below 100 show collapse; values above 100 show recovery or growth.

COVID traffic recovery index where 2019 baseline equals 100

24-Hour Melbourne Traffic Shape

Compares the full day in 15-minute bins. This reveals how lockdown changed the shape of the city, not just the total number of vehicles.

24 hour traffic shape overlay for COVID comparison days

Melbourne COVID Traffic Heartbeat Heatmap

A compact visual heartbeat of the city: each row is a comparison day, each column is a 15-minute time bin, and darker colour means heavier movement.

COVID traffic heartbeat heatmap by time of day and comparison period

Hourly Traffic Change vs 2019 Baseline

Shows which hours fell below the pre-COVID baseline and which hours later exceeded it. This is especially useful for understanding changed work, nightlife, freight, and commuter patterns.

Hourly traffic percentage change compared with the 2019 baseline

SCATS Site Shock vs Recovery Scatter

Each dot is a SCATS site. The x-axis shows how much traffic remained during lockdown compared with 2019, while the y-axis shows how strongly the site had recovered or over-recovered by the 2025 busiest day.

SCATS site shock versus recovery scatter plot

Top 30 Sites by Absolute Traffic Collapse

Ranks the SCATS sites with the largest absolute traffic loss on the selected 2020 lockdown day compared with the 2019 baseline.

Top 30 SCATS sites by absolute traffic collapse during lockdown

Top 30 Sites by Post-COVID Growth

Ranks locations that grew most above the 2019 baseline by the 2025 busiest detected day, highlighting growth corridors and changed movement demand.

Top 30 SCATS sites by post-COVID growth

Active Mapped SCATS Sites by Comparison Day

Shows the number of mapped SCATS sites with usable non-zero volume after the coordinate join for each comparison day.

Active mapped SCATS sites by COVID comparison day
Interpretation: the COVID comparison is powerful because it turns Melbourne traffic data into a behavioural history of the city. It shows lockdown collapse, structural recovery, outer-corridor growth, and the return of daily movement intensity in a way that can be understood by journalists, transport planners, advertisers, property analysts, and the general public.

For Journalists and Media

📄 Export For Journalists and Media as PDF
Purpose of this section:
This page is designed to help journalists, editors, researchers, and public-interest writers quickly turn Department of Transport SCATS data into clear, evidence-based traffic stories. The charts, rankings, maps, and datasets below provide ready-made leads for articles about Melbourne traffic history, peak demand, disruption, recovery, growth, and local infrastructure pressure.

The headline ideas below are directly supported by data and visualisations already integrated into this page. Each idea links to the section where the supporting chart, ranking, map, or dataset can be inspected.

Major City-Level Stories

Local and Infrastructure Stories

Data-Driven Feature Angles

Media usage note: The charts and datasets on this page are intended to make public-interest traffic reporting easier. Reporters can use the linked sections to verify claims, identify local angles, compare time periods, and request follow-up analysis based on the same processing pipeline.

The Traffic Intelligence Story Engine

This is not a single static report.
It is an ongoing analytical engine capable of generating new datasets, new charts, and new story angles as additional Department of Transport SCATS data becomes available. The value of the platform increases each time new data is processed through the same validated workflow.

The Melbourne SCATS Unified Analysis system has been developed as a reusable, script-driven platform. It can ingest, clean, deduplicate, aggregate, and visualise large-scale traffic signal volume data using repeatable processing steps. That means the page can evolve from a one-off analysis into a continuing source of traffic intelligence for journalists, researchers, councils, infrastructure observers, and the public.

1. New SCATS DataFresh Department of Transport files are added to the archive.
2. V3 ProcessingChunked, restart-safe scripts clean and aggregate the records.
3. Chart GenerationUpdated PNG charts, tables, rankings, and JSON summaries are produced.
4. Story DiscoveryNew records, anomalies, growth zones, and behavioural shifts are identified.

Ongoing Story Types

new busiest days new peak-time shifts new growth corridors traffic shock detection holiday pattern changes suburb-level local angles

Reusable Processing Capability

  • Month-by-month restart-safe execution
  • Large-scale aggregation across billions of 15-minute observations
  • Repeatable CSV, JSON, chart, and map outputs
  • Modular scripts that can be expanded as new questions emerge
  • Direct linkage between questions, charts, and supporting datasets

Why It Matters

Most public traffic reporting is episodic: one report, one story, one chart. This system is different. It creates a continuing analytical base where each new dataset can be compared against more than a decade of historical movement patterns.

Key concept:
This page is best understood as a traffic intelligence engine. It does not merely describe the past; it creates a framework for discovering future traffic stories as Melbourne changes.

Future Story Potential

Long-term capability: Because the architecture is modular and script-driven, the platform can continue producing new analytical outputs without redesigning the page. New charts, story ideas, downloadable datasets, and question-to-answer links can be added as the system matures.

Media Highlights and Public-Facing Insights

📄 Export Media Highlights and Public-Facing Insights as PDF

Most Newsworthy Daily Traffic Event

Friday 12 December 2025 — 166,208,622 movements

Busiest Day in Melbourne Traffic History

Friday 12 December 2025 — 166,208,622 movements

Quietest Day in Melbourne Traffic History

Use the Confirmed Daily Totals and calendar heatmap sections for the lowest validated daily result.

Top Daily Story Angle

Friday has emerged as a major strength point in Melbourne movement behaviour.

Top 10 Traffic Surprises

  1. Friday now appears stronger than many traditional weekday assumptions would suggest.
  2. The network peak is concentrated around the late afternoon, especially near 17:15.
  3. AM and PM peak windows together account for a very large share of daily movement.
  4. COVID-era disruption and recovery are visible across multiple chart layers.
  5. Site 4415 — PRINCES NR CANNING — dominates the loaded site ranking.
  6. Top SCATS sites can be linked directly to parcel and OOH opportunity discovery.
  7. Weekday/weekend splits create immediate campaign scheduling intelligence.
  8. Monthly and seasonal patterns now support public story generation.
  9. Processing evidence shows the platform was built from real large-scale compute work.
  10. The page now acts as a reusable media story engine, not just a data dump.

Department of Transport and Institutional Observations

This section presents structured observations derived from the unified Melbourne SCATS analysis layer. It is written for transport authorities, infrastructure planners, data teams, policy advisers and public-interest analysts who need to understand what the network is doing at system scale, not merely at isolated intersections.

Cleaned 15-Minute Observations

37,877,397,311

Distinct SCATS Sites

4,907

Loaded Date Range

2014-01-01 → 2026-04-07

Total Cleaned Movements

539,020,710,239

Busiest Network Time Bin

17:15

Busiest Recorded Day

2025-12-12

Institutional reading: the main value of this work is not simply that SCATS records were counted. The value is that raw operational traffic data has been transformed into a cleaned, deduplicated, queryable and explainable public intelligence layer capable of supporting repeatable planning questions.

1Network structure is highly predictable

The completed time-bin analysis confirms 17:15 as the strongest average network-wide 15-minute interval, while 03:00 is the quietest. This shows the network has a stable daily rhythm rather than random demand behaviour.

Planning implication: many operational interventions can be tested against repeatable historical patterns rather than treated as one-off events.

2Peak demand is structurally embedded

The PM peak is the dominant traffic period, accounting for 17.81% of all movements compared with 16.91% for the AM peak.

Planning implication: evening network pressure deserves particular attention in demand management, signal timing, corridor planning and incident-response modelling.

3A small number of nodes carry strategic load

The site-intelligence layer identifies SCATS 4415 — PRINCES NR CANNING as the current busiest loaded site, with 674,498,771 total movements.

Planning implication: the highest-ranked nodes should be treated as strategic pressure points, not ordinary intersections.

4Daily demand can be quantified at civic scale

The completed daily totals process identifies Friday 12 December 2025 as the busiest recorded day, with 166,208,622 cleaned movements.

Planning implication: the archive supports event detection, abnormal-day analysis and public explanations of exceptional traffic behaviour.

5Long-run records expose data gaps and partial periods

The archive spans more than 12 years and includes known caveats such as 2018-12 as a zero-volume data-gap month and 2026-04 as a partial month because the dataset ends on 2026-04-07.

Planning implication: publishing analysis with caveats improves trust and avoids overstating precision.

6Cleaning turns operational data into institutional intelligence

The unified cleaned layer contains 0 remaining negative cleaned rows after processing, allowing the dataset to be used for higher-level reporting, ranking and map generation.

Planning implication: the institutional value is unlocked by repeatable transformation, not merely by collecting traffic records.

Planning-Relevant Observation Matrix

ObservationEvidence in this pageInstitutional relevanceSuggested next analysis
Stable daily rhythm17:15 busiest; 03:00 quietestSupports repeatable time-of-day modellingCompare weekday, weekend and school-holiday profiles
PM peak dominance17.81% PM peak share vs 16.91% AM peak shareHighlights evening pressure as a priority planning windowSplit by corridor, region and site tier
Strategic node concentrationTop site: SCATS 4415, 674,498,771 movementsIdentifies sites where small failures may create large effectsRank top nodes by growth, volatility and incident sensitivity
Exceptional day detection2025-12-12: 166,208,622 cleaned movementsCreates a basis for explaining unusual network daysLink abnormal days to incidents, weather, events and roadworks
Long-run coverage2014-01-01 to 2026-04-07 across 4,907 sitesAllows multi-year trend analysis rather than snapshot reportingBuild site-level growth and decline classifications

Recommended Institutional Uses

1. Network performance briefingsUse the cleaned summary outputs to create repeatable monthly or quarterly public-facing network performance updates.
2. Corridor prioritisationRank corridors by volume, peak share, growth, instability and incident sensitivity rather than by anecdotal pressure.
3. Public transparency dashboardsTranslate raw SCATS records into accessible charts and maps so the public can understand how Melbourne moves.
4. Event and incident reviewUse abnormal daily totals and time-bin deviations to identify days where the network behaved outside its expected pattern.
5. Investment validationCompare pre- and post-project movement patterns across affected corridors to test whether infrastructure changes produced measurable shifts.
6. Data quality governanceMaintain a visible register of caveats, partial months, zero-volume periods and cleaning rules so analytical outputs remain auditable.
Closing institutional note:
These observations are derived independently from publicly available SCATS data. They demonstrate that large-scale traffic intelligence can now be generated outside traditional institutional workflows when raw data, high-performance processing, statistical cleaning, mapping and public communication are combined into a single repeatable system.

Public Dashboard Insights

This section translates the large-scale SCATS analysis into plain-English guidance for the general public: when Melbourne traffic usually builds, when it is most intense, and when travel is typically easier.

Public takeaway:
Melbourne traffic is not random. Across the cleaned SCATS archive, the city follows a highly structured daily rhythm: a morning build-up, a steadier daytime period, a stronger afternoon/evening peak, and then a clear overnight fall-away.

Strongest Current Peak

17:15

Current completed time-bin profile leader from the running aggregate.

Most Predictable Pressure

Weekday AM & PM Peaks

The recurring commute pattern is the easiest for the public to understand and plan around.

Best General Travel Window

Outside Peak Periods

Mid-morning, early afternoon and later evening are generally more forgiving than peak commute windows.

Quietest Network Period

Overnight / Early Morning

Lowest general movement occurs when commuter, school and freight pressures are reduced.

Average Commute Pressure by Time of Day

The public-facing commute-pressure profile should be based on the 96 daily 15-minute bins. Once the final profile script completes, this card can display the generated chart directly.

Time WindowTypical Public InterpretationPressure Level
Overnight to early morningLowest general traffic pressure; best suited to unavoidable long cross-city travel.Low
Morning commuteTraffic builds quickly as commuter and school movement enter the network.High
Midday / early afternoonMovement remains active but usually becomes less intense than the main commute peaks.Moderate
Afternoon / evening commuteThe strongest current completed profile point is around 17:15, making this the clearest public warning window.Very High
Later eveningTraffic pressure falls away as commuter demand clears.Lower

Chart target: replace with commute_pressure_profile.png once the final 96-bin profile image is generated.

Typical Melbourne Traffic Day

A normal Melbourne traffic day behaves like a daily pulse: low overnight movement, morning acceleration, a daytime plateau, a stronger afternoon peak, then evening decline.

1. Quiet Start

Overnight and very early morning movement is comparatively light.

2. Morning Build

Commuter and school activity pushes the network upward.

3. Daytime Plateau

Volumes remain active but less concentrated than peak windows.

4. Afternoon Peak

The network reaches its strongest daily pressure, currently led by the 17:15 bin.

5. Evening Release

Pressure declines as work, school and shopping trips clear.

Chart target: replace with typical_day_profile.png once the final public-friendly daily profile graphic is exported.

Best and Worst Travel Times

This guidance-style summary gives the public a simple way to interpret the statistical profile without needing to understand SCATS data, SQL, DuckDB or detector-level aggregation.

Public QuestionPlain-English Answer
When is traffic usually worst?During the afternoon/evening commute, with the current completed profile led by 17:15.
When should people avoid optional travel?The main weekday commute windows, especially the afternoon peak when multiple trip types overlap.
When is travel generally easier?Outside the main peaks: mid-morning, early afternoon, later evening, and overnight.
What is the simplest rule?If the trip is flexible, avoid the school/commuter peaks and favour the shoulders of the day.
What should be added next?A downloadable best_worst_travel_times.csv generated directly from the final 96-bin profile.
Public dashboard status: this section is now ready for publication as explanatory guidance. The final visual polish should be to insert the generated commute-pressure and typical-day PNG charts after the time-bin profile script completes.

Academic and Research Opportunities

This section highlights the research value of the cleaned Melbourne SCATS archive for universities, research groups, transport economists, policy teams, and infrastructure analysts. The archive is not only useful for reporting what Melbourne traffic does; it can also support research into why the network behaves that way, how stable those behaviours are, and which policy interventions may shift demand.

Research positioning: A 2014–2026, 15-minute interval traffic archive gives researchers a rare longitudinal view of how Melbourne's signalised road network behaves across years, weekdays, seasons, infrastructure changes, and disruption periods.

Long-Term Traffic Growth Trends

Multi-year SCATS coverage from 2014–2026 enables longitudinal modelling of Melbourne traffic growth, structural demand shifts, before-and-after infrastructure studies, and corridor-level comparisons.

  • Identify sites with sustained growth, decline, or plateauing demand.
  • Compare pre- and post-infrastructure change periods.
  • Measure how traffic demand shifts across corridors rather than relying on isolated snapshots.

Research outputs: growth rankings, monthly trend profiles, site-level time series, before/after comparison tables.

Network Stability Metrics

The 96-bin daily structure is ideal for studying volatility, repeatability, reliability, and peak-period stability across the network. Melbourne's traffic rhythm can be tested as a measurable system rather than described only anecdotally.

  • Measure how consistently peak periods recur.
  • Detect abnormal days, disruption signatures, and corridor instability.
  • Compare weekday, weekend, school holiday, and seasonal network behaviour.

Research outputs: volatility scores, confidence bands, recurring peak metrics, abnormal-day detection.

Policy Simulation Inputs

The cleaned and unified dataset can support simulation-based research into traffic demand, infrastructure policy, freight movement, public transport substitution, and network response to incidents or major projects.

  • Model staggered work hours and peak-spreading effects.
  • Test congestion pricing, freight priority, and incident-response scenarios.
  • Provide baseline demand inputs for transport modelling and forecasting.

Research outputs: scenario input tables, baseline demand curves, policy sensitivity comparisons.

Open Research Pathway

The project can support university projects, honours or postgraduate transport studies, public-policy research, and independent reproducibility work by exposing cleaned outputs, documented assumptions, and repeatable analysis scripts.

  • Useful for transport engineering, urban planning, data science, GIS, and public-policy courses.
  • Supports reproducible research from public-sector source data.
  • Creates a bridge between open data, media reporting, and formal academic analysis.

Future upgrade: add sample CSV downloads, schema notes, and example SQL queries for researchers.

Academic value statement: This archive provides a practical foundation for studying Melbourne's traffic system as a long-running, high-resolution behavioural dataset. It can be used to examine growth, reliability, corridor pressure, policy interventions, and the public value unlocked when raw transport data is cleaned, validated, and made understandable.

Public Intelligence, Open Data and Open Source Direction

📄 Export Public Intelligence Statement as PDF
Public intelligence statement:
This SCATS + TIRTL platform could have been kept private, packaged as a paid dashboard, or sold as a proprietary transport-data product. Instead, the core findings, maps, methodology notes, data dictionaries and downloadable outputs are being made public because Melbourne’s traffic data has civic value as well as commercial value.

The purpose of this project is not simply to display traffic data. It is to turn raw public transport datasets into usable public intelligence for residents, journalists, councils, researchers, freight/logistics observers, OOH media, transport operators, developers and the general public.

Many practical traffic questions remain unanswered because the relevant data is difficult to locate, slow to process, or locked inside specialist workflows. By building compact data dictionaries, known-question guides, downloadable CSV/JSON outputs, public evidence pages and repeatable scripts, this platform makes it possible to move from a community question to a first-pass evidence response in minutes rather than days, weeks or months.

Public Access Principle

Open by default

Evidence Layer

SCATS + TIRTL

Response Model

Question → dataset → answer

Public Users

Residents, media, councils

Commercial Users

OOH, freight, property

Methodology

Inspectable outputs

Data Dictionaries

AI-ready context

Future Direction

Traffic AI Analyst

Why this matters:
Releasing data is not the same as making it understandable. The public charts show what changed; the dictionaries, downloads and methodology notes explain where the evidence came from, what it can prove, and what further data would be required. This turns open transport data into a practical civic intelligence layer.

The data dictionaries are especially important because they transform a large archive of CSV, JSON, chart, map and HTML outputs into a searchable analytical system. Instead of guessing which file answers a question, the project can identify the relevant dataset, inspect the available columns, explain the caveats, and produce a defensible first-pass evidence brief.

This is the principle behind the project: public transport data should not merely be released — it should be made understandable, testable, downloadable and useful.

Guiding statement:
The Department of Transport may release the data, but the public also deserves the intelligence.

🤝 Project Supporters & Sponsors

This independent Melbourne traffic intelligence project is privately built, processed, hosted, and maintained. Organisations that support the project help keep the public analytics, charts, maps, downloads, and technical documentation available for journalists, researchers, transport analysts, students, businesses, and the wider public.

Downloadable Data and Reports

📄 Export Downloadable Data and Reports as PDF

The page now references a broad set of downloadable and reproducible assets: core SCATS time-series outputs, daily/monthly totals, temporal behaviour profiles, site/corridor/OOH intelligence outputs, chart PNGs, scripts, map exports, animation files and reproducibility metadata.

Download status: the download layer should prioritise public-ready CSVs, JSON metadata, chart PNGs, scripts, map exports, animation files and reproducibility outputs.

Complete SCATS Chart Archive

Download a single ZIP archive containing the chart images currently referenced on this page. This is useful for journalists, researchers, OOH media analysis, offline review and report preparation.

📦 Download All SCATS Charts ZIP

SCATS Animation Archive

Download the complete animation archive containing Kepler.gl movement animations, 24-hour traffic pulse visualisations, COVID recovery sequences, time-bin animations, and other motion-based Melbourne traffic intelligence outputs referenced on this page.

🎞️ Download All SCATS Animations ZIP

Kepler.gl Interactive Map Exports

Kepler.gl export note: Upload these three interactive HTML map files and three PNG exports into the same web directory as this page so the embedded preview and download links resolve correctly.

Reproducibility and Scientific Confirmation

Reproducibility sits at the heart of serious scientific work. A large statistical result becomes much more persuasive when other scientists, engineers, analysts, and institutions can independently inspect the same databases, run the same processing scripts, and confirm that they reach the same or very similar results.

High-performance computing methodology: The compute architecture behind this platform reflects techniques more commonly associated with high-performance computing (HPC) and large-scale analytical systems. Rather than relying on institutional supercomputers, the workflows were engineered using commodity hardware, resumable month-by-month processing, logical deduplication layers, heavy DuckDB aggregation pipelines, staged spill-to-disk strategies, and long-running fault-tolerant analytical workflows — effectively creating a “poor man’s supercomputer” for Melbourne-scale traffic intelligence.

Generated Processing-Time Chart

Processing Time by Completed CSV

Chart showing the relative cost of each completed CSV workflow.

Melbourne SCATS traffic analysis chart showing Processing Time By Completed Csv from 2014 to 2026
Why confirmation by other scientists matters:
Independent confirmation reduces the chance of hidden errors, increases confidence in the published outputs, and helps distinguish robust findings from one-off analytical mistakes. In practical terms, it means that a transport engineer, statistician, journalist, university researcher, or government analyst should be able to inspect the archive, run the workflow, and confirm whether the published totals, rankings, and charts are reproducible from the underlying data.
Reproducibility principle: This page is intended not only to present findings, but also to make those findings easier to verify. Where possible, the source databases, scripts, outputs, and workflow notes should be downloadable so external reviewers can repeat the analysis themselves.

Core SCATS Databases

3 DuckDB archives

Core Processing Scripts Listed

V3 headline workflow included

Wrapper Scripts Listed

V3 merge wrapper included

Logs Folder

Included in workflow structure

Scientific Standard

Independent confirmation encouraged

Archive Footprint

102.7 GB on disk

Download the SCATS Databases

These are the three core DuckDB archives used to build the unified cleaned analytical layer. Due to the very large archive sizes, bandwidth considerations and ongoing platform refinement, the databases are currently distributed manually rather than via direct public download.

Database access requests:

Author: Clarke Towson, BCMS (Bachelor of Computer & Mathematical Science)
Manager — Spotswood Trailers
Linux Systems Specialist & Former DST Group High Performance Computing Specialist

Call: +61 432 359 166
Email: clarke@spotswoodtrailers.com.au
Facebook: clarke.towson

The combined analytical environment currently spans approximately 98GB of DuckDB databases and underpins the reproducible SCATS diagnostics, coverage audits, deduplication evidence and cleaned movement analytics presented throughout this platform.

Processing Scripts and Reproducibility

The complete Melbourne SCATS Intelligence processing workflow is maintained publicly on GitHub, including DuckDB analytical scripts, chart-generation pipelines, diagnostics, data-quality auditing, month-by-month chunked processing wrappers and supporting documentation.

The repository is intended to provide transparency, reproducibility and independent verification of the analytical workflows powering this platform. External reviewers can inspect the processing logic, rerun analytical stages, validate outputs and review the engineering approach used to process more than 12 years of Melbourne SCATS data.

The platform combines DuckDB, HPC-inspired chunked execution workflows, reproducible CSV/JSON outputs, diagnostics, data-quality auditing and multi-database analytical infrastructure spanning more than 533 billion cleaned vehicle movements.

Core Python Scripts Currently Listed

ScriptRole in WorkflowDownload
generate_busiest_day_chunkedV3.pyComputes busiest day using chunked monthly processing.Download
generate_busiest_site_chunkedV3.pyComputes busiest SCATS site using the improved one-month-per-execution method.Download
generate_busiest_time_bin_chunkedV3.pyFinds the busiest 15-minute time bin across the archive.Download
generate_daily_totals_chunkedV3.pyBuilds day-level network totals.Download
generate_day_of_week_profile_chunkedV3.pyProduces day-of-week traffic profiles.Download
generate_growth_rankings_from_site_month_totals.pyComputes growth and decline rankings from site-month totals.Download
generate_monday_vs_friday_comparison.pyCompares Monday and Friday traffic behaviour.Download
generate_monthly_totals_chunkedV3_FIXED.pyBuilds month-level totals across the archive.Download
generate_month_of_year_profile_chunkedV3.pyCreates month-of-year traffic profiles.Download
generate_peak_hour_summary.pyProduces a peak-hour summary from derived outputs.Download
generate_peak_shares_chunkedV3.pyComputes peak-share metrics using chunked monthly processing.Download
generate_seasonal_chart_ready.pyFormats seasonal outputs for charts and publication.Download
generate_site_month_totals_chunkedV3.pyBuilds month totals per SCATS site.Download
generate_site_totals_chunkedV3.pyBuilds total traffic rankings by site.Download
generate_time_bin_profile_chunkedV3.pyCreates time-bin traffic profiles across the archive.Download
generate_top_10_months_of_year_by_avg_daily_volume.pyRanks strongest months of year by average daily volume.Download
generate_top_10_peak_time_bins.pyExtracts top peak time bins.Download
generate_top_10_sites_by_month_variability.pyFinds sites with strongest month-to-month variability.Download
generate_top_10_years_by_avg_daily_volume.pyRanks years by average daily traffic volume.Download
generate_top_20_busiest_days_from_daily_totals.pyExtracts the busiest days from daily totals.Download
generate_top_20_decline_sites_from_growth_rankings.pyExtracts top decline sites from growth rankings.Download
generate_top_20_growth_sites_from_growth_rankings.pyExtracts top growth sites from growth rankings.Download
generate_top_20_quietest_days_from_daily_totals.pyExtracts the quietest days from daily totals.Download
generate_top_50_sites_from_site_totals.pyBuilds top-50 site rankings from total site volumes.Download
generate_total_cleaned_volume_chunkedV2.pyComputes total cleaned volume across the archive.Download
generate_weekday_vs_weekend_chart_ready.pyFormats weekday-vs-weekend outputs for charts.Download
generate_weekday_weekend_split_chunkedV3.pyBuilds weekday/weekend split outputs.Download
generate_yearly_chart_ready.pyFormats yearly outputs for chart publication.Download
generate_yearly_totals_chunkedV3.pyBuilds yearly totals across the archive.Download
merge_headline_metricsV3.pyMerges derived outputs into a headline metrics layer for the page.Download

Wrapper and Launch Scripts Currently Listed

ScriptRoleDownload
run_busiest_site_until_done.ps1PowerShell wrapper for iterative busiest-site processing.Download
run_total_cleaned_volume_until_done.batBatch launcher for total cleaned volume runs.Download
run_total_cleaned_volume_until_done.ps1PowerShell wrapper for iterative total cleaned volume processing.Download

How external reviewers can confirm the work

  • Download the original, continuation, and recovery SCATS DuckDB archives.
  • Inspect the Python scripts used to create totals, rankings, and chart-ready outputs.
  • Run the scripts independently and compare generated CSVs and JSON summaries.
  • Check whether headline metrics, site rankings, and chart inputs can be reproduced.
  • Review logs and workflow notes to understand execution order and processing assumptions.

Suggested publication note

  • Independent confirmation is encouraged.
  • Transport engineers, statisticians, and scientists should be able to inspect the same archives and workflow.
  • Published claims become stronger when they are reproducible by external parties.
  • This section is intended to make the work easier to verify, critique, and improve.
Hosting note: The download links above use sensible relative paths for publication. If your final hosting structure differs, simply update the href targets to match your real downloads directory.

Data Confidence and Validation

📄 Export Data Confidence and Validation as PDF
Validation Summary: The platform is built on a cleaned, deduplicated SCATS analytical layer with negative sentinel values handled, null-cleaning recorded, 148/148 months processed in the main monthly pipeline, and major outputs cross-referenced by charts, CSVs, JSON metadata and runtime evidence.
Audit Evidence: Confidence is supported by resumable month-by-month workflows, completion metadata, processing-time charts, cleaned-volume totals, site totals, temporal profiles and reproducible scripts. The strongest confidence applies to measured historical aggregates; modelled OOH and commercial scenarios remain interpretive planning tools.

Data Transparency and Reporting Integrity

This section demonstrates transparency around data processing, assumptions, and reporting reproducibility. The workflows used in this system are designed to be repeatable, auditable, and resistant to data corruption or silent processing failures.

Data Processing Timeline

The following stages summarize the chronological evolution of the ingestion and transformation pipeline.

Stage Description Outcome
Raw File Acquisition Department of Transport SCATS CSV files were collected and organized into chronological year-based directories. Established structured source archive beginning from 2014-01-01 through 2026-04-07.
Primary Ingestion Chunked ingestion workflows processed daily CSV files into DuckDB tables using controlled batch loading strategies. Created primary database: scats.duckdb
Continuation Loading Additional ingestion passes processed remaining historical files and extended dataset coverage beyond the initial load. Created continuation database: scats_continuation.duckdb
Recovery Processing Failed or corrupted source files were isolated and reprocessed using dedicated recovery workflows. Created recovery database: scats_recovery.duckdb
Deduplication and Cleaning Duplicate detector-day records and invalid negative values were removed or normalized using deterministic cleaning logic. Produced unified analytical surface: scats_all_clean_dedup
Derived Dataset Generation Aggregated summaries were computed including monthly totals, daily totals, site-level traffic volumes, and peak-period distributions. Generated structured output CSV and JSON reporting artifacts.
Public Reporting Integration Processed outputs were integrated into visual dashboards, interactive maps, and downloadable public reporting pages. Delivered production-grade public traffic intelligence platform.

Data Provenance Summary

All datasets are derived from publicly released Department of Transport Victoria SCATS traffic signal volume archives. Transformation lineage is preserved through controlled database separation and structured pipeline execution.

Source Transformation Output
Raw SCATS CSV Files Schema Normalization scats.duckdb
Remaining CSV Coverage Extended Batch Processing scats_continuation.duckdb
Failed File Recovery Isolated Reprocessing scats_recovery.duckdb
All Clean Sources Deduplication & Validation scats_all_clean_dedup
Clean Analytical Surface Aggregation Pipelines Monthly, Daily, Site-Level Reports

Validation Run Logs

All major dataset generation processes were executed using repeatable chunked workflows. Each execution cycle validated progress against completed output records to prevent duplicate processing or silent failure loops.

Statistical Confidence and Error Bounds

The measured SCATS aggregates on this page have high internal confidence where they are derived directly from the cleaned, deduplicated pipeline and supported by completion metadata. The strongest claims are the historical totals, site totals, daily/monthly profiles and time-based behavioural outputs.

Interpretive layers — including OOH revenue scenarios, ROI models and future real-time comparison concepts — should be treated as planning models. Future TIRTL integration will improve corridor speed, vehicle-class and heavy-vehicle confidence.

Methodology

This page is intended to sit on top of a serious, multi-stage transport analytics workflow rather than a single one-off query. The SCATS and TIRTL databases were built through staged ingestion, schema design, recovery handling, cleaning, deduplication, validation, and repeatable reporting logic so that the resulting outputs can stand up to technical scrutiny.

Methodological position:
The objective was not merely to load traffic data, but to create a reproducible analytical system capable of supporting city-scale historical traffic intelligence, cross-checking, and later operational or public-facing reporting.

Methodology Overview Diagram

1. Public Source Files

SCATS CSV archives and TIRTL observations are collected and preserved as source evidence.

2. Staged Ingestion

Files are loaded into original, continuation, and recovery databases with source-file tracking.

3. Cleaning Rules

Negative placeholders and invalid readings are excluded from cleaned traffic totals.

4. Deduplication

Cross-database overlap is resolved before headline totals, rankings, and charts are generated.

5. Aggregation

Monthly, daily, site, peak-share, and time-bin summaries are produced through repeatable scripts.

6. Public Intelligence

Results become maps, charts, Top 10 findings, journalist notes, and downloadable public outputs.

1. Source Acquisition and Database Architecture

  • SCATS: multiple ingest phases were used to build the full archive, including an original load, a continuation load, and a separate recovery load for failed CSVs.
  • TIRTL: a separate SQLite-based corridor intelligence database was built for traffic count, classification, and speed behaviour, particularly suited to freeway and bridge analysis.
  • The SCATS environment uses a normalized metadata and fact-table structure including source_file, scats_site, scats_detector_day, and expected-date logic for coverage checks.
  • The TIRTL environment uses dedicated tables for raw observations, bridge-focused 15-minute summaries, and baseline comparison layers.
  • The architecture deliberately separates raw, cleaned, and analytical layers so that the original source record can remain intact while higher-quality reporting views are created above it.

2. Staged SCATS Ingestion Strategy

  • The SCATS archive was not treated as a single monolithic import. It was ingested in stages to make large-scale loading practical and auditable.
  • The first database captured the original ingest.
  • A continuation database captured the next phase of the archive as additional files were loaded.
  • A recovery database was then built specifically to process the files that had previously failed ingestion.
  • This staged design preserved observability: which files loaded, which failed, which were later recovered, and how the final analytical layer was assembled.
  • Source-file tracking was retained so the provenance of loaded data could be inspected rather than assumed.

3. Recovery Logic for Failed SCATS Files

  • A dedicated recovery ingest process was created to parse historical failure logs, locate failed CSVs on disk, and load them into a separate database using the same core schema.
  • This recovery path handled malformed dates more flexibly, reused site metadata, and updated source-file status so that recovered loads were properly recorded.
  • Internal duplicate rows within individual failed files were resolved before insertion by keeping one record per composite key.
  • This avoided contaminating the recovered database with duplicate detector-day rows while still salvaging usable data from previously problematic files.
  • The recovery layer was kept separate from the original and continuation layers so that its contribution could be understood and controlled during later unification.

4. Deduplication and Unified Query Layer

  • Rather than immediately performing a very large physical merge, the SCATS databases were attached logically and queried together in place.
  • A unified analytical surface was created through scats_all_clean_dedup, which combines cleaned interval rows from the original, continuation, and recovery databases.
  • Deduplication is performed with a row-number strategy partitioned by scats_site, count_date, detector, and interval_index.
  • A priority order was applied so that recovered data can override earlier failed or incomplete versions where overlap exists.
  • This yields one logical row per site, date, detector, and 15-minute interval without requiring an immediate high-risk physical merge of very large files.

5. Wide-to-Long Transformation and Interval Intelligence

  • Raw SCATS detector-day records store traffic counts in wide format as interval columns v00 through v95.
  • Those records were transformed into a long-format analytical view, scats_15min_long, so that every 15-minute interval becomes an explicit row.
  • This transformation was critical because wide storage hides important data-quality issues and makes time-of-day analysis much harder.
  • The long-format layer enabled direct inspection of interval indexes, time bins, missing values, unusual sentinel values, and time-of-day volume structure.
  • It also made later analysis possible for peak detection, volatility analysis, network profiles, anomaly work, and daily pattern reconstruction.

6. Cleaning Logic and Sentinel Handling

  • Negative interval values were identified in the SCATS data and investigated rather than ignored.
  • The frequency distribution of values such as -1022, -1023, and -1 strongly indicated that they were not genuine traffic counts but system markers for missing or invalid data.
  • Instead of overwriting raw source values, a separate cleaned analytical layer was created: scats_clean.
  • Within that layer, negative interval values are mapped to NULL, preserving the distinction between “zero traffic” and “invalid or unavailable traffic.”
  • This is analytically important because replacing faults with zero would distort peak patterns, averages, reliability calculations, and anomaly detection.

7. Validation and Integrity Checks

  • The databases were audited systematically rather than informally sampled.
  • Checks included: table inventories, row counts, date ranges, distinct site counts, null-key checks, duplicate-key checks, interval-index validation, time-bin coverage, negative-value audits, and orphan metadata checks.
  • Expected-date logic and missing-date logic were used to identify coverage gaps and distinguish between true archival gaps and simple reporting assumptions.
  • Primary-key integrity on scats_detector_day was tested directly, including duplicate excess estimation.
  • The long-format layer was used to verify that interval indexes ran correctly from 0 to 95 and that the expected 96 daily time bins were present.

8. Performance Engineering and Operational Design

  • At this scale, analytical correctness alone is not enough; workload shape matters.
  • Large unified queries were found to exceed memory and temp-spill limits when executed as one monolithic job, so the workflow was redesigned around chunked month-by-month processing.
  • This reduced failure risk, enabled real progress reporting, and made very large unified summaries feasible on workstation hardware.
  • Temporary spill was redirected to the drive with more available space, insertion-order preservation was disabled where safe, and thread counts were tuned conservatively for heavy workloads.
  • The final reporting strategy is therefore designed around staged CSV generation and reusable aggregates, not repeated full-history brute-force scans.

9. Why the Combined SCATS + TIRTL Approach Matters

  • SCATS provides high-value intersection and signal-layer intelligence: site-level flow, detector behaviour, peak timing, local demand, and daily pattern structure.
  • TIRTL adds corridor and bridge intelligence: counts, speeds, and vehicle-class behaviour, especially valuable for freeway and bridge analysis.
  • Together, the two systems move the analysis from isolated point measurements to network behaviour.
  • This means the platform can progress beyond “what is happening at one intersection?” to “how does demand move through Melbourne as a system, from local signals into strategic corridors?”
  • That combined architecture is what makes downstream questions about bottlenecks, congestion propagation, freight behaviour, network synchronization, and predictive traffic intelligence genuinely powerful.

10. Institutional Relevance

  • This methodology is designed to be legible not only to general readers, but also to technical reviewers in transport agencies, infrastructure teams, consultancies, and academic settings.
  • The key message is that the database was built through a disciplined pipeline: acquisition, staged ingestion, recovery, normalization, cleaning, deduplication, validation, and repeatable reporting.
  • The point is not merely that the system is large; it is that the analytical layer is traceable, reproducible, and methodologically serious.
  • That is what allows outputs from the system to support not just exploratory charts, but potentially high-value operational, strategic, and public-interest traffic intelligence.

Data Quality, Cleaning and Deduplication Evidence

📄 Export Data Quality Section as PDF

This section documents the raw data-quality checks behind the cleaned SCATS outputs. It shows why the public charts should not be treated as a simple dump of raw SCATS tables: the platform performs structural validation, duplicate-key checks, interval quality auditing, and negative/sentinel-value detection before producing public analytical outputs.

401,123,083Detector-day rows scanned
533.486BMovement total in quality scan
0Duplicate detector-day keys found
0Duplicate rows involved
1,205,268,529Negative interval cells detected
704,560,054Sentinel interval cells detected
37,532,313Null interval cells detected
12.92 minQuality scan runtime
Most important integrity finding: across 401,123,083 detector-day rows, the duplicate detector-day key scan found zero duplicate keys. For this audit, the detector-day key is scats_site + detector + count_date.
Why the cleaning layer matters: the raw interval columns contain large numbers of negative and sentinel-coded values. The scan detected 1,205,268,529 negative interval cells and 704,560,054 sentinel interval cells. These are exactly the kinds of values that require interpretation before producing cleaned movement totals and public-facing charts.

1. Database Contribution Summary

Contribution of each DuckDB database to the quality scan.

DatabaseDetector-day rowsMovement totalStartEndSite-detector pairs
scats200,220,982294.945B2014-01-012021-07-11104,081
scats_continuation189,625,146219.807B2021-07-122026-04-07122,082
scats_recovery11,276,95518.734B2014-03-022022-05-08106,554

2. Duplicate Detector-Day Key Summary

Duplicate-key evidence by database. The result is clean: no duplicate detector-day keys were found in this scan.

DatabaseDuplicate keysRows involvedMax rows for one key
scats000
scats_continuation000
scats_recovery000

Interval Quality Evidence

The detector-day schema stores 96 15-minute columns per day (v00 to v95). This audit scans every interval column for nulls, negative values and known sentinel values. It provides direct evidence that the cleaned reporting layer is necessary.

3. Highest Negative/Sentinel Interval Rates

Time binColumnNegative cellsNegative %Sentinel cellsSentinel %
02:15v0912,857,0503.205%7,584,1921.891%
00:15v0112,844,7153.202%7,666,9551.911%
11:45v4712,842,9393.202%7,424,6961.851%
02:45v1112,833,7873.199%7,558,6911.884%
02:00v0812,812,6573.194%7,584,0341.891%
14:15v5712,785,9453.188%7,445,2171.856%
02:30v1012,770,7473.184%7,568,7851.887%
00:45v0312,749,1763.178%7,485,0551.866%

4. Highest Null Interval Rates

Time binColumnNull cellsNull %
21:15v85844,8730.211%
21:30v86824,5790.206%
22:15v89821,3520.205%
22:00v88819,4880.204%
21:45v87798,4980.199%
22:30v90792,6010.198%
22:45v91774,0680.193%
21:00v84764,1110.190%

5. Monthly Quality Flags

A simple detector-day row-count z-score test highlights months with unusually low or high structural volume. These are engineering flags, not public traffic conclusions.

MonthDetector-day rowsDays presentZ-scoreFlag
2026-04824,9577-3.09Low row-count flag
2021-074,090,310202.21High row-count flag

6. Site-Detector Stability

Summarises how long site-detector pairs remain active inside each database segment.

DatabaseSite-detector pairsAvg active daysMedian active daysMax active daysMovement total
scats104,0811923.72566.02,568294.945B
scats_continuation122,0821553.31724.01,725219.807B
scats_recovery106,554105.8155.015518.734B

Slowest Data-Quality Queries

These timings document the real operating cost of the data-quality layer and show which checks are computationally expensive.

DatabaseQueryElapsed
scats_continuationmonthly_quality_summary2.51 min
scatsinterval_quality_scan1.53 min
scats_continuationinterval_quality_scan1.35 min
scats_continuationduplicate_detector_day_key_summary1.34 min
scats_continuationsite_detector_stability_summary1.33 min
scatssite_detector_stability_summary30.009 sec
scatsmonthly_quality_summary27.066 sec
scatsduplicate_detector_day_key_summary14.319 sec
scats_recoverymonthly_quality_summary12.522 sec
scats_recoverysite_detector_stability_summary11.675 sec

Downloadable Data-Quality Outputs

Why this matters: the quality evidence shows that the public SCATS outputs are the result of a validated data-engineering workflow, not a direct visualisation of raw files. The zero duplicate-key result strengthens trust in the detector-day structure, while the negative/sentinel interval counts demonstrate why cleaning and careful interpretation are essential.

Database Diagnostics and Structural Statistics

📄 Export Database Diagnostics Section as PDF

This section documents the physical SCATS analytical environment behind the public charts. It is intended for developers, data journalists, transport analysts, government readers and anyone who wants to verify that the platform is not just a visual dashboard, but a large, structured, reproducible database-backed analytical system.

97.95 GBCombined DuckDB file size
401,123,083Detector-day rows scanned
533.486BVehicle movements in diagnostic scan
2014-01-01 → 2026-04-07Database coverage window
13Base tables catalogued
6Views catalogued
424Columns catalogued
0Unexplained missing months in V3 audit
0Errors across V1 + V2B + V3 diagnostics
Important distinction: the diagnostic movement total above comes from the physical scats_detector_day tables across the three DuckDB files. The headline cleaned movement figure elsewhere on this page is produced by the completed cleaned/deduplicated reporting workflow. This diagnostics section documents database structure, coverage and operational scale.
Runtime result: the structural V2B diagnostic scan completed in 585.1 seconds while scanning 401,123,083 detector-day rows across three databases, including monthly/yearly coverage, regional summaries, source-file summaries and 96 interval-column completeness checks. The V1 schema inventory completed in 1.214 seconds.

1. Multi-Database Architecture

The platform currently uses three DuckDB files: the original SCATS ingest, the continuation ingest, and a recovery database for failed/edge-source material.

DatabaseSizeDetector-day rowsMovement total
scats59.33 GB200,220,982294.945B
scats_continuation35.58 GB189,625,146219.807B
scats_recovery3.04 GB11,276,95518.734B

2. Largest Base Tables

These row counts establish the physical scale of the analytical environment before any public-facing charting is considered.

DatabaseTableRows
scatsscats_detector_day200,220,982
scats_continuationscats_detector_day189,625,146
scats_recoveryscats_detector_day11,276,955
scats_continuationscats_site5,436
scats_recoveryscats_site5,165
scatsscats_site5,001
scats_recoveryscats_expected_date2,990
scatssource_file2,724

Structural Coverage by Year

The yearly structural coverage table gives an audit-style view of database coverage. The dedicated V3 month audit below is now the clearest reference for calendar completeness because it compares an explicit expected-month calendar against all three SCATS DuckDB databases.

V3 month audit result: the dedicated month-coverage audit confirms 148 expected months across the 2014-01-01 → 2026-04-07 analysis window, with 147 detected months, 1 known unavailable month, and 0 unexplained missing months. The only known unavailable month is 2018-12.

Structural Coverage Interpretation Note

The earlier low-level structural table is useful for understanding how detector-day material is distributed across the physical ingest architecture, but the dedicated V3 month audit is the clearer authority for calendar coverage.

The V3 audit explicitly constructs the expected month calendar from 2014-01-01 to 2026-04-07, then compares that calendar against detected months across all three DuckDB databases: scats.duckdb, scats_continuation.duckdb, and scats_recovery.duckdb.

  • No unexplained missing months were found.
  • 2018-12 is the single known unavailable monthly ingest source and is disclosed transparently.
  • 2026 is naturally partial because the dataset currently ends on 2026-04-07.
  • The finalized yearly movement totals and yearly comparison charts elsewhere on this page remain the authoritative polished analytical outputs.

This section therefore serves as an audit-style engineering view of the database structure and coverage, not merely a polished presentation layer.

V3 Authoritative Month Coverage Audit

This table is the preferred coverage reference. It resolves the ambiguity from lower-level ingest diagnostics by comparing an explicit expected month calendar against detected months across the full multi-database SCATS environment.

Year Expected months Detected months Known unavailable months Unexplained missing months Diagnostic movement total Audit note
201412120040.318B
201512120040.985B
201612120042.605B
201712120043.261B
201812111040.213B2018 includes known unavailable monthly ingest source: 2018-12.
201912120045.474B
202012120036.951B
202112120042.036B
202212120045.138B
202312120046.767B
202412120048.049B
202512120048.761B
2026440012.928BFinal year is naturally partial because the current dataset ends on 2026-04-07.

Known Missing or Unavailable Month Audit

MonthStatusNote
2018-12Known unavailableOne monthly ingest source was unavailable and is disclosed transparently.

Lower-Level Detector-Day Structural Table

The table below remains useful as a detector-day structural view, but it should be read alongside the V3 audit above. Its “Distinct ingest months detected” field reflects the lower-level grouping behaviour of the diagnostic query and is not the final coverage authority.

YearDetector-day rowsDays presentDistinct ingest months detectedDiagnostic movement total
201425,690,1003651240.318B
201525,179,7083631240.985B
201625,045,9483631242.605B
201724,939,7423601243.261B
201823,343,754207740.213B
201930,468,5473581245.474B
202036,320,9023621236.951B
202138,232,647191742.036B
202238,283,6533631245.138B
202339,717,7783641246.767B
202440,769,5283651248.049B
202541,729,3523631248.761B
202611,401,42497412.928B

3. Regional Coverage

Top regions by detector-day rows. This confirms that the database can be inspected geographically, not just city-wide.

RegionDetector-day rowsSite count sumMovement total
GEE19,724,00473020.727B
FRA17,939,55257722.796B
VIC16,872,35769413.583B
MEN16,407,99652221.994B
CRN15,727,45148720.286B
SPR15,707,47247421.604B
GRE14,707,63753822.471B
BBN14,105,28842921.861B
WV113,860,84643818.919B
WV213,577,99141222.386B

4. 15-Minute Interval Completeness

The detector-day schema contains v00 through v95, representing 96 15-minute bins per day. The V2B diagnostic scan checked non-null coverage across every interval column without exploding the database into long format.

99.789%Minimum interval coverage
99.903%Average interval coverage
99.981%Maximum interval coverage

5. Source-File Structure

The source-file summary found 4,446 database/source-file group records across the three databases. The largest source-file grouping was in scats with 138,584 detector-day rows.

6. Slowest Diagnostic Queries

These timings help document the real operating cost of the diagnostic layer.

DatabaseQueryElapsed
scats_continuationsource_file_summary189.090s
scats_continuationmonthly_coverage45.086s
scatsinterval_non_null_check44.132s
scats_continuationinterval_non_null_check35.539s
scats_continuationyearly_coverage8.643s
scatsmonthly_coverage8.320s
scatsregion_coverage5.872s
scats_continuationregion_coverage5.398s

Downloadable Diagnostic Outputs

The diagnostics section is backed by generated CSV and JSON files, making the database inventory reproducible and auditable.

Why this matters: the public charts show the story; this section shows the machinery. The combination of schema inventory, row-count evidence, interval-column checks, coverage windows, and zero-error diagnostics helps technical audiences understand that the SCATS platform is an engineered analytical environment rather than a collection of static images.

Detected Database Schemas

The SCATS reporting system is now documented as a three-database DuckDB archive. The original, continuation, and recovery databases feed the unified cleaned analytical layer used by the public charts, tables, maps, rankings, peak-share analysis, and headline traffic findings.

Schema milestone:
The placeholder schema section has now been replaced with the detected SCATS database names, table inventory, core table definitions, index strategy, and the role of the unified analytical surface scats_all_clean_dedup. This makes the page easier for journalists, researchers, transport analysts, and technical reviewers to audit.

Primary SCATS DB

scats.duckdb

Continuation SCATS DB

scats_continuation.duckdb

Recovery SCATS DB

scats_recovery.duckdb

Core Fact Table

scats_detector_day

15-Minute Model

v00–v95 / scats_15min_long

Index Pattern

7 core indexes per DB

Three Coordinated SCATS DuckDB Archives

DatabaseRoleDetected ObjectsNotes
scats.duckdb Primary historical ingestion archive scats_15min_long, scats_detector_day, scats_expected_date, scats_missing_dates, scats_site, source_file Original bulk archive with the long-format 15-minute view and missing-date support.
scats_continuation.duckdb Continuation archive scats_detector_day, scats_expected_date, scats_site, source_file Continues ingestion coverage beyond the original archive boundary.
scats_recovery.duckdb Recovery archive scats_detector_day, scats_expected_date, scats_site, source_file Stores recovered rows from files that required separate recovery processing.

Core Table Model

The SCATS database model is centred on a detector-day fact table. Each row represents one SCATS site, one count date, and one detector, with 96 quarter-hour volume columns covering a full 24-hour day.

Table / ViewPurposeImportant Columns / Structure
scats_detector_day Main detector-day traffic fact table. scats_site, count_date, detector, region_code, volume_24hour, source_file_id, and v00 to v95. Primary key: (scats_site, count_date, detector).
scats_site SCATS site metadata and geospatial lookup table. scats_site, site_name, site_type, municipality, latitude, longitude, first_seen_date, last_seen_date.
source_file Ingestion audit trail for every source CSV/file. source_file_id, file_path, file_name, file_date, file_year, file_month, file_size_bytes, loaded_at, row_count, load_status, notes.
scats_expected_date Calendar completeness support table. expected_date primary key.
scats_missing_dates Detected missing-date support object in the primary archive. d timestamp field used to record missing date diagnostics.
scats_15min_long Long-format analytical view that converts the 96 wide interval columns into time-bin rows. scats_site, count_date, detector, region_code, source_file_id, interval_index, time_bin, volume_15m.

Wide-to-Long 15-Minute Design

Design interpretation:
The raw SCATS detector-day model stores 96 interval columns from v00 to v95. The long-format analytical layer turns those columns into interval_index, time_bin, and volume_15m rows. This is what makes time-of-day analysis, peak-share analysis, busiest time-bin analysis, heatmaps, and animated traffic maps practical.
LayerShapeBest For
Wide detector-day tableOne row per site/date/detector with v00v95Compact storage, ingestion, source-file auditing, detector-day validation.
Long 15-minute viewOne row per site/date/detector/quarter-hour intervalMonthly totals, daily totals, peak periods, time-bin ranking, map animation, public charts.
Unified clean dedup layerCross-database cleaned and deduplicated 15-minute analytical surfacePublic reporting, reproducible headline metrics, site rankings, city-wide analysis.

Detected Index Strategy

The same seven core indexes appear across the SCATS archive family. They support the most important query paths: date slicing, site lookup, combined site/date scans, map/geospatial outputs, municipality filtering, source-file auditing, and load-status diagnostics.

IndexDefinitionWhy It Matters
idx_scats_detector_day_datescats_detector_day(count_date)Supports date, site, geospatial, municipality, and source-file status queries.
idx_scats_detector_day_sitescats_detector_day(scats_site)Supports date, site, geospatial, municipality, and source-file status queries.
idx_scats_detector_day_site_datescats_detector_day(scats_site, count_date)Supports date, site, geospatial, municipality, and source-file status queries.
idx_scats_site_latlonscats_site(latitude, longitude)Supports date, site, geospatial, municipality, and source-file status queries.
idx_scats_site_municipalityscats_site(municipality)Supports date, site, geospatial, municipality, and source-file status queries.
idx_source_file_datesource_file(file_date)Supports date, site, geospatial, municipality, and source-file status queries.
idx_source_file_statussource_file(load_status)Supports date, site, geospatial, municipality, and source-file status queries.

Unified Analytical Surface

Primary public reporting layer: scats_all_clean_dedup

The public page should continue to describe scats_all_clean_dedup as the trusted analytical surface. It logically combines the original, continuation, and recovery databases, removes duplicate detector intervals, cleans invalid negative values, and powers the finished public outputs.

Output Powered By scats_all_clean_dedupCurrent StatusWhy It Is Important
Monthly totalsCompleteConfirms long-term growth, seasonal behaviour, COVID-era disruptions, and the highest-volume month.
Daily totalsCompleteIdentifies the busiest recorded day and supports public-facing daily-history stories.
Busiest site rankingCompleteIdentifies the strongest loaded SCATS sites and the backbone of signalised traffic demand.
Peak-share analysisCompleteQuantifies morning peak, afternoon peak, and combined peak dominance.
Busiest / quietest time binsCompleteDefines the network’s strongest and weakest average 15-minute periods.
Maps and visualisationsIn progress / expandingTurns database structure into public-facing spatial intelligence.

Schema Relationship Diagram

source_file

  • file name and path
  • file date / year / month
  • load status
  • row count and audit trail

scats_site

  • site id and name
  • municipality
  • latitude / longitude
  • first and last seen dates

scats_expected_date

  • expected coverage calendar
  • date completeness support
  • missing-date diagnostics

scats_detector_day

Main fact table: one SCATS site, one date, one detector, and 96 quarter-hour columns from v00 to v95.

scats_15min_long

Long-format interval model: interval_index, time_bin, and volume_15m for analysis, animation, and time-of-day reporting.

scats_all_clean_dedup

Unified reporting surface combining scats.duckdb, scats_continuation.duckdb, and scats_recovery.duckdb into cleaned public analytics.

source_file + scats_site + scats_expected_date │ ▼ scats_detector_day ─────────────► scats_15min_long │ │ ▼ ▼ scats_all_clean_dedup ─────► public charts, maps, rankings, and Top 10 findings

Technical Reader Notes

What This Now Confirms

  • The Melbourne SCATS Intelligence platform is not simply a chart page — it is supported by a documented, reproducible multi-database analytical environment.
  • The three DuckDB archives (scats.duckdb, scats_continuation.duckdb, scats_recovery.duckdb) share a consistent analytical schema and support unified city-wide processing.
  • The detector-day fact model provides a stable 96-bin daily interval architecture, allowing consistent 15-minute behavioural analysis across more than 12 years of historical traffic movement.
  • Deduplication and data-quality auditing confirm zero duplicate detector-day keys within the cleaned analytical layer.
  • The indexing and query strategy aligns with the platform’s dominant access patterns including: date, site, site-date, geography, region, municipality, source-file auditing and behavioural time-series analytics.
  • Database diagnostics, month auditing, interval validation, negative/sentinel handling and performance benchmarking provide an unusually transparent level of engineering evidence for an open transport analytics project.
  • The analytical environment has now been benchmarked successfully across a 97.95GB multi-database DuckDB footprint using high-memory local analytics and HPC-inspired chunked processing workflows.

Future Technical Extensions

  • Live SCATS ingestion: future support for current-day comparison against historical baselines.
  • TIRTL integration: freeway, bridge and corridor intelligence including speed, direction, heavy vehicles and classification.
  • Live Melbourne Movement Index: real-time comparison against historical behavioural expectations.
  • Expanded reproducibility: additional downloadable workflow examples, notebook-style demonstrations and reference datasets.
  • Commercial OOH intelligence: customer-facing dashboards, exposure scoring and automated reporting layers.
  • Public APIs: future machine-readable interfaces for journalists, researchers and developers.

GitHub File Explorer and Script Search

📄 Export GitHub File Explorer as PDF

Search the Melbourne SCATS Intelligence GitHub repository for processing scripts, CSV outputs, JSON metadata, chart assets, diagnostics, DuckDB benchmarking, workflow notes and reproducibility outputs.

Open Source Repository:
github.com/clarketowson/melbourne-scats-intelligence

The search below allows developers, journalists, transport analysts, government readers and researchers to quickly locate scripts, charts, CSV outputs, JSON metadata and analytical workflows.

Search the Repository

Loading repository file registry...
File Category Description Path Open
Why this matters: The Melbourne SCATS Intelligence platform is designed to be reproducible. Rather than describing outputs abstractly, this repository exposes the actual processing scripts, workflow logic, diagnostics and generated outputs used to build the analytical platform.

Operational Pipeline Status and File Registry

📄 Export Operational Status as PDF

The SCATS analytical pipeline should now be treated as substantially complete. Historical movement intelligence, behavioural layers, yearly totals, diagnostics, data quality systems and performance benchmarking are operational.

Current status — May 2026:
The SCATS-side platform is now effectively complete for historical analysis. Future development is expected to focus on TIRTL enrichment, optional live-data ingestion, automation, additional visualisations and commercial packaging layers.
Pipeline Component Status Notes
Historical SCATS ingestion Complete 2014–2026 historical coverage loaded.
Deduplicated analytical layer Complete Zero duplicate detector-day keys confirmed.
Yearly totals Complete Historical growth and COVID-era comparison operational.
Daily / monthly totals Complete Behavioural baselines established.
Time-bin profiles Complete 15-minute behavioural analytics operational.
Weekday / weekend layer Complete Behavioural separation complete.
Database diagnostics Complete Coverage and structure auditing operational.
Data quality evidence Complete Negative/sentinel and duplicate-key auditing complete.
Performance benchmarking Complete 97.95GB environment benchmarked successfully.
GitHub reproducibility Ready Public repository prepared for commit.
TIRTL integration Complete Corridor speed, freight and classification layer.

Primary Completed Output Files

📄 Export Output File Registry as PDF

The Melbourne SCATS Intelligence platform now includes a large completed output environment spanning historical traffic analytics, behavioural profiles, diagnostics, performance benchmarking, reproducibility artifacts, mapping layers and public-facing publication assets.

Current status — May 2026:
The SCATS-side analytical output layer is now substantially complete. Core historical movement intelligence, yearly totals, behavioural analytics, diagnostics, data-quality evidence, performance metrics and publication outputs have been generated and integrated into the platform.
Output Category Status Examples
Historical Totals Complete Yearly totals, monthly totals, daily totals, growth indices, cumulative movement charts.
Behavioural Analytics Complete 15-minute time-bin profiles, weekday/weekend, day-of-week and month-of-year behaviour.
Site Intelligence Complete Busiest intersections, site totals, site-month intelligence, movement rankings.
OOH & Parcel Intelligence Complete Parcel opportunity mapping, Google Maps integrations, OOH exposure discovery layers.
Database Diagnostics Complete Coverage auditing, structural diagnostics, month validation, yearly coverage confirmation.
Data Quality Evidence Complete Duplicate-key auditing, negative/sentinel handling, interval-quality validation.
Performance Benchmarking Complete Query timing benchmarks, memory utilisation, database size reporting.
Publication Assets Complete PNG charts, map exports, animations, JSON metadata, CSV downloads, PDF exports.
Why this matters: The platform now operates as a reproducible analytical environment rather than a collection of standalone charts. Outputs are generated through scripted workflows and supported by diagnostics, metadata and reproducibility layers.

Current Script Registry

📄 Export Script Registry as PDF

The analytical registry now reflects a mature multi-stage DuckDB workflow spanning ingestion, recovery, cleaning, diagnostics, benchmarking, chart generation, publication and reproducibility systems.

Current status — May 2026:
The Melbourne SCATS Intelligence workflow is now effectively complete for historical analysis. The pipeline includes ingestion, continuation, recovery, deduplication, behavioural analytics, diagnostics, performance benchmarking and publication layers, supported by a public open-source GitHub repository:

github.com/clarketowson/melbourne-scats-intelligence

The repository includes analytical workflows, processing scripts, chart-generation logic, diagnostics, data-quality systems and reproducibility pathways supporting the Melbourne SCATS Intelligence platform.
Pipeline Layer Status Representative Outputs
Ingestion + Continuation Complete Historical SCATS loading, continuation workflows, multi-database architecture.
Recovery Layer Complete Failed-source recovery, recovery database generation.
Deduplicated Analytical Layer Complete Unified clean datasets, zero duplicate detector-day confirmation.
Historical Totals Scripts Complete Yearly, monthly, daily, growth and cumulative movement outputs.
Behavioural Scripts Complete Time-bin, weekday/weekend, day-of-week, month-of-year profiling.
Site Intelligence Scripts Complete Busiest-site, site totals, site-month intelligence.
Diagnostics Scripts Complete Database diagnostics, coverage auditing, month validation.
Data Quality Scripts Complete Duplicate-key, negative-value, interval-quality auditing.
Performance Scripts Complete DuckDB benchmarking, query timings, memory reporting.
Publication Layer Complete Chart generation, HTML publication, maps, SEO integration, PDF exports.
TIRTL Integration Future Freeway speed, vehicle classification, corridor intelligence.
Why this matters: The platform is now largely engineering-complete on the SCATS side. Future work is expected to focus on TIRTL enrichment, live ingestion and optional commercial/reporting layers rather than foundational analytics.

17 — Processing Time by Completed CSV / JSON Output

Workflow processing-time summary rebuilt from the final JSON completion files generated by the SCATS analytics pipeline.

Runtime-bearing outputs found

13

Completed outputs

13

Cumulative compute time

386.6h

Equivalent compute days

16.1 days

Longest completed job

busiest_time_bin
46.8h

Average runtime

29.7h

This section now reflects the broader processing workload, not just the original subset chart. The metadata shows a multi-day compute pipeline spanning temporal, behavioural, site-level, peak-period and network-total analytics. The final yearly totals job remains the last major remaining script to run.

All Runtime-Bearing Completed JSON Outputs

Comprehensive runtime chart rebuilt from every uploaded JSON file containing total_elapsed_seconds.

Processing time for all runtime-bearing completed SCATS JSON outputs

Top 12 Longest Processing Jobs

The heaviest scripts are the time-bin, peak-share, site-level and behavioural profile computations.

Top 12 longest-running completed SCATS processing jobs

Processing Time by Analytics Category

Runtime grouped by the kind of intelligence being produced: site-level analytics, behavioural profiles, time-bin analysis and network totals.

Processing time grouped by analytics category

Download Runtime Summary

The rebuilt CSV summarises each runtime-bearing JSON output, including metric name, filename, completion status, months processed and runtime hours.

Longest Completed Runtime Jobs

Output / Metric Runtime Compute Days Months Status
busiest_time_bin
chunked_busiest_time_bin_final.json
46.8h 1.95 days 148/148 Complete
peak_shares
chunked_peak_shares_final.json
45.6h 1.90 days 148/148 Complete
time_bin_profile
time_bin_profile_final.json
44.2h 1.84 days 148/148 Complete
busiest_site
chunked_busiest_site_final.json
41.6h 1.73 days 148/148 Complete
month_of_year_profile
month_of_year_profile_final.json
34.3h 1.43 days 148/148 Complete
site_month_totals
site_month_totals_final.json
32.6h 1.36 days 148/148 Complete
busiest_day
chunked_busiest_day_final.json
31.5h 1.31 days 148/148 Complete
monthly_totals
monthly_totals_final.json
4.5h 0.19 days 148/148 Complete
daily_totals
daily_totals_final.json
4.4h 0.18 days 148/148 Complete
total_cleaned_volume
chunked_total_cleaned_volume_final.json
4.0h 0.17 days 148/148 Complete

Interpretation

These runtimes are a major credibility signal. They show that the page is backed by a genuine large-scale compute workflow rather than a cosmetic dashboard. The outputs were generated through resumable month-by-month processing, strict completion metadata, deduplicated logical views and heavy DuckDB aggregations over the unified SCATS dataset.

System Performance Metrics

📄 Export System Performance Metrics as PDF

This section is intended for technical readers interested in the engineering characteristics of the analytical system powering the Melbourne SCATS Intelligence platform. The metrics below were generated directly from reproducible DuckDB benchmark scripts operating against the three production analytical databases.

Average Query Runtime

17.48 sec

Average runtime across 18 benchmark queries.

Largest Query Runtime

190.11 sec

Duplicate detector-day key scan (scats_continuation).

Database Size

97.95 GB

Across the original, continuation and recovery DuckDB archives.

Peak Memory Usage

36.25 GB

Maximum observed process memory during benchmark execution.

Peak Temp Spill

0.0 GB

No temporary spill was required during benchmark execution.

Processing Mode

Chunked

Monthly unified clean process with DuckDB analytical benchmarks.

Benchmark Success Rate

18 / 18

All benchmark queries completed successfully.

Threads / Memory Limit

10 / 40GB

DuckDB runtime configuration used during benchmarking.
Benchmark summary — 16 May 2026:
The DuckDB analytical environment successfully completed 18 benchmark queries across the three production SCATS databases with an average runtime of 17.48 seconds. The largest benchmark query was the duplicate detector-day key scan on scats_continuation.duckdb, completing in 190.11 seconds. Peak observed memory usage reached 36.25 GB while requiring 0 GB of temporary spill, indicating that the configured memory ceiling and chunked processing approach were sufficient for the benchmark workload.

Why this matters

Large-scale SCATS analytics are computationally expensive because the platform processes hundreds of millions of detector-day rows and tens of billions of 15-minute observations. These benchmark results demonstrate that the system is operating efficiently using a high-memory DuckDB analytical approach with HPC-inspired chunked processing techniques rather than relying on cloud-scale infrastructure.

Technical Configuration

Setting Value
Primary analytical table scats_detector_day
Databases processed 3
DuckDB threads 10
Configured memory limit 40GB
Temp directory A:\TrafficAnalytics\DATA\TEMP
Processing mode Chunked monthly unified clean process
Total benchmark elapsed time 587.03 sec (~9.8 min)

Downloadable Benchmark Outputs

Project Timeline — Full System Evolution Across Windows, Linux, SCATS and TIRTL

This timeline documents the evolution of the Melbourne Traffic Intelligence Platform from raw transport-data handling into a public-facing intelligence system combining SCATS signal-volume data, TIRTL vehicle-classification and speed-flow data, charts, maps, freight intelligence, parcel intelligence, satellite SEO pages, reproducibility outputs, and media-ready reporting layers.

Key build insight:
The project did not emerge as a single static webpage. It evolved across both a Windows analytics environment and the Linux host essexskipper, moving from raw data engineering and template construction into a dual-source SCATS + TIRTL intelligence platform capable of supporting public, journalistic, commercial, transport-planning and government-accountability questions.
Stage Description Date / Period Platform Significance
Windows analytics environment initialized Project folders, Python virtual environment, DuckDB, Pandas, NumPy, Plotly, Matplotlib, Jupyter and supporting analytics libraries were established on the Windows NVMe workspace. 12 April 2026
10:29–11:19 AM
Created the high-performance local analytics base for large-scale SCATS processing and reporting.
Linux template system begins on essexskipper Initial public-facing HTML template work began on the Linux host, starting with template.html and rapidly iterating through early template versions. 14 April 2026
5:38 PM onward
Marked the beginning of the public intelligence-page layer and the visual reporting framework.
Master template evolution Rapid template iteration progressed from early template files through multiple mastertemplate versions, defining layout, structure, chart placement, navigation, public framing and platform architecture. 14–16 April 2026 Established the reusable publishing framework that later became the main SCATS statistics page and informed the later TIRTL page structure.
Technology stack and architecture assets added Branding, technology logos, and system-architecture assets were added, including Python, SQLite, Kepler.gl, AlmaLinux, Pandas, NumPy, Matplotlib, Google Maps, Transport Open Data, SCATS, TIRTL, Bash, VicMap, DuckDB, Windows and OpenAI/ChatGPT assets. 15 April 2026 Formalised the project as a documented multi-technology data-engineering and publication system.
Initial SCATS ingestion and processing Large-scale SCATS ingestion and processing workflows began, building the foundation for intersection-level Melbourne traffic intelligence from signal-volume records. Mid April 2026 Converted raw archive material into structured analytical data suitable for city-scale querying.
First populated public SCATS pages The first SCATSPopulated HTML outputs were generated, representing the transition from templates and raw calculations into visible public-facing traffic intelligence pages. 20 April 2026 Demonstrated that the data pipeline could produce publishable web outputs, not just internal files.
Continuation and recovery ingest The dataset was expanded beyond the initial ingest and failed historical CSV files were recovered into a dedicated recovery dataset to improve completeness and robustness. Late April 2026 Reduced missing-data risk and enabled broader historical coverage across the Melbourne SCATS archive.
Unified SCATS deduplication layer A clean logical analytical layer was created across primary, continuation and recovery databases, including deduplication, negative-value cleanup, and unified reporting views. Late April – Early May 2026 Created the core query surface for headline metrics, charts, rankings and repeatable SCATS reporting.
SCATS charting and reporting generation Automated chart and report outputs began, including monthly totals, yearly trends, COVID disruption and recovery, time-of-day charts, busiest days, weekday profiles, site rankings, suburb intelligence and processing summaries. 30 April 2026 onward Transformed raw and cleaned SCATS data into visual evidence suitable for media, public explanation, policy discussion and citywide traffic storytelling.
TIRTL integration begins High-resolution corridor-level traffic, speed, direction and vehicle-classification intelligence was integrated alongside SCATS intersection data. Early May 2026 Gave the platform both intersection-level and corridor/freeway-level analytical depth, allowing SCATS signal pressure to be viewed beside TIRTL truck, vehicle-class and speed behaviour.
TIRTL truck and freight intelligence layer built The TIRTL work expanded into truck-share rankings, truck movement rankings, suburb truck summaries, freight corridor outputs, map layers, site-heading lookups and downloadable data-dictionary outputs. Mid May 2026 Turned the platform from a general traffic-volume system into a freight-aware transport intelligence system capable of supporting heavy-vehicle, corridor and suburb pressure analysis.
SCATS + TIRTL combined pressure analysis Combined outputs were generated to compare SCATS signal pressure with TIRTL freeway/corridor pressure, including pressure-quadrant mapping, freight-led suburbs, high-traffic/high-truck-pressure suburbs and worst freight-time summaries. Late May 2026 Created the first integrated evidence layer showing where local signal pressure, freeway/corridor behaviour and freight exposure overlap.
Speed-flow, nowcast and abnormal-flow analysis The TIRTL analysis expanded into speed-flow pressure heatmaps, historical 15-minute worsening-risk nowcast outputs, abnormal speed-flow episode detection, incident-like candidate identification, recovery-duration proxies and construction RDO movement effects. Late May 2026 Moved the project beyond static movement totals into dynamic traffic-state intelligence, showing where conditions historically worsened, recovered or displayed abnormal speed-flow signatures.
West Gate Tunnel and Kensington impact evidence pages Post-tunnel SCATS + TIRTL map outputs and Kensington-focused evidence pages were built to test local concerns around Macaulay Rd, Epsom Rd, Kensington Rd, truck impacts, traffic redistribution and inner-north-west no-truck-zone debates. Late May 2026 Demonstrated that the platform can respond directly to live public and media issues by producing local evidence packs, maps, caveats and downloadable audit files.
Public intelligence platform and SEO expansion The platform expanded into a full public web resource with interactive maps, Top 100 rankings, Vicmap parcel intelligence, OOH billboard opportunity analysis, satellite pages, sitemap, metadata, structured data, image SEO and TIRTL-specific SEO upgrades. Early May 2026 – Current Converted the engineering pipeline into a discoverable public traffic intelligence platform for media, commuters, planners, OOH advertisers, property analysts, transport operators and researchers.
Reproducibility and AI-readiness layer Compact file catalogues, column dictionaries, priority dataset lists, database table summaries, known-question documents and project context packs were created to make the SCATS + TIRTL system understandable to future ChatGPT sessions, journalists, developers and technical reviewers. Late May 2026 – Current Made the project self-describing and prepared the foundation for a future Traffic AI Analyst chatbot that can answer public questions using verified source files instead of guessed filenames.

1. Initialize

Windows analytics environment and Python/DuckDB stack established.

2. Template

Linux HTML template system begins on essexskipper.

3. Ingest

SCATS archive data loaded, extended, recovered and deduplicated.

4. Integrate

TIRTL vehicle-classification, truck-share, speed and corridor data added.

5. Analyse

SCATS + TIRTL pressure, freight, speed-flow, abnormal-flow and nowcast outputs generated.

6. Publish

Public SEO-ready intelligence platform, maps, evidence pages and downloads released.

7. Document

Data dictionaries, context packs, known-question guides and audit trails created.

8. Prepare AI

Foundation laid for a future public Traffic AI Analyst over verified SCATS + TIRTL outputs.

Data provenance note:
Some source SCATS and TIRTL files carry older timestamps from the original transport-data archives. Those timestamps describe source-data provenance, not the 2026 platform-build date. The platform engineering timeline begins with the April 2026 analytics and publishing work, then expands through the May 2026 TIRTL, freight, speed-flow, nowcast and public evidence-page layers.

On-Site Computing Infrastructure – 7 Cullen Court

Infrastructure summary:
The SCATS analysis presented on this page was produced using a local, on-site analytics environment located at 7 Cullen Court, Spotswood. The workflow combines a Windows 10 processing workstation with a Linux analytics node, local NVMe and SSD storage, DuckDB, Python, Pandas, and Matplotlib. This means the archive has been processed locally rather than relying on remote cloud infrastructure.
Why this matters: this is a city-scale traffic analytics pipeline running from a private, on-site computing environment beside one of Melbourne’s most important transport corridors. The setup demonstrates that large-scale transport intelligence can be produced with carefully configured local hardware, restart-safe chunked processing, and open analytical tools.

Primary Windows Analytics Workstation

System Platform

  • Computer name: DESKTOP-ON95QET
  • Operating system: Windows 10 Pro
  • OS build: 19045
  • Architecture: 64-bit

CPU

  • Processor: AMD Ryzen 9 3900X
  • Physical cores: 12
  • Logical threads: 24
  • Max clock: 3.793 GHz

Memory

  • Total RAM: 63.94 GB
  • Configuration: 4 × 16 GB Micron modules
  • Speed: 2400 MHz

GPU

  • Graphics: NVIDIA GeForce GTX 1060 3GB
  • Role: visualisation, display, and charting workflows

Storage

  • A: 1 TB NVMe scratch / analytics drive
  • C: 1 TB Samsung 970 EVO Plus NVMe
  • D: 4 TB Samsung SSD 860 EVO
  • E: 2 TB extra storage

Windows SCATS Databases

  • scats.duckdb: 59.33 GB
  • scats_continuation.duckdb: 35.58 GB
  • scats_recovery.duckdb: 3.04 GB
  • Combined: approximately 97.95 GB

Linux Analytics Node – essexskipper

System Platform

  • Hostname: essexskipper
  • Operating system: AlmaLinux 10.1
  • Kernel: Linux 6.12.0-124.21.1.el10_1.x86_64
  • Hardware: ASUS PRIME B350-PLUS platform

CPU

  • Processor: AMD Ryzen 5 1600
  • Physical cores: 6
  • Logical threads: 12
  • Max clock: 3.2 GHz

Memory

  • Total RAM: approximately 30 GiB
  • Swap: approximately 31 GiB
  • Role: Linux processing, storage, database staging, and support workflows

GPU and Network

  • GPU: NVIDIA GeForce GTX 1060 3GB
  • Network: Intel I210 Gigabit Ethernet

Linux Storage Pool

  • System NVMe: Samsung 970 EVO Plus 1 TB
  • /home: 852 GB XFS volume
  • Additional mounted storage: multiple 2 TB, 4 TB, 5.5 TB, and 6 TB class drives

Linux SCATS Databases

  • scats.duckdb: 59.33 GB
  • scats_continuation.duckdb: 35.58 GB
  • scats_snapshot.duckdb: 16.23 GB
  • scats_recovery.duckdb: 3.04 GB
  • Combined listed DuckDB footprint: approximately 114.18 GB

Software and Analytical Stack

Python Analytics Stack

Python 3.14.2 DuckDB 1.5.1 Pandas 3.0.2 Matplotlib 3.10.8

Used for chunked processing, aggregation, validation, chart generation, and HTML reporting outputs.

Processing Model

  • Month-by-month chunked execution
  • Restart-safe CSV and JSON progress outputs
  • NVMe-backed temporary processing
  • Large DuckDB analytical scans and aggregations
  • PNG chart generation for public reporting

Local Infrastructure Value

  • No dependency on cloud compute for the published outputs
  • Direct control over database files and processing runs
  • Local repeatability and auditability
  • Physical proximity to the West Gate Freeway corridor
Location context: the computing infrastructure used for this project is located on-site at 7 Cullen Court, Spotswood, adjacent to the West Gate Freeway corridor. This connects the analysis environment directly to the transport geography being observed and explained.
📄 Export Architecture Section as PDF Use browser print / save as PDF for a print-ready architecture extract.

System Architecture — From Raw Source Files to Published Traffic Intelligence

This section explains how the Melbourne Traffic Intelligence Platform converts raw transport data into cleaned, validated, deduplicated and publishable outputs. The architecture combines SCATS signal-volume archives, TIRTL corridor intelligence, Python processing, DuckDB analytical databases, recovery workflows, chart generation, maps, Vicmap parcel intelligence and SEO-ready HTML publication.

Architecture summary:
Raw SCATS CSV files and TIRTL corridor data are ingested, cleaned, validated and transformed into a unified analytical layer. Python and DuckDB scripts then generate CSV, JSON, PNG, HTML and interactive map outputs for public traffic analysis, media reporting, OOH billboard opportunity discovery and long-term Melbourne transport intelligence.

Pipeline Overview

1. Source SCATS CSV archives, TIRTL data, Vicmap parcel references
2. Ingest Python loaders, DuckDB databases, staged imports
3. Recover Failed CSV recovery, continuation database, missing-file handling
4. Clean Negative sentinel handling, validation, normalization
5. Deduplicate Unified clean analytical view across databases
6. Analyse Monthly, daily, site, time-bin and ranking scripts
7. Visualise PNG charts, CSV/JSON outputs, maps and tables
8. Publish HTML platform, SEO pages, parcel intelligence, public reporting
Architecture Layer Role Key Outputs / Evidence
Raw source layer Stores the original traffic-signal and corridor datasets before transformation. SCATS daily CSV traffic-signal volume files; TIRTL corridor records; Vicmap / parcel reference fields.
Ingestion layer Loads large volumes of daily SCATS CSV files into structured analytical storage. Python loaders, DuckDB import workflows, primary SCATS database creation.
Continuation layer Extends processing beyond the initial load when dataset scale requires a second major database. Continuation DuckDB database and expanded temporal coverage.
Recovery layer Recovers failed or missing historical CSV loads into a separate database instead of abandoning them. Recovery database, recovered detector-day records, reduced missing-data risk.
Cleaning and validation layer Normalises records, handles negative sentinel values, checks tables/views and prevents known retry-loop issues such as zero-row months. Clean SCATS views, preflight checks, explicit zero-row month handling.
Unified deduplication layer Creates a logical clean analytical surface across primary, continuation and recovery datasets. Unified clean deduplicated views, cross-database querying, repeatable reporting layer.
Analytics layer Generates the headline intelligence used across the public website and satellite pages. Monthly totals, daily totals, time-bin profiles, site totals, Top 100 rankings, congestion findings.
TIRTL corridor layer Adds freeway/corridor-level movement, speed, direction and vehicle classification intelligence. Bridge and corridor metrics, speed/classification analysis, SCATS/TIRTL contextual comparison.
Visualisation layer Converts analysis outputs into public-friendly charts, tables, maps and interactive exploration tools. PNG charts, CSV/JSON summaries, Google Maps, OpenStreetMap/Leaflet, Kepler-style visual exploration.
Parcel intelligence layer Combines traffic volume rankings with nearby Vicmap/VicPlan parcel selection for OOH and property opportunity analysis. Integrated Top 100 Parcel Opportunity Map, SPI/PFI fields, lot/plan references, road-parcel status.
Publication and SEO layer Publishes the intelligence as a discoverable public platform with structured metadata and internal topic clusters. Main HTML page, satellite pages, sitemap, robots.txt, structured data, Open Graph metadata, image SEO.

System Architecture Diagram

📄 Export System Architecture as PDF

The Melbourne SCATS Intelligence platform operates as a staged analytical pipeline rather than a simple reporting dashboard. Multiple DuckDB databases, chunked processing workflows, diagnostics systems and public-facing reporting layers combine to transform raw transport datasets into reproducible public transport intelligence.

Architecture overview:
The platform ingests historical SCATS archives into staged DuckDB databases, processes continuation and recovery datasets, constructs a unified cleaned analytical layer and produces reproducible CSV, JSON, PNG, map and HTML outputs. TIRTL sits alongside SCATS as a corridor-intelligence source supporting freeway, bridge, speed and vehicle-class analysis.

HPC-Style Chunked Processing Architecture

The diagram below illustrates the end-to-end engineering pipeline powering the platform — from raw SCATS ingestion through to diagnostics, analytics, visualisation and public publication.

Melbourne SCATS Intelligence HPC Style Chunked Processing Architecture

1. SCATS as the Intersection Layer

SCATS provides high-volume signalised-intersection movement counts suitable for ranking, trend analysis, behavioural profiling and citywide traffic-volume measurement at 15-minute resolution.

2. TIRTL as the Corridor Layer

TIRTL adds corridor intelligence including speed, classification, vehicle type, direction and freeway performance, especially for bridge and freight analysis.

3. DuckDB as the Analytical Engine

DuckDB enables large local analytical workloads across approximately 97.95GB of databases and hundreds of millions of detector-day rows, using chunked month-by-month processing and staged analytical execution.

4. Diagnostics and Quality Assurance

Structural diagnostics, month audits, duplicate-key checks, interval-quality scans and performance benchmarks ensure the analytical environment is transparent, reproducible and technically defensible.

5. Analytics and Output Generation

The processing layer generates yearly, monthly, daily, site-level and 15-minute behavioural outputs alongside CSV, JSON, chart and animation assets.

6. HTML as the Intelligence Surface

The public-facing platform converts database outputs into charts, interactive maps, rankings, OOH parcel intelligence, reproducible downloads and SEO-discoverable transport insights.

Why this matters: This platform is not simply a collection of charts. It is a staged data-engineering, diagnostics and publication pipeline designed to transform messy, large-scale transport datasets into reproducible public intelligence. The architecture reflects an HPC-inspired analytical approach operating at a scale rarely seen outside institutional transport environments.

Technology Stack and Data Sources

This platform is built on a combination of open-source infrastructure, analytical tooling, official transport data sources, mapping systems, and AI-assisted workflow support. These components underpin the ingestion, cleaning, analysis, visualisation, and publication layers of the Melbourne traffic intelligence system.

Why this section matters:
For technical readers, journalists, agencies, and industry, the stack below helps show that the reporting layer sits on top of a real and traceable engineering workflow rather than a one-off set of charts.

Core Infrastructure

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

AlmaLinux

Primary server operating system environment.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Linux

Underlying platform foundation for the workflow.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Bash

Automation, orchestration, and reporting scripts.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Windows

Supporting desktop workflow and operational environment.

Data Engineering and Analytics

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Python

Primary language for analysis and automation.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Pandas

Data wrangling and structured reporting workflows.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

NumPy

Numerical processing and supporting computation.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Matplotlib

Chart generation and visual statistical outputs.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

DuckDB

Analytical engine for large-scale SCATS processing.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

SQLite

Compact analytical store supporting TIRTL workflows.

Mapping and Visualisation

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Google Maps

Location context and hotspot reference imagery.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Kepler.gl

Geospatial exploration and movement visualisation.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Vicmap

Victorian spatial context and mapping support.

Data Sources and Standards

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

SCATS

Signalised intersection traffic data foundation.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

TIRTL

Corridor, count, speed, and classification intelligence.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

CEOS

Technology lineage behind TIRTL sensing systems.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Transport Victoria Open Data

Official public transport and road data source layer.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Creative Commons

Open data licensing and reuse framework.

AI and Platform Support

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

ChatGPT

AI-assisted workflow support, drafting, and iteration.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

OpenAI

Underlying AI platform support within the workflow.

Spotswood Trailers logo for Melbourne SCATS traffic analysis and trailer hire

Spotswood Trailers

Project host, publication platform, and site branding.

System Development Overview

This section documents how the system evolved from initial ingestion experiments into a full unified transport intelligence platform. It reflects the iterative engineering process required to manage extremely large-scale transport datasets and transform them into structured, validated, and publicly accessible outputs.

Phase Description Outcome
Initial Design Early ingestion experiments were conducted using raw Department of Transport SCATS CSV files. Initial schema definitions were developed to normalize detector data, timestamps, and signal intersection metadata into structured DuckDB tables. Basic ingestion scripts were created and tested on small batches to validate schema correctness and loading performance. Established the foundational schema design and validated the feasibility of large-scale ingestion using DuckDB. Confirmed the viability of structured SCATS ingestion workflows.
Scaling Phase The ingestion system was expanded to handle thousands of daily CSV files across multiple years of SCATS data. Parallel loading workflows and disk spill management techniques were introduced to allow processing of extremely large datasets without exceeding memory limits. The database grew to tens of gigabytes during this stage. Successfully scaled ingestion to full historical coverage beginning in 2014. Created large primary databases including scats.duckdb and scats_continuation.duckdb, enabling sustained high-volume loading.
Deduplication Phase Data integrity challenges were addressed by implementing deduplication logic across multiple databases. Recovery workflows were introduced to process failed or corrupted source files. Additional validation routines were created to remove invalid negative values and ensure consistent detector-day uniqueness. Produced a unified cleaned dataset exceeding tens of billions of 15-minute observations. Established scats_recovery.duckdb and the combined scats_all_clean_dedup analytical surface.
Integration Phase Analytical scripts were developed to generate standardized outputs including daily totals, monthly totals, peak period distributions, busiest intersections, and growth metrics. Chunked execution workflows were introduced to safely process multi-year time ranges without memory exhaustion. Generated large-scale derived datasets including:
  • Monthly traffic totals
  • Daily traffic totals
  • Site-level traffic summaries
  • Peak-hour intensity profiles
  • Network-wide growth indicators
Publication Phase Visualization templates were developed to transform analytical outputs into public-facing charts, maps, and downloadable datasets. Interactive Google Maps layers and statistical dashboards were integrated into the reporting framework. Documentation, transparency notes, and technical references were added to support public review and professional use. Delivered a fully published public traffic intelligence platform containing large-scale historical datasets, visual summaries, technical documentation, and downloadable outputs suitable for public, media, and research use.

If Every Database Record Were Printed

Media-scale comparison:
The unified cleaned SCATS layer contains 37,877,397,311 cleaned 15-minute observations. If those records were printed as a simple line-by-line database extract, the paper output would be vast enough to become a physical infrastructure-scale object in its own right.

Cleaned Records

37,877,397,311

Assumed Print Density

50 records / A4 page

Estimated Pages

757,547,946

Paper Stack Height

~75.8 km

End-to-End Length

~225,000 km

Earth Circumference Equivalent

~5.6 times around Earth

Using a conservative database-printing assumption of around 50 records per A4 page, the cleaned archive would require approximately 757.5 million pages. Stacked vertically, that paper would rise about 75.8 kilometres. Laid end-to-end, the pages would stretch roughly 225,000 kilometres, or around 5.6 times around Earth’s equator.

Extreme comparison: If each cleaned record were printed on its own page, the archive would require about 37.9 billion pages. Laid end-to-end, that would stretch roughly 11.25 million kilometres, or about 29 times the distance from Earth to the Moon. This is not a practical printing scenario, but it helps communicate the sheer scale of the dataset to a general audience.
ScenarioPagesStack HeightEnd-to-End LengthPlain-English Comparison
Database-style printout ~757.5 million pages ~75.8 km ~225,000 km About 5.6 times around Earth
One record per page ~37.9 billion pages ~3,788 km ~11.25 million km About 29 Earth–Moon distances

This comparison is useful for public communication because it turns an abstract data-engineering number into something physical and intuitive: the SCATS archive is not spreadsheet-scale; it is an industrial-scale transport dataset.

📈 Page Statistics

This page is now configured to display live audience reach for sponsors, journalists, researchers, and organisations assessing the public value of this traffic intelligence project.

Total Page Views

Loading...

Page First Published

May 2026

Data Coverage Period

2014 → 2026

Dataset Scale

539B+ movements

V3 Headline Merge Status

Confirmed merge result:
The V3 headline merge completed successfully in strict mode at 2026-04-29 07:12:30. All required source summaries were present, readable, and complete. The merged headline metrics JSON and CSV were written successfully.

Merge Script Version

V3

Strict Complete Mode

True

All Sources Present

True

All Sources Complete

True

Distinct Sites

4,907

Missing Sources

None

Unreadable Sources

None

Source Completion Status

SourceStateMonths CompletedFile Exists
total_cleaned_volumeComplete148 / 148Yes
busiest_siteComplete148 / 148Yes
busiest_dayComplete148 / 148Yes
busiest_time_binComplete148 / 148Yes
peak_sharesComplete148 / 148Yes

Responsible Use of Traffic Data

This platform uses aggregated transport-count intelligence rather than personal movement records. The analytical layer is based on signalised-intersection traffic counts, corridor measurements and reproducible public transport datasets rather than individual-level behavioural tracking.

Appropriate uses include public-interest reporting, congestion analysis, infrastructure discussion, OOH exposure modelling, freight/logistics context, transport planning discussion, journalism, reproducible research and commercial movement intelligence.

Important distinction:
Measured SCATS outputs should be distinguished from modelled commercial scenarios. Traffic volumes, rankings, growth patterns and behavioural statistics are directly measured from historical datasets. Revenue estimates, campaign ROI assumptions, OOH valuation scenarios and commercial opportunity models remain exploratory and should not be interpreted as financial forecasts.

The platform is designed to encourage transparency and reproducibility. Wherever possible, downloadable CSV, JSON, diagnostic and methodological outputs are provided to support independent verification.

Why this matters: The platform aims to make transport intelligence more transparent and publicly understandable while avoiding privacy concerns associated with individual movement tracking.

System Limitations and Constraints

SCATS network-node limitation: Not every SCATS ID corresponds to a named public signalised intersection. Some IDs appear in traffic-volume outputs but not in the public SCATS site register. The V5.2 charts preserve these records and label them as network nodes rather than guessing names.

This section transparently communicates known limitations and operational constraints associated with the SCATS dataset and the analysis outputs. These limitations do not invalidate the findings, but they help readers interpret the results correctly.

Limitation Area Known Constraint Interpretation Impact
Known Data Gaps The archive contains at least one confirmed zero-volume data-gap month: 2018-12. The month 2026-04 is also partial because the current archive ends on 2026-04-07. These periods should not be interpreted as true traffic collapse. They should be treated as coverage limitations when comparing monthly totals.
Sensor Reliability Notes SCATS relies on detector infrastructure at signalised intersections. Individual detectors may be offline, misconfigured, damaged, replaced, duplicated, or missing metadata during parts of the archive. Site-level conclusions should be interpreted with awareness that detector availability may vary over time.
Vehicle Events vs Unique Vehicles SCATS records traffic movements or detector events. It does not identify unique vehicles. A single vehicle may be counted multiple times as it passes through multiple signalised intersections.
Signalised Intersections Only SCATS primarily covers signalised intersections and does not represent every road segment, freeway link, local street, private road, driveway, or unsignalised movement. Results describe the monitored SCATS network, not every vehicle movement in Victoria.
Invalid Values Negative and structurally invalid readings are treated as invalid and excluded or converted to null values during cleaning. Cleaned totals are more reliable than raw totals, but null handling must be considered when interpreting incomplete detector histories.
Missing Site Metadata Some SCATS site names, coordinates, or historical metadata may be incomplete, inconsistent, or unavailable. Traffic volumes may still be included even where labels or map positions are incomplete.
Historical Comparability The SCATS network changes over time as intersections are added, removed, upgraded, or reconfigured. Long-term growth patterns may reflect both actual traffic growth and changes in detector coverage.
Prediction Constraint The current platform is primarily historical and analytical. It does not yet publish a formal predictive congestion model. Forecasting claims should be avoided unless a separate validated prediction model is later added.

Template Notes

Updated Template Takeaways

Frequently Asked Questions

FAQ focus:
This section addresses data accuracy, scale, methodology, technical background, and common misconceptions — including whether modern AI tools could replicate this work.
Question Answer
What is your technical background? I worked for over two decades in high-performance computing (HPC) environments, including at Australia’s Defence Science and Technology (DST) Group. My background is in large-scale systems, data processing, and scientific computing workflows, which directly influenced how this traffic analysis system was designed and executed.
How were you able to process a dataset of this scale independently? The system was designed using principles from high-performance computing rather than traditional analytics workflows. The data was partitioned and processed in controlled chunks, allowing large-scale analysis to run reliably on a single machine. This approach mirrors techniques used in supercomputing environments, adapted for commodity hardware.
Why wasn’t a supercomputer required? Supercomputers reduce processing time but are not strictly required if the workload is structured correctly. By designing the pipeline to run in deterministic chunks with controlled memory usage, the analysis becomes time-intensive rather than infeasible.
Can this page be generated quickly using AI tools? No. AI can assist with formatting, code generation, and explanation, but it does not replace the underlying data processing. This project required cleaning, deduplicating, and analysing billions of real records across more than a decade of data. The results come from computation, not generation.
If a data team used AI, could they reproduce this quickly? AI would accelerate parts of the workflow, but the core constraints remain. The bottleneck is not writing code — it is processing large datasets, handling edge cases, and validating results. Even with AI assistance, the compute time and engineering effort are still required.
Is this mainly an example of prompt engineering? No. Prompt engineering can help generate code or structure outputs, but it does not create validated datasets. This project required building and running a full data pipeline — from raw ingestion through cleaning, deduplication, and aggregation — to produce consistent results.
Could these results be approximated or faked? Approximation is possible, but it would not produce internally consistent results across all dimensions. The figures align across monthly totals, daily totals, site rankings, and time-bin profiles because they are derived from the same dataset. Synthetic data would struggle to maintain that consistency.
What would give away a fake analysis? Inconsistent totals, unrealistic peak patterns, or mismatches between site-level and network-level results would quickly expose synthetic data. Real traffic systems produce structured, repeatable patterns that are difficult to replicate convincingly without actual measurements.
What is the hardest part of building this? The hardest part is managing the data at scale. This includes cleaning corrupted values, removing duplicates, structuring data efficiently, and ensuring large queries complete reliably. Writing code is relatively straightforward — designing a system that works at this scale is not.
Why does compute time matter if AI is fast? AI can generate plausible answers instantly, but it cannot verify them without processing the underlying data. When working with billions of records, computation time becomes a fundamental constraint. Fast answers are not the same as correct answers.
Is this just a data visualisation project? No. The visualisations are the final layer. The core of the project is the construction of a cleaned, deduplicated, and queryable dataset representing Melbourne’s traffic network over time.
Why hasn’t this been done publicly before? While the data is publicly available, it is extremely large and difficult to process. Many analyses rely on samples or subsets because full-network processing introduces significant engineering complexity. This project focuses on completeness rather than partial insight.
Can the results be independently verified? Yes. The pipeline is deterministic, meaning the same inputs produce the same outputs. Intermediate datasets can be regenerated and cross-checked, providing a transparent path from raw data to final results.
What is the biggest misconception about this page? That the difficulty lies in building the page itself. In reality, the page is the simplest part. The complexity is in transforming raw data into a reliable, structured, and analyzable system.
Is this similar to a “proof of work” concept? A simple way to understand it is like a physical structure. Anyone can look at a completed house or building, but constructing it requires real effort and time. This page is similar — the outputs are easy to inspect, but they are the result of substantial underlying computation and data processing. That effort makes the results difficult to fake and gives them credibility.
In one sentence, what can AI not do here? AI can describe the system, but it cannot replace the act of running the data.
Could this system be applied to other cities around the world? Yes. The system is designed around general data engineering principles rather than Melbourne-specific logic. Many cities globally use SCATS (Sydney Coordinated Adaptive Traffic System) or comparable traffic signal systems, which generate similar data structures. With access to those datasets, the same processing pipeline could be adapted to produce equivalent traffic intelligence, including network-wide patterns, peak behaviour, and location-level analysis.
What would be required to apply this to another city? The primary requirement is access to raw traffic signal data. Once available, the process involves adapting ingestion, cleaning, and aggregation steps to the local data format. The computational approach remains the same, but each dataset typically requires validation and tuning to account for local differences in structure and quality.
Does this mean similar analysis could exist globally? Potentially, yes. Many cities already generate the underlying data required for this level of analysis. The limiting factor is not data availability, but the effort required to process and structure it at scale. Where that effort is applied, similar full-network traffic intelligence systems could be developed.
Why isn’t this already standard in cities around the world? In many cases, the data exists but is not processed into a fully usable analytical form. Converting raw traffic signal data into a clean, consistent, and queryable system requires significant engineering effort. As a result, many organisations rely on partial analysis or summaries rather than full-network reconstruction.
What changes if systems like this become widespread? It would significantly increase transparency around how traffic systems actually behave. Decisions about infrastructure, congestion management, and commercial location value could be based on full-network evidence rather than partial data or assumptions.

Technical Terms Explained (Plain English)

Tip for readers:
If you are not technical, focus on the “Why it matters” column. It explains why each concept is important to the story.
Term Plain-English Meaning Why It Matters
SCATS A traffic signal system that records vehicle movements at intersections. This is the source of the traffic signal data behind the analysis.
15-minute time bins Traffic data grouped into 15-minute intervals across each day. This allows precise analysis of when traffic actually peaks.
Data cleaning Fixing or removing invalid values from raw data. This is what turns messy public data into usable evidence.
Deduplication Removing duplicate records so the same movement is not counted twice. This protects the headline totals from being inflated.
Chunked processing Processing the dataset in smaller pieces instead of all at once. This made it possible to process billions of records without a supercomputer.
Deterministic pipeline A system where the same input always produces the same output. This makes the results repeatable, checkable, and harder to fake.
Full-network analysis Analysis across the whole traffic network, not just selected locations. This gives the page far more authority than a sample-based report.
Aggregation Combining many records into totals, rankings, or summaries. This is how billions of raw records become charts journalists can use.
Time-bin profile A breakdown showing how traffic changes through the day. This reveals real commuter behaviour, not just daily totals.
Peak window The period when traffic is at its highest. This helps identify the most important hours for congestion, planning, and advertising exposure.
OOH Out-of-home advertising, such as billboards and roadside signs. This connects traffic volume to commercial billboard and exposure value.
Commodity hardware Normal commercially available computers, not specialised supercomputers. This shows the system was built with clever design rather than institutional-scale infrastructure.
High-performance computing (HPC) Computing methods used for very large or difficult processing jobs. This explains why the project uses supercomputing-style thinking even on a single machine.
Pipeline The sequence of steps from raw data to final charts and maps. This shows the page is not just presentation — it is the output of a working data system.
Proof of work Evidence that real effort was required to produce an output. This helps explain why the page is difficult to fake: the results reflect actual computation, not instant AI generation.

Page and System Version History

Version 11 — 17 June 2026:
Added the Latest DTP Open Data Intelligence Briefs section to the main SCATS page. The new section links to the public open-data briefings archive, latest PDF brief, latest evidence pack and June 2026 release folder, and explains the repeatable monthly SCATS + TIRTL reporting capability for each new Department of Transport and Planning open-data release.
Version 10 — 17 June 2026:
Added the Melbourne Suburb Traffic Intensity Map, the Melbourne Commute + Traffic Pressure Map, and the Version 2 metro-filtered commute graph gallery. New navigation links were added near the top of the page and in the platform index so readers can jump directly to suburb traffic intensity, commute intelligence and the new commute-pressure graph set.
Version 9 — 28 May 2026:
The Melbourne SCATS Intelligence platform reached a substantially more polished public-release structure. The page was reorganised into a clearer reader journey, a chapter-style platform index was added, quick-access navigation was reordered, Melbourne Weather × SCATS interpretation was strengthened, and the public-facing structure now better supports journalists, transport professionals, OOH advertisers, councils, researchers, developers and the general public.

This section tracks the evolution of both the reporting platform and the underlying analytical environment. Each version represents a major milestone in capability, scale, engineering maturity, reproducibility, public accessibility or editorial clarity. The project has evolved from an ingestion experiment into a large-scale public transport intelligence platform supported by diagnostics, data-quality evidence, performance benchmarking, interactive maps, commercial OOH intelligence, weather-associated traffic analysis, SCATS × TIRTL integration pathways and open-source workflows.

Version Date Description
Version 1 April 2026 Initial system creation including early SCATS ingestion experiments and first-stage database schema development. Basic ingestion scripts were tested on small datasets to validate timestamp normalisation, detector structures and 15-minute storage workflows.
Version 2 Late April 2026 Large-scale ingestion capability introduced. Historical SCATS data was loaded into primary DuckDB databases including scats.duckdb and scats_continuation.duckdb. Parallel ingestion and HPC-inspired chunked processing workflows were implemented to support multi-year analytical workloads on commodity hardware.
Version 3 Early May 2026 Data validation, cleaning and recovery systems introduced. Failed source-file recovery workflows led to creation of scats_recovery.duckdb. Unified cleaned analytical layers were produced, enabling large-scale city-wide analytics across tens of billions of 15-minute observations.
Version 4 May 2026 Major analytical capability expansion. Monthly totals, daily totals, site-level summaries, yearly movement analysis, peak traffic distributions, growth indices, busiest-site intelligence and behavioural time-bin outputs were completed using standardised chunked execution pipelines.
Version 5 May 2026 Public-facing reporting framework launched. Interactive maps, cinematic traffic animations, downloadable datasets, OOH parcel intelligence, Google Maps integration, journalist-focused reporting layers and transparency notes were integrated into the public web platform.
Version 6 May 2026 Documentation and engineering maturity phase. Methodology diagrams, FAQ systems, schema inventories, diagnostics outputs, database structure summaries, system architecture notes and public-facing reproducibility sections were added. The platform began shifting from a data report into a documented analytical system.
Version 7 Mid May 2026 Database diagnostics, structural coverage and data-quality systems completed. The platform gained authoritative month auditing, yearly coverage diagnostics, deduplication evidence, interval-quality scans, negative and sentinel-value analysis, zero duplicate detector-day key confirmation and system performance benchmarking.
Version 8 16 May 2026 Near-complete Melbourne SCATS Intelligence platform achieved. The GitHub repository was finalised for public commit, yearly totals intelligence completed, PDF export systems stabilised, reproducibility pathways expanded and performance benchmarking confirmed stable operation across a 97.95GB multi-database DuckDB analytical environment. The platform became a public transport intelligence and analytical infrastructure layer for journalists, researchers, government readers, developers, OOH media and the general public.
Version 9 (Current) 28 May 2026 Major editorial, navigational and public-release refinement phase. The full page was reordered into a clearer reader journey: executive summary, headline metrics, key findings, maps, suburb intelligence, behavioural analytics, commercial OOH opportunity, SCATS × TIRTL direction, media relevance, reproducibility and technical appendix. A new chapter-style platform index was added near the top of the page, quick-access buttons were reordered to match the new structure, and the Melbourne Weather × SCATS section was strengthened with clearer public interpretation of observed weather-associated traffic behaviour. The platform now presents less like a technical archive and more like a complete public-facing Melbourne traffic intelligence portal.

About this page

This template is designed for the final unified SCATS reporting workflow. It assumes the primary analytical surface is scats_all_clean_dedup, the unified, deduplicated, cleaned 15-minute interval layer built across the original, continuation, and recovery SCATS databases.

Template last updated: 13th May 2026 AEST

Top-line reading:
The unified cleaned SCATS layer is now a mature Melbourne-wide movement intelligence base, covering 37,877,397,311 cleaned 15-minute observations across 2014-01-01 to 2026-04-07, with 707,242,951 null cleaned values identified and 0 remaining negative cleaned rows. The completed total-cleaned-volume run confirms 539,020,710,239 cleaned vehicle movements across 148 of 148 months. Recent outputs now add time-bin behaviour, weekday/weekend splits, day-of-week analysis, month-of-year seasonality, site-month intelligence, corridor dominance, OOH parcel opportunity mapping, and cinematic movement visualisations. The page now functions as a public Melbourne traffic intelligence platform, not merely a statistics report.
Important note: This platform now combines cleaned historical SCATS measurements, completed temporal analytics, OOH exposure intelligence, parcel discovery workflows, interactive maps, processing evidence and reproducible outputs. Commercial revenue and ROI figures remain scenario models, while traffic totals and behavioural profiles are measured outputs from the cleaned analytical pipeline.
Print/PDF feature: Key sections now include print-ready PDF placeholder buttons so media, analysts, and institutions can later generate cleaner hard-copy or PDF briefing packs.