Skip to content

Main content

Activity Diary Location Precision

Attach explicit spatial-precision wording to an activity diary entry without geocoding or inferring a location.

Loading tool…

Description

Label an activity-diary location transcription with a supplied precision tag.

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 an activity-diary location transcription with a supplied precision tag.

When to use this tool

Use Activity Diary Location Precision when you already have entryId, locationWording, precisionTag and need to label an activity-diary location transcription with a supplied precision tag.

How to use the tool and how it works

  1. Enter entryId, locationWording, precisionTag. 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 entryId/locationWording/precisionTag nonempty; JSON-quote the location text in the label.1

Input fieldMeaning and unitsAccepted input
entryIdEntry IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
locationWordingLocation WordingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
precisionTagPrecision TagRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
labelLabelRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "entryId": "D17",
    "locationWording": "District A",
    "precisionTag": "district"
  },
  "output": {
    "label": "D17; location=\"District A\" [district]"
  }
}

Limitations and assumptions

  • No location is derived or generalized and the label does not establish adequate privacy or actual spatial precision.
  • 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/activity-diary-location-precision — tool.io

Similar or alternative tools