[GRASS-dev] [GRASS GIS] #1957: v.in.ascii (points.c) does not import some numbers in attached example

[GRASS GIS]

#1957: v.in.ascii (points.c) does not import some numbers in attached example
----------------------+-----------------------------------------------------
  Reporter:  ychemin  |       Owner:  grass-dev@…              
      Type:  defect   |      Status:  closed                   
  Priority:  normal   |   Milestone:  6.5.0                    
 Component:  Vector   |     Version:  svn-trunk                
Resolution:  fixed    |    Keywords:  v.in.ascii               
  Platform:  Linux    |         Cpu:  x86-64                   
----------------------+-----------------------------------------------------

Comment(by hamish):

 It is likely that even 255 columns will not be supported by grass, just
 because the buffers are too small. Better to make the bottleneck the DB
 backend not the GRASS frontend.

 As a ballpark estimate, say 2 columns x,y at 10 chars wide, + 253 columns
 of varchar(255), with field seps, plus a DOS newline,
  10 + 1 + 10 + 1 + 253*255 + 252 + 2 = 64791

 I think it's also worth about the solutions of transposing the array and
 creating a script to make each data row its own map, with the constant-
 step time series as a single column not a series of individual rows.. work
 around the DB limitation by thinking of the problem in a different way..


 Hamish

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