Label COCO Body Landmarks

@bleenco1 VersionLabel / Schema

Reindexes a flat [Landmark] keypoint list in COCO-body order into a named Landmarks2d.Human17 record, exposing the 17 joints by field name instead of array position. A Maybe<Landmarks2d.Human17> sink instead yields an empty result when the list is short.

How it fits

Typical backends

A COCO-convention pose estimator produces an ordered keypoint list that is named here, then drawn back onto the frame by visualize.

Named joints feed a consumer that addresses individual body parts by field, such as a joint-angle or posture metric expecting a typed pose record.

Caveats

Hard constraintWhen connected to a Landmarks2d.Human17 consumer the incoming input list must carry at least 17 points; a shorter list is a hard contract breach that stops the deployment. Connect a Maybe<Landmarks2d.Human17> consumer instead to tolerate short lists: a valid list yields the record and a short list yields an empty result, and every input always produces exactly one output.
OrderingJoints are assigned strictly by position (index 0 to 16 in COCO-body order). A list in any other order type-checks and runs but binds the wrong points to each named field with no error.
I/O contractOnly the first 17 entries are consumed; any points beyond index 16 in the input list are dropped silently.
LimitationThis is a pure relabeling step with no smoothing, confidence gating, or coordinate transformation; point values pass through unchanged.

Versions

53df2966latestdefault
Automated release
6/25/2026