Combined SCATS + TIRTL Future ChatGPT Briefing Pack

Critical terminology warning

System overview

Recommended future upload checklist

Top TIRTL datasets

Top SCATS datasets

If this table is empty, re-run this script with the correct SCATS data dictionary directory.

Future page/data-product ideas

Future ChatGPT starter prompt

I have uploaded my Combined SCATS + TIRTL Future ChatGPT Briefing Pack plus the relevant data dictionary CSVs and selected data outputs. Please read the briefing pack first, then use the priority dataset catalogue and column dictionaries to help me design the next traffic intelligence page, journalist pack, dashboard, data product, or methodology document. Remember that vehicle movements and truck movements are sensor passings, not unique vehicles.

Markdown briefing copy

# Combined SCATS + TIRTL Future ChatGPT Briefing Pack

Generated: 2026-05-24T16:17:34
Version: v1

## Purpose

This briefing pack is designed to be uploaded into future ChatGPT sessions so the assistant can quickly understand the available Melbourne SCATS and TIRTL traffic intelligence outputs, their columns, their public-release value, and how they should be used to build new pages, dashboards, journalist packs, maps, data products, methodology documents, and commercial ideas.

## Critical terminology warning

**Important terminology: vehicle movements, truck movements, vehicles, and trucks in these traffic intelligence outputs refer to sensor movement records / passings. They should not be interpreted as counts of unique vehicles or unique trucks.**

This distinction matters because a single real-world vehicle may appear multiple times if it passes multiple sensors, directions, site-headings, or corridors.

## System overview

### SCATS

SCATS is the large historical traffic signal / intersection movement intelligence layer. It is best suited to long-term traffic pressure analysis, suburb intelligence, busiest site rankings, time-of-day trends, day-of-week trends, month/year trends, public dashboards, and media-friendly city-scale movement analysis.

Typical SCATS use cases:

- Suburb traffic intelligence pages and PDFs.
- Busiest intersections and corridors.
- Worst times to drive.
- Long-term trend and COVID-era comparison work.
- OOH advertising and parcel opportunity discovery.
- Journalist queries requiring suburb, site, corridor, or temporal rankings.

### TIRTL

TIRTL is the truck movement and truck-share intelligence layer. It is best suited to truck-heavy corridor analysis, freight/logistics exposure, suburb truck-share rankings, truck movement maps, and comparison of heavy-vehicle pressure across Melbourne road corridors.

Typical TIRTL use cases:

- Top truck movement sites.
- Highest truck-share sites.
- Truck movement suburb/locality summaries.
- Freight corridor maps.
- Logistics, industrial property, planning, media, council, and transport analysis.

## TIRTL dictionary status

TIRTL dictionary found and loaded.

- Files catalogued: 16
- Column rows: 238
- Priority datasets: 16

### Highest-value TIRTL datasets

1. `tirtl_top_truck_share_sites_enriched.csv` — Truck-share ranking — score 95 — Good public release candidate
2. `tirtl_top_truck_sites_enriched.csv` — Truck movement ranking — score 93 — Good public release candidate
3. `melbourne_tirtl_truck_map_layer.csv` — Map layer / geospatial — score 81 — Good public release candidate
4. `tirtl_top_truck_share_sites.csv` — Truck-share ranking — score 72 — Good public release candidate
5. `tirtl_top_truck_sites.csv` — Truck movement ranking — score 70 — Good public release candidate
6. `tirtl_suburb_truck_summary.csv` — Suburb/locality truck intelligence — score 68 — Good public release candidate
7. `tirtl_site_locality_lookup.csv` — Spatial join / locality lookup — score 54 — Public methodology / technical appendix
8. `tirtl_daily_summary.csv` — Daily network trend — score 53 — Good public release candidate
9. `tirtl_monthly_network_summary.csv` — Monthly network trend — score 48 — Good public release candidate
10. `tirtl_monthly_network_summary_export.csv` — Monthly network trend — score 48 — Good public release candidate
11. `tirtl_site_heading_master.csv` — Site master / lookup — score 47 — High-value public summary; consider keeping full CSV controlled
12. `tirtl_site_heading_summary.csv` — Site master / lookup — score 43 — Public methodology / technical appendix

## SCATS dictionary status

SCATS dictionary was not found at the supplied folder. This pack still works as a TIRTL briefing pack, but for combined SCATS + TIRTL work, upload the SCATS data dictionary CSVs/HTML as well.

## Recommended future ChatGPT upload packs

### Minimum orientation pack

Upload these when starting a future traffic-intelligence chat:

- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\data_dictionary\tirtl_data_dictionary_priority_datasets_v3.csv` — TIRTL priority dataset list — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\data_dictionary\tirtl_data_dictionary_files_v3.csv` — TIRTL file catalogue — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\data_dictionary\tirtl_data_dictionary_columns_v3.csv` — TIRTL column catalogue — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\data_dictionary\tirtl_data_dictionary_summary_v3.json` — TIRTL summary JSON — exists: YES
- `` — SCATS priority dataset list — exists: UNKNOWN
- `` — SCATS file catalogue — exists: UNKNOWN
- `` — SCATS column catalogue — exists: UNKNOWN

### TIRTL page/dashboard build pack

- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_top_truck_share_sites_enriched.csv` — Best journalist-facing truck-share ranking — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_top_truck_sites_enriched.csv` — Best journalist-facing truck-volume ranking — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\melbourne_tirtl_truck_map_layer.csv` — Main TIRTL map/dashboard layer — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_suburb_truck_summary.csv` — Suburb/locality truck summary — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_monthly_network_summary.csv` — Monthly network trend — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_daily_summary.csv` — Daily network trend — exists: YES

### Technical methodology pack

- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_site_locality_lookup.csv` — Spatial join proof / methodology — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_site_heading_master.csv` — TIRTL site-heading master / joins — exists: YES
- `A:\TrafficAnalytics\PROJECTS\reports\tirtl_melbourne\exports\tirtl_import_manifest.csv` — Import audit / reproducibility — exists: YES

## Best page/data-product ideas now possible

### TIRTL-specific pages

- Melbourne's highest truck-share roads.
- Melbourne's busiest truck movement corridors.
- Suburb-by-suburb truck pressure rankings.
- Industrial freight exposure map.
- Truck movement methodology and data-quality page.
- Truck movement story pack for journalists.
- Freight-heavy suburb profiles.
- Council-level or corridor-level truck burden summaries.

### SCATS + TIRTL combined pages

- Melbourne traffic pressure vs truck pressure comparison.
- Suburbs with high total traffic but low truck share.
- Suburbs with moderate traffic but unusually high truck share.
- Freight corridors vs commuter corridors.
- OOH advertising opportunity map combining total movement exposure and truck/freight exposure.
- Industrial property intelligence pages.
- Council planning intelligence packs.
- Journalist query assistant / data concierge page.

## Suggested prompt for future ChatGPT sessions

Copy/paste this into a future chat after uploading the files:

```text
I have uploaded my Combined SCATS + TIRTL Future ChatGPT Briefing Pack plus the relevant data dictionary CSVs and selected data outputs. Please read the briefing pack first, then use the priority dataset catalogue and column dictionaries to help me design the next traffic intelligence page, journalist pack, dashboard, data product, or methodology document. Remember that vehicle movements and truck movements are sensor passings, not unique vehicles.
```