Skip to content

Main content

Agroforestry Shared Cost Share

Allocate an explicit shared cost using a supplied nonnegative weight share without selecting an allocation policy.

Loading tool…

Description

Allocate supplied shared cost by a stated weight share.

Agroforestry records distinguish position counts, nominal clearances, dry-mass allocation, source labels and year-index conventions. A stated setback threshold is not automatically an applicable legal requirement, and a rotation-year margin does not establish a suitable cutting interval. Local ratios preserve supplied assumptions.

Allocate supplied shared cost by a stated weight share.

When to use this tool

Use Agroforestry Shared Cost Share when you already have totalSharedCost, assignedWeight, sumOfWeights and need to allocate supplied shared cost by a stated weight share.

How to use the tool and how it works

  1. Enter totalSharedCost, assignedWeight, sumOfWeights. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read allocatedCost, allocationFraction. Use the output convention below.

Require cost/assigned weight>=0, sumOfWeights>0 and assigned<=sum; fraction=assigned/sum, cost=total*fraction.1

Input fieldMeaning and unitsAccepted input
totalSharedCostTotal Shared CostRequired. Finite number; minimum 0.
assignedWeightAssigned WeightRequired. Finite number; minimum 0.
sumOfWeightsSum Of WeightsRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
allocatedCostAllocated CostRequired. Finite number.
allocationFractionAllocation FractionRequired. Finite number.
json
{
  "input": {
    "totalSharedCost": 1000,
    "assignedWeight": 3,
    "sumOfWeights": 10
  },
  "output": {
    "allocatedCost": 300,
    "allocationFraction": 0.3
  }
}

Limitations and assumptions

  • Currency and weighting definitions are supplied. This does not verify all weights, establish fair allocation, ownership, entitlement or actual cost.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review original tree, site, measurement, cost and management records. Use complete ecological, arboricultural, veterinary and applicable legal assessment when local counts or margins cannot establish an appropriate decision.

References

  1. Calculation and input contract: agroforestry/agroforestry-shared-cost-share — tool.io

Similar or alternative tools