Skip to content

Main content

Tree Guild Layer Source Label

Qualify an explicit tree-guild layer label by source without asserting plant compatibility.

Loading tool…

Description

Qualify an explicit tree-guild layer label by source.

Garden-resource planning uses supplied geometry, material stocks, visit counts and accounting boundaries. Water elevation difference gives nominal head before losses, while a screened reject fraction uses the screened total. Local arithmetic does not establish plant compatibility, suitable animal care, drainage performance or a safe structural design.

Qualify an explicit tree-guild layer label by source.

When to use this tool

Use Tree Guild Layer Source Label when you already have plantRecordId, layerWording, source and need to qualify an explicit tree-guild layer label by source.

How to use the tool and how it works

  1. Enter plantRecordId, layerWording, source. 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 token. Use the output convention below.

Enter plantRecordId, layerWording, source using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
plantRecordIdPlant Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
layerWordingLayer WordingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
sourceSourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "plantRecordId": "P17",
    "layerWording": "understory",
    "source": "Plan A"
  },
  "output": {
    "token": "[\"P17\",\"understory\",\"Plan A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without asserting plant compatibility. Sources and asserted relationships are not independently authenticated.
  • 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.

Alternative or Complementary methods

Measure actual site geometry and reconcile resource stocks, transfers and observation periods. For water delivery, account for the complete hydraulic path and losses; nominal head and local garden margins remain preliminary bookkeeping or geometry.

References

  1. Calculation and input contract: permaculture/tree-guild-layer-source-label — tool.io

Similar or alternative tools