[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                      
-----------------------+----------------------------------------------------
Changes (by mmetz):

  * status:  reopened => closed
  * resolution:  => invalid


Comment:

 Replying to [comment:7 mmetz]:
 > Still not working. Test data are LiDAR laz data available here
 >
 > http://liblas.org/samples/
 >
 > The file I used is srs.laz
 >
 > [snip]
 >
 > # only the first 5 columns were imported
 >
 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.

 Closing as invalid.

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