On Jan 8, 2008 4:20 PM, Markus Neteler <[EMAIL PROTECTED]> wrote: > On Jan 8, 2008 3:36 PM, Benjamin Ducke <[EMAIL PROTECTED]> wrote: ... > > Question is: > > > > Patch the actual OGR sources or the stuff in grass6/db/drivers/ogr or > > the db.in.ogr module itself? Where would be the best place to put the > > type recognition? > > db.in.ogr simply calls v.in.ogr which calls OGR lib which calls OGR-CSV > driver... the best place is there: > > - if .csvt is there, use it > - if .csvt is absent, try recognition. Have env var to disable/enable this. > - if .csvt is absent and recognition disable, proceed as usual > > Or rewrite db.in.ogr as C program...
Ah sorry, another idea: - or fix that C program to become an $ETC tool for GRASS which simply creates the .csvt file! That could be an elegant and easy solution. Store in tools/csvdetect/ or so then within GRASS. Good luck, Markus _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
