zone-occupancy
CORE · WIREDZone occupancy: presence, not throughput. Whether a defined region is occupied right now, by how many objects of what class and since when, plus interval reports. A capability any device can implement, from an in-ground magnetometer to a camera.
Data model
The configuration and state tree. Safety constraints are expressed as YANG must and validated at every boundary.
grouping zone-occupancy { // a device "uses" it, typically behind a feature
container zone-occupancy {
container configuration {
list zone {
key "zone-id";
leaf sensing-method { type identityref; } // loop, magnetometer, video...
leaf classifies { type boolean; } // can this zone report object class?
}
}
container zones {
config false; // live rollup of the change stream
list zone {
key "zone-id";
leaf presence { type boolean; }
leaf occupancy-count { type uint16; units "objects"; }
leaf occupied-since { type date-and-time; }
list present-class { key "class"; } // class, count, confidence
}
}
}
// presence, not throughput: counts of what passed stay in vehicle-detection
}
Notifications & events
Each event is its own typed notification with its own ce-type. Consumers filter by subject before parsing.
Event families:
zone
Subject & bindings
# canonical subject (reference CloudEvents binding)
openits.us-tx.txdot.d07.zone-occupancy.i35-exit-214.zone-occupancy-changed
Schema registry
Every revision is immutable and content-addressed. Cite the exact date in ce-dataschema; there is no latest alias.