Zero Bounding Box - Githubissues

Moving this discussion to its own thread: https://github.com/potree/PotreeConverter/issues/421#issuecomment-671675523

@elixirml please send me the las or laz file that causes this issue so that I can take a look at it. (mschuetz@potree.org)

hello @m-schuetz in this link you can find the .las file with which we are trying to convert to a point cloud

https://drive.google.com/file/d/1UQfnx-M1Z4nDIiM15GcPDxgMN1ZWIE9v/view?usp=sharing

we have tried to convert using Converter.exe C:\Users\Big\las\2.las -o C:\Users\Big\conv\2 also Converter.exe C:\Users\Big\las\2.las -rescale 0.0001 0.0001 0.0001 -o C:\Users\Big\conv\2 but we couldn't finish the process

we are using the following hardware:

Intel Core i3 2.13Ghz, 2 cores, 4 threads 6 Gb Ram Windows 10 Pro Potreeconverter 2.0

the output is as follows >>

flags:
#paths: 1

output attributes:
name                              offset    size
================================================
position                               0      12
intensity                             12       2
return number                         14       1
number of returns                     15       1
classification flags                  16       1
classification                        17       1
user data                             18       1
scan angle                            19       2
point source id                       21       2
gps-time                              23       8
rgb                                   31       6
================================================
                                              37
================================================
cubicAABB: {
        "min": [0.000000, 0.000000, 0.000000],
        "max": [0.000000, 0.000000, 0.000000],
        "size": [0.000000, 0.000000, 0.000000]
}
#points: 9'104'949
total file size: 312.6 MB
maxPointsPerChunk: 455247

=======================================
=== COUNTING
=======================================
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
tStartTaskAssembly: 0.000998s
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
[26%, 1s], [COUNTING: 77%, duration: 1s, throughput: 7MPs][RAM: 0WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
.1GB (highest 0.1GB), CPU: 69%]
countPointsInCells: 1.224424s
finished counting in 1s
=======================================
createLUT: 0.088526s

=======================================
=== CREATING CHUNKS
=======================================
distributePoints0: 0.000212s
distributePoints1: 0.002898s
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
[33%, 2s], [DISTRIBUTING: 0%, duration: 0s, throughput: -na'n(i'nd)MPs][RAM: 0.3GB (highest 0.3GB), CPU: 71%]

C:\Users\Big\PotreeConverter_2.0_windows_x64>

any comment will be of great help Thank you very much for your time best regards

Hi, I don't have a functional understanding of this but I've encountered the issue. This seems to be a LAS 1.3 or 1.4 format file. When opening with the LAS 1.3/1.4 importer in cloudcompare (rather than the standard LAS importer) I can save it as a standard LAZ file and it works fine in PotreeConverter 2 (file attached).

PDAL's "translate" command gives a similar error for this cloud:

(pdal translate readers.las Error) Global encoding WKT flag not set for point format 6 - 10.
PDAL: readers.las: Unsupported LAS input point format: 7.

https://drive.google.com/file/d/1z0sMDmM15pZrlLfr_U1HYCXkaVor2586/view?usp=sharing

@elixirml were there supposed to be other attributes? The cloudcompare process left it with RGB only.

@elixirml Just a point of clarification. When Markus suggested the rescale workaround, it was directed towards a different user experiencing a different problem. Also, it required a separate piece of software from LAS tools called las2las. Notice the different executable in the command line: las2las -i crash.las -rescale 0.0001 0.0001 0.0001 -o no_crash.las - this is not using the converter.

Someone correct me if I'm wrong, but the converter only has a few tags that it accepts as arguments, namely the following:

-i YOUR_INPUT_FILE -o YOUR_OUTPUT_LOCATION -m CONVERTER_METHOD

There is no -rescale flag, so using this wouldn't have a positive result. I'd advise against submitting flags that aren't supported. But absolutely give it a go with the las2las tool if you think scale is part of the problem.

By the way, you can make output easier to read on GitHub if you wrap it with three backticks (```) at the beginning and end. This will prevent GitHub from modifying the format or making text larger when a hash is at the beginning of a line.

I wish I could be of some help here, but I have yet to see this occur and I'm not sure what it's catching on. If I don't lose power due to the hurricanes, I'll spin up a debugger Monday or Tuesday.

Hi, I think your las file is "broken". Report by lasinfo:

  scale factor x y z:         0.0000000041866 0.000000003956875 0.000000004512207
  offset x y z:               6.657199859619141 -0.156700000166893 2941.326416015625
  min x y z:                  0 0 0
  max x y z:                  0 0 0
WARNING: stored resolution of min_x not compatible with x_offset and x_scale_factor: 0
WARNING: stored resolution of min_y not compatible with y_offset and y_scale_factor: 0
WARNING: stored resolution of min_z not compatible with z_offset and z_scale_factor: 0
WARNING: stored resolution of max_x not compatible with x_offset and x_scale_factor: 0
WARNING: stored resolution of max_y not compatible with y_offset and y_scale_factor: 0
WARNING: stored resolution of max_z not compatible with z_offset and z_scale_factor: 0
...
WARNING: real max x larger than header max x by 10.843800
WARNING: real max y larger than header max y by 3.800175
WARNING: real min y smaller than header min y by 0.156700
WARNING: real max z larger than header max z by 2945.838623

The las metadata claims that the bounding box is zero. However, PotreeConverter heavily relies on correct bounding box data for the octree generation. It seems like lasinfo with the -repair argument could be used to compute the correct bounding box.

And you might also have to rescale in addition to repairing the bounding box, until the new PotreeConverter release with automatic rescaling is published

las2las -i crash.las -rescale 0.0001 0.0001 0.0001 -o no_crash.las

More issues:

The las file says it uses version 1.2, but it specifies point data record format 7. Las version 1.2 does not have point record format 7.
Format 7 has a minimum size of 36 bytes but in your las file, points have a size of only 30 bytes.

You'll need to make your las file standard compliant.

hello friends, Thank you very much for your clarifications, advice and dedication to this topic. We will try to work with las2las too;)

We can instruct the design area to correctly export the .las file to try again, but I would appreciate it if you could please indicate some technical considerations when exporting the new .las file and thus generate one that is compatible with the standard.

Soon I will write to you with the new results. Thank you very much for your time Best regards

What exactly is your process to generate LAS point clouds? It would be helpful to see relevant settings and commands (if using command line tools). Do all of the point clouds you generate suffer from this broken state? Also, did you generate your LAS file using the core i3 system with limited RAM?

We can instruct the design area to correctly export the .las file to try again, but I would appreciate it if you could please indicate some technical considerations when exporting the new .las file and thus generate one that is compatible with the standard.

If you're using your own las exporter, try running lasinfo on it, it usually catches many of the main issues of non-conforming las files. And then there is the spec itself, which is relatively intelligible: https://www.asprs.org/wp-content/uploads/2010/12/LAS_1_4_r13.pdf

Edit: The issue with the duplicates isn't against the standard but such a large amount of duplicates indicate some issue with the data set or exporter, so they should be dealt with anyway.

@m-schuetz Regarding the edit:

The issue with the duplicates isn't against the standard but such a large amount of duplicates indicate some issue with the data set or exporter, so they should be dealt with anyway.

Does this case also involve a large amount of duplicates? I thought that was mainly clouds in #427 like with millions of points near the absolute center. The hallmarks of this one are the mismatched point sizes for the point type declared & the strange zero sized bounding box. Just for documentation sake, did you also find a ton of points on top of each other?

@midnight-dev Ah you're right, I was confusing this with #427. No duplicates in this issue.

hello Friends We have carefully followed all the advice listed above. As a result, I comment that we carry out new tests with 2 files:

3.las (1.1 GB.)
4.las (20 Mb)

the steps to follow with both files were the following:

1.- lasinfo -i file_orig.las 2.- las2las -i file_orig.las -rescale 0.0001 0.0001 0.0001 -o file_no_crash.las 3.- lasinfo -i file_no_crash.las 4.- lasinfo -i file_no_crash.las -repair 5.- lasinfo -i file_no_crash.las 6.- Converter.exe file_no_crash.las -o C:\Users\Big\conv 7.- Exit

The conversion of the 4.las file was successful, but when looking in the viewfinder, its color was a bit diffuse black (capture attached). On the other hand the conversion of the 3.las file did not finish.

Below is the detail of the conversion outputs of file 3 and 4 respectively:

console output 3.las

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>lasinfo -i C:\Users\Big\las\3.las

WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
lasinfo (200813) report for 'C:\Users\Big\las\3.las'
reporting all LAS header entries:
  file signature:             'LASF'
  file source ID:             0
  global_encoding:            0
  project ID GUID data 1-4:   00000000-0000-0000-0000-000000000000
  version major.minor:        1.2
  system identifier:          ''
  generating software:        ''
  file creation day/year:     0/0
  header size:                227
  offset to point data:       227
  number var. length records: 0
  point data format:          7
  point data record length:   30
  number of point records:    29625116
  number of points by return: 0 0 0 0 0
  scale factor x y z:         0.0000000228479 0.0000000217133 0.00000001303186
  offset x y z:               -13.521200180053711 -13.324399948120117 1035.885986328125
  min x y z:                  0 0 0
  max x y z:                  0 0 0
WARNING: stored resolution of min_x not compatible with x_offset and x_scale_factor: 0
WARNING: stored resolution of min_y not compatible with y_offset and y_scale_factor: 0
WARNING: stored resolution of min_z not compatible with z_offset and z_scale_factor: 0
WARNING: stored resolution of max_x not compatible with x_offset and x_scale_factor: 0
WARNING: stored resolution of max_y not compatible with y_offset and y_scale_factor: 0
WARNING: stored resolution of max_z not compatible with z_offset and z_scale_factor: 0
reporting minimum and maximum for all LAS point record entries ...
  X                   0  999999999
  Y                   0 1000000000
  Z                   0  999999999
  intensity           0          0
  return_number       1          1
  number_of_returns   1          1
  edge_of_flight_line 0          0
  scan_direction_flag 0          0
  classification      0          0
  scan_angle_rank     0          0
  user_data           0          0
  point_source_ID     0          0
  gps_time 0.000000 0.000000
  Color R 0 65280
        G 0 65280
        B 0 65280
  extended_return_number          1      1
  extended_number_of_returns      1      1
  extended_classification         0      0
  extended_scan_angle             0      0
  extended_scanner_channel        0      0
WARNING: 29625116 points outside of header bounding box
number of first returns:        29625116
number of intermediate returns: 0
number of last returns:         29625116
number of single returns:       29625116
WARNING: point type is 7 but (legacy) number of point records in header is 29625116 instead zero.
overview over number of returns of given pulse: 29625116 0 0 0 0 0 0
histogram of classification of points:
        29625116  never classified (0)
WARNING: real max x larger than header max x by 9.326700
WARNING: real min x smaller than header min x by 13.521200
WARNING: real max y larger than header max y by 8.388900
WARNING: real min y smaller than header min y by 13.324400
WARNING: real max z larger than header max z by 1048.917847

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>las2las -i C:\Users\Big\las\3.las -rescale 0.0001 0.0001 0.0001 -o C:\Users\Big\conv\3\3_no_crash.las

WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>lasinfo -i C:\Users\Big\conv\3\3_no_crash.las

WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
lasinfo (200813) report for 'C:\Users\Big\conv\3\3_no_crash.las'
reporting all LAS header entries:
  file signature:             'LASF'
  file source ID:             0
  global_encoding:            0
  project ID GUID data 1-4:   00000000-0000-0000-0000-000000000000
  version major.minor:        1.2
  system identifier:          'LAStools (c) by rapidlasso GmbH'
  generating software:        'las2las (version 200813)'
  file creation day/year:     0/0
  header size:                227
  offset to point data:       227
  number var. length records: 0
  point data format:          7
  point data record length:   30
  number of point records:    0
  number of points by return: 0 0 0 0 0
  scale factor x y z:         0.0001 0.0001 0.0001
  offset x y z:               -13.521200180053711 -13.324399948120117 1035.885986328125
  min x y z:                  -13.5212 -13.3244 1035.8860
  max x y z:                  -13.5212 -13.3244 1035.8860

tStartTaskAssembly: 0.000899s
countPointsInCells: 0.029626s
finished counting in 0s
=======================================
createLUT: 0.078962s

=======================================
=== CREATING CHUNKS
=======================================
distributePoints0: 0.000214s
distributePoints1: 0.002157s
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
finished creating chunks in 0s
=======================================

=======================================
=== INDEXING
=======================================

tStartTaskAssembly: 0.001146s
countPointsInCells: 0.016172s
finished counting in 0s
=======================================
createLUT: 0.085859s

=======================================
=== CREATING CHUNKS
=======================================
distributePoints0: 0.000220s
distributePoints1: 0.002199s
WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36
finished creating chunks in 0s
=======================================

=======================================
=== INDEXING
=======================================

At this point the process ended abruptly

Console output 4.las

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>lasinfo -i C:\Users\Big\las\4.las

lasinfo (200813) report for 'C:\Users\Big\las\4.las'
reporting all LAS header entries:
  file signature:             'LASF'
  file source ID:             0
  global_encoding:            0
  project ID GUID data 1-4:   00000000-0000-0000-0000-000000000000
  version major.minor:        1.2
  system identifier:          'libLAS'
  generating software:        'libLAS 1.8.0'
  file creation day/year:     269/2019
  header size:                227
  offset to point data:       227
  number var. length records: 0
  point data format:          3
  point data record length:   34
  number of point records:    532890
  number of points by return: 0 0 0 0 0
  scale factor x y z:         0.000000002215626 0.000000001714564 0.000000000782776
  offset x y z:               4.840159416198731 -2.95121431350708 477.9866943359375
  min x y z:                  4.840159416198731 -2.95121431350708 477.9866943359375
  max x y z:                  7.055785655975342 -1.236650705337524 478.76947021484375
reporting minimum and maximum for all LAS point record entries ...
  X                   0 1000000000
  Y                   0 1000000000
  Z                   0 1000000000
  intensity           0        255
  return_number       0          0
  number_of_returns   0          0
  edge_of_flight_line 0          0
  scan_direction_flag 0          0
  classification      0          0
  scan_angle_rank     0          0
  user_data           0          0
  point_source_ID     0          0
  gps_time 0.000000 0.000000
  Color R 0 0
        G 0 0
        B 0 0
number of first returns:        532890
number of intermediate returns: 0
number of last returns:         532890
number of single returns:       532890
WARNING: there are 532890 points with return number 0
WARNING: there are 532890 points with a number of returns of given pulse of 0
histogram of classification of points:
          532890  never classified (0)

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>las2las -i C:\Users\Big\las\4.las -rescale 0.0001 0.0001 0.0001 -o C:\Users\Big\conv\4\4_no_crash.las

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>lasinfo -i C:\Users\Big\conv\4\4_no_crash.las

lasinfo (200813) report for 'C:\Users\Big\conv\4\4_no_crash.las'
reporting all LAS header entries:
  file signature:             'LASF'
  file source ID:             0
  global_encoding:            0
  project ID GUID data 1-4:   00000000-0000-0000-0000-000000000000
  version major.minor:        1.2
  system identifier:          'LAStools (c) by rapidlasso GmbH'
  generating software:        'las2las (version 200813)'
  file creation day/year:     269/2019
  header size:                227
  offset to point data:       227
  number var. length records: 0
  point data format:          3
  point data record length:   34
  number of point records:    532890
  number of points by return: 0 0 0 0 0
  scale factor x y z:         0.0001 0.0001 0.0001
  offset x y z:               4.840159416198731 -2.95121431350708 477.9866943359375
  min x y z:                  4.8402 -2.9512 477.9867
  max x y z:                  7.0558 -1.2366 478.7695
reporting minimum and maximum for all LAS point record entries ...
  X                   0      22156
  Y                   0      17146
  Z                   0       7828
  intensity           0        255
  return_number       0          0
  number_of_returns   0          0
  edge_of_flight_line 0          0
  scan_direction_flag 0          0
  classification      0          0
  scan_angle_rank     0          0
  user_data           0          0
  point_source_ID     0          0
  gps_time 0.000000 0.000000
  Color R 0 0
        G 0 0
        B 0 0
number of first returns:        532890
number of intermediate returns: 0
number of last returns:         532890
number of single returns:       532890
WARNING: there are 532890 points with return number 0
WARNING: there are 532890 points with a number of returns of given pulse of 0
histogram of classification of points:
          532890  never classified (0)

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>lasinfo -i C:\Users\Big\conv\4\4_no_crash.las -repair

lasinfo (200813) report for 'C:\Users\Big\conv\4\4_no_crash.las'
reporting all LAS header entries:
  file signature:             'LASF'
  file source ID:             0
  global_encoding:            0
  project ID GUID data 1-4:   00000000-0000-0000-0000-000000000000
  version major.minor:        1.2
  system identifier:          'LAStools (c) by rapidlasso GmbH'
  generating software:        'las2las (version 200813)'
  file creation day/year:     269/2019
  header size:                227
  offset to point data:       227
  number var. length records: 0
  point data format:          3
  point data record length:   34
  number of point records:    532890
  number of points by return: 0 0 0 0 0
  scale factor x y z:         0.0001 0.0001 0.0001
  offset x y z:               4.840159416198731 -2.95121431350708 477.9866943359375
  min x y z:                  4.8402 -2.9512 477.9867
  max x y z:                  7.0558 -1.2366 478.7695
reporting minimum and maximum for all LAS point record entries ...
  X                   0      22156
  Y                   0      17146
  Z                   0       7828
  intensity           0        255
  return_number       0          0
  number_of_returns   0          0
  edge_of_flight_line 0          0
  scan_direction_flag 0          0
  classification      0          0
  scan_angle_rank     0          0
  user_data           0          0
  point_source_ID     0          0
  gps_time 0.000000 0.000000
  Color R 0 0
        G 0 0
        B 0 0
number of first returns:        532890
number of intermediate returns: 0
number of last returns:         532890
number of single returns:       532890
number of point records in header is correct.
number of points by return in header is correct.
WARNING: there are 532890 points with return number 0
WARNING: there are 532890 points with a number of returns of given pulse of 0
histogram of classification of points:
          532890  never classified (0)
bounding box is correct.

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>lasinfo -i C:\Users\Big\conv\4\4_no_crash.las

lasinfo (200813) report for 'C:\Users\Big\conv\4\4_no_crash.las'
reporting all LAS header entries:
  file signature:             'LASF'
  file source ID:             0
  global_encoding:            0
  project ID GUID data 1-4:   00000000-0000-0000-0000-000000000000
  version major.minor:        1.2
  system identifier:          'LAStools (c) by rapidlasso GmbH'
  generating software:        'las2las (version 200813)'
  file creation day/year:     269/2019
  header size:                227
  offset to point data:       227
  number var. length records: 0
  point data format:          3
  point data record length:   34
  number of point records:    532890
  number of points by return: 0 0 0 0 0
  scale factor x y z:         0.0001 0.0001 0.0001
  offset x y z:               4.840159416198731 -2.95121431350708 477.9866943359375
  min x y z:                  4.8402 -2.9512 477.9867
  max x y z:                  7.0558 -1.2366 478.7695
reporting minimum and maximum for all LAS point record entries ...
  X                   0      22156
  Y                   0      17146
  Z                   0       7828
  intensity           0        255
  return_number       0          0
  number_of_returns   0          0
  edge_of_flight_line 0          0
  scan_direction_flag 0          0
  classification      0          0
  scan_angle_rank     0          0
  user_data           0          0
  point_source_ID     0          0
  gps_time 0.000000 0.000000
  Color R 0 0
        G 0 0
        B 0 0
number of first returns:        532890
number of intermediate returns: 0
number of last returns:         532890
number of single returns:       532890
WARNING: there are 532890 points with return number 0
WARNING: there are 532890 points with a number of returns of given pulse of 0
histogram of classification of points:
          532890  never classified (0)

C:\Users\Big Science\Downloads\LAStools\LAStools\bin>cd C:\Users\Big\PotreeConverter_2.0_windows_x64

C:\Users\Big\PotreeConverter_2.0_windows_x64>Converter.exe C:\Users\Big\conv\4\4_no_crash.las -o C:\Users\Big\conv

flags:
#paths: 1

output attributes:
name                              offset    size
================================================
position                               0      12
intensity                             12       2
return number                         14       1
number of returns                     15       1
classification                        16       1
scan angle rank                       17       1
user data                             18       1
point source id                       19       2
gps-time                              21       8
rgb                                   29       6
================================================
                                              35
================================================
cubicAABB: {
        "min": [4.840159, -2.951214, 477.986694],
        "max": [7.055759, -0.735614, 480.202294],
        "size": [2.215600, 2.215600, 2.215600]
}
#points: 532'890
total file size: 17.3 MB
maxPointsPerChunk: 26644

=======================================
=== COUNTING
=======================================
tStartTaskAssembly: 0.000666s
countPointsInCells: 0.211520s
finished counting in 0s
=======================================
createLUT: 0.105876s

=======================================
=== CREATING CHUNKS
=======================================
distributePoints0: 0.000243s
distributePoints1: 0.002715s
finished creating chunks in 1s
=======================================

=======================================
=== INDEXING
=======================================
[67%, 1s], [INDEXING: 0%, duration: 0s, throughput: -na'n(i'nd)MPs][RAM: 0.0GB (highest 0.1GB), CPU: 0%]
[67%, 2s], [INDEXING: 0%, duration: 0s, throughput: -na'n(i'nd)MPs][RAM: 0.1GB (highest 0.1GB), CPU: 46%]
sampling: 1.740692s
flushing: 1.764235s
metadata & hierarchy: 1.786577s

=======================================
=== STATS
=======================================
#points:               532'890
#input files:          1
sampling method:       poisson
chunk method:          LASZIP
input file size:       0.0GB
duration:              3.277s
throughput (MB/s)      5MB
throughput (points/s)  0.2M
output location:       C:\Users\Big\conv
duration(chunking-count):       0.223
duration(chunking-distribute):  0.732
duration(chunking-total):       0.982
duration(indexing):     1.789

I hope this information is useful for you as well. A hug Thank you very much for your time and dedication. Best regards tubo

I wanted to put a point cloud through the converter and step through most of the logic until I found something enlightening, but I need to look over my IDE settings. Something isn't chooching and I'm still missing the symbols for a dependency.

From what I can see, the RGB data is completely stripped or clamped to zeros on las version 4. That explains why it's rendered as black - because an RGB of 0, 0, 0 is the color black. There's a clear difference in other stats too.

What I'd like to do is check the original LAS. If you're willing and able to upload the original, we can analyze it and attempt conversions. Checking 2, 3, 4 or other derivatives may not be of much help because the malfunctioning original file was altered during conversion, and that could result in other artifacts that are snowballing into larger errors.

While I work on fixing my debugging configuration, I'd like some more information.

Which program actually created the original LAS file?
What hardware was used (drone, land-based LiDAR, with or without GPS/RTK/PPK, etc.)?
Have you successfully scanned, exported, and converted point clouds in the past using the same software and hardware with the same order of operations?
Was the record medium an SSD, an SD card, USB thumb drive?
Is the data drive still in its original state (not wiped, formatted, or otherwise overwritten)? I ask because if it's still in the same condition, you can try exporting the data again using the same software as you did the very first time, and you can also run a chkdsk on the drive to see if there are corrupt sectors, which could create significant problems. SD cards used in humid or dusty environments can often become corrupt to varying levels.

hello @midnight-dev ,Thank you for your time and dedication to this topic. I'll try to answer some of your questions below:

1.- Which program actually created the original LAS file? R: the design team uses a software called "solid edge", the point cloud is worked in "cloud compare". 2.- What hardware was used (drone, land-based LiDAR, with or without GPS/RTK/PPK, etc.)? R: I'm not sure but it seems to me that it is land-based LiDAR technology 3.- Have you successfully scanned, exported, and converted point clouds in the past using the same software and hardware with the same order of operations? R: the design team has successfully exported point clouds, with their software. we have not succeeded in converting a point cloud using Potree. 4.- Was the record medium an SSD, an SD card, USB thumb drive? R:I don't have that information exactly, but I'll ask 5.- Is the data drive still in its original state (not wiped, formatted, or otherwise overwritten)? I ask because if it's still in the same condition, you can try exporting the data again using the same software as you did the very first time, and you can also run a chkdsk on the drive to see if there are corrupt sectors, which could create significant problems. SD cards used in humid or dusty environments can often become corrupt to varying levels. R:I don't have that information exactly, but I'll ask

I will request new .LAS files from the design team for further testing As soon as I have information I will write to you again keep in touch Greetings and thank you very much

3.las doesn't work because it has an invalid combination of las format 7 and byte length 30:

point data format:          7
point data record length:   30

4.las works because las format 3 and byte length 34 are a valid combination:

point data format:          3
point data record length:   34

The message WARNING: point size 30 too small by 6 bytes for point type 7. assuming point_size of 36 is probably coming from laszip (integrated into the converter) trying to work with non-spec-conforming files anyway, but the PotreeConverter doesn't do that.

Maybe las2las with the set_point_type option can help: las2las -i 2.laz -set_point_type 3 -o format_3.laz

potree / PotreeConverter

Zero Bounding Box #429

At this point the process ended abruptly