GDACS Disaster Alert Monitor - Event Revisions

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Documentation captured from build 1.0.3. Example outputs retain their original sample context; they are not live results.

GDACS Disaster Alert Monitor - Event Revisions

Stable event identities retain changing alert levels and episode details.

Monitor GDACS disaster alerts, country coverage, alert levels and event revisions. Export source evidence and compare saved observations.

Start in under a minute

1. Paste event types into the first input field, or use the included sample.
2. Keep the five-result limit for your first run and choose Start.
3. Open Observations, Scope and diagnostics, or the Readable run report in Output. Export CSV or JSON from the dataset.

{
  "eventTypes": [
    "EQ"
  ],
  "maxResults": 5,
  "itemsPerQuery": 3
}

No source account, API key, paid proxy or extra subscription is required for these public endpoints. Source availability and rate limits still apply.

Who this helps

Logistics and business-continuity teams reviewing official disaster alerts.

A real output sample

Captured in a successful bounded Apify run; arrays and long text are shortened for readability. Values are snapshots, not live guarantees.

{
  "recordId": "EQ:1572122",
  "title": "Green earthquake (Magnitude 5.7M, Depth:10km) in Pakistan 17/10/2026 05:06 UTC, 2 thousand (in MMI>=VII).",
  "eventType": "EQ",
  "eventId": "1572122",
  "episodeId": "1740688",
  "country": "Pakistan",
  "alertLevel": "Green",
  "severity": "Magnitude 5.7M, Depth:10km",
  "updatedAt": "Sun, 18 Oct 2026 14:01:04 GMT",
  "url": "https://www.gdacs.org/report.aspx?eventtype=EQ&eventid=1572122",
  "observedAt": "2026-10-18T15:18:35.993Z",
  "comparisonStatus": "not_requested"
}

What you receive

One row per unique confirmed observation. Every row includes a stable recordId, title, source URL and observation time.

Saved comparisons

Enable Compare with saved observations, choose a snapshot name, and reuse the same input scope. The first run establishes history; it cannot report changes before that point. Enable Save only new or changed observations for later runs if you want a change-only export. An unchanged run can correctly save zero rows.

Only confirmed saved rows advance history. A bounded or failed run never establishes that a missing record was deleted. History is stored in a named key-value store in the running user's account. Use one writer per snapshot: do not overlap runs against the same snapshot. Change the snapshot name when starting a new independent workflow.

Scope and limitations

Current GDACS RSS window only; supported types EQ, FL, TC, DR, WF or ALL. This is a periodic observation feed, not emergency warning delivery or proof of disruption at a facility. Attribute GDACS / European Union when redistributing source information.

At most ten input values and five hundred saved rows per run. Each input uses a bounded source response. Shared feeds are cached within the run; public documents may require a robots.txt request. Requests are paced. Responses are capped at 8 MiB and share the run deadline. No authentication bypass or code execution is performed. HTTP 429 stops further requests. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

Pricing

The configured base price is $0.001 per saved observation, plus $0.00005 per start at the default memory. Five observations cost $0.00505 at that base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Diagnostics, reports and unchanged skipped rows are not dataset result events.

A practical workflow

Logistics and business-continuity teams reviewing official disaster alerts. Stable event identities retain changing alert levels and episode details. Start with the included five-result sample, review source links, then save your own scope as an Actor task. Use a named snapshot for repeat runs and keep source metadata with downstream exports.

Make it recurring

Save an Actor task with your inputs, then attach an Apify Schedule. For change detection, keep the same snapshot and avoid overlapping runs. Add an integration to deliver results to your own spreadsheet or workflow. No external delivery is enabled automatically.

Frequently asked questions

Why did a repeat run return zero rows? With change-only mode enabled, unchanged records are skipped. Check SUMMARY to distinguish this from empty matches, limits, or an upstream error.

Does a missing record mean it was deleted? No. Searches cover a bounded source window; a record can move outside it. Missing records never become deletion claims.

Can I export or integrate the data? Yes. Use Apify dataset exports for CSV/JSON, or the Actor API and your own integrations. No external message or delivery is enabled by default.

Examples

1. Event types: EQ — A bounded EQ observation sample. Review source evidence and export rows or compare them in a later run.
2. Event types: FL — A bounded FL observation sample. Review source evidence and export rows or compare them in a later run.
3. Event types: TC — A bounded TC observation sample. Review source evidence and export rows or compare them in a later run.

Source and support

Official source documentation. This independent Mayd IT tool is not affiliated with the source platform. Open an Actor issue with the run ID and expected result, or contact bmay@mayd-it.com. Never include credentials.

Workflow library and related tools

Product guide · Workflow and real output · All data tools · Use with AI