CFA incident responses, Victoria, 2009-10 to 2021-22
liveCFA incident responses, one row per incident from 1 July 2009 to 30 June 2022, read from the workbook's sheet for each financial year. Each row has the date and time the incident was reported, CFA's incident number, the CFA district and the incident type code and description. The incidents cover fires, rescues, hazardous material calls, alarms and assistance to other agencies across the CFA area.
Also called: CFA incident data, Country Fire Authority incident responses, CFA callouts by incident type, Victorian fire brigade incidents.
- What does each row hold?
- One incident CFA brigades responded to, with the date and time it was reported, CFA's incident number, the CFA district number and the incident type as a code and as words. The workbook holds one sheet per financial year from 2009-10 to 2021-22, and the financial year is kept from the sheet name.
- Why do some rows have no district or incident type?
- The publisher leaves the district blank or writes NULL where none was recorded, and some incidents have no type recorded. Both are kept as null.
- What do the incident type codes mean?
- They are the codes of the Australasian Incident Reporting System. Each row also carries the type in words as CFA wrote it, so the codes can be read without a separate list.
Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 6 fields, count and filter across all 529,351 rows and diff its versions. Every answer names the version and carries CFA's attribution. No key.
Then ask it: What does CFA incident responses, Victoria, 2009-10 to 2021-22 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=incident_type&metric=count&financial_year=eq.2021-22
Incidents by incident type where financial year is 2021-22: 8,691 Mutual Aid Given - FRV, 1,785 Vehicle accident-no injuries, 1,541 Vehicle accident-with injuries, 1,403 Controlled burning.
Download it as Excel, CSV, JSON and 6 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/vic-cfa-incident-responses/latest/ redirects to the newest version.
https://publicdata.au/d/vic-cfa-incident-responses/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/vic-cfa-incident-responses/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("vic-cfa-incident-responses")
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("vic-cfa-incident-responses")
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/vic-cfa-incident-responses/v/2026-10-03/data.duckdb' AS vic_cfa_incident_responses (READ_ONLY);
SELECT financial_year, count(*) FROM vic_cfa_incident_responses.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/vic-cfa-incident-responses/aggregate?group=incident_type&metric=count&financial_year=eq.2021-22");
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 |
|---|---|---|---|
| financial_year | string | (sheet) | The financial year of the workbook sheet the row is on, such as 2021-22. |
| incident_datetime | datetime | (row header 1) | The date and time of the incident, local time, as recorded by CFA. |
| incident_no | integer | (cell: incident_no) | |
| district_no | integer | (cell: District_no) | The CFA district number. Null where none was recorded. |
| incident_type_code | string | (cell: incident_type_code) | The incident type code, kept as text because codes such as 352.1 carry a decimal part. |
| incident_type | string | (cell: incident_type) |
Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is incident_no, financial_year.
A sample of 10 rows
From the latest version, newest first by reported at, each financial year in turn, then in the publisher's order, with every field. A blank cell is shown as null.
| financial_year | incident_datetime | incident_no | district_no | incident_type_code | incident_type |
|---|---|---|---|---|---|
| 2021-22 | 2022-06-30T22:53:29 | 848058 | 14 | 352 | Vehicle accident-no injuries |
| 2020-21 | 2021-06-30T21:42:46 | 814390 | 14 | 523.53 | Mutual Aid Given - FRV |
| 2019-20 | 2020-06-30T23:30:12 | 781316 | 8 | 412 | Odour or gas, gas leak, (domestic or LPG) |
| 2018-19 | 2019-06-30T23:23:07 | 734347 | 7 | 600 | Good intent call; insuff info to classify |
| 2017-18 | 2018-06-30T23:32:04 | 686152 | 8 | 622 | Steam vapour, fog or dust thought to be smoke |
| 2016-17 | 2017-06-30T23:58:44 | 639511 | 14 | 731 | Sprinkler malfunction - monitored by fire service |
| 2015-16 | 2016-06-30T23:15:45 | 596247 | 14 | 151 | Passenger vehicle fire including buses |
| 2014-15 | 2015-06-30T23:57:35 | 552524 | 7 | 751 | Smoke detector operated-no fire-smoke from other location |
| 2013-14 | 2014-06-30T23:43:37 | 509821 | 8 | 921 | Dispatched and cancelled en-route |
| 2012-13 | 2013-06-30T23:38:30 | 467788 | 8 | 352.1 | Vehicle accident-with injuries |
The first row as JSON
As it appears in data.json.
GET https://publicdata.au/d/vic-cfa-incident-responses/latest/data.json
{
"financial_year": "2021-22",
"incident_datetime": "2021-07-01T00:17:03",
"incident_no": 814394,
"district_no": 18,
"incident_type_code": "152",
"incident_type": "Road or transport vehicle fire"
}
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. Each file carries the same provenance header.
By financial_year (13 files)
by/financial_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-10-03 529,351 rows6 fieldsxlsxda15e636c66bThe publisher's server states no change date, so this version is dated by the fetch.
versions.json · changes.json · history.tar.zst (4.4 MB, every version's Parquet and manifest)
Questions
How do I download CFA incident responses, Victoria as a CSV file?
Open https://publicdata.au/d/vic-cfa-incident-responses/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/vic-cfa-incident-responses/v/2026-10-03/data.csv today. The same path serves Excel, JSON, Parquet, SQLite, DuckDB, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.
Can I open CFA incident responses, Victoria in Excel?
Yes. https://publicdata.au/d/vic-cfa-incident-responses/v/2026-10-03/data.xlsx is a workbook with the 529,351 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/vic-cfa-incident-responses/v/2026-10-03/data.csv.gz is the CSV at about a tenth of the size.
What years does CFA incident responses, Victoria cover?
The current version covers 2009 to 2021. Each release from CFA becomes a new dated version here, and earlier versions stay online.
How often is CFA incident responses, Victoria updated?
CFA no longer updates it. This site checks the portal every week and adds a dated version when the file changes.
Can I use CFA incident responses, Victoria 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 CFA incident responses, Victoria?
No. The publisher is Country Fire Authority, and its page is https://discover.data.vic.gov.au/dataset/cfa-incident-responses. This site republishes the publisher's file without changing its content. The original sits beside every version as source.xlsx with its SHA-256, so the two can be compared.
How do I get only the rows for one financial year?
Every version has one JSON file per value of financial_year, 13 files in the current version, listed with row counts at https://publicdata.au/d/vic-cfa-incident-responses/v/2026-10-03/by/financial_year/index.json. For example https://publicdata.au/d/vic-cfa-incident-responses/v/2026-10-03/by/financial_year/2018-19.json holds the 47,803 rows where financial_year is 2018-19.
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.xlsx so the change can be checked.