GOES DCP Transmissions Containing Parity Errors

Calendar-based logs providing a historical record of GOES Data Collection Platforms (DCP) flagged with transmission errors.

Detection Overview

Raw data messages are flagged by the Wallops Island GOES DCS when transmission errors are identified. While the specific bit-level error is not identified, the DCS determined that at least one bit of data was corrupt.

A parity error indicator flag is set by the DCS system and encoded into the raw data message stream.

Example Log Entry

NESDISID DAY TIME (GMT) & CHANNEL
165E248E 31 0330- 77E 0730- 77E 1130- 77E
16F5E46E 31 0134- 29E 0406-127E 0534- 29E

HADS Decoder Handling

If the corrupt raw data message is still decodable, HADS acknowledges the parity flag and sets the SHEF encoder to append a Data Qualifier Code to each associated data value.

// SHEF Message with Parity Error Flag ('F')

.E SRGT2 011031 DH1045/HGIRG/DIN15/3.01F/3.01F/3.01F
.E1 3.01F/3.01F/3.01F/3.01F/3.01F

.E SRGT2 011031 DH1045/PCIRG/DIN15/15.18F/15.18F/15.18F
.E1 15.18F/15.18F/15.18F/15.18F/15.18F

Note: If raw messages are contaminated beyond a certain threshold, the HADS processor may fail to decode the transmission entirely.

Archive Access

Current System Status Return to Monthly Calendar Contact HADS Team

Tech Note

The 'F' qualifier in SHEF indicates that while data is present, the source transmission contained parity errors and should be vetted for quality before inclusion in critical models.