publicdata.au publicdata.au on GitHub

Traffic camera locations, ACT

live
Publisher Access Canberra, City and Environment DirectorateUpdated monthlyLicence CC BY 4.0Latest 2026-10-29Rows 1,283Fields 8

The 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.

Before you use it
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.
1,272 camera locations drawn in 35 cells of 0.05 degrees, the fullest with 111.
Camera locations counted in cells of 0.05 degrees. State outlines from the ABS Australian Statistical Geography Standard 2021, CC BY 4.0.
1,283camera locations
2002 to 2022years drawn
8fields
11formats
2versions
012342002 MOBILE SPEED CAMERA: 220022007 MOBILE SPEED CAMERA: 220072008 MOBILE SPEED CAMERA: 420082009 MOBILE SPEED CAMERA: 220092016 MOBILE SPEED CAMERA: 22016 POINT TO POINT CAMERA: 220162017 MOBILE SPEED CAMERA: 320172020 MOBILE SPEED CAMERA: 320202022 MOBILE SPEED CAMERA: 22022
MOBILE SPEED CAMERAPOINT TO POINT CAMERA
Camera locations decommissioned per year by camera type, 2002 to 2022. 2001 is not drawn because the rows begin on 1 April 2001. 2024 is not drawn because the rows run to 1 October 2024. Both figures are counts of rows from version 2026-10-29, worked out in the build. Nothing else is added.

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,283 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/mcp

One command. No key, no account, no sign-up.

Download it as Excel, CSV, JSON and 8 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.

Format
"Latest" redirects to the newest version and will change when the publisher releases again. A dated version keeps its content.
https://publicdata.au/d/act-traffic-camera-locations/latest/data.xlsx
Download this file

One workbook with a records sheet of 1,283 typed rows, a fields sheet and a publicdata sheet with the provenance. Dates are real Excel dates. Opens in Excel, Numbers, LibreOffice and Sheets.

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.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.

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.

FieldTypePublisher's headerNote
camera_typestringCAMERA TYPE
camera_location_codestringCAMERA LOCATION CODE
location_codestringLOCATION_CODE
latitudenumberLATITUDE
longitudenumberLONGITUDE
location_descriptionstringLOCATION DESCRIPTION
locationstringLocationThe publisher's own text of the coordinates, as (latitude, longitude).
decommissioned_datedateDecommissioned Camera_DateThe 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_typecamera_location_codelocation_codelatitudelongitudelocation_descriptionlocationdecommissioned_date
FIXED ONLY SPEED CAMERA10301030-35.22567149.16112FEDERAL HIGHWAY BETWEEN ZELLING STREET AND ANTILL STREET(-35.22567, 149.16112)null
MOBILE SPEED CAMERA30623062-35.355139149.053829Badimara Street Waramanga(-35.355139, 149.053829)null
POINT TO POINT CAMERA2002/20032002-35.3471149.10827HINDMARSH DRIVE WESTBOUND BETWEEN MUGGA LANE AND TYAGARAH STREET(-35.3471, 149.10827)null
RED LIGHT AND SPEED CAMERA10251025-35.1863149.1191GUNGAHLIN DRIVE/GUNDAROO DRIVE(-35.1863, 149.1191)null
FIXED ONLY SPEED CAMERA10341034-35.3193149.06346TUGGERANONG PARKWAY NEAR COTTER ROAD OVERPASS, NORTHBOUND(-35.3193, 149.06346)null
MOBILE SPEED CAMERA01220122I-35.23807149.11362Gungahlin Drive, Australian Capital Territory 2617, Australia(-35.23807, 149.11362)null
POINT TO POINT CAMERA2006/20072006-35.395173149.074769ATHLLON DRIVE SOUTHBOUND BETWEEN BEASLEY STREET AND DRAKEFORD DRIVE(-35.395173, 149.074769)2016-11-01
RED LIGHT AND SPEED CAMERA10201020-35.2755149.12725BARRY DRIVE/MARCUS CLARKE STREET(-35.2755, 149.12725)null
FIXED ONLY SPEED CAMERA1026Snull-35.19198149.08327BARTON HIGHWAY BETWEEN CURRAN DRIVE AND GOLD CREEK ROAD(-35.19198, 149.08327)null
MOBILE SPEED CAMERA0196F0196F-35.1854149.14814271 Anthony Rolfe Ave, Gungahlin ACT 2912, Australia(-35.1854, 149.14814)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": "RED LIGHT AND SPEED CAMERA",
  "camera_location_code": "1025",
  "location_code": "1025",
  "latitude": -35.1863,
  "longitude": 149.1191,
  "location_description": "GUNGAHLIN DRIVE/GUNDAROO DRIVE",
  "location": "(-35.1863, 149.1191)",
  "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.

Try rows or aggregate for this dataset. The query builder needs JavaScript.

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.

OperatorWhat it matches
eq.valueEqual to the value.
neq.valueNot equal to the value. A blank cell does not match.
gt.valueGreater than the value.
gte.valueGreater than or equal to the value.
lt.valueLess than the value.
lte.valueLess 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.nullBlank in the source, or suppressed by the publisher.
ParameterWhat it does
selectFields to return, comma-separated. Every field when absent.
orderfield.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.
limitRows per page, 1 to 10,000. 100 when absent.
offsetRows to skip. The next URL in each answer sets it for you.
groupOn aggregate, fields to group by, comma-separated.
metricOn aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent.
formatjson, 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 with a GeoJSON beside it. Each file carries the same provenance header.

By camera_type (4 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-10-29
    1,283 rows8 fieldsutf-8-sig69453548cf66
  • 2026-08-21
    1,262 rows8 fieldsutf-8-sig267a8ceb6aaa

versions.json · changes.json · history.tar.zst (106 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-10-29/data.csv today. The same path serves Excel, JSON, GeoJSON, Parquet, SQLite, DuckDB, GeoPackage, GeoParquet, NDJSON. 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-10-29/data.xlsx is a workbook with the 1,283 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-10-29/data.csv.gz is the CSV at about a tenth of the size.

What years does Traffic camera locations cover?

The current version covers 2002 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. 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 camera type?

Every version has one JSON file per value of camera_type, 4 files in the current version, listed with row counts at https://publicdata.au/d/act-traffic-camera-locations/v/2026-10-29/by/camera_type/index.json. For example https://publicdata.au/d/act-traffic-camera-locations/v/2026-10-29/by/camera_type/mobile-speed-camera.json holds the 1,253 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.

Attribution and citation

The licence requires the publisher's attribution. We ask that you also name publicdata.au and link to the version you used.

Access Canberra, ACT Government, Traffic speed camera locations, https://www.data.act.gov.au/d/426s-vdu4, accessed 2 November 2026, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/act-traffic-camera-locations/v/2026-10-29/

The map's state outlines are from the ABS Australian Statistical Geography Standard 2021, under CC BY 4.0.

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.

Licence record

Access Canberra, City and Environment Directorate 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-10-29 read it from www.data.act.gov.au on 2 November 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/act-traffic-camera-locations")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23123518

Each copy carries the same attribution and links back to this page.

For agents and tools

This page carries a schema.org Dataset record and is listed in /.well-known/ard.json and /catalog.json.

Source

Access Canberra, City and Environment Directorate publishes this table on www.data.act.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 2 November 2026. Source SHA-256 69453548cf66fce9…

Improve this dataset

This page is built from register/act-traffic-camera-locations.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