[GRASS-dev] [GRASS GIS] #2472: v.in.lidar gives negative point count on large las files

#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
Keywords: v.in.lidar point initial count | Platform: Unspecified
      Cpu: x86-64 |
---------------------------------------------+------------------------------
Trying to use v.in.lidar to import points from an las file with 3531181701
points

v.in.lidar -o -b input=/gisdata/grass7/lidardir/big_lidar_file_ground.laz
output=whole_co_ground_pts
Over-riding projection check
Importing -763785595 points..

Seems to be importing so far..

Running GRASS 7.0 SVN snapshot from 10/25/14

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2472&gt;
GRASS GIS <http://grass.osgeo.org>

#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
Keywords: v.in.lidar point initial count | Platform: Unspecified
      Cpu: x86-64 |
---------------------------------------------+------------------------------

Comment(by dnewcomb):

v.in.lidar has been running now for 10 hours and is using 13 GB of RAM for
this instance. Write access to the sqlite database by other vector
operations is currently blocked.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2472#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

#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
Keywords: v.in.lidar point initial count | Platform: Unspecified
      Cpu: x86-64 |
---------------------------------------------+------------------------------

Comment(by mlennert):

Replying to [ticket:2472 dnewcomb]:
> Trying to use v.in.lidar to import points from an las file with
3531181701 points
>
> v.in.lidar -o -b
input=/gisdata/grass7/lidardir/big_lidar_file_ground.laz
output=whole_co_ground_pts
> Over-riding projection check
> 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.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2472#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

#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
Keywords: v.in.lidar point initial count | Platform: Unspecified
      Cpu: x86-64 |
---------------------------------------------+------------------------------

Comment(by mlennert):

Replying to [comment:1 dnewcomb]:
> v.in.lidar has been running now for 10 hours and is using 13 GB of RAM
for this instance. Write access to the sqlite database by other vector
operations is currently blocked.

Try importing with the -t flag to not create an attribute table. Or
possibly use PostgreSQL as a back end for the attributes.

Moritz

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2472#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>