How rkomtchuente/eonet works
EONET tracks natural events by fetching open-event data hourly, upserting the latest event geometry into PostgreSQL, and exposing event records through an HTTP API. The repository also contains a Tableau workbook, but its contents and connection to the data flow were not inspected, so no relationship is asserted. The graph reflects the sampled ETL, DAG, and API code; the README provides no further capability details.
Main entry points: natural_events_ETL.py EONET ETL · eonet_dag.py Hourly DAG · main.py Events API
Components 9
Event ingestion
- Hourly DAG
dags/eonet_dag.py - EONET ETL
dags/natural_events_ETL.py
Event storage
- PostgreSQL Events
- Table schema SQL
tablecreation.sql
Data access
- Events API
api/main.py - Tableau workbook
eonet events.twb
Other components
- Airflow scheduler
- NASA EONET API
- API client
Connections 6
- Airflow scheduler → Hourly DAG: runs
dags/eonet_dag.py - Hourly DAG → EONET ETL: calls
dags/eonet_dag.py - EONET ETL → NASA EONET API: fetches events
dags/natural_events_ETL.py - EONET ETL → PostgreSQL Events: upserts events
dags/natural_events_ETL.py - API client → Events API: requests events
api/main.py - Events API → PostgreSQL Events: queries events
api/main.py