Skip to content

Main content

Census Area Boundary Population Factor Tool

Rebase a population inventory using explicit transferred counts, not an area-proportional population assumption.

Loading tool…

Description

Subtract transferredOut within oldPopulation and add nonnegative transferredIn for rebasedPopulation.

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.

Subtract transferredOut within oldPopulation and add nonnegative transferredIn for rebasedPopulation.

When to use this tool

Use Census Area Boundary Population Factor when you need one transparent population-accounting component.

How to use the tool and how it works

  1. Enter oldPopulation, transferredOut, transferredIn, newLandArea. 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 rebasedPopulation, newDensity, netBoundaryChange. Use the output convention below.

Subtract transferredOut within oldPopulation and add nonnegative transferredIn for rebasedPopulation. Divide by positive newLandArea and return netBoundaryChange.1

Input fieldMeaning and unitsAccepted input
oldPopulationOld PopulationRequired. Finite number; minimum 0.
transferredOutTransferred OutRequired. Finite number; minimum 0.
transferredInTransferred InRequired. Finite number; minimum 0.
newLandAreaNew Land AreaRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
rebasedPopulationRebased PopulationRequired. Finite number.
newDensityNew DensityRequired. Finite number.
netBoundaryChangeNet Boundary ChangeRequired. Finite number.
json
{
  "input": {
    "oldPopulation": 10000,
    "transferredOut": 1000,
    "transferredIn": 2500,
    "newLandArea": 50
  },
  "output": {
    "rebasedPopulation": 11500,
    "newDensity": 230,
    "netBoundaryChange": 1500
  }
}

Limitations and assumptions

  • Transfers describe boundary reassignment, not necessarily migration; population counts and land area must refer to compatible records and dates.
  • 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/census-area-boundary-population-factor — tool.io

Similar or alternative tools