Our application as loaded is showing us a slice at a specific X coordinate where the geologic surfaces or horizons can be quite different depending on how we choose to impose hierarchy rules.
Along the left side of the slice, the ordering of the horizons is unambiguous. These horizons, highlighted by the bright lines are:
Ground Surface
Bottom of First Gravel
Bottom of Sand
Bottom of Second Gravel
Bottom of Silty Sand
Bottom of Silt
Bottom of Clay
Bottom of Third Gravel
As we move to the right, beyond the center of the slice, the ordering of these horizons becomes less obvious since the 6th horizon (bottom of slit) intersects and is above the two higher horizons (5 and ultimately 4).
The geologic_surfaces module in our application has its "Account for Hierarchy" toggle off
which is why the normal hierarchy as created by 3D_Geology_Map
and shown with slice differs from the highlighting horizon lines.
If we turn on the "Reverse Surface Hierarchy" toggle, the layering in the slice is dramatically different:
This reversed hierarchy favors the lower surfaces and allows the bottom of Silt to intrude into the two layers above (Silty Sand and Second Gravel), causing those two layers to thin and/or pinch out.
If we connect plume_shell to the Viewer and set the Explode Distance (in Explode_and_Scale) to 15, we can see the 3D representation of this model, in the REVERSED hierarchy:
and the NORMAL hierarchy
© 1994-2018 ctech.com