Description
Record an explicit residential geocoding precision assertion.
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.
Record an explicit residential geocoding precision assertion.
When to use this tool
Use Residential Address Geocode Precision Code when you already have recordId, suppliedPrecision, sourceMethod and need to record an explicit residential geocoding precision assertion.
How to use the tool and how it works
- Enter recordId, suppliedPrecision, sourceMethod. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter recordId, suppliedPrecision, sourceMethod using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordId | Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedPrecision | Supplied Precision | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceMethod | Source Method | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recordId": "R17",
"suppliedPrecision": "street centroid",
"sourceMethod": "method M4"
},
"output": {
"token": "[\"R17\",\"street centroid\",\"method M4\"]"
}
}Limitations and assumptions
- The result records supplied values without addresses, coordinate inference or privacy guarantees. Sources and asserted relationships are not independently authenticated.
- 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
Similar or alternative tools
- Neighborhood Boundary Vintage Tag
Preserve explicit neighborhood boundary source and vintage metadata.
- Migration Origin Destination Label
Qualify explicitly recorded migration endpoints by their classification version.