On Thu, April 10, 2008 08:50, Hamish wrote:
> Mark:
>> the v.in.ascii was:
>> v.in.ascii -z -n input=57697.txt output=lidar57697 format=point fs=,
>> skip=0 {columns=code int} x=1 y=2 z=3 cat=0
>>
>> which yeilds:
>> maximum input row length: 43
>> maximum number of columns: 4
>> minimum number of columns: 4
>> column: 1 type: double
>> column: 2 type: double
>> column: 3 type: double
>> column: 4 type: integer
>>
>> <ERROR> number of columns defined (1) does not match number of columns
>> (4) in input.
>
>
> The columns= option is to rename columns, not to say to include them or
> not. So for v.in.ascii you need to name all 4, in order:
> columns='x double, y double, z double, code int'
Yes, sorry, the info I gave was wrong. But what happens if you use no
column= option at all ?
Moritz
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
