> 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/guide/devices-and-settings/device-specific-controls/other/tracks-upload.md). # Tracks upload Upload recorded track and datalogger files from a GPS device into Navixy with the Tracks upload block. A one-off upload, not a stored setting. Imports recorded track or datalogger files exported from a device. This is useful when a device logged data offline, out of coverage, and you want that history on the platform. ## Settings * **Attach file**: select the recorded track file to upload. Common formats are CSV, TXT, Excel, and OCT. ## Availability Appears on device models that produce uploadable datalogger or track files. ## Limitations * This is a one-off file upload, not a stored setting. There is nothing to save on the device. ## See also * [Raw data](/docs/user/guide/devices-and-settings/object-management/raw-data.md): export the device's raw telemetry from the Navixy platform. --- # 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/guide/devices-and-settings/device-specific-controls/other/tracks-upload.md?ask=&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.