#2472: v.in.lidar gives negative point count on large las files
-----------------------+---------------------------------------------
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Default | Version: svn-releasebranch70
Resolution: | Keywords: v.in.lidar point initial count
CPU: x86-64 | Platform: Unspecified
-----------------------+---------------------------------------------
Comment (by wenzeslaus):
Replying to [comment:2 mlennert]:
> Replying to [ticket:2472 dnewcomb]:
> > Trying to use v.in.lidar to import points from an las file with
3531181701 points
> >
> > `Importing -763785595 points...`
>
> A sign of integer overflow. AFAICT, in this particular case this is just
in the message where a '%d' placeholder is used which represents a signed
int. But the count of the number of points is defined as unsigned int and
with larger files this will probably also overflow.
Changed to `unsigned long long` with `unsigned long` as a fallback in
r66255. Please test.
(This supposes usage without topology and attribute table.)
If the test works, please update the
[https://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance#Large_vector_data_processing
wiki] and propose updates to the
[https://grass.osgeo.org/grass71/manuals/v.in.lidar.html manual] if
needed.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2472#comment:4>
GRASS GIS <https://grass.osgeo.org>