LAStools and laslook are best installed via the default installer. This blog entry shows additional installation options. The goal of all installation methods is to copy files from the installation media to the target location. It is always possible to complete this task through a manual copy or a batch script.
- LAStools is a collection of program files. All files should be in the same installation directory (with structured subdirectories).
- laslook is a windows program for executing LAStools. It needs to know where your LAStools files are stored. Some additional files are required.
LAStools file structure
LAStools is typically installed in “c:\lastools“, but can also be installed in other directories. The table below shows the data within a LAStools installation:
Directory/Files | Description | |
.\*.exe | LAStool executeable; e.g. las2las.exe | |
.\*64.exe | 64 bit version of a LAStool executeable; e.g. las2las64.exe | |
.\serf\geo | Files to do a non-standard georeferencing or transformation | |
.\serf\blast | Files needed by the BLAST extension | |
.\serf\potree16 | potree installation; required for laspublish; version 16 | |
.\serf\potree18 | potree installation; required for laspublish; version 18 |
If there was a previous installation and the LAStools directory is already set this directory will be used. This is checked by the file „laslook.ini“ in the User files (UF) directory. Within the section [frSettings] the Key „edLasToolDir“ will hold this information.
Second we look for the default directory „c:\lastools\bin“: If this directory exists this will be taken.
Third the optional start argument „/lastools=…“ will be checked. If a path is given we use this directory.
If we do not get the path information so far a user dialog will appear where the user can enter the desired installation directory of LAStools.
laslook file structure
laslook has two targets for installation files: program files (PF) and user files (UF). By default, program files are located in the program files directory and user files are located in the public user directory. During setup, the program file directory can be set individually, and the user directory can be set from public to private. If an installation is carried out without admin rights, this can be done as a private installation.
File category | Target for public installation (Default) | Target for private installation |
Program files (PF) | c:\program files\rapidlasso\laslook | C:\Users\[user]\AppData\Local\Programs\rapidlasso\lasgui |
User files (UF) | C:\Users\Public\Documents\rapidlasso\laslook | C:\Users\[user]\Documents\rapidlasso\laslook |
For special installations, such as installation on a USB stick, the files can be also referenced elsewhere. All user files are first searched at location (PF). If they are not found, they are expected at (UF). This enables an “all-in-one-directory“ installation, for example on a USB stick. If a user file is stored in (PF,) the directory must be writable. Program settings can be adjusted via the user setup dialog. The user settings are saved in a file “laslook.ini“ under (UF). The location of the program databases (user database and program database) is also stored in “laslook.ini“. Below are the files of a full laslook installation and their default location:
Filename | Target | Notes |
laslook.exe | PF | laslook application |
laslook.lng | PF | language file |
markdown.jhl | PF | format settings for markdown files (e.g. READMES) |
lastoolsinfo.jhl | PF | format settings for file information (lasinfo output) |
laslook.vsf | PF | gui design file |
sqlite3.dll | PF | database driver |
LASzip64.dll | PF | LAS reader/writer |
libeay32.dll | PF | open SSL connection |
openssl.exe | PF | open SSL connection |
ssleay32.dll | PF | open SSL connection |
lastools.db3 | PF (+ini) | LAStools documentation database |
lasclassification.txt | UF | the classification texts used to be easily changed by the user |
laslook.db3 | UF (+ini) | laslook user data database |
layout_current.lay | UF | json of the current/last screen layout |
layout_default.lay | UF | json of the default screen layout |
layout_default.lay_backup | UF | backup of default screen layout |
rapidlasso.laz | UF | a small LAZ sample |
LICENSE.txt | UF | license text |
laslook.ini
The local configuration “laslook.ini” is created in (UF) after the first boot to store user/application settings. Most configurations can be set via the setup dialog within the application. Some settings such as the location of the DB file can be only set manually using a text editor.
USB stick Installation
Typically, program files are stored in the programs folder, while user data is stored in the user’s folder. To enable portable installations, you can simply move all files from the programs folder and the public data folder to a local directory. If the program needs a user file, it first looks for it in the program folder: If the file is found there, this file is used. Simply run “laslook.exe” to start the program.
Unattended Setup & other options
An unattended/silent setup can be done in 2 ways: Simply copying the files using a own script or using command line switches from the setup program. We use InnoSetup” to create the installer.
This are the most important switches of InnoSetup:
Argument | Description |
/SILENT | Forces a silent installation without user interaction. |
/LOG=“c:\temp\setup.log“ | Write a log file into the given filename. |
/lastools=“c:\program files\lastools“ | Use this directory as LAStools target (if no installation was done before. Details see description above). |
/SAVEINF=“c:\admin\inf.txt“ | Writes all settings made into a file „inf.txt“. |
/LOADINF=“c:\public\inf.txt“ | Gets all settings out of the previous generated „inf.txt“ file. |
Please see the InnoSetup documentation for further information.