> For the complete documentation index, see [llms.txt](https://3dpaws.comet.ucar.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://3dpaws.comet.ucar.edu/accessing-the-data.md).

# Accessing the Data

Guidance for accessing and verifying 3D-PAWS observations through CHORDS and Grafana.

### Overview

3D-PAWS stations transmit environmental observations through connected data services for storage, visualization, analysis, and integration into observation systems.

***

#### Data Flow

**Sensors → Data Logger → Network → CHORDS → Grafana**

* **CHORDS** stores and provides access to station observations.
* **Grafana** provides dashboards for viewing current and historical observations.

{% hint style="info" %}
The exact data path depends on the data logger and communications configuration. For example, Particle-based stations transmit observations through the Particle Cloud before they reach CHORDS.
{% endhint %}

***

#### Viewing Data

| Platform    | Purpose                 | Key Features                                                 |
| ----------- | ----------------------- | ------------------------------------------------------------ |
| **CHORDS**  | Data storage and access | Time-series observations, API access, external integration   |
| **Grafana** | Data visualization      | Current conditions, historical data, customizable dashboards |

Use the pages in this section for detailed instructions on accessing and working with each platform.

→ [**CHORDS**](/accessing-the-data/chords.md)

→ [**Grafana**](/accessing-the-data/grafana.md)

***

#### Verify Station Data

After deployment or maintenance, confirm that observations are reaching the data service and updating as expected.

Check that:

* new observations are being received
* timestamps are correct
* observations are updating at the expected frequency
* all expected sensor variables are present
* measurement values are physically reasonable for current conditions

#### Basic Data Quality Checks

When reviewing station data, look for patterns that are consistent with how each measurement should behave.

| Measurement           | What to Look For                                                                                                                                                |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Temperature**       | A recognizable day/night cycle without abrupt, unexplained jumps                                                                                                |
| **Relative Humidity** | Changes that generally respond to temperature and changing moisture conditions; watch for values persistently near 0% or 100%                                   |
| **Pressure**          | Smooth changes over time; abrupt jumps or flat values may indicate a problem                                                                                    |
| **Rainfall**          | Zero during dry periods and discrete increases during precipitation events; accumulation should not increase because of irrigation or other non-weather sources |
| **Wind Speed**        | Natural variability over time; extended periods of exactly zero may indicate a broken anemometer                                                                |
| **Wind Direction**    | Direction should vary with changing winds; a fixed value for long periods may indicate a broken vane or connection issue if wind speeds are present.            |

***

#### If Data Is Missing or Incorrect

If observations are missing, incomplete, or unexpected, begin with the basic station checks:

1. Verify that the data logger is powered and operating.
2. Confirm network connectivity.
3. Check sensor and cable connections.
4. Verify the station configuration.
5. Confirm that observations are reaching the expected data service.

{% hint style="info" %}
For Particle-based stations, **INFO messages** provide a useful first check of data logger status, connected sensors, storage, communications, and other system conditions.
{% endhint %}

For detailed diagnostic procedures, see **Troubleshooting**.

***

#### Pages in This Section

* **CHORDS** – accessing stored station observations and data services
* **Grafana** – viewing station observations and dashboards
* **Particle / CHORDS Integrations** – configuring the data path between Particle Cloud and CHORDS


---

# 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 dynamically by asking a question.

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

```
GET https://3dpaws.comet.ucar.edu/accessing-the-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.