Message Coverage
Data Push uses two separate filters before sending data to your target:
- The Data Source setting controls which messages are eligible for the distribution target.
- The Output Format setting controls which eligible message types can be represented and sent.
For example, a target using the My account data source can receive only messages accessible to that account. If the same target uses a partner-specific UAV-position format, only eligible aircraft position messages are sent because that format cannot represent operator position, system telemetry, or operation updates.
Message Types by Output Format
| Data type | DUMP JSON / DUMP JSON Typed | Cursor on Target XML | SAPIENT | Partner-specific UAV-position formats |
|---|---|---|---|---|
| UA telemetry | Sent as tele-ua | Sent as aircraft CoT events | Sent as SAPIENT detections | Sent when the format can represent the position message |
| Operator position telemetry | Sent as tele-operator | Sent as operator CoT events | Not sent | Not sent |
| System telemetry | Sent as tele-system by default | Sent as system CoT events | Not sent | Not sent |
| Operation updates | Sent as operation-update | Not sent | Not sent | Not sent |
| ADS-B, UAT, FLARM, and OGN traffic | Not sent | Not sent | Not sent | Not sent |
DUMP JSON and DUMP JSON Typed are the best choices when your target needs the complete Data Push message set.
System telemetry can be disabled for a target with the distribute_system_telemetry connection setting.