[GRASS-user] Re: Unexplained DBI-DBMF error from v.in.ogr

[Aren Cambre]

I think the problem may actually be with the build of GRASS GIS shipped with
QGIS. I just installed 6.4.1 RC1 and now get a useful error.

Aren

On Sat, Feb 5, 2011 at 10:15 PM, Aren Cambre <aren at arencambre.com> wrote:

> I am running *v.in.ogr* to import a PostGIS table. This table shows up
> fine in QGIS. Here's the command:
> *v.in.ogr -o "dsn=PG:dbname='de' host=localhost port=5432
> user='[redacted]' password='[redacted]' sslmode=disable"
> layer=consistent.master output=master_grassX*
>
> This command was produced by QGIS's GRASS Tools.
>
> The problem is that I get an error but no explanation at all. Here's the
> output:
>
> Width for column school_zone set to 255 (was not specified by OGR), some
> strings may be truncated!
>
> Width for column vehicle_color set to 255 (was not specified by OGR), some
> strings may be truncated!
>
> Width for column offense_location set to 255 (was not specified by OGR),
> some strings may be truncated!
>
> Width for column work_zone set to 255 (was not specified by OGR), some
> strings may be truncated!
>
> DBMI-DBF driver error:
>
>
>
> Unable to create table: 'create table master_grassX (cat integer,
> offense_street_name varchar ( 30 ), school_zone varchar ( 255 ),
> defendant_dl varchar ( 20 ), defendant_dl_state varchar ( 2 ), vehicle_model
> varchar ( 20 ), offense_code integer, vehicle_color varchar ( 255 ),
> citation_id_base varchar ( 20 ), vehicle_make varchar ( 20 ), defendant_dob
> date, speed_limit integer, source varchar ( 20 ),
> vehicle_registration_expiration_date date, offense_crossstreet_number
> varchar ( 10 ), defendant_sex varchar ( 1 ), citing_jurisdiction integer,
> offense_county varchar ( 10 ), officer_id varchar ( 20 ), offense_location
> varchar ( 255 ), defendant_zip varchar ( 9 ), vehicle_licenseplate_state
> varchar ( 2 ), offense_street_number varchar ( 10 ), offense_timestamp
> datetime, citation_id_stub varchar ( 20 ), offense_crossstreet_name varchar
> ( 30 ), speed_alleged integer, vehicle_year integer, vehicle_licenseplate
> varchar ( 10 ), work_zone varchar ( 255 ), defendant_race varchar ( 10 ))'
>
> Finished with error
>
>    The problem is I get no details at all on the error cause. Yes, the
> driver error really is blank.
>
>
> I turned postgres logging to log all queries (following the recipe at
> http://stackoverflow.com/questions/722221/how-to-log-postgres-sql-queries).
> I analyzed the queries and didn't see anything surprising. I've attached the
> log in case it's helpful.
>
>
> I checked the */dbf* directory, and it has no files. I also checked the *
> vector/master_grassX* directory and found no problems, just four files (*
> coor*, *dbln*, *head*, *hist*) with unsurprising contents.
>
>
> I'm new to GRASS, so I'm not sure what else to check. Is there another log
> source? Did I discover a bug that needs to be filed?
>
>
> Aren Cambre
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20110205/865ef785/attachment-0001.html