> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/section-02-using-velogic-studio/road-metrics.md).

# Road metrics

Reference guide for joint angle, movement quality, and position metrics used in Velogic Studio for road bike fitting.

Our system offers an extensive range of metrics. Using 3D data well requires combining multiple factors in your decision making. Here is some guidance for "orthodox" positions.

## Joint Angle Metrics

| Metric         | Range                                     |
| -------------- | ----------------------------------------- |
| Ankle Angle    | Average 100-130, range < 30               |
| Knee Angle     | Max 140-145, Min >68                      |
| Hip Angle      | Max 90-105, up to 120 if rider has issues |
| Shoulder Angle | Average 75-100                            |
| Elbow Angle    | Average 155-170                           |
| Torso Angle    | 35-40 for Elite, 40-50 general, 50+ rare  |

## Movement Quality Metrics

| Metric                  | Average Range | Good Range |
| ----------------------- | ------------- | ---------- |
| Knee Lateral Travel     | <40           | <20        |
| Knee Travel Angle       | <8            | 0-2        |
| Hip Vertical Travel     | <40           | <15        |
| Hip Horizontal Travel   | <40           | <10        |
| Ankle Swivel            | <10           | \~5        |
| Shoulder Lateral Travel | <40           | \~20       |

## Position Metrics

| Metric         | Range (Road) |
| -------------- | ------------ |
| Knee over foot | 0 to -40     |
| Sitting angle  | 72 to 76     |

> **Note:** Sitting angle is measured with reference to the bottom bracket, which is established during bike measurement. If you haven't yet taken bike measurements, sitting angle will not be shown.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.velogicfit.com/section-02-using-velogic-studio/road-metrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
