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

# Troubleshooting

Fixes for the most common problems with imports, projects, clips, streaming and the map view.

Find your problem in the list below. If it isn't there, see [Contact support](#contact-support).

### I can't import data, or the Import button is disabled

You need **Full access** to the project, or you must be an organization admin. People with **Can view** or **Can download** access can't import. Ask someone with **Full access** to change your permission, or to import the data for you. If you have the right access, **Import** stays disabled until you've filled in the required fields and every file has finished uploading. See [Importing data](https://docs.lumidb.com/import-data/importing-data.md).

### An import failed or takes a long time

1. Click **Tasks** in the top bar. The button is disabled when there are no tasks.
2. Find your import under **Imports**. The row shows its progress, or the error message if it failed.
3. For a failed import, click **Retry** after you have fixed the cause. When an import is ready, click **Focus** to go to the data.

Common causes of failures are an unrecognized projection, a file in an unsupported format, wrong bounds in a LAS header, and points that lie very far apart, which usually means the projection is wrong. See [Coordinate systems and projections](https://docs.lumidb.com/import-data/coordinate-systems-and-projections.md) and [Supported formats and file requirements](https://docs.lumidb.com/import-data/supported-formats-and-file-requirements.md).

### My data is in the wrong place

Check the projection you entered during the import. Click the dataset in the **Layers** panel and look at its **Projection** row. See [Coordinate systems and projections](https://docs.lumidb.com/import-data/coordinate-systems-and-projections.md).

### My data floats above or below the basemap

Open **Display options** and move the **Terrain offset** slider. You can also turn the **3D terrain** option off, to show the basemap flat.

### My raster is white, black or missing

Check the NoData value, the number of bands and the data type of the file. See [Supported formats and file requirements](https://docs.lumidb.com/import-data/supported-formats-and-file-requirements.md). A raster imported without a projection can also appear in the wrong place.

### The dataset looks low-resolution or has large gaps

Check these causes in order:

1. A slow network connection can keep progressive streaming from updating the view quickly. Check the streaming indicator in the bottom right corner of the map to see if data is still loading.
2. The dataset may not have been uploaded or stored at full resolution. Ask your admin for higher-resolution data.
3. Active filters may be hiding parts of the dataset.

### An export button is grayed out

LumiDB grays out **LAZ**, **E57** or **glTF** in the **Clip** panel when the estimated export is over the limit: 10 GB, or 4 GB for glTF. Point at the button to see the limit. Draw a smaller area, or use **Original files**. See [Merging, cropping, and filtering datasets](https://docs.lumidb.com/explore-and-analyze/merging-cropping-and-filtering-datasets.md).

### I can't remove a clip, or I can't find it

Open the clip from the **Layers** panel, click **...** at the top of its panel and choose **Clear**. Very small clips are hard to select in the 3D view, so use the **Layers** panel instead. If the clip still stays after you reload the page, clear the cache of your browser or try another browser.

### Something looks stale, or a button doesn't respond

1. Reload the page.
2. Clear the cache of your browser, or open LumiDB in a private window.
3. Try another browser.

Describe the problem in an email to <help@lumidb.com> if none of these help. Mention which browser you use.

### I can't add a person to a project

Invite people from the **Share** panel of a project. See [Sharing projects and inviting collaborators](https://docs.lumidb.com/sharing-and-access/sharing-projects-and-inviting-collaborators.md). If the invitation doesn't work, try another browser.

### Streaming to ArcGIS or QGIS doesn't work

See the troubleshooting sections of ArcGIS and QGIS. Check that your API key is active.

### The ArcGIS Online Map Viewer doesn't accept my link

The Map Viewer is 2D and can't open the **ArcGIS I3S link**. To see a point cloud in ArcGIS Online, use the Scene Viewer. For a raster, copy the **WMTS link** from the **Share** menu and add it with **Add layer from URL** as type **WMTS (OGC)**. See [ArcGIS](https://docs.lumidb.com/integrations/arcgis.md).

### Things LumiDB can't do yet

* Use your own elevation model, for example a DTM GeoTIFF, as 3D terrain. The 3D terrain comes from a global model, and an elevation raster is shown as an image, as a hillshade or as contours.
* Clip or filter rasters.
* Stream rasters as WMS. Use WMTS or XYZ tiles.

### Contact support

Write to <help@lumidb.com> with questions, feedback or feature requests. The whole team reads it. To help us answer quickly, include:

* the name of the project and the dataset
* what you expected and what happened
* a screenshot, and the time when it happened
* the browser or the software you use


---

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