Context
Nimbus PR 3 ships smoke plume polygons via HMS. HMS also publishes satellite-based fire detection points (hot spots) — these are the cause of the smoke. They're a separate data shape (point detections vs density polygons) and a different aviation-safety abstraction (TFRs via NOTAMs handle the airspace restriction angle, fires are more about situational awareness).
Suggested shape
skywatch nimbus fires LAT LON --radius 100 — list fire detection points within radius- Model:
Nimbus::Models::FireDetection with lat/lon, satellite source (GOES/VIIRS/MODIS), confidence, observation time
- Data source: HMS fire detection KML (same NESDIS server as smoke plumes)
- Brief integration: probably not — TFRs are the right surface for "don't fly here because of fire"; fire detections are situational context that doesn't quite fit adverse_conditions
Out of MVP scope
Filed as deferred so PR 3 stays focused on plume polygons — the core aviation-visibility signal.
Context
Nimbus PR 3 ships smoke plume polygons via HMS. HMS also publishes satellite-based fire detection points (hot spots) — these are the cause of the smoke. They're a separate data shape (point detections vs density polygons) and a different aviation-safety abstraction (TFRs via NOTAMs handle the airspace restriction angle, fires are more about situational awareness).
Suggested shape
skywatch nimbus fires LAT LON --radius 100— list fire detection points within radiusNimbus::Models::FireDetectionwith lat/lon, satellite source (GOES/VIIRS/MODIS), confidence, observation timeOut of MVP scope
Filed as deferred so PR 3 stays focused on plume polygons — the core aviation-visibility signal.