On 25/09/13 21:25, Peter Löwe wrote:
The initial location from which v.in.ogr was invoked was already switched to a
sqlite-backend. How can this issue be overcome ?
Just a note: you cannot switch a location to a specific backend. This
setting is per mapset. In grass6, each new mapset created
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
Hamish,
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
can I ask what part of it you are trying to load? The actual trace
data (time vs amplitude) or to extract the navigation data for
source, receiver, or CDP?
Peter wrote:
I'm evaluating the SEG-Y formate to exchange data between software packages
from the exploration industry like Petrel and Gocad and GRASS. So far only
demo
data sets are used. I will inquire wether P1/90 is also available.
links:
Hi list,
I'm using GRASS6.4.2 on a Suse-based HPC Cluster.
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:
GRASS 6.4.2 (startup_sqlite):~/geodata/petrel/SEG_Y_Demo
