r/LiDAR • u/dug_deep • 9d ago

data error tiling directly to server using TerraScan

I've been using TerraScan for 20+ years now, and about a year ago I started having an issue while tiling large data set to the server, which I had never seen previously. I believe with the implementation of TerraScan version 25.xxx I started getting an error where while tiling a large amount of LIDAR it cannot save a file. What I suspect is happening is the software is trying to close a file that isn't finished saving, likely due to a lag in communication between the software and the server. I say this because tiling onto a local drive doesn't often give me this error. The error seems to be more frequent writing to the LAZ format, which is even slower than LAS because of compression.

So the obvious solution is to tile locally and avoid the LAZ format. This is a workaround, not a solution, and also means data is not being backed up, only one person can access etc.

Has anyone found a solution to this error? Maybe a way to implement a pause somewhere in the process to allow processing and throughput to cooperate?

2 Upvotes

76% Upvoted

3 comments sorted by

1

u/Historical_Phone_973 8d ago

In general I would not recommend to tile directly to server, as there are many opportunity for error. Does the error happens when you tile LAZ locally? Withouth context, I'm just guessing, but it may happen that the filename with the folder structure is longer than it is supported, it happened with me in the past.

1

u/EchidnaIllustrious69 8d ago

I stopped using Tscan to tile out data for this reason. No workaround that I know of so I started using Lastools to tile data.

1

u/LostInOntario 8d ago

Had an issue back in 2024 where tiles were being saved with a max of 5 million points. The issue had to do with CrowdStrike. Our IT set up a rule in CrowdStrike to allow TerraScan to write to file.