Reference · built on requestCommons signalHazards & public safety

NASA EONET

Curated natural events worldwide from NASA's Earth Observatory Natural Event Tracker, as JSON, GeoJSON, RSS and Atom.

Request accessPricing ↗

About

EONET, the Earth Observatory Natural Event Tracker, is a NASA service supported by the Earth Science Data Systems Program and the NASA Earth Observatory. Its v3 API at eonet.gsfc.nasa.gov/api/v3 lists natural events in 13 categories, from drought and dust to wildfires and volcanoes, each with a title, an id, a closed date, categories, source links and one or more dated geometry entries of type Point or Polygon. Events are drawn from 33 listed sources, among them GDACS, InciWeb, IRWIN, the USGS Earthquake Hazards Program and the Smithsonian Global Volcanism Program.

Through Fibric, an operator watches open events near your sites, suppliers and routes worldwide and proposes a hold, a notice or a supplier check for a person to approve.

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

  • /events: open events by default, with status open, closed or all, and filters for source, category, days, start, end, limit and bbox
  • /events/geojson: the same events as a GeoJSON FeatureCollection, plus /events/rss and /events/atom feeds
  • Per event: id, title, description, link, closed, categories, sources and a geometry array with date, type and coordinates
  • magnitudeValue and magnitudeUnit on geometry entries where a source reports one, such as acres for a wildfire, with magID, magMin and magMax filters
  • /categories: the 13 event categories, from drought, dustHaze and earthquakes to severeStorms, volcanoes, waterColor and wildfires
  • /sources: the 33 curating sources with ids such as GDACS, InciWeb, IRWIN, CALFIRE, USGS_EHP, SIVolcano and CEMS
  • /layers and /magnitudes: web map layers per category and the magnitude units in use

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

  • Check suppliers against open events worldwide

    Match supplier and port locations to open severeStorms, floods and wildfires events and propose an inbound delay note on affected purchase orders for a person to confirm.

    With Inbound Delay

  • Hold shipments into a flood or storm area

    Filter /events by category floods and severeStorms with a bbox around a delivery region and propose a hold on orders into it, for a person to approve.

    With Weather Hold

  • Add active events to the morning brief

    Each morning, list open events within a set distance of each site, with category, source and last geometry date, for a manager to review.

    With Morning Brief

  • Notify sites near a new volcanic or wildfire event

    When a new wildfires or volcanoes event opens within a site's radius, draft a notice with the source link for the site lead to send.

    With Severe Weather Notice

Requirements

  • Site, supplier and route coordinates, or a bbox per region, to match against event geometry
  • A rule for which categories and sources matter to you, passed as category and source parameters
  • A check on the closed field and the latest geometry date, because an open event can carry a geometry from days earlier
  • Tolerance for approximate extents: NASA states EONET spatial and temporal extents are approximations for general information
Authentication
No key or registration. The v3 endpoints answer public GET requests; the documentation names no rate limit.

Limits

  • NASA's disclaimer says EONET metadata and services are for visualization and general information only, and extents are approximations at best
  • Events arrive as sources curate them; there is no push or webhook, so you poll /events
  • Omitting status returns open events only; closed events need status=closed or all with a date window
  • Magnitude is present only where the source reports one, and the unit differs by category

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 NASA EONET ↗

Questions and answers

Which categories does EONET track?
Thirteen: drought, dustHaze, earthquakes, floods, landslides, manmade, seaLakeIce, severeStorms, snow, tempExtremes, volcanoes, waterColor and wildfires. Pass one or more ids, comma-separated, in the category parameter of /events.
How do I get events for a place and a period?
Use bbox for a bounding box, days for a count of prior days including today, or start and end in YYYY-MM-DD form. Add status=all or status=closed to include events that have ended; the default returns open events only.
Is EONET a formal record of event extent?
No. NASA's disclaimer states that EONET metadata and services are intended for visualization and general information, that extents are based on multiple sources, and that they are approximations at best. Use it to trigger a check, not as evidence.
Ask about NASA EONET

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by NASA Earth Science Data Systems Program and NASA Earth Observatory (eonet.gsfc.nasa.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy