Road crashes, Tasmania
liveOne row per crash on a Tasmanian road, from the Crash Data Management database Tasmania Police uses. The publisher names the layer for crashes since 1 January 2009 and it also holds crashes back to January 1998. Each row carries the crash number, date and time, the crash movement description, severity, whether police attended, the road surface, light condition, centre line marking, speed zone, a location description and the point coordinates.
Also called: Tasmanian Vehicle Crash Data, Tasmanian Crash Data (CDM), Tasmania car accident data, State Growth crash statistics.
- Where is the publisher's file?
- There is none. The publisher serves the crashes as an ArcGIS feature layer with no download. This site reads every feature of the layer in pages, in the order of the layer's own identifier, and keeps them as one GeoJSON file, which is the source file beside every version.
- Does it include every crash?
- The publisher includes crashes reported by Tasmania Police, and property damage only crashes reported by the public. A crash nobody reported is not here.
- How often is it updated?
- The layer changes as the police crash database changes. This site checks it weekly and adds a dated version when the features change.
- Why are there crashes before 2009?
- The publisher names the layer for crashes since 1 January 2009, and it also holds 56,136 crashes dated from January 1998 to December 2008 in the September 2026 version. They are kept as published.

Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 25 fields, count and filter across all 177,080 rows and diff its versions. Every answer names the version and carries State Growth's attribution. No key.
Then ask it: What does Road crashes, Tasmania 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=light_condition&metric=count&severity=eq.Fatal
Crashes by light condition where severity is Fatal: 560 Daylight, 217 Darkness (without street light), 103 Darkness (with street light), 51 Dawn / Dusk.
Download it as CSV, Parquet, SQLite and 5 more formats
Pick a format and a version. CSV is picked first because it opens in the tools most offices have. The URL is yours to keep. A dated version keeps its content.
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.
A GeoPackage with one point layer, records, in the publisher's coordinate system, plus the fields and publicdata tables. Drag it into QGIS or ArcGIS.
GeoParquet: the Parquet table with a WKB geometry column and its coordinate system in the file's geo metadata. Reads directly in DuckDB, GeoPandas, QGIS and GDAL.
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 severity, 6 files. The example is by/severity/property-damage-only.json. Every file carries the same header and a partition note.
Excel is not offered because the table is 61.7 MB as CSV, over the 50 MB limit for Excel. JSON is not offered because the table is 127.1 MB as NDJSON, over the 50 MB limit for JSON. GeoJSON is not offered because the file would be 147.4 MB, over the 100 MB limit for GeoJSON.
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/tas-road-crashes/latest/ redirects to the newest version.
https://publicdata.au/d/tas-road-crashes/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/tas-road-crashes/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("tas-road-crashes")
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("tas-road-crashes")
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/tas-road-crashes/v/2026-11-17/data.duckdb' AS tas_road_crashes (READ_ONLY);
SELECT severity, count(*) FROM tas_road_crashes.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/tas-road-crashes/aggregate?group=light_condition&metric=count&severity=eq.Fatal");
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 point geometry became longitude and latitude fields. Rows were left alone.
| Field | Type | Publisher's header | Note |
|---|---|---|---|
| id | integer | ID | The feature layer's object id. |
| vcrn | string | VCRN | The police crash report number. Kept as text. |
| description | string | DESCRIPTION | The DCA (Definitions for Coding Accidents) code and its description. |
| crash_date_time | datetime | CRASH_DATE_TIME | UTC, from the layer's date field. |
| severity | string | SEVERITY | |
| visited | string | VISITED | |
| surface_type | string | SURFACE_TYPE | |
| light_condition | string | LIGHT_CONDITION | |
| centre_line | string | CENTRE_LINE | |
| speed_zone | string | SPEED_ZONE | Kept as text to preserve leading zeros, for example 060. |
| location_description | string | LOCATION_DESCRIPTION | |
| longitude | number | (longitude) | Decimal degrees, WGS84, from the point geometry. |
| latitude | number | (latitude) | Decimal degrees, WGS84, from the point geometry. |
| sa2_2021_code | string | (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_name | string | (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_code | string | (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_name | string | (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_code | string | (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_name | string | (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_code | string | (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_name | string | (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_code | string | (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_name | string | (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_code | string | (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_name | string | (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 id.
A sample of 10 rows
From the latest version, newest first by date and time, each severity in turn, then in the publisher's order, with every field. A blank cell is shown as null.
| id | vcrn | description | crash_date_time | severity | visited | surface_type | light_condition | centre_line | speed_zone | location_description | longitude | latitude | sa2_2021_code | sa2_2021_name | lga_2025_code | lga_2025_name | sal_2021_code | sal_2021_name | poa_2021_code | poa_2021_name | sed_2025_code | sed_2025_name | ced_2025_code | ced_2025_name |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 53229540 | 26007525 | - | 2026-11-16T16:04:00 | Minor | Yes | Sealed | Darkness (without street light) | Single broken | 100 | Batman Highway, Sidmouth, West Tamar | 146.878838715 | -41.2282690619 | 602021055 | Grindelwald - Lanena | 65810 | West Tamar | 60601 | Sidmouth | 7270 | 7270 | 60113 | Bass (Rosevears) | 601 | Bass |
| 53228110 | 26007518 | - | 2026-11-16T01:00:00 | Property Damage Only | Yes | Sealed | Daylight | None | 080 | Bungana WayKennedy Drive, Cambridge, Clarence | 147.464875227 | -42.8313156107 | 601021005 | Cambridge | 61410 | Clarence | 60090 | Cambridge (Tas.) | 7170 | 7170 | 60414 | Franklin (Rumney) | 604 | Franklin |
| 53228164 | 26007522 | - | 2026-11-15T16:50:00 | Not known | No | Sealed | Daylight | Single broken | 050 | Amy Road, Newstead, Launceston | 147.163732518 | -41.4491287958 | 602011042 | Newstead | 64010 | Launceston | 60453 | Newstead (Tas.) | 7250 | 7250 | 60105 | Bass (Launceston) | 601 | Bass |
| 53225985 | 26007477 | - | 2026-11-13T21:44:00 | First Aid | Yes | Sealed | Daylight | Single broken | 110 | Tasman Highway, Warrane, Clarence | 147.374783516 | -42.8582624096 | 601021009 | Mornington - Warrane | 61410 | Clarence | 60718 | Warrane | 7018 | 7018 | 60411 | Franklin (Pembroke) | 604 | Franklin |
| 53225860 | 26007472 | - | 2026-11-12T16:52:00 | Serious | Yes | Sealed | Daylight | Double continuous | 100 | Tasman Highway, Nunamara, Launceston | 147.304470634 | -41.3877097727 | 602031058 | Dilston - Lilydale | 64010 | Launceston | 60470 | Nunamara | 7259 | 7259 | 60115 | Bass (Windermere) | 601 | Bass |
| 53220444 | 26007313 | 120 - Wrong side/other head on (not overtaking) | 2026-11-04T19:36:00 | Fatal | Yes | Sealed | Daylight | Double continuous | 080 | Bass Highway, Somerset, Waratah-Wynyard | 145.805848541 | -41.0282916298 | 604011081 | Somerset | 65410 | Waratah-Wynyard | 60608 | Somerset (Tas.) | 7322 | 7322 | 60209 | Braddon (Murchison) | 602 | Braddon |
| 53227887 | 26007512 | - | 2026-11-15T22:40:00 | Minor | Yes | Sealed | Daylight | Double continuous | 080 | Brooker Highway, Derwent Park, Glenorchy | 147.297525135 | -42.8333107654 | 601031016 | Derwent Park - Lutana | 62610 | Glenorchy | 60152 | Derwent Park | 7009 | 7009 | 60302 | Clark (Elwick) | 603 | Clark |
| 53229501 | 26007524 | - | 2026-11-15T21:10:00 | Property Damage Only | Yes | Sealed | Daylight | Single broken | 040 | Campbell Street, Hobart, Hobart | 147.3274459 | -42.8773075181 | 601051027 | Hobart | 62810 | Hobart | 60276 | Hobart | 7000 | 7000 | 60303 | Clark (Hobart) | 603 | Clark |
| 53225947 | 26007473 | - | 2026-11-12T20:20:00 | First Aid | Yes | Sealed | Daylight | Single Continuous | 050 | Intersection of Cole Street and Gordon Street and Cole Street, Sorell, Sorell | 147.562637038 | -42.7814475951 | 601061035 | Sorell - Richmond | 64810 | Sorell | 60609 | Sorell | 7172 | 7172 | 60512 | Lyons (Prosser) | 605 | Lyons |
| 53224964 | 26007452 | - | 2026-11-11T19:20:00 | Serious | Yes | Sealed | Daylight | Single broken | 110 | Bass Highway, Elizabeth Town, Meander Valley | 146.564928296 | -41.4720301509 | 602021054 | Deloraine | 64210 | Meander Valley | 60186 | Elizabeth Town | 7304 | 7304 | 60506 | Lyons (McIntyre) | 605 | Lyons |
The first row as JSON
As it appears in data.ndjson.
GET https://publicdata.au/d/tas-road-crashes/latest/data.ndjson
{
"id": 1652,
"vcrn": "13000032",
"description": "136 - Vehicles in parallel lane/ right turn side swipe",
"crash_date_time": "2013-03-30T00:16:00",
"severity": "Property Damage Only",
"visited": "Yes",
"surface_type": "Sealed",
"light_condition": "Daylight",
"centre_line": "Single Continuous",
"speed_zone": "060",
"location_description": "Intersection of Brooker Avenue, Hobart, Hobart",
"longitude": 147.3307030815645,
"latitude": -42.878281459848566,
"sa2_2021_code": "601051027",
"sa2_2021_name": "Hobart",
"lga_2025_code": "62810",
"lga_2025_name": "Hobart",
"sal_2021_code": "60276",
"sal_2021_name": "Hobart",
"poa_2021_code": "7000",
"poa_2021_name": "7000",
"sed_2025_code": "60303",
"sed_2025_name": "Clark (Hobart)",
"ced_2025_code": "603",
"ced_2025_name": "Clark"
}
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 with a GeoJSON beside it. Each file carries the same provenance header.
By severity (6 files)
by/severity/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-17 177,080 rows+130 added −1 removed 107 changed25 fieldsutf-8408672c9a98c
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-11-09 176,951 rows+152 added −4 removed 81 changed25 fieldsutf-85a89a32bfe00
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-11-02 176,803 rows+138 added −1 removed 87 changed25 fieldsutf-83d462f126913
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-10-27 176,666 rows+144 added −0 removed 101 changed25 fieldsutf-89fc7c45be25b
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-10-20 176,522 rows+129 added −3 removed 134 changed25 fieldsutf-8c30cd8d7c6c6
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-10-13 176,396 rows+155 added −2 removed 71 changed25 fieldsutf-894928289606b
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-10-05 176,243 rows+22 added −0 removed 12 changed25 fieldsutf-8bbf7791732de
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-10-04 176,221 rows+18 added −0 removed 7 changed25 fieldsutf-86124d5a4dbba
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-10-03 176,203 rows+46 added −0 removed 39 changed25 fieldsutf-8b9524641c0a7
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-10-01 176,157 rows+8 added −0 removed 1 changed25 fieldsutf-8854c7df5ba96
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher's file changed on 2026-09-30, which an earlier version already carries, so this version is dated 2026-10-01.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-09-30 176,149 rows+18 added −2 removed 29 changed25 fieldsutf-8f1f3d528b711
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
- 2026-09-29 176,133 rows25 fieldsutf-85d4f0e21680d
The layer states no edit date, so this version is dated by the newest record it holds.
The publisher offers no file. These bytes are every feature of the layer as the service returned them in WGS84, ordered by its object id, so the same layer gives the same bytes.
versions.json · changes.json · history.tar.zst (70 MB, every version's Parquet and manifest)
Questions
How do I download Road crashes as a CSV file?
Open https://publicdata.au/d/tas-road-crashes/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/tas-road-crashes/v/2026-11-17/data.csv today. The same path serves Parquet, SQLite, DuckDB, GeoPackage, GeoParquet, NDJSON. A dated URL never changes, so use it when the file must stay the same.
Can I open Road crashes in Excel?
Not as a workbook. Excel is not offered because the table is 61.7 MB as CSV, over the 50 MB limit for Excel. Load the CSV or the Parquet file with Power Query, or take one partition file at a time. https://publicdata.au/d/tas-road-crashes/v/2026-11-17/data.csv.gz is the CSV at about a tenth of the size.
What years does Road crashes cover?
The current version covers 1998 to 2025. Each release from State Growth becomes a new dated version here, and earlier versions stay online.
How often is Road crashes updated?
State Growth releases it as the police database changes. This site checks the portal every week and adds a dated version when the file changes.
Can I use Road crashes 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 crashes?
No. The publisher is Department of State Growth, and its page is https://data.gov.au/data/dataset/tasmanian. 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.geojson with its SHA-256, so the two can be compared.
How do I get only the rows for one severity?
Every version has one JSON file per value of severity, 6 files in the current version, listed with row counts at https://publicdata.au/d/tas-road-crashes/v/2026-11-17/by/severity/index.json. For example https://publicdata.au/d/tas-road-crashes/v/2026-11-17/by/severity/property-damage-only.json holds the 122,192 rows where severity is Property Damage Only. A GeoJSON file sits beside each one.
What coordinate system does Road crashes use?
Longitude and latitude in WGS84 (EPSG:4326), as the feature service projects them on request. The layer's own coordinates are Web Mercator. 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 crashes 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 State Growth 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.geojson so the change can be checked.
The licence requires the publisher's attribution. We ask that you also name publicdata.au and link to the version you used.
Department of State Growth, Tasmanian Government, Tasmanian Vehicle Crash Data, https://data.gov.au/data/dataset/tasmanian, accessed 16 November 2026, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/tas-road-crashes/v/2026-11-17/
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.
Department of State Growth states the licence, CC BY 4.0, on its own page, which was read and recorded here on 30 September 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 2026-11-17 read it from data.gov.au on 16 November 2026.
- Hugging Faceload_dataset("National-Digital/tas-road-crashes")
- Kagglewith a starter notebook
- ZenodoDOI 10.5281/zenodo.23076693
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.
Department of State Growth publishes this table on data.stategrowth.tas.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.
Fetched 16 November 2026. Source SHA-256 408672c9a98c6c49…
This page is built from register/tas-road-crashes.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