MapTiler Server user interface
This article describes the user interface of the MapTiler Server. After you successfully install
MapTiler Server on Linux, Windows, or Mac, your server should (by default) be available on the address http://localhost:3650. If you open it in a browser, you will see a blank screen with a MapTiler Server logo.
Signing in to the administration
The administration is available on http://localhost:3650/admin. Fill in the password you set during the installation, or which was generated automatically (and which is visible in the terminal window).
Maps
After you sign in, you will see the landing page with your maps. It is going to be probably blank at first.
Tiles
The second area is called Tiles. Paste your geodata (in MBTiles or tiled GeoPackage format) into a predefined folder, click on the Re-Scan button and all datasets will be visible in the administration.
Click on the Publish button for each dataset you want to be published.
Click on the Details button if you want to take a closer look at an individual data set.
On the new page, you can manipulate the dataset, see details, and get links for map services.
You can open an Embeddable viewer in the new window and browse your dataset.
Web map service (WMTS) GetCapabilities doc. is available on the page with the dataset and URL /WMTS.
Settings
The whole setting section is divided into five parts:
Server
In the Server section, you can set up the behavior of the MapTiler Server.
Security
On the Security page, you can change your password.
The hash of your password is stored in the config.json file: if you delete it, a new password will be automatically generated for you.
Another option to change your password is to run it from a command line by appending the --adminPassword suffix.
Rasterization
Rasterization is fully supported on Windows and Linux. Mac users requiring rasterization can use Docker image.
License
Unlock the full potential of your MapTiler Server with a valid License Key.
About
This section shows information about the software you are running (version, build date, …). This is very important when you are submitting a bug report.
