Label Halpe Body Landmarks

@bleenco1 VersionLabel / Schema

Reindexes a flat [Landmark] list in Halpe-26 order into a named Landmarks2d.Human26 record with full-body and foot fields. A Maybe<Landmarks2d.Human26> sink yields an empty result on a short list; either arm always emits exactly one output.

How it fits

Typical backends

A Halpe-26 estimator's keypoints are named, then drawn back onto the frame by visualize for a full-body overlay including the feet.

The named record feeds a gait or biomechanics metric that reads the foot joints by field, such as a stride or heel-strike measure.

Caveats

Hard constraintWhen connected to a Landmarks2d.Human26 consumer the incoming input list must carry at least 26 points; a shorter list is a hard contract breach that stops the deployment. Connect a Maybe<Landmarks2d.Human26> 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 bound strictly by position in full Halpe-26 order (body keypoints, then head/neck/hip, then the six foot points). A list in any other order runs without error but names the wrong points.
I/O contractOnly the first 26 points are consumed; entries beyond index 25 on input are dropped silently.
AccuracyFoot keypoints are typically the least reliable part of a pose estimate; this step copies them through unchanged, so low-resolution or occluded feet stay noisy with no quality flag.

Versions

7a9bdd7elatestdefault
Automated release
6/25/2026