I've reported this one as bug http://trac.osgeo.org/grass/ticket/1445.
Aren On Mon, Sep 5, 2011 at 10:30 AM, Aren Cambre <[email protected]> wrote: > So I've narrowed it down a bit more. > > Attached is an Excel spreadsheet showing the data GRASS is trying to insert > interposed with the actual column information (name, field type, length, > etc.) in the GRASS DBF. Note that in some cases, the first *'* in a string > doesn't appear; that's just how Excel somehow works. (*'* means take the > following text literally, so *'string'* may appear as *string'* in a few > places.) > > I'm not clear I see anything obscenely wrong, but I did notice a few cases > where possibly non-numeric stuff, like *18:40:00*, is being entered into a > field with N type. Is this valid? > > Again, the key problem here is that GRASS is giving me a "Cannot insert new > row" error, but it gives me no clue of what the actual problem is. > > Aren > > > On Sun, Sep 4, 2011 at 10:19 PM, Aren Cambre <[email protected]> wrote: > >> I reported this as a bug: http://trac.osgeo.org/grass/ticket/1439. >> >> It also happens with the standalone copy of GRASS GIS 6.4.1. >> >> Aren >> >> >> On Sun, Sep 4, 2011 at 7:47 PM, Aren Cambre <[email protected]> wrote: >> >>> I am running the GRASS 6.4.1 that is bundled with QGIS 1.7. >>> >>> When I run v.in.ogr.qgis from the UI, I end up with an error. The source >>> is a QGIS PostGIS layer that is just geometry points. >>> >>> From the error details, I assume that v.in.ogr.qgis is just a bridge >>> between QGIS and v.in.ogr as the actual error message is from v.in.ogr. >>> >>> The command doesn't work, and the error message is unhelpful. Here's the >>> module's output: >>> *v.in.ogr -o "dsn=PG:dbname='de' host=localhost port=5432 >>> user='postgres' password='[redacted]' sslmode=disable" "layer=raw.TxDOT >>> crash" "where="Cnty_ID" = '57'" output=pointdata snap=-1 min_area=0.0001 >>> * >>> *Over-riding projection check* >>> *Layer: raw.TxDOT crash* >>> *Default driver / database set to:* >>> *driver: dbf* >>> *database: $GISDBASE/$LOCATION_NAME/$MAPSET/dbf/* >>> *Counting polygons for 264398 features...* >>> *Importing map 264398 features...* >>> *DBMI-DBF driver error:* >>> *Cannot insert new row: insert into pointdata values ( 1, '[redacted--was >>> a time]', '', 1, NULL, 32.959261, 2, NULL, NULL, NULL, 6, 0, NULL, 'N', >>> '', NULL, 0, NULL, NULL, NULL, NULL, '', NULL, 0, 2, '762', '', NULL, 0, >>> NULL, 0, NULL, NULL, NULL, '', 'N', NULL, 0, NULL, 'E BETHEL SCHOOL RD', 8, >>> NULL, 0, NULL, 4, 38, NULL, NULL, NULL, '', 'N', NULL, NULL, 'N', 1, NULL, >>> 94, '', NULL, NULL, 8, 22, 22, NULL, NULL, 'N', 'N', '[redacted--was a >>> date]', NULL, 2, NULL, '', 'N', NULL, NULL, NULL, NULL, NULL, NULL, >>> NULL, NULL, NULL, NULL, NULL, 0, NULL, 0, 1, 0, 1, NULL, NULL, 5, 'Y', NULL, >>> NULL, NULL, '', 3, '', NULL, '', 1, 2, NULL, 'N', 'MOCKINGBIRD LN', NULL, 1, >>> '', 57, NULL, 1, NULL, NULL, 64, 0, 1, NULL, 0, NULL, NULL, NULL, '', 1, 0, >>> NULL, 'N', NULL, 'N', 0, NULL, 1, NULL, 2003000146, 'Y', '', NULL, 0, NULL, >>> '', 2, 'Y', -96.968529, 0, 0, NULL )* >>> *Finished with error* >>> >>> I have no idea why this insert didn't work; the error has no details. >>> Searching online, it appears this error message almost always has an >>> explanation provided by GRASS. >>> >>> Is there something that is being done to suppress the error details here? >>> >>> Aren >>> >> >> >
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
