# Ability to multi-class pose labels but keep same keypoints

**URL:** <https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908>\
**Category:** 🛠️ Feature Reqs\
**Created:** [August 27, 2024, 5:51pm UTC](https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908 "2024-08-27T17:51:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hart\_Woolery](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/hart_woolery/32/2586_2.png) [@Hart\_Woolery](https://discuss.roboflow.com/u/Hart_Woolery)\
**Post date:** [August 27, 2024, 5:51pm UTC](https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908/1 "2024-08-27T17:51:40Z")

</div>

I would like to be able to handle the scenario where I have n-classes all with the same number/kind of keypoints. I’m not sure if this is currently possible the way classes are setup in pose. For example, I have 11 keypoints for a race car, and I want to classify the driver for each race car

---

<div class="post-metadata">

**Author:** ![Lake](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/lake/32/4110_2.png) [@Lake](https://discuss.roboflow.com/u/Lake)\
**Post date:** [August 27, 2024, 6:06pm UTC](https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908/2 "2024-08-27T18:06:15Z")

</div>

Hi there!

I would do this in a two stage model workflow. First run a keypoint detection model on the full image, then run a classification model on the driver. You can get the driver with another driver object detection model, or use the keypoint detection bounding box to crop!

Can you tell me more about your keypoint use case and how points might be used when doing a driver classification?

---

<div class="post-metadata">

**Author:** ![Hart\_Woolery](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/hart_woolery/32/2586_2.png) [@Hart\_Woolery](https://discuss.roboflow.com/u/Hart_Woolery)\
**Post date:** [August 27, 2024, 6:23pm UTC](https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908/3 "2024-08-27T18:23:02Z")

</div>

To clarify, what I’m really classifying is the race car (ie same bounding box as keypoints), it’s just easiest to name the class the driver’s name. since the output data is setup like class\_number, x,y,w,h,k1x,k1y,k1v,… i figure all I’m really changing here is the class\_number from the existing setup. I can’t do two models because this is realtime on edge device and needs to be done in a single pass

---

<div class="post-metadata">

**Author:** ![Hart\_Woolery](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/hart_woolery/32/2586_2.png) [@Hart\_Woolery](https://discuss.roboflow.com/u/Hart_Woolery)\
**Post date:** [August 27, 2024, 6:31pm UTC](https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908/4 "2024-08-27T18:31:36Z")

</div>

How I envision this in roboflow would be grouping the classes. All grouped classes share the same keypoints.

---

<div class="post-metadata">

**Author:** ![Lake](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/lake/32/4110_2.png) [@Lake](https://discuss.roboflow.com/u/Lake)\
**Post date:** [August 27, 2024, 6:45pm UTC](https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908/5 "2024-08-27T18:45:12Z")

</div>

Right, there is no way to group classes for keypoints currently. I can see how that would be useful for this case!

With our Workflows tool ([Roboflow Workflows: The open source tool to build vision applications](https://roboflow.com/workflows/build)) you can set up a two stage model workflow that can stream on edge with our Inference Pipeline. As you mention, this will be slower than one model, so I’m not sure if it will work for your use case. But this will definitely be the best option for accuracy!

Otherwise, manually creating each keypoints class should work, even though the setup will need to be done manually for each new class name.

---

<div class="post-metadata">

**Author:** ![Hart\_Woolery](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/hart_woolery/32/2586_2.png) [@Hart\_Woolery](https://discuss.roboflow.com/u/Hart_Woolery)\
**Post date:** [August 27, 2024, 9:30pm UTC](https://discuss.roboflow.com/t/ability-to-multi-class-pose-labels-but-keep-same-keypoints/6908/6 "2024-08-27T21:30:31Z")

</div>

Thanks, I will probably just create a separate classification model and use it to change classes on the keypoint data
