DJI MISSION FILES · MEDIA · TELEMETRY

Bring DJI missions and media into the workflow.

Connect DJI mission planning and collected media to Drone Scout through documented file and telemetry workflows. Export WPML/KMZ missions, review DJI video and flight logs, and prepare supported imagery for geospatial work.

WPML / KMZDJI → MISBFlight logsSDK scope

FEATURE / 18

DJI workflows & SDK scope

  • WPML / KMZ mission export
  • Windows controller-transfer API
  • DJI video and telemetry
  • Flight-log replay

Platform overview →

CAPABILITIES

Useful integration starts with the supported handoff.

The current implementation connects mission files, collected media and metadata. Device, controller and source compatibility should be checked for each workflow.

WPML / KMZ mission export

Export planned routes into the documented waypoint-file structure for review and loading through a compatible DJI controller workflow.

Windows controller-transfer API

A Windows USB/MTP transfer API exists for an accessible controller waypoint folder. Controller acceptance still requires verification, and the map-panel transfer button is not connected to that API.

DJI video and telemetry

Convert supported DJI video with SRT/CSV sidecars toward a MISB/KLV workflow, preserving the distinction between available metadata and inferred geographic context.

Flight-log replay

Use supported DJI DatCon CSV logs for time-based trajectory review, bringing flight context into post-collection analysis.

Imagery and inspection inputs

Use supported DJI EXIF/XMP imagery and radiometric sources in the relevant oriented-imagery, processing and thermal workflows.

Current DJI SDK boundary

The source audit found no implemented DJI Mobile SDK, Onboard SDK or Cloud API flight-control adapter. A future SDK integration needs a defined API family, devices and supported functions.

THE WORKFLOW

A clear path through the work.

Prepare

01

Create a mission plan or gather source media.

Handoff

02

Export supported files or bind telemetry.

Review

03

Confirm controller or source-data compatibility.

Use

04

Continue into processing, FMV or project review.

THE RESULT

Connect DJI collections to the wider project.

Bring mission plans, camera collections and flight context into the same processing and review conversation. Select the supported file path today and define any additional SDK work against the actual aircraft and controller requirements.

WHAT YOUR TEAM TAKES FORWARD

  • Mission-file exchange and controller review
  • DJI media, telemetry and trajectory workflows
  • A clearly defined starting point for future SDK integration

AVAILABILITY & WORKFLOW SCOPE

File-format support is not direct DJI SDK flight control. The inspected code has no shipped MSDK/OSDK/Cloud API control adapter; the separate optional thermal SDK plugin remains deferred. Compatibility is not universal across DJI aircraft, controller apps or firmware.

QUESTIONS, ANSWERED

A few useful details.

Is there a direct DJI SDK flight-control integration today?

The current code and documentation audit did not find one. Implemented support covers mission files and media/telemetry workflows, which are described on this page.

Does Send to RC provide a finished one-click workflow?

No. The Windows transfer API exists, but the audited map-panel button is not wired to it. A successful file transfer also does not prove controller acceptance.

Can you scope a DJI SDK integration?

Use the workflow discussion to identify the SDK/API family, aircraft, controller, firmware and functions required. This is integration scoping, not a claim that the adapter is already delivered.

BRING YOUR NEXT PROJECT

Let’s connect your workflow.

Start with a collection, an operational challenge or a deliverable. We’ll help map the path from capture to a useful result.