Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
type identifier for the BinaryPayload. Use this type to determine decoding strategy
version identifier for the binary message
binary message payload data
timestamp when ingested
unique id for this BinaryPayload
All items are required unless otherwise noted! "required" means if they are missing on send, the conversion to the message format will be rejected and fall back to opaque XML representation
Used in:
Endpoint is optional; if missing/empty do not populate.
endpoint=
callsign=
A note about timestamps: Uses "timeMs" units, which is number of milliseconds since 1970-01-01 00:00:00 UTC All items are required unless otherwise noted! "required" means if they are missing in the XML during outbound conversion to protobuf, the message will be rejected
<event>
Used in:
<event type="x">
optional, but see below!
field was optional in early cot implementations but now required in MIL-STD-6090. This message definition treats as "optional" due to legacy definition/use, but updated/new clients should be populating on all outgoing message and should treat any missing/empty value as CoT value "Undefined". A CoT/XML value of "Undefined" for this field should be conveyed in this message by omitting this value for compactness
optional
optional
optional
optional
<event uid="x">
<event time="x"> converted to timeMs
<event start="x"> converted to timeMs
<event stale="x"> converted to timeMs
<event how="x">
<point>
<point lat="x">
<point lon="x">
<point hae="x"> use 999999 for unknown
<point ce="x"> use 999999 for unknown
<point ce="x"> use 999999 for unknown
comprises children of <detail> This is optional - if omitted, then the cot message had no data under <detail>
Used in:
<contact>
<__group>
<precisionlocation>
<status>
<takv>
<track>
All items are required unless otherwise noted! "required" means if they are missing on send, the conversion to the message format will be rejected and fall back to opaque XML representation
Used in:
name=
role=
Container for TakMessage and metadata, such as groups
optional sequence of binary payloads
Container for MissionAnnouncement and metadata
All items are required unless otherwise noted! "required" means if they are missing on send, the conversion to the message format will be rejected and fall back to opaque XML representation
Used in:
geopointsrc=
altsrc=
All items are required unless otherwise noted! "required" means if they are missing on send, the conversion to the message format will be rejected and fall back to opaque XML representation
endpoint=
callsign=
All items are required unless otherwise noted! "required" means if they are missing on send, the conversion to the message format will be rejected and fall back to opaque XML representation
Used in:
battery=
TAK Protocol control message This specifies to a recipient what versions of protocol elements this sender supports during decoding.
Used in:
Lowest TAK protocol version supported If not filled in (reads as 0), version 1 is assumed
Highest TAK protocol version supported If not filled in (reads as 0), version 1 is assumed
Top level message sent for TAK Messaging Protocol Version 1.
Used in:
,Optional - if omitted, continue using last reported control information
Optional - if omitted, no event data in this message
All items are required unless otherwise noted! "required" means if they are missing on send, the conversion to the message format will be rejected and fall back to opaque XML representation
Used in:
device=
platform=
os=
version=
All items are required unless otherwise noted! "required" means if they are missing on send, the conversion to the message format will be rejected and fall back to opaque XML representation
Used in:
speed=
course=