Re: Designing a DB for storing biological data

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Designing a DB for storing biological data
Date: 2014-06-14 19:03:11
Message-ID: alpine.LNX.2.11.1406141157180.17243@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 14 Jun 2014, Damir Dezeljin wrote:

> I am designing a database for storing various biological and ecological
> data. Although there is no clear dividing line, it is possible to group
> the data into two groups, namely the measured (physical) and quantitative
> (mostly biological) data;

I left a couple of comments out of my first response.

First, measurements are quantitative so it does not matter what you're
measuring, all your data are quantitative. Your physical, chemical, and
geomorphic data (study area size, water velocity, air temperature) are ratio
data of continuous measurements. Your biological data are counts and/or size
or weight measurements.

Second, your database queries should be those appropriate to extract the
data you wish to statistically analyze, which is what I assume is the point
of the whole exercise. The database is for storage. You can do your spatial
analyses with GRASS and your statistical analyses with R.

Rich

--
Richard B. Shepard, Ph.D.
Applied Ecosystem Services, Inc. | Troutdale, OR 97060 USA
www.appl-ecosys.com Voice: 503-667-4517 Fax: 503-667-8863

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-06-14 19:03:45 Re: Using pg_start_backup() and pg_stop_backup() - using 9.1.2.2
Previous Message Rich Shepard 2014-06-14 18:24:58 Re: Designing a DB for storing biological data