How ajeeva91-debug/alertora works
ALERTORA AI is a prototype severe-weather nowcasting and emergency-response platform. Users choose a location or map point, inspect hazard forecasts and risk, then use alerts, district operations guidance, or citizen precautions to respond. The browser controller renders the GIS map, timeline, countdown, simulation, and explainability panels; its API service uses mock data by default and can call the FastAPI backend when enabled. The backend prediction endpoint delegates to the nowcast engine. The documented sensor fusion and spatial database are not evidenced as live ingestion or persistence in the sampled runtime code.
Main entry points: app.js App controller · api.js API service · main.py REST API · mockData.js Demo weather data
Components 16
Browser experience
- App controller
js/app.js - GIS map
js/app.js - Nowcast timeline
js/app.js - Storm simulation
js/app.js - Storm countdown
js/app.js - Alerts feed
js/app.js - EOC operations
js/app.js - Safety guidance
js/app.js - XAI factors
js/app.js
Data service
- API service
js/api.js - Demo weather data
js/mockData.js
Forecast backend
- REST API
backend/main.py - Nowcast engine
backend/ai_engine.py - API data models
backend/models.py
Other components
- Dashboard user
- Nominatim geocoder
Connections 15
- Dashboard user → App controller: uses
- App controller → API service: requests data
- API service → Demo weather data: reads fallback
- API service → REST API: fetches live data
- REST API → Nowcast engine: requests prediction
- REST API → API data models: imports schemas
- App controller → GIS map: renders map
- App controller → Nowcast timeline: renders forecasts
- App controller → Storm simulation: runs demo
- App controller → Storm countdown: starts timer
- App controller → Alerts feed: renders alerts
- App controller → EOC operations: renders district view
- App controller → Safety guidance: renders precautions
- App controller → XAI factors: renders factors
- App controller → Nominatim geocoder: reverse geocodes