Yearly traffic counts by station, New South Wales
liveThe Road Traffic Counts Yearly Summary table from Transport for NSW's NSW Roads Traffic Volume Counts dataset, as the publisher exports it from its traffic volume API. Each row is one station, year, traffic and cardinal direction, vehicle classification and period, with the traffic count, a partial year flag and the publisher's availability, reliability and quality indicators. The publisher's row number is kept as the key.
Also called: NSW annual average daily traffic by station, TfNSW traffic count yearly summary, NSW road traffic volumes by year.
Part of NSW Roads Traffic Volume Counts, 2 tables the publisher releases together: Traffic count stations, New South Wales.
- What is in each row?
- One station, year, direction, vehicle class and period of the week, such as weekdays or the morning (AM) peak, with the traffic count Transport for NSW reports for it and its flags for a partial year, data availability, reliability and quality.
- How is the traffic count formed?
- The count is the figure Transport for NSW reports for the station, year, direction, vehicle class and period named. Its documentation on the dataset page explains how counts are built. Note the partial year flag and the quality indicators before comparing stations or years.
- Where is each station?
- Join on the station key to the station table in this collection, which has the road, suburb and coordinates.
Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 22 fields, count and filter across all 276,877 rows and diff its versions. Every answer names the version and carries TfNSW's attribution. No key.
Then ask it: What does Yearly traffic counts by station, New South Wales hold, and what changed in the newest version?
claude mcp add --transport http publicdata https://publicdata.au/mcp One command. No key, no account, no sign-up.
Settings, then Connectors, then Add custom connector, and paste https://publicdata.au/mcp.
On the web and in the desktop app.
Open https://chatgpt.com/plugins/plugin_asdk_app_6abbc4cec1a08191b61eaccfe2091100 and connect the publicdata.au plugin.
Listed in ChatGPT's plugin directory. publicdata.au asks for no key and no account.
https://publicdata.au/mcp Streamable HTTP. Cursor, VS Code or any client that connects to a remote MCP server.
Using https://publicdata.au/llms.txt, how many people died on Queensland roads in 2025, by month? For an assistant that reads the web and has no connector.
The dashboard above, live. Click to filter, add panels, share a link or embed a frame.
Query APIFilter and count from a URLaggregate?group=classification_type&metric=avg.traffic_count&period=eq.ALL%20DAYS&year=eq.2026&classification_type=neq.UNCLASSIFIED&traffic_direction_seq=eq.2
Average daily vehicles at a classifying station, both directions together by classification type where period is ALL DAYS and year is 2026 and classification type is not UNCLASSIFIED and traffic direction seq is 2: 16,325 ALL VEHICLES, 14,219 LIGHT VEHICLES, 2,345 HEAVY VEHICLES.
Download it as Excel, CSV, Parquet and 4 more formats
Pick a format and a version. Excel is picked first because it opens in the tools most offices have. The URL is yours to keep. A dated version keeps its content.
One workbook with a records sheet of 276,877 typed rows, a fields sheet and a publicdata sheet with the provenance. Dates are real Excel dates. Opens in Excel, Numbers, LibreOffice and Sheets.
UTF-8 without a byte-order mark, RFC 4180 quoting, one header row using the normalised field names. Opens in Excel, Numbers and Sheets.
Columnar and typed. The smallest download and the fastest to query. Reads directly in DuckDB, pandas, Polars, Arrow and Spark. The provenance header is in the file metadata.
One database with a records table, a fields table and a publicdata metadata table. Open it with any SQLite client.
One DuckDB database with a records table of typed columns, a fields table and a publicdata metadata table. It attaches read-only over HTTPS, so DuckDB, Python and R can query it without downloading it.
The first line is the provenance header, then one JSON object per line. For streaming and for tools that read line by line.
The same CSV, gzipped, at about a tenth of the size. curl, pandas, DuckDB and R read it directly.
One JSON file per value of year, 21 files. The example is by/year/2010.json. Every file carries the same header and a partition note.
JSON is not offered because the table is 153.6 MB as NDJSON, over the 50 MB limit for JSON.
In your own tools
Use it in Excel, R, Python and more
Excel and Power BI read the CSV from its address and refresh from it. The R and Python packages take any dataset on this site by its slug, so a new dataset needs no new release. The DuckDB file attaches read-only over HTTPS, and a query reads only the blocks it touches.
The dated URL in the code never changes. https://publicdata.au/d/nsw-traffic-volume-yearly/latest/ redirects to the newest version.
https://publicdata.au/d/nsw-traffic-volume-yearly/latest/data.csv In Excel choose Data, then From Web, and paste this address. Excel keeps it, so Refresh All reads the newest version. A sheet holds about a million rows; past that, load the query to the Data Model.
https://publicdata.au/d/nsw-traffic-volume-yearly/latest/data.csv In Power BI Desktop choose Get data, then Web, paste this address and choose Anonymous when asked how to sign in. A scheduled refresh reads the same address, so the report follows each new version.
library(publicdataau)
df <- pd_read("nsw-traffic-volume-yearly")
pd_attribution(df) install.packages("publicdataau"). pd_read() fetches the version's Parquet file; pd_rows() and pd_aggregate() ask the query API instead, and pd_connect() attaches the DuckDB file.
import publicdata_au as pd_au
df = pd_au.read("nsw-traffic-volume-yearly")
df.attrs["publicdata"]["attribution"] pip install "publicdata-au[pandas]". read() fetches the version's Parquet file; rows() and aggregate() ask the query API, and connect() attaches the DuckDB file.
INSTALL httpfs; LOAD httpfs;
ATTACH 'https://publicdata.au/d/nsw-traffic-volume-yearly/v/2026-11-04/data.duckdb' AS nsw_traffic_volume_yearly (READ_ONLY);
SELECT year, count(*) FROM nsw_traffic_volume_yearly.records GROUP BY 1 ORDER BY 2 DESC; The DuckDB file attaches read-only over HTTPS and only the blocks a query touches are read. Parquet works the same way: FROM read_parquet(url).
const res = await fetch("https://publicdata.au/api/v1/datasets/nsw-traffic-volume-yearly/aggregate?group=classification_type&metric=avg.traffic_count&period=eq.ALL%20DAYS&year=eq.2026&classification_type=neq.UNCLASSIFIED&traffic_direction_seq=eq.2");
const { rows, publicdata } = await res.json();
console.log(rows, publicdata.attribution); The query API answers a page on any site as well as Node, with no key. It returns the rows and the attribution the licence asks for.
What is in it
Column names are made snake_case and the publisher's original header is kept beside each one. Blank cells are null. Nothing is added, removed, ranked or summarised.
| Field | Type | Publisher's header | Note |
|---|---|---|---|
| cartodb_id | integer | cartodb_id | |
| station_key | integer | station_key | |
| station_id | string | station_id | |
| traffic_direction_seq | integer | traffic_direction_seq | |
| traffic_direction_name | string | traffic_direction_name | |
| cardinal_direction_seq | integer | cardinal_direction_seq | |
| cardinal_direction_name | string | cardinal_direction_name | |
| classification_seq | integer | classification_seq | |
| classification_type | string | classification_type | |
| count_type | string | count_type | |
| year | integer | year | |
| period | string | period | |
| partial_year | boolean | partial_year | |
| latest_date | string | latest_date | |
| traffic_count | integer | traffic_count | |
| data_start_date | string | data_start_date | |
| data_end_date | string | data_end_date | |
| data_duration | integer | data_duration | |
| data_availability | integer | data_availability | |
| data_reliability | integer | data_reliability | |
| data_quality_indicator | integer | data_quality_indicator | |
| updated_on | string | updated_on |
Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is cartodb_id.
A sample of 10 rows
From the latest version, newest first by year, then in the publisher's order, with every field. A blank cell is shown as null.
| cartodb_id | station_key | station_id | traffic_direction_seq | traffic_direction_name | cardinal_direction_seq | cardinal_direction_name | classification_seq | classification_type | count_type | year | period | partial_year | latest_date | traffic_count | data_start_date | data_end_date | data_duration | data_availability | data_reliability | data_quality_indicator | updated_on |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 994119 | 99990014 | T0479-PR | 1 | PRESCRIBED | 1 | NORTH | 3 | HEAVY VEHICLES | TRAFFIC COUNT | 2026 | AM PEAK | false | null | 764 | null | null | null | 0 | 100 | 0 | 2026-02-08 09:15:01.294821+00 |
| 994234 | 58874 | F3FWY005 | 1 | PRESCRIBED | 1 | NORTH | 1 | ALL VEHICLES | TRAFFIC COUNT | 2026 | AM PEAK | false | null | 7259 | null | null | null | -1 | -1 | 0 | 2026-02-08 09:15:01.294821+00 |
| 994284 | 99990014 | T0479-PR | 1 | PRESCRIBED | 1 | NORTH | 3 | HEAVY VEHICLES | TRAFFIC COUNT | 2026 | WEEKDAYS | false | null | 3556 | null | null | null | -1 | -1 | 0 | 2026-02-08 09:15:01.294821+00 |
| 994406 | 99990014 | T0479-PR | 1 | PRESCRIBED | 1 | NORTH | 1 | ALL VEHICLES | TRAFFIC COUNT | 2026 | AM PEAK | false | null | 6988 | null | null | null | -1 | -1 | 0 | 2026-02-08 09:15:01.294821+00 |
| 994464 | 99990014 | T0479-PR | 1 | PRESCRIBED | 1 | NORTH | 1 | ALL VEHICLES | TRAFFIC COUNT | 2026 | WEEKDAYS | false | null | 40259 | null | null | null | -1 | -1 | 0 | 2026-02-08 09:15:01.294821+00 |
| 1055140 | 136483 | 136483 | 1 | PRESCRIBED | 1 | NORTH | 3 | HEAVY VEHICLES | TRAFFIC COUNT | 2026 | WEEKENDS | false | null | 47 | null | null | null | -1 | -1 | 0 | 2026-09-02 11:26:47.302119+00 |
| 994563 | 58874 | F3FWY005 | 1 | PRESCRIBED | 1 | NORTH | 2 | LIGHT VEHICLES | TRAFFIC COUNT | 2026 | WEEKENDS | false | null | 17508 | null | null | null | -1 | -1 | 0 | 2026-02-08 09:15:01.294821+00 |
| 1055223 | 18479665 | T0495 | 1 | PRESCRIBED | 1 | NORTH | 1 | ALL VEHICLES | TRAFFIC COUNT | 2026 | PM PEAK | false | null | 92 | null | null | null | -1 | -1 | 0 | 2026-09-02 11:26:47.302119+00 |
| 994660 | 58874 | F3FWY005 | 1 | PRESCRIBED | 1 | NORTH | 3 | HEAVY VEHICLES | TRAFFIC COUNT | 2026 | OFF PEAK | false | null | 3139 | null | null | null | 0 | 100 | 0 | 2026-02-08 09:15:01.294821+00 |
| 1055256 | 74496000 | T0596 | 1 | PRESCRIBED | 7 | WEST | 1 | ALL VEHICLES | TRAFFIC COUNT | 2026 | ALL DAYS | false | null | 16220 | null | null | null | -1 | -1 | 0 | 2026-09-02 11:26:47.302119+00 |
The first row as JSON
As it appears in data.ndjson.
GET https://publicdata.au/d/nsw-traffic-volume-yearly/latest/data.ndjson
{
"cartodb_id": 670946,
"station_key": 55318,
"station_id": "02015",
"traffic_direction_seq": 2,
"traffic_direction_name": "PRESCRIBED AND COUNTER",
"cardinal_direction_seq": 9,
"cardinal_direction_name": "BOTH",
"classification_seq": 0,
"classification_type": "UNCLASSIFIED",
"count_type": "TRAFFIC COUNT",
"year": 2018,
"period": "WEEKDAYS",
"partial_year": false,
"latest_date": null,
"traffic_count": 39273,
"data_start_date": null,
"data_end_date": null,
"data_duration": null,
"data_availability": -1,
"data_reliability": -1,
"data_quality_indicator": 0,
"updated_on": "2018-12-14 05:33:24.64657+00"
}
Query it without downloading
The query API returns only the rows you ask for, as JSON, NDJSON or CSV, from the same typed rows as the files. It needs no key. Build a query here and run it, then copy the URL or the code into your own work.
How filters work
Each filter is field=operator.value in the query string, and every filter must match. A number or date field compares as a number or date, and a text field compares as text. Values are case-sensitive, except that like and ilike ignore case in the ASCII letters A to Z. Prefix not. to negate a filter, as not.eq.value.
| Operator | What it matches |
|---|---|
| eq.value | Equal to the value. |
| neq.value | Not equal to the value. A blank cell does not match. |
| gt.value | Greater than the value. |
| gte.value | Greater than or equal to the value. |
| lt.value | Less than the value. |
| lte.value | Less than or equal to the value. |
| like.*text* | Matches a pattern where * stands for any run of characters, ignoring case in the ASCII letters A to Z. |
| ilike.*text* | The same as like. Both ignore case in ASCII letters only, so É and é differ. |
| in.(a,b,c) | Equal to any value in the list. A value cannot contain a comma. |
| is.null | Blank in the source, or suppressed by the publisher. |
| Parameter | What it does |
|---|---|
| select | Fields to return, comma-separated. Every field when absent. |
| order | field.asc or field.desc, comma-separated. When absent, rows come in the order of the file they are read from. For the newest versions that is the version's own data.parquet, which keeps the publisher's order unless the dataset sorted it. Any other version is read from the Parquet file the answer names in file, and when that file is sorted the answer names its sort in order, which ties follow too. |
| limit | Rows per page, 1 to 10,000. 100 when absent. |
| offset | Rows to skip. The next URL in each answer sets it for you. |
| group | On aggregate, fields to group by, comma-separated. |
| metric | On aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent. |
| format | json, ndjson or csv. JSON carries the provenance header, and the others carry it in response headers. |
Without a version the API answers from the newest version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer from that version alone. Every version with a table can be queried, and /api/v1/datasets/<slug>/versions lists them. A query on a version the database does not hold is read from its Parquet file, and one that would read too much of it is refused with DuckDB SQL that answers it from the file. The 2 newest versions are loaded; versions lists them.
The API allows 60 requests in 10 seconds from one address. Above that it answers 429 for 10 seconds with a Retry-After header, a RateLimit-Policy header and a JSON body that gives the limit. Every API answer carries the same RateLimit-Policy. A client should wait the Retry-After seconds, or read the files, which have no limit. openapi.json describes this dataset's query paths for client generators and agents.
https://publicdata.au/mcp is a remote MCP server over Streamable HTTP with the same tools, defined in the same place, so a tool added to the pages is added here too. It needs no key and no account. Its row tools and the query API answer every version through one query path, so a tool's answer and the query URL it cites give the same rows. A query that would read too much of a file is refused with DuckDB SQL that answers it from the file. It also has search and fetch, the two tools ChatGPT's deep research and company knowledge call by name, which run search_datasets and read a dataset's record in the shapes those features expect. The row tools are held to the query API's limit of 60 queries in 10 seconds from one address, and each call is two queries because it also counts the matching rows. Add it to Claude Code with claude mcp add --transport http publicdata https://publicdata.au/mcp, add the URL in Claude as a custom connector, connect the publicdata.au plugin in ChatGPT, or give it to any client that connects to remote MCP servers. Each dataset with a table is also a resource at https://publicdata.au/d/<slug>/fields.json, which lists its fields with their types, the publisher's descriptions, their ranges and the values they hold, so an agent can read a dataset's shape before it writes a query.
Smaller files
The same rows split by a field, one JSON file each. Each file carries the same provenance header.
By year (21 files)
by/year/index.json lists every file with its row count.
What changed
One version for every release the publisher has made since this site started following the dataset. The date is the day the file changed on the portal.
- 2026-11-04 276,877 rows+8364 added −8364 removed 0 changed22 fieldsutf-8-sig9033e97d659d
- 2026-10-11 276,877 rows+832 added −832 removed 0 changed22 fieldsutf-8-sig52016d8b9f1b
- 2026-10-04 276,877 rows+9582 added −9567 removed 1 changed22 fieldsutf-8-sig27a429d13b43
- 2026-09-04 276,862 rows22 fieldsutf-8-sig9ac6aca26db7
versions.json · changes.json · history.tar.zst (4.1 MB, every version's Parquet and manifest)
Questions
How do I download Yearly traffic counts by station as a CSV file?
Open https://publicdata.au/d/nsw-traffic-volume-yearly/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/nsw-traffic-volume-yearly/v/2026-11-04/data.csv today. The same path serves Excel, Parquet, SQLite, DuckDB, NDJSON. A dated URL never changes, so use it when the file must stay the same.
Can I open Yearly traffic counts by station in Excel?
Yes. https://publicdata.au/d/nsw-traffic-volume-yearly/v/2026-11-04/data.xlsx is a workbook with the 276,877 rows on a records sheet, the field list on a second sheet and the provenance on a third. The CSV also opens in Excel. https://publicdata.au/d/nsw-traffic-volume-yearly/v/2026-11-04/data.csv.gz is the CSV at about a tenth of the size.
What years does Yearly traffic counts by station cover?
The current version covers 2006 to 2025. Each release from TfNSW becomes a new dated version here, and earlier versions stay online.
How often is Yearly traffic counts by station updated?
TfNSW releases it irregularly. This site checks the portal every week and adds a dated version when the file changes.
Can I use Yearly traffic counts by station commercially?
Yes. CC BY 4.0 allows commercial use, redistribution and derived works as long as the attribution is kept. The attribution string is in this page's side column and inside every file.
Is this the official source for Yearly traffic counts by station?
No. The publisher is Transport for NSW, and its page is https://data.nsw.gov.au/data/dataset/2-nsw-roads-traffic-volume-counts-api. National Digital converted the publisher's file to other formats. It renamed and typed the columns and kept only those the schema lists. National Digital made these changes, and the publisher is not responsible for them. The original sits beside every version as source.csv with its SHA-256, so the two can be compared.
How do I get only the rows for one year?
Every version has one JSON file per value of year, 21 files in the current version, listed with row counts at https://publicdata.au/d/nsw-traffic-volume-yearly/v/2026-11-04/by/year/index.json. For example https://publicdata.au/d/nsw-traffic-volume-yearly/v/2026-11-04/by/year/2010.json holds the 23,333 rows where year is 2010.
What this site did to the data. Cells were typed, headers were renamed and the encoding was made UTF-8. Rows were left alone. The publisher's file sits beside every version as source.csv so the change can be checked.
NSW Roads Traffic Volume Counts is 2 tables here, and each takes its version date from its own file.
The licence requires the publisher's attribution. We ask that you also name publicdata.au and link to the version you used.
Transport for NSW, NSW Government, NSW Roads Traffic Volume Counts API, sourced 9 November 2026, https://data.nsw.gov.au/data/dataset/2-nsw-roads-traffic-volume-counts-api, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/nsw-traffic-volume-yearly/v/2026-11-04/
The attribution alone is inside every file. Harvard is the author-date form a report or a brief asks for. Paste the HTML on a web page so the links carry.
Transport for NSW states the licence, CC BY 4.0, on its own page, which was read and recorded here on 1 October 2026.
Every fetch reads the licence again and stops when it has changed. The fetch that made version 2026-11-04 read it from data.nsw.gov.au on 9 November 2026.
- Hugging Faceload_dataset("National-Digital/nsw-traffic-volume-yearly")
- Kagglewith a starter notebook
- ZenodoDOI 10.5281/zenodo.23123109
Each copy carries the same attribution and links back to this page.
- datapackage.jsonFrictionless data package pointing at the latest version
- schema.jsonTable Schema for every field
- schema.xlsxthe same field list as an Excel data dictionary
- versions.jsonevery version with date, rows, fields and hash
- changes.jsondiff for every consecutive pair
- manifest.jsonwhere the bytes came from and when
- Query APIfiltered rows and counts without a download
- openapi.jsonOpenAPI 3.1 for this dataset's query paths
- explore/charts and dashboards in the browser, shareable and embeddable
- index.mdthis page as Markdown
This page carries a schema.org Dataset record and is listed in /.well-known/ard.json and /catalog.json.
Transport for NSW publishes this table on opendata.transport.nsw.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.
Fetched 9 November 2026. Source SHA-256 9033e97d659d8ad3…
This page is built from register/nsw-traffic-volume-yearly.yaml on GitHub. Anyone can propose a fix to it, such as a clearer description or a field the publisher renamed, as a pull request.
Report a file that differs from the publisher's · How to contribute