> 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/qna/using-navixy/raw-data/including-parameters-in-raw-data-export.md).

# Including parameters in raw data export

Select any integrated parameters for your GPS tracker model when exporting raw data; the export supports up to 1,000 parameter columns

## Question

What parameters can be included in raw data export?

## Answer

When exporting raw data, you can select any parameters available for a specific GPS tracker model.

Here are the key selection features:

* **All integrated parameters** for each device model are available.
* You can **filter parameters** by name.
* You can **select up to 1,000 parameters** per export.
* If a parameter supports **multiple indices** (for example, AVL IOs), the system will ask you to specify which indices to include.
* Each selected parameter **adds a separate column** to the CSV file.

## Links

* [Raw data export](/docs/expert-center/faq-and-troubleshooting/access-iot-data/save-iot-data-to-csv-file.md)


---

# 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/qna/using-navixy/raw-data/including-parameters-in-raw-data-export.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.