Skip to content

Main content

Residential Move Date Precision

Label explicitly supplied move-date text and precision without converting uncertain dates to exact timestamps.

Loading tool…

Description

Label a residential move-date transcription and declared precision.

Geographic activity records depend on location precision, boundary vintage, observation time, population denominator and access-window conventions. A travel-time budget differs from actual accessibility, and rectangular cell area does not establish privacy. Local shares and labels need the original survey and spatial definitions.

Label a residential move-date transcription and declared precision.

When to use this tool

Use Residential Move Date Precision when you already have moveId, dateText, precision and need to label a residential move-date transcription and declared precision.

How to use the tool and how it works

  1. Enter moveId, dateText, precision. 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 label. Use the output convention below.

Require moveId/dateText nonempty and precision day, month, year, approximate or unknown; JSON-quote the date text in the label.1

Input fieldMeaning and unitsAccepted input
moveIdMove IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
dateTextDate TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
precisionPrecisionRequired. Text; one of "day", "month", "year", "approximate", "unknown"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
labelLabelRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "moveId": "M17",
    "dateText": "2026-10",
    "precision": "month"
  },
  "output": {
    "label": "M17; date=\"2026-10\"; precision=month"
  }
}

Limitations and assumptions

  • The date is not parsed and precision is not inferred; no actual move, residency or chronology is verified.
  • 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.

Alternative or Complementary methods

Use the actual route, service schedule, survey frame and boundary source when assessing mobility or access. Review disclosure across the full spatial dataset and linked records; a location label or cell-size product is not a complete privacy method.

References

  1. Calculation and input contract: human-geography/residential-move-date-precision — tool.io

Similar or alternative tools