[GRASS-stats] Loading a point-vector table with 466 columns

[Nikos Alexandris]

Roger:
> >> Next script in R generating increasing NR and NC cases through
> >> writeVECT6() to test plugin=FALSE/plugin=TRUE ratios?

Hamish:
> > Does R have any built in profiling tools? as grass is just a
> collection
> > of small C programs the normal ones work fine with it:

Roger:
> Yes, at the R level, so they won't help here. readVECT6() banches on 
> plugin - if TRUE, it just calls readOGR() on the GRASS driver, if
> FALSE, it does (something like) v.out.ogr with shapefile driver to a
> temporary file and readOGR() on the shapefile. The C/C++ level code is
> in the (same) GDAL shared object for v.out.ogr and readOGR(), so I
> think the only difference is in the use or not of the plugin.

> My second post (testing v.out.ogr to shapefile against ogr2ogr from
> GRASS plugin to shapefile for a many-column vector) should reveal
> where the problem is - my present feeling is that the plugin and
> v.out.ogr handle access to the GRASS vector and its attribute data
> differently in one way or another.

Good (and bad :-p) to see that there is room for improvement. C/C++ code
is unknown territory from end-user level ( =requires time to explore...
within this short life-time ;-) ).

Kindest regards, Nikos