# Data Recording and Management

## Recording Observations <a href="#recording-observations" id="recording-observations"></a>

One of RoboDot's main features is its capability to record GNSS observation data, which can serve as both a backup and a primary source for post-processing workflows. This is especially useful for ensuring data integrity and accuracy during field operations. The recording activity is confirmed via a green indicator light, and users can also verify the status through the Web UI or the touch screen display. This dual confirmation method enhances the reliability of data recording, making it an essential tool for GNSS data collection and management.

Filename format: dot###m#d#y#h#m#s#gpst (in GPS time indicating the start date of the record)

The observation file extension is .rub. It should be converted to RINEX using the RoboDot Utility Software or via Wingman Tools online portal.

### Setup

The RoboDot device offers flexible recording trigger options to accommodate various user needs. First, the **Auto**-start feature with "Record on Boot" enabled allows recording to commence automatically once a GNSS lock is acquired, ensuring seamless data capture without manual intervention. This is particularly advantageous in scenarios where immediate data recording is crucial.&#x20;

Alternatively, users can exercise **manual** control over the recording process through the Rec/Stop button available on the Status and Rover web pages, providing more granularity and control to the operator. These options make the device versatile and adaptable to different operational demands.

## Recording Shots <a href="#file-access" id="file-access"></a>

Rover Mode creates an additional .sht file which is a csv file with details on each point recorded. Learn more in the [Rover Mode](https://docs.robota.us/robodot-touch-3.1.16/robodot-touch-user-guide/operating-modes/rover-mode) section.

## File Access <a href="#file-access" id="file-access"></a>

<figure><img src="https://997082541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FME2NmecYqe2KQizbIXUx%2Fuploads%2FsVvMJJNDsmuE8IJYgGXj%2Ffiles.jpg?alt=media&#x26;token=7a959b08-7c54-4538-b974-4b5e22f9cbf1" alt="" width="291"><figcaption><p>Web UI Files Menu</p></figcaption></figure>

To download project files, access the Web UI and navigate to the Files page. There, you can download files such as .rub and .sht for further processing or analysis. These files can also be shared with Wingman to facilitate company-wide use, streamlining collaboration and ensuring all team members have access to the necessary data.

### Downloading

Location: Web UI, Files Page

File types:

* .rub: Raw observations
  * Convert to RINEX for post-processing with RoboDot Utility
  * Used in post processing workflows
* .sht: Position data (Rover mode)
  * Contains rover shots generated by "Mark Location"
  * Also created for base points
  * Comma separated text file.

{% hint style="info" %}
Connection services (BLE/TCP/NTRIP) are paused during file download.
{% endhint %}

### Sharing Files <a href="#sharing-files" id="sharing-files"></a>

In the Files Page, files can be uploaded to the Wingman portal by selecting the desired file and clicking "share files". Follow the instructions on the share page.

Wingman can email you a copy of the file and submit observation files to Opus.

See the hardware asset in the Wingman Dashboard at [www.robota.us](http://www.robota.us) to configure the desired behavior.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.robota.us/robodot-touch-3.1.16/robodot-touch-user-guide/data-recording-and-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.