> 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/supported-formats-and-file-requirements.md).

# Supported formats and file requirements

Which file formats LumiDB imports, which attributes it keeps and what your files need to contain.

This page lists what you can import into LumiDB and what your files need to contain. For the import steps, see [Importing data](https://docs.lumidb.com/import-data/importing-data.md).

### Point clouds

| Format      | File types                     | Notes                                                                    |
| ----------- | ------------------------------ | ------------------------------------------------------------------------ |
| LAS and LAZ | `.las`, `.laz`                 | The best choice. LumiDB keeps most attributes.                           |
| E57         | `.e57`                         | LumiDB keeps position, intensity and color.                              |
| ASCII       | `.xyz`, `.asc`, `.pts`, `.txt` | Plain text with one point on each line. See [ASCII files](#ascii-files). |

LumiDB recognizes the format from the content of a file, not from its extension. A file that isn't a point cloud fails with **Unsupported file type detected**.

#### Attributes LumiDB keeps from LAS and LAZ

* Intensity, classification, return number and number of returns
* RGB color and near infrared
* GPS time and point source ID
* Scan angle, scan direction, edge of flight line and scanner channel
* User data, and the synthetic, key point, withheld and overlap flags

#### Object ID and height above ground

LumiDB can color and filter points by **Object ID** and **Height Above Ground**. It reads them from named extra bytes in the LAS or LAZ file. The names are case-insensitive.

| In LumiDB               | Name of the extra bytes field                                  |
| ----------------------- | -------------------------------------------------------------- |
| **Object ID**           | `TreeID`, or `ClusterID`. If both exist, LumiDB uses `TreeID`. |
| **Height Above Ground** | `HeightAboveGround`                                            |
| **Extra Data**          | `Change`                                                       |

LumiDB ignores other extra bytes fields. The fields must be declared in the file's extra bytes record, and they can be integers or floating-point numbers.

#### ASCII files

ASCII files have no header, and LumiDB doesn't ask which column is which. It decides from the number of columns on each line. Separate the values with commas or spaces.

| Columns   | Meaning                              |
| --------- | ------------------------------------ |
| 3         | X, Y, Z                              |
| 4         | X, Y, Z, intensity                   |
| 6         | X, Y, Z, red, green, blue            |
| 7 or more | X, Y, Z, intensity, red, green, blue |

LumiDB skips lines it can't read and the single count line at the start of a `.pts` file. An ASCII file doesn't declare a projection, so you always have to set it. See [Coordinate systems and projections](https://docs.lumidb.com/import-data/coordinate-systems-and-projections.md).

#### E57 files

LumiDB converts scans stored in spherical coordinates to XYZ and applies the position of each scan. It keeps a point source ID only when the file holds more than one scan, and it drops repeated identical points.

### Rasters

| File            | Purpose                                                   |
| --------------- | --------------------------------------------------------- |
| `.tif`, `.tiff` | GeoTIFF image or elevation model                          |
| `.asc`          | ASCII grid                                                |
| `.prj`          | Projection of the raster, if the file doesn't contain one |
| `.tfw`, `.wld`  | World file that places a TIFF                             |

Put a raster and its sidecar files in the same import. LumiDB pairs them by file name.

* **Color rasters:** with three bands, LumiDB shows them as RGB color. An alpha band becomes transparency, and other extra bands are ignored.
* **Single-band rasters:** 8-bit rasters appear in gray. Other rasters are treated as elevation, and you can show them with **Hillshade** or **Contours**.
* **Data types:** 8-bit, 16-bit and 32-bit floating point work well. 32-bit integer rasters import, but they can't be shown yet. Convert them to 32-bit floating point first.
* **NoData:** LumiDB treats a pixel as empty when all its color bands equal the NoData value. Use a NoData value that fits the data type. For example, a value of 256 on an 8-bit band can make the whole raster appear white.
* **Compression:** GeoTIFFs that use ZSTD compression import, as well as other common compression types.
* **Not available for rasters yet:** clipping and filtering.

### Images

| File                   | Notes                                       |
| ---------------------- | ------------------------------------------- |
| JPEG (`.jpg`, `.jpeg`) | Geotagged photos, for example from a drone. |
| TIFF (`.tif`, `.tiff`) | Geotagged photos.                           |

LumiDB imports the photos of a flight as one imageset and skips other file types in the same import. See [Import photos as imagesets](https://docs.lumidb.com/import-data/import-photos-as-imagesets.md). It reads this metadata from each photo:

* **Position:** the longitude, latitude and height from the EXIF metadata. LumiDB reads heights as meters above sea level unless the file declares another height reference.
* **Camera direction:** yaw, pitch and roll from the XMP metadata that drones such as DJI write.
* **Capture time**, and the camera make and model.
* **Preview:** the preview image that the camera embeds in the photo file. Photos without one have no preview.

A photo without a position imports, but LumiDB can't place it in the 3D view.

### Vectors

| File                 | Notes                                                                         |
| -------------------- | ----------------------------------------------------------------------------- |
| GeoJSON (`.geojson`) | Must be a `FeatureCollection`.                                                |
| Shapefile (`.shp`)   | Add the `.shx`, `.dbf` and `.prj` files, and the `.cpg` file if you have one. |

Each file, or each set of Shapefile parts, becomes one locked group in the **Layers** panel. LumiDB doesn't keep holes in polygons. Your browser reads vector files before it uploads them, so very large files can take a while.

### Files

You can attach any file type to a project, for example a CAD drawing, a report or a model. Other file types, such as DGN and DXF, are stored and can be downloaded, but they aren't shown on the map.

### Size

Very large single files can fail to import. If that happens, write to <help@lumidb.com> and include the file size and the format.

### Convert a file first

If your data is in another format, such as PLY, PCD or DWG, convert it to LAZ or GeoTIFF before you import it. Tools such as PDAL, GDAL and QGIS can do this.


---

# 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/supported-formats-and-file-requirements.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.
