How shaswatabarua/nasa-fire-calendar-backend works
This is a small FastAPI service for querying NASA fire-activity data. Clients can request fire history for a geographic area and date range, or compare a date’s fire activity with a day-of-year climatology baseline; a health route reports that the API is running. The route handlers in main.py issue SQL through SQLAlchemy and format the results. The README is empty, so this map reflects only the supplied source; database schema and deployment details are not shown.
Main entry points: main.py SQLAlchemy engine
Components 8
HTTP API
- FastAPI app
main.py - Health route
main.py
Fire Analytics
- Fire history route
main.py - Critical periods route
main.py
Data Access
- SQLAlchemy engine
main.py - Daily fire data
- Climatology baseline
Other components
- API client
Connections 14
- API client → FastAPI app: HTTP request
- FastAPI app → Health route: dispatches
- FastAPI app → Fire history route: dispatches
- FastAPI app → Critical periods route: dispatches
- Health route → API client: returns status
- Fire history route → SQLAlchemy engine: queries history
- Critical periods route → SQLAlchemy engine: queries activity
- Critical periods route → SQLAlchemy engine: queries baseline
- SQLAlchemy engine → Daily fire data: reads
- SQLAlchemy engine → Climatology baseline: reads
- SQLAlchemy engine → Fire history route: returns rows
- SQLAlchemy engine → Critical periods route: returns values
- Fire history route → API client: returns history
- Critical periods route → API client: returns assessment