Traffic camera locations, ACT
liveThe locations of the ACT's traffic enforcement cameras as Access Canberra lists them, with fixed speed cameras, red light and speed cameras, point to point cameras and mobile speed camera sites. Each row carries the camera type, the camera location code, the location code, the latitude and longitude, a description of the location, the publisher's own text of the coordinates and the date the camera was decommissioned where that applies.
Also called: Canberra speed camera locations, ACT red light camera locations, ACT point to point camera locations, ACT mobile speed camera sites.
Part of Traffic and parking fines in the ACT, 6 tables the publisher releases together: Traffic and camera offences and fines, ACT, Traffic camera offences and fines, ACT, 2010 to 2021, Parking offences and fines, ACT, Mobile speed camera visits, ACT, Mobile phone detection camera sites, ACT.
- What is in each row?
- One traffic enforcement camera or mobile speed camera site, with its camera type, its location codes, its coordinates, a description of the place and the date it was decommissioned if it has been.
- Are decommissioned cameras included?
- Yes. The publisher keeps every location, including those no longer in use, and gives the date a camera was decommissioned.
- Does every location have coordinates?
- No. Some older mobile sites have no latitude or longitude, and three rows carry only the publisher's text of the coordinates with no camera type or code. They are kept as published, and one row that is blank in every column is left out.
- How do I link it to the fines?
- The camera location code matches the camera location in the ACT traffic and camera fines tables in this collection. The publisher says some cleaning may be needed for the codes to match.
Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 8 fields, count and filter across all 1,262 rows and diff its versions. Every answer names the version and carries Access Canberra's attribution. No key.
Then ask it: What does Traffic camera locations, ACT hold, and what changed in the newest version?
claude mcp add --transport http publicdata https://publicdata.au/mcpOne 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.
https://publicdata.au/mcpStreamable 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=camera_type&metric=count
Camera locations by camera type: 1,229 MOBILE SPEED CAMERA, 13 RED LIGHT AND SPEED CAMERA, 13 FIXED ONLY SPEED CAMERA, 4 POINT TO POINT CAMERA.
Download it as Excel, CSV, JSON and 9 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 never changes.
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/act-traffic-camera-locations/latest/ redirects to the newest version.
https://publicdata.au/d/act-traffic-camera-locations/latest/data.csvIn 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/act-traffic-camera-locations/latest/data.csvIn 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("act-traffic-camera-locations")
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("act-traffic-camera-locations")
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/act-traffic-camera-locations/v/2026-08-21/data.duckdb' AS act_traffic_camera_locations (READ_ONLY);
SELECT camera_type, count(*) FROM act_traffic_camera_locations.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/act-traffic-camera-locations/aggregate?group=camera_type&metric=count");
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. Cells were typed and headers were made snake_case. The publisher's header is kept beside every field in schema.json. Rows were left alone.
| Field | Type | Publisher's header | Note |
|---|---|---|---|
| camera_type | string | CAMERA TYPE | |
| camera_location_code | string | CAMERA LOCATION CODE | |
| location_code | string | LOCATION_CODE | |
| latitude | number | LATITUDE | |
| longitude | number | LONGITUDE | |
| location_description | string | LOCATION DESCRIPTION | |
| location | string | Location | The publisher's own text of the coordinates, as (latitude, longitude). |
| decommissioned_date | date | Decommissioned Camera_Date | The month the camera was decommissioned, as its first day. Blank for a camera in use. |
Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json.
A sample of 10 rows
One location of each camera type in turn, in the publisher's order, leaving out rows with no coordinates. A blank cell is shown as null.
| camera_type | camera_location_code | location_code | latitude | longitude | location_description | location | decommissioned_date |
|---|---|---|---|---|---|---|---|
| FIXED ONLY SPEED CAMERA | 1033N | 1033 | -35.34778 | 149.069481 | TUGGERANONG PARKWAY NEAR HINDMARSH DRIVE UNDERPASS | (-35.34778, 149.069481) | null |
| MOBILE SPEED CAMERA | 0286 | 0286A | -35.319037 | 149.139831 | 6 Eyre Street Kingston ACT 2604 Australia | (-35.319037, 149.139831) | null |
| POINT TO POINT CAMERA | 2006/2007 | 2006 | -35.395173 | 149.074769 | ATHLLON DRIVE SOUTHBOUND BETWEEN BEASLEY STREET AND DRAKEFORD DRIVE | (-35.395173, 149.074769) | 2016-11-01 |
| RED LIGHT AND SPEED CAMERA | 1002 | 1002 | -35.2761 | 149.12948 | NORTHBOURNE AVENUE/BARRY DRIVE/COOYONG STREET | (-35.2761, 149.12948) | null |
| FIXED ONLY SPEED CAMERA | 1026S | null | -35.19198 | 149.08327 | BARTON HIGHWAY BETWEEN CURRAN DRIVE AND GOLD CREEK ROAD | (-35.19198, 149.08327) | null |
| MOBILE SPEED CAMERA | 3072 | 3072A | -35.394284 | 149.096534 | Langdon Ave Wanniassa ACT 2903 Australia | (-35.394284, 149.096534) | null |
| POINT TO POINT CAMERA | 2005/2008 | 2008 | -35.373625 | 149.092969 | ATHLLON DRIVE NORTHBOUND BETWEEN DRAKEFORD DRIVE AND BEASLEY STREET | (-35.373625, 149.092969) | 2016-11-01 |
| RED LIGHT AND SPEED CAMERA | 1006 | 1006 | -35.24783 | 149.13412 | NORTHBOURNE AVENUE/ANTILL STREET/MOUAT STREET | (-35.24783, 149.13412) | null |
| FIXED ONLY SPEED CAMERA | 1026N | 1026 | -35.19213 | 149.08327 | BARTON HIGHWAY BETWEEN CURRAN DRIVE AND GOLD CREEK ROAD | (-35.19213, 149.08327) | null |
| MOBILE SPEED CAMERA | 0283 | 0283B | -35.361179 | 149.077721 | 80 Macfarland Crescent Chifley ACT 2606 Australia | (-35.361179, 149.077721) | null |
The first row as JSON
As it appears in data.json.
GET https://publicdata.au/d/act-traffic-camera-locations/latest/data.json
{
"camera_type": "MOBILE SPEED CAMERA",
"camera_location_code": "0286",
"location_code": "0286A",
"latitude": -35.319037,
"longitude": 149.139831,
"location_description": "6 Eyre Street Kingston ACT 2604 Australia",
"location": "(-35.319037, 149.139831)",
"decommissioned_date": null
}
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 with ilike. 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. Case-sensitive. |
| ilike.*text* | The same as like, ignoring case. |
| 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. The publisher's row order when absent. |
| 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 loaded version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer that never changes. /api/v1/datasets/<slug>/versions lists the loaded versions. The 1 newest version is 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. 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, or give it to any client that connects to remote MCP servers. Each queryable dataset 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 with a GeoJSON beside it. Each file carries the same provenance header.
By camera_type (5 files)
by/camera_type/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-08-21 1,262 rows8 fieldsutf-8-sig267a8ceb6aaa
versions.json · changes.json · history.tar.zst (55 KB, every version's Parquet and manifest)
Questions
How do I download Traffic camera locations as a CSV file?
Open https://publicdata.au/d/act-traffic-camera-locations/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/act-traffic-camera-locations/v/2026-08-21/data.csv today. The same path serves Excel, JSON, GeoJSON, Parquet, SQLite, DuckDB, GeoPackage, GeoParquet, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.
Can I open Traffic camera locations in Excel?
Yes. https://publicdata.au/d/act-traffic-camera-locations/v/2026-08-21/data.xlsx is a workbook with the 1,262 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/act-traffic-camera-locations/v/2026-08-21/data.csv.gz is the CSV at about a tenth of the size.
What years does Traffic camera locations cover?
The current version covers 2007 to 2022. Each release from Access Canberra becomes a new dated version here, and earlier versions stay online.
How often is Traffic camera locations updated?
Access Canberra releases it monthly. This site checks the portal every week and adds a dated version when the file changes.
Can I use Traffic camera locations 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 Traffic camera locations?
No. The publisher is Access Canberra, City and Environment Directorate, and its page is https://www.data.act.gov.au/d/426s-vdu4. This site republishes the publisher's file without changing its content. 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 camera type?
Every version has one JSON file per value of camera_type, 5 files in the current version, listed with row counts at https://publicdata.au/d/act-traffic-camera-locations/v/2026-08-21/by/camera_type/index.json. For example https://publicdata.au/d/act-traffic-camera-locations/v/2026-08-21/by/camera_type/mobile-speed-camera.json holds the 1,229 rows where camera_type is MOBILE SPEED CAMERA. A GeoJSON file sits beside each one.
What coordinate system does Traffic camera locations use?
Longitude and latitude in decimal degrees as published. The publisher does not name the datum; GDA94 differs from GDA2020 and WGS84 by under 2 metres. The GeoJSON file uses the same coordinates, which is what GeoJSON expects.
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.
Traffic and parking fines in the ACT is 6 tables here, and each takes its version date from its own file.