Anchor
Definition
An Anchor represents the curated Point used as the preferred display location of a specific Address OR non-addressable device, service, equipment or physical environment. In both cases, the record serves as the anchoring point from which another feature (i.e. Occupant) can derive, reference or inherit the Anchor's attribution.
Feature Structure
- Anchor objects are Feature objects
- Anchor objects MUST have an
"id"
member with aFEATURE-ID
value - Anchor objects MUST have a
"feature_type"
member with the value"anchor"
- Anchor objects MUST have a
"geometry"
member with aPOINT
value
Property Keys
Property | Type | Description |
---|---|---|
address_id |
null or ADDRESS-ID |
ID reference to Address record |
unit_id |
UNIT-ID |
Unique identifier of the Unit the Anchor possesses a spatial relationship with |
Example
{
"id": "11111111-1111-1111-1111-111111111111",
"type": "Feature",
"feature_type": "anchor",
"geometry": {
"type": "Point",
"coordinates": [1.0, 2.0]
},
"properties": {
"address_id": "22222222-2222-2222-2222-222222222222",
"unit_id": "33333333-3333-3333-3333-333333333333"
}
}
Property Capturing Rules
ADDRESS_ID
- MUST be
null
when the Anchor feature is used solely for placement of a non-addressable location
UNIT_ID
- Anchor MUST be placed within the referenced Unit
Geometry Capturing Rules
- Individual Anchors MUST be created to denote a preferred display location of an allowable feature to support the following use cases:
- Snapping behavior in editing tools
- Derivation of an addressable entity's Point location based on reference to an Anchor by ID OR matched Address
- Decoupling of predetermined Address locations from volatile content subject to frequent updates or redelivery in other formats (i.e. Occupants)
- Zero or more Anchors MAY be placed within a Unit
- Zero or more Anchors MAY be placed within a Fixture or Kiosk
- Anchor placement SHOULD be orderly and patterned to produce a desirable map aesthetic quality when features are "snapped" to them. (Illustration)