Authenticate and subscribe
Use TAK Server REST authentication, retrieve selected server context and receive CoT traffic over a secured WebSocket endpoint configured for the deployment.
Team collaboration
From CoT event
to shared 3D context.
Connect TAK Server workflows to a Unity geospatial experience. Route Cursor on Target events, persist mission context locally and give tasks, chat, files, sensor data and video a place on the map.
REST authenticationTAK Server API pathway
CoT over WebSocketEvent delivery to Unity
Local persistenceDuckDB mission repositories
Mission contextChat, tasks, files and notifications
Process Cursor on Target
Parse CoT XML, route event types, marshal updates safely to the Unity main thread and maintain heartbeat and reconnect behavior.
Keep mission context local
Store CoT events, chat messages, tasks, files and notifications in a local DuckDB database under application-controlled storage.
Turn events into scene context
Use pooled markers, team models, level-of-detail handling and interaction components to carry event state into the geospatial scene.
Integration boundary: real-server, certificate, reconnect, load and target-hardware matrices remain part of deployment acceptance. The current TAK path expects CoT over WebSocket at the configured Marti subscription endpoint.
Team operations
More than markers on a map.
Carry the objects teams use to coordinate into the same spatial workflow.
Team awareness
Represent team members, callsigns, affiliation, position, altitude, accuracy and selected device status from CoT event context.
Tasks and notifications
Create, update, complete and synchronize task state, including subtasks, assignments, due dates and mission notifications.
Chat and mission packages
Carry chat, data packages, attached files and extracted mission content into persistent, location-aware application workflows.
Video capabilities
Video is most useful when it has context.
GeoVerse3D can associate video and file metadata with mission objects today, while customer delivery profiles can add the live-feed behavior appropriate to the selected devices, servers and security controls.
| Capability | Operator experience | Delivery boundary |
|---|---|---|
| Video/file attachments Current model path | Attach video references and related files to spatial tags, tasks or mission context so media can be discovered from the scene. | Repository code represents video as file and attachment context; it does not claim built-in live decoding or analytics. |
| Geospatial video view Delivery profile | Display operator-selected feeds or clips alongside map position, sensor identity, task and event history. | Feed protocol, player, latency, metadata and hardware decoding are selected and validated per deployment. |
| TAK video workflow Integration profile | Carry approved video references through the TAK-connected mission workflow and open them in the appropriate role-based interface. | Server interoperability, permissions, link lifetime, storage and bandwidth policy require live-environment acceptance. |
| Analytics + computer vision Optional extension | Place detections or observations back into the spatial context when a separate analytics pipeline is part of the solution. | No live-video analytics capability is claimed for the current Unity baseline. |
Secure by configuration. Proven by testing.
Production TAK delivery should validate TLS and private-CA trust, credential storage, server-version compatibility, endpoint policy, failure recovery and target-device behavior. GeoVerse3D provides the integration foundation; deployment acceptance proves the mission configuration.
Bring your TAK
environment.
We’ll map your server path, CoT event set, mission objects, video context and target-device matrix into an integration test.
Plan a TAK evaluation