publicdata.au publicdata.au on GitHub

Bushfires NT brigade and office locations

live
Publisher Northern Territory Fire and Emergency ServicesUpdated when a site changesLicence CC BY 4.0Latest 2024-05-29Rows 23Fields 8

The office headquarters and volunteer bushfire brigade sites of Bushfires NT, part of Northern Territory Fire and Emergency Services. Each row carries the site code, name and type, the fire management zone, the street address, the land parcel, and the latitude and longitude. The publisher ships the table as a workbook inside the shapefile download, and that workbook is read here.

Also called: Bushfires NT Brigade and Office Headquarters Locations, NT volunteer bushfire brigade locations, Bushfires NT office addresses.

Before you use it
What is in each row?
One Bushfires NT site, either an office headquarters or a volunteer bushfire brigade, with its site code, name, fire management zone, street address, land parcel, and latitude and longitude.
Why do two rows share an address?
Where a brigade works from a Bushfires NT office, as in Alice Springs, the publisher lists the office and the brigade as two sites at one address.
How often is it updated?
The publisher updates the file when a site changes. This site checks it weekly and adds a dated version when the file changes.
23 sites drawn in 21 cells of 0.05 degrees, the fullest with 2.
Sites counted in cells of 0.05 degrees. State outlines from the ABS Australian Statistical Geography Standard 2021, CC BY 4.0.

Made for agents

Connect your AI agent

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

Then ask it: What does Bushfires NT brigade and office locations 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/nt-bushfire-brigade-locations/latest/data.xlsx
Download this file

One workbook with a records sheet of 23 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/nt-bushfire-brigade-locations/latest/ redirects to the newest version.

https://publicdata.au/d/nt-bushfire-brigade-locations/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 headers were made snake_case. The publisher's header is kept beside every field in schema.json. Rows were left alone.

FieldTypePublisher's headerNote
site_idstringSiteID
namestringName
site_typestringSiteTypeHeadquarters or Volunteer Bushfire Brigade.
fire_management_zonestringFMZone
addressstringLocAddress
parcelstringLocParcel
latitudenumberLatitude
longitudenumberLongitude

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

The first 10 rows

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

site_idnamesite_typefire_management_zoneaddressparcellatitudelongitude
AH_HQAcacia Hills, OfficeHeadquartersVernon Arafura2645 Stuart Highway, Acacia Hills (cnr Townend Road)Sec 2900 Hundred of Strangways-12.70238131.08704
AH_VBBAcacia HillsVolunteer Bushfire BrigadeVernon Arafura330 Whitstone Road, Acacia HillsSec 1715 Hundred of Colton-12.76594131.17063
AS_HQAlice Springs, OfficeHeadquartersAlice Springs3 Elder Street, Ciccone, Alice SpringsLot 1548 Town of Alice Springs-23.6996435133.8719234
AS_VBBAlice SpringsVolunteer Bushfire BrigadeAlice Springs3 Elder Street, Ciccone, Alice SpringsLot 1548 Town of Alice Springs-23.6996435133.8719234
BART_VBBBARTVolunteer Bushfire BrigadeVernon Arafura16 Cameron Road, BatchelorLot 142 Town of Batchelor-13.05206131.03425
BS_VBBBerry SpringsVolunteer Bushfire BrigadeVernon Arafura812 Cox Peninsula Road, Berry SpringsSec 1857 Hundred of Ayers-12.70114131.01319
CP_VBBCox PeninsulaVolunteer Bushfire BrigadeVernon Arafura142 Wagait Tower Road, Wagait BeachSec 62 Hundred of Bray-12.43571130.74954
DA_VBBDaly RiverVolunteer Bushfire BrigadeVernon Arafura496 Wooliana Road, Daly RiverNT Por 2801-13.7104048130.6811567
DD_VBBDouglas DalyVolunteer Bushfire BrigadeVernon Arafura75 Wilson Road, Fleming16 Town of Fleming-13.8513872131.3003822
DR_VBBDarwin RiverVolunteer Bushfire BrigadeVernon Arafura0 Darwin River Road, Darwin RiverSec 2788 Hundred of Cavenagh-12.82156130.95735
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/nt-bushfire-brigade-locations/latest/data.json
{
  "site_id": "AH_HQ",
  "name": "Acacia Hills, Office",
  "site_type": "Headquarters",
  "fire_management_zone": "Vernon Arafura",
  "address": "2645 Stuart Highway, Acacia Hills (cnr Townend Road)",
  "parcel": "Sec 2900 Hundred of Strangways",
  "latitude": -12.70238,
  "longitude": 131.08704
}

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.

versions.json · changes.json · history.tar.zst (5.7 KB, every version's Parquet and manifest)

Questions

How do I download Bushfires NT brigade and office locations as a CSV file?

Open https://publicdata.au/d/nt-bushfire-brigade-locations/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/nt-bushfire-brigade-locations/v/2024-05-29/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 Bushfires NT brigade and office locations in Excel?

Yes. https://publicdata.au/d/nt-bushfire-brigade-locations/v/2024-05-29/data.xlsx is a workbook with the 23 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/nt-bushfire-brigade-locations/v/2024-05-29/data.csv.gz is the CSV at about a tenth of the size.

How often is Bushfires NT brigade and office locations updated?

NTFES releases it when a site changes. This site checks the portal every week and adds a dated version when the file changes.

Can I use Bushfires NT brigade and office locations 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 Bushfires NT brigade and office locations?

No. The publisher is Northern Territory Fire and Emergency Services, and its page is https://data.nt.gov.au/dataset/bushfires-nt-brigade-and-office-headquarters-locations. 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.zip with its SHA-256, so the two can be compared.

What coordinate system does Bushfires NT brigade and office locations use?

Decimal degrees as published. The publisher's shapefile of the same sites names GDA94. 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.zip so the change can be checked.

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.

Bushfires NT, Northern Territory Fire and Emergency Services, Northern Territory Government, Bushfires NT Brigade and Office Headquarters Locations, https://data.nt.gov.au/dataset/bushfires-nt-brigade-and-office-headquarters-locations, accessed 4 October 2026, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/nt-bushfire-brigade-locations/v/2024-05-29/

The map's state outlines are from the ABS Australian Statistical Geography Standard 2021, under CC BY 4.0.

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

Northern Territory Fire and Emergency Services 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 2024-05-29 read it from data.nt.gov.au on 4 October 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/nt-bushfire-brigade-locations")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23140629

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

Northern Territory Fire and Emergency Services publishes this table on ftp-dlrm.nt.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 4 October 2026. Source SHA-256 97ee18e4b7c303cf…

Improve this dataset

This page is built from register/nt-bushfire-brigade-locations.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