Ramp Length Calculator
Audit actual local3D ramp route polyline against independently reported chainage, not aggregate horizontal-run/rise modeled haul distance 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 ramp route length follows its ordered three-dimensional survey vertices.
A ramp route length follows its ordered three-dimensional survey vertices.1
Independent chainage can be compared with the polyline sum.
When to use Ramp 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 Ramp Length Calculator and understand its results
- Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.
- Enter observedRampSurveyXyzM, callerIndependentRouteChainageM, using the field meanings and rules below, then run the tool.
- Read observedRampSurveyPolylineM, signedChainageMinusSurveyM. 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 |
|---|---|---|---|
| observedRampSurveyXyzM | Observed ramp survey xyz m | numeric matrix | Required |
| callerIndependentRouteChainageM | Caller independent route chainage m | number | Required |
Require 2..128 local XYZ vertices with exactly three columns and nonnegative independent chainage. Sum Euclidean distances between adjacent vertices; repeated consecutive vertices contribute zero. Return length and chainage−length.
length=Σhypot(Δx,Δy,Δz); discrepancy=chainage−length Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| observedRampSurveyPolylineM | Observed ramp survey polyline m | number |
| signedChainageMinusSurveyM | Signed chainage minus survey m; preserve the subtraction order and sign defined in the mechanics | number |
{
"input": {
"observedRampSurveyXyzM": [
[
0,
0,
0
],
[
3,
4,
0
],
[
3,
4,
12
]
],
"callerIndependentRouteChainageM": 18
},
"output": {
"observedRampSurveyPolylineM": 17,
"signedChainageMinusSurveyM": 1
}
}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 Ramp Volume Calculator: Surveyed ramp segments can be recorded as separate prismatic sections with exclusions. 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
-
Ramp Length Calculator — tool.io
Similar or alternative tools
- Ramp Volume Calculator
Surveyed ramp segments can be recorded as separate prismatic sections with exclusions.
- Ore Body Strike Length Calculator
A strike-trace length follows the ordered local trace rather than only its endpoints.