[GRASSLIST:7724] Re: importing with v.in.ascii into mysql db gives error

[Jason Horn]

Thanks Ian for the suggestion.  I tried removing the "_" character  
from column names, but no luck.  I still get the error:

dbmi: Protocol error
ERROR: Cannot describe table stations

Thanks, though.  It was a good thought.


On Jul 26, 2005, at 11:29 AM, Ian MacMillan wrote:

> Jason,
> I am no positive about this, but I don't think you are allowed to  
> have the _ character in the database.  It looks like it is reading  
> your column 'station_id' as just 'station', and then choking on the  
> _ symbol.  I can't remember for sure about this, but I think that  
> you can use '.' instead.
>
> G'luck
> -Ian
>
> On Jul 26, 2005, at 7:17 AM, Jason Horn wrote:
>
>
>> I have successfully set up mysql to store attribute data for  
>> several point coverages for my project.  However when I use  
>> v.in.ascii to import new files, I get the following error:
>>
>> dbmi: Protocol error
>> ERROR: Cannot describe table stations
>>
>> Does anyone know what this means?  Below is the full text of the  
>> command I am using, and the error.  The text file with the  
>> coordinates is properly formatted.
>>
>> GRASS 6.1.cvs (Texas_ll_WGS84):~ > cat coordinates.csv |  
>> v.in.ascii out=stations fs="," x=2 y=3 cat=1 columns='cat int, x  
>> double, y double, station_id varchar(10), name varchar(50), state  
>> varchar(10), elev int, height int, lat_deg int, lon_deg int'
>> Maximum input row length: 78
>> Maximum number of columns: 10
>> Minimum number of columns: 10
>> column: 1  type: integer
>> column: 2  type: double
>> column: 3  type: double
>> column: 4  type: string  length: 4
>> column: 5  type: string  length: 22
>> column: 6  type: string  length: 7
>> column: 7  type: integer
>> column: 8  type: integer
>> column: 9  type: integer
>> column: 10  type: integer
>> dbmi: Protocol error
>> ERROR: Cannot describe table stations
>>
>>
>>
>
>
>