FORMAT: XML
PROTOCOL: COT
STATUS: DESIGNING
CUSTOM COT MESSAGES

Specialized Data Sharing Protocols

Design and implement custom Cursor-on-Target (COT) message types for specialized data sharing needs. Enable unique operational capabilities with tailored data formats that extend TAK's native functionality.

50+
Custom Types
100%
Compatible
Standards
Based
UNDERSTANDING COT

What is COT?

Cursor-on-Target is the messaging protocol that powers the TAK ecosystem

Universal Protocol

COT (Cursor-on-Target) is an XML-based messaging protocol used throughout the TAK ecosystem to share tactical information. It provides a standardized way to communicate position data, status updates, and operational information between TAK clients and servers.

Extensible Design

While COT defines standard message types (points, tracks, etc.), the protocol is designed to be extensible. Custom message types can be created to support specialized operational requirements while maintaining compatibility with standard TAK clients.

Interoperability

COT messages ensure interoperability between different TAK clients (ATAK, WinTAK, iTAK, WebTAK) and TAK Server, enabling seamless data sharing across platforms and organizations.

COT STRUCTURE

Message Anatomy

Understanding the components of a COT message

01

Event Attributes

Core metadata including version, type, UID, timestamps, and source method.

02

Point Data

Geographic coordinates (lat/lon), altitude (HAE), and accuracy estimates (CE/LE).

03

Detail Section

Standard elements like contact info, remarks, and status indicators.

04

Custom Extensions

Proprietary data structures for specialized operational requirements.

example_cot_message.xml 
<!-- Standard COT Message Structure -->
<event version="2.0" type="a-f-G-U-C"
      uid="ASSET-001" time="2026-01-15T10:30:00Z"
      start="2026-01-15T10:30:00Z"
      stale="2026-01-15T10:35:00Z"
      how="h-e">
  
  <point lat="39.542" lon="-80.781"
          hae="45.0" ce="10.0"
          le="20.0"/>
  
  <detail>
    <contact callsign="ALPHA-1"/>
    <remarks>Status update</remarks>
    
    <!-- Custom extensions go here -->
    <custom_data type="sensor_reading">
      <temperature>72.5</temperature>
      <humidity>45.2</humidity>
    </custom_data>
  </detail>
</event>
CUSTOM TYPES

What We Build

Specialized COT message types for unique operational needs

Sensor Data Messages

Custom COT types for transmitting sensor readings, telemetry, and environmental data with standardized formatting.

Telemetry Data Sensor Readings Status Updates
Example: Weather station readings, drone telemetry, vehicle diagnostics

Mission Planning Messages

Structured messages for mission plans, checkpoints, resource allocation, and task assignments.

Mission Plans Checkpoints Task Lists
Example: Multi-phase operation plans, checkpoint synchronization, resource requests

Document & Report Messages

Structured formats for sharing reports, intelligence summaries, and operational documentation.

Reports Intelligence Documentation
Example: Situation reports, intelligence briefs, after-action reviews

Alert & Notification Messages

Priority alert messages with escalation levels, acknowledgment requirements, and response tracking.

Alerts Notifications Escalation
Example: Emergency alerts, threat warnings, system status notifications

Analytics & Metrics Messages

Data aggregation messages for sharing analytics, performance metrics, and operational statistics.

Analytics Metrics Statistics
Example: Performance dashboards, resource utilization, trend analysis

Integration Bridge Messages

Message types that bridge TAK with external systems, translating proprietary formats to COT.

System Integration Format Translation Protocol Bridge
Example: Legacy system integration, third-party API translation, protocol conversion
DEVELOPMENT PROCESS

Design & Implementation

Our approach to custom COT message development

Requirements Analysis

Identify the specific data elements, relationships, and operational workflows that need to be represented in COT format.

  • Data requirements gathering
  • Use case definition
  • Compatibility analysis

Schema Design

Design XML schema for custom message types, ensuring proper structure, validation, and extensibility.

  • XML schema definition
  • Data type specification
  • Validation rules

Implementation

Develop message generators, parsers, and validators for the custom COT types.

  • Message generation code
  • Parser implementation
  • Validation logic

Testing & Validation

Comprehensive testing to ensure compatibility with TAK clients and proper data handling.

  • Unit testing
  • Integration testing
  • Client compatibility

Documentation

Create comprehensive documentation including schema definitions, usage examples, and integration guides.

  • Schema documentation
  • Usage examples
  • Integration guides

Deployment & Support

Deploy custom message types and provide ongoing support for updates and enhancements.

  • Production deployment
  • Training materials
  • Ongoing support
STANDARDS COMPLIANCE

Maintaining Compatibility

Ensuring custom COT messages work seamlessly with the TAK ecosystem

TAK Compatibility

All custom message types are designed to be compatible with standard TAK clients. Unknown elements are gracefully ignored, ensuring no disruption to existing systems.

Versioning Strategy

Proper versioning ensures backward compatibility and smooth migration paths as message types evolve.

Security Considerations

Custom messages follow TAK security best practices, including proper encryption and authentication handling.

Schema Validation

XML schema validation ensures message integrity and proper structure for reliable parsing and processing.

EXAMPLE IMPLEMENTATIONS

Real-World Examples

Custom COT messages in action

Sensor Integration

Weather Station COT Messages

Custom COT type for transmitting weather station data including temperature, humidity, wind speed, and barometric pressure. Messages update every 5 minutes and include location metadata for mapping.

XML Schema MQTT Bridge TAK Server
Mission Planning

Multi-Phase Operation Messages

Structured COT messages for complex multi-phase operations with synchronized checkpoints, resource requirements, and timeline coordination across multiple teams.

Custom Schema ATAK Plugin Coordination
Legacy Integration

SCADA System Bridge

Custom COT messages that translate proprietary SCADA protocol data into TAK-compatible format, enabling industrial monitoring systems to integrate with tactical networks.

Protocol Translation Modbus Integration Real-Time Bridge

Need Custom COT Messages?

Whether you need specialized data formats, legacy system integration, or unique operational messaging, we can design and implement custom COT message types that extend TAK's capabilities.

START A PROJECT LEARN MORE ABOUT US