Regional Cubic to Board Foot Factor Lookup
Audit independently matched regional cubic-to-board-foot conversion factor. Audit caller independently verified matched reference against actual observation, not a fabricated specification. Caller independently verifies units, applicability and matching conditions; no operational recipe, safety certification, causal efficacy or legal/resource classification is inferred.
Description
Regional board-foot factors encode a specific assortment and scaling convention.
Regional board-foot factors encode a specific assortment and scaling convention.1
Comparing a submitted value with a supplied factor does not select the applicable region or replace log measurement. Use this tool to compare an observation with an exact caller-supplied numeric reference.
When to use Regional Cubic to Board Foot Factor Lookup
Use this tool to compare an observation with an exact caller-supplied numeric reference. Establish the species/site, survey protocol, units, sampled area or exposure, and the independently chosen reference or model.
How to use Regional Cubic to Board Foot Factor Lookup and understand its results
- Establish the species/site, survey protocol, units, sampled area or exposure, and the independently chosen reference or model.
- Enter callerRegionalBoardFootFactorIds, callerRegionalBoardFootFactorValues, queryRegionalBoardFootFactorId, observedRegionalBoardFootFactorValue, using the field meanings and rules below, then run the tool.
- Read callerMatchedRegionalBoardFootFactorValue, signedObservedMinusRegionalBoardFootFactorReference. Interpret the fields using their units, signs and evidence conventions below.
- If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerRegionalBoardFootFactorIds | Caller regional board foot factor ids | list of string | Required |
| callerRegionalBoardFootFactorValues | Caller regional board foot factor values | list of number | Required |
| queryRegionalBoardFootFactorId | Query regional board foot factor id | string | Required |
| observedRegionalBoardFootFactorValue | Observed regional board foot factor value | number | Required |
Enter nonempty aligned caller reference IDs and numeric reference values, an exact query ID and an observed value on the same unit and protocol basis. Reference values and the observation must be nonnegative; they need not be integers. IDs must be unique and nonblank, with at most 128 UTF-16 units each. The implementation uses case-sensitive exact matching without trimming, returns the matched reference value and subtracts it from the observation. An absent query or duplicate key fails. No regional dataset is installed, retrieved or authenticated.
reference=values[indexOfExact(queryId,ids)]; signedDifference=observed−reference Use the exact units, boundary rules, ordering and missing-evidence conventions above.
| Output field | Meaning | Value type |
|---|---|---|
| callerMatchedRegionalBoardFootFactorValue | Caller Matched Regional Board Foot Factor Value; follow the units, sign, ordering and evidence convention stated above | number |
| signedObservedMinusRegionalBoardFootFactorReference | Signed Observed Minus Regional Board Foot Factor Reference; follow the units, sign, ordering and evidence convention stated above | number |
{
"input": {
"callerRegionalBoardFootFactorIds": [
"a",
"b"
],
"callerRegionalBoardFootFactorValues": [
2,
4
],
"queryRegionalBoardFootFactorId": "b",
"observedRegionalBoardFootFactorValue": 5
},
"output": {
"callerMatchedRegionalBoardFootFactorValue": 4,
"signedObservedMinusRegionalBoardFootFactorReference": 1
}
}Limitations and assumptions
The numerical reference, unit basis and observation come from the caller. No authoritative regional table, standard edition, calibration or management rule is installed, retrieved or verified.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.
Alternative or Complementary methods
Use Kozak Taper Curve Calculator for this related task: A Kozak 1969-style taper relation expresses squared relative diameter as a quadratic in relative height.
Use Scribner/Doyle Log Scale Recovery Lookup when its separate inputs and assumptions fit the question: Scribner and Doyle references represent different board-foot estimation conventions.
References
Similar or alternative tools
- Kozak Taper Curve Calculator
A Kozak 1969-style taper relation expresses squared relative diameter as a quadratic in relative height.
- Scribner/Doyle Log Scale Recovery Lookup
Scribner and Doyle references represent different board-foot estimation conventions.