> For the complete documentation index, see [llms.txt](https://water-strategy.gitbook.io/waterstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://water-strategy.gitbook.io/waterstrategy/getting-started/uploading-external-data.md).
# Uploading External Data
In WaterStrategy, users have the flexibility to manage large and complex datasets more efficiently by loading data from external files as [**DataFrameParameter**](https://water-strategy.gitbook.io/waterstrategy/modeling-basics/parameters/dataframe-parameter) using the "url" keyword, rather than embedding all the data directly into the interface. The file formats include:
* CSV
* Excel
* HDF5
Note: Among the previous options, Excel files have the slowest performance while HDF5 files have the best performance and are preferred for large datasets.
To upload a file in WaterStrategy, navigate to your **project** and click on the Files tab. From there, click **Choose Files** and select the file you want to upload and click .
This will add the file to your project, making it available for use across all networks within the project.
Once the files have been uploaded, they will be displayed in the **Files** tab within your project. From there, you can easily view, manage, and share them across all networks in the project.
---
# 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://water-strategy.gitbook.io/waterstrategy/getting-started/uploading-external-data.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.
.
This will add the file to your project, making it available for use across all networks within the project.
