DJI Terra FAQ: Licenses, Mapping, LiDAR & Support

Start with the required outputs: maps, meshes, point clouds or Gaussian Splatting. Compare the current Standard and Flagship feature lists against that workflow. Send us your sensor, dataset size and deliverables if you need help selecting an edition.

DJI currently describes Standard and Flagship as perpetual licenses. Confirm the exact edition, online or offline mode and device entitlement on the quotation before ordering. A perpetual software entitlement should be distinguished from optional services or separately licensed products.

Yes. Tell us the edition or workflow you are considering, the required number of installations and your billing details. Our team can prepare a quotation and clarify the product designation before purchase. Use our contact page for project-specific requests.

A demonstration may show features from another edition or software release. Check the feature comparison for the particular output you need, especially Gaussian Splatting and advanced workflows. Do this before purchasing rather than assuming every visible tool belongs to every license.

Check DJI's current trial application and activation instructions. Trial availability and included functions can differ from a purchased entitlement. Prepare a representative dataset and use the evaluation to check output quality, processing requirements and the features relevant to your project.

Drone Emotions provides reseller guidance and a point of contact for software selection and project questions. DJI remains the product developer and publishes the official technical documentation. For a product defect or account-specific investigation, the appropriate DJI support channel may also be needed.

Choose the account your organization intends to manage and retain access to it. Confirm the account before redeeming a code, then follow DJI's activation and binding instructions. For a shared company workflow, agree internally who will manage the entitlement and device changes.

Activation establishes the software entitlement; binding associates the eligible license with a particular computer. These are different steps. If an activated license does not unlock a feature, inspect its device binding and confirm that the feature belongs to the selected entitlement.

An online license requires an internet connection for paid-feature permission checks. If the processing workstation must remain isolated, discuss the offline version before purchase. The two deployment modes have different activation procedures and should be selected to suit the environment.

The offline workflow uses a request generated for the processing computer and an exchanged license file. A connected computer can be used for the exchange while the modeling workstation stays offline. Follow the current instructions for the exact request and response files.

A move must follow the applicable unbinding or exchange process and the entitlement's device rules. Do not assume a replacement computer is automatically licensed. Check the current DJI terms for your license type, and contact us before retiring an inaccessible workstation.

Confirm the account, edition, license status, bound device and software version. For an online entitlement, also check connectivity. Record the exact message and the feature you are trying to use; that information helps distinguish a license issue from an unsupported workflow.

DJI Terra is designed for supported 64-bit Windows systems. Check the current hardware requirements before planning a workstation. A Mac should not be treated as a supported native Terra installation simply because it can run other mapping or visualization software.

Use DJI's current requirements as the starting point, then consider the actual project and output types. Installed RAM is different from RAM available to Terra. Leave capacity for the operating system and processing peaks, and check the GPU memory needed by the chosen workflow.

Check the current Terra configuration table before choosing hardware. DJI specifies NVIDIA-based requirements for relevant reconstruction workflows; similar advertised graphics performance does not establish compatibility. Match the supported GPU requirements and driver guidance to the installed Terra release.

More processing capacity can help complete larger jobs or reduce runtime. It does not fix blurred images, missing coverage or incorrect reference data. Assess survey accuracy through the capture, processing and validation workflow rather than through the price of the workstation.

Use the official DJI download resources linked from our Download page. Check the version and accompanying instructions before installation. Keep a record of the installer version used for important projects so later processing changes can be traced.

Read the release notes and preserve the source datasets, important project settings and deliverables. Test the updated version on a representative project before changing a production workflow. For cluster deployments, review the requirements for all participating computers as well.

The tutorial's aircraft is an example, not a compatibility guarantee for another camera or sensor. Check the supported input data and metadata requirements for your project type. A small representative test is useful before committing to a large survey workflow.

Prioritize sharp photographs, useful overlap and consistent coverage of the surfaces you need. Review the dataset for blur, severe exposure problems and missing views. A high image count alone does not establish that the subject has been captured well enough for reconstruction.

Downward-looking photographs may document roofs and terrain while leaving facades poorly observed. Plan additional viewpoints when the deliverable requires those surfaces. Select the capture pattern for the geometry of the subject and the supported flight workflow.

Keep an untouched copy of the original files and their folder structure. Work from a separate processing copy, and record the survey date, sensor and reference information. This makes it easier to diagnose missing inputs and to repeat processing later.

Recent DJI Terra releases include rolling shutter optimization for eligible imagery. Check the installed version and supported data before using it. The optimization does not replace appropriate capture planning or project-specific accuracy validation.

Recent versions include frame extraction from suitable video inputs, with metadata requirements that must be checked. Use it for an appropriate workflow and inspect coverage and image quality. A general video clip should not be assumed equivalent to a planned survey dataset.

A 2D orthomosaic is suited to plan-view documentation and GIS review. A 3D mesh represents surfaces in three dimensions and can show buildings or other structures. Choose the output according to the intended use and the data you have captured.

It establishes the relationship between photographs and the reconstructed scene. Review the calibrated images and available quality information before committing to heavier output generation. Problems at this stage can carry through into the finished map or model.

Where the project type and feature access support them, configure the required outputs in the reconstruction workflow. Check each deliverable independently: a satisfactory 3D view does not automatically demonstrate that the map has the requested coverage, resolution or reference system.

Choose it for the source data, requested detail and downstream use. A finer output pixel size can increase file size without adding information that was absent from capture. Compare the finished map against the delivery specification and suitable independent checks.

Start by examining the image coverage and the triangulation result. Surfaces that lack useful viewpoints or matching detail are difficult to reconstruct. Identify the affected region and review the inputs before repeatedly changing processing settings.

Agree on the required data type and format with the recipient. Preserve the coordinate reference, units and any companion files needed for the selected output. Open the exported deliverable in the receiving workflow before handing over the project.

POS refers to position and orientation information associated with the capture. Inspect the imported values and the reference system used by the dataset. Position metadata helps organize a georeferenced reconstruction, but its presence alone does not prove the final survey accuracy.

Check the input reference system, coordinate order, units and any imported position files. Then compare those settings with the output system and surveyed control. Diagnose the mismatch before applying an arbitrary offset to a deliverable intended for engineering or mapping.

They refer to different elevation references. Keep the height system of the capture, control and requested output consistent, or apply the appropriate transformation. A horizontal match does not mean the elevation reference is also correct.

Terra provides coordinate-system options including workflows for imported definitions and local transformations. Select the method that matches the project reference data. Document the definition and transformation parameters so the receiving team can interpret and reproduce the result.

Consider it when the project requires a defined transformation between reference systems and you have suitable common reference data. Establish and validate the parameters rather than using the tool as a general correction for an unexplained shift.

Recent Terra releases support local elevation-file workflows. Check the required file format, geographic coverage and relationship to the survey datum. Confirm the resulting elevations with suitable known points before applying the workflow to the full delivery.

Control points help constrain the reconstruction. Checkpoints are held aside to assess the result independently. Assign each point the intended role and retain the surveyed coordinates and reference information with the project.

Good capture positioning can strengthen the workflow, but the final deliverable still needs checks against the project requirements. Review positioning consistency, reconstruction quality and independent reference measurements rather than accepting a result solely because the flight reported RTK fixed.

GSD describes image sampling on the ground. Accuracy concerns agreement with a suitable reference. They are related considerations, but a fine pixel size should not be used as the sole evidence that a survey satisfies an accuracy requirement.

Use a distribution that represents the area and its variation in terrain, rather than concentrating every point in one convenient corner. The appropriate design depends on the site and survey specification. Record point quality and visibility as well as location.

Review the calibrated images and error information alongside the distribution of control and checks. Look for unusual patterns or excluded regions. Interpret the report in the context of the capture and project references; a single favorable metric is not a complete validation.

Accuracy depends on capture, sensor behavior, positioning, reference data, processing and validation. Define the required tolerance and assess the actual deliverable against independent evidence. Share the dataset conditions and specification if you need help planning that evaluation.

These are separate input and processing workflows. Photogrammetry uses image observations; a Zenmuse LiDAR project uses the files and positioning information required by that sensor. Choose the project type matching the survey data.

Retain the complete original survey folders and the files needed for the sensor workflow. Copy them intact before processing. If an import fails, compare the dataset with the sensor-specific data instructions before renaming, moving or deleting individual files.

No single answer applies to every sensor and output. DJI has introduced free point cloud processing for supported Zenmuse workflows, including L3 processing in Terra V5.1. Check the sensor, software version and requested output; additional capabilities can have separate license requirements.

Errors in these inputs can affect how survey strips align and how the point cloud is positioned. Follow the data collection and calibration procedure for the specific sensor. Inspect the processed result and relevant quality information before using it for measurements.

Ground classification helps separate terrain from other points, but the result must be reviewed in the actual scene. Vegetation, structures and incomplete ground observations can affect the output. Inspect representative areas before generating or accepting terrain deliverables.

Supported workflows can combine point cloud data with associated visible-light information. Check the required paired inputs and the available output options for the sensor and Terra release. Inspect both the geometry and the color result rather than treating appearance as an accuracy check.

Terra includes measurement tools for supported reconstructed data. Select the appropriate tool and reference surface for the task, then verify the data scale and quality. The reliability of the measurement depends on the underlying reconstruction and reference setup.

Define the stockpile boundary and base reference clearly. Inspect the reconstructed surfaces and whether important edges are missing. Record the method and validate it against the project tolerance so later comparisons use an equivalent basis.

A surface model can include buildings and vegetation. A terrain-focused elevation product depends on suitable ground observations and processing. Identify which product your recipient needs before using it for engineering heights, profiles or earthwork interpretation.

Check the elevation source, vertical reference and the terrain represented in the data. Select an interval suited to the project and inspect the resulting lines. Then verify units and coordinates in the receiving GIS or CAD application.

Detailed inspection remains a distinct documented workflow. Confirm the supported aircraft, export method and current requirements before planning execution. A model-based inspection project should be checked against the geometry and operating conditions of the actual site.

Use older lessons for their capture concepts, but confirm current function availability first. DJI identifies detailed inspection and agricultural applications as the remaining route-planning workflows in Terra 5.x. Select flight planning tools supported by the aircraft and controller you actually use.

It processes suitable multi-band survey data into outputs used for crop and vegetation assessment. Keep the sensor's bands and capture metadata organized, and select the processing workflow supported for that dataset.

NDVI is one indicator derived from spectral data. Interpret it with capture conditions, crop stage and field observations. Use differences as a prompt for investigation rather than assuming a single index explains every stress or management issue.

A usable observation needs the band information expected by the workflow. Missing or mismatched files can make a dataset incomplete. Preserve the original grouped files and check supported sensor data before attempting to reconstruct the survey.

Current documentation describes thermal reconstruction using compatible data. Check the supported camera and Terra version for your project. Thermal mapping has its own input and parameter requirements and should not be treated as an ordinary RGB orthomosaic.

The documented thermal workflow uses visible-light observations with matching thermal imagery. Preserve the paired inputs and check their completeness. Review the capture and import instructions before attempting to process a folder containing only an arbitrary collection of thermal pictures.

Review the material and environmental parameters required by the workflow, as well as the capture conditions. A visually striking heat map should not be accepted as a validated temperature analysis without checking those settings and the intended inspection method.

No. They are different representations. A mesh describes polygonal surfaces; Gaussian Splatting is used for detailed scene visualization through rendered Gaussian elements. Select the representation for the intended application and check whether downstream tools accept the output.

Visual realism and survey validation answer different questions. Assess the geometric and reference requirements of the actual project using suitable independent checks. Choose the deliverable needed for measurements as well as any representation needed for visualization.

Terra cluster reconstruction distributes supported processing work among participating computers on a local network. Plan shared data access and device resources for that deployment. It is different from assuming a hosted cloud service will process the project automatically.

Confirm compatible software, hardware and network access. Every participating device needs access to the paths required by the project. Check the current licensing conditions for the selected processing type before treating another computer as an eligible worker.

Recent Terra releases support Gaussian cluster workflows. Match the software version and supported input type to the project, and confirm licensing for each participating node. Older cluster guides can describe a different supported scope.

Choose a viewer that supports the representation and export format you have produced. Check the current DJI visualization resources for Gaussian workflows, or the requirements of your GIS and CAD tools for other outputs. Test a representative export before final delivery.

Record the exact error code, processing stage and input type. Check free disk space, available memory and the relevant driver guidance, then consult DJI's error reference. Keep the original project and files so the failure can be investigated consistently.

Compare the symptom with the release notes and known-issue guidance for that version. Test a small representative project and preserve the earlier outputs for comparison. Describe the change in behavior rather than assuming every processing difference is the same defect.

Provide the Terra version, sensor, computer configuration, input size, processing stage and requested outputs. Include the exact message or relevant screenshot and the available logs. Describe the steps that reproduce the issue and whether it affects one project or several.

Check that the application interprets the reference system and units correctly. Inspect coverage and compare suitable known locations or elevations. Retain the required companion files and confirm the receiving team can open the chosen format.

Start with the current DJI developer documentation for the specific format or integration. Confirm the expected data representation, supported platform and deployment requirements. A browser visualization integration and an automated processing workflow are different tasks and should be evaluated separately.

Use our contact page and describe the workflow you are trying to complete. For software selection, include your sensor and required deliverables. For a technical issue, add the version, settings and exact symptom so the team can identify the relevant processing stage.