Skip site navigation (1) Skip section navigation (2)

Re: Entering '<1' and 'BDL'

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: Postgresql PDX_Users <pdxpug(at)postgresql(dot)org>
Subject: Re: Entering '<1' and 'BDL'
Date: 2010-04-20 20:25:10
Message-ID: alpine.LNX.2.00.1004201318470.4238@salmo.appl-ecosys.com (view raw or flat)
Thread:
Lists: pdxpug
On Tue, 20 Apr 2010, Tom Keller wrote:

> Why distinguish "below detection limit" at the data level? I would use the
> ... value measured and enforce the ramification of the detection limit in
> subsequent analysis. Then use NULL for missing values only. or isn't that
> feasible?

Tom,

   There is no measured value when it falls below the detection limit of the
instrument. Consider: you have a 6' measuring tape and you use that to
measure the length of your car. The car extends beyond the length of the
tape. What value do you enter for car length?

   There are actually three situations that may occur with permit compliance
monitoring, and each must be recorded as distinct from the others. One, the
sample was not taken, or analyzed, or entered in the system. Two, the sample
was taken and analyzed, but the value falls outside the measuring range of
the instrument (or analytical method) used. Three, the sample could not be
taken because the stream channel was dry (ergo, no water to sample), the
pond frozen (ditto), or the machinery shut down and the plant not operating.
The latter two are expected and reasonable occurrences; the first one is a
no-no.

Rich

In response to

Responses

pdxpug by date

Next:From: Tom KellerDate: 2010-04-20 20:49:10
Subject: Re: Entering '<1' and 'BDL'
Previous:From: Tom KellerDate: 2010-04-20 19:49:50
Subject: Re: Entering '<1' and 'BDL'

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group