> For the complete documentation index, see [llms.txt](https://docs.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phoenixlidar.com/3rd-party-software-documentation/bathymetric-lidar-processing-in-riprocess/creating-a-project-in-riprocess/processing-parameters/exponential-decomposition.md).

# Exponential Decomposition

**Exponential Decomposition (XDC)** is typically able to extract bathymetric points further underwater than **Online Waveform Processing (OWP)**. XDC accomplishes this by averaging several waveforms to increase the signal-to-noise ratio in regards to bathymetric returns.&#x20;

XDC processing is more intensive and requires processing to be restricted to only areas with water coverage. This is done using a GEOJSON format polygon definition file. See the following Riegl documentation regarding creating a GEOJSON polygon in QGIS and ArcGIS:

{% file src="/files/clTRRMQTLi3piqhuvTn6" %}

Once the polygon is created, you should enable XDC and waveform averaging:

<figure><img src="/files/f7Llo9D3w2lcbvKP5BDw" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Waveform averaging using 15 waveforms (as shown above) records bathymetric lidar returns deeper underwater than OWP processing. The benefit of averaging more waveforms (31, 63) is not quite as significant, so it is generally recommended to use 15.&#x20;
{% endhint %}

Ensure that your **Water Surface Selector** is also set to use the same GEOJSON polygon:

<figure><img src="/files/LueqfMxZYbnEW273Aufg" alt=""><figcaption></figcaption></figure>


---

# 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://docs.phoenixlidar.com/3rd-party-software-documentation/bathymetric-lidar-processing-in-riprocess/creating-a-project-in-riprocess/processing-parameters/exponential-decomposition.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.
