> For the complete documentation index, see [llms.txt](https://strydtaiwan.gitbook.io/stryd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://strydtaiwan.gitbook.io/stryd/strydduo/how-to-use-stryd-footpath-with-stryd-duo.md).
# 如何使用 Stryd Footpath 與 Stryd Duo？
## 使用跑步後如何從 Stryd Duo 同步 Stryd Footpath 數據
1. 確保您的 Stryd Duo 就附近
2. 打開手機上的 Stryd App
3. 點擊 App 主頁上的「同步」按鈕
[](https://downloads.intercomcdn.com/i/o/875798615/eb22a2224129aaa9843e44ad/Pasted_Image_11_5_23__5_16%E2%80%AFPM.png)
4. 一旦您收到同步成功的通知，您將能夠在 Stryd PowerCenter 中看到 Stryd Footpath
5. 在網頁版瀏覽器中開啟[Stryd PowerCenter](https://www.stryd.com/powercenter/)
6. 您可以在「Footpath Visualization」的找到此數據（網頁版左邊分頁欄位，有跟上圖一樣的符號）
7. 點擊右邊 「Add Run」選擇你想看的數據日期（可以選擇的右上角會有小白點）
您將透過分析工具，視覺化兩隻腳和不同的數據。視覺數據包含：
1. 左腳（橘色線） Left footpath - Orange lines
2. 右腳 （藍線色）Right footpath - Blue lines
3. 側面視角 Side view footpath
4. 頭頂視角 Top view footpath
5. 背面視角 Back view footpath
6. 平衡數據 Balance data
7. 自訂指標 Custom Stryd metrics from the run
透過以上 Stryd Footpath （Stryd 動作軌跡），把整個跑步過程中的動作軌跡，以側面、背面與頭頂視角來呈現，讓跑者可以去比較及分析不同的訓練或比賽記錄，以下是您可以如何利用這些數據去提高跑步表現：
* 受傷：在恢復期當中觀察動作軌跡的細微變化，去追蹤復原的程度。
* 疲勞：可以觀察在跑步過程中疲勞在何時出現並產生了哪些變化，以便調整訓練去提高抗疲勞能力。
* 技術：量化並視覺化不同技術訓練對動作軌跡的影響，以確定它們是否提供了預期的好處。
* 跑鞋：觀察不同的鞋子對動作軌跡所造成的變化，找到最有幫助、最適合自己的那雙跑鞋。
* 表現：透過長期的視覺化動作軌跡記錄，可以觀察到在不同的跑步表現當中有哪些動作軌跡上的差異。
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://strydtaiwan.gitbook.io/stryd/strydduo/how-to-use-stryd-footpath-with-stryd-duo.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.