> 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/integrations/qgis.md).

# QGIS

Stream LumiDB point clouds and rasters into QGIS.

Use LumiDB data in QGIS. Point clouds stream as Entwine Point Tiles (EPT). Rasters stream as XYZ tiles, WMTS or a cloud-optimized GeoTIFF. You need an [API key](https://docs.lumidb.com/archive-management/api-keys.md) for all of them. The overview page, [Integrations](https://docs.lumidb.com/integrations.md), explains which link to use for which tool.

### Point clouds

Choose **QGIS link** in the **Share** menu. The link points to a point cloud in the Entwine Point Tile (EPT) format, which QGIS reads as a point cloud layer. Add the link as a point cloud data source over HTTP and sign in with an authentication configuration that sends your API key. The key goes in an `Authorization: apikey lumi_your_key_here` header, or in the password field of basic authentication. For a walkthrough, see the [LumiDB and QGIS article](https://blog.lumidb.com/lumidb-heart-qgis).

LumiDB sends the point cloud in pages as QGIS explores it, so large datasets, including very large ones, stream without waiting for the whole dataset to load. The point counts that QGIS shows for the layer are estimates.

### Rasters

#### XYZ tiles

In QGIS, open **Browser**, right-click **XYZ Tiles** and choose **New Connection…**. Paste the **XYZ tile URL**. Set **Authentication** to an HTTP header configuration with `Authorization: apikey lumi_your_key_here`.

#### WMTS

In QGIS, open **Browser**, right-click **WMS/WMTS** and choose **New Connection…**. Paste the **WMTS capabilities URL** and set the same authentication. LumiDB serves the tiles in the raster's own projection, and QGIS reprojects them if your project uses another.

#### Cloud-optimized GeoTIFF (COG)

Choose **Layer** → **Add Layer** → **Add Raster Layer…**, set **Source type** to **Protocol: HTTP(S), cloud, …** and paste the **COG download URL**. Leave authentication set to **No authentication**, because the link is already signed. The link expires after about an hour, so open the **Share** menu again to get a fresh one. Use a COG when you need the real values, for example for elevation data, instead of the 8-bit tiles of XYZ and WMTS.

### Troubleshooting

| Problem                                                       | What to try                                                                                                                                                                                                                                                                               |
| ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| QGIS says the key is wrong or asks for a login                | Check that your authentication configuration sends `Authorization: apikey lumi_your_key_here`, or uses the key as the password of basic authentication. Check that the key hasn't expired or been revoked on the [API keys](https://docs.lumidb.com/archive-management/api-keys.md) page. |
| The COG layer fails to load                                   | Leave authentication set to **No authentication**. The link is already signed, so an authentication configuration makes the request fail. If the link is older than an hour, open the **Share** menu again for a fresh one.                                                               |
| The raster looks different in QGIS than in LumiDB             | XYZ tiles and WMTS are 8-bit images. For the real values, for example elevation, use the COG link.                                                                                                                                                                                        |
| The point count in QGIS is different from the count in LumiDB | QGIS shows an estimate. LumiDB sends the point cloud in pages, so the layer doesn't count every point up front. The dataset details in LumiDB show the exact number of points.                                                                                                            |
| The data appears in the wrong place                           | Check the projection of the dataset. See [Coordinate systems and projections](https://docs.lumidb.com/import-data/coordinate-systems-and-projections.md).                                                                                                                                 |

If you are still stuck, write to <help@lumidb.com>.


---

# 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/integrations/qgis.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.
