goes-fdc-fire

○unverified

Active-fire alerts read from the SOURCE product rather than from a vendor feed: NOAA's GOES-R ABI L2 Fire/Hot-Spot Characterization (ABI-L2-FDC), taken straight off the public NOAA Open Data S3 buckets. This is the same operational detection that NASA FIRMS re-serves for GOES — verified, not asserted: over the Palisades Fire ignition window, reading ABI-L2-FDCF and keeping the four mask codes FIRMS exports reproduces the FIRMS rows at F1 1.0000 with FRP equal to within the CSV's rounding (research/fire-detection-cloud-native/VALIDATION.md). Reading the source is what buys the difference: - cadence: ABI-L2-FDCC is a 5-min CONUS scan; FIRMS ingests the 10-min Full Disk. - fields: fire Temp (K), Area (m2) and DQF, all dropped by the FIRMS CSV. - YOUR threshold: FIRMS exports only mask 10/11/30/31 and silently discards the probability classes. In three hours over an active megafire it withheld 18 high-probability fire pixels. Here `min_class` is a parameter, so the subscriber decides what counts as a fire — not the vendor. - provenance: S3 objects are immutable and carry an ETag, so a firing commits the exact bytes it was derived from, not a hash of rows seen at query time. What it does NOT claim: earlier detection. Same product, same scan, same pixels as FIRMS. The win is resolution, completeness, control and auditability.