.laz file stops when indexing 50%

.laz file stops when indexing 50%

Anonymous
Not applicable
2,868 Views
8 Replies
Message 1 of 9

.laz file stops when indexing 50%

Anonymous
Not applicable

When i try to import the pointcload file (.laz) its all fine till the  indexing is on 50% then it will cost a few minutes and the follow message appears "could not import scan! ReCap has encountered an error importing: 'C_27GZ2'This file will be removed from the project. Please check the file and re-add it to try again." 

The side where i downloaded the .laz file is : https://downloads.pdok.nl/ahn3-downloadpage/

 

What i allready tried:

- I updatet Revit Recap.

- Downloaded the file again.

- Imported the file again.

 

Recap still gives the same problem. 

 

Recap Info: 

- Recap 2021 

- last update on 23-01-2021

0 Likes
2,869 Views
8 Replies
Replies (8)
Message 2 of 9

Pointdump
Consultant
Consultant

Rien,
Those are HUGE files! I downloaded one LAZ (C_58BZ2.LAZ) that is 3.2GB. Even Cloud Compare, which normally opens large LAS/LAZ files in seconds, is choking.
What is the file size of the one you're trying to use?
Dave

Dave Stoll
Las Vegas, Nevada

EESignature

64GB DDR4 2400MHz ECC SoDIMM / 1TB SSD
NVIDIA Quadro P5000 16GB
Windows 10 Pro 64 / Civil 3D 2027
Message 3 of 9

Anonymous
Not applicable

Thanks for the fast reaction, the size of the file is 2,57 GB. 
is there a possibility to decrease the size of this file?

0 Likes
Message 4 of 9

Pointdump
Consultant
Consultant

Rien,
Cloud Compare did finally open mine, so I'd use it to trim or crop to your area of interest. Good workflow >>>Here<<<.
Even LASInfo was choking, but finally I got a listing of classifications:
histogram of classification of points:
239163651 unclassified (1)
429124276 ground (2)
15472426 building (6)
3149192 water (9)
67044 Reserved for ASPRS Definition (26)

Dave

Dave Stoll
Las Vegas, Nevada

EESignature

64GB DDR4 2400MHz ECC SoDIMM / 1TB SSD
NVIDIA Quadro P5000 16GB
Windows 10 Pro 64 / Civil 3D 2027
Message 5 of 9

Pointdump
Consultant
Consultant

Rien,
Another good video on reducing Point Cloud file size, so that ReCap can handle it, is >>>Here<<<.
Dave

Dave Stoll
Las Vegas, Nevada

EESignature

64GB DDR4 2400MHz ECC SoDIMM / 1TB SSD
NVIDIA Quadro P5000 16GB
Windows 10 Pro 64 / Civil 3D 2027
Message 6 of 9

Pointdump
Consultant
Consultant

Rien,
OK, I found the C_27GZ2.LAZ file and downloaded it. 2.7GB! It took ReCap 56 minutes to "chew on things", but all worked.
From LASInfo:
histogram of classification of points:
210631152 unclassified (1)
322386312 ground (2)
23395932 building (6)
1718215 water (9)
80582 Reserved for ASPRS Definition (26)
So if you use LAS2LAS in LASTools you can keep only Ground(2) Points and that will reduce file size to 1.2GB. Further clipping and resampling in CloudCompare will reduce file size further.

 


Dave

Dave Stoll
Las Vegas, Nevada

EESignature

64GB DDR4 2400MHz ECC SoDIMM / 1TB SSD
NVIDIA Quadro P5000 16GB
Windows 10 Pro 64 / Civil 3D 2027
Message 7 of 9

Anonymous
Not applicable

Dave

 

Many thanks for the good and fast help! I will download the programs and try it.

Is it possible that you sent me your file so i can compare them?  

 

Rien 

 

0 Likes
Message 8 of 9

Pointdump
Consultant
Consultant

Rien,
I started to gezipt them up, but it looks like the file size will be huge and take forever. But do get both LASTools and CloudCompare and let me know if you have any questions with either.
One question I had that I couldn't find an answer to is the Coordinate System. Their GeoTiffs seem to be using Amersfoort/RD New, EPSG:28992, but I didn't see any metadata on the point clouds.

Dave

Dave Stoll
Las Vegas, Nevada

EESignature

64GB DDR4 2400MHz ECC SoDIMM / 1TB SSD
NVIDIA Quadro P5000 16GB
Windows 10 Pro 64 / Civil 3D 2027
0 Likes
Message 9 of 9

Anonymous
Not applicable

I am having the same issue with a .PTS file of about 120MB. I have tried with various clouds ranging from 1M to 30M points, with various clouds edited, modified and exported using Cloudcompare. I have noticed recently that indexing stops at 50% and I can't figure out the rhyme or reason. If anyone knows of a bug or catch that causes this please let me know. -Thanks.

0 Likes