> For the complete documentation index, see [llms.txt](https://docs-jmapserver-lima.k2geospatial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-jmapserver-lima.k2geospatial.com/e/extensions/import/importation-procedure.md).

# Importation Procedure

The graphical interface of the Importation extension, which can be accessed by going to **Tools -> Import data** in the Pro application, guides the user through the steps of the importation process.

Importation involves three sequential steps:

1. Selecting the type of data,
2. Selecting the data sets to import and
3. Configuring the parameters associated with each type of data.

### Selecting the type of data

<figure><img src="/files/0NthNlSZJXnrWtXxW0a8" alt=""><figcaption></figcaption></figure>

Five types of data formats can be imported:&#x20;

* MIF files, usually produced by MapInfo applications;&#x20;
* SHP files, usually produced by ESRI applications;&#x20;
* CSV files, which are text files with separate values containing X and Y geographical coordinates;&#x20;
* GPS data structured according to the NMEA standard; and&#x20;
* Raster data from servers that are compliant with the WMS standard.

The subsequent steps vary according to the format type of the data to import.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-jmapserver-lima.k2geospatial.com/e/extensions/import/importation-procedure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.