> 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/es/guide/devices-and-settings/device-specific-controls/other/tracks-upload.md).

# Carga de recorridos

Cargue archivos de recorrido grabado y del registrador de datos desde un dispositivo GPS en Navixy con el bloque de carga de Tracks. Una carga única, no una configuración guardada.

Importa archivos de ruta grabada o de registrador de datos exportados desde un dispositivo. Esto es útil cuando un dispositivo registró datos fuera de línea, sin cobertura, y usted desea ese historial en la plataforma.

## Configuración

* **Adjuntar archivo**: seleccione el archivo de ruta grabada para cargar. Los formatos comunes son CSV, TXT, Excel y OCT.

## Disponibilidad

Aparece en modelos de dispositivos que generan archivos de registrador de datos o de ruta cargables.

## Limitaciones

* Esta es una carga única de archivo, no una configuración guardada. No hay nada que guardar en el dispositivo.

## Ver también

* [Datos brutos](/docs/user/es/guide/devices-and-settings/object-management/raw-data.md): exporte la telemetría bruta del dispositivo desde la plataforma 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/es/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.