On Wednesday 23 November 2005 17:15, Brent Wood wrote:
> I suggest you look at PostGIS to store 2D & 3D geometric (spatial) data,
> it may solve some of your problems
>
> You can store a vertical line as a well, and segments of that line which
> represent the layers you are describing.
>
> Bren
I suggest you look at PostGIS to store 2D & 3D geometric (spatial) data,
it may solve some of your problems
You can store a vertical line as a well, and segments of that line which
represent the layers you are describing.
Brent Wood
On Tue, 22 Nov 2005, Dennis Veatch wrote:
> On Tuesday
On Tuesday 22 November 2005 11:40, Lincoln Yeoh wrote:
> At 01:19 PM 11/21/2005 -0500, Dennis Veatch wrote:
> >I had thought just adding some fields called topsoil_start/topsoil_end,
> >gravel_start/gravel_end, etc. But them I'm left with how to take those
> > values and give to total depth for eac
At 01:19 PM 11/21/2005 -0500, Dennis Veatch wrote:
I had thought just adding some fields called topsoil_start/topsoil_end,
gravel_start/gravel_end, etc. But them I'm left with how to take those values
and give to total depth for each layer and total depth of the well.
But I'm not sure that is t
The problem is that each well can have a different number of and types of
layers. Trying to pre-plan all the combinations could be a big headache. My
first thought is the following layout-
well_number layer_number bottom_depth layer_type
1 1 10
On Monday 21 November 2005 20:04, Michael Glaesemann wrote:
> On Nov 22, 2005, at 3:19 , Dennis Veatch wrote:
> > I had thought just adding some fields called topsoil_start/
> > topsoil_end,
> > gravel_start/gravel_end, etc. But them I'm left with how to take
> > those values
> > and give to total
On Nov 22, 2005, at 3:19 , Dennis Veatch wrote:
I had thought just adding some fields called topsoil_start/
topsoil_end,
gravel_start/gravel_end, etc. But them I'm left with how to take
those values
and give to total depth for each layer and total depth of the well.
But I'm not sure that is
