GnssInterferencePayload
| Source file | schemas/payload_gnss_interference.schema.json |
$id | urn:synapsecommand:cdm:3.0.0:payload_gnss_interference |
| CDM schema version | 3.0.0 |
| SHA-256 of source | 72b6a565fe0c566b3c61bd7e6ce012e01d7a8bcde49881a12cc707ac5249ef16 |
The typed payload for EventType.GNSS_INTERFERENCE.
extra="allow" here, unlike the canonical objects: this model's job is to give the fields
we DO understand a checked shape while letting a source's extra fields ride along in the
same dict. Forbidding extras here would force an adapter to split one payload across two
places, and the never-drop rule would be satisfied by the letter while the meaning
scattered.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
frequency_band | string | yes | GNSS band, e.g. L1, L2, L5, E1, B1 — the source's own name. (min length 1) |
interference_type | InterferenceType | yes | |
signal_strength_dbm | number | null | no | Received power in dBm, negative in practice. None = not reported; the unit is in the field name because a bare 'signal_strength' has been read as dBW, dBm and a 0-100 bar by three different consumers. Default null. |
Referenced definitions
Every $ref on this page resolves to one of these, inlined here so the page is a
complete reference and not a starting point for chasing pointers.
InterferenceType
JAMMING denies, SPOOFING deceives, and the difference decides the response.
Kept distinct from UNKNOWN deliberately: a receiver that has lost lock knows it is being jammed, whereas a receiver reporting a plausible but false position does not know it is being spoofed. An adapter that cannot tell says UNKNOWN rather than guessing JAMMING.
Closed vocabulary — a value outside this list is invalid, and UNKNOWN is a
member rather than a null wherever the enum has one.
| Value |
|---|
JAMMING |
SPOOFING |
UNKNOWN |