Frequently Asked Questions for LiMapper

Installation and Licensing

What are the hardware requirements for installation of LiMapper?

  • CPU: Intel Core i5 or equivalent (minimum), Intel Core i7 (recommended).

  • GPU: NVIDIA GTX750 Ti or equivalent (minimum), NVIDIA GTX1060 or better (recommended). CUDA, SM20 or better. At least 2 GB of memory.

  • DISK: 1 GB free disk space for installation; the space required for processing depends on the data size. 500 GB of free disk space is recommended.

  • RAM: 16 GB (minimum), 32 GB or more (recommended).

What operating systems are supported?

  • Windows 7: Windows 7 SP1, with Windows Update KB2999226 required.

  • Windows 8: Windows 8.1, with Windows Updates KB2919355 and KB2919442 required.

  • Windows Server 2012 RC2: Windows Updates KB2919355 and KB2919442 are required.

  • Windows 10: No additional requirements.

What if the hardware & system requirements are satisfied but the software still does not work properly?

  • Install Visual C++ Redistributable for Visual Studio 2015 x64. If this fails, please update your operating system and try again.
  • If the problem persists, please send an email with a description of the problem to and we will contact you to troubleshoot the problem as soon as possible.

How should the error "No CUDA device is found" that occurs when launching LiMapper be resolved?

  • Please update the drivers of your CUDA devices. If no CUDA devices are available on your machine, please ignore the error message.

    Note: Use of Compute Unified Device Architecture (CUDA) devices increases the software efficiency.

How can I check to see if CUDA devices are available on a computer with LiMapper installed?

  • Launch LiMapper, click File > Settings, and the recognized CUDA device(s) will then be listed.

What can I do if LiMapper does not recognize a computer’s NVIDIA graphics card?

  • Please download the latest version of the driver from the official NVIDIA website and then update the driver.

Tips and Tricks

How do I change the menu language?

  • Click File > Settings > Language, and then change the language. Any language change will require a restart to become effective.

How can I pause LiMapper while it is carrying out data processing operations?

  • Click Stop Process in the Process ribbon to pause processing. You will then need to wait until all the multi-thread and GPU calculation tasks have been terminated by LiMapper before restarting paused processing operations. For more information on how to resume a paused process please refer to “How do I resume the process from the break point?” in this FAQ document.

Can I resume a process from a LiMapper break point?

Yes; if the system crashes, the computer shuts off unexpectedly, or you choose to pause a processing operation, you can resume the operation(s) from a LiMapper break point. Resumption of processing tasks from the break point is supported in the following processes:

  • Align Photo

  • Build Dense Cloud

  • Build Orthomosaic

How do I resume an interrupted/paused process from a LiMapper break point?

  • Click Start Process in the Process ribbon to resume from the break point.

What if the deviations between the initial camera positions and their positions after photo alignment are so large that objects in the scene have been distorted?

  • Please evaluate the accuracy of the initial camera position information (the coordinates are embedded in the photo EXIF or imported POS files), and adjust POS Accuracy in LiMapper to match the accuracy before running the process. Higher accuracy in the initial position will lead to smaller discrepancies between the initial position and the adjusted position after photo alignment.

Can I generate orthomosaic imagery using an external DEM/DSM, such as a DEM/DSM generated from the LiDAR point cloud, and if so, how?

  • Yes. Before processing the Mosaic, click Configure in the Process ribbon. Under the Build Orthomosaic tab, select either the Pixel-level mosaic based on self-defined surface mode or the Object-level mosaic based on self-defined surface mode and enter the external DEM/DSM.


Why does Create/Save Project fail?

  • Please ensure that you have both read and write access to the project folder. Do not save your project within the system’s protected paths, such as "C:/Program Files", "C:/Users", or "C:/Windows".

  • Please ensure that sufficient storage space is available in the project drive. The generated products such as dense cloud and orthomosaic imagery are usually large datasets that require large amounts of storage space.

  • If the problem persists, please send an email with a description of the problem to

Why do different data crash frequently on one computer but work correctly on other computers?

  • Check to ensure that the current Windows user has read and write access to the project folder.

  • If the current project folder is located on a cloud drive, change the project folder location to a local drive and try again.

In what cases would a project fail during processing?

  • The case where the scene to be reconstructed does not have sufficient texture features. Some examples of scenes that lack texture features include bodies of water and snow-covered landscapes.

  • The case where there is not enough overlap area between the photographs. The minimum required flight front overlap is 60% and the minimum required flight side overlap is 30%.

    Note: The changes of terrains will influence the overlap rate. Generally, when flight height remains unchanged, the overlap will be decreased as the scanned terrain rises. . In these situations, users should increase the front and side overlapping ratios or use a terrain-following flight mode during data collection.

What should I do if a Blue Screen of Death (BSOD) occurs during building of a dense cloud or building of an Orthomosaic?

  • If your CPU is the Intel I7-7820X, the problem is likely to be caused by a driver bug. The solution is to switch “CPU Core Usage” to "Auto" rather than "Sync All Cores" or "By Core Usage" in the BIOS.
  • If the problem persists, please send an email with a description of the problem to

results matching ""

    No results matching ""