Getting Started with Dronetag Integration
Dronetag provides several integration options to allow access to data from our devices, focusing primarily on Remote ID data. This guide will help you choose the most suitable method for integrating Dronetag into your systems, whether you are working with UTM platforms or building custom solutions.
I Want to Use Existing Integrations
If you prefer to work with established platforms, Dronetag supports several ready-made integrations:
The integrations currently implemented by Dronetag include:
| Integration | What it is used for | Access method |
|---|---|---|
| Aloft | Sharing Dronetag telemetry with Aloft services. | Dronetag App integration |
| SafeSky | Making Dronetag flights visible in SafeSky. | Dronetag App integration or Data Push |
| InterUSS | Exchanging flight data with U-Space / UTM systems through InterUSS services. | Platform integration |
| TAK Server | Streaming Remote ID data to TAK-compatible systems. | Data Push using Cursor on Target (CoT) XML |
| SAPIENT | Sending Remote ID telemetry as SAPIENT detection reports. | Data Push |
Data Push can also deliver Dronetag's own formats, including DUMP JSON, DUMP JSON Typed, and Dronetag Legacy JSON. These are useful when you are building a custom integration instead of connecting to one of the platforms listed above. See Protocols and Formats for recommended combinations.
I Want to Build My Own Integration
For custom solutions or new integrations, we provide multiple options for building the integrations:
If you're unsure which integration method is right for you, check out our guide on Choosing the Right Integration Method for more information and guidance.