- Project Demo: https://biabcaval.github.io/space_apps_hackaton/
- Project Presentation (PDF): https://www.dropbox.com/scl/fi/bia57oy3e2cbe68ysvt5c/Breez-Nasa-Space-Apps-2025.pdf?rlkey=jeovhp7gmhpb6enq3rdgbkhdk&st=xdo5drt5&dl=0
Breez is a NASA Space Apps 2025 project focused on helping people understand local air quality risk using real-time and satellite-backed environmental data.
The application combines:
- OpenWeather air pollution data for global coverage
- NASA TEMPO satellite measurements for US-focused atmospheric insights
- Daymet historical climate data for contextual trend visualization
- Risk-group-oriented health guidance
Breez gives users a practical, location-based environmental briefing so they can:
- See current AQI and pollutant concentrations
- Compare forecasted air quality trends
- Switch between global API data and satellite-derived data
- Understand health impact guidance by risk group
- View weather and climate context for the selected location
- Frontend: React + Vite (
frontend) - Backend API: FastAPI (
backend) - Optional service: WhatsApp notification microservice (
qualidade-do-ar)
The main user flow documented below is based on frontend + backend.
Users can opt in to notifications by providing name, phone number, and current location.
Users search by city/address and select a location to load all environmental widgets.
The main dashboard shows map context, AQI score, and pollutant concentration cards.
Users can switch to forecast mode to inspect daily AQI evolution and trend bars.
Recommendations are tailored by audience segment (children, elderly, athletes, etc.) based on AQI conditions.
Hourly and daily weather forecasts provide context for air quality interpretation.
Switching data source to TEMPO surfaces satellite-derived pollutant estimates and metadata.
Climate charts add historical context (temperature and precipitation) for the selected location.
cd backend
source venv/bin/activate
python main.pyExpected: API running at http://localhost:8000.
Required environment values are read from backend/.env, including:
OPENWEATHER_API_KEY_1(orOPENWEATHER_API_KEYS)EARTHDATA_USERNAMEandEARTHDATA_PASSWORD(for TEMPO endpoints)
cd frontend
npm install
npm run dev -- --host 127.0.0.1 --port 5173Frontend env expected in .env (repo root currently contains these keys):
VITE_API_URL_PRIMARYVITE_API_URL_FALLBACK
The health recommendation CSV is required by the HealthInfoTab component and is included at:
frontend/public/data/crisis_group.csv
- TEMPO coverage is US-focused; non-US locations may not return satellite measurements.
- TEMPO data has practical latency and may use historical fallback windows.
- The WhatsApp service in
qualidade-do-aris optional and not required for the core UI flow shown above.








