Skip to content

Main content

Residential Mobility Tenure Month Term Tool

Explicit month-coordinate tenure and prior-move exposure rate; months are ordinal coordinates, not fixed day durations.

Loading tool…

Description

Return month-coordinate tenure and 12 × previousMoves/exposureMonths.

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.

Return month-coordinate tenure and 12 × previousMoves/exposureMonths.

When to use this tool

Use Residential Mobility Tenure Month Term when you need one transparent population-accounting component.

How to use the tool and how it works

  1. Enter moveInMonth, observationMonth, previousMoves, exposureMonths. 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 tenureMonths, movesPerYear. Use the output convention below.

Require observationMonth no earlier than moveInMonth, nonnegative previousMoves, and positive exposureMonths. Return month-coordinate tenure and 12 × previousMoves/exposureMonths.1

Input fieldMeaning and unitsAccepted input
moveInMonthMove In MonthRequired. Safe integer.
observationMonthObservation MonthRequired. Safe integer.
previousMovesPrevious MovesRequired. Safe integer; minimum 0.
exposureMonthsExposure MonthsRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
tenureMonthsTenure MonthsRequired. Safe integer.
movesPerYearMoves Per YearRequired. Finite number.
json
{
  "input": {
    "moveInMonth": 100,
    "observationMonth": 130,
    "previousMoves": 3,
    "exposureMonths": 60
  },
  "output": {
    "tenureMonths": 30,
    "movesPerYear": 0.6
  }
}

Limitations and assumptions

  • Month inputs are numeric coordinates rather than parsed dates; annualized moves use the supplied exposure, without modeling mobility or household stability.
  • 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/residential-mobility-tenure-month-term — tool.io

Similar or alternative tools