Hi,
2015-03-16 13:47 GMT+01:00 Daniel Victoria daniel.victo...@gmail.com:
In the 'Name of output OGR datasource' field, the user has to type the
entire path, which some times can be quite long. Of course I can copy/paste
the output path but couldn't we have a directory or file chooser dialog
Hi List,
Just an observation and an improvement idea.
I'm exporting some vector files with v.out.ogr (Grass 7.0 on Win7)
In the 'Name of output OGR datasource' field, the user has to type the
entire path, which some times can be quite long. Of course I can copy/paste
the output path but couldn't
On Mon, Mar 16, 2015 at 9:07 PM, Rich Shepard rshep...@appl-ecosys.com
wrote:
On Sun, 15 Mar 2015, Paulo van Breugel wrote:
The attribute table is in a sqlite table already, unless you are still
using dbf as database backend for grass. Just link your other tables to
that attribute table?
On Mon, 16 Mar 2015, Andy Wickert wrote:
So would this be adding additional SQL database tables as additional
layers associated with a GRASS GIS vector data set? I had thought that
the layers also needed to be linked to vector points... so I'm guessing
that this would still be linking outside
Rich Shepard rshep...@appl-ecosys.com schreef op 15 maart 2015 23:49:06 CET:
On Sun, 15 Mar 2015, Andy Wickert wrote:
So to boil it down to the simplest part of what you said, the key is
just
to have an ID column in the GRASS table that links to a table in a
database structure outside of
On Sun, 15 Mar 2015, Paulo van Breugel wrote:
The attribute table is in a sqlite table already, unless you are still
using dbf as database backend for grass. Just link your other tables to
that attribute table?
Paulo,
Thanks for reminding us. I forgot about that. You are correct that the
