[GRASSLIST:10833] Re: v.in.ascii error

[Stuart Edwards]

About a month ago I started a thread 'v.in.ascii quirk' (Grasslist  
10237) and after some backwards and forwards with Maciek Sieczka, he  
determined that there was a bug (at least one IMO) and forwarded it  
to the developers list.  I've never heard of a resolution. It does  
seem that this is a fundamental issue for data input and while I can  
now work with the command, it is probably one of the most syntax  
sensitive commands for the *nix impaired user to execute.

Stuart Edwards
On Mar 8, 2006, at 5:32 PM, Hamish wrote:

>> I think your command should look something like this:
>>
>> v.in.ascii input=/home/pierluigi/Desktop/zinc output=zinc  
>> format=point
>> fs=| columns='x double, y double, ppm double' x=1 y=2
>
>> From the command line yes, but quote the pipe (|).
>
> so if you try:
>
> G6> v.in.ascii input=/home/pierluigi/Desktop/zinc output=zinc \
>   format=point fs='|' columns='x double, y double, ppm double' x=1 y=2
>
> It should be ok. The shell needs to be protected from special chars
> (pipe is the redirect command) and also needs to be told that  
> multiword
> answers belong with a single option. The GUI and SQL don't need to be
> protected as such.
>
> If you are running from the GUI, you should not quote the pipe (|) or
> the column names/types:
>
>> SQL parser error in statement:
>> create table zinc ( cat integer, 'x double precision, y double
>>  precision, ppm double precision' )
>
> The ' before the x and after precision should not be there. You are
> quoting too much.
>
>
>> I realised that the gui of v.in.ascii usually puts together the
>> command incorrectly, so I always use the cli to import ascii files.
>
> How so? If it is broken we can fix it, but I don't think it is broken.
>
>
> Hamish