Ore Body Width Calculator
Measure observed ore footprint span in independently specified local width direction, not fitted geological width, geodesy or coordinate inference. Caller independently verifies units, applicability and matching conditions; no operational recipe, safety certification, causal efficacy or legal/resource classification is inferred.
Description
A projected footprint width depends on an independently chosen direction in local coordinates.
A projected footprint width depends on an independently chosen direction in local coordinates.1
It is a sampled directional span rather than a fitted geological boundary.
When to use Ore Body Width 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 Ore Body Width Calculator and understand its results
- Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.
- Enter observedOreLocalPlanXyM, callerUnitWidthDirectionXy, using the field meanings and rules below, then run the tool.
- Read observedProjectedOreWidthM. 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 |
|---|---|---|---|
| observedOreLocalPlanXyM | Observed ore local plan xy m | numeric matrix | Required |
| callerUnitWidthDirectionXy | Caller unit width direction xy | list of number | Required |
Use a nonempty XY matrix with exactly two columns and a two-element direction whose Euclidean norm differs from one by at most 1e−10. Project every point by dot product and return max−min projection. One point returns zero.
width=max(p_i·direction)−min(p_i·direction) Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| observedProjectedOreWidthM | Observed projected ore width m | number |
{
"input": {
"observedOreLocalPlanXyM": [
[
0,
0
],
[
3,
4
],
[
1,
2
]
],
"callerUnitWidthDirectionXy": [
0,
1
]
},
"output": {
"observedProjectedOreWidthM": 4
}
}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 Ore Body Strike Length Calculator: A strike-trace length follows the ordered local trace rather than only its endpoints.
References
-
Ore Body Width Calculator — tool.io
Similar or alternative tools
- Pit Diameter Calculator
An observed pit boundary can be summarized by its largest point-pair chord.
- Ore Body Strike Length Calculator
A strike-trace length follows the ordered local trace rather than only its endpoints.