publicdata.au publicdata.au on GitHub

Western Queensland flood extent, February 2019

live
Publisher Department of Natural Resources and Mines, Manufacturing and Regional and Rural DevelopmentUpdated no longerLicence CC BY 4.0Latest 2019-02-09Rows 22Fields 7

The 2019 Floodline Western Queensland layer of the Queensland Flood extent series, one row per polygon of mapped inundation for the February 2019 flood over the Flinders and Diamantina catchments in western Queensland, drawn from 3 metre satellite 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: 2019 western Queensland flood map, Western Queensland flood extent, February 2019 polygons, 2019 Floodline Western Queensland 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, Bundaberg flood extent, January 2013, Fitzroy River flood extent, April 2017, Logan and Albert rivers flood extent, April 2017.

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 22 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 Western Queensland flood extent, February 2019 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.

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 keeps its content.

Format
"Latest" redirects to the newest version and will change when the publisher releases again. A dated version keeps its content.
https://publicdata.au/d/qld-flood-extent-2019-western/latest/data.xlsx
Download this file

One workbook with a records sheet of 22 typed rows, a fields sheet and a publicdata sheet with the provenance. Dates are real Excel dates. Opens in Excel, Numbers, LibreOffice and Sheets.

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-2019-western/latest/ redirects to the newest version.

https://publicdata.au/d/qld-flood-extent-2019-western/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.

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.

FieldTypePublisher's headerNote
objectidintegerobjectid
feature_typestringfeaturetype
locationstringlocation
feature_reliabilitydatefeaturereliabilityThe date the department gives for the reliability of the outline, usually the capture date of its source.
feature_sourcestringfeaturesource
attribute_reliabilitydateattributereliability
attribute_sourcestringattributesource

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.

objectidfeature_typelocationfeature_reliabilityfeature_sourceattribute_reliabilityattribute_source
1FloodlineDiamantina Drainage Basin2019-02-08Diamantina_2019_3m_ps_flood_mosaic2019-02-08Diamantina_2019_3m_ps_flood_mosaic
2FloodlineDiamantina Drainage Basin2019-02-08Diamantina_2019_3m_ps_flood_mosaic2019-02-08Diamantina_2019_3m_ps_flood_mosaic
3FloodlineDiamantina Drainage Basin2019-02-08Sentinel_nw_2019_10mv22019-02-08Sentinel_nw_2019_10mv2
4FloodlineDiamantina Drainage Basin2019-02-08Sentinel_nw_2019_10mv22019-02-08Sentinel_nw_2019_10mv2
5FloodlineDiamantina Drainage Basin2019-02-08Sentinel_nw_2019_10mv22019-02-08Sentinel_nw_2019_10mv2
6FloodlineDiamantina Drainage Basin2019-02-08Sentinel_nw_2019_10mv22019-02-08Sentinel_nw_2019_10mv2
7FloodlineDiamantina Drainage Basin2019-02-08Sentinel_nw_2019_10mv22019-02-08Sentinel_nw_2019_10mv2
8FloodlineFlinders Drainage Basin2019-02-09Planet - Flinders_2019_3m_ps_flood_mosaic2019-02-09Planet - Flinders_2019_3m_ps_flood_mosaic
9FloodlineFlinders Drainage Basin2019-02-09Sentinel_nw_2019_10mv22019-02-09Sentinel_nw_2019_10mv2
10FloodlineFlinders Drainage Basin2019-02-09Planet - Flinders_2019_3m_ps_flood_mosaic2019-02-09Planet - Flinders_2019_3m_ps_flood_mosaic
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/qld-flood-extent-2019-western/latest/data.json
{
  "objectid": 1,
  "feature_type": "Floodline",
  "location": "Diamantina Drainage Basin",
  "feature_reliability": "2019-02-08",
  "feature_source": "Diamantina_2019_3m_ps_flood_mosaic",
  "attribute_reliability": "2019-02-08",
  "attribute_source": "Diamantina_2019_3m_ps_flood_mosaic"
}

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 that like and ilike ignore case in the ASCII letters A to Z. Prefix not. to negate a filter, as not.eq.value.

OperatorWhat it matches
eq.valueEqual to the value.
neq.valueNot equal to the value. A blank cell does not match.
gt.valueGreater than the value.
gte.valueGreater than or equal to the value.
lt.valueLess than the value.
lte.valueLess 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.nullBlank in the source, or suppressed by the publisher.
ParameterWhat it does
selectFields to return, comma-separated. Every field when absent.
orderfield.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.
limitRows per page, 1 to 10,000. 100 when absent.
offsetRows to skip. The next URL in each answer sets it for you.
groupOn aggregate, fields to group by, comma-separated.
metricOn aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent.
formatjson, 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 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. 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.

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.

  • 2019-02-09
    22 rows7 fieldsutf-8357c7a959ad5

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

Questions

How do I download Western Queensland flood extent as a CSV file?

Open https://publicdata.au/d/qld-flood-extent-2019-western/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/qld-flood-extent-2019-western/v/2019-02-09/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 Western Queensland flood extent in Excel?

Yes. https://publicdata.au/d/qld-flood-extent-2019-western/v/2019-02-09/data.xlsx is a workbook with the 22 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-2019-western/v/2019-02-09/data.csv.gz is the CSV at about a tenth of the size.

How often is Western Queensland 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 Western Queensland 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 Western Queensland 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. National Digital converted the publisher's file to other formats. It renamed and typed the columns and kept only those the schema lists. 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.

What coordinate system does Western Queensland 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, 2019 Floodline Western Queensland, 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-2019-western/v/2019-02-09/

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 2019-02-09 read it from www.data.qld.gov.au on 3 October 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/qld-flood-extent-2019-western")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23122501

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

For agents and tools

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 357c7a959ad58fd6…

Improve this dataset

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