[GRASS-dev] v.in.ogr: how to force sqlite instead of dbf for output location ? SEG-Y input (Geology/Seismic Data)

Markus Metz markus.metz.giswork at gmail.com
Thu Sep 26 00:58:55 PDT 2013

Peter Löwe wrote:
> When trying to ingest SEG-Y data (geology/seismics) into a new location via v.in.ogr (GDAL 1.9.0) this error is thrown since the new location is set by default (?) to dbf:
> The initial location from which v.in.ogr was invoked was already switched to a sqlite-backend. How can this issue be overcome ?

You can use from any location

g.proj georef=demo20071121142735_CH1_35P.seg location=segy_sqlite

This will create a new location with the projection information of the
given dataset, but will not import the dataset. Then you would need to
switch to a mapset in the new location, set default db backend to
sqlite with db.connect and import the dataset with v.in.ogr. Or
easier, use GRASS 7.


Markus M

More information about the grass-dev mailing list