> 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/browsing-datasets.md).

# Browsing datasets

This article explains how to browse the datasets in a project.

### Open a project

Datasets live in projects. On the **Projects** page, click a project to open it. To see every dataset in your organization instead, open **Project data** in the sidebar. It lists the datasets grouped by project, with their size and import date. Use the search box to find a dataset by name, or switch to the map view with the buttons at the top right.

### Open the Layers panel

The **Layers** panel on the left lists everything in the project. Datasets show a color dot, which is the color LumiDB uses for them on the map. Groups expand to show the datasets inside them.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FmNzt7p2ST6RiNmNiPcMU%2F01-layers-panel.png?alt=media" alt="The Layers panel listing files, point cloud datasets, raster datasets and groups" width="336"><figcaption><p>The Layers panel</p></figcaption></figure></div>

### Show, hide and lock layers

Hover over a layer to show two buttons. **Hide** hides the layer from the map and shows it again. **Lock** locks the layer.

### View dataset details

Click a dataset to open its details panel on the right and outline its area on the map.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FNRN353LVQzBSPUiKKay7%2F02-layer-details.png?alt=media" alt="The details panel of a point cloud dataset" width="340"><figcaption><p>Dataset details</p></figcaption></figure></div>

The panel shows:

* **Description**. A description that LumiDB writes for the dataset is labeled **AI generated**.
* **Custom fields**, such as attribution and capture date. Click **+** to add a field.
* **General** information: projection, number of points, density, spacing and area. A raster shows its dimensions, resolution, coverage, number of source files and size instead, and an **Opacity** slider.
* **More details**: open this section for more, such as the number of files, the height range and the mean number of returns.

The buttons at the top of the panel are:

* **Focus** centers the view on the dataset.
* **Share** copies a link, or gets a streaming link for ArcGIS, QGIS or other software. A point cloud has a **3D tileset link**, a **QGIS link** and an **ArcGIS I3S link**. A raster has an **XYZ tiles link**, a **WMTS link**, an **ArcGIS link** and a **Cloud-optimized GeoTIFF (COG) link**. See [Integrations](https://docs.lumidb.com/integrations.md).
* **Download** opens a list of the original files, with a download button for each.
* **Options** (**...**) has **Move dataset...**, **Re-process** and **Delete dataset**. **Re-process** imports the dataset again from its original files. See [Importing data](https://docs.lumidb.com/import-data/importing-data.md).

### Visualize datasets in 3D

Explore the data by zooming in on the map. As you zoom, LumiDB progressively streams higher-resolution data.

### Adjust the resolution level

Click **Display options** in the toolbar and set **Level of detail**.

### Search for a place

Click **Search** in the toolbar and type a place name to move the map there.


---

# 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/browsing-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.
