Reference · built on requestCommons signalHazards & public safety

GDACS

Near-real-time alerts for earthquakes, cyclones, floods, volcanoes, droughts, and wildfires from GDACS, as RSS, CAP, KML, and JSON.

About

The Global Disaster Alert and Coordination System is a cooperation framework between the United Nations and the European Commission. The Joint Research Centre computes the alerts; the UN Office for the Coordination of Humanitarian Affairs acts as secretariat. Earthquake, tsunami, and tropical cyclone assessments run automatically; floods and volcanic eruptions are entered manually. Each event gets a Green, Orange, or Red alert level from an alert score that weighs hazard severity, exposed population, and country vulnerability. The RSS feed at gdacs.org/xml/rss.xml lists current events with event type, alert level, dates, country, bounding box, and a per-event CAP file; a Swagger-documented JSON API serves event data, episodes, polygons, and impact estimates.

Through Fibric, an operator reads alerts whose bounding box touches your sites, suppliers, or lanes and proposes the notice, hold, or chase for your approval.

This is a reference listing. It documents what Fibric would read from GDACS 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

  • Current events from xml/rss.xml, with gdacs:eventtype EQ, TC, FL, VO, DR, or WF, gdacs:eventid, gdacs:episodeid, and gdacs:iscurrent
  • gdacs:alertlevel and gdacs:alertscore per event, plus episode-level gdacs:episodealertlevel and gdacs:episodealertscore
  • gdacs:fromdate, gdacs:todate, gdacs:dateadded, gdacs:datemodified, gdacs:country, gdacs:iso3, geo:Point, and gdacs:bbox as lonmin lonmax latmin latmax
  • gdacs:severity, gdacs:population, and gdacs:vulnerability values, the gdacs:glide number, and a gdacs:cap link to the event's CAP XML
  • Event and episode records from the API: /api/Events/geteventdata, /api/Events/getepisodedata, and /api/Events/geteventlist/search by eventlist, alertlevel, fromDate, toDate, and country
  • Geometry from /api/Polygons/getgeometry by eventtype, eventid, episodeid, and polygontype, and impact estimates from /api/Export/getimpact and /api/Export/getaffectedlocations
  • Feed variants xml/rss_24h.xml, xml/rss_7d.xml, xml/gdacs_cap.xml, and xml/gdacs.kml, and hazard products such as /api/Shakemap/getdetails and /api/Cyclonesurge/getdetails

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 inbound orders behind a Red cyclone

    When a TC or FL event at Orange or Red covers a supplier's location, the operator lists the open purchase orders from that supplier and proposes a delay expectation and a chase.

    With Inbound Delay, Supplier Fill Rate

  • Reroute shipments crossing an alert box

    The operator matches in-transit shipment lanes to the bounding box of new Orange or Red events and proposes an exception note per shipment with the GDACS report link.

    With Carrier Exception

  • Warn staff at sites inside an alert

    For an EQ, TC, or WF event whose polygon covers a site, the operator drafts a notice with alert level, dates, and the CAP instruction, for a person to send.

    With Severe Weather Notice, Evacuation Roster

  • Watch vendor sites for disruption

    The operator keeps a list of vendor locations, flags any inside a current event, and proposes an outage watch with the episode id and alert score.

    With Vendor Outage

Requirements

  • A point or polygon per site, supplier, or lane to test against gdacs:bbox and, where needed, the event polygon from /api/Polygons/getgeometry
  • A rule for which alert levels act: Green for awareness, Orange and Red for a proposal
  • Polling of rss.xml on an interval, with gdacs:datemodified and gdacs:episodeid used to tell a new episode from a repeat
  • Credit to GDACS on reuse: per-event resources carry the notice European Union, CC BY 4.0, reuse allowed with appropriate credit
Authentication
No key or account. The RSS, CAP, and KML feeds and the JSON API answer plain GET requests; the Swagger document declares no security scheme.

Limits

  • GDACS states its information is purely indicative and should not be used for decision making without other sources
  • Notifications are near real time, but no guarantee is given of completeness or timeliness, and they do not replace national alerts
  • Floods and volcanic eruptions are entered manually; only earthquakes, tsunamis, and tropical cyclones are fully automatic
  • Search endpoints return the first 100 elements and need pageSize and pageNumber to page further

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 GDACS ↗

Questions and answers

What do the Green, Orange, and Red levels mean?
They come from the GDACS alert score. For earthquakes, Green is a score below 1, Orange from 1 to below 2, Red 2 and above; the score weighs intensity, exposed population by Modified Mercalli zone, and country vulnerability from the INFORM index. Tsunami scores are calculated separately.
How fast are alerts issued?
Earthquake, tsunami, and tropical cyclone assessments are automatic. The earthquake model uses USGS shakemaps made available a few minutes after the event. Floods and volcanic eruptions are entered manually. GDACS gives no guarantee of completeness or timeliness.
Can I reuse GDACS data?
The RSS channel is marked public domain, and per-event resources carry a European Union CC BY 4.0 notice requiring credit to GDACS. The terms of use provide the data as is, without warranty, and state that GDACS services do not override alerts from national disaster management authorities.
Ask about GDACS

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.