---
title: Motion Data - Biomechanics Output
description: The mocap data is organized as a list of frames, where each frame corresponds to a specific timestamp. Each frame contains joint data for various body parts. Below is the explanation of each field and
---
[Skip to content](https://docs.move.ai/knowledge/motion-data-biomechanics-output#main-content)
Open main navigation
Close main navigation
- [Move](https://www.move.ai/)
[Move](https://www.move.ai/)
Welcome to the Move Knowledge Base
- There are no suggestions because the search field is empty.
1. [Move Docs](https://docs.move.ai/knowledge?hsLang=en)
2. [Move One](https://docs.move.ai/knowledge/move-one?hsLang=en)
3. [Using your Animations](https://docs.move.ai/knowledge/move-one?hsLang=en#using-your-animations)
# Motion Data - Biomechanics Output
#### Data Structure
The mocap data is organized as a list of frames, where each frame corresponds to a specific timestamp. Each frame contains joint data for various body parts. Below is the explanation of each field and its meaning.
#### Timestamps
Each frame starts with a timestamp field, indicating the time at which the data was captured. The timestamp is represented in seconds.
#### Joint Data
The `joint_data` field contains a dictionary of joints, where each key is the name of a joint, and the value is an object containing the following properties:
- **Position**: A list with the x, y, and z coordinates of the joint in the world space (values are in meters).
- **Type**: The type of rotation (e.g., `euler_xyz`, `euler_x`, `euler_zyx`).
- **Rotations**: A list of rotation values, which varies in length depending on the type of rotation (values are in radians). These rotations are expressed their local coordinate frame.
- **Torques**: A list of torque values applied to the joint (values are newton-meter).
- **Reaction Forces**: The reaction force experienced by the foot joints (values are in Newton). If the value is 0.0, this means that the foot joint is not in contact with any surface.
#### Example of Joint Data
```
"Root": { "position": [-0.1304, -0.0399, 0.9518], "type": "euler_xyz", "rotations": [0.3791, -0.2012, 2.8031], "torques": [-337.3071, 241.416, 200.5884], "reaction_forces": 0.0 }
```
Each joint entry follows a similar structure, providing a comprehensive dataset for motion capture analysis.
---
- [Genesis](https://docs.move.ai/knowledge/genesis?hsLang=en#main-content)
- [Overview](https://docs.move.ai/knowledge/genesis?hsLang=en#overview)
- [System Prep & Setup](https://docs.move.ai/knowledge/genesis?hsLang=en#system-prep-setup)
- [Genesis Live](https://docs.move.ai/knowledge/genesis?hsLang=en#genesis-live)
- [Genesis Post](https://docs.move.ai/knowledge/genesis?hsLang=en#genesis-post)
- [Output Data](https://docs.move.ai/knowledge/genesis?hsLang=en#output-data)
- [Optimising your System](https://docs.move.ai/knowledge/genesis?hsLang=en#optimising-your-system)
- [System Management](https://docs.move.ai/knowledge/genesis?hsLang=en#system-management)
- [Release Notes](https://docs.move.ai/knowledge/genesis?hsLang=en#release-notes)
- [Move One](https://docs.move.ai/knowledge/move-one?hsLang=en#main-content)
- [Move One Pricing](https://docs.move.ai/knowledge/move-one?hsLang=en#move-one-pricing)
- [Move Platform](https://docs.move.ai/knowledge/move-one?hsLang=en#move-platform)
- [Move One iOS App](https://docs.move.ai/knowledge/move-one?hsLang=en#move-one-ios-app)
- [Using your Animations](https://docs.move.ai/knowledge/move-one?hsLang=en#using-your-animations)
- [Legacy Accounts - App Store Billing](https://docs.move.ai/knowledge/move-one?hsLang=en#legacy-accounts-app-store-billing)
- [Troubleshooting](https://docs.move.ai/knowledge/troubleshooting?hsLang=en#main-content)
- [Z-Cams](https://docs.move.ai/knowledge/troubleshooting?hsLang=en#z-cams)
- [Genesis](https://docs.move.ai/knowledge/troubleshooting?hsLang=en#genesis)
[](http://move.ai)
www.move.ai
Copyright © 2026, Move AI