> For the complete documentation index, see [llms.txt](https://docs.lumidb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumidb.com/explore-and-analyze/merging-cropping-and-filtering-datasets.md).

# Merging, cropping, and filtering datasets

This guide explains how LumiDB merges datasets and their tiles, how to clip a region for analysis, and how to filter points by classification or elevation before you export or stream the data.

### Merging

Point cloud datasets often consist of multiple tiles. Traditionally, you have to merge these tiles manually in separate software. In LumiDB, dataset and tile boundaries are abstracted, so you see them as a unified dataset directly in the browser.

Merging happens automatically. All datasets that are visible in the project are combined for visualization, including their internal tiles. To leave a dataset out, hide it in the **Layers** panel.

### Clipping

1. Navigate to the area of interest on the map.
2. Click **Clip** in the toolbar.
3. Click the map to place the corners of a polygon. Double-click to place the last corner and finish the polygon.
4. Drag the corners to adjust the polygon. The area of the clip appears on the map.

LumiDB adds the clip to the **Layers** panel as a new layer, and the **Clip** panel opens on the right.

<figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2Fd3In9lbCiVbM10YMthHt%2F01-clip-selected.jpg?alt=media" alt="A clip on the map with the Clip panel open on the right"><figcaption><p>A selected clip and the Clip panel</p></figcaption></figure>

### Remove a clip

1. Click the clip on the map or in the **Layers** panel to open the **Clip** panel.
2. Click the **...** button at the top of the panel, then click **Clear**.

### Filtering

1. Click **Filters** in the toolbar. The point colors update to show classification.
2. Use **Elevation** to show only points between a minimum and maximum height.
3. Use **Classification** to hide or show classes. For example, clear **9: Water** or **1: Unassigned** to hide those points.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FVPavWJHWJkDRsLMVrctk%2F02-filters-panel.png?alt=media" alt="The Filters panel with the elevation range and the classification list" width="340"><figcaption><p>The Filters panel</p></figcaption></figure></div>

### Export to file

Once you've finished clipping and filtering, use the **Export** section of the **Clip** panel:

* **LAZ**, **E57** and **glTF** export the clipped data in that format.
* **Original files** downloads the original tile files separately.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FLcO5HgIA6LAVfQzxYKgH%2F03-export-formats.png?alt=media" alt="The Export section of the Clip panel with the LAZ, E57 and glTF buttons highlighted" width="340"><figcaption><p>Export formats</p></figcaption></figure></div>

LAZ, E57 and glTF open the same dialog:

1. Click **LAZ**, **E57** or **glTF**.
2. In **Export projection**, check the coordinate system for the exported points. The field starts with a suggestion. To use another one, enter an EPSG code or search by name. LumiDB reprojects the points on the fly, and the dataset itself doesn't change.
3. Check the **Estimated size**.
4. Click **Export**.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2Fd8coqutJtmTARsu0cV2F%2F03b-export-dialog.png?alt=media" alt="The Export LAZ dialog with the export projection and the estimated size" width="400"><figcaption><p>The export dialog</p></figcaption></figure></div>

{% hint style="info" %}
An export can be at most 10 GB, or 4 GB for glTF. When LumiDB estimates that a clip is over the limit, the button is grayed out. Point at it to see the limit. Draw a smaller area, or use **Original files**.
{% endhint %}

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FBTda2TAa4fIdj8OrAu2Q%2F04-export-large-clip.png?alt=media" alt="The Export section for a large clip, with E57 and glTF grayed out" width="340"><figcaption><p>E57 and glTF are grayed out for a large clip</p></figcaption></figure></div>

You can also stream a clip into other software with the **Stream** buttons (**ArcGIS**, **3D Tiles** and **QGIS**), or share it with colleagues. See Cesium 3D Tileset export and Sharing projects and inviting collaborators.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lumidb.com/explore-and-analyze/merging-cropping-and-filtering-datasets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
