> 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/station-metadata.md). # Station Metadata The [**3D-PAWS Metadata Form**](https://docs.google.com/document/d/1q_UKSZHwp8ADDljWSyT0m7x3b6vQNsZgFbbu2g5cdOE/edit?tab=t.0) is used to record essential information about each station following installation. It captures key details such as station identity, geographic coordinates, power configuration, communications setup, and sensor placement. This metadata ensures that all 3D-PAWS stations are documented consistently, allowing for reliable data interpretation, troubleshooting, and long-term network management. Technicians should complete the form immediately after installation, including photographs, alignment notes, and power or communications verification. Accurate metadata supports future maintenance, calibration, and data validation by linking environmental observations to precise site conditions and installation parameters. #### **Why It Matters** Post-installation metadata is as important as the sensor data itself. Site conditions, instrument heights, alignment, and power/communications details directly affect how observations should be interpreted, compared, and quality-controlled across the network. Without this context, it becomes difficult to distinguish real environmental signals from installation-related biases or later site changes. This form also supports **station traceability and interoperability**, including reporting to frameworks like **WIS 2.0** through a WMO identifier. Consistent metadata makes each 3D-PAWS station reproducible, easier to maintain over time, and more valuable for shared research and operational datasets. --- # 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/station-metadata.md?ask=&goal= ``` `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.