Description
Resolve supplied corner-lot frontage names without deciding a statutory front-yard designation.
Planning indicators combine supplied counts, time intervals, distances, and area definitions. The denominator, geometric envelope, and category boundaries affect a reported density or share. A scenario calculation follows those assumptions while the governing rules and actual site conditions require separate verification.
Resolve supplied corner-lot frontage names without deciding a statutory front-yard designation.
When to use this tool
Use Setback Corner Lot Frontage Token when you need an explicit scenario indicator from supplied site dimensions, service records, or policy assumptions.
How to use the tool and how it works
- Enter frontageNames, selectedFrontages. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read matched, unknown. Use the output convention below.
Require distinct frontageNames and deduplicate selectedFrontages. Return selected names present in the bank as matched and the rest as unknown, preserving first selection order.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| frontageNames | Frontage Names | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| selectedFrontages | Selected Frontages | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| matched | Matched | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| unknown | Unknown | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
{
"input": {
"frontageNames": [
"north",
"east"
],
"selectedFrontages": [
"east",
"south"
]
},
"output": {
"matched": [
"east"
],
"unknown": [
"south"
]
}
}Limitations and assumptions
- This matches exact labels, not parcel geometry or street hierarchy. The caller defines frontage categories; the tool does not decide which corner-lot setback rule applies.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
- 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. Signed zero is exported as zero.
Alternative or Complementary methods
Check measured site data and the applicable authoritative definitions before using a scenario in a planning decision. Geographic analysis, transport modeling, or a complete design review may be needed beyond the stated term.
References
Similar or alternative tools
- Parcel Frontage Depth Ratio
Supplied parcel-dimension ratio without zoning or buildability interpretation.
- Parcel Setback Area Term
Compute one rectangular setback strip from supplied dimensions without accounting for corner overlaps or zoning rules.