> 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/deploying-3d-paws.md).

# Deploying 3D-PAWS

Guidance for selecting a site, installing and verifying the station, aligning wind measurements, and documenting the deployment.

### Overview

Deploying a 3D-PAWS station involves more than physically installing the equipment. Proper site selection, instrument placement, system verification, and documentation are essential for producing reliable and representative observations.

Use the pages in this section to move through the deployment process from site selection through final documentation.

***

#### Deployment Workflow

**1. Site Selection**

Choose a location that provides representative environmental conditions, appropriate instrument exposure, adequate solar access and communications, and safe access for installation and maintenance.

→ [**Site Selection**](/deploying-3d-paws/site-selection.md)

**2. Field Installation**

Install and secure the pre-assembled station, instruments, power system, and supporting equipment.

Use the **3D-PAWS Installation Checklist** during deployment to guide installation and final field checks.

→ [**Field Installation and Deployment**](/deploying-3d-paws/field-installation-and-deployment.md)

→ [**3D-PAWS Installation Checklist**](https://docs.google.com/document/d/1--PBiW-t_eiH6AI-fDY2usEfYwW2dc-Q79F7PT1GA9w/view?tab=t.0#heading=h.aowdo0rqk9y6)

**3. Wind Vane Alignment**

Align the wind vane to **true north** so that wind direction measurements are referenced correctly.

→ [**Wind Vane Alignment**](/deploying-3d-paws/wind-vane-alignment.md)

**4. System Verification**

Before leaving the site, verify that the station is powered, sensors are operating, communications are functioning, and observations are reaching the expected data service.

System verification is included as part of the **Field Installation and Deployment** procedure and Installation Checklist.

→ [**Field Installation and Deployment**](/deploying-3d-paws/field-installation-and-deployment.md)

**5. Station Metadata**

Record the station location, configuration, instrument heights, site conditions, photographs, and known siting limitations using the 3D-PAWS metadata documentation.

→ [**Station Metadata**](/deploying-3d-paws/station-metadata.md)

→ [**3D-PAWS Metadata Form**](https://docs.google.com/document/d/1q_UKSZHwp8ADDljWSyT0m7x3b6vQNsZgFbbu2g5cdOE/view?tab=t.0#heading=h.ju4qxs8rykjh)

***

#### Observing Practices and Standards

For deployment and instrument siting, refer to [**Volume I – Measurement of Meteorological Variables**](https://library.wmo.int/records/item/68695-guide-to-instruments-and-methods-of-observation?offset=3) of WMO-No. 8, particularly the guidance for the environmental variable being measured.

{% hint style="info" %}
3D-PAWS do not always follow the standard instrument heights or configurations described in WMO guidance. For example, wind sensors in a typical 3D-PAWS configuration are installed at approximately **2 m above ground level**, rather than the 10 m height commonly used for standard surface wind observations.

Document these installation characteristics in the station metadata so observations can be interpreted appropriately.
{% 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 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/deploying-3d-paws.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.