2 commits

Author	SHA1	Message	Date
Graham McIntire	6476bc8045	Dedupe ERA5 fetch jobs by (lat, lon, valid_time) ... The Era5FetchWorker now declares an Oban unique constraint on {lat, lon, valid_time} for any job in available/scheduled/executing/ retryable, so two backfill runs targeting the same contact grid point can no longer spawn parallel CDS requests for the same hour. Because Oban OSS insert_all doesn't honor unique, ERA5 jobs are now routed through Oban.insert/1 from ContactWeatherEnqueueWorker and the era5_backfill mix task. Other worker types still use insert_all.	2026-04-08 15:52:53 -05:00
Graham McIntire	dea407c8ca	Add ERA5 reanalysis and RTMA data sources ... ERA5 (Copernicus CDS API): - Era5Profile schema matching HRRR profile structure for interop - Era5Client with async job submission, polling, GRIB2 download - Era5FetchWorker (Oban queue: era5, max_attempts: 5) - Unified lookup: Weather.best_profile_for_contact/1 tries HRRR first, falls back to ERA5 for pre-2014 contacts RTMA (NOAA S3, 2.5km/15-min): - RtmaObservation schema for surface-only fields - RtmaClient with byte-range GRIB2 requests (same pattern as HRRR) - RtmaFetchWorker (Oban queue: rtma, max_attempts: 10) - Weather.find_nearest_rtma/3 for surface condition lookup Both queues added to production Oban config (2 workers each).	2026-04-07 12:04:16 -05:00