> 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/get-started/quickstart-import-view-and-share.md).

# Quickstart: import, view and share

Import your first dataset, look at it in 3D and share it with someone, in about ten minutes.

This guide takes you from a file on your computer to a link you can send to a client. It takes about ten minutes, and most of that is waiting for the import.

You need a LumiDB account and a point cloud or raster file. A LAZ, LAS or GeoTIFF file works well. See [Supported formats and file requirements](https://docs.lumidb.com/import-data/supported-formats-and-file-requirements.md) if you are not sure about your file.

### 1. Create a project

A project holds your data and decides who can see it. Sign in at [app.lumidb.com](https://app.lumidb.com), open **Projects** and click **New project**. LumiDB creates a project named **Untitled project** and opens it. To rename it, use the **...** menu on the project card in **Projects**.

### 2. Import your data

1. In the **Layers** panel on the left, click **Import** and choose **Point cloud** or **Raster**. In an empty project you can also click one of the two buttons in the **Import data** prompt.

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

2. Drag your file into the dialog, or click **Browse files**. Wait until the file has uploaded.
3. Check the **Input projection**, the coordinate system of your file. LumiDB fills it in when the file declares it, and marks it **Auto-detected**. Otherwise enter it. See [Coordinate systems and projections](https://docs.lumidb.com/import-data/coordinate-systems-and-projections.md) if you aren't sure which to use.
4. Enter a name and click **Import**.

Large files take a while. Click **Tasks** in the top bar to follow the progress. When the import is ready, your data shows up in the **Layers** panel.

{% hint style="info" %}
You don't need an account to share a point cloud once: LumiDB has a public upload page at [app.lumidb.com/upload](https://app.lumidb.com/upload). It accepts **.laz**, **.las** and **.e57** files and emails you a link that works for 7 days.
{% endhint %}

{% hint style="info" %}
You need **Full access** to a project to import into it. If you created the project, you have it. See [Importing data](https://docs.lumidb.com/import-data/importing-data.md) for all the options.
{% endhint %}

### 3. Look at your data

Scroll to zoom, drag with the left button to move, and drag with the right button to rotate. Click **Focus datasets** in the bottom right corner to bring everything into view. See [Camera and navigation](https://docs.lumidb.com/get-started/camera-and-navigation.md).

<figure><img src="https://150512722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMI9s5xLuAdXOTKpfljc3%2Fuploads%2FkWu0vMtmrY6KAzGGTxTp%2F02-project-view.jpg?alt=media" alt="The project view with the Layers panel, the toolbar and the Share button highlighted"><figcaption><p>The project view</p></figcaption></figure>

Try the tools in the toolbar: **Measure**, **Cross section** and **Clip**. Open **Display options** to color the points, for example by elevation.

### 4. Share it

1. Click **Share** in the top right corner.
2. Enter your client's email address, choose **Full access**, **Can download**, or **Can view** and click **Invite**. Or turn on **Public** and click **Copy project link** to get a link anyone can open.
3. Send the link, and add the guide for your clients if they are new to LumiDB.

See [Sharing projects and inviting collaborators](https://docs.lumidb.com/sharing-and-access/sharing-projects-and-inviting-collaborators.md) for roles and permissions.

### Where to go next

| I want to                     | Read                                                                                                                                |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Cut out an area and export it | [Merging, cropping, and filtering datasets](https://docs.lumidb.com/explore-and-analyze/merging-cropping-and-filtering-datasets.md) |
| Use my data in ArcGIS or QGIS | [Integrations](https://docs.lumidb.com/integrations.md)                                                                             |
| Use the API                   | [API keys](https://docs.lumidb.com/archive-management/api-keys.md)                                                                  |
| Connect an AI assistant       | [Connecting AI assistants (MCP)](https://docs.lumidb.com/integrations/connecting-ai-assistants-mcp.md)                              |
| Fix a problem                 | [Troubleshooting](https://docs.lumidb.com/troubleshooting.md)                                                                       |


---

# 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/get-started/quickstart-import-view-and-share.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.
