Description
Convert supplied core depths to elevations while retaining the raw signed depth difference.
Geological records use depth datums, age-before-present coordinates and recovery definitions. A signed difference or recovered-length ratio can expose a supplied inconsistency without reconstructing geological history or correcting sample loss.
Convert supplied core depths to elevations while retaining the raw signed depth difference.
When to use this tool
Use Core Top Bottom Datum Sign when checking an explicit geological coordinate, interval or recovery convention.
How to use the tool and how it works
- Enter topDepth, bottomDepth, datumElevation, depthPositiveDown. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read topElevation, bottomElevation, signedThickness. Use the output convention below.
Convert topDepth and bottomDepth to elevations by subtracting from datumElevation when depthPositiveDown, otherwise adding. signedThickness always equals bottomDepth-topDepth.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| topDepth | Top Depth | Required. Finite number. |
| bottomDepth | Bottom Depth | Required. Finite number. |
| datumElevation | Datum Elevation | Required. Finite number. |
| depthPositiveDown | Depth Positive Down | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| topElevation | Top Elevation | Required. Finite number. |
| bottomElevation | Bottom Elevation | Required. Finite number. |
| signedThickness | Raw bottomDepth-topDepth, unaffected by depthPositiveDown. | Required. Finite number. |
{
"input": {
"topDepth": 2,
"bottomDepth": 7,
"datumElevation": 100,
"depthPositiveDown": true
},
"output": {
"topElevation": 98,
"bottomElevation": 93,
"signedThickness": 5
}
}Limitations and assumptions
- All lengths share one unit. The thickness field retains raw coordinate order even when the elevation convention changes; layer validity and datum accuracy are not established.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use verified datums, original logs and appropriate geological interpretation when correlating units or reconstructing missing intervals.
References
Similar or alternative tools
- Core Depth Reference Offset
offset = recordedDepth-referenceDepth, negated when positiveDown is false.
- Lithology Log Interval Share
overlapThickness is the nonnegative intersection of the two depth intervals; logShare divides it by logBase-logTop.