[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:11 hamish]:
 > Replying to [comment:10 mmetz]:
 > > 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.
 >
 > correct. columns 6 and 7 are not empty.
 [snip]
 >
 > I think it is reasonable for G_getl2() to stop on null terminators, and
 there's nothing more to do here but file a bug with `las2txt`.
 >
 I would rather call this a user error that I did because the proper way to
 do it would be to investigate the .la[s|z] file first with `lasinfo`,
 decide what attributes I want to import based on the attributes available
 and then set the --parse options accordingly. Or use v.in.lidar which does
 it all automatically;-)

 Markus M

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