Layers

The Layers menu is used to configure all settings related to layers, how they are displayed and grouped.

_images/layers_1.png

The project’s layers are shown in the left-hand panel and can be re-ordered (and assigned/unassigned to groups) by drag-and-drop. The Search layer tool (top-left) can be useful for quickly locating layers.

The three buttons in the top-right allow you to:

  • ADD NEW LAYER - Adds a new layer to this project and opens its general layer settings.
  • ADD NEW GROUP - Adds a new layer group to this project and opens its group settings.
  • LOAD LAYERS - Opens a dialog for batch-publishing multiple layers available from Mappin’s WMS server (discussed below).

When a layer or group in the left-hand panel is selected, the following settings appear:

Load Layers dialog

The Load Layers dialog can be used to batch-publish multiple layers.

The tool sends a (GetCapabilities) request to Mappin’s WMS server for a full list of available layers. For each layer, it reports its Name, Alias and Group (if any). A special column (New) will feature a check if you do not already have a layer published in Mappin with the same Name. Entries without a check indicate layers you have already published in Mappin.

_images/load_layers_1.png

The New checkbox (top-right) filters the list to only show layers you have not already published through Mappin.

The IMPORT SELECTED button will create new layers in the current project for the selected layers using default settings, populating alias and group settings where possible. If you import a layer with the same Name as a layer you have already published, that published layer’s settings will be overwritten with default layer settings.

For Mappin to automatically populate a layer’s Name (PostGIS) and Data CRS fields, you’ll need to have the table’s schema listed in the list of schemata searched for Mappin layers for this project (in Global Configuration).

Warning

on-premises customers will also need to ensure that the PostgreSQL database user which Mappin uses to read data from the PostGIS database (usually mappin) has SELECT rights on the table and USAGE rights on the containing schema.

Layer groups in QGIS projects

Mappin will automatically create Mappin groups for QGIS layer groups. However, Mappin does not support nested groups (a group within a group). Therefore, if your QGIS project contains nested layer groups, Mappin only creates a group for the top-level parent group which will feature all of the nested layers within the QGIS project.