> 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/zh/di-02-jie-shi-yong-velogic-studio/road-metrics.md).

# 公路指标

Velogic Studio 中用于公路自行车拟合的关节角度、动作质量和姿势指标参考指南。

我们的系统提供了丰富的指标。要充分利用 3D 数据，需要在决策中结合多个因素。以下是关于“标准”姿势的一些指导。

## 关节角度指标

| 指标    | 范围                         |
| ----- | -------------------------- |
| 踝关节角度 | 平均 100-130，范围 < 30         |
| 膝关节角度 | 最大140-145，最小 >68           |
| 髋关节角度 | 最大 90-105，如果骑手有问题可达 120    |
| 肩部角度  | 平均75-100                   |
| 肘角    | 平均 155-170                 |
| 躯干角度  | 精英级 35-40，普通 40-50，50+ 较少见 |

## 动作质量指标

| 指标     | 平均范围 | 良好范围 |
| ------ | ---- | ---- |
| 膝盖横向移动 | <40  | <20  |
| 膝盖移动角度 | <8   | 0-2  |
| 髋部垂直移动 | <40  | <15  |
| 髋部水平移动 | <40  | <10  |
| 踝部摆动   | <10  | \~5  |
| 肩部横向移动 | <40  | \~20 |

## 姿势指标

| 指标     | 范围（公路）  |
| ------ | ------- |
| 膝盖在脚上方 | 0 到 -40 |
| 坐姿角    | 72 到 76 |

> **注意：** 坐姿角是以中轴为参考进行测量的，该中轴在自行车测量时确定。如果您尚未进行自行车测量，则不会显示坐姿角。


---

# 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/zh/di-02-jie-shi-yong-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.