Ore Body Strike Length Calculator
Inventory actual independently identified local ore strike trace segments, not point-to-point map distance or discovery of strike/geodesy. Caller independently verifies units, applicability and matching conditions; no operational recipe, safety certification, causal efficacy or legal/resource classification is inferred.
Description
A strike-trace length follows the ordered local trace rather than only its endpoints.
A strike-trace length follows the ordered local trace rather than only its endpoints.1
Trace identity and order must be established independently.
When to use Ore Body Strike Length 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 Strike Length Calculator and understand its results
- Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.
- Enter observedOreStrikeTraceLocalXyM, callerIndependentlyOrderedStrikeTraceVerified, using the field meanings and rules below, then run the tool.
- Read observedStrikePolylineLengthM. 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 |
|---|---|---|---|
| observedOreStrikeTraceLocalXyM | Observed ore strike trace local xy m | numeric matrix | Required |
| callerIndependentlyOrderedStrikeTraceVerified | Caller independently ordered strike trace verified | boolean | Required |
Require the trace-verified flag true and 2..128 XY vertices with exactly two columns. Sum adjacent Euclidean segment lengths in the supplied order. Repeated vertices are allowed; no geographic projection is performed.
length=Σhypot(Δx,Δy) Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| observedStrikePolylineLengthM | Observed strike polyline length m | number |
{
"input": {
"observedOreStrikeTraceLocalXyM": [
[
0,
0
],
[
3,
0
],
[
3,
4
]
],
"callerIndependentlyOrderedStrikeTraceVerified": true
},
"output": {
"observedStrikePolylineLengthM": 7
}
}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 Ore Body Width Calculator: A projected footprint width depends on an independently chosen direction in local coordinates. For a complementary comparison, use Ramp Length Calculator: A ramp route length follows its ordered three-dimensional survey vertices.
References
-
Ore Body Strike Length Calculator — tool.io
Similar or alternative tools
- Ore Body Width Calculator
A projected footprint width depends on an independently chosen direction in local coordinates.
- Ramp Length Calculator
A ramp route length follows its ordered three-dimensional survey vertices.