Projection FAQ

1.[Error]: "Unable to open this project as it was made with a newer version of the LiDAR360MLS."

  • Cause: The project file was created in a higher version of the software, and the current software version is lower, which does not support opening it.

  • Solution: Use a higher version of the software to open it.

2.[Error]: "Failed to upgrade project file ..."

  • Cause: Upgrading the low-version project file failed, possibly due to damage to the project file or database.

  • Solution: Analyze the specific project file.

3.[Error[: "An exception was thrown while loading..."

  • Cause: Encoding error in the project file (LIMMP), default encoding is GBK. If other encodings were used to store Chinese characters, an exception will be thrown when reading the project file.

  • Solution: Use a third-party tool like Notepad to modify the file encoding.

4.[Error]: "Failed to load project file path from ..."

  • Cause: Similar to the above, encoding errors cause exceptions.

  • Solution: Use a third-party tool like Notepad to modify the file encoding.

5.[Error]: "Failed to save project file ..."

  • Cause: The project file (.LiMMP/.gpkg) has read-only permissions or is being used by another application.

  • Solution: Right-click on the .LiMMP and .gpkg files, check if the "Read-only" checkbox is selected; if it is, uncheck it and try again; if not, check if the project file is being used by another application; if so, close the application and try again.

6.[Error]: "Unable to change file permissions to writable..."

  • Cause: When opening the project, the system automatically upgrades the permissions of the read-only project file (.LiMMP/.gpkg) to writable. If the file is being used, the upgrade will fail.

  • Solution: Close the application using the project file.

7.[Error]: "Failed to open layer...|..."

  • Cause: Failure to open the vector layer (followed by the corresponding layer name after “|”), two possibilities: one is that the gpkg file path has changed, making it unable to find the file; the other is that the corresponding table does not exist.
  • Solution: For the first case, check if the gpkg path exists; if not, find the corresponding gpkg and place it in the correct path; for the second case, analyze the specific data.

8.[Error] "Failed to copy <InstallDir>/@default_en.gpkg to /.gpkg"

  • Cause: When creating a new project, the software attempts to copy the default template file to the user-defined project folder but fails.

    There are three possible reasons:

    1. The template file @default_zh.gpkg is missing from the path.
    2. The user-specified project directory does not exist or the path is incorrect.
    3. Insufficient remaining space on the target disk.
  • Solutions:

    1. For a missing template file: Ensure that the software has been correctly installed. If the issue persists, it is recommended to reinstall the software to restore any missing template files.
    2. For an invalid target path: Check and confirm that the project path you entered is correct. If the path is invalid, select a valid directory as the new project save location.
    3. For insufficient disk space: Free up disk space or choose another drive with sufficient space to save the new project.

results matching ""

    No results matching ""