[GRASS5] Database linking question

Rich Shepard rshepard at appl-ecosys.com
Tue Jan 2 22:57:21 EST 2001

On Tue, 2 Jan 2001, Eric G . Miller wrote:

> Anyway, I'll keep hammering away at this, but for GRASS to be a contender
> in the Vector GIS arena it really needs a robust, data attribute system
> (Relational is nice, SQL is unnecessary and probably undesirable).  I
> really don't want to try to reinvent the wheel either (I'm not sure I'm up
> to it anyway) so I'd prefer to find an existing solution that can be
> "plugged" in.  I'm not sure what you all have in mind for the future GRASS
> Vector library, but I think it needs to take into account this need and
> should try to make it simple for the module programmer to handle (perhaps
> transparent in some instances).


  I'm not a GIS data storage guru (nor do I want to be one). But, postgres
handles graphic objects so I wonder why topology functions couldn't be added
to the base that already exists. After all, it's advertised as an
"object-relational dbms", and there are built-in graphics data types.

  Even when data are stored as arc-node sets, couldn't the connections be
stored in an associated table? I, much less than anyone here, do not
understand the issues involved.


Dr. Richard B. Shepard, President

                       Applied Ecosystem Services, Inc. (TM)
              Making environmentally-responsible mining happen. (SM)
            2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
 + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard at appl-ecosys.com

If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'

More information about the grass-dev mailing list