Custom Flight Areas
In addition to the pre-configured GEO-Zone defined globally by DJI FlySafe, users can configure geo-fences or no-fly zones on the DJI Dock to meet any specific operational requirements.
Services
/dji/areas/import
| Description | Store custom flight areas description in cloud storage. |
|---|---|
| Request | Custom Flight Areas description |
| Response | None |
| DJI Bindings | N/A |
/dji/areas/export
| Description | Get custom flight areas description currently stored in cloud storage. |
|---|---|
| Request | None |
| Response | Custom Flight Areas description |
| DJI Bindings | N/A |
/dji/areas/deploy
| Description | Force DJI Dock to sync the custom flight areas descriptions from cloud on the aircraft. This call is non-blocking, sync progress is reported on the progress subtopic. |
|---|---|
| Request | None |
| Response | None |
| DJI Bindings | Service flight_areas_update |
Telemetry
/dji/areas/alarms
| Description | Array of active custom flight areas |
|---|---|
| Push | Every 2s when localized |
| Type | []AreaAlarm |
| DJI Bindings | Event flight_areas_drone_location |
/dji/areas/deploy/progress
| Description | Progress update on areas file syncing from cloud to aircraft |
|---|---|
| Push | Every 2s when syncing |
| Type | []DeployProgress |
| DJI Bindings | Event flight_areas_sync_progress |
Schemas
AreaAlarm
| Key | Type | Description |
|---|---|---|
| areaId | string | Unique ID for the custom flight area as defined in the JSON description file. |
| distance | float | Distance between the aircraft and the boundary of the area in m. |
| isInside | bool | True if the aircraft is inside the area. False otherwise. |
Sample
{
"areaId": "nfz-002",
"distance": 62.12,
"isInside": false,
}
DeployProgress
| Key | Type | Description |
|---|---|---|
| status | string | Status of the deploy process. Possible value are "unknown", "deploy failed", "switch failed", "delayed", "in progress" and "completed". |
| reason | string | Reason for the current deploy process status. |
Sample
{
"status": "deploy failed",
"reason": "failed to get file information on the aircraft side"
}