Reference · built on requestCommons signalHazards & public safety

NSW RFS Major Incidents Feed

Current fires and incidents in New South Wales with alert level, status and location from the NSW Rural Fire Service feed.

About

The NSW Rural Fire Service publishes its Current Incidents Feed for New South Wales as GeoJSON, GeoRSS and Common Alerting Protocol XML at rfs.nsw.gov.au/feeds. Each feature carries a title, an alert level category, a pubDate, a guid that points at incidents.rfs.nsw.gov.au/api/v1/incidents, and a description with ALERT LEVEL, LOCATION, COUNCIL AREA, STATUS, TYPE, FIRE, SIZE, RESPONSIBLE AGENCY and UPDATED. Geometry is a Point or a GeometryCollection with a point and polygons. Data.NSW lists the feed under a Creative Commons Attribution licence, updated every 30 minutes.

Through Fibric, an operator matches incidents to your sites, stores and delivery areas in New South Wales and proposes a hold, a notice or an evacuation check for a person to approve.

This is a reference listing. It documents what Fibric would read from NSW RFS Major Incidents Feed and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • majorIncidents.json: a GeoJSON FeatureCollection of current incidents, with Point or GeometryCollection geometry including fire polygons
  • category per feature: the alert level, such as Advice, and Planned Burn or Not Applicable for other entries
  • description fields: ALERT LEVEL, LOCATION, COUNCIL AREA, STATUS, TYPE, FIRE, SIZE in hectares, RESPONSIBLE AGENCY and UPDATED
  • guid per incident linking to incidents.rfs.nsw.gov.au/api/v1/incidents/<id>, plus title, link and pubDate
  • majorIncidents.xml: the same incidents as RSS 2.0 with GeoRSS point elements and a channel ttl of 60
  • majorIncidentsCAP.xml: the Common Alerting Protocol form of the feed listed on Data.NSW

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold deliveries into a council area with an active fire

    Match order postcodes to COUNCIL AREA and to fire polygons and propose a hold on affected deliveries, with the alert level shown, for a person to confirm.

    With Weather Hold

  • Notify a site when an incident enters its radius

    When an incident point or polygon falls inside a site's watch radius, draft a notice with alert level, status and UPDATED time for the site lead to send.

    With Severe Weather Notice

  • Stand up an evacuation roster

    On a new incident near a site, pull the people on shift from the schedule and propose the roster and contacts for a person to confirm.

    With Evacuation Roster

  • Re-sequence field visits around incidents

    Compare the day's visit list with incident polygons and propose a new order that avoids affected areas, for a dispatcher to approve.

    With Route Resequence

Requirements

  • Site, store or delivery-area coordinates in New South Wales to match against incident points and polygons
  • A parser for the description string, since STATUS, SIZE and RESPONSIBLE AGENCY are HTML-separated text, not JSON fields
  • Attribution to the State of New South Wales (NSW Rural Fire Service) under the Creative Commons Attribution licence on Data.NSW
  • Polling on the 30-minute update cycle rather than on every request
Authentication
No key. The three feed URLs answer public GET requests; the JSON response sets Cache-Control max-age=30, must-revalidate.

Limits

  • The structured fields live inside the description text; the JSON properties are title, link, category, guid, pubDate and description
  • Incident information is updated every 30 minutes, so a feature can lag the ground by that long
  • The feed covers current incidents only; there is no history endpoint in the feed itself
  • The rfs.nsw.gov.au documentation pages sit behind a browser challenge; the feed URLs themselves do not

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request NSW RFS Major Incidents Feed ↗

Questions and answers

How often does the feed update?
Data.NSW states incident information is updated every 30 minutes. The RSS channel sets ttl to 60, and the JSON response carries Cache-Control: max-age=30, must-revalidate with a Last-Modified header. Poll on that cycle and compare UPDATED per incident.
Which formats are published?
Three: GeoJSON at /feeds/majorIncidents.json, GeoRSS at /feeds/majorIncidents.xml and Common Alerting Protocol at /feeds/majorIncidentsCAP.xml. Data.NSW lists all three under the NSW Rural Fire Service Current Incidents Feed dataset.
What licence applies?
Data.NSW lists the dataset under Creative Commons Attribution. The RSS channel's copyright element reads State of New South Wales (NSW Rural Fire Service). Credit the NSW RFS when you republish incident data.
Ask about NSW RFS Major Incidents Feed

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.