Package-level declarations
Types
A CoT message received from a connected TAK client, paired with the client's identity.
Publishes Meshtastic node-database entries to connected TAK clients as CoT contacts.
Converts route CoT XML (b-m-r) into ATAK-importable KML data packages.
Access to the local TAK server's per-install certificates.
The pieces of the per-install TAK PKI that go into the exported ATAK data package.
Generates TAK data packages (.zip) compatible with ATAK/iTAK/WinTAK import.
Bidirectional bridge between the local TAK server and the Meshtastic mesh network.
Debug-only test runner that sends the SDK's CoT XML test fixtures through the REAL TAK mesh pipeline: strip → parse → dispatch, via TAKMeshIntegration.sendCoTToMeshForTest. Each fixture is run through BOTH the v2 (firmware >= 2.8.0) and v1 (legacy) dispatch paths so the self-test's pass/fail rate reflects what a real connected radio would actually do on either firmware generation, rather than always exercising the v2 pipeline regardless of the connected radio's firmware — see TAKMeshIntegration.useTakV2.
Legacy v1 CoT <-> TAKPacket conversion for firmware <= 2.7.x.
Conversion between CoTMessage and TAKPacketV2 (v2 wire protocol).
Which outbound TAK protocol a TakTestResult was dispatched through. See TAKMeshIntegration.
Result of sending a single test fixture through the TAK mesh pipeline.
Functions
Platform factory for TAKServer. The JVM/Android implementation lives in jvmAndroidMain and uses JSSE (SSLServerSocket) with the per-install identity kept in certificateStore.
actual factory for the KMP expect fun createTAKServer declared in commonMain. Both the Desktop JVM target and the Android target share this source set, so both run the same JSSE-based TLS listener backed by the per-install PKI kept in certificateStore.
Serialize this CoTMessage to a single <event> XML element suitable for the CoT streaming TCP protocol used by ATAK / iTAK / WinTAK clients.