> For the complete documentation index, see [llms.txt](https://docs.motus.org/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motus.org/en/stations/downloading-data.md).

# Downloading Data

## Before getting started

These instructions will help guide you through downloading detection data from a Motus receiver station. Included are details on the equipment you will need, the parts of the receiver, and step-by-step instructions on how to download the data.

Why are we downloading detection data? Motus receiver stations are only capable of automatically sending detection data to the centralized database when a cellular network or WiFi is available. In remote locations with no cellular reception or WiFi, detection data must be manually downloaded from the receiver itself. Once the files are downloaded, data can be emailed to Birds Canada for uploading to the Motus website.

## Instructions 

Methods for downloading data from a Motus receiver depends on the model of receiver being used. Select a model from the links below to view instructions:

* [SensorGnome](/en/stations/downloading-data/downloading-data-from-a-sensorgnome.md)
* [CTT SensorStation](/en/stations/downloading-data/downloading-data-from-a-sensorstation.md)
* [Lotek SRX](/en/stations/downloading-data/downloading-data-from-a-lotek-srx.md)

{% hint style="info" %}
**Automated data uploads**\
\
Both SensorGnomes and CTT SensorStations can be programmed to automatically upload data to Motus with an internet or cellular connection. Review their guides for more information.
{% endhint %}

## **Uploading data to Motus**

1. Prepare the data for uploading 
   1. Add all files for a receiver to a .zip or .7z archive
   2. Ensure that each archive contains data from *only one receiver*
   3. Do *not* change any of the detection data filenames. The name of the archive itself doesn't matter, but it's best to give it a description name for your own benefit
2. Log in to Motus.
3. Select your project from the dropdown menu. 
4. Select '[Upload Detection Files](https://motus.org/data/project/sgJobs)' from the management menu.
5. Follow the instructions on that page to upload these data.
6. After processing is complete (usually 1-6 hours, but sometimes longer) you'll receive a \
   "Processing complete"  email. Ensure that you review this email and the job log as it may contain important information about your upload.

{% hint style="info" %}
Don't worry if you accidentally upload data to the wrong project. This will not have any impact on the data, and all detections will be associated with the correct project and station on the back-end. However it will result in the job log being found in the wrong project, and there will be a statement in the "Processing complete" email that "there is no deployment found for this receiver". Otherwise, there is no impact.
{% endhint %}


---

# 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://docs.motus.org/en/stations/downloading-data.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.