> 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/coordinate-systems-and-projections.md).

# Coordinate systems and projections

How LumiDB reads coordinate systems, how to choose the right input projection and how to fix data that lands in the wrong place.

LumiDB needs to know the coordinate reference system (CRS) of every dataset to put it in the right place on the map. LumiDB reads it from your files when they declare one, and you confirm or enter it in the **Input projection** field when you import data. If the projection is wrong, the data ends up in the wrong place, at the wrong height or at the wrong scale.

### Enter the input projection

The point cloud and raster import dialogs both have a required **Input projection** field. You can enter:

* an EPSG code, for example `EPSG:3067`, or just `3067`
* an EPSG code with a vertical datum, for example `EPSG:3067+3900` for ETRS-TM35FIN with N2000 heights
* a proj4 string, for example `+proj=utm +zone=35 +ellps=GRS80 +units=m +no_defs`

You can also search by the name or code of a projection while you type. The dialog remembers the last five projections you used.

{% hint style="info" %}
The field doesn't accept WKT. If your CRS has no EPSG code, convert it to a proj4 string, or contact <help@lumidb.com>.
{% endhint %}

A small map in the dialog shows where the data will land with the projection you entered. Check that it is in the right place before you start the import.

### Detected projections

LAS, LAZ, E57 and GeoTIFF files can declare their own projection. When you add files, LumiDB reads it from each file. If every file declares the same one, LumiDB fills in **Input projection** and marks it **Auto-detected**. The value in the field is what LumiDB uses, so you can replace it. Do that if you know the file declares the wrong projection. You can read a header with a tool such as `lasinfo` or QGIS.

* **The files disagree:** each file shows its own projection and a warning appears. The field stays empty. Choose one projection, and LumiDB applies it to all the files. Import files with different projections separately.
* **A file declares none:** the field stays empty. Enter the projection yourself. ASCII point clouds never declare one.

For the steps, see [Importing data](https://docs.lumidb.com/import-data/importing-data.md).

### Heights and vertical datums

Point clouds have heights as well as positions, and heights are measured from different surfaces. Use the **File heights are ellipsoidal** checkbox together with the projection to tell LumiDB what yours are.

| Your file                                             | What to enter                                                                                        | What LumiDB does                                         |
| ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| Heights above a national datum, such as N2000         | The CRS with its vertical, for example `EPSG:3067+3900`                                              | Stores the heights in that datum.                        |
| Heights above the ellipsoid, such as GNSS heights     | The horizontal CRS, and select **File heights are ellipsoidal**                                      | Stores ellipsoidal heights.                              |
| Ellipsoidal heights that you want in a national datum | The CRS with its vertical, for example `EPSG:3067+3900`, and select **File heights are ellipsoidal** | Converts the heights to that datum with the geoid model. |
| Heights, and you enter no vertical datum              | A horizontal CRS only                                                                                | Changes units if needed, but never shifts the heights.   |

Write a combined CRS as `EPSG:3067+3900`. Don't add a vertical datum to a proj4 string with `+vunits`.

{% hint style="info" %}
The **File heights are ellipsoidal** checkbox is under **Advanced options** in the point cloud import dialog. It isn't in the raster dialog.
{% endhint %}

### Check where your data went

* The bottom left corner of the project view shows the coordinate system of the view, for example `EPSG:3067 (m)`.
* Click a dataset in the **Layers** panel. Its **Projection** row shows the CRS the dataset is stored in.
* If the data is hundreds of kilometers away from where it should be, the projection is probably wrong. Another common cause is that the file stores northing before easting, because some projections define their axes that way. LumiDB reads the first coordinate as easting. Contact <help@lumidb.com> if you think this is the cause.

### Rasters

For a GeoTIFF that declares a projection, LumiDB fills in **Input projection** for you. If your raster doesn't declare one, enter it in the dialog. If your raster comes with a `.prj` file, add it to the import. ASCII grids (`.asc`) have no projection of their own and need the `.prj` file or the field. A projection that only describes a local or engineering system counts as no projection.

### Vectors

* **GeoJSON:** LumiDB uses the `crs` of the file. Without one, it assumes WGS84 if the coordinates look like longitude and latitude. Otherwise the dialog shows a **Source projection fallback** field.
* **Shapefile:** LumiDB uses the `.prj` file. Without one, enter the projection in the fallback field.

Everything is converted to WGS84 in your browser during the import.

### Local and project coordinates

Data without a real-world CRS, such as a site grid, can't be placed on the map correctly. As a workaround, import it as Web Mercator (`EPSG:3857`). The data appears near the equator, far from where you surveyed, but its coordinates stay as they are in the file.

### Fix common errors

| Message or symptom                                                                        | What to do                                                                                                                                                                          |
| ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Source projection is not recognized**                                                   | Check the code or the proj4 string for typos. For an EPSG code, make sure it exists at [epsg.io](https://epsg.io/). If it still isn't accepted, paste its proj4 definition instead. |
| **Could not load EPSG:** followed by a number                                             | The code is unknown. Try the proj4 definition.                                                                                                                                      |
| **PRJ projection is not recognized. Remove the PRJ file to set the projection manually.** | Import the vectors without the `.prj` file and enter the projection yourself.                                                                                                       |
| A raster import fails with a projection error                                             | Enter the correct projection in the dialog, or add a `.prj` file next to the raster.                                                                                                |
| Few points or no points after the import                                                  | LumiDB skips points that lie outside the bounds written in the LAS header. If the header bounds are wrong, fix them with a tool such as `lasinfo` or PDAL and import again.         |
| Data is in the right place but at the wrong height                                        | Check the vertical datum and the **File heights are ellipsoidal** checkbox.                                                                                                         |

Still stuck? Write to <help@lumidb.com>. Include the projection you entered, the header of the file if you can, and a screenshot of the import dialog.


---

# 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/coordinate-systems-and-projections.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.
