Pit Depth Calculator
Audit actual matched rim/floor elevations across pit survey pairs, not assumed slope×radius or geodesy. Caller independently verifies units, applicability and matching conditions; no operational recipe, safety certification, causal efficacy or legal/resource classification is inferred.
Description
A rim-to-floor depth needs paired elevations sharing the same datum.
A rim-to-floor depth needs paired elevations sharing the same datum.1
Multiple paired observations can have different depths.
When to use Pit Depth Calculator
Use this tool to calculate or review the supplied observations under the stated rules. Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.
How to use Pit Depth Calculator and understand its results
- Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.
- Enter observedPitRimLevelsM, observedPitFloorLevelsM, using the field meanings and rules below, then run the tool.
- Read observedRimToFloorDepthsM, maximumObservedPitDepthM. Inspect nested result fields where present, and review unknown records separately from known matches.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedPitRimLevelsM | Observed pit rim levels m | list of number | Required |
| observedPitFloorLevelsM | Observed pit floor levels m | list of number | Required |
Use nonempty aligned finite rim and floor levels. Compute rim−floor, require every depth≥0, and return all depths plus their maximum.
depth_i=rim_i−floor_i; maximum=max(depth_i) Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| observedRimToFloorDepthsM | Observed rim to floor depths m | list of number |
| maximumObservedPitDepthM | Maximum observed pit depth m | number |
{
"input": {
"observedPitRimLevelsM": [
100,
102
],
"observedPitFloorLevelsM": [
80,
81
]
},
"output": {
"observedRimToFloorDepthsM": [
20,
21
],
"maximumObservedPitDepthM": 21
}
} Limitations and assumptions
Units, ledger boundaries, survey interpretation and model applicability must be independently established. These summaries do not assign reserve/resource classifications or establish support adequacy, ventilation safety or an operating setting.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above.
Alternative or Complementary methods
For a related step, use Pit Diameter Calculator: An observed pit boundary can be summarized by its largest point-pair chord. For a complementary comparison, use Bench Height Calculator: Bench height uses top and toe elevations sharing a survey datum.
References
-
Pit Depth Calculator — tool.io
Similar or alternative tools
- Pit Diameter Calculator
An observed pit boundary can be summarized by its largest point-pair chord.
- Bench Height Calculator
Bench height uses top and toe elevations sharing a survey datum.