[GRASS5] running grass on macosx

[Hamish]

> You can also import the ascii data into another program (excel, open
> office, filemaker) and export it as dbf. Then you can use v.in.db to
> import it.

This will probably not work if you have more than 32k or 65k points to
bring in; spreadsheets are horrible for large datasets. Just start up in
GRASS 6.0.0 to do the import & then switch back to 6.1 if the 6.1 import
is broken.


> The thing is, I don¹t know in which versions v.in.ascii is broken and
> in which it is OK.

I'm not sure if the insert into DB quoting problem is just happening to
me. Can anyone else who is self-compiling on Debian/sarge test? It
happens to me on multiple Debian/sarge machines with fresh CVS.

hmmm interesting. I've just tried a copy of 6.1 that was compiled March 
2005 and it breaks too, although 6.0.0 is fine. I'm sure it only started
to break in the last few days, so I wonder if an upgraded library is to 
blame somehow..?



Hamish


> Right now, I'm getting this. (fresh & latest CVS, in a new mapset)
[SQL insert is incorrectly 'quoting' int & double fields]
>
>
> GRASS:6.1-cvs > echo "1|2|3" | v.in.ascii out=test654
> Maximum input row length: 6
> Maximum number of columns: 3
> Minimum number of columns: 3
> column: 1  type: integer
> column: 2  type: integer
> column: 3  type: integer
> DBMI-DBF driver error:
> Incompatible value type.
> Error in db_execute_immediate()
>
> ERROR: Cannot insert values: insert into test654 values ( 1, '1', '2',
> 
> '3')
>
> GRASS:6.1-cvs > db.connect -p
> driver:dbf
> database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
> schema:(null)
> group:(null)