publicdata.au publicdata.au on GitHub

Road crash locations, South Australia

live
Publisher Department for Infrastructure and TransportUpdated yearlyLicence CC BY 4.0Latest 2025-09-19Rows 43,522Fields 40

One row per location where a road crash was reported to South Australia Police from 2020 to 2024. Each row carries the site's coordinates, the number of crashes there, and counts of those crashes by severity (property damage, injury, serious injury, fatal), by type (rear end, hit fixed object, head on and others), at night, and involving a bicycle or a pedestrian, with the numbers of casualties, serious injuries and deaths.

The Department for Infrastructure and Transport releases a new five-year file each year.

Also called: Road Crash Locations in SA, SA crash sites, South Australian car accident locations, DIT road crash data.

Before you use it
Is each row one crash?
No. Each row is one location where crashes happened in the five years, with the number of crashes there and counts by severity, crash type and road user. The publisher's separate Road Crash Data files on the portal have one row per crash, without coordinates.
Why does the file cover only five years?
The publisher releases a new five-year file each year and keeps the earlier files on the portal. This dataset follows the newest file, so each release becomes a version here.
Which coordinates are these?
The publisher supplies the same file in GDA94 and GDA2020. This dataset uses the GDA2020 file, which is the current national datum.
43,522 crash sites drawn in 2,308 cells of 0.05 degrees, the fullest with 2,755.
Crash sites counted in cells of 0.05 degrees. State outlines from the ABS Australian Statistical Geography Standard 2021, CC BY 4.0.
43,522crash sites
40fields
12formats
1version

Made for agents

Connect your AI agent

Any agent that connects to publicdata.au/mcp can find this dataset, read its 40 fields, count and filter across all 43,522 rows and diff its versions. Every answer names the version and carries Infrastructure and Transport's attribution. No key.

Then ask it: What does Road crash locations, South Australia 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 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 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/sa-road-crash-locations/latest/data.xlsx
Download this file

One workbook with a records sheet of 43,522 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/sa-road-crash-locations/latest/ redirects to the newest version.

https://publicdata.au/d/sa-road-crash-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 the point geometry became longitude and latitude fields. The publisher's property names are kept beside every field in schema.json. Rows were left alone.

FieldTypePublisher's headerNote
unique_locstringunique_locThe publisher's identifier for the location. Kept as text to preserve leading zeros.
longitudenumber(longitude)Decimal degrees, GDA2020, from the point geometry.
latitudenumber(latitude)Decimal degrees, GDA2020, from the point geometry.
total_crashesintegertotal_crashes
cse_pdointegercse_pdo
cse_injintegercse_inj
cse_fatintegercse_fat
cse_siintegercse_si
total_casualtiesintegertotal_casualties
total_fatalitiesintegertotal_fatalities
total_serious_injuriesintegertotal_serious_injuries
cty_rear_endintegercty_rear_end
cty_hit_fixed_objectintegercty_hit_fixed_object
cty_side_swipeintegercty_side_swipe
cty_right_angleintegercty_right_angle
cty_head_onintegercty_head_on
cty_hit_pedestrianintegercty_hit_pedestrian
cty_roll_overintegercty_roll_over
cty_right_turnintegercty_right_turn
cty_hit_parked_vehileintegercty_hit_parked_vehileThe publisher's header spells vehicle as vehile.
cty_hit_animalintegercty_hit_animal
cty_hit_object_on_roadintegercty_hit_object_on_road
cty_left_road_ocintegercty_left_road_oc
cty_otherintegercty_other
cty_unknownintegercty_unknown
uty_bicycleintegeruty_bicycle
uty_pedestrianintegeruty_pedestrian
lco_nightintegerlco_night
sa2_2021_codestring(spine: sa2)Code of the Statistical Area Level 2 (2021) the point falls in. Joined by location from abs-sa2-2021, not published by the publisher.
sa2_2021_namestring(spine: sa2)Name of the Statistical Area Level 2 (2021) the point falls in. Joined by location from abs-sa2-2021, not published by the publisher.
lga_2025_codestring(spine: lga)Code of the Local Government Area (2025) the point falls in. Joined by location from abs-lga-2025, not published by the publisher.
lga_2025_namestring(spine: lga)Name of the Local Government Area (2025) the point falls in. Joined by location from abs-lga-2025, not published by the publisher.
sal_2021_codestring(spine: suburb)Code of the Suburb and Locality (2021) the point falls in. Joined by location from abs-suburbs-localities-2021, not published by the publisher.
sal_2021_namestring(spine: suburb)Name of the Suburb and Locality (2021) the point falls in. Joined by location from abs-suburbs-localities-2021, not published by the publisher.
poa_2021_codestring(spine: postcode)Code of the Postal Area (2021) the point falls in. Joined by location from abs-postal-areas-2021, not published by the publisher.
poa_2021_namestring(spine: postcode)Name of the Postal Area (2021) the point falls in. Joined by location from abs-postal-areas-2021, not published by the publisher.
sed_2025_codestring(spine: state_electorate)Code of the State Electoral Division (2025) the point falls in. Joined by location from abs-state-electoral-divisions-2025, not published by the publisher.
sed_2025_namestring(spine: state_electorate)Name of the State Electoral Division (2025) the point falls in. Joined by location from abs-state-electoral-divisions-2025, not published by the publisher.
ced_2025_codestring(spine: federal_electorate)Code of the Commonwealth Electoral Division (2025) the point falls in. Joined by location from abs-federal-electoral-divisions-2025, not published by the publisher.
ced_2025_namestring(spine: federal_electorate)Name of the Commonwealth Electoral Division (2025) the point falls in. Joined by location from abs-federal-electoral-divisions-2025, not published by the publisher.

Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is unique_loc.

A sample of 10 rows

The ten sites with the most crashes in the five years, most first. A blank cell is shown as null.

unique_loclongitudelatitudetotal_crashescse_pdocse_injcse_fatcse_sitotal_casualtiestotal_fatalitiestotal_serious_injuriescty_rear_endcty_hit_fixed_objectcty_side_swipecty_right_anglecty_head_oncty_hit_pedestriancty_roll_overcty_right_turncty_hit_parked_vehilecty_hit_animalcty_hit_object_on_roadcty_left_road_occty_othercty_unknownuty_bicycleuty_pedestrianlco_nightsa2_2021_codesa2_2021_namelga_2025_codelga_2025_namesal_2021_codesal_2021_namepoa_2021_codepoa_2021_namesed_2025_codesed_2025_nameced_2025_codeced_2025_name
13306231670362138.623404838-34.92788603311910217011801166128500000000005026401011001Adelaide40070Adelaide40002Adelaide5000500040001Adelaide401Adelaide
13323731666371138.644042057-34.96334935568521603250525336200110000001013401071024Unley - Parkside47980Unley40999Myrtle Bank (SA)5064506440044Unley410Sturt
13337861674517138.65649356-34.88945226557421503250411424000360000000022401051018Payneham - Felixstow45290Norwood Payneham and St Peters40515Glynde5070507040020Hartley410Sturt
13296901660049138.616971843-35.02117822349427007001111360000000000306403031067Blackwood44340Mitcham40119Blackwood (SA)5051505140045Waite403Boothby
13318741670399138.637090477-34.9271748394933160122010003000118000000208401051017Norwood (SA)45290Norwood Payneham and St Peters41053Norwood (SA)5067506740010Dunstan410Sturt
13241231670939138.552010461-34.9246302084830180426053201000420000001019404031108Richmond (SA)48410West Torrens41466Torrensville5031503140046West Torrens401Adelaide
13301521690823138.610748976-34.7434727394429150016003104000000000002019402041048Salisbury North47140Salisbury40196Burton (SA)5110511040038Ramsay409Spence
13314021697661138.621900805-34.68140867944341001120164151600300000000011402021035Virginia - Waterloo Corner45680Playford41133Penfield5121512140042Taylor409Spence
13288631676433138.601905497-34.87366147739291001110117143010120000101112401061021Prospect46510Prospect41220Prospect (SA)5082508240013Enfield401Adelaide
13257791667717138.57130707-34.9531952463725120114013013000300000000012404031107Plympton48410West Torrens40728Kurralta Park5037503740002Badcoe401Adelaide
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/sa-road-crash-locations/latest/data.json
{
  "unique_loc": "06672192063094",
  "longitude": 131.49268236900002,
  "latitude": -31.38073715799993,
  "total_crashes": 1,
  "cse_pdo": 1,
  "cse_inj": 0,
  "cse_fat": 0,
  "cse_si": 0,
  "total_casualties": 0,
  "total_fatalities": 0,
  "total_serious_injuries": 0,
  "cty_rear_end": 0,
  "cty_hit_fixed_object": 1,
  "cty_side_swipe": 0,
  "cty_right_angle": 0,
  "cty_head_on": 0,
  "cty_hit_pedestrian": 0,
  "cty_roll_over": 0,
  "cty_right_turn": 0,
  "cty_hit_parked_vehile": 0,
  "cty_hit_animal": 0,
  "cty_hit_object_on_road": 0,
  "cty_left_road_oc": 0,
  "cty_other": 0,
  "cty_unknown": 0,
  "uty_bicycle": 0,
  "uty_pedestrian": 0,
  "lco_night": 0,
  "sa2_2021_code": "406011134",
  "sa2_2021_name": "West Coast (SA)",
  "lga_2025_code": "49399",
  "lga_2025_name": "Unincorporated SA",
  "sal_2021_code": "41669",
  "sal_2021_name": "Yalata",
  "poa_2021_code": "5690",
  "poa_2021_name": "5690",
  "sed_2025_code": "40015",
  "sed_2025_name": "Flinders",
  "ced_2025_code": "404",
  "ced_2025_name": "Grey"
}

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

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.

versions.json · changes.json · history.tar.zst (1.4 MB, every version's Parquet and manifest)

Questions

How do I download Road crash locations as a CSV file?

Open https://publicdata.au/d/sa-road-crash-locations/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/sa-road-crash-locations/v/2025-09-19/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 Road crash locations in Excel?

Yes. https://publicdata.au/d/sa-road-crash-locations/v/2025-09-19/data.xlsx is a workbook with the 43,522 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/sa-road-crash-locations/v/2025-09-19/data.csv.gz is the CSV at about a tenth of the size.

What years does Road crash locations cover?

The current version covers the years since 2020. Each release from Infrastructure and Transport becomes a new dated version here, and earlier versions stay online.

How often is Road crash locations updated?

Infrastructure and Transport releases it yearly. This site checks the portal every week and adds a dated version when the file changes.

Can I use Road crash 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 Road crash locations?

No. The publisher is Department for Infrastructure and Transport, and its page is https://data.sa.gov.au/data/dataset/road-crashes-in-sa. National Digital converted the publisher's file to other formats. It renamed and typed the columns and kept only those the schema lists. It added place columns from ABS boundary layers, which the schema marks as joined. National Digital made these changes, and the publisher is not responsible for them. The original sits beside every version as source.zip with its SHA-256, so the two can be compared.

What coordinate system does Road crash locations use?

Coordinates are longitude and latitude in GDA2020 (EPSG:7844), from the publisher's GDA2020 file. The GeoJSON file uses the same coordinates, which is what GeoJSON expects.

Which SA2, council area, suburb, postcode, state electorate and federal electorate is each row of Road crash locations in?

Each row with coordinates carries the SA2 (2021), Council area (LGA 2025), Suburb or locality (2021), Postcode (postal area 2021), State electorate (2025) and Federal electorate (2025) its point falls in, with the code of each. This site joins them by location against the ABS boundaries, https://publicdata.au/d/abs-sa2-2021/, https://publicdata.au/d/abs-lga-2025/, https://publicdata.au/d/abs-suburbs-localities-2021/, https://publicdata.au/d/abs-postal-areas-2021/, https://publicdata.au/d/abs-state-electoral-divisions-2025/, https://publicdata.au/d/abs-federal-electoral-divisions-2025/, and Infrastructure and Transport did not publish them. The schema marks each one as joined and names the boundary version. A row without coordinates, or a point outside every area, has them blank. Place columns from Australian Statistical Geography Standard (ASGS) Edition 3 boundaries, Australian Bureau of Statistics, licensed under CC BY 4.0.

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.zip so the change can be checked.

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.

Department for Infrastructure and Transport, Government of South Australia, Road Crash Locations in SA, https://data.sa.gov.au/data/dataset/road-crashes-in-sa, accessed 29 September 2026, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/sa-road-crash-locations/v/2025-09-19/

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

Department for Infrastructure and Transport states the licence, CC BY 4.0, on its own page, which was read and recorded here on 1 October 2026.

Place columns from Australian Statistical Geography Standard (ASGS) Edition 3 boundaries, Australian Bureau of Statistics, licensed under CC BY 4.0.

Every fetch reads the licence again and stops when it has changed. The fetch that made version 2025-09-19 read it on 29 September 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/sa-road-crash-locations")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23076655

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

Department for Infrastructure and Transport publishes this table on data.sa.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 29 September 2026. Source SHA-256 b78b3d9e8fb19be2…

Improve this dataset

This page is built from register/sa-road-crash-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