Skip to content

Main content

Neighborhood Service Per Capita Gap Tool

Calculate neighborhood service per capita gap from explicit caller-supplied inputs.

Loading tool…

Description

Scale nonnegative localServices by basePopulation/localPopulation, both positive.

Population indicators depend on compatible boundaries, time periods, counted groups, and denominator choices. A share or density can change when exclusions or daytime populations change, even without arithmetic error.

Scale nonnegative localServices by basePopulation/localPopulation, both positive.

When to use this tool

Use Neighborhood Service Per Capita Gap when you need one transparent population-accounting component.

How to use the tool and how it works

  1. Enter localServices, localPopulation, benchmarkPerBase, basePopulation. 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 localPerBase, gap, servicesForBenchmark. Use the output convention below.

Scale nonnegative localServices by basePopulation/localPopulation, both positive. Subtract nonnegative benchmarkPerBase and compute localPopulation × benchmark/basePopulation for servicesForBenchmark.1

Input fieldMeaning and unitsAccepted input
localServicesLocal ServicesRequired. Finite number; minimum 0.
localPopulationLocal PopulationRequired. Finite number; strictly above 0.
benchmarkPerBaseBenchmark Per BaseRequired. Finite number; minimum 0.
basePopulationBase PopulationRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
localPerBaseLocal Per BaseRequired. Finite number.
gapSigned difference under the stated subtraction order.Required. Finite number.
servicesForBenchmarkServices For BenchmarkRequired. Finite number.
json
{
  "input": {
    "localServices": 4,
    "localPopulation": 2000,
    "benchmarkPerBase": 3,
    "basePopulation": 1000
  },
  "output": {
    "localPerBase": 2,
    "gap": -1,
    "servicesForBenchmark": 6
  }
}

Limitations and assumptions

  • Service definitions and population bases must match; the benchmark is supplied and does not establish service adequacy, entitlement, or actual access.
  • 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 source definitions, geography, temporal alignment, and uncertainty before making a demographic or service-access conclusion.

References

  1. Calculation and input contract: human-geography/neighborhood-service-per-capita-gap — tool.io

Similar or alternative tools