Next Article in Journal
Multi-Stage and Multi-Objective Optimization of Solar Air-Source Heat Pump Systems for High-Rise Residential Buildings in Hot-Summer and Cold-Winter Regions
Previous Article in Journal
Research on the Economic Scheduling Problem of Cogeneration Based on the Improved Artificial Hummingbird Algorithm
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article

Energy-Saving Geospatial Data Storage—LiDAR Point Cloud Compression

1
Department of Geodesy and Geomatics, Faculty of Environmental Engineering, Geomatics and Renewable Energy, Kielce University of Technology, 25-314 Kielce, Poland
2
3Deling Sp z o.o., 31-532 Krakow, Poland
*
Author to whom correspondence should be addressed.
Submission received: 13 November 2024 / Revised: 13 December 2024 / Accepted: 16 December 2024 / Published: 20 December 2024
(This article belongs to the Special Issue Low-Energy Technologies in Heavy Industries)

Abstract

:
In recent years, the growth of digital data has been unimaginable. This also applies to geospatial data. One of the largest data types is LiDAR point clouds. Their large volumes on disk, both at the acquisition and processing stages, and in the final versions translate into a high demand for disk space and therefore electricity. It is therefore obvious that in order to reduce energy consumption, lower the carbon footprint of the activity and sensitize sustainability in the digitization of the industry, lossless compression of the aforementioned datasets is a good solution. In this article, a new format for point clouds—3DL—is presented, the effectiveness of which is compared with 21 available formats that can contain LiDAR data. A total of 404 processes were carried out to validate the 3DL file format. The validation was based on four LiDAR point clouds stored in LAS files: two files derived from ALS (airborne laser scanning), one in the local coordinate system and the other in PL-2000; and two obtained by TLS (terrestrial laser scanning), also with the same georeferencing (local and national PL-2000). During research, each LAS file was saved 101 different ways in 22 different formats, and the results were then compared in several ways (according to the coordinate system, ALS and TLS data, both types of data within a single coordinate system and the time of processing). The validated solution (3DL) achieved CR (compression rate) results of around 32% for ALS data and around 42% for TLS data, while the best solutions reached 15% for ALS and 34% for TLS. On the other hand, the worst method compressed the file up to 424.92% (ALS_PL2000). This significant reduction in file size contributes to a significant reduction in energy consumption during the storage of LiDAR point clouds, their transmission over the internet and/or during copy/transfer. For all solutions, rankings were developed according to CR and CT (compression time) parameters.

1. Introduction

On one hand, traditional incandescent light bulbs are being replaced by LEDs, resulting in savings in electricity consumption. On the other hand, however, we are seeing an increasing problem with light pollution of the surrounding space [1,2,3]. The same energy saving trends can be seen in transportation [4], industry [5,6], building maintenance [7], heavy industry [8], companies [9] and even at the household level [10,11,12].
The increasing demand for energy is also fuelled by the growing popularity of data centres [13,14,15]. Every packet of data and, ultimately, the information created from it require access to sensors. This applies whether it is in the field of digital twins [16], sea pollution [17] or real estate good governance principle support [18].
In the field of geospatial data, the development of measurement sensors means that we have more and more data with improving quality:
-
Scanners are working ever faster;
-
Point clouds are getting denser;
-
GDSs of orthophotos are getting smaller and smaller;
-
The resolution of remote sensing data is increasing;
-
Two-dimensional datasets are being developed into three-dimensional datasets;
-
Not only individual buildings, but entire towns and cities are being modelled;
-
Areas along roads are being covered with spherical images or LiDAR point clouds, e.g., Google Street View, HERE.
Geospatial data are used in a very wide range of issues including air pollution [19], land consolidation [20,21], building management [22], forestry [23], cadastre [24,25,26], spatial planning [27], BIM [28,29,30] and HBIM [31,32] modelling, smart villages [33,34], smart cities [35], estate valuation [36,37], mining [38,39], environment [40,41], urban greenery [42], geology [43], safety [44], offshore [45], tourism [46] and energy production infrastructure conditions such as wind turbines [47,48,49].
In addition, the above data are multiplied due to the updates performed. Also, the desire to access archive data contributes to the need for more storage space.
Energy is needed for data acquisition, processing and storage. Due to the mobility of the systems acquiring geospatial data, their energy requirements are constantly minimised; however, in terms of processing and storage, energy saving is not a key aspect. Therefore, the issues cited in the title appear to be important to explore and present.
The issue of LiDAR point cloud compression interested the corresponding author more than 10 years ago, as can be seen in the conference programme of the Polish Society for Photogrammetry and Remote Sensing in Poznan [50]. The results of the research presented at the above conference were not published in the form of an article, and the scope of the validation was not very wide, with only 10 formats being checked. The topic was, therefore, taken up again with a wider team of authors, with increased validation (22 formats) and a proposal for a new solution to this problem (3DL format).
The novelty presented in this paper is the 3DL format containing LiDAR data, which implements the authors’ preferred strategy of converting point clouds into smaller-volume files rather than just archiving them.

2. State of the Art

Today, the growth of digital data is enormous. As an indication of the scale of the challenge, Statista [51] reports that approximately 329 million TB of data are created every day. This amounts to approximately 2.3 ZB per week and 120 ZB per year. As information societies, we try to collect all kinds of data. On the one hand, the large volumes of the data collected provide opportunities for analysis, resulting in growth, but on the other hand, it involves risks and poses challenges. The same trend can be observed in the field of geospatial data. Examples include publications on reference datasets [20,52,53], orthophotos [54] and ISOK (an IT system for shielding the country from exceptional threats, mainly flood threats). This growing trend is supported by both the development of measurement units and the capacity to process large datasets.
There is, therefore, a real need for ways of storing digital data that save disk space without losing any of their content or functionality.
Airborne laser scanning (ALS), performed in Poland as part of the ISOK project between 2010 and 2015, may also be a good example [55]. Due to the lack of publicly available information, the authors estimated that during a single scan of 92% of Poland’s area, approximately 125 TB of resulting LiDAR ALS data were collected in the form of LAS files. Bearing in mind that within the framework of subsequent projects, a large portion of point clouds is updated and recipients would like to be able to access both current and archival data, the conversion of LAS collections to more efficient formats seems indispensable. Currently, ALS data in Poland are available at https://mapy.geoportal.gov.pl/imap/Imgp_2.html?gpmap=gp0 if you wish (accessed on 10 November 2024) as LAZ files.
ALS data cover very large areas (e.g., tens or secti square kilometres), but their accuracy and density are not the highest. If the client is interested in a cloud with a point density every few millimetres and the area/object is not too large, then LiDAR TLS (Terrestrial Laser Scanning) measurements should be performed. In addition to topographic applications [56,57], environmental [58,59,60] or forestry [61,62,63] LiDAR data are very often used in architecture or for inventory purposes of various objects [64,65,66,67,68,69,70], to create 3D BIM models of existing objects [71,72,73], mining [74], tourism [75] or 3D cadaster [76].
To speed up data acquisition, mobile laser scanning (MLS) can be used for objects for which the required accuracy is lower. Examples of applications of this technology in various fields are as follows: [77,78,79] urban environment, [80] road extraction, [81] cadastre, [82,83] forestry, [84] mining, [85] tunnelling or the low-cost version [86,87,88].
The smaller volume of LiDAR data reduces not only the need to prepare disk space for their storage, but also the smaller amount of data to be transmitted when visualising the data in the browser versions of programs or when downloading them.
The functionality of the ‘smaller’ files is also not insignificant. If we use a typical archiver to package LAS files, we create a copy of our data in compressed files. These can be stored in any way, anywhere. However, if we want to use them, they must be unpacked. This seemingly obvious example has implications in terms of volume (disk space), time (packing, unpacking and copying time) and energy consumption (see Figure 1). Longer data running times for archiving also mean increased electricity requirements.
Therefore, it would be far better to save/convert LiDAR data into formats that are dedicated to them, and their reduced size does not result in the need for additional steps before reuse. A key question, then, is which data handling strategy will be more effective: LiDAR domain-specific compression algorithms and formats (such as LAZ), or general-purpose compression algorithms (such as ZIP or RAR).
Of course, it is impossible to overlook the role of software manufacturers here, who are essentially influencing the ‘popularity’ of data formats through their implementation in the software they produce (import and export functions). On the other hand, if the newly invented format were ‘revolutionary’ and extremely effective in terms of volume reduction, it would certainly find favour with software providers quite quickly.
On the technical side, lossy or lossless compression can be performed. Lossy can be used in cases where the loss of excess information after decompression is relatively harmless, e.g., video or audio. In the field of geospatial data, lossless compression is far more useful, where the reconstructed data sequence is identical to the source.
To perform lossless compression, various coding algorithms are used that modify the way data are represented to reduce their volume. These algorithms look for repetitions in the input data and replace them with shorter codes. In this way, the repeating patterns can be reconstructed after decompression, restoring the original file. One example of a lossless compression method is the Huffman algorithm. It involves assigning shorter codes to frequently occurring characters in the input data and longer codes for infrequently occurring characters. These codes are assigned in such a way that no interference is created in the decompression process. As a result, frequently used symbols receive short codes and rarely used symbols receive long codes.
The most popular formats offering lossless data compression are ZIP and RAR. In the case of the RAR format, compression algorithms are applied in two stages: compression and encoding. In the compression stage, the LZSS (Lempel–Ziv–Storer–Szymanski) algorithm, which is an adaptive dictionary algorithm, is used. At the encoding stage, Huffman coding is used, which assigns short binary codes to the most frequent symbols.
For the ZIP format, the primary compression algorithm is Deflate, which is a combination of the LZ77 algorithm and Huffman coding. The LZ77 algorithm uses a dictionary to replace repeated data sequences, while Huffman coding assigns short binary codes to the most frequent symbols
As already noted in 2013 in the publication [89], LiDAR data, by virtue of their size, are expensive to store and computationally intensive.
The LAS format was developed by ASPRS in LAS 1.0 in 2003, and with its publicly available description of the format, it has been recognised as the global standard for handling laser scanning data, adopted by manufacturers of scanning equipment, and point cloud processing applications and systems. It is currently being developed to LAS version 1.4.
Despite the development of the LAS format and its efficiency in storing LiDAR data, Martin Isenburg foresaw problems with the gigantic amount of laser scanning data and proposed the LAZ format in November 2011, describing it as follows: ‘As the sampling density of LiDAR increases so does the size of the resulting files. Typical LAS files contain tens to hundreds of millions points today, but soon, billions will be commonplace. The LAZ file format is a completely lossless compression scheme for LiDAR in binary LAS format versions 1.0 to 1.3. Encoding and decoding speeds are around one to three million points per second, and our compressed files are only 7–25% of the original file size. Compression and decompression happen on-the fly in a streaming manner, and random access is supported with a default granularity of 50,000 points. A reference implementation unencumbered by patents or intellectual property concerns is freely available with an LGPL license, making the proposed compression scheme suitable to become part of the LAS standard [90]’. From the 2011 quote above, there has indeed been an increase in the density and speed of LiDAR data acquisition; LAS data compression has been maintained and the format itself has become a common solution in many freeware and commercial software.
It is also worth noting that the purpose of developing the LAZ format was far broader than just reducing the volume of LiDAR files. As you can read in [91], Dr Isenburg was aware of the human impact on the world around him. The goal was not only the technology, but also its potential to improve the condition of our planet, e.g., to reduce the carbon footprint.
Research on the compression of LiDAR data has been carried out by [92], among others. In this study, 7-Zip, RAR, LASZip (LAZ) and the authors’ newly proposed format, LASComp, were tested. A performance analysis of the proposed solution was performed for a set of 13 ALS test files ranging from 97 MB to 930 MB in size. The following average compression ratio values were obtained: 22.4% for 7-Zip, 17.1% for RAR, 13.4% for LASZip (LAZ) and 11.8% for LASComp. However, neither the times required for compression nor the computer on which the calculations were performed are presented. This would certainly have given an overview of the computing power requirements of the solution. Despite the promising results in terms of CR and more than 10 years since the publication of these research results, the authors are not aware of software in which the LASComp format would be implemented.
An interesting approach is presented in the paper [93] where the LiDAR ALS cloud is first classified into trees and non-trees, and then a separate compression is performed for each class. The authors describe it as follows: ‘This paper proposes a new geometry-based LiDAR compression approach that can compress the data significantly while maintaining the geometric accuracy. For example, building boundaries are well preserved. Furthermore, its storage format provides meaningful semantic information and supports multiresolution access. To better evaluate the new geometry based compression method, we also implemented an image based compression scheme based on JPEG2000, i.e., we generate the depth image for 3D tree and building/ground data respectively, compress them by JPEG2000, and compare the imaged based compression with the proposed geometry based compression. Experimental results show that the proposed geometry-based airborne LIDAR compression performs much better than image-based compression. The compression performance is especially significant for building and ground data at lower bit rates’ [93]. After detailed analysis, it turns out that, for example, the edges of buildings are simplified by line fitting and then compress the boundary pixel location and plane parameters by WinZip or arithmetic encoder. As a result, ‘instead of recording all the boundary points, say 100 zigzag points, we only need to record the two end points to reduce the file size significantly without introducing much error’ [93].
The JPEG-2000 Standard was used to perform the compression of LiDAR ALS data also in the work [94]. Admittedly, the study carried out concerned ALS full-waveform (FWD) data, but the results presented are promising.
Interesting summaries and also detailed descriptions of various algorithms for the lossless compression of LiDAR data can be found in the work [95]. Although there is no author summary of the results with the obtained CR or CT (compression time) values, the publication deserves a mention.
Very interesting information and results, especially in the context of the results presented in Chapter 4 of this manuscript, can be found in the publication [96], as methodologically, it is the most convergent with the research presented below. It focuses on comparing only the final LAS files with LiDAR ALS clouds converted to other point cloud storage formats. Checks were made for the following formats: LASzip (LAZ), LASComp, LiDAR Compressor, 7-Zip, WinZip and WinRAR. Key metadata were provided for the seven test files: file size, number of points, density (pts/sq m) and bits per point (bpp). The results were assessed in terms of CR efficiency, calculated as compressed file size/original file size in percent, CT (compression time in seconds) and bits per point. Unfortunately, the hardware parameters of the set on which the conversions were performed were not given, so it is difficult to assess the CT. On the other hand, it is very good that the CT values were given, because despite not knowing the PC specifications, one can see the differences in CT between the formats. Also missing from the paper is information on which settings 7-Zip, WinZip and WinRAR compression was performed and in which specific programs. In terms of the CR, the following average results were achieved: LAZ—16.6%, LASComp—18.4%, LiDAR Compressor—20.8%, 7-Zip—24.1%, WinZip—39.3% and WinRAR—20.2%. Thus, it can be seen that LiDAR-dedicated formats are more efficient than general compression software, with the best of the general ones, WinRAR, achieving a score close to the worst dedicated one, the LiDAR Compressor. In terms of CT, the average times are as follows: LAZ—16.7 s, LASComp—164 s, LiDAR Compressor—44 s, 7-Zip—322 s, WinZip—163 s and WinRAR—48.7 s. For this parameter, the results are more varied, but the fastest is the compression to LAZ. As far as bpp is concerned, the order of the results coincides with CR.
Increasingly, LiDAR data compression issues, in addition to publications directly related to computer science, geoinformatics, photogrammetry, geodesy or heritage documentation, are appearing in robotics, automotive or autonomous vehicle navigation. The specificity of these works is a little different because they focus on data processing reliability, data processing speed and technical–technological aspects, and not, like geospatial works, on the compression of the resulting point clouds themselves or for archiving purposes [97,98].
An example is paper [99], where the authors ‘compare various low-level lossless compression algorithms that could be used in LiDAR sensors for a memory size reduction or improved bandwidth utilisation. The algorithm comparison performed using several factors such as an implementation complexity, compression speed and effectiveness. Finally, a simple, yet effective compression algorithm is proposed that could be beneficial for battery-powered robots, e.g., UAVs, and systems with a high frame rate requirements such as autonomous vehicles’. The algorithms being compared were as follows: DE—Delta Encoding, GRC—Golomb-Rice Compression, SSD—Symmetric Segmented Delta encoding and EDC—Extended Delta Compression. EDC performed the best with CR of 62% and 53%, depending on the test set.
The Delta Encoding algorithm for compressing LiDAR data also appears in the paper [100]. The authors called this solution as ‘RIDDLE (Range Image Deep DeLta Encoding)’ and describe it as ‘a data-driven algorithm to compress range images with predictive neural networks. This method is inspired by the use of Delta Encoding in PNG image compression’. As an evaluation of the effectiveness of the solution, they present a visualisation of reconstructed point clouds, coloured by per point Chamfer distance, for the G-PCC, Draco, PNG and RIDDLE algorithms with compression rates calculated as bits per point and reduced by almost eight times from 32 bpp to 4.02 bpp.
An interesting paper on the compression of LiDAR data in automotive applications is [101]. Compression is performed here using a recurrent neural network and residual blocks to progressively compress one frame’s information from the 3D LiDAR unit. Due to the measurement unit used (Velodyne HDL-32E) and the way the SLAM (Simultaneous Localisation And Mapping) data were assembled, it was possible to compress individual frames rather than the whole file. The effect of compression is described as Bitrate (bpp) and assessed by SNNRMSE (Symmetric Nearest Neighbour Root Mean Squared Error), expressed in cm. JPEG-based, Octree and the author’s RNN-based solution were tested, obtaining results of 2.04 bpp and 15.15 cm SNNRMSE for the RNN-based method, 4.04 bpp and 16.48 cm for the JPEG-based method, and 5.02 bpp and 15.49 cm for Octree compression.
In the paper [102], the quality of compression, i.e., the ratio of file sizes after and before compression, was called the compression factor. During testing, compression was performed using two data-independent methods: TUCKER [103] and P-TUCKER [104] vs. two data-dependent methods: RSTC [105] and SLiC. SLiC is a novel grouped wavelet technique developed by authors for static roadside LiDAR data compression. This method compresses LiDAR data both spatially and temporally using a kd-tree data structure based on Haar wavelet coefficients. The study was carried out on real (UNR and TAMU) and synthetic data. The difference from the previous mentioned publication is the position of the LiDAR data acquisition unit. In the examples cited so far, these were TLS (terrestrial laser scanning) or MLS (mobile laser scanning) clouds from a moving platform. In the case of this publication, the scanning unit is permanently mounted at the survey station. In this way, parts of the environment (buildings, road surfaces or infrastructure) can be considered as reference objects.
A very interesting, comprehensive and summarising paper on LiDAR data compression in automotive was published this year in Sensors [106]. Due to its review nature, it brings together work with results obtained in the field of the following:
-
Coding-based compression methods applied to LiDAR data;
-
Format-based compression methods (LAS and PCD format only);
-
Two-dimensional-based intra-frame compression methods;
-
Two-dimensional-based inter-frame compression methods;
-
Three-dimensional tree-based compression methods;
-
Sparse-tensor-based and point-based methods.

3. Materials and Methods

3.1. Materials

The test files were TLS and ALS data, each with a local and PL-2000 (EPSG:2178) coordinate system (CS), resulting in a total of 4 LiDAR point clouds. A brief overview is provided in Table 1.
A visualisation of the above point clouds in colouring by RGB values is shown in Figure 2.
The ALS data originated from Kielce City Hall and were acquired in 2019. The commissioning unit was the Office of the Smart City in Kielce City Hall. A point cloud with a nominal density of 20 pts/sq m was delivered with a height error of no more than 0.15 m.
The TLS cloud is one scanposition acquired by a Faro Focus s150 scanner at ‘1/4’ resolution, i.e., points every 6.1 mm @ 10 m from the scanner. In order to obtain complementary datasets, the original ALS point cloud from the PL-1992 CS (EPSG:2180) was transformed to the PL-2000 s7 CS (EPSG:2178), obtaining the ALS_2000 file. A second transformation was then performed on the X and Y coordinates, approximating the data to zero and creating a local CS (ALS_LOK). The TLS point cloud was originally in the local CS (TLS_LOK) and then a transformation was performed along the X and Y coordinates, obtaining the TLS dataset in the PL-2000 s7 CS (TLS_2000). No post-height transformations were performed on any of the clouds. Also, the range of additional data collected such as intensity (INT) or RGB values was not altered.
In terms of the precision of the coordinate recording, the ALS cloud in the original version was recorded to 2 decimal places, while for the study, the ALS clouds were recorded to the same precision as the TLS, i.e., to 4 decimal places, topping up the third and fourth places with zeros. TLS clouds were recorded with precision to four decimal places.
The ALS point cloud has an extent of approximately 800 × 500 m, which, with 15,885,170 points, gives approximately 39.7 pts/sq m. The TLS cloud at approximately 280 × 265 m, with the number of points, 23,998,971, gives approximately 320 pts/sq m. Obviously, due to the data acquisition perspective, these clouds differ from each other in terms of both density and uniformity. A summary of such differences using TLS and MLS clouds as an example is presented in the paper [78]. In this case, ALS clouds, which are sparser but more uniform, are contrasted with TLS clouds, which are heavily saturated with points in close proximity to the scanner, while single points are found at the boundaries of the file range. The above characteristics can be seen very well in Figure 2A,B.

3.2. Hardware, Software and Formats

The computer sets shown in Table 2 were used to carry out the tests. The letter designation of the computer used for every conversion is also included in the Table 3 with the compression results.
During the study, 22 file formats (*.7z, *.bzip2, *.gzip, *.xz, *.zip, *.RAR, *.RAR4, *.pod, *.BIN, *.LAZ, *.TXT, *.E57, *.PCD, *.PN, *.PV, *.PNTS, *.PCD, *.XYZ, *.ASC, *.PTS, *.RPC, *.3DL) were checked in 8 software.
These 22 formats can be divided into 3 groups (see Figure 1):
-
General purpose compression algorithms (*.7z, *.bzip2, *.gzip, *.xz, *.zip, *.RAR, *.RAR4)—group 1 in Figure 1;
-
Compression algorithms specific to the LiDAR domain (*.pod, *.BIN, *.LAZ, *.E57, *.PCD, *.PN, *.PV, *.PNTS, *.PCD, *.PTS, *.RPC, *.3DL)—group 2 in Figure 1;
-
General/universal formats that do not have compression features (*.TXT, *.XYZ, *.ASC)—group 3 in Figure 1.
Most of the conversions were carried out on Set A using the following software: 7-Zip 23.0, WinRAR 6.24 x64, Bentley Pointools PODcreator 02.00.01.00, LAStools 1.0.0.0, CloudCompare 2.13 and FME Workbench 2022.1. Trimble RealWorks 12.1 was used on set B, while set C was used to convert LAS to 3dl. Detailed information about all 101 conversions are in the Table 3 in Section 4.

3.3. New LiDAR Data Format—3DL

This study also examines a new point cloud storage format (*.3dl) developed by 3Deling company under project number POIR.01.01.01-00-1283/17-00 from the Polish agency The National Centre for Research and Development. This proprietary solution developed under project ‘Development of software to optimise the process of creating project documentation based on data obtained as a result of terrestrial laser scanning, with particular emphasis on simplifying access and interpretation possibilities of point clouds, as part of Activity 1.1: R&D projects of enterprises of the Operational Programme Intelligent Development 2014–2020, co-financed by the European Regional Development Fund’. Although it is not yet available in other software besides 3Deling’s in-house software, it will be evaluated on a par with other commercial formats for storing LiDAR data. The conversion to 3DL format is a two-step process: first the *.las to *.pod conversion is performed and then *.pod to *.3dl.
The 3DL format is designed to efficiently store large point clouds. To obtain this efficiency, the points in this format are structured in a set of octrees data structure. This allows for quick access to points from any desired region of the cloud. The main part of the points is placed in leaf level of the octree. Some are also present in the trunk of the octree (level 0) to facilitate a quick draft view of the cloud, as they can be quickly accessed during the opening of the file. To achieve space efficiency, the compression method was used. The coordinates of the points are represented as 2 byte integers, calculated relative to their octree branch position. This way, the size of 3DL files is similar to the size of the pod files.

3.4. Methods

The test files prepared in the LAS format were subjected to compression using different software, into different formats (both listed in Section 3.2), and using different compression methods and grades. For each conversion, the parameters listed below were noted:
-
Software name;
-
The output file format;
-
Compression method;
-
The compression ratio (where different ones were available);
-
Compression time (from file properties);
-
Size of the compressed file;
-
Compression ratio expressed in %.
The compression ratio (CR) was calculated according to Formula (1):
CR = file   size   after   compression   file   size   before   compression   × 100 %
Time was recorded in the properties of each file as the difference between the time it was created and the time it was last modified.
Keeping in mind the two key aspects of this study, i.e., compression rate and compression time, two summaries/rankings were prepared, sorting the individual solutions from the best compressed to the worst compressed, and those that took the least time to perform the conversion to the longest processed. The complete rankings are provided in Table A1 and Table A2 for the compression ratio (CR) in Appendix A, and in Table A3 and Table A4 for the compression time (CT) in Appendix B. Moreover, a full set of information on all 101 conversions can be found in Table 3 in Section 4.

4. Results

In the eight software, conversions to 22 file formats were made for each of the four base LAS files. This gave a total of 404 results, which are shown in Table 3 below.
Table 3. Summary of the results. File size after conversion [in bytes] and compression rate (CR) in % for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000, respectively. Explanations below the table.
Table 3. Summary of the results. File size after conversion [in bytes] and compression rate (CR) in % for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000, respectively. Explanations below the table.
SoftwareFormat Degree of CompressionCompression
Method
File Size After Conversion
[bytes]
CR [%]File Size After Conversion
[bytes]
CR [%]File Size After Conversion
[bytes]
CR [%]File Size After Conversion
[bytes]
CR [%]Hardware
Unit
ALS_LOKALS_PL2000TLS_LOKTLS_PL2000
540,096,009540,096,009623,973,543623,973,545
7-ZIP7zFastestLZMA2183,853,13834.04%183,323,16333.94%287,664,58446.10%272,357,61643.65%A
LZMA183,312,95133.94%182,774,24633.84%285,769,97845.80%271,351,33843.49%A
PPMd203,769,78637.73%202,009,98237.40%245,953,76439.42%240,472,12438.54%A
BZip2223,270,46341.34%222,709,48641.24%262,281,33742.03%247,376,75239.65%A
Fast LZMA2186,484,08934.53%186,034,62934.44%280,523,70744.96%270,878,19143.41%A
LZMA186,641,48334.56%186,190,50034.47%279,901,19444.86%270,716,76543.39%A
PPMd195,636,29336.22%194,180,49235.95%232,906,44437.33%224,313,53535.95%A
BZip2210,506,58638.98%209,879,18238.86%240,660,38138.57%230,580,96836.95%A
NormalLZMA2160,275,66829.68%159,602,64929.55%243,765,41239.07%236,326,86737.87%A
LZMA160,153,98429.65%159,490,15029.53%242,327,36438.84%235,862,30737.80%A
PPMd190,125,42035.20%188,852,26034.97%227,342,98136.43%220,803,33435.39%A
BZip2208,165,02138.54%207,397,59438.40%238,120,58238.16%228,833,61536.67%A
MaximumLZMA2160,243,50729.67%159,407,80729.51%241,172,71038.65%235,481,72637.74%A
LZMA160,070,59029.64%159,550,36829.54%240,303,86438.51%235,083,56937.68%A
PPMd187,800,55134.77%186,411,56134.51%226,328,09136.27%220,420,16935.33%A
BZip2208,137,37038.54%207,374,02538.40%237,624,11938.08%228,271,45736.58%A
Ultra LZMA2159,877,32829.60%159,448,24429.52% 239,172,88138.33% 234,389,71537.564%A
LZMA160,175,95629.66%159,390,35229.51%239,039,98538.31%234,336,98137.556%A
PPMd189,726,18235.13%188,280,41734.86%224,523,52535.98%219,035,45035.10%A
BZip2208,120,21738.53%207,358,72338.39%237,490,69638.06%228,102,47836.56%A
bzip2BZip2Fastest223,270,29341.34%222,709,32441.24%262,281,19142.03%247,376,59039.65%A
Fast210,506,41638.98%209,879,02038.86%240,660,23538.57%230,580,80636.95%A
Normal 208,164,85138.54%207,397,43238.40%238,120,43638.16%228,833,45336.67%A
Maximum208,137,20038.54%207,373,86338.40%237,623,97338.08%228,271,29536.58%A
Ultra 208,120,04738.53%207,358,56138.39%237,490,55038.06%228,102,31636.56%A
gzipdeflateFastest242,246,293 44.85%242,853,849 44.96%351,633,352 56.35%324,863,932 52.06%A
Normal 227,376,745 42.10%228,933,501 42.39%327,601,116 52.50%304,665,243 48.83%A
Maximum226,737,427 41.98%228,334,717 42.28%326,904,830 52.39%304,002,413 48.72%A
Ultra 226,684,785 41.97%228,289,365 42.27%326,872,237 52.39%303,984,848 48.72%A
xzLAZM2Fastest183,867,72434.04%183,337,75233.95%287,681,46446.10%272,374,49243.65%A
Fast186,485,09234.53%186,035,63634.44%280,524,90044.96%270,879,36443.41%A
Normal 160,275,83229.68%159,602,82429.55%243,765,64039.07%236,327,08037.87%A
Maximum160,243,54029.67%159,407,84429.51%241,172,76838.65%235,481,76837.74%A
Ultra 159,877,21629.60%159,448,14029.52%239,172,79238.33%234,389,61237.56%A
zipFastestdeflate242,246,43944.85%242,853,99144.96%351,633,48756.35%324,864,07452.06%A
deflate64239,780,14644.40%240,034,57844.44%343,736,48355.09%322,368,46551.66%A
BZip2223,270,48941.34%222,709,51241.24%262,281,36542.03%247,376,77839.65%A
LZMA183,312,97633.94%182,774,27133.84%285,770,02145.80%271,351,37943.49%A
PPMd203,367,19937.65%201,395,80337.29%245,806,17839.39%240,053,74238.47%A
Fastdeflate242,246,43944.85%242,853,99144.96%351,633,48756.35%324,864,07452.06%A
deflate64239,780,14644.40%240,034,57844.44%343,736,48355.09%322,368,46551.66%A
BZip2210,506,61238.98%209,879,20838.86%240,660,40938.57%230,580,99436.95%A
LZMA186,641,50834.56%186,190,52634.47%279,901,23744.86%270,716,80643.39%A
PPMd196,704,57036.42%195,052,75836.11% 234,031,03637.51%224,686,31736.01%A
Normal deflate227,376,89142.10%228,933,64342.39%327,601,25152.50%304,665,38548.83%A
deflate64221,386,07540.99%222,247,61741.15%316,486,96350.72%298,794,50347.89%A
BZip2208,165,04738.54%207,397,62038.40%238,120,61038.16%228,833,64136.67%A
LZMA160,154,01029.65%159,490,17629.53%242,327,39138.84% 304,002,55548.72%A
PPMd190,995,84835.36%189,864,69735.15%227,860,18536.52% 220,537,51435.34%A
Maximumdeflate226,737,57341.98%228,334,85942.28%326,904,96552.39%304,002,55548.72%A
deflate64220,825,08540.89%221,718,15741.05%315,802,56150.61% 298,197,83447.79%A
BZip2208,137,39638.54%207,374,05138.40% 237,624,14738.08%228,271,48336.58%A
LZMA160,070,61629.64%159,550,39429.54% 240,303,89138.51%235,083,59437.68%A
PPMd185,262,78934.30%184,133,35034.09%223,065,01835.75%217,823,84734.91%A
Ultra deflate226,684,93141.97%228,289,50742.27%326,872,37252.39%303,984,99048.72%A
deflate64220,788,07840.88%221,692,57041.05%315,801,83350.61%298,177,16747.79%A
BZip2208,120,24338.53%207,358,74938.39% 237,490,72438.06% 228,102,50436.56%A
LZMA160,175,98229.66%159,390,37829.51% 239,040,01238.31% 234,337,00637.56%A
PPMd190,493,73835.27%189,254,44035.04%218,230,54534.97%212,636,60234.08%A
WINRARRAR Fastest248,632,94746.03%250,741,68546.43%308,882,76549.50%243,294,99538.99%A
Fast212,058,22939.26%212,071,73039.27%290,661,57646.58%242,338,90038.84%A
Normal204,240,43937.82%204,164,12737.80%288,836,51646.29%241,845,81338.76%A
Good 204,476,71737.86%204,394,79537.84%288,191,56046.19%241,717,34638.74%A
Best204,535,53937.87%204,453,74037.86%287,906,67346.14%241,656,15538.73%A
RAR4 Fastest220,739,13040.87%220,962,48740.91%337,918,43454.16%317,688,95950.91%A
Fast209,366,61738.76%209,285,47738.75%295,952,18547.43%288,590,52046.25%A
Normal201,400,39137.29%201,315,34237.27%291,820,03846.77%242,792,56038.91%A
Good 201,603,52337.33%201,516,35937.31%291,059,64746.65%242,610,61738.88%A
Best201,657,80037.34%201,573,12937.32%290,754,61846.60%242,561,84438.87%A
ZIP Fastest237,750,59844.02%238,994,68944.25%352,152,58156.44%326,916,72452.39%A
Fast237,816,54344.03%239,071,43044.26%349,483,57156.01%325,381,12952.15%A
Normal238,397,78744.14%239,742,06844.39%339,856,86854.47%317,928,07950.95%A
Good239,149,51344.28%240,517,08144.53%338,998,62454.33%317,429,34250.87%A
Best239,643,28244.37%241,016,87644.62%338,799,95654.30%317,338,72250.86%
BEN PODCRpod Precision to 1 mm175,075,63132.416%175,075,83932.42%264,353,05242.37%264,352,84242.37%A
LASTOOLS BIN 32381,244,13670.59%381,244,13670.59%479,979,47676.92% 479,979,47676.92%A
64381,244,13670.59%381,244,13770.59%479,979,47776.92% 479,979,47776.92%A
LAZ 3280,739,47114.95%80,739,47114.95%290,783,95346.60% 231,193,87337.05%A
6480,739,47114.95%80,739,47214.95%290,783,95446.60% 231,193,87437.05%A
TXT 321,006,883,110186.43%1,126,156,881208.51%1,029,311,815164.96%1,275,337,421204.39%A
641,006,883,110186.43%1,126,156,882208.51%1,029,311,816164.96%1,275,337,422204.39%A
CCBIN 762,492,977141.18%762,492,961141.18%767,970,080123.08%767,969,989123.08%A
E57 303,128,57656.12%303,128,57656.12%457,958,40073.39%457,958,40073.39%A
LAS 540,096,007100.00%540,096,007100.00%623,973,543100.00%623,973,543100.00%A
PCD 826,029,199152.94%826,029,199152.94%863,963,233138.46%863,963,233138.46%A
PN 381,244,08070.59%381,244,08070.59%575,975,30492.31%575,975,30492.31%A
PV 254,162,72047.06%254,162,72047.06%383,983,53661.54%383,983,53661.54%A
TXT 2,175,726,572402.84%2,295,000,343424.92%2,082,519,220333.75%2,328,913,212373.24%A
FMELAS 540,096,007100.00%540,096,007100.00%623,973,473100.00%623,973,473100.00%A
E57 191,418,36835.44%191,418,36835.44%289,189,88846.35%289,189,88846.35%A
POD 194,778,68936.06%194,778,68936.06%288,775,70146.28%288,775,70146.28%A
PNTS 238,277,66644.12%238,277,66644.12%359,984,68157.69%359,984,68157.69%A
PCD 555,981,321102.94%555,981,333102.94%647,972,576103.85%647,972,585103.85%A
XYZ 518,385,35895.98%518,171,36395.94%717,143,511114.93%951,340,542152.46%A
BIN 444,784,81682.35%444,784,81682.35%575,975,36092.31%575,975,36092.31%A
TRW ASC 341,396,15963.21%460,669,93085.29%449,596,22072.05%695,970,159111.54%B
LAZ 191,352,29235.43%168,516,89231.20%285,072,89645.69%248,006,34939.75%B
POD 291,032,70953.89%291,032,70953.89%432,896,04969.38%432,896,04969.38%B
PTS 765,462,711141.73%884,736,482163.81%1,049,110,606168.13%1,295,504,598207.62%B
RPC 361,845,85467.00%361,845,80167.00%471,210,40175.52%471,190,24775.51%B
3DL3dl3dlPrecision to 1 mm174,767,27532.36%174,767,27532.36%263,998,19042.31%263,998,28642.31%C
Explanations: Softwares: TRW—TRIMBLE REALWORKS 12.1, CC—CloudCompare 2.13, BEN PODCR—Bentley PODCreator 02.00.01.00. Formats: CC BIN—CC entities, CC E57—E57 Cloud, CC PCD—PointCloud library Cloud, CC PN—Point + Normal Cloud, CC PV—Point + Value Cloud, CC TXT—ASCII FME E57—ASTM E57, FME PNTS—Cesium 3D point cloud, FME XYZ—Point Cloud txt, FME BIN—Terrascan, TRW LAZ—LAZzip Files 1.2, TRW PTS—PTS Files, TRW RCP—Autodesk ReCap Files.
As described in the Methodology (Section 3.4), the key aspects of the studies conducted were the compression ratio (CR) and the time taken to perform the compression itself (CT). A detailed ranking of the results is presented in Appendix A, Table A1 and Table A2 for CR, and Appendix B, Table A3 and Table A4 for CT. A summary of the results, with the best and worst values, and their discussion are presented below.
Table 4 shows brief statistics characterizing the results obtained in terms of the compression rate and compression time.
With the best compression ratios, a significant reduction in the volume of the input files is achieved. For ALS data, this is almost a sevenfold volume reduction (from 100% to 14.95%), while for TLS data, it is almost three times. The best CRs for ALS data are also almost three times better than the mean and more than two times smaller than the median. For the TLS data, the differences are smaller and the best CRs are less than two times smaller than the mean values and only 50% lower than the median.
The other extreme of the results, i.e., the worst CRs are more than 4 times larger than the ALS input data and 3–4 times larger for the TLS data. Even greater variation between the min. and max. is achieved for CT from 1 s in the fastest version (for all input files) to more than 40 min for the ALS data, and 260 min and 169 min for the TLS data.
Table 5, Table 6, Table 7 and Table 8 were prepared to highlight the best and worst results for both CR and CT, with the best (Table 5) and worst (Table 6) solutions for CR, and the fastest (Table 7) and slowest (Table 8) solutions for CT selected for each.
The most effective in terms of file size reduction for ALS data was the LAZ format with a conversion performed in LASTOOLS 1.0.0.0 software with almost seven times the file size reduction. It is also worth noting that the ‘next’ solution (3rd place, 7-ZIP 23.0 software) is twice as bad, with a CR of 30%. For TLS data, the first two places went to ZIP format files prepared in 7-ZIP software, while the remaining places were also taken by 7-ZIP solutions for other formats. The differences in CR within the TOP 10 for TLS data are no greater than 2–3%. It is noteworthy that out of the 40 results in Table 5, 36 places were taken by the results from 7-ZIP software, i.e., software from the ‘general’ group. This demonstrates the high flexibility of the compression capabilities of generic file-volume-reduction algorithms. The LAZ from the LASTOOLS result, on the other hand, demonstrates the high degree of sophistication of the developed algorithm.
Table 6. Worst 10 solutions for the CR chosen from Table A1 and Table A2 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
Table 6. Worst 10 solutions for the CR chosen from Table A1 and Table A2 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
RankSoftwareFormat and MethodCRSoftwareFormat and MethodCRSoftwareFormat and MethodCRSoftwareFormat and MethodCR
92FMEXYZTXT95.98%FMEXYZTXT95.94%FMELAS 100.00%CCLAS 100.00%
93CCLAS 100.00%CCLAS 100.00%CCLAS 100.00%FMEPCD 103.85%
94FMELAS 100.00%FMELAS 100.00%FMEPCD 103.85%TRW ASC 111.54%
95FMEPCD 102.94%FMEPCD 102.94%FMEXYZTXT114.93%CCBIN 123.08%
96CCBIN 141.18%CCBIN 141.18%CCBIN 123.08%CCPCD 138.46%
97TRWPTS 141.73%CCPCD 152.94%CCPCD 138.46%FMEXYZTXT152.46%
98CCPCD 152.94%TRWPTS 163.81%LASTOOLS TXT32164.96%LASTOOLS TXT32204.39%
99LASTOOLS TXT32186.43%LASTOOLS TXT32208.51%LASTOOLS TXT64164.96%LASTOOLS TXT64204.39%
100LASTOOLS TXT64186.43%LASTOOLS TXT64208.51%TRWPTS 168.13%TRWPTS 207.62%
101CCTXT 402.84%CCTXT 424.92%CCTXT 333.75%CCTXT 373.24%
In terms of the least CR-efficient results presented in Table 6, in principle, almost all (except *.TXT from FME) failed to do their job, i.e., they did not compress the data from the input files. This refers to 31 solutions out of the 40 presented in Table 6. As expected, the worst format for storing LiDAR data, whether ALS or TLS and regardless of the conversion software, turned out to be *.TXT (12 out of 31 results). In addition, *.TXT from CloudCompare is almost double or more than double the size of *.TXT from LASTOOLS, depending on the underlying file. Due to the internal design (a text file with an added line about the number of points in the file), the *.PTS format also appears in this comparison. The same can be said for the *.XYZ, *.ASC and *.PCD formats.
Additionally, the CloudCompare 2.13 and FME Workbench 2022.1 software were checked for reading and writing the *.LAS format. Before and after writing, the file sizes are identical, which means that the above-mentioned software did not ‘cut’ anything from the data, nor did it add anything ‘from itself’ to the new files.
Table 7. Top 10 solutions for the CT chosen from Table A3 and Table A4 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
Table 7. Top 10 solutions for the CT chosen from Table A3 and Table A4 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
RankSoftwareFormat and MethodTimeSoftwareFormat and MethodTimeSoftwareFormat and MethodTimeSoftwareFormat and MethodTime
1CCPV 1CCBIN 1CCBIN 1FMEPCD 1
2FMELAS 1CCPN 1CCPN 1CCPN 2
3FMEE57 1FMELAS 1FMELAS 1CCPV 2
4FMEPNTS 1FMEPCD 1FMEPCD 1FMELAS 2
5FMEPCD 1LASTOOLSBIN322LASTOOLS BIN322FMEBIN Terrascan 2
6LASTOOLSBIN322LASTOOLSBIN642LASTOOLSBIN642LASTOOLS BIN323
7LASTOOLSBIN642CCPV 2CCPV 2LASTOOLS BIN643
8CCBIN 2FMEBIN 2FMEE57 3FMEE57 3
9CCPN 2WINRARRAR4Fastest 3FMEBIN Terrascan 3CCBIN 4
10FMEBIN 2FMEE57 3WINRARRAR4Fastest4WINRARRARFastest5
As far as CT is concerned, the top 10 fastest conversions are very close in terms of the time for ALS data—1 to 2–3 s and only close for TLS data—1 to 4–5 s. Among the formats, BIN dominates here (16 out of 40 results), and among the software, FME (17 out of 40 results). In only two cases, the last places in the top 10 for TLS data were taken by generic solutions (RAR4 from WINRAR), the rest being formats dedicated to LiDAR data.
Table 8. Worst 10 solutions for the CT chosen from Table A3 and Table A4 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
Table 8. Worst 10 solutions for the CT chosen from Table A3 and Table A4 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
RankSoftwareFormat and MethodTimeSoftwareFormat and MethodTimeSoftwareFormat and MethodTimeSoftwareFormat and MethodTime
927-ZIPxzLAZM2Ultra 1977-ZIP7zUltra LZMA1977-ZIPzipmaxLZMA2297-ZIPzipUltra PPMd243
937-ZIPzipUltra LZMA2007-ZIPzipUltra LZMA1977-ZIP7zUltra LZMA2717-ZIP7zUltra LZMA2258
947-ZIP7zUltra LZMA22017-ZIP7zUltra LZMA21997-ZIPxzLAZM2Ultra 2757-ZIPxzLAZM2Ultra 258
957-ZIPzipmaxPPMd2257-ZIPzipmaxPPMd2227-ZIP7zUltra LZMA22767-ZIP7zUltra LZMA262
967-ZIPgzipdeflateUltra 2497-ZIPgzipdeflateUltra 2457-ZIPgzipdeflateUltra 2967-ZIPzipUltra LZMA263
977-ZIPzipUltra deflate2497-ZIPzipUltra deflate2457-ZIPzipUltra PPMd3117-ZIPzipUltra deflate306
987-ZIPzipUltra PPMd2507-ZIPzipUltra PPMd2517-ZIPzipUltra LZMA3307-ZIPgzipdeflateUltra 307
997-ZIPzipUltra deflate642757-ZIPzipUltra deflate642667-ZIPzipUltra deflate3487-ZIPzipUltra deflate64329
100TRWPOD 514TRWPOD 4927-ZIPzipUltra deflate64352TRWLAZ 403
101TRWRPC 2655TRWRPC 2521TRWRPC 15,604TRWRPC 10,149
In Table 8, where the longest-compressing data formats are included, three things are noteworthy. The first is the overwhelming dominance of 7-ZIP (33 out of 40 results), with 23 out of 33 results being ultra-operation. The second point to note is the longest conversion times, independent of the base file, for the *.RCP format from Trimble RealWorks. Significantly, the times of up to 44 and 42 min for ALS data, and 260 and 169 min for TLS data are typically five times longer than the previous ranked result. It remains a matter for future research to see whether the ‘problem’ lies with TRW or the *.RCP format itself. The third issue is Trimble RealWorks as one of the two programs in Table 8. However, it is worth bearing in mind that. Trimble RealWorks was designed for point cloud registration and 3D modelling, not as a converter or data compression software. The availability of multiple output formats should rather be read as a plus and as an additional capability.
The 3Deling’s proprietary *.3DL format deserves a separate paragraph of comment. Comparing the results obtained for the *.3dl format in terms of the CR yielded place, the rankings are as follows: 15 out of 101 for ALS_LOK with a value of 32.36%, 16th place for ALS_PL2000 with a value of 32.36%, 38th place for TLS_LOK with a value of 42.31% and 48th place for TLS_PL2000 with a value of 42.31%. Comparing these results to others obtained by commercial and/or long-established formats, it can be said that they are good.
In terms of time, however, rankings are as follows: 34th for ALS data and 46th for TLS data. It is worth noting, however, that these conversions were performed on a different computer (Hardware Unit C) and also required double conversion (*.las to *.pod and then *.pod to *.3dl). If one was to look only at the last conversion (*.pod to *.3dl), then with a time of 5 s for ALS data, it would be places 14 and 12, and for TLS data with a time of 12 s, it would be 26 and 25.
Compared to the other formats in terms of compression efficiency and disk space savings, *.3dl performs better than the mean for each of the four files, as well as being in the second quartile. In terms of time, it scores in the middle of the pack (around 50th out of 101). It is worth noting that *.3dl, in the compression ranking for the TLS_LOK file, was in first place as regards dedicated point cloud formats. For the TLS_PL2000 file, it achieved the same result in terms of CR, which demonstrates the ‘robustness’ of the format to changes in the ‘length’ of the coordinates: around zero for TLS_LOK and around 7 million and 5 million for X and Y in TLS_PL2000. This is important as the *.3dl format was created to work with and store TLS data. The added value, on the other hand, is the very high rankings of ALS data as the second format dedicated to point clouds, second only to the LAZ solution.

5. Discussion

In order to critically analyse the results obtained, they were compared with the results described in other works. It is difficult to find the results of converting LiDAR data to the same formats in different works. From all the formats forfeited, it was possible to select three for which data exist in publications to count CR in %; these are the LAZ, RAR and ZIP formats. Table 9 brings together the results from other publications and the present study.
In both works of [90,96], as well as in the author’s preliminary research (2014, Poznan), the test files were ALS clouds. Therefore, the CRs overlap with the values achieved within the present study in LASTOOLS. Performing the LAS-to-LAZ conversion using Trimble RealWorks, the CR data were twice as bad. In terms of TLS data, the CR values are considerably worse with both LASTOOLS and Trimble RealWorks, but still offer a reduction in file volume of more than half.
In terms of the ZIP format, the obtained averaged results from all methods and modes for both 7-ZIP and WINRAR are close to the literature values. Only the conversion of ALS data in 7-ZIP CR data was slightly better than in the cited publications. In the case of the RAR format, CR values worse than in the cited literature were achieved, which encourages further research into the properties of this format.
Looking at all 404 conversions, it can be concluded that ALS data compress better than TLS data. This is the case in approximately 77% of the cases.
It is worth noting that no new format has emerged in the last 10 years that would reduce the size of LiDAR files in a revolutionary way.
The data compression issues that arise in automotive topics operate on LiDAR data, but with completely different characteristics. These are data recorded in a different SLAM manner and can therefore be compressed at the single-frame level. In addition, automotive data are of relatively low density compared to TLS data or classic MLS solutions like Riegl VMZ, based on the TLS VZ series unit or VMQ/X/Y systems based on the VUX sensor. Another difference is the range of the data collected. In automotive data, as a rule, only geometry is acquired and can be reduced to three coordinates. On the other hand, in the case of TLS, MLS or ALS data, the intensity, RGB values, echo information, airstrip, class and, in the case of data from moving systems, GPS time are also recorded. Therefore, compression efficiency calculated in bpp will be inadequate when comparing between publications. The compression performed in this study reduced the bpp count from 272 bpp for ALS data to 40.7 bpp for the best LAZ format, and from 208 bpp for TLS data to around 70 bpp. These values are similar to those presented in the work of [106,107], despite the different perspectives on space and the different range of information collected in the final file.
As part of future research, it is planned to carry out the following:
  • Make the base files available for download and conversion to formats not included in this study for all interested parties;
  • Test two-stage and multi-stage conversions, e.g., LAS to intermediate format and then, e.g., to *.RCP, instead of direct LAS -> RCP;
  • Develop a methodology for evaluating the compression of LiDAR data to a single point value, taking into account multiple parameters including compression rate, compression time, hardware specification/PC processing power, density of the point cloud etc.;
  • Test the proposed solution, i.e., 3DL, on point clouds used in other publications/public datasets.

6. Conclusions

This paper presents a new file format for containing LiDAR point clouds named 3DL. Following the strategies shown in Figure 1, the solution is instead of just archiving the cloud, it should be converted to a new format, achieving a smaller volume while leaving the data usable all the time. The solution was benchmarked against 21 other formats, which, with different parameters, yielded 100 comparative solutions. The reference parameters were CR (compression ratio in %) and CT (compression time in seconds).
The newly developed 3DL format that was validated achieves very good results in CR. For the ALS test files, it ranks second in group 2 (CR about 32%), i.e., converted formats, i.e., reduced but still usable, second only to the LAZ format. The LAZ format, which was designed by Martin Isenburg for ALS data, outclasses the competition with a CR score of 15%, i.e., an almost seven-fold reduction in file size through conversion. It is puzzling that despite the passage of more than 10 years, a better solution for ALS than the LAZ format has still not been developed. For the TLS samples, the best solution from group 2 is the new 3DL format (CR approx. 42%) for TLS_LOK and LAZ (CR approx. 37%) and 3DL (CR approx. 42%) for the TLS_PL2000 cloud. These results are all the more significant because only group 1 (archiving) formats, which consume energy in both compression and decompression, are better by ‘only’ 3–8 percentage points.
Admittedly, the compression methods used in the archivers (group 1) are more versatile (good for both ALS and TLS data), but their ‘dual’-energy requirements (compression and decompression) and significantly higher CT values exclude them from being the preferred or recommended solutions.
The current disadvantage of the solution presented (3DL) is the need to switch from LAS to POD, and then from POD to 3DL. It is planned to develop a one-step LAS to 3DL conversion in the future.
The authors hope that the results presented here will encourage other researchers to make greater use of geospatial data in the context of multidisciplinary analyses related to energy transition or space–environment relationships.

Author Contributions

Conceptualization, A.W. and M.B.; methodology, A.W. and M.B.; software, M.B.; validation, A.W., K.P. and M.B.; formal analysis, A.W. and K.P.; investigation A.W., K.P. and M.B.; resources, A.W.; data curation, A.W., K.P. and M.B.; writing—original draft preparation, A.W., K.P. and M.B.; writing—review and editing, A.W.; visualization, A.W. and K.P.; supervision, A.W.; project administration, A.W. and M.B.; funding acquisition: in develop *.3dl part—M.B., for compression evaluation: not applicable—no funds. All authors have read and agreed to the published version of the manuscript.

Funding

Research on the compression ratio comparison received no internal nor external funding. The research about the *.3dl file format was funded by The National Centre for Research and Development, grant number POIR.01.01.01-00-1283/17-00 named ‘Development of software to optimise the process of creating project documentation based on data obtained as a result of terrestrial laser scanning, with particular emphasis on simplifying access and interpretation possibilities of point clouds, as part of Activity 1.1: R&D projects of enterprises of the Operational Programme Intelligent Development 2014–2020, co-financed by the European Regional Development Fund’.

Data Availability Statement

The datasets presented in this article are not readily available because the data are part of an ongoing study.

Conflicts of Interest

Author Marek Baścik was employed by the 3Deling Sp z o.o. The remaining authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.

Appendix A

Table A1. Ranking of the results by the compression ratio (CR) for ALS_LOK (left) and ALS_PL2000 (right) LAS files.
Table A1. Ranking of the results by the compression ratio (CR) for ALS_LOK (left) and ALS_PL2000 (right) LAS files.
RankSoftwareFormat and MethodSize of FileCRRankSoftwareFormat and MethodSize of FileCR
1LASTOOLSLAZ 3280,739,47114.95%1LASTOOLSLAZ 3280,739,47114.95%
2LASTOOLSLAZ 6480,739,47114.95%2LASTOOLSLAZ 6480,739,47214.95%
37-ZIPxzLAZM2Ultra159,877,21629.60%37-ZIP7zUltraLZMA159,390,35229.51%
47-ZIP7zUltraLZMA2159,877,32829.60%47-ZIPzipUltraLZMA159,390,37829.51%
57-ZIP7zmaxLZMA160,070,59029.64%57-ZIP7zmaxLZMA2159,407,80729.51%
67-ZIPzipmaxLZMA160,070,61629.64%67-ZIPxzLAZM2max159,407,84429.51%
77-ZIP7znormalLZMA160,153,98429.65%77-ZIPxzLAZM2Ultra159,448,14029.52%
87-ZIPzipnormalLZMA160,154,01029.65%87-ZIP7zUltraLZMA2159,448,24429.52%
97-ZIPzipUltraLZMA160,175,95629.66%97-ZIP7znormalLZMA159,490,15029.53%
107-ZIPzipUltraLZMA160,175,98229.66%107-ZIPzipnormalLZMA159,490,17629.53%
117-ZIP7zmaxLZMA2160,243,50729.67%117-ZIP7zmaxLZMA159,550,36829.54%
127-ZIPxzLAZM2max160,243,54029.67%127-ZIPzipmaxLZMA159,550,39429.54%
137-ZIP7znormalLZMA2160,275,66829.68%137-ZIP7znormalLZMA2159,602,64929.55%
147-ZIPxzLAZM2normal160,275,83229.68%147-ZIPxzLAZM2normal159,602,82429.55%
153DL3dl3dlprecision < 1mm174,767,27532.36%15TRWLAZ 1.2168,516,89231.20%
16BEN PODCRpodpodprecision < 1 mm175,075,63132.42%163DL3dl3dlprecision < 1mm174,767,27532.36%
177-ZIP7zfastestLZMA183,312,95133.94%17BEN PODCRpodpodprecision < 1mm175,075,83932.42%
187-ZIPzipfastestLZMA183,312,97633.94%187-ZIP7zfastestLZMA182,774,24633.84%
197-ZIP7zfastestLZMA2183,853,13834.04%197-ZIPzipfastestLZMA182,774,27133.84%
207-ZIPxzLAZM2fastest183,867,72434.04%207-ZIP7zfastestLZMA2183,323,16333.94%
217-ZIPzipmaxPPMd185,262,78934.30%217-ZIPxzLAZM2fastest183,337,75233.95%
227-ZIP7zfastLZMA2186,484,08934.53%227-ZIPzipmaxPPMd184,133,35034.09%
237-ZIPxzLAZM2fast186,485,09234.53%237-ZIP7zfastLZMA2186,034,62934.44%
247-ZIP7zfastLZMA186,641,48334.56%247-ZIPxzLAZM2fast186,035,63634.44%
257-ZIPzipfastLZMA186,641,50834.56%257-ZIP7zfastLZMA186,190,50034.47%
267-ZIP7zmaxPPMd187,800,55134.77%267-ZIPzipfastLZMA186,190,52634.47%
277-ZIP7zUltraPPMd189,726,18235.13%277-ZIP7zmaxPPMd186,411,56134.51%
287-ZIP7znormalPPMd190,125,42035.20%287-ZIP7zUltraPPMd188,280,41734.86%
297-ZIPzipUltraPPMd190,493,73835.27%297-ZIP7znormalPPMd188,852,26034.97%
307-ZIPzipnormalPPMd190,995,84835.36%307-ZIPzipUltraPPMd189,254,44035.04%
31TRWLAZ 1.2191,352,29235.43%317-ZIPzipnormalPPMd189,864,69735.15%
32FMEE57 191,418,36835.44%32FMEE57 191,418,36835.44%
33FMEPOD 194,778,68936.06%337-ZIP7zfastPPMd194,180,49235.95%
347-ZIP7zfastPPMd195,636,29336.22%34FMEPOD 194,778,68936.06%
357-ZIPzipfastPPMd196,704,57036.42%357-ZIPzipfastPPMd195,052,75836.11%
36WINRARRAR6 normal201,400,39137.29%36WINRARRAR6 normal201,315,34237.27%
37WINRARRAR7 good201,603,52337.33%377-ZIPzipfastestPPMd201,395,80337.29%
38WINRARRAR8 the best201,657,80037.34%38WINRARRAR7 good201,516,35937.31%
397-ZIPzipfastestPPMd203,367,19937.65%39WINRARRAR8 the best201,573,12937.32%
407-ZIP7zfastestPPMd203,769,78637.73%407-ZIP7zfastestPPMd202,009,98237.40%
41WINRARRAR normal204,240,43937.82%41WINRARRAR normal204,164,12737.80%
42WINRARRAR good204,476,71737.86%42WINRARRAR good204,394,79537.84%
43WINRARRAR the best204,535,53937.87%43WINRARRAR the best204,453,74037.86%
447-ZIPbzip2BZip2Ultra208,120,04738.53%447-ZIPbzip2BZip2Ultra207,358,56138.39%
457-ZIP7zUltraBZip2208,120,21738.53%457-ZIP7zUltraBZip2207,358,72338.39%
467-ZIPzipUltraBZip2208,120,24338.53%467-ZIPzipUltraBZip2207,358,74938.39%
477-ZIPbzip2BZip2max208,137,20038.54%477-ZIPbzip2BZip2max207,373,86338.40%
487-ZIP7zmaxBZip2208,137,37038.54%487-ZIP7zmaxBZip2207,374,02538.40%
497-ZIPzipmaxBZip2208,137,39638.54%497-ZIPzipmaxBZip2207,374,05138.40%
507-ZIPbzip2BZip2normal208,164,85138.54%507-ZIPbzip2BZip2normal207,397,43238.40%
517-ZIP7znormalBZip2208,165,02138.54%517-ZIP7znormalBZip2207,397,59438.40%
527-ZIPzipnormalBZip2208,165,04738.54%527-ZIPzipnormalBZip2207,397,62038.40%
53WINRARRAR5 fast209,366,61738.76%53WINRARRAR5 fast209,285,47738.75%
547-ZIPbzip2BZip2fast210,506,41638.98%547-ZIPbzip2BZip2fast209,879,02038.86%
557-ZIP7zfastBZip2210,506,58638.98%557-ZIP7zfastBZip2209,879,18238.86%
567-ZIPzipfastBZip2210,506,61238.98%567-ZIPzipfastBZip2209,879,20838.86%
57WINRARRAR fast212,058,22939.26%57WINRARRAR fast212,071,73039.27%
58WINRARRAR4 fastest220,739,13040.87%58WINRARRAR4 fastest220,962,48740.91%
597-ZIPzipUltradeflate64220,788,07840.88%597-ZIPzipUltradeflate64221,692,57041.05%
607-ZIPzipmaxdeflate64220,825,08540.89%607-ZIPzipmaxdeflate64221,718,15741.05%
617-ZIPzipnormaldeflate64221,386,07540.99%617-ZIPzipnormaldeflate64222,247,61741.15%
627-ZIPbzip2BZip2fastest223,270,29341.34%627-ZIPbzip2BZip2fastest222,709,32441.24%
637-ZIP7zfastestBZip2223,270,46341.34%637-ZIP7zfastestBZip2222,709,48641.24%
647-ZIPzipfastestBZip2223,270,48941.34%647-ZIPzipfastestBZip2222,709,51241.24%
657-ZIPgzipdeflateUltra226,684,78541.97%657-ZIPgzipdeflateUltra228,289,36542.27%
667-ZIPzipUltradeflate226,684,93141.97%667-ZIPzipUltradeflate228,289,50742.27%
677-ZIPgzipdeflatemax226,737,42741.98%677-ZIPgzipdeflatemax228,334,71742.28%
687-ZIPzipmaxdeflate226,737,57341.98%687-ZIPzipmaxdeflate228,334,85942.28%
697-ZIPgzipdeflatenormal227,376,74542.10%697-ZIPgzipdeflatenormal228,933,50142.39%
707-ZIPzipnormaldeflate227,376,89142.10%707-ZIPzipnormaldeflate228,933,64342.39%
71WINRARZIP fastest237,750,59844.02%71FMEPNTS 238,277,66644.12%
72WINRARZIP fast237,816,54344.03%72WINRARZIP fastest238,994,68944.25%
73FMEPNTS 238,277,66644.12%73WINRARZIP fast239,071,43044.26%
74WINRARZIP normal238,397,78744.14%74WINRARZIP normal239,742,06844.39%
75WINRARZIP good239,149,51344.28%757-ZIPzipfastestdeflate64240,034,57844.44%
76WINRARZIP the best239,643,28244.37%767-ZIPzipfastdeflate64240,034,57844.44%
777-ZIPzipfastestdeflate64239,780,14644.40%77WINRARZIP good240,517,08144.53%
787-ZIPzipfastdeflate64239,780,14644.40%78WINRARZIP the best241,016,87644.62%
797-ZIPgzipdeflatefastest242,246,29344.85%797-ZIPgzipdeflatefastest242,853,84944.96%
807-ZIPzipfastestdeflate242,246,43944.85%807-ZIPzipfastestdeflate242,853,99144.96%
817-ZIPzipfastdeflate242,246,43944.85%817-ZIPzipfastdeflate242,853,99144.96%
82WINRARRAR fastest248,632,94746.03%82WINRARRAR fastest250,741,68546.43%
83CCPV 254,162,72047.06%83CCPV 254,162,72047.06%
84TRWPOD 291,032,70953.89%84TRWPOD 291,032,70953.89%
85CCE57 303,128,57656.12%85CCE57 303,128,57656.12%
86TRWASC 341,396,15963.21%86TRWRPC 361,845,80167.00%
87TRWRPC 361,845,85467.00%87CCPN 381,244,08070.59%
88CCPN 381,244,08070.59%88LASTOOLSBIN 32381,244,13670.59%
89LASTOOLSBIN 32381,244,13670.59%89LASTOOLSBIN 64381,244,13770.59%
90LASTOOLSBIN 64381,244,13670.59%90FMEBIN Terrascan444,784,81682.35%
91FMEBIN Terrascan444,784,81682.35%91TRWASC 460,669,93085.29%
92FMEXYZ TXT518,385,35895.98%92FMEXYZ TXT518,171,36395.94%
93CCLAS 540,096,007100.00%93CCLAS 540,096,007100.00%
94FMELAS 540,096,007100.00%94FMELAS 540,096,007100.00%
95FMEPCD 555,981,321102.94%95FMEPCD 555,981,333102.94%
96CCBIN 762,492,977141.18%96CCBIN 762,492,961141.18%
97TRWPTS 765,462,711141.73%97CCPCD 826,029,199152.94%
98CCPCD 826,029,199152.94%98TRWPTS 884,736,482163.81%
99LASTOOLSTXT 321,006,883,110186.43%99LASTOOLSTXT 321,126,156,881208.51%
100LASTOOLSTXT 641,006,883,110186.43%100LASTOOLSTXT 641,126,156,882208.51%
101CCTXT 2,175,726,572402.84%101CCTXT 2,295,000,343424.92%
Table A2. Ranking of results by compression ratio (CR) for TLS_LOK (left) and TLS_PL2000 (right) LAS files.
Table A2. Ranking of results by compression ratio (CR) for TLS_LOK (left) and TLS_PL2000 (right) LAS files.
RankSoftwareFormat and MethodSize of FileCRRankSoftwareFormat and MethodSize of FileCR
17-ZIPzipUltraPPMd218,230,54534.97%17-ZIPzipUltraPPMd212,636,60234.08%
27-ZIPzipmaxPPMd223,065,01835.75%27-ZIPzipmaxPPMd217,823,84734.91%
37-ZIP7zUltraPPMd224,523,52535.98%37-ZIP7zUltraPPMd219,035,45035.10%
47-ZIP7zmaxPPMd226,328,09136.27%47-ZIP7zmaxPPMd220,420,16935.33%
57-ZIP7znormalPPMd227,342,98136.43%57-ZIPzipnormalPPMd220,537,51435.34%
67-ZIPzipnormalPPMd227,860,18536.52%67-ZIP7znormalPPMd220,803,33435.39%
77-ZIP7zfastPPMd232,906,44437.33%77-ZIP7zfastPPMd224,313,53535.95%
87-ZIPzipfastPPMd234,031,03637.51%87-ZIPzipfastPPMd224,686,31736.01%
97-ZIPbzip2BZip2Ultra237,490,55038.06%97-ZIPbzip2BZip2Ultra228,102,31636.56%
107-ZIP7zUltraBZip2237,490,69638.06%107-ZIP7zUltraBZip2228,102,47836.56%
117-ZIPzipUltraBZip2237,490,72438.06%117-ZIPzipUltraBZip2228,102,50436.56%
127-ZIPbzip2BZip2max237,623,97338.08%127-ZIPbzip2BZip2max228,271,29536.58%
137-ZIP7zmaxBZip2237,624,11938.08%137-ZIP7zmaxBZip2228,271,45736.58%
147-ZIPzipmaxBZip2237,624,14738.08%147-ZIPzipmaxBZip2228,271,48336.58%
157-ZIPbzip2BZip2normal238,120,43638.16%157-ZIPbzip2BZip2normal228,833,45336.67%
167-ZIP7znormalBZip2238,120,58238.16%167-ZIP7znormalBZip2228,833,61536.67%
177-ZIPzipnormalBZip2238,120,61038.16%177-ZIPzipnormalBZip2228,833,64136.67%
187-ZIP7zUltraLZMA239,039,98538.31%187-ZIPbzip2BZip2fast230,580,80636.95%
197-ZIPzipUltraLZMA239,040,01238.31%197-ZIP7zfastBZip2230,580,96836.95%
207-ZIPxzLAZM2Ultra239,172,79238.33%207-ZIPzipfastBZip2230,580,99436.95%
217-ZIP7zUltraLZMA2239,172,88138.33%21LASTOOLSLAZ 32231,193,87337.05%
227-ZIP7zmaxLZMA240,303,86438.51%22LASTOOLSLAZ 64231,193,87437.05%
237-ZIPzipmaxLZMA240,303,89138.51%237-ZIP7zUltraLZMA234,336,98137.556%
247-ZIPbzip2BZip2fast240,660,23538.57%247-ZIPzipUltraLZMA234,337,00637.56%
257-ZIP7zfastBZip2240,660,38138.57%257-ZIPxzLAZM2Ultra234,389,61237.56%
267-ZIPzipfastBZip2240,660,40938.57%267-ZIP7zUltraLZMA2234,389,71537.564%
277-ZIP7zmaxLZMA2241,172,71038.65%277-ZIP7zmaxLZMA235,083,56937.68%
287-ZIPxzLAZM2max241,172,76838.65%287-ZIPzipmaxLZMA235,083,59437.68%
297-ZIP7znormalLZMA242,327,36438.84%297-ZIP7zmaxLZMA2235,481,72637.74%
307-ZIPzipnormalLZMA242,327,39138.84%307-ZIPxzLAZM2max235,481,76837.74%
317-ZIP7znormalLZMA2243,765,41239.07%317-ZIP7znormalLZMA235,862,30737.80%
327-ZIPxzLAZM2normal243,765,64039.07%327-ZIP7znormalLZMA2236,326,86737.87%
337-ZIPzipfastestPPMd245,806,17839.39%337-ZIPxzLAZM2normal236,327,08037.87%
347-ZIP7zfastestPPMd245,953,76439.42%347-ZIPzipfastestPPMd240,053,74238.47%
357-ZIPbzip2BZip2fastest262,281,19142.03%357-ZIP7zfastestPPMd240,472,12438.54%
367-ZIP7zfastestBZip2262,281,33742.03%36WINRARRAR the best241,656,15538.73%
377-ZIPzipfastestBZip2262,281,36542.03%37WINRARRAR good241,717,34638.74%
383DL3dl3dlPrec. < 1 mm263,998,19042.31%38WINRARRAR normal241,845,81338.76%
39BEN PODCRpodpodPrec. < 1 mm264,353,05242.37%39WINRARRAR fast242,338,90038.84%
407-ZIP7zfastLZMA279,901,19444.86%40WINRARRAR8 the best242,561,84438.87%
417-ZIPzipfastLZMA279,901,23744.86%41WINRARRAR7 good242,610,61738.88%
427-ZIP7zfastLZMA2280,523,70744.96%42WINRARRAR6 normal242,792,56038.91%
437-ZIPxzLAZM2fast280,524,90044.96%43WINRARRAR fastest243,294,99538.99%
44TRWLAZ 1.2285,072,89645.69%447-ZIPbzip2BZip2fastest247,376,59039.65%
457-ZIP7zfastestLZMA285,769,97845.80%457-ZIP7zfastestBZip2247,376,75239.65%
467-ZIPzipfastestLZMA285,770,02145.80%467-ZIPzipfastestBZip2247,376,77839.65%
477-ZIP7zfastestLZMA2287,664,58446.10%47TRWLAZ 1.2248,006,34939.75%
487-ZIPxzLAZM2fastest287,681,46446.10%483DL3dl3dlprecision < 1 mm263,998,28642.31%
49WINRARRAR the best287,906,67346.14%49BEN PODCRpodpodprecision < 1 mm264,352,84242.37%
50WINRARRAR good288,191,56046.19%507-ZIP7zfastLZMA270,716,76543.39%
51FMEPOD 288,775,70146.28%517-ZIPzipfastLZMA270,716,80643.39%
52WINRARRAR normal288,836,51646.29%527-ZIP7zfastLZMA2270,878,19143.41%
53FMEE57 289,189,88846.35%537-ZIPxzLAZM2fast270,879,36443.41%
54WINRARRAR fast290,661,57646.58%547-ZIP7zfastestLZMA271,351,33843.49%
55WINRARRAR8 the best290,754,61846.60%557-ZIPzipfastestLZMA271,351,37943.49%
56LASTOOLSLAZ 32290,783,95346.60%567-ZIP7zfastestLZMA2272,357,61643.65%
57LASTOOLSLAZ 64290,783,95446.60%577-ZIPxzLAZM2fastest272,374,49243.65%
58WINRARRAR7 good291,059,64746.65%58WINRARRAR5 fast288,590,52046.25%
59WINRARRAR6 normal291,820,03846.77%59FMEPOD 288,775,70146.28%
60WINRARRAR5 fast295,952,18547.43%60FMEE57 289,189,88846.35%
61WINRARRAR fastest308,882,76549.50%617-ZIPzipUltradeflate64298,177,16747.79%
627-ZIPzipUltradeflate64315,801,83350.61%627-ZIPzipmaxdeflate64298,197,83447.79%
637-ZIPzipmaxdeflate64315,802,56150.61%637-ZIPzipnormaldeflate64298,794,50347.89%
647-ZIPzipnormaldeflate64316,486,96350.72%647-ZIPgzipdeflateUltra303,984,84848.718%
657-ZIPgzipdeflateUltra326,872,23752.386%657-ZIPzipUltradeflate303,984,99048.72%
667-ZIPzipUltradeflate326,872,37252.39%667-ZIPgzipdeflatemax304,002,41348.72%
677-ZIPgzipdeflatemax326,904,83052.39%677-ZIPzipnormalLZMA304,002,55548.72%
687-ZIPzipmaxdeflate326,904,96552.39%687-ZIPzipmaxdeflate304,002,55548.72%
697-ZIPgzipdeflatenormal327,601,11652.50%697-ZIPgzipdeflatenormal304,665,24348.83%
707-ZIPzipnormaldeflate327,601,25152.50%707-ZIPzipnormaldeflate304,665,38548.83%
71WINRARRAR4 fastest337,918,43454.16%71WINRARZIP the best317,338,72250.86%
72WINRARZIP the best338,799,95654.30%72WINRARZIP good317,429,34250.87%
73WINRARZIP good338,998,62454.33%73WINRARRAR4 fastest317,688,95950.91%
74WINRARZIP normal339,856,86854.47%74WINRARZIP normal317,928,07950.95%
757-ZIPzipfastestdeflate64343,736,48355.09%757-ZIPzipfastestdeflate64322,368,46551.66%
767-ZIPzipfastdeflate64343,736,48355.09%767-ZIPzipfastdeflate64322,368,46551.66%
77WINRARZIP fast349,483,57156.01%777-ZIPgzipdeflatefastest324,863,93252.06%
787-ZIPgzipdeflatefastest351,633,35256.35%787-ZIPzipfastestdeflate324,864,07452.06%
797-ZIPzipfastestdeflate351,633,48756.35%797-ZIPzipfastdeflate324,864,07452.06%
807-ZIPzipfastdeflate351,633,48756.35%80WINRARZIP fast325,381,12952.15%
81WINRARZIP fastest352,152,58156.44%81WINRARZIP fastest326,916,72452.39%
82FMEPNTS 359,984,68157.69%82FMEPNTS 359,984,68157.69%
83CCPV 383,983,53661.54%83CCPV 383,983,53661.54%
84TRWPOD 432,896,04969.38%84TRWPOD 432,896,04969.38%
85TRWASC 449,596,22072.05%85CCE57 457,958,40073.39%
86CCE57 457,958,40073.39%86TRWRPC 471,190,24775.51%
87TRWRPC 471,210,40175.52%87LASTOOLSBIN 32479,979,47676.92%
88LASTOOLSBIN 32479,979,47676.92%88LASTOOLSBIN 64479,979,47776.92%
89LASTOOLSBIN 64479,979,47776.92%89CCPN 575,975,30492.31%
90CCPN 575,975,30492.31%90FMEBIN Terrascan575,975,36092.31%
91FMEBIN Terrascan575,975,36092.31%91FMELAS 623,973,473100.00%
92FMELAS 623,973,473100.00%92CCLAS 623,973,543100.00%
93CCLAS 623,973,543100.00%93FMEPCD 647,972,585103.85%
94FMEPCD 647,972,576103.85%94TRWASC 695,970,159111.54%
95FMEXYZ TXT717,143,511114.93%95CCBIN 767,969,989123.08%
96CCBIN 767,970,080123.08%96CCPCD 863,963,233138.46%
97CCPCD 863,963,233138.46%97FMEXYZ TXT951,340,542152.46%
98LASTOOLSTXT 321,029,311,815164.96%98LASTOOLSTXT 321,275,337,421204.39%
99LASTOOLSTXT 641,029,311,816164.96%99LASTOOLSTXT 641,275,337,422204.39%
100TRWPTS 1,049,110,606168.13%100TRWPTS 1,295,504,598207.62%
101CCTXT 2,082,519,220333.75%101CCTXT 2,328,913,212373.24%

Appendix B

Table A3. Ranking of the results by the compression time (CT) for ALS_LOK (left) and ALS_PL2000 (right) LAS files.
Table A3. Ranking of the results by the compression time (CT) for ALS_LOK (left) and ALS_PL2000 (right) LAS files.
RankSoftwareFormat and MethodCTRankSoftwareFormat and MethodCT
1CCPV 11CCBIN 1
2FMELAS 12CCPN 1
3FMEE57 13FMELAS 1
4FMEPNTS 14FMEPCD 1
5FMEPCD 15LASTOOLSBIN 322
6LASTOOLSBIN 3226LASTOOLSBIN 642
7LASTOOLSBIN 6427CCPV 2
8CCBIN 28FMEBIN Terrascan 2
9CCPN 29WINRARRAR4 fastest 3
10FMEBIN Terrascan 210FMEE57 3
11CCE57 311WINRARRAR fastest 4
12WINRARRAR fastest 412LASTOOLSLAZ 325
13WINRARRAR4 fastest 413LASTOOLSLAZ 645
14WINRARZIP fastest 514CCE57 5
15WINRARZIP fast515CCLAS 5
16LASTOOLSLAZ 32516FMEPOD 5
17LASTOOLSLAZ 64517WINRARZIP fastest 6
18FMEPOD 518WINRARZIP fast6
197-ZIP7zfastestLZMA2819CCPCD 6
207-ZIPxzLAZM2fastest8207-ZIP7zfastestLZMA28
21WINRARZIP normal8217-ZIPxzLAZM2fastest8
22WINRARZIP good 822WINRARZIP normal8
23WINRARZIP the best823WINRARZIP good 8
24CCLAS 824WINRARZIP the best9
25BEN PODCR podpodprecision < 1 mm925BEN PODCR podpodprecision < 1mm9
26CCPCD 1026FMEPNTS 9
27FMEXYZ 10277-ZIP7zfastestBZip211
287-ZIP7zfastestBZip211287-ZIPbzip2BZip2fastest11
297-ZIPbzip2BZip2fastest11297-ZIPgzipdeflatefastest11
307-ZIPgzipdeflatefastest11307-ZIPzipfastestdeflate11
317-ZIPzipfastestdeflate11317-ZIPzipfastestBZip211
327-ZIPzipfastestBZip211327-ZIPzipfastestdeflate6412
337-ZIPzipfast deflate11337-ZIPzipfast deflate12
347-ZIPzipfastestdeflate641234WINRARRAR5 fast12
357-ZIPzipfast deflate641235FMEXYZ TXT12
36WINRARRAR5 fast12367-ZIP7zfast BZip213
377-ZIP7zfast BZip213377-ZIPbzip2BZip2fast13
387-ZIPzipfast BZip213387-ZIPzipfast deflate6413
397-ZIP7zfast LZMA214397-ZIPzipfast BZip213
407-ZIPbzip2BZip2fast14407-ZIP7zfast LZMA214
417-ZIPxzLAZM2fast 14417-ZIPxzLAZM2fast 14
427-ZIP7znormal BZip216427-ZIP7znormal BZip216
437-ZIPbzip2BZip2normal 16437-ZIPbzip2BZip2normal 16
447-ZIPzipnormal BZip21744WINRARRAR fast17
45WINRARRAR fast1745WINRARRAR6 normal17
46WINRARRAR6 normal17467-ZIPzipnormal BZip218
47WINRARRAR7 good 2047WINRARRAR7 good 19
48WINRARRAR8 the best2148WINRARRAR8 the best21
497-ZIPzipfastestLZMA24497-ZIP7zfastestLZMA24
507-ZIP7zfastestLZMA25507-ZIPzipfastestLZMA25
51WINRARRAR normal2651WINRARRAR normal25
52TRWASC 2852WINRARRAR good 34
53WINRARRAR good 33533DL3dl3dlprecision < 1mm34
543DL3dl3dlprecision < 1 mm3454TRWASC 37
55WINRARRAR the best3955WINRARRAR the best39
567-ZIP7zmax BZip242567-ZIPbzip2BZip2max 40
577-ZIPbzip2BZip2max 42577-ZIPzipmax BZip241
587-ZIPzipmax BZip243587-ZIP7zmax BZip243
597-ZIPgzipdeflatenormal 47597-ZIP7zfastestPPMd47
607-ZIPzipnormal deflate47607-ZIPgzipdeflatenormal 47
617-ZIP7zfastestPPMd49617-ZIPzipnormal deflate47
627-ZIP7zfast PPMd51627-ZIP7zfast PPMd50
637-ZIPzipfastestPPMd5363TRWLAZ 1.251
64 LAZ 1.254647-ZIPzipfastestPPMd52
657-ZIP7znormal LZMA255657-ZIP7znormal LZMA254
667-ZIPxzLAZM2normal 55667-ZIPxzLAZM2normal 54
677-ZIPzipnormal deflate645567LASTOOLSTXT 3258
68LASTOOLSTXT 325768LASTOOLSTXT 6458
69LASTOOLSTXT 6457697-ZIPzipfast PPMd59
707-ZIPzipfast PPMd5970CCTXTASCII Cloud 61
717-ZIP7zfast LZMA63717-ZIP7znormal PPMd63
727-ZIPzipfast LZMA63727-ZIPzipfast LZMA63
737-ZIP7znormal PPMd65737-ZIP7zfast LZMA64
74CCTXT 68747-ZIPzipnormal deflate6469
757-ZIP7zmax LZMA269757-ZIPzipnormal PPMd72
767-ZIP7zmax PPMd96767-ZIP7zmax PPMd94
777-ZIPxzLAZM2max 96777-ZIP7zmax LZMA295
787-ZIPgzipdeflatemax 99787-ZIPxzLAZM2max 95
797-ZIPzipmax deflate102797-ZIPgzipdeflatemax 98
80 PTS 109807-ZIPzipmax deflate98
817-ZIPzipmax deflate64114817-ZIPzipmax deflate64113
827-ZIP7zUltra PPMd118827-ZIP7zUltra PPMd117
837-ZIPzipnormal PPMd13483TRWPTS 123
847-ZIPbzip2BZip2Ultra 139847-ZIP7znormal LZMA140
857-ZIP7zUltra BZip2142857-ZIPzipnormal LZMA142
867-ZIPzipnormal LZMA142867-ZIPzipUltra BZip2142
877-ZIP7znormal LZMA143877-ZIP7zUltra BZip2147
887-ZIPzipUltra BZip2150887-ZIPbzip2BZip2Ultra 152
897-ZIP7zmax LZMA163897-ZIP7zmax LZMA160
907-ZIPzipmax LZMA164907-ZIPzipmax LZMA162
917-ZIP7zUltra LZMA196917-ZIPxzLAZM2Ultra 196
927-ZIPxzLAZM2Ultra 197927-ZIP7zUltra LZMA197
937-ZIPzipUltra LZMA200937-ZIPzipUltra LZMA197
947-ZIP7zUltra LZMA2201947-ZIP7zUltra LZMA2199
957-ZIPzipmax PPMd225957-ZIPzipmax PPMd222
967-ZIPgzipdeflateUltra 249967-ZIPgzipdeflateUltra 245
977-ZIPzipUltra deflate249977-ZIPzipUltra deflate245
987-ZIPzipUltra PPMd250987-ZIPzipUltra PPMd251
997-ZIPzipUltra deflate64275997-ZIPzipUltra deflate64266
100TRWPOD 514100TRWPOD 492
101TRWRPC 2655101TRWRPC 2521
Table A4. Ranking of the results by the compression time (CT) for TLS_LOK (left) and TLS_PL2000 (right) LAS files.
Table A4. Ranking of the results by the compression time (CT) for TLS_LOK (left) and TLS_PL2000 (right) LAS files.
RankSoftwareFormat and MethodCTRankSoftwareFormat and MethodCT
1CCBIN 11FMEPCD 1
2CCPN 12CCPN 2
3FMELAS 13CCPV 2
4FMEPCD 14FMELAS 2
5LASTOOLSBIN 3225FMEBIN Terrascan 2
6LASTOOLSBIN 6426LASTOOLSBIN 323
7CCPV 27LASTOOLSBIN 643
8FMEE57 38FMEE57 3
9FMEBIN Terrascan 39CCBIN 4
10WINRARRAR4 fastest 410WINRARRAR fastest 5
11CCLAS 411CCE57 5
12FMEPNTS 412CCLAS 5
13CCE57 513CCPCD 5
14WINRARRAR fastest 614WINRARZIP fastest 7
15CCPCD 615WINRARZIP fast7
16WINRARZIP fastest 716LASTOOLSLAZ 327
17WINRARZIP fast717LASTOOLSLAZ 647
18WINRARZIP normal818FMEPNTS 7
19WINRARZIP the best819WINRARZIP normal9
20LASTOOLSLAZ 32820WINRARZIP good 9
21LASTOOLSLAZ 648217-ZIP7zfastestLZMA210
22WINRARZIP good 9227-ZIPxzLAZM2fastest10
237-ZIPxzLAZM2fastest1023WINRARZIP the best10
247-ZIP7zfastestLZMA21124FMEPOD 10
25FMEPOD 11257-ZIP7zfastestBZip212
267-ZIP7zfastestBZip214267-ZIPbzip2BZip2fastest12
277-ZIPbzip2BZip2fastest14277-ZIPzipfastestBZip213
287-ZIPzipfastestBZip21428WINRARRAR6 normal13
29WINRARRAR5 fast1429WINRARRAR7 good 13
30BEN PODCR podpodprecision < 1mm1430WINRARRAR8 the best13
317-ZIPzipfast LZMA1531WINRARRAR5 fast14
32WINRARRAR6 normal1632BEN PODCRpodpodprecision < 1mm14
33FMEXYZ TXT1633WINRARRAR fast15
347-ZIP7zfast BZip21734WINRARRAR normal15
357-ZIPbzip2BZip2fast1735WINRARRAR good 16
367-ZIPgzipdeflatefastest1736WINRARRAR the best16
377-ZIPzipfastestdeflate1737FMEXYZ 16
387-ZIPzipfast deflate17387-ZIP7zfast LZMA217
397-ZIPzipfast BZip217397-ZIP7zfast BZip217
407-ZIPxzLAZM2fast 18407-ZIPbzip2BZip2fast17
41WINRARRAR fast18417-ZIPgzipdeflatefastest17
427-ZIP7zfast LZMA219427-ZIPzipfastestdeflate17
43WINRARRAR7 good 19437-ZIPzipfast deflate17
447-ZIPzipfastestdeflate6420447-ZIPzipfast BZip217
457-ZIPzipfast deflate6420457-ZIPxzLAZM2fast 18
46WINRARRAR8 the best20467-ZIPzipfastestdeflate6419
477-ZIP7znormal BZip222477-ZIPzipfast deflate6420
487-ZIPzipnormal BZip222487-ZIPbzip2BZip2normal 21
497-ZIPbzip2BZip2normal 23497-ZIP7znormal BZip222
50WINRARRAR normal23507-ZIPzipnormal BZip222
51WINRARRAR good 29517-ZIP7zfastestLZMA31
52WINRARRAR the best32527-ZIPzipfastestLZMA31
537-ZIP7zfastestLZMA3353WINRARRAR4 fastest 33
547-ZIPzipfastestLZMA33543DL3dl3dlprecision < 1 mm46
55TRWASC ASCII46557-ZIPbzip2BZip2max 48
563DL3dl3dlprecision < 1 mm46567-ZIP7zmax BZip250
577-ZIP7zmax BZip252577-ZIPzipmax BZip251
587-ZIPzipmax BZip253587-ZIP7zfastestPPMd54
59TRWLAZ 1.253597-ZIP7zfast PPMd56
607-ZIPbzip2BZip2max 54607-ZIPzipfastestPPMd58
617-ZIP7zfastestPPMd5561TRWASC 59
62CCTXT 59627-ZIPzipfast PPMd62
637-ZIP7zfast PPMd60637-ZIPgzipdeflatenormal 65
647-ZIPgzipdeflatenormal 60647-ZIPzipnormal deflate65
657-ZIPzipnormal deflate6065CCTXT 65
667-ZIPzipfastestPPMd61667-ZIP7zfast LZMA71
677-ZIPzipfast PPMd66677-ZIPzipfast LZMA71
68LASTOOLSTXT 326868LASTOOLSTXT 3272
69LASTOOLSTXT 646869LASTOOLSTXT 6472
707-ZIPzipnormal deflate6471707-ZIP7znormal LZMA275
717-ZIP7zfast LZMA75717-ZIPxzLAZM2normal 75
727-ZIP7znormal PPMd75727-ZIPzipnormal deflate6475
737-ZIP7znormal LZMA280737-ZIPzipnormal PPMd79
747-ZIPxzLAZM2normal 81747-ZIP7znormal PPMd87
757-ZIPzipnormal PPMd84757-ZIP7zmax PPMd114
767-ZIPgzipdeflatemax 121767-ZIPgzipdeflatemax 128
777-ZIPzipmax deflate123777-ZIPzipmax deflate128
787-ZIP7zmax PPMd124787-ZIPzipnormal LZMA129
79TRWPTS 130797-ZIP7zmax LZMA2130
807-ZIPxzLAZM2max 138807-ZIPxzLAZM2max 130
817-ZIPzipmax deflate64138817-ZIPzipmax deflate64144
82TRWPOD 146827-ZIP7zUltra PPMd148
837-ZIP7zUltra PPMd15483TRWPOD 152
847-ZIP7zUltra BZip218484TRWPTS 156
857-ZIP7znormal LZMA185857-ZIPzipUltra BZip2161
867-ZIPzipnormal LZMA186867-ZIPbzip2BZip2Ultra 168
877-ZIPbzip2BZip2Ultra 187877-ZIP7zUltra BZip2171
887-ZIP7zmax LZMA2199887-ZIP7znormal LZMA176
897-ZIPzipUltra BZip2212897-ZIPzipmax PPMd181
907-ZIP7zmax LZMA219907-ZIP7zmax LZMA210
917-ZIPzipmax PPMd220917-ZIPzipmax LZMA214
927-ZIPzipmax LZMA229927-ZIPzipUltra PPMd243
937-ZIP7zUltra LZMA271937-ZIP7zUltra LZMA2258
947-ZIPxzLAZM2Ultra 275947-ZIPxzLAZM2Ultra 258
957-ZIP7zUltra LZMA2276957-ZIP7zUltra LZMA262
967-ZIPgzipdeflateUltra 296967-ZIPzipUltra LZMA263
977-ZIPzipUltra PPMd311977-ZIPzipUltra deflate306
987-ZIPzipUltra LZMA330987-ZIPgzipdeflateUltra 307
997-ZIPzipUltra deflate348997-ZIPzipUltra deflate64329
1007-ZIPzipUltra deflate64352100TRWLAZ 1.2403
101TRWRPC 15,604101TRWRPC 10,149

References

  1. Kocifaj, M.; Wallner, S.; Barentine, J.C. Measuring and Monitoring Light Pollution: Current Approaches and Challenges. Science 2023, 380, 1121–1124. [Google Scholar] [CrossRef] [PubMed]
  2. Sala, K. Zanieczyszczenie Świetlne. Zagrożenia i Sposoby Jego Ograniczania. Rocz. Adm. Publicznej 2020, 6, 254–266. [Google Scholar] [CrossRef]
  3. Erwinski, K.; Karpinska, D.; Kunz, M.; Paprocki, M.; Czokow, J. An Autonomous City-Wide Light Pollution Measurement Network System Using LoRa Wireless Communication. Sensors 2023, 23, 5084. [Google Scholar] [CrossRef] [PubMed]
  4. Gajdzik, B.; Awdziej, M.; Jaciow, M.; Lipowska, I.; Lipowski, M.; Szojda, G.; Tkaczyk, J.; Wolniak, R.; Wolny, R.; Grebski, W.W. Encouraging Residents to Save Energy by Using Smart Transportation: Incorporating the Propensity to Save Energy into the UTAUT Model. Energies 2024, 17, 5341. [Google Scholar] [CrossRef]
  5. Kelly Kissock, J.; Eger, C. Measuring Industrial Energy Savings. Appl. Energy 2008, 85, 347–361. [Google Scholar] [CrossRef]
  6. Madlool, N.A.; Saidur, R.; Rahim, N.A.; Kamalisarvestani, M. An Overview of Energy Savings Measures for Cement Industries. Renew. Sustain. Energy Rev. 2013, 19, 18–29. [Google Scholar] [CrossRef]
  7. Tommerup, H.; Svendsen, S. Energy Savings in Danish Residential Building Stock. Energy Build. 2006, 38, 618–626. [Google Scholar] [CrossRef]
  8. Gajdzik, B.; Wolniak, R.; Grebski, W.W. An Econometric Model of the Operation of the Steel Industry in POLAND in the Context of Process Heat and Energy Consumption. Energies 2022, 15, 7909. [Google Scholar] [CrossRef]
  9. de Groot, H.L.F.; Verhoef, E.T.; Nijkamp, P. Energy Saving by Firms: Decision-Making, Barriers and Policies. Energy Econ. 2001, 23, 717–740. [Google Scholar] [CrossRef]
  10. Chirarattananon, S.; Chaiwiwatworakul, P.; Hien, V.D.; Rakkwamsuk, P.; Kubaha, K. Assessment of Energy Savings from the Revised Building Energy Code of Thailand. Energy 2010, 35, 1741–1753. [Google Scholar] [CrossRef]
  11. Gajdzik, B.; Jaciow, M.; Hoffmann-Burdzińska, K.; Wolny, R.; Wolniak, R.; Grebski, W.W. Impact of Economic Awareness on Sustainable Energy Consumption: Results of Research in a Segment of Polish Households. Energies 2024, 17, 2483. [Google Scholar] [CrossRef]
  12. Hamilton, I.G.; Summerfield, A.J.; Shipworth, D.; Steadman, J.P.; Oreszczyn, T.; Lowe, R.J. Energy Efficiency Uptake and Energy Savings in English Houses: A Cohort Study. Energy Build. 2016, 118, 259–276. [Google Scholar] [CrossRef]
  13. Rong, H.; Zhang, H.; Xiao, S.; Li, C.; Hu, C. Optimizing Energy Consumption for Data Centers. Renew. Sustain. Energy Rev. 2016, 58, 674–691. [Google Scholar] [CrossRef]
  14. Xie, N.; Dong, G.; Zhang, T. Using Lossless Data Compression in Data Storage Systems: Not for Saving Space. IEEE Trans. Comput. 2011, 60, 335–345. [Google Scholar] [CrossRef]
  15. Lintner, W.; Tschudi, B.; Van Geet, O. Best Practices Guide for Energy-Efficient Data Center Design; U.S. Department of Energy: Washington, DC, USA, 2011; p. i-24. [Google Scholar]
  16. Teng, S.Y.; Touš, M.; Leong, W.D.; How, B.S.; Lam, H.L.; Máša, V. Recent Advances on Industrial Data-Driven Energy Savings: Digital Twins and Infrastructures. Renew. Sustain. Energy Rev. 2021, 135, 110208. [Google Scholar] [CrossRef]
  17. Tomczak, A.; Kogut, T.; Kabała, K.; Abramowski, T.; Ciążela, J.; Giza, A. Automated Estimation of Offshore Polymetallic Nodule Abundance Based on Seafloor Imagery Using Deep Learning. Sci. Total Environ. 2024, 956, 177225. [Google Scholar] [CrossRef] [PubMed]
  18. Tysiac, P.; Janowski, A.; Walacik, M. UAV Measurements and AI-Driven Algorithms Fusion for Real Estate Good Governance Principles Support. Int. J. Appl. Earth Obs. Geoinf. 2024, 134, 104229. [Google Scholar] [CrossRef]
  19. Szopińska, K.; Cienciała, A.; Bieda, A.; Kwiecień, J.; Kulesza, Ł.; Parzych, P. Verification of the Perception of the Local Community Concerning Air Quality Using ADMS-Roads Modeling. Int. J. Environ. Res. Public Health 2022, 19, 10908. [Google Scholar] [CrossRef]
  20. Balawejder, M.; Warchoł, A.; Konttinen, K. Energy Efficiency in Agricultural Production—Experience from Land Consolidation in Poland and Finland. Energies 2023, 16, 7598. [Google Scholar] [CrossRef]
  21. Basista, I.; Balawejder, M.; Kuchta, A. A Land Consolidation Geoportal As a Useful Tool in Land Consolidation Projects—A Case Study of Villages in Southern Poland. Acta Sci. Pol. Adm. Locorum 2023, 22, 453–469. [Google Scholar] [CrossRef]
  22. Su, Y.; Jin, Q.; Zhang, S.; He, S. A Review on the Energy in Buildings: Current Research Focus and Future Development Direction. Heliyon 2024, 10, e32869. [Google Scholar] [CrossRef] [PubMed]
  23. Kardoš, M.; Sačkov, I.; Tomaštík, J.; Basista, I.; Borowski, Ł.; Ferenčík, M. Elevation Accuracy of Forest Road Maps Derived from Aerial Imaging, Airborne Laser Scanning and Mobile Laser Scanning Data. Forests 2024, 15, 840. [Google Scholar] [CrossRef]
  24. Busko, M.; Balawejder, M.; Kovalyshyn, O.; Apollo, M. Do Geographic Location and Historical Conditions Affect the Quality and Availability of Open Cadastral Data? From Early Cadastral Maps till Now. Reports Geod. Geoinform. 2023, 116, 23–38. [Google Scholar] [CrossRef]
  25. Grzelka, K.; Bydłosz, J.; Bieda, A. Analysis of the Prospects for the Development of 3D Cadastral Visualisation. Acta Sci. Pol. Adm. Locorum 2023, 22, 45–57. [Google Scholar] [CrossRef]
  26. Bydłosz, J.; Bieda, A. Developing a Uml Model for the 3d Cadastre in Poland. Land 2020, 9, 466. [Google Scholar] [CrossRef]
  27. Filepné Kovács, K.; Varga, D.; Kukulska-Kozieł, A.; Cegielska, K.; Noszczyk, T.; Husar, M.; Iváncsics, V.; Ondrejicka, V.; Valánszki, I. Policy Instruments as a Trigger for Urban Sprawl Deceleration: Monitoring the Stability and Transformations of Green Areas. Sci. Rep. 2024, 14, 2666. [Google Scholar] [CrossRef]
  28. Kładź, M.; Borkowski, A.S. Using BIM for the Development of Accessibility. Bud. I Archit. 2024, 23, 5–13. [Google Scholar] [CrossRef]
  29. Klapa, P.; Gawronek, P. Synergy of Geospatial Data from TLS and UAV for Heritage Building Information Modeling (HBIM). Remote Sens. 2023, 15, 128. [Google Scholar] [CrossRef]
  30. Borkowski, A.S.; Kochański, Ł.; Wyszomirski, M. A Case Study on Building Information (BIM) and Land Information (LIM) Models Including Geospatial Data. Geomat. Environ. Eng. 2023, 17, 19–34. [Google Scholar] [CrossRef]
  31. Gawronek, P.; Noszczyk, T. Does More Mean Better? Remote-Sensing Data for Monitoring Sustainable Redevelopment of a Historical Granary in Mydlniki, Kraków. Herit. Sci. 2023, 11, 23. [Google Scholar] [CrossRef]
  32. Markiewicz, J.; Górecka, K.; Zawieska, D.; Zieliński, M.; Łapiński, S.; Kot, P. The Integration of the Multi-Temporal Conservation Works and Non-Invasive Measurements. Int. Arch. Photogramm. Remote Sens. Spat. Inf. Sci.—ISPRS Arch. 2022, 46, 343–349. [Google Scholar] [CrossRef]
  33. Bielska, A.; Łuczyński, R.; Sajnóg, N.; Mikulska, K.S. Use of Public Registers for Selected Solutions within the Smart Villages Concept. GIS Odyssey J. 2022, 2, 25–37. [Google Scholar] [CrossRef]
  34. Bielska, A.; Stańczuk-Gałwiaczek, M.; Sobolewska-Mikulska, K.; Mroczkowski, R. Implementation of the Smart Village Concept Based on Selected Spatial Patterns—A Case Study of Mazowieckie Voivodeship in Poland. Land Use Policy 2021, 104, 105366. [Google Scholar] [CrossRef]
  35. Balawejder, M.; Matkowska, K.; Colak, H.E. The Impact of Surveying Works on the Development of Smart City. In Proceedings of the 25th Anniversary Conference Geographic Information Systems Conference and Exhibition “GIS ODYSSEY 2018”, Perugia, Italy, 10–14 September 2018; pp. 20–32. [Google Scholar]
  36. Cienciała, A.; Sajnóg, N.; Sobolewska-Mikulska, K. Unreliability of Cadastral Data on Parcel Area and Its Effect on Sustainable Real Estate Valuation. Rep. Geod. Geoinform. 2023, 116, 39–46. [Google Scholar] [CrossRef]
  37. Szopińska, K.; Krajewska, M.; Bieda, A.; Blistan, P. Prioritization of Source Data Necessary for the Valuation of Real Estate with Mineral Deposits: The Case of Poland. Acta Montan. Slovaca 2024, 29, 436–452. [Google Scholar] [CrossRef]
  38. Wajs, J.; Trybała, P.; Górniak-Zimroz, J.; Krupa-Kurzynowska, J.; Kasza, D. Modern Solution for Fast and Accurate Inventorization of Open-Pit Mines by the Active Remote Sensing Technique—Case Study of Mikoszów Granite Mine (Lower Silesia, SW Poland). Energies 2021, 14, 6853. [Google Scholar] [CrossRef]
  39. Szafarczyk, A.; Gawałkiewicz, R. An Inventory of Opencast Mining Excavations Recultivated in the Form of Water Reservoirs as an Example of Activities Increasing the Retention Potential of the Natural Environment: A Case Study from Poland. Geol. Geophys. Environ. 2023, 49, 401–418. [Google Scholar] [CrossRef]
  40. Krzepek, K.; Günther, A.; Huth, V.; Jansen, F.; Iwaszczuk, D. The Influence of Vegetation on Sentinel-1 Intensity Time Series Using NDVI and In-Situ Data in Peatlands: A Case Study. In Proceedings of the IGARSS 2024–2024 IEEE International Geoscience and Remote Sensing Symposium, Athens, Greece, 7–12 July 2024; pp. 4775–4778. [Google Scholar]
  41. Szeląg, B.; Sobura, S.; Stoińska, R. Application of Multispectral Images from Unmanned Aerial Vehicles to Analyze Operations of a Wastewater Treatment Plant. Energies 2023, 16, 2871. [Google Scholar] [CrossRef]
  42. Przewoźna, P.; Inglot, A.; Mielewczyk, M.; Maczka, K.; Matczak, P. Accessibility to Urban Green Spaces: A Critical Review of WHO Recommendations in the Light of Tree-Covered Areas Assessment. Ecol. Indic. 2024, 166, 112548. [Google Scholar] [CrossRef]
  43. Pukanská, K.; Bartoš, K.; Gašinec, J.; Pašteka, R.; Zahorec, P.; Papčo, J.; Kseňak, Ľ.; Bella, P.; Andrássy, E.; Dušeková, L.; et al. Measurement of Spatio-Temporal Changes of Cave Ice Using Geodetic and Geophysical Methods: Dobšiná Ice Cave, Slovakia. Cryosphere Discuss. 2023, 1–29. [Google Scholar] [CrossRef]
  44. Kogut, T.; Wancel, D.; Stępień, G.; Smuga-Kogut, M.; Szostak, M.; Całka, B. Risk of Tree Fall on High-Traffic Roads: A Case Study of the S6 in Poland. Appl. Sci. 2024, 14, 4479. [Google Scholar] [CrossRef]
  45. Kogut, T.; Tomczak, A.; Słowik, A.; Oberski, T. Seabed Modelling by Means of Airborne Laser Bathymetry Data and Imbalanced Learning for Offshore Mapping. Sensors 2022, 22, 3121. [Google Scholar] [CrossRef]
  46. Gorgoglione, L.; Malinverni, E.S.; Smaniotto Costa, C.; Pierdicca, R.; Di Stefano, F. Exploiting 2D/3D Geomatics Data for the Management, Promotion, and Valorization of Underground Built Heritage. Smart Cities 2023, 6, 12. [Google Scholar] [CrossRef]
  47. Mitka, B.; Klapa, P.; Gniadek, J. Use of Terrestrial Laser Scanning for Measurements of Wind Power Stations. Geomat. Environ. Eng. 2019, 13, 39–49. [Google Scholar] [CrossRef]
  48. Stałowska, P.; Suchocki, C.; Zagubień, A. Application of Terrestrial Laser Scanning Measurements for Wind Turbine Blade Condition Surveying. Metrol. Meas. Syst. 2023, 30, 403–422. [Google Scholar] [CrossRef]
  49. Będkowski, J. End to End Navigation Stack for Nuclear Power Plant Inspection with Mobile Robot. SoftwareX 2024, 26, 101750. [Google Scholar] [CrossRef]
  50. Ogólnopolskie Sympozjum Naukowe PTFiT "Zdalne Metody Pomiarowe dla Potrzeb Modelowania 3D. 2014. Available online: https://ptfit.sgp.geodezja.org.pl/wp-content/uploads/2014/09/komunikat_4_PTFiT_2014.pdf (accessed on 10 November 2024).
  51. Statista. Available online: https://www.statista.com/statistics/871513/worldwide-data-created (accessed on 10 November 2024).
  52. Apollo, M.; Jakubiak, M.; Nistor, S.; Lewinska, P.; Krawczyk, A.; Borowski, Ł.; Specht, M.; Krzykowska-Piotrowska, K.; Marchel, Ł.; Pęska-Siwik, A.; et al. Geodata in Science—A Review of Selected Scientific Fields. Acta Sci. Pol. Form. Circumiectus 2023, 22, 17–40. [Google Scholar] [CrossRef]
  53. Wadowska, A.; Pęska-Siwik, A.; Maciuk, K. Problems of Collecting, Processing and Sharing Geospatial Data. Acta Sci. Pol. Form. Circumiectus 2022, 21, 5–16. [Google Scholar] [CrossRef]
  54. Warchoł, A.; Balawejder, M. The Use of Orthophotomaps to Verify the Network of Agricultural Transport Roads in the Land Consolidation Project. In Proceedings of the FIG Congress 2022 Volunteering for the Future—Geospatial Excellence for a Better living, Warsaw, Poland, 1–15 September 2022. [Google Scholar]
  55. Bakuła, K.; Kurczyński, Z. Generowanie Referencyjnego Numerycznego Modelu Terenu o Zasięgu Krajowym w Oparciu o Lotnicze Skanowanie Laserowe w Projekcie ISOK. Arch. Fotogram. Kartogr. I Teledetekcji 2013, 59–68. Available online: http://ptfit.sgp.geodezja.org.pl/wydawnictwa/monografia/09-Kurczynski.pdf (accessed on 10 November 2024).
  56. Wódka, M.; Kamieniarz, S.; Wojciechowski, T.; Ucka, M.P.; Perski, Z.; Sikora, R.; Karwacki, K.; Jureczka, J.; Onek, W.N.A.D.; Krieger, W.; et al. Post-Mining deformations in the Area Affected by the former “Siersza” Hard Coal Mine in Trzebinia (Southern Poland). Geol. Q. 2024, 68, 1–20. [Google Scholar]
  57. Suba, N.-S.; Bydłosz, J.; Sturza, A.A.; Dragomir, E.I. Interpolation Method Consistency Analysis in the Creation of Digital Terrain Models. J. Appl. Eng. Sci. 2024, 14, 161–166. [Google Scholar] [CrossRef]
  58. Sobura, S.; Kapusta, Ł. Assesing the Potential of Digital Terrain Models for Monitoring Additional Subsidence of Communication Embankments in Mining Areas—A Case Study Ocena Możliwości Numerycznych Modeli Terenu Do Monitorowania Dodatkowych Obniżeń Nasypów Komunikacyjnych Na T. Struct. Environ. 2024, 16, 84–96. [Google Scholar] [CrossRef]
  59. Inglot, A.; Tysiac, P. Airborne Laser Scanning Point Cloud Update by Used of the Terrestrial Laser Scanning and the Low-Level Aerial Photogrammetry. In Proceedings of the 2017 Baltic Geodetic Congress (BGC Geomatics), Gdansk, Poland, 22–25 June 2017; pp. 34–38. [Google Scholar]
  60. Wang, D.; Puttonen, E.; Casella, E. PlantMove: A Tool for Quantifying Motion Fields of Plant Movements from Point Cloud Time Series. Int. J. Appl. Earth Obs. Geoinf. 2022, 110, 102781. [Google Scholar] [CrossRef]
  61. Krok, G.; Kraszewski, B.; Stereńczak, K. Application of Terrestrial Laser Scanning in Forest Inventory—An Overview of Selected Issues. For. Res. Pap. 2020, 81, 175–194. [Google Scholar] [CrossRef]
  62. Wężyk, P.; Hawryło, P.; Szostak, M.; Zięba-Kulawik, K.; Winczek, M.; Siedlarczyk, E.; Kurzawiński, A.; Rydzyk, J.; Kmiecik, J.; Gilewski, W.; et al. Using LiDAR Point Clouds in Determination of the Scots Pine Stands Spatial Structure Meaning in the Conservation of Lichen Communities in “Bory Tucholskie” National Park. Arch. Photogramm. Cartogr. Remote Sens. 2019, 31, 85–103. [Google Scholar] [CrossRef]
  63. Balestra, M.; Marselis, S.; Sankey, T.T.; Cabo, C.; Liang, X.; Mokroš, M.; Peng, X.; Singh, A.; Stereńczak, K.; Vega, C.; et al. LiDAR Data Fusion to Improve Forest Attribute Estimates: A Review. Curr. For. Rep. 2024, 10, 281–297. [Google Scholar] [CrossRef]
  64. Sobura, S.; Bacharz, K.; Granek, G. Analysis of two-option integration of unmanned aerial vehicle and terrestrial laser scanning data for historical architecture inventory. Geod. Cartogr. 2023, 49, 76–87. [Google Scholar] [CrossRef]
  65. Warchoł, A. Analysis of Possibilities to Registration TLS Point Clouds without Targets on the Example of the Castle Bridge in Rzeszów. In Proceedings of the International Multidisciplinary Scientific GeoConference Surveying Geology and Mining Ecology Management (SGEM 2015), Albena, Bulgaria, 18–24 June 2015. [Google Scholar]
  66. Markiewicz, J. Evaluation of 2D Affine—Hand-Crafted Detectors for Feature-Based TLS Point Cloud Registration. Reports Geod. Geoinform. 2024, 117, 69–88. [Google Scholar] [CrossRef]
  67. Damięcka-Suchocka, M.; Katzer, J.; Suchocki, C. Application of TLS Technology for Documentation of Brickwork Heritage Buildings and Structures. Coatings 2022, 12, 1963. [Google Scholar] [CrossRef]
  68. Wu, C.; Yuan, Y.; Tang, Y.; Tian, B. Application of Terrestrial Laser Scanning (Tls) in the Architecture, Engineering and Construction (Aec) Industry. Sensors 2022, 22, 265. [Google Scholar]
  69. Stałowska, P.; Suchocki, C.; Rutkowska, M. Crack Detection in Building Walls Based on Geometric and Radiometric Point Cloud Information. Autom. Constr. 2022, 134, 104065. [Google Scholar] [CrossRef]
  70. Róg, M.; Rzonca, A. The Impact of Photo Overlap, the Number of Control Points and the Method of Camera Calibration on the Accuracy of 3d Model Reconstruction3. Geomat. Environ. Eng. 2021, 15, 67–87. [Google Scholar] [CrossRef]
  71. Gruner, F.; Romanschek, E.; Wujanz, D.; Clemen, C. Co-Registration of Tls Point Clouds With Scan-Patches and Bim-Faces. Int. Arch. Photogramm. Remote Sens. Spat. Inf. Sci.—ISPRS Arch. 2022, 46, 109–114. [Google Scholar] [CrossRef]
  72. Skrzypczak, I.; Oleniacz, G.; Leśniak, A.; Zima, K.; Mrówczyńska, M.; Kazak, J.K. Scan-to-BIM Method in Construction: Assessment of the 3D Buildings Model Accuracy in Terms Inventory Measurements. Build. Res. Inf. 2022, 50, 859–880. [Google Scholar] [CrossRef]
  73. Borkowski, A.S.; Kubrat, A. Integration of Laser Scanning, Digital Photogrammetry and BIM Technology: A Review and Case Studies. Eng 2024, 5, 2395–2409. [Google Scholar] [CrossRef]
  74. Blachowski, J.; Wajs, J.; Walerysiak, N.; Becker, M. Monitoring of Post-Mining Subsidence Using Airborne and Terrestrial Laser Scanning Approach. Arch. Min. Sci. 2024, 69, 431–446. [Google Scholar] [CrossRef]
  75. Bieda, A.; Balawejder, M.; Warchoł, A.; Bydłosz, J.; Kolodiy, P.; Pukanská, K. Use of 3D Technology in Underground Tourism: Example of Rzeszow (Poland) and Lviv (Ukraine). Acta Montan. Slovaca 2021, 26, 205–221. [Google Scholar] [CrossRef]
  76. Bydłosz, J.; Warchoł, A.; Balawejder, M.; Bieda, A. Practical Verification of Polish 3D Cadastral Model. In Proceedings of the 7th International FIG Workshop on 3D Cadastres, New York, NY, USA, 11–13 October 2021; pp. 185–206. [Google Scholar]
  77. Di Stefano, F.; Chiappini, S.; Gorreja, A.; Balestra, M.; Pierdicca, R. Mobile 3D Scan LiDAR: A Literature Review. Geomat. Nat. Hazards Risk 2021, 12, 2387–2429. [Google Scholar]
  78. Warchoł, A.; Karaś, T.; Antoń, M. Selected Qualitative Aspects of Lidar Point Clouds: Geoslam Zeb-Revo and Faro Focus 3D X130. Int. Arch. Photogramm. Remote Sens. Spat. Inf. Sci.—ISPRS Arch. 2023, 48, 205–212. [Google Scholar] [CrossRef]
  79. Wysocki, O.; Hoegner, L.; Stilla, U. MLS2LoD3: Refining Low LoDs Building Models with MLS Point Clouds to Reconstruct Semantic LoD3 Building Models. In Recent Advances in 3D Geoinformation Science; Springer Nature: Cham, Switzerland, 2024; pp. 367–380. [Google Scholar]
  80. Guan, H.; Li, J.; Yu, Y.; Wang, C.; Chapman, M.; Yang, B. Using Mobile Laser Scanning Data for Automated Extraction of Road Markings. ISPRS J. Photogramm. Remote Sens. 2014, 87, 93–107. [Google Scholar] [CrossRef]
  81. Rutzinger, M.; Elberink, S.O.; Pu, S.; Vosselman, G. Automatic Extraction of Vertical Walls from Mobile and Airborne Laser Scanning Data. Geoinf. Sci. 2009, XXXVIII, 7–11. [Google Scholar]
  82. Liang, X.; Hyyppa, J.; Kukko, A.; Kaartinen, H.; Jaakkola, A.; Yu, X. The Use of a Mobile Laser Scanning System for Mapping Large Forest Plots. IEEE Geosci. Remote Sens. Lett. 2014, 11, 1504–1508. [Google Scholar] [CrossRef]
  83. Rutzinger, M.; Pratihast, A.K.; Oude Elberink, S.J.; Vosselman, G. Tree Modelling from Mobile Laser Scanning Data-Sets. Photogramm. Rec. 2011, 26, 361–372. [Google Scholar] [CrossRef]
  84. Adamek, A.; Będkowski, J.; Kamiński, P.; Pasek, R.; Pełka, M.; Zawiślak, J. Method for Underground Mining Shaft Sensor Data Collection. Sensors 2024, 24, 4119. [Google Scholar] [CrossRef] [PubMed]
  85. Zhang, H.; Mao, S.; Li, M. A Coal Mine Excavation Tunnels Modeling Method Based on Point Clouds. Appl. Sci. 2024, 14, 9454. [Google Scholar] [CrossRef]
  86. Mitka, B.; Klapa, P.; Gawronek, P. Laboratory Tests of Metrological Characteristics of a Non-Repetitive Low-Cost Mobile Handheld Laser Scanner. Sensors 2024, 24, 6010. [Google Scholar] [CrossRef]
  87. Trybała, P.; Kasza, D.; Wajs, J.; Remondino, F. Comparison of Low-Cost Handheld Lidar-Based Slam Systems for Mapping Underground Tunnels. Int. Arch. Photogramm. Remote Sens. Spat. Inf. Sci.—ISPRS Arch. 2023, 48, 517–524. [Google Scholar] [CrossRef]
  88. Kędziorski, P.; Jagoda, M.; Tysiąc, P.; Katzer, J. An Example of Using Low-Cost LiDAR Technology for 3D Modeling and Assessment of Degradation of Heritage Structures and Buildings. Materials 2024, 17, 5445. [Google Scholar] [CrossRef] [PubMed]
  89. Ali, T.A. Compression of LiDAR Data Using Spatial Clustering and Optimal Plane-Fitting. Adv. Remote Sens. 2013, 02, 58–62. [Google Scholar] [CrossRef]
  90. Isenburg, M. LASzip. Photogramm. Eng. Remote Sens. 2013, 79, 209–217. [Google Scholar] [CrossRef]
  91. Rapidlasso Laszip—Background. Available online: https://rapidlasso.de/laszip/ (accessed on 10 November 2024).
  92. Mongus, D.; Žalik, B. Efficient Method for Lossless LIDAR Data Compression. Int. J. Remote Sens. 2011, 32, 2507–2518. [Google Scholar] [CrossRef]
  93. Li, X.; Zeng, W.; Duan, Y. Geometry Based Airborne Lidar Data Compression. In Proceedings of the 2013 IEEE International Conference on Multimedia and Expo (ICME), San Jose, CA, USA, 15–19 July 2013. [Google Scholar]
  94. Jóźków, G.; Toth, C.; Quirk, M.; Grejner-Brzezinska, D. Study on Sensor Level LiDAR Waveform Data Compression Using JPEG-2000 Standard Multi-Component Transform. Photogramm.-Fernerkund.-Geoinf. 2015, 2015, 201–213. [Google Scholar] [CrossRef]
  95. Abdelwahab, M.M.; El-Deeb, W.S.; Youssif, A.A.A. LIDAR Data Compression Challenges and Difficulties. In Proceedings of the 2019 5th International Conference on Frontiers of Signal Processing (ICFSP), Marseille, France, 18–20 September 2019; pp. 111–116. [Google Scholar] [CrossRef]
  96. Kotb, A.; Hassan, S.; Hassan, H. A Comparative Study among Various Algorithms for Lossless Airborne LiDAR Data Compression. In Proceedings of the 2018 14th International Computer Engineering Conference (ICENCO), Cairo, Egypt, 29–30 December 2018; pp. 17–21. [Google Scholar] [CrossRef]
  97. Będkowski, J. Open Source, Open Hardware Hand-Held Mobile Mapping System for Large Scale Surveys. SoftwareX 2024, 25, 101618. [Google Scholar] [CrossRef]
  98. Siejek, M.; Kasza, D.; Wajs, J. Methodology of Spatial Data Acquisition and Development of High-Definition Map for Autonomous Vehicles—Case Study from Wrocław, Poland. Civ. Environ. Eng. Rep. 2024, 34, 87–103. [Google Scholar] [CrossRef]
  99. Maksymova, I.; Steger, C. Extended Delta Compression Algorithm for Scanning LiDAR Raw Data Handling. In Proceedings of the 2nd Workshop on Proximity Perception 2019 IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS 2019), Macau, China, 8 November 2019. [Google Scholar]
  100. Zhou, X.; Qi, C.R.; Zhou, Y.; Anguelov, D. RIDDLE: Lidar Data Compression with Range Image Deep Delta Encoding. In Proceedings of the IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR), New Orleans, LA, USA, 18–24 June 2022; pp. 1–19. [Google Scholar]
  101. Tu, C.; Takeuchi, E.; Carballo, A.; Takeda, K. Point Cloud Compression for 3d Lidar Sensor Using Recurrent Neural Network with Residual Blocks. In Proceedings of the 2019 International Conference on Robotics and Automation (ICRA), Montreal, QC, Canada, 20–24 May 2019; pp. 3274–3280. [Google Scholar] [CrossRef]
  102. Mollah, M.P.; Debnath, B.; Sankaradas, M.; Chakradhar, S.; Mueen, A. Efficient Compression Method for Roadside LiDAR Data. In Proceedings of the 31st ACM International Conference on Information & Knowledge Managem, Atlanta, GA, USA, 17–21 October 2022; pp. 3371–3380. [Google Scholar] [CrossRef]
  103. Kolda, T.G.; Bader, B.W. Tensor Decompositions and Applications. SIAM Rev. 2009, 51, 455–500. [Google Scholar] [CrossRef]
  104. Oh, S.; Park, N.; Lee, S.; Kang, U. Scalable Tucker Factorization for Sparse Tensors-Algorithms and Discoveries. In Proceedings of the 2018 IEEE 34th International Conference on Data Engineering (ICDE), Paris, France, 16–19 April 2018; pp. 1132–1143. [Google Scholar] [CrossRef]
  105. Feng, Y.; Liu, S.; Zhu, Y. Real-Time Spatio-Temporal LiDAR Point Cloud Compression. In Proceedings of the 2020 IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS), Las Vegas, NV, USA, 24 October 2020–24 January 2021; pp. 10766–10773. [Google Scholar] [CrossRef]
  106. Roriz, R.; Silva, H.; Dias, F.; Gomes, T. A Survey on Data Compression Techniques for Automotive LiDAR Point Clouds. Sensors 2024, 24, 3185. [Google Scholar] [CrossRef] [PubMed]
  107. van Beek, P. Image-Based Compression of Lidar Sensor Data. IS T Int. Symp. Electron. Imaging Sci. Technol. 2019, 31, 43-1–43-7. [Google Scholar] [CrossRef]
Figure 1. Workflow of tasks in the LiDAR point cloud data storage strategy.
Figure 1. Workflow of tasks in the LiDAR point cloud data storage strategy.
Energies 17 06413 g001
Figure 2. Visualisation by RGB values of the point clouds used for the survey. (A) Top view and (C) Vertical cross-section of an ALS point cloud; (B) top view and (D) vertical cross-section of a TLS point cloud.
Figure 2. Visualisation by RGB values of the point clouds used for the survey. (A) Top view and (C) Vertical cross-section of an ALS point cloud; (B) top view and (D) vertical cross-section of a TLS point cloud.
Energies 17 06413 g002
Table 1. Overview of LiDAR point clouds in the LAS files used to conducting the research.
Table 1. Overview of LiDAR point clouds in the LAS files used to conducting the research.
Name of FileALS_LOKALS_PL2000TLS_LOKTLS_PL2000
Horizontal CSLocal CSEPSG:2178Local CSEPSG:2178
File formatLAS 1.2LAS 1.2LAS 1.2LAS 1.2
Size of file
[byte]
540,096,009540,096,009623,973,543623,973,545
Number of points15,885,17015,885,17023,998,97123,998,971
min X−600.00007,474,400.0000−135.01897,474,864.9811
max X199.99007,475,199.9900147.88517,475,147.8851
min Y100.00005,638,000.0000−78.88515,639,921.1149
max Y599.99005,638,499.9900186.22845,640,186.2284
min H267.2700267.2700115.4018115.4018
max H359.5100359.5100184.3779184.3779
min INT373764256425
max INT4404440465,27965,279
Line++++
Echo++++
Color (RGB)++++
Time (GPS)++--
Scanner++++
Angle++++
Coords Prec.0.00010.00010.00010.0001
Span by X799.9900799.9900282.9040282.9040
Span by Y499.9900499.9900265.1135265.1135
Span by H92.240092.240068.976168.9761
Span by INT4367436758,85458,854
Bytes per point34342626
Table 2. Hardware units used to preparing conversions.
Table 2. Hardware units used to preparing conversions.
UnitABC
CPU11th Gen Intel® Core™ i5-1135G7 @2.40 GHz 2.42 Ghz (Intel, Santa Clara, CA USA)AMD Ryzen 5 2600 Six-Core 3.40 GHz (AMD, Santa Clara, CA USA)Intel(R) Core(TM) i7-7800X CPU @ 3.50 GHz
RAM8 GB32 GB128 GB
OSWindows 11 Home 64Windows 10 Pro 64Windows 10 Pro 64
TypelaptopPCPC
Table 4. Statistics characterizing the results obtained in terms of the compression rate (CR) and compression time (CT) for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
Table 4. Statistics characterizing the results obtained in terms of the compression rate (CR) and compression time (CT) for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
ALS_LOKALS_PL2000TLS_LOKTLS_PL2000
CR
[%]
CT
[s]
CR
[%]
CT
[s]
CR
[%]
CT
[s]
CR
[%]
CT
[s]
min.14.95%1.014.95%1.034.97%1.034.08%1.0
max.402.84%2655.0424.92%2521.0333.75%15,604.0373.24%10,149.0
avg.51.71%87.652.74%85.757.97%227.658.18%172.5
median38.54%26.038.40%25.046.28%29.043.39%31.0
std. dev.46.71%270.850.27%257.539.11%1548.046.96%1006.5
Table 5. Top 10 solutions for the CR chosen from Table A1 and Table A2 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
Table 5. Top 10 solutions for the CR chosen from Table A1 and Table A2 for all four base files: ALS_LOK, ALS_PL2000, TLS_LOK and TLS_PL2000.
RankSoftwareFormat and MethodCRSoftwareFormat and MethodCRSoftwareFormat and MethodCRSoftwareFormat and MethodCR
1LASTOOLS LAZ 3214.95%LASTOOLSLAZ 3214.95%7-ZIPzipUltra PPMd34.97%7-ZIPzipUltra PPMd34.08%
2LASTOOLSLAZ 6414.95%LASTOOLSLAZ 6414.95%7-ZIPzipmax PPMd35.75%7-ZIPzipmax PPMd34.91%
37-ZIPxzLAZM2Ultra 29.60%7-ZIP7zUltra LZMA29.51%7-ZIP7zUltra PPMd35.98%7-ZIP7zUltra PPMd35.10%
47-ZIP7zUltra LZMA229.60%7-ZIPzipUltra LZMA29.51%7-ZIP7zMax PPMd36.27%7-ZIP7zmaxPPMd35.33%
57-ZIP7zMax LZMA29.64%7-ZIP7zMax LZMA229.51%7-ZIP7zNormal PPMd36.43%7-ZIPzipNormal PPMd35.34%
67-ZIPzipMaxLZMA29.64%7-ZIPxzLAZM2Max29.51%7-ZIPzipNormal PPMd36.52%7-ZIP7zNormal PPMd35.39%
77-ZIP7zNormal LZMA29.65%7-ZIPxzLAZM2Ultra 29.52%7-ZIP7zFastPPMd37.33%7-ZIP7zFastPPMd35.95%
87-ZIPzipNormal LZMA29.65%7-ZIP7zUltra LZMA229.52%7-ZIPzipFastPPMd37.51%7-ZIPzipFastPPMd36.01%
97-ZIPzipUltra LZMA29.66%7-ZIP7zNormal LZMA29.53%7-ZIPbzip2BZip2Ultra 38.06%7-ZIPbzip2BZip2Ultra 36.56%
107-ZIPzipUltra LZMA29.66%7-ZIPzipNormal LZMA29.53%7-ZIP7zUltra BZip238.06%7-ZIP7zUltra BZip236.56%
Table 9. Comparison of the CR results of the current study with the literature values.
Table 9. Comparison of the CR results of the current study with the literature values.
LAZZIPRAR
Isenburg15.6%50.0%22.2%
Kotb16.6%39.3%20.2%
AW2014 Poznan19.7%46.5%42.6%
this research
ALS14.9%33.3%34.0%44.3%39.8%38.3%
TLS41.8%42.7%43.8%53.3%42.9%45.5%
from LASTOOLSfrom TRWfrom 7-ZIPfrom WINRARRAR
from WINRAR
RAR4
from WINRAR
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content.

Share and Cite

MDPI and ACS Style

Warchoł, A.; Pęzioł, K.; Baścik, M. Energy-Saving Geospatial Data Storage—LiDAR Point Cloud Compression. Energies 2024, 17, 6413. https://doi.org/10.3390/en17246413

AMA Style

Warchoł A, Pęzioł K, Baścik M. Energy-Saving Geospatial Data Storage—LiDAR Point Cloud Compression. Energies. 2024; 17(24):6413. https://doi.org/10.3390/en17246413

Chicago/Turabian Style

Warchoł, Artur, Karolina Pęzioł, and Marek Baścik. 2024. "Energy-Saving Geospatial Data Storage—LiDAR Point Cloud Compression" Energies 17, no. 24: 6413. https://doi.org/10.3390/en17246413

APA Style

Warchoł, A., Pęzioł, K., & Baścik, M. (2024). Energy-Saving Geospatial Data Storage—LiDAR Point Cloud Compression. Energies, 17(24), 6413. https://doi.org/10.3390/en17246413

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop