[GRASS5] v.in.ascii

[Moritz Lennert]

On Thu, June 23, 2005 3:36, Hamish said:
>> So, are you saying if I have x,y,z data, I should use columns=3? What
>> if I have x,y,z,t data, where z is an elevation and t is some value?
>> I assume columns=4? Does GRASS know the difference between z and t?
>
> from the help page:
> Parameters:
> [...]
>   columns   Columns definition for points mode in SQL style, for example:
>      'x double precision, y double precision, cat int, name varchar(10)'
> [...]
> Flags:
>   -z   create 3D file
>   -t   Do not create table in points mode.
>
>
> The column= parameter lets you name the attribute columns. I think the
> code that is causing this bug was to let you override the automatically
> determined column type. If you don't use columns= it just names them
> str_1, int_1, int_2, etc.

Would it be very hard to have the module give you the choice of using the
first line as the column names ?

Moritz