One polygon of mapped flood extent, with the feature type, the location name, the source the outline was drawn from and the reliability dates the department records for the shape and its attributes.

Is this the peak of the flood?

Not always. The department describes the polygons as the approximate inundation when the source imagery or survey was captured, and recommends them for use at about 1:5,000 to 1:10,000.

Can I use it to tell whether a property will flood?

No. It shows one past flood. Councils publish flood planning maps for present risk.

Datasets / Queensland / Natural Resources and Mines / Historical flood extents, Queensland

Bundaberg flood extent, January 2013

Name: Bundaberg flood extent, January 2013
Creator: Department of Natural Resources and Mines, Manufacturing and Regional and Rural Development
Published: 2013-01-29
License: https://creativecommons.org/licenses/by/4.0/

live

Publisher Department of Natural Resources and Mines, Manufacturing and Regional and Rural DevelopmentUpdated no longerLicence CC BY 4.0Latest 2013-01-29Rows 25Fields 7

The 2013 Floodline Bundaberg layer of the Queensland Flood extent series, one row per polygon of mapped inundation for the January 2013 Bundaberg flood that followed ex-tropical cyclone Oswald, drawn from aerial imagery. Each row has the feature type, location, source and the reliability dates for the feature and its attributes. The polygons are read from the state's map service in WGS84 and published in GDA2020.

Also called: Bundaberg 2013 flood map, Bundaberg flood extent, January 2013 polygons, 2013 Floodline Bundaberg layer.

Part of Historical flood extents, Queensland, 8 tables the publisher releases together: Bundaberg flood extent, 2010, Queensland towns flood extent, January 2011, Queensland towns flood extent, April 2011, South west Queensland towns flood extent, 2012, Fitzroy River flood extent, April 2017, Logan and Albert rivers flood extent, April 2017, Western Queensland flood extent, February 2019.

Before you use it

What is in each row?: One polygon of mapped flood extent, with the feature type, the location name, the source the outline was drawn from and the reliability dates the department records for the shape and its attributes.
Is this the peak of the flood?: Not always. The department describes the polygons as the approximate inundation when the source imagery or survey was captured, and recommends them for use at about 1:5,000 to 1:10,000.
Can I use it to tell whether a property will flood?: No. It shows one past flood. Councils publish flood planning maps for present risk.

Made for agents

Connect your AI agent

Any agent that connects to publicdata.au/mcp can find this dataset, read its 7 fields, count and filter across all 25 rows and diff its versions. Every answer names the version and carries Natural Resources and Mines's attribution. No key.

Then ask it: What does Bundaberg flood extent, January 2013 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.

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.

ExploreChart every row in your browser

A dashboard over every row. Click to filter, add panels, share a link or embed a frame.

Query APIFilter and count from a URL

aggregate?group=feature_type&metric=count

Flood polygons by feature type: 25 Floodline.

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.

Format

Version "Latest" redirects to the newest version and will change when the publisher releases again. A dated version never changes.

https://publicdata.au/d/qld-flood-extent-2013-bundaberg/latest/data.xlsx

Download

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/qld-flood-extent-2013-bundaberg/latest/ redirects to the newest version.

https://publicdata.au/d/qld-flood-extent-2013-bundaberg/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/qld-flood-extent-2013-bundaberg/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("qld-flood-extent-2013-bundaberg")
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("qld-flood-extent-2013-bundaberg")
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/qld-flood-extent-2013-bundaberg/v/2013-01-29/data.duckdb' AS qld_flood_extent_2013_bundaberg (READ_ONLY);
SELECT objectid, count(*) FROM qld_flood_extent_2013_bundaberg.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/qld-flood-extent-2013-bundaberg/aggregate?group=feature_type&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. Cells were typed and field names were made snake_case. Shapes were moved to GDA2020. Rows were left alone.

Field	Type	Publisher's header	Note
objectid	integer	objectid
feature_type	string	featuretype
location	string	location
feature_reliability	date	featurereliability	The date the department gives for the reliability of the outline, usually the capture date of its source.
feature_source	string	featuresource
attribute_reliability	date	attributereliability
attribute_source	string	attributesource

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

The first 10 rows

From the latest version, in the publisher's order, with every field. A blank cell is shown as null.

objectid	feature_type	location	feature_reliability	feature_source	attribute_reliability	attribute_source
1	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
2	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
3	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
4	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
5	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
6	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
7	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
8	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
9	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery
10	Floodline	Bundaberg	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery	2013-01-29	Orthophotography_10cm_Bundaberg Flood Imagery

The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/qld-flood-extent-2013-bundaberg/latest/data.json
{
  "objectid": 1,
  "feature_type": "Floodline",
  "location": "Bundaberg",
  "feature_reliability": "2013-01-29",
  "feature_source": "Orthophotography_10cm_Bundaberg Flood Imagery",
  "attribute_reliability": "2013-01-29",
  "attribute_source": "Orthophotography_10cm_Bundaberg Flood Imagery"
}

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

2013-01-29
25 rows7 fieldsutf-8a8172d56f608

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 (1.4 MB, every version's Parquet and manifest)

Questions

How do I download Bundaberg flood extent as a CSV file?

Open https://publicdata.au/d/qld-flood-extent-2013-bundaberg/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/qld-flood-extent-2013-bundaberg/v/2013-01-29/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 Bundaberg flood extent in Excel?

Yes. https://publicdata.au/d/qld-flood-extent-2013-bundaberg/v/2013-01-29/data.xlsx is a workbook with the 25 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/qld-flood-extent-2013-bundaberg/v/2013-01-29/data.csv.gz is the CSV at about a tenth of the size.

How often is Bundaberg flood extent updated?

Natural Resources and Mines no longer updates it. This site checks the portal every week and adds a dated version when the file changes.

Can I use Bundaberg flood extent 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 Bundaberg flood extent?

No. The publisher is Department of Natural Resources and Mines, Manufacturing and Regional and Rural Development, and its page is https://www.data.qld.gov.au/dataset/flood-extent-series. 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 Bundaberg flood extent use?

The map service projects the polygons to WGS84 (EPSG:4326) on request. They are moved to GDA2020 for publication. 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.

Historical flood extents, Queensland is 8 tables here, and each takes its version date from its own file.

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 of Natural Resources and Mines, Manufacturing and Regional and Rural Development, Queensland Government, Flood extent series, 2013 Floodline Bundaberg, sourced 3 October 2026, https://www.data.qld.gov.au/dataset/flood-extent-series, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/qld-flood-extent-2013-bundaberg/v/2013-01-29/

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 of Natural Resources and Mines, Manufacturing and Regional and Rural Development states the licence, CC BY 4.0, on its own page, which was read and recorded here on 1 October 2026.

Every fetch reads the licence again and stops when it has changed. The fetch that made version 2013-01-29 read it from www.data.qld.gov.au on 3 October 2026.

Also published on

Hugging Faceload_dataset("National-Digital/qld-flood-extent-2013-bundaberg")
Kagglewith a starter notebook
ZenodoDOI 10.5281/zenodo.23122491

Each copy carries the same attribution and links back to this page.

For agents and tools

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.

Source

Department of Natural Resources and Mines, Manufacturing and Regional and Rural Development publishes this table on spatial-gis.information.qld.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 3 October 2026. Source SHA-256 a8172d56f6086ab1…

Improve this dataset

This page is built from register/qld-flood-extent-2013-bundaberg.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