> 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/import-data/importing-data.md).

# Importing data

You can import point clouds, rasters, photos, files and vector data into a project. To import, you need **Full access** to the project, or you must be an organization admin.

### If you can't import

If you only have **Can view** or **Can download** access to a project, you can't import data. To make new data available:

1. Ask someone with **Full access** to the project, or an organization admin, to import the data.
2. Give them the data and relevant details, such as the coordinate system and what it's for.
3. Once it's imported, the dataset appears in the **Layers** panel.

To learn how access works, see [Sharing projects and inviting collaborators](https://docs.lumidb.com/sharing-and-access/sharing-projects-and-inviting-collaborators.md).

### Import data

1. Open the project and click **Import** at the bottom of the **Layers** panel.
2. Choose the type of data: **Point cloud**, **Raster**, **Images**, **Files** or **Vectors**.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2F3lVeX2x3MUKf8i2NXFph%2F01-import-menu.png?alt=media" alt="The Import menu with Point cloud, Raster, Images, Files and Vectors" width="440"><figcaption><p>Choose what you want to import</p></figcaption></figure></div>

3. Drag and drop your files into the dialog, or click **Browse files**. LumiDB starts uploading each file straight away. A green check next to a file means it has uploaded, and the map preview shows where the files are. Keep the page open until every file has uploaded.
4. Fill in the fields on the right. The fields marked with an asterisk are required. **Import** stays disabled until you've filled them in and every file has uploaded.
5. Click **Import**.

The import runs in the background. Click **Tasks** in the top bar to follow its progress. The list shows the imports of the project you have open. When an import finishes, the data appears in the **Layers** panel, and in an empty project the view moves to the new data.

<div align="left"><figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2Fbwp2sCeL7vWYCTGFm7Aq%2F03-imports-list.png?alt=media" alt="The Imports list showing finished imports" width="460"><figcaption><p>Follow imports in Tasks</p></figcaption></figure></div>

### Point clouds

<figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FqqDc3ezOlKWObtUSKwCj%2F02-import-dialog.png?alt=media" alt="The Import dataset dialog" width="720"><figcaption><p>The Import dataset dialog</p></figcaption></figure>

LumiDB accepts **.laz**, **.las**, **.e57** and ASCII point clouds (**.xyz**, **.asc**, **.pts**, **.txt**). If you add several files, LumiDB merges them into one dataset.

| Field                                                   | What to enter                                                                                                                                                                                                                                                    |
| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dataset name**                                        | A name for the dataset. Required.                                                                                                                                                                                                                                |
| **Input projection**                                    | The coordinate system of the files. Required. LumiDB fills it in when the files declare it. Otherwise enter an EPSG code, search by name, or enter a proj4 string. To include a vertical datum, use an EPSG code with a vertical part, such as `EPSG:3067+3900`. |
| **Advanced options** → **File heights are ellipsoidal** | Select this if the heights in your files are ellipsoidal.                                                                                                                                                                                                        |

#### Coordinate system detection

When you add files, LumiDB reads the coordinate system from each file that declares one. This works for LAS, LAZ, E57 and GeoTIFF files. If every file has the same coordinate system, LumiDB fills in **Input projection** and marks it **Auto-detected**. You can replace it with another projection.

<figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FHjWbJkbJ6HRR7sTYgp8K%2F02b-crs-auto-detected.png?alt=media" alt="The Import dataset dialog with two files and the Input projection filled in and marked Auto-detected" width="720"><figcaption><p>LumiDB detects the projection when all files agree.</p></figcaption></figure>

If the files have different coordinate systems, the dialog shows each file's own coordinate system and a warning that no single CRS was detected. **Input projection** stays empty, and LumiDB applies the projection you choose to all the files. Import files with different coordinate systems as separate datasets.

<figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2Fd1aSgGQMlJrAogn3LPLx%2F02c-crs-mismatch.png?alt=media" alt="The Import dataset dialog with two files that have different coordinate systems and a warning" width="720"><figcaption><p>A warning appears when the files have different coordinate systems.</p></figcaption></figure>

If a file doesn't declare a coordinate system, **Input projection** stays empty. Enter it yourself. See [Coordinate systems and projections](https://docs.lumidb.com/import-data/coordinate-systems-and-projections.md).

### Rasters

Add **.tif**, **.tiff** or **.asc** files, with optional **.prj** and **.tfw** or **.wld** sidecar files. Enter a **Raster name**. **Input projection** works as it does for point clouds: LumiDB fills it in when the file declares a coordinate system, and otherwise you enter an EPSG code or proj4 string.

### Images

Add geotagged JPEG or TIFF photos, for example from a drone flight. Enter a **Name**. LumiDB imports the photos as an imageset and shows where each photo was taken. See [Import photos as imagesets](https://docs.lumidb.com/import-data/import-photos-as-imagesets.md).

### Files

Add files of any type. LumiDB stores each file as its own layer. To keep the files together, enter a **Group name**. Leave it empty to import them without a group. Use **Description** to describe the files. LumiDB applies it to every file in the import.

### Vectors

Add GeoJSON files, or Shapefile components (**.shp**, **.shx**, **.dbf**, **.prj** and **.cpg**). LumiDB pairs Shapefile components by file name. The dialog has no fields to fill in: a map preview shows where the data is.

LumiDB reprojects Shapefile data to WGS 84 using the coordinate system in the **.prj** file. If a Shapefile has no **.prj** file, the dialog marks it **PRJ missing** and asks for a **Source projection fallback**. Enter an EPSG code or search by name. LumiDB doesn't keep holes in polygons.

### Import a name that already exists

If you import a point cloud or raster with a name that is already in use, LumiDB doesn't overwrite the existing dataset. It adds a new dataset that shows the name you typed, and the old one stays as it is. Delete the old dataset if you don't need it.

### Re-process a dataset

To import a point cloud or raster again from its original files, open the dataset, click **Options** (**...**) at the top of the details panel and choose **Re-process**. LumiDB runs the import again with the current import pipeline. The existing version stays available until the new one is ready.

{% hint style="info" %}
Need to import a format that isn't listed here? Contact <help@lumidb.com>.
{% endhint %}


---

# 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/import-data/importing-data.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.
