The results of lasinfo running are different on different computers.

[PT M]

Hello,

Sorry for my bad English.

I use the same data to run lasinfo on different computers and the results are different.

There are errors in this data (about gps_time).

Command：lasinfo -i F:\Lidar\test1007\32_73404894.las -odir F:\Lidar\test1007 -otxt -histo classification 1 -histo point_source_id 1 -histo user_data 1 -histo gps_time 1

Computer A outputs a complete report. But computer B stopped at "reporting minimum and maximum for all LAS point record entries ..."

And I tried again without outputting the report. Computer A successfully displayed the content. But computer B showed an error "ERROR: allocating 366625377 neg bins"

Why is this and what should I do to get computer B to output a full report？

Computer A: Windows 10 Pro x64

Computer B: Windows Server 2016 Standard x64

Thanks,

PT

[Jochen Rapidlasso]

Hi PT,

what you want do do does not make much sense.

Why not do a histogram for each dimension one by one?
Doing this all at once mean that you got a very high number of output bins of 
(classification * point_source_id * user_data * gps_time) 

One computer A can handle 366625377 bins, computer B not.

The question is: Can you handle a result in  366625377 bins?

If yes: Use computer A.

Cheers,

Jochen @rapidlasso

[Albert Godfrind]

Is this with the same file on both platforms ? Or different files ? If the same, maybe it got mangled when copying from one machine to the other. If not, maybe one is much larger than the other.

> computer B showed an error "ERROR: allocating 366625377 neg bins"

may just indicate that computer B has insufficient capacity (RAM) compared to computer A ?

[PT M]

Thanks Jochen

Everything became normal after I gave up counting the GPS time. It seems that there is something wrong with the GPS time of the data.

[PT M]

Thanks Albert

I'm sure the data hasn't changed.

Computer B even has more RAM than Computer A.

Everything became normal after I gave up counting the GPS time. It seems that there is something wrong with the GPS time of the data.