[GRASS-dev] Re: [GRASS GIS] #198: v.in.ascii: column scanning is borked

[GRASS GIS]

#198: v.in.ascii: column scanning is borked
-----------------------+----------------------------------------------------
  Reporter:  hamish    |       Owner:  grass-dev@…              
      Type:  defect    |      Status:  closed                   
  Priority:  critical  |   Milestone:  6.4.2                    
 Component:  Vector    |     Version:  svn-develbranch6         
Resolution:  invalid   |    Keywords:  v.in.ascii               
  Platform:  All       |         Cpu:  All                      
-----------------------+----------------------------------------------------

Comment(by mmetz):

 Replying to [comment:9 hamish]:
 > Replying to [comment:8 mmetz]:
 > > It's not v.in.ascii, it's G_getl2() that fails to fetch the
 > > whole line, probably because of some obscure encoding of the
 > > output of las2txt which I am not able to figure out, or
 > > las2txt writes weird characters for empty fields.
 >
 > Hi,
 >
 > instead of piping to v.in.ascii can you save to a file which we can have
 a peek at in hexdump?  what version of las2txt?  does the same happen with
 the snake lidar sample data from the grass wiki lidar page or just this
 dataset?
 >
 las2txt version: libLAS 1.6.1 with GeoTIFF 1.3.0 GDAL 1.8.0 LASzip 1.2.0

 The same happens with "Serpent Mound Model LAS Data.las" from the grass
 wiki lidar page.

 Attached is the las2txt output for srs.laz.

 I am pretty sure this problem is caused by las2txt which does not check if
 a given attribute exists. If it does not exist, some weird value is
 written.

 Markus M

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/198#comment:10>
GRASS GIS <http://grass.osgeo.org>