[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:  new                      
 Priority:  normal      |   Milestone:  6.5.0                    
Component:  Vector      |     Version:  svn-trunk                
 Keywords:  v.in.ascii  |    Platform:  Linux                    
      Cpu:  x86-64      |  
------------------------+---------------------------------------------------

Comment(by hamish):

 max dbf columns somewhere 255-1028+
   http://compgroups.net/comp.lang.clipper/maximum-fields-per-record-
 dbf/888510

 for sqlite: "`The default setting for SQLITE_MAX_COLUMN is 2000. You can
 change it at compile time to values as large as 32767.`"
   http://www.sqlite.org/limits.html

 PgSQL, "250 - 1600 depending on column types",
   http://www.postgresql.org/about/

 MySQL, "There is a hard limit of 4096 columns per table, but the effective
 maximum may be less for a given table."
   http://dev.mysql.com/doc/refman/4.1/en/column-count-limit.html


 how many met stations? if less than the number of time records maybe
 consider to invert the array and organize data by time instead of
 position? or split up into multiple files by e.g. year?


 Hamish

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