Pit Diameter Calculator
Measure maximum actual local pit-boundary point-pair chord, not equivalent-area circle diameter, unsampled boundary inference or geodesy. Caller independently verifies units, applicability and matching conditions; no operational recipe, safety certification, causal efficacy or legal/resource classification is inferred.
Description
An observed pit boundary can be summarized by its largest point-pair chord.
An observed pit boundary can be summarized by its largest point-pair chord.1
That sampled planar chord differs from an equivalent-area diameter.
When to use Pit Diameter 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 Diameter Calculator and understand its results
- Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.
- Enter observedPitBoundaryLocalXyM, using the field meanings and rules below, then run the tool.
- Read maximumObservedPitBoundaryChordM. 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 |
|---|---|---|---|
| observedPitBoundaryLocalXyM | Observed pit boundary local xy m | numeric matrix | Required |
Require 2..128 local XY boundary points with exactly two columns. Inspect every unordered pair, compute the Euclidean distance and return the maximum. Identical points can produce a zero maximum; no geodesic conversion is performed.
diameterObserved=max_(i<j) hypot(x_j−x_i,y_j−y_i) Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| maximumObservedPitBoundaryChordM | Maximum observed pit boundary chord m | number |
{
"input": {
"observedPitBoundaryLocalXyM": [
[
0,
0
],
[
3,
0
],
[
3,
4
]
]
},
"output": {
"maximumObservedPitBoundaryChordM": 5
}
}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 Depth Calculator: A rim-to-floor depth needs paired elevations sharing the same datum. For a complementary comparison, use Ore Body Width Calculator: A projected footprint width depends on an independently chosen direction in local coordinates.
References
-
Pit Diameter Calculator — tool.io
Similar or alternative tools
- Pit Depth Calculator
A rim-to-floor depth needs paired elevations sharing the same datum.
- Ore Body Width Calculator
A projected footprint width depends on an independently chosen direction in local coordinates.