[GRASSLIST:5871] Re: error importing shapefile with v.in.ogr

[Michael Barton]

I think that you probably have a column name that sql doesn't like. My guess
is that the problem is with the column named "where". This is an SQL
reserved operator and probably not permitted as a column name.

Michael
____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ  85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>


> From: "LJunek at t-online.de" <LJunek at t-online.de>
> Date: Fri, 18 Feb 2005 12:58:15 +0100
> To: <GRASSLIST at baylor.edu>
> Subject: [GRASSLIST:5842] error importing shapefile with v.in.ogr
> 
> Dear users,
> I'd like to import a shapefile into GRASS6.0 and use v.in.ogr .
> The module doesn't create an attribute table:
> 
> v.in.ogr dsn=. output=le_ausschr_hg_biotopkartierung_biotope
> layer=le_ausschr_hg_biotopkartierung_biotope
> PROJ_INFO file not found for location landschaftselemente
> PROJ_UNITS file not found for location landschaftselemente
> Projection of input dataset and current location appear to match.
> Proceeding with import...
> Layer: le_ausschr_hg_biotopkartierung_biotope
> DBMI-DBF driver error:
> SQL parser error in statement:
> create table le_ausschr_hg_biotopkartierung_biotope (cat integer, ID
> integer, AREA double precision, PERIMETER double precision, BIOTOPE_S_
> integer, BIOTOPE_S2 integer, EB integer, ST integer, SM integer, ENUM
> varchar ( 16 ), NAM varchar ( 25 ), FLA double precision, SA double
> precision, W double precision, WHERE integer, KARTE integer, NUMMER
> integer, RECNR integer, FLAECHE double precision, XKOOR double
> precision, YKOOR double precision, BIOTOP_NR integer)
> Error in db_execute_immediate()
> 
> ERROR: Cannot create table: create table
>        le_ausschr_hg_biotopkartierung_biotope (cat integer, ID integer,
>        AREA double precision, PERIMETER double precision, BIOTOPE_S_
>        integer, BIOTOPE_S2 integer, EB integer, ST integer, SM integer,
>        ENUM varchar ( 16 ), NAM varchar ( 25 ), FLA double precision, SA
>        double precision, W double precision, WHERE integer, KARTE
> integer,
>        NUMMER integer, RECNR integer, FLAECHE double precision, XKOOR
>        double precision, YKOOR double precision, BIOTOP_NR integer)
> 
> I already moved the ID column to the first position, nothing changes.
> So what could I do else?
> Thanx Larissa
>