Conditional Depth/Elevation

Question

Hi -

When a Bottom depth (in Stratigraphy) is equal to the Startholedepth (in Point), the Elevation/Depth prints at the top of the Core log, but not at the bottom of the soil log. I'm having the worst time trying to get the Elevation/Depth entity to print on the bottom of the test boring log..

I've added a Text with Depth entity to the ElevationDepth column on the test boring log. Here are my expressions:

Text Expression: <<Format(<<Calc(<<POINT.Elevation>> - <<PlungeFactor>> * <<STRATIGRAPHY.Bottom>>)>>,0.0)>>
<<Format(<<STRATIGRAPHY.Bottom>>,0.0)>>

Depth Expression: <<HasData(<<POINT.Elevation>>,<<STRATIGRAPHY.Bottom>>,<<Calc(<<STRATIGRAPHY.Bottom>>-0.175)>>)>>

Output Condition:

<<IIf(_
<<Calc(_
<<STRATIGRAPHY.Bottom>> = <<POINT.startholedepth>>_
)>>_
)>>

Kirk Johnson · Answer

Hi Terry,

It would be difficult without the files because some of the things you are describing are custom ways your files are setup.

I will take a random guess. You probably have 2 reports one with an expression that has an end depth based on your startholedepth field and another that has a start depth based on the startholedepth field. The data most likely doesn't display because the depth data equals at bottom of the first report.

You have the right approach with the "second entity" for this one value.

Again this is a random guess.

On this separate second entity I think your text expression should stay the same.

Try changing the Depth expression to

<<Calc(<<STRATIGRAPHY.Bottom>>-0.175)>>

The reason being is your expression says if you have elevation just use Stratigraphy bottom. We know that won't work cause the report is told to stop at startholedepth which matches the strat bottom

for your Output condition since this is a separate second entity

<<POINT.startholedepth>> = <<STRATIGRAPHY.Bottom>>

If this happens to work great. It would be much better to have the files (library and Project) .. No guarantees on the above example.