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

2013-09-26 Thread Moritz Lennert
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

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

2013-09-26 Thread Markus Metz
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

Re: [GRASS-dev] [GRASS GIS] #957: v.voronoi has extra lines in output

2013-09-26 Thread GRASS GIS
#957: v.voronoi has extra lines in output ---+ Reporter: helena | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.4

Re: [GRASS-dev] [GRASS GIS] #957: v.voronoi has extra lines in output

2013-09-26 Thread GRASS GIS
#957: v.voronoi has extra lines in output ---+ Reporter: helena | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.4

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

2013-09-26 Thread Peter Löwe
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?

[GRASS-dev] [GRASS GIS] #2085: build failure on s390s

2013-09-26 Thread GRASS GIS
#2085: build failure on s390s ---+ Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.4.4

Re: [GRASS-dev] [GRASS GIS] #2085: diglib build failure on IBM s390x (was: build failure on s390s)

2013-09-26 Thread GRASS GIS
#2085: diglib build failure on IBM s390x ---+ Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.4.4

Re: [GRASS-dev] [GRASS GIS] #2085: diglib build failure on IBM s390x and ppc64 (was: diglib build failure on IBM s390x)

2013-09-26 Thread GRASS GIS
#2085: diglib build failure on IBM s390x and ppc64 --+- Reporter: hamish| Owner: grass-dev@… Type: defect| Status: new Priority: normal

[GRASS-dev] [GRASS GIS] #2086: libgis build failure on alpha

2013-09-26 Thread GRASS GIS
#2086: libgis build failure on alpha ---+ Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone:

[GRASS-dev] [GRASS GIS] #2087: grass64 man page: missing words

2013-09-26 Thread GRASS GIS
#2087: grass64 man page: missing words +--- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: critical| Milestone: 6.4.4

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

2013-09-26 Thread Hamish
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:  

Re: [GRASS-dev] [GRASS GIS] #1941: wxGUI fails with Japanese locale -- mixed Python installs on Windows

2013-09-26 Thread GRASS GIS
#1941: wxGUI fails with Japanese locale -- mixed Python installs on Windows --+- Reporter: venkat| Owner: grass-dev@… Type: defect| Status: new Priority: major