Bushfire and prescribed burn history, South Australia
liveState-wide fire scar mapping from the Department for Environment and Water. Each row is one area burnt by a bushfire or by a prescribed burn on land managed by state agencies, with the incident name and number, the date, financial year, calendar year and season of the fire, the area in hectares, comments, and the publisher's codes for date reliability, imagery, feature source and capture method.
The publisher notes that a landscape approach is used, so the mapping may be incomplete for a given reserve or region, and that burn-offs on private land are excluded.
Also called: SA fire history, Bushfires and Prescribed Burns History, South Australian fire scar mapping, DEW fire history shapefile.
- What is in each row?
- One mapped fire scar, the area burnt by a bushfire or a prescribed burn, with its incident name and number, the fire date, financial year, calendar year and season, the area in hectares, and the publisher's codes for how reliable the date is and how the shape was captured. The shape itself is in the GeoParquet, GeoJSON, GeoPackage and PMTiles files.
- Does it cover every fire in South Australia?
- No. The Department maps major bushfires across the state and prescribed burns on land managed by state agencies. It says the mapping may be incomplete for a given reserve or region, and burn-offs on private land are left out.
- Why is the incident number 0 in some rows?
- The publisher writes 0 where a fire has no incident number on record. Every fire before 2000 has 0, and so do about two in three bushfires since then. Most prescribed burns since 2000 carry a number. The value is kept as published.
Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 14 fields, count and filter across all 6,968 rows and diff its versions. Every answer names the version and carries Environment and Water's attribution. No key.
Then ask it: What does Bushfire and prescribed burn history, South Australia 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=season&metric=count&incident_type=eq.Bushfire
Fire scars by season where fire type is Bushfire: 3,985 SUMMER, 766 SPRING, 476 AUTUMN, 125 WINTER.
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/sa-fire-history/latest/ redirects to the newest version.
https://publicdata.au/d/sa-fire-history/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/sa-fire-history/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("sa-fire-history")
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("sa-fire-history")
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/sa-fire-history/v/2026-07-10/data.duckdb' AS sa_fire_history (READ_ONLY);
SELECT incident_number, count(*) FROM sa_fire_history.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/sa-fire-history/aggregate?group=season&metric=count&incident_type=eq.Bushfire");
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 |
|---|---|---|---|
| incident_number | integer | INCIDENTNU | The publisher's incident number, or 0 where none is on record. |
| incident_name | string | INCIDENTNA | |
| incident_type | string | INCIDENTTY | Bushfire or Prescribed Burn. |
| fire_date | date | FIREDATE | |
| financial_year | string | FINANCIALY | |
| fire_year | integer | FIREYEAR | |
| season | string | SEASON | |
| date_reliability | integer | DATERELIAB | The publisher's code for how reliable the fire date is. |
| image_information | string | IMAGEINFOR | The satellite or aerial imagery the scar was mapped from, as the publisher wrote it. |
| feature_source | integer | FEATURESOU | |
| capture_method | integer | CAPTUREMET | |
| capture_source | integer | CAPTURESOU | |
| comments | string | COMMENTS | |
| hectares | number | HECTARES |
Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json.
A sample of 10 rows
From the latest version, newest first by year, then in the publisher's order, with every field. A blank cell is shown as null.
| incident_number | incident_name | incident_type | fire_date | financial_year | fire_year | season | date_reliability | image_information | feature_source | capture_method | capture_source | comments | hectares |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1146 | Finniss (Heysen Trail) | Prescribed Burn | 2026-05-11 | 2025/2026 | 2026 | AUTUMN | 1 | null | 15 | 14 | 4 | Ecological burn - OPS_PLAN_ID=2189; PLAN_NAME=Ops Plan 3 | 1.11562833 |
| 202602022 | Deep Creek | Bushfire | 2026-02-01 | 2025/2026 | 2026 | SUMMER | 1 | Sentinel 2 14th February 2026 | 10 | 1 | 4 | CRIIMSON Incident Number 1687074 | 4311.58692473 |
| 0 | Canunda | Bushfire | 2026-02-05 | 2025/2026 | 2026 | SUMMER | 1 | null | 15 | 14 | 4 | CRIIMSON incident Number 1687807 | 1.47268656 |
| 0 | Magarey | Bushfire | 2026-01-31 | 2025/2026 | 2026 | SUMMER | 1 | null | 15 | 14 | 4 | CRIIMSON Incident Number 1686806 | 4.08291759 |
| 0 | Salisbury Heights | Bushfire | 2026-01-21 | 2025/2026 | 2026 | SUMMER | 1 | null | 15 | 14 | 4 | CRIIMSON Incident Number 1683266 | 0.77828643 |
| 1108 | Bandon North | Prescribed Burn | 2026-04-16 | 2025/2026 | 2026 | AUTUMN | 1 | null | 15 | 14 | 34 | Ecological Burn - OPS_PLAN_ID=1886; PLAN_NAME=Ops Plan 1 | 73.62141686 |
| 1032 | Belair (Ballast Pit Track) | Prescribed Burn | 2026-04-29 | 2025/2026 | 2026 | AUTUMN | 1 | null | 1 | 12 | 4 | OPS_PLAN_ID=1705; PLAN_NAME=Ops Plan 2 | 7.32812033 |
| 202601017 | Tooperang | Bushfire | 2026-01-18 | 2025/2026 | 2026 | SUMMER | 1 | Sentinel 2 20th Jan 2026 | 10 | 1 | 4 | CRIIMSON Incident number 1682678 | 642.90092401 |
| 1078 | Mark Oliphant (Evans Drive East) | Prescribed Burn | 2026-04-28 | 2025/2026 | 2026 | AUTUMN | 1 | null | 1 | 12 | 4 | OPS_PLAN_ID=1782; PLAN_NAME=Ops Plan 1 | 8.72178476 |
| 0 | Saddleworth | Bushfire | 2026-02-09 | 2025/2026 | 2026 | SUMMER | 1 | null | 1 | 12 | 4 | CRIIMSON Incident Number 1688494 | 7.40339534 |
The first row as JSON
As it appears in data.json.
GET https://publicdata.au/d/sa-fire-history/latest/data.json
{
"incident_number": 0,
"incident_name": "NW12",
"incident_type": "Prescribed Burn",
"fire_date": "2014-06-30",
"financial_year": "2013/2014",
"fire_year": 2014,
"season": "WINTER",
"date_reliability": 4,
"image_information": null,
"feature_source": 0,
"capture_method": 0,
"capture_source": 23,
"comments": null,
"hectares": 61.14989926
}
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.
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-07-10 6,968 rows14 fieldszip77ac00fe1b69
versions.json · changes.json · history.tar.zst (60 MB, every version's Parquet and manifest)
Questions
How do I download Bushfire and prescribed burn history as a CSV file?
Open https://publicdata.au/d/sa-fire-history/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/sa-fire-history/v/2026-07-10/data.csv today. The same path serves Excel, JSON, GeoJSON, Parquet, SQLite, DuckDB, GeoPackage, PMTiles, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.
Can I open Bushfire and prescribed burn history in Excel?
Yes. https://publicdata.au/d/sa-fire-history/v/2026-07-10/data.xlsx is a workbook with the 6,968 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-fire-history/v/2026-07-10/data.csv.gz is the CSV at about a tenth of the size.
What years does Bushfire and prescribed burn history cover?
The current version covers 1931 to 2025. Each release from Environment and Water becomes a new dated version here, and earlier versions stay online.
How often is Bushfire and prescribed burn history updated?
Environment and Water releases it when the publisher maps new fires. This site checks the portal every week and adds a dated version when the file changes.
Can I use Bushfire and prescribed burn history 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 Bushfire and prescribed burn history?
No. The publisher is Department for Environment and Water, and its page is https://data.sa.gov.au/data/dataset/fire-history. This site republishes the publisher's file without changing its content. The original sits beside every version as source.zip with its SHA-256, so the two can be compared.
What coordinate system does Bushfire and prescribed burn history use?
Shapes in GDA2020 (EPSG:7844), from the GDA2020 layer the publisher ships beside a GDA94 copy. The GeoJSON file uses GDA2020 as well, which differs from the WGS84 GeoJSON expects by well under a metre.
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.