> For the complete documentation index, see [llms.txt](https://skaha-labs.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://skaha-labs.gitbook.io/documentation/online-processing/conversion-to-volumetric-water-content.md).

# Conversion to Volumetric Water Content

Next is the conversion of microwave brightness temperature into volumetric water content.

Skaha's land-surface model (LSM) is used to calculate the average field moisture level. Details about the process can be found in the LSM documentation. 

If the dataset is for a new field, calculating the average soil moisture can take several hours. The calculation takes only a few seconds if the meteorological, satellite, and soil data have already been obtained. 

Below is an example of a field calibrated in brightness temperature $$T\_B$$ (left) and volumetric water content (right). Since we assume a linear relation between the two, the only change between the two is in the units. 

![](/files/qjdAJLesiz34aqj0li0K)![](/files/Q4Gud7MZbRAmGbQZvzxW)


---

# 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://skaha-labs.gitbook.io/documentation/online-processing/conversion-to-volumetric-water-content.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.