Re: [GRASS-user] db.connect/db.in.ogr Questions

2011-03-11 Thread Micha Silver
On 03/11/2011 02:01 AM, Rich Shepard wrote: On Thu, 10 Mar 2011, Hamish wrote: set 'g.gisevn set=DEBUG=5' to find the data line it dies on, if you don't already know that. (empty records was it?) Hamish, Already did that and posted the results. The suggestion was to use the postgres

Re: [GRASS-user] db.connect/db.in.ogr Questions

2011-03-11 Thread Rich Shepard
On Fri, 11 Mar 2011, Micha Silver wrote: Also make sure you're clear on the distinction in GRASS between the geography of vector layers and their attributes. GRASS always stores the vector geography in it's own internal format (enforcing topology, etc) and there's no need from GRASS's point of

[GRASS-user] db.connect/db.in.ogr Questions

2011-03-10 Thread Rich Shepard
My postgres tables are in /usr/local/pgsql/data/. My GRASS database is in ~/grassdata/. Since the water well log table did not want to cleanly import with v.in.ascii using the default dbf driver/database, I'll use the postgres table. db.connect wants a driver name (pg), and the database name

Re: [GRASS-user] db.connect/db.in.ogr Questions

2011-03-10 Thread Rich Shepard
On Thu, 10 Mar 2011, Hamish wrote: set 'g.gisevn set=DEBUG=5' to find the data line it dies on, if you don't already know that. (empty records was it?) Hamish, Already did that and posted the results. The suggestion was to use the postgres table and ignore the dbf table. so maybe like