2003 Canberra bushfire burn area and property damage
liveThe ACT Government's spatial record of the January 2003 bushfires, from the Office of the Surveyor-General. It holds the total burn area and the parcels affected, each with a description of its status (uninhabitable, property redevelopment, habitable primary dwelling damage or habitable outbuilding damage). The shapes are served as GeoParquet, GeoJSON, a GeoPackage and map tiles.
Also called: 2003 Bushfire Data ACT, Canberra fires January 2003 damage map, 2003 Canberra firestorm property damage.
- What is in each row?
- One shape with the publisher's description of it. One shape is the total burn area of the January 2003 fires in the ACT, and the others are land parcels marked as uninhabitable, for property redevelopment, or with damage to a primary dwelling or a habitable outbuilding.
- Will it change?
- The publisher marks the data as never updated. It is the record of one event.
- Where is the publisher's file?
- The portal serves the layer as a table with each shape as text. This site reads the portal's GeoJSON export of the same rows, ordered by the portal's row identifier, and keeps that file as the source of every version.
Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 1 fields, count and filter across all 988 rows and diff its versions. Every answer names the version and carries ACT Surveyor-General's attribution. No key.
Then ask it: What does 2003 Canberra bushfire burn area and property damage 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.
A dashboard over every row. Click to filter, add panels, share a link or embed a frame.
Query APIFilter and count from a URLaggregate?group=poly_desc&metric=count
Areas by status: 444 uninhabitable, 413 property redevelopment, 65 habitable primary dwelling damage, 65 habitable outbuilding damage.
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/act-2003-bushfire/latest/ redirects to the newest version.
https://publicdata.au/d/act-2003-bushfire/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/act-2003-bushfire/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("act-2003-bushfire")
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("act-2003-bushfire")
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/act-2003-bushfire/v/2016-01-22/data.duckdb' AS act_2003_bushfire (READ_ONLY);
SELECT poly_desc, count(*) FROM act_2003_bushfire.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/act-2003-bushfire/aggregate?group=poly_desc&metric=count");
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. Shapes were moved to GDA2020 and the one attribute was kept as published. Rows were left alone.
| Field | Type | Publisher's header | Note |
|---|---|---|---|
| poly_desc | string | poly_desc | The total burn area, or the status of an affected parcel as the publisher describes it. |
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, each status in turn, then in the publisher's order, with every field. A blank cell is shown as null.
| poly_desc |
|---|
| property redevelopment |
| total burn area |
| habitable outbuilding damage |
| habitable primary dwelling damage |
| uninhabitable |
| property redevelopment |
| habitable outbuilding damage |
| habitable primary dwelling damage |
| uninhabitable |
| property redevelopment |
The first row as JSON
As it appears in data.json.
GET https://publicdata.au/d/act-2003-bushfire/latest/data.json
{
"poly_desc": "property redevelopment"
}
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.
- 2016-01-22 988 rows1 fieldsutf-8-sigd84ab8002434
versions.json · changes.json · history.tar.zst (152 KB, every version's Parquet and manifest)
Questions
How do I download 2003 Canberra bushfire burn area and property damage as a CSV file?
Open https://publicdata.au/d/act-2003-bushfire/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/act-2003-bushfire/v/2016-01-22/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 2003 Canberra bushfire burn area and property damage in Excel?
Yes. https://publicdata.au/d/act-2003-bushfire/v/2016-01-22/data.xlsx is a workbook with the 988 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-2003-bushfire/v/2016-01-22/data.csv.gz is the CSV at about a tenth of the size.
What years does 2003 Canberra bushfire burn area and property damage cover?
The current version covers the years since 2003. Each release from ACT Surveyor-General becomes a new dated version here, and earlier versions stay online.
How often is 2003 Canberra bushfire burn area and property damage updated?
ACT Surveyor-General no longer updates it. This site checks the portal every week and adds a dated version when the file changes.
Can I use 2003 Canberra bushfire burn area and property damage 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 2003 Canberra bushfire burn area and property damage?
No. The publisher is Office of the Surveyor-General, ACT Government, and its page is https://www.data.act.gov.au/d/sksx-b49e. This site republishes the publisher's file without changing its content. The original sits beside every version as source.geojson with its SHA-256, so the two can be compared.
What coordinate system does 2003 Canberra bushfire burn area and property damage use?
The portal's GeoJSON export is in WGS84 longitude and latitude; the shapes are moved to GDA2020, which differs by under 2 metres. 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.geojson so the change can be checked.