Past wave buoy deployments, Department of Transport, Western Australia
liveThe Department of Transport's list of past wave rider buoy deployments, from the Wave Stations Historic layer of DOT-024 on the Western Australian Government's public map service. Each row carries the location name and identifier, the dates its data covers, its coordinates and depth, and the publisher's links to its readme, deployment metadata and yearly processed data where one is offered.
Also called: Wave Stations, Department of Transport (DOT-024), Wave Stations Historic, WA wave rider buoy locations.
Part of Wave buoy stations of the Department of Transport, Western Australia, 2 tables the publisher releases together: Wave buoy stations in operation, Department of Transport, Western Australia.
- What is in each row?
- One deployment of a Department of Transport wave rider buoy, with its location name and identifier, the dates its data covers, its latitude, longitude and depth, the publisher's links to the data readme and deployment metadata, a yearly data download for about half of the deployments, the licence the publisher attaches to the record, the date the record was produced and its status. The live readings column is empty for every past deployment.
- Are the wave readings included?
- No. The publisher serves each deployment's readings as a zip of yearly workbooks linked from the download column where the row has one, which this site does not copy. Each row here describes a buoy deployment.
- Where is the publisher's file?
- There is none for the station list. This site reads every feature of the publisher's public map service layer in pages, in WGS84, and keeps them as one GeoJSON file, which is the source file beside every version.
Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 13 fields, count and filter across all 43 rows and diff its versions. Every answer names the version and carries Department of Transport WA's attribution. No key.
Then ask it: What does Past wave buoy deployments, Department of Transport, Western 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.
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=depth&metric=count
Buoy deployments by depth: 6 10m, 3 8m, 3 7m, 3 6m.
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/wa-wave-stations-historic/latest/ redirects to the newest version.
https://publicdata.au/d/wa-wave-stations-historic/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/wa-wave-stations-historic/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("wa-wave-stations-historic")
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("wa-wave-stations-historic")
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/wa-wave-stations-historic/v/2026-10-03/data.duckdb' AS wa_wave_stations_historic (READ_ONLY);
SELECT location_id, count(*) FROM wa_wave_stations_historic.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/wa-wave-stations-historic/aggregate?group=depth&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.
| Field | Type | Publisher's header | Note |
|---|---|---|---|
| location_name | string | location_name | |
| location_id | string | location_id | |
| data_available_between | string | data_available_between | The first and last dates of the deployment's data, as the publisher writes them. |
| latitude | number | latitude | |
| longitude | number | longitude | |
| depth | string | depth | Water depth at the buoy as the publisher writes it, for example 60m. |
| readme | string | readme | |
| download_metadata | string | download_metadata | |
| live_wave | string | live_wave | |
| download_data | string | download_data | |
| licence | string | licence | |
| production_date | string | production_date | |
| status | string | status |
Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is location_id.
The first 10 rows
From the latest version, in the publisher's order, with every field. A blank cell is shown as null.
| location_name | location_id | data_available_between | latitude | longitude | depth | readme | download_metadata | live_wave | download_data | licence | production_date | status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Denison 01 | DEN02 | 29/07/1974 and 28/10/1975 | -29.261931 | 114.847233 | 20m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/DEN02_Metadata.zip | null | null | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Esperance 01 | ESP11 | 21/02/1980 and 04/03/1981 | -33.840542 | 121.932788 | 12m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/ESP11_Metadata.zip | null | null | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Augusta 02 | AUG30 | 02/09/1988 and 22/02/1990 | -34.366376 | 115.169455 | 10m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/AUG30_Metadata.zip | null | null | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Hillarys | HIL25 | 31/03/1987 and 20/05/1987 | -31.828876 | 115.730289 | 6m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/HIL25_Metadata.zip | null | null | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Geraldton 02 | GER10 | 13/03/1980 and 01/01/1985 | -28.759709 | 114.565567 | 12m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/GER10_Metadata.zip | null | null | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Coral Bay | COR48 | 22/12/2004 and 30/03/2005 | -23.174308 | 113.744177 | 20m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/COR48_Metadata.zip | null | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WaveRider_Yearly_Processed/COR48_YEARLY_PROC… | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Kwinana | KWA36 | 02/11/1993 and 06/12/1993 | -32.242973 | 115.754455 | NA | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/KWA36_Metadata.zip | null | null | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Guilderton 02 | GUI29 | 11/04/1988 and 19/07/1988 | -31.359709 | 115.481955 | 10m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/GUI29_Metadata.zip | null | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WaveRider_Yearly_Processed/GUI29_YEARLY_PROC… | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Jurien Bay 01 | JUR14 | 18/03/1981 and 23/09/1982 | -30.292209 | 115.033622 | 11.5m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/JUR14_Metadata.zip | null | null | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
| Cape Naturaliste 01 | NAT43 | 28/05/1999 and 27/04/2004 | -33.362209 | 114.775567 | 50m | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/NAT43_Metadata.zip | null | https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WaveRider_Yearly_Processed/NAT43_YEARLY_PROC… | http://creativecommons.org/licenses/by/4.0/ | Dataset Produced on 02/07/2021 10:14 | #Historic |
The first row as JSON
As it appears in data.json.
GET https://publicdata.au/d/wa-wave-stations-historic/latest/data.json
{
"location_name": "Denison 01",
"location_id": "DEN02",
"data_available_between": "29/07/1974 and 28/10/1975",
"latitude": -29.261931,
"longitude": 114.847233,
"depth": "20m",
"readme": "https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/WAVE_READ_ME.htm",
"download_metadata": "https://s3-ap-southeast-2.amazonaws.com/transport.wa/WAVERIDER_DEPLOYMENTS/DeploymentMetadata/DEN02_Metadata.zip",
"live_wave": null,
"download_data": null,
"licence": "http://creativecommons.org/licenses/by/4.0/",
"production_date": "Dataset Produced on 02/07/2021 10:14",
"status": "#Historic"
}
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-10-03 43 rows13 fieldsutf-88f10aaa61ccaThe layer states no edit date or dated records, so this version is dated by the portal record.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 (7.5 KB, every version's Parquet and manifest)
Questions
How do I download Past wave buoy deployments, Department of Transport as a CSV file?
Open https://publicdata.au/d/wa-wave-stations-historic/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/wa-wave-stations-historic/v/2026-10-03/data.csv today. The same path serves Excel, JSON, GeoJSON, Parquet, SQLite, DuckDB, GeoPackage, GeoParquet, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.
Can I open Past wave buoy deployments, Department of Transport in Excel?
Yes. https://publicdata.au/d/wa-wave-stations-historic/v/2026-10-03/data.xlsx is a workbook with the 43 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/wa-wave-stations-historic/v/2026-10-03/data.csv.gz is the CSV at about a tenth of the size.
What years does Past wave buoy deployments, Department of Transport cover?
The current version covers the years since 1974. Each release from Department of Transport WA becomes a new dated version here, and earlier versions stay online.
How often is Past wave buoy deployments, Department of Transport updated?
Department of Transport WA releases it as buoys are deployed and retired. This site checks the portal every week and adds a dated version when the file changes.
Can I use Past wave buoy deployments, Department of Transport 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 Past wave buoy deployments, Department of Transport?
No. The publisher is Department of Transport, Western Australia, and its page is https://catalogue.data.wa.gov.au/dataset/wave-stations. 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 Past wave buoy deployments, Department of Transport use?
Longitude and latitude in decimal degrees from the publisher's own attribute columns. The layer is held in GDA2020, which differs from WGS84 by under 2 metres. The GeoJSON file uses the same coordinates, which is what GeoJSON expects.
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.
The publisher releases Wave buoy stations of the Department of Transport, Western Australia as 2 files at once, so all 2 tables here share a version date.