Trimble Business Center

Hello all,

The process of importing largish point clouds in .las and .laz formats has always seemed a bit buggy.  It takes a long times, some times you have to kill the program and try again, etc.  But I was always able to eventually get the import completed.  By largish, these .las files are generally no more, or around, 10GB.  

I thought I had found the reason, within the Options menu there is a location to designate where TBC shall store its temporary processing files.  It defaults to the C: drive C:Trimble

Well, many times it hangs up at 96%, and never finishes, even when left for many, many hours.  I imagine that means 96% is some randomly generated number.  But now, I am getting weird error messages and failure to import.  Of course, I can't repeat the process and get the error message this AM.  But I am wondering if others are seeing this issue.  I have seen in other threads and forums that the hang up at 96% seems to happen to others also.

I will post the error message when/if I get it again.

Hi Clayton,

 I experienced this same issue just yesterday. I am attempting to import a .las file into TBC and the import process gets hung up at 96% every time. I tried multiple times with the same data as a .las and.laz, both with the same result. Finally after complete insanity of trying the same thing over and over again, I was able to import the .laz file. When it did import it got hung up at 100% for about 20min before finally excepting the file. I too thought it had something to do with the temp file so on my last attempt I cleared out the temp file before importing, it worked. I dont know if that was just a coincidence or if clearing out the file allowed TBC to use more recourses. Definitely something Trimble needs to look into. 

Hello all,

The process of importing largish point clouds in .las and .laz formats has always seemed a bit buggy.  It takes a long times, some times you have to kill the program and try again, etc.  But I was always able to eventually get the import completed.  By largish, these .las files are generally no more, or around, 10GB.  

I thought I had found the reason, within the Options menu there is a location to designate where TBC shall store its temporary processing files.  It defaults to the C: drive C:Trimble

Well, many times it hangs up at 96%, and never finishes, even when left for many, many hours.  I imagine that means 96% is some randomly generated number.  But now, I am getting weird error messages and failure to import.  Of course, I can't repeat the process and get the error message this AM.  But I am wondering if others are seeing this issue.  I have seen in other threads and forums that the hang up at 96% seems to happen to others also.

I will post the error message when/if I get it again.

Thank you Brandon.  If this helps, here is one of the error messages I have received.

CB

Hi Clayton,

 I experienced this same issue just yesterday. I am attempting to import a .las file into TBC and the import process gets hung up at 96% every time. I tried multiple times with the same data as a .las and.laz, both with the same result. Finally after complete insanity of trying the same thing over and over again, I was able to import the .laz file. When it did import it got hung up at 100% for about 20min before finally excepting the file. I too thought it had something to do with the temp file so on my last attempt I cleared out the temp file before importing, it worked. I dont know if that was just a coincidence or if clearing out the file allowed TBC to use more recourses. Definitely something Trimble needs to look into. 

Hello all,

The process of importing largish point clouds in .las and .laz formats has always seemed a bit buggy.  It takes a long times, some times you have to kill the program and try again, etc.  But I was always able to eventually get the import completed.  By largish, these .las files are generally no more, or around, 10GB.  

I thought I had found the reason, within the Options menu there is a location to designate where TBC shall store its temporary processing files.  It defaults to the C: drive C:Trimble

Well, many times it hangs up at 96%, and never finishes, even when left for many, many hours.  I imagine that means 96% is some randomly generated number.  But now, I am getting weird error messages and failure to import.  Of course, I can't repeat the process and get the error message this AM.  But I am wondering if others are seeing this issue.  I have seen in other threads and forums that the hang up at 96% seems to happen to others also.

I will post the error message when/if I get it again.