Looks like there's a SQLite driver bug in the development code. Version is
7.9.dev 1bd88db63
points.dat (same result without quotes on the text):
-123.754167|45.704167|"USGS Gauge"
-123.818006|45.691833|"Mohler S&G"
v.in.ascii in=$HOME/projects/oregon/mohler/data/features/points.dat \
out=points for=point columns='x double precision, y double precision, \
name=char(10)' x=1 y=2 --o
ERROR: Unable to open input file # WHY?
</home/rshepard/projects/oregon/mohler/data/features/points.dat>
Scanning input for column types...
Number of columns: 3
Number of rows: 2
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "=": syntax error
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "=": syntax error
ERROR: Unable to create table: create table points ( cat integer, x double
precision, y=double precision, name=char(10) )
WARNING: Table <points> linked to vector map <points> does not exist
Installed here is sqlite-3.13.0-x86_64-1.
Regards,
Rich
Hi Rich,
There seems to be a typo in your columns option. There should not be a "=" after the last column name, but a white space:
Should be:
columns='x double precision, y double precision, name char(10)'
(not: columns='x double precision, y double precision,
\ name=char(10)')
That should fix it...
Cheers
Stefan
On Mon, 26 Aug 2019, Stefan Blumentrath wrote:
There seems to be a typo in your columns option. There should not be a "="
after the last column name, but a white space: Should be: columns='x
double precision, y double precision, name char(10)'
(not: columns='x double precision, y double precision,
Stefan,
I should have seen that myself.
Apologies to all,
Rich
On Mon, 26 Aug 2019, Stefan Blumentrath wrote:
That should fix it...
Stefan,
Now if someone can tell me why running a bash script, or copying the command
in the script, results in grass telling me that it cannot read the file, yet
it can when I type the same command, letter-by-letter, in the grass shell
I'll be very happy.
I put module commands in shell scripts as I develop the analyses both for
repeated use and as a record of what I've done. I haven't yet found why
grass won't accept a command such as:
$HOME/projects/state/site/data/stuff.dat
when 'stuff.dat' is an ASCII text file formatted for a specific module.
Regards,
Rich
On Mon, 26 Aug 2019, Rich Shepard wrote:
Now if someone can tell me why running a bash script, or copying the command
in the script, results in grass telling me that it cannot read the file, yet
it can when I type the same command, letter-by-letter, in the grass shell
I'll be very happy.
Fixed: typo in the script that I overlooked each time.
Rich