> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/id/guide/devices-and-settings/device-specific-controls/other/tracks-upload.md).

# Pengunggahan lintasan

Unggah berkas trek dan datalogger yang terekam dari perangkat GPS ke Navixy dengan blok unggah trek. Ini unggahan satu kali, bukan pengaturan yang disimpan.

Mengimpor berkas track atau datalogger yang direkam dan diekspor dari perangkat. Ini berguna ketika perangkat mencatat data secara offline, di luar jangkauan, dan Anda ingin riwayat tersebut ada di platform.

## Pengaturan

* **Lampirkan berkas**: pilih berkas track yang direkam untuk diunggah. Format yang umum adalah CSV, TXT, Excel, dan OCT.

## Ketersediaan

Muncul pada model perangkat yang menghasilkan berkas datalogger atau track yang dapat diunggah.

## Keterbatasan

* Ini adalah unggahan berkas satu kali, bukan pengaturan yang disimpan. Tidak ada yang perlu disimpan di perangkat.

## Lihat juga

* [Data mentah](/docs/user/id/guide/devices-and-settings/object-management/raw-data.md): ekspor telemetri mentah perangkat dari platform Navixy.


---

# 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://navixy.com/docs/user/id/guide/devices-and-settings/device-specific-controls/other/tracks-upload.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.