General

I'd like the instructions/tips on the operation of InfiPoints.

Please utilize the following.

  • InfiPoints Operation Manual: [Help] tab > [Learn with Tutorial] from the ribbon menu
  • InfiPoints Academy (This site): [Help] tab > [How-to Video] from the ribbon menu
  • Help: [Help] tab > [Help Index] from the ribbon menu

 

I'd like to reduce the project folder size.

Run [Application Menu] > [Clean up Project] to reduce the project folder size by deleting unnecessary files and revisions.
Please refer to the InfiPoints Help or the InfiPoints Operation Manual for the details.

 

What is the scan index?

At Elysium, we call the point cloud structure (the positional relation from the scanner position) as "scan index". Scan index data is a prerequisite to auto-processing of point cloud data in InfiPoints.
Please refer to "What differentiates the point cloud data for the auto-processing in InfiPoints?" for the details.

 

What differentiates the point cloud data for auto-processing in InfiPoints?

It is whether to have the scan index data (the positional relation from the scanner position). Scan index data is a prerequisite to the following processes in InfiPoints.

  • [Regist Auto] in [Registration] panel
  • [Align All] in [Registration] panel
  • [Pre-process] tab > [Remove Noise] > [Remove Noise] from the ribbon menu
  • [Analysis] tab > [Detect Collision Mode] > [Enable Collision Detection] from the ribbon menu

Whether the scan index data is maintained depends on the laser scanner and the application used prior to the point cloud import to InfiPoints. There are also some cases in which the scan index data is not obtained in laser scanning.

The following is a list of point cloud file formats which will be imported to InfiPoints including the scan index data. (As of February 2024 Update)

  • E57 file (*.e57) (*1)
  • FLS file (*.fls, *.fws, *.lsproj)
  • ZFS file (*.zfs, *.zfprj)
  • PTX file (*.ptx)
  • DotProduct file (*.dp)
  • ReCap file (*.rcp, *.rcs) (*1)

(*1): These formats could be with or without the scan index information depending on the application used to pre-process the point cloud data prior to the data import to InfiPoints.

The plus symbol "+" on the icon for the point cloud files in [Tree (Overview)] panel indicates that the corresponding point cloud file has scan index data.

 

InfiPoints seems frozen while working in InfiPoints.

InfiPoints may seem frozen temporarily when working with "Autosave" option enabled. This could happen especially when the project with huge point cloud data. It may work to solve the problem to disable the autosave from [Application Menu] > [Option] > [System Settings] > [Miscellaneous] page > [Autosave].

 

"Failed to execute FlgConverter." error occurs.

If you are working on a computer from HP, it could be due to "HP Sure Sense", free antivirus software provided by HP. Please check for the security alerts of HP Sure Sense.

If you see an alert on the InfiPoints installation folder, confirm that the folder contains nothing suspicious or harmful, then set to exclude that folder in scanning.

 

InfiPoints abends when working on a specific project.

It could be due to the data corruption of the belonging point cloud file(s). If you are working on a copy of the original project, or a project which has been moved from its original location, the data corruption may have occurred in the project data set.

When working on a copy, confirm that the project file size of the copy is equivalent to that of the original. Also, use [Error Check] in "Property" window of each project revision to run the data corruption check on point cloud data.

 

Are there any additional pre-process steps when working on point cloud data from MMS or drones?

When working on point cloud data (LAS file <*.las> / text file <*.txt, *.asc, *.xyz>) from MMS or drones, and if you wish to run commands which require the scan index information (automatic scan registration, noise reduction, and/or primitive extraction), run [Pre-process] tab > [Point Cloud with Scan Index] > [Create] from the ribbon menu in advance to create point cloud data with scan index.

 

However, please note that the result point cloud data is not guaranteed to cover the entire source point cloud. For example, when obtaining point cloud data in laser scanning, all laser pulses hit the objects when facing a wall, but this does not apply when creating point cloud data with scan index in InfiPoints, and there may be some missing points when the specified resolution is too low for the source data.

Therefore, please be aware of the following when working on point cloud data with scan index created in InfiPoints.

  • Automatic registration with [Regist Auto] in [Registration] panel
    • This works basically okay.
      However, generally speaking, the accuracy tends to be lower with point cloud data obtained from MMS or drones compared to tripod scanners, which decreases the registration accuracy.
  • Noise reduction with [Pre-process] tab > [Remove Noise] > [Remove Noise] from the ribbon menu
    • The result may not be correct for the overwrapping noise, the front noise, etc., which the noise detection is conducted by comparing scans.
  • Primitive extraction with [Pre-process] tab > [Extract Planes and Pipes] from the ribbon menu(*1)
    • The missing points will affect the success rate in primitive extraction, but not badly.
      In post processes which use the extracted planes (dimensioning, modeling, texture creation, etc.), the planes extracted from the point cloud data created with [Create Point Cloud with Scan Index] command will work equivalent to that from PTX data, etc.

      (*1): For this command, you do not need to run [Create Point Cloud with Scan Index] in advance. Check "Keep the created point cloud with scan index" option in the option settings dialog.
  • Collision detection with [Analysis] tab > [Detect Collision Mode] > [Enable Collision Detection] from the ribbon menu
    • The missing points may affect the accuracy.

 

InfiPoints freezes after the point cloud import, or while saving with a revision comment.

This may be caused by the issue which was fixed in InfiPoints October 2020 Update (7.0.1).

If you are using InfiPoints in Ver.7.0 or earlier, you may experience this due to Windows Update, etc. So, please confirm whether this occurs in the latest version. To view the version information, select [Help] tab > [Version Information] > [Version Information] from the ribbon menu.