[GRASS5] Re: An internal db for GRASS

Rich Shepard rshepard at appl-ecosys.com
Sat Feb 10 17:00:04 EST 2001

On Sat, 10 Feb 2001, Eric G . Miller wrote:

> In theory, you could use postgresql to store *all* data.  I think the
> only way it could work is to mostly *not* use the built-in geometric types
> and have some "middleware" for all I/O.  It would take a considerable
> amount of effort to come up with a workable base schema (you'd need
> extra catalog tables) and the "middleware" would have to have a lot of
> smarts built in.  I have a conception of how to do this, but it is not
> trivial.


  Well, I know postgres, and I've been writing database programs for almost
a decade now, so I could help with the effort.

  It seems to me that the effort would be worth-while. I see the need for a
comprehensive spatial/attribute relational database as a priority for GRASS
as it develops and expands its user base.


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