Ok Michal,
yes it's possible to extract 2D sections to a *.gdb 3D array column, and
crooked lines should work even if the line segments are added as separate
segments using the database merge facility, i.e. if it's not initially done as
one crooked line.
For the example shown below though there is an existing line database *.gdb
file that was first Voxi inverted to create the 3D modeled properties voxel.
This voxel is then sliced along the flight lines (not very crooked lines) back
into the GDB file creating an array of susceptibility, density, or conductivity
along with a voxel topography channel.
Here's the OM menu work flow-
Geosoft line database->Voxi inverted to model properties-> Section Tools->
Sample Voxel To Database->
Section tools sample voxel to database menu
and the modeled density array and a voxel topo channel are created in this
example.
There are three options for the above depending on what's set in the GDB file
to be the Z coordinate, the example menu above is presented if there is no
specified Z coordinate channel, just the XY coordinates are specified. If the
Z is already set to the topographic elevation, the voxel topography channel
(Topo above) won't appear in the menu. If the Z channel is a depth array
channel, the depth array channel will be asked for, along with an elevation
(topography) channel.
All of the above three Z coordinate methods will populate an array data channel
in a line database with the voxel model property numbers for the selected
database lines that traverse across the voxel.
If any of the above discussion sounds off anyone please feel free to add their
two cents from their experience with the voxel sampling tool. One thing I've
noticed is the topo channel heights for the first voxel cell is offset in depth
to the voxel cell size. That is, if the topographic surface is say, 1500 m at
one voxel cell site, the first voxel Topography channel number (Topo above),
will be 1450 if 50 m voxel cubes are the cell sizes in the voxel.
Ed
On Monday, June 27, 2016 2:35 PM, author.nameemail
<[email protected]> wrote:
Hi Ed,
Thanks for the information, I wasn't aware of this feature til now.
It's not what I'm looking for though. The extraction from a 3D model is aimed
at creating a database that doesn't exist yet (unlike the case described in the
video, where the desired database already exists).
I appreciate the help!
Michal
---
Forum archives can be accessed here: http://lyris.geosoft.com/read/?forum=geonet
You are currently subscribed to geonet as: [email protected].
To subscribe or unsubscribe from any of our forums, select the User Forum
selection on the Geosoft Community page:
http://www.geosoft.com/support/community/forums/register/
---
Forum archives can be accessed here: http://lyris.geosoft.com/read/?forum=geonet
You are currently subscribed to geonet as: [email protected].
To subscribe or unsubscribe from any of our forums, select the User Forum
selection on the Geosoft Community page:
http://www.geosoft.com/support/community/forums/register/
