Skip to content

Main content

Urban Density Area Basis Label Tool

Compute a density while retaining an explicit area-basis label; no gross/net boundary conversion is inferred.

Loading tool…

Description

Divide nonnegative count by positive areaHectares and append the selected gross, net, residential, or developable basis label.

Urban indicators compare counts or areas within a defined study boundary. Changing the denominator, the counted units, or whether a share is expressed as a fraction changes the meaning even when the arithmetic is correct.

Divide nonnegative count by positive areaHectares and append the selected gross, net, residential, or developable basis label.

When to use this tool

Use Urban Density Area Basis Label when you need a reproducible density or share using an explicitly chosen study boundary and denominator.

How to use the tool and how it works

  1. Enter count, areaHectares, basis. 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 densityPerHectare, label. Use the output convention below.

Divide nonnegative count by positive areaHectares and append the selected gross, net, residential, or developable basis label.1

Input fieldMeaning and unitsAccepted input
countCount under the stated selection and duplicate convention.Required. Finite number; minimum 0.
areaHectaresArea HectaresRequired. Finite number; strictly above 0.
basisBasisRequired. Text; one of "gross", "net", "residential", "developable"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
densityPerHectareDensity Per HectareRequired. Finite number.
labelFormatted label for the supplied components under the convention above.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "count": 200,
    "areaHectares": 4,
    "basis": "net"
  },
  "output": {
    "densityPerHectare": 50,
    "label": "net area basis"
  }
}

Limitations and assumptions

  • The basis label is supplied rather than verified; counts and area coverage must be compatible for a meaningful density.
  • 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

Document the data definitions and compare several planning indicators rather than treating one ratio as a design verdict.

References

  1. Calculation and input contract: urban-planning/urban-density-area-basis-label — tool.io

Similar or alternative tools