Description
Preserve explicit neighborhood boundary source and vintage metadata.
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.
Preserve explicit neighborhood boundary source and vintage metadata.
When to use this tool
Use Neighborhood Boundary Vintage Tag when you already have neighborhoodId, boundarySource, vintageText and need to preserve explicit neighborhood boundary source and vintage metadata.
How to use the tool and how it works
- Enter neighborhoodId, boundarySource, vintageText. 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 neighborhoodId, boundarySource, vintageText 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 |
|---|---|---|
| neighborhoodId | Neighborhood Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| boundarySource | Boundary Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| vintageText | Vintage Text | 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": {
"neighborhoodId": "N17",
"boundarySource": "map M4",
"vintageText": "2020 boundaries"
},
"output": {
"token": "[\"N17\",\"map M4\",\"2020 boundaries\"]"
}
}Limitations and assumptions
- The result records supplied values without harmonizing spatial units. 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
- Household Move Origin Destination Distance Tag
Preserve explicit household move zone and distance metadata.
- Residential Address Geocode Precision Code
Record an explicit residential geocoding precision assertion.