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
On Sun, 15 Mar 2015, Andy Wickert wrote:
EXAMPLE 1:
I want to present a time series of stream gage data. I would like a data
table to have:
time water_discharge_m3_s sediment_discharge_m3_s
And to have an entire time series of values for a given grass vector
category (i.e. vector
Dear GRASS users,
I have a question regarding attaching data where there may me more than one
value per category to a single GIS point. Here are a couple of examples;
the first may already be taken care of by the temporal GIS component of
GRASS, but the second would not be.
EXAMPLE 1:
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 GRASS?
Andy,
Yes. You can keep all point attributes in SQLite (or other rdbms)
On Sun, Mar 15, 2015 at 11:49 PM, Rich Shepard rshep...@appl-ecosys.com
wrote:
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, Mar 15, 2015 at 4:08 PM, Rich Shepard rshep...@appl-ecosys.com
wrote:
On Sun, 15 Mar 2015, Andy Wickert wrote:
EXAMPLE 1:
I want to present a time series of stream gage data. I would like a data
table to have:
time water_discharge_m3_s sediment_discharge_m3_s
And to
