Configuration¶

Use single tab UI¶

By default, OpenGeo Explorer shows all categories (GeoServer Catalogs, PostGIS Databases, and QGIS Project) in a single panel as branches in a tree. If you enable the multi-tab user interface, each category is put in a separate tab, with a tree of elements belonging to the corresponding category, as shown in the next figure.

Multi-tab interface

Subcategories (such as layers or workspaces, in the case of a GeoServer catalog) can be accessed using the buttons on the lower part of the panel.

All other functionality is identical, though drag and drop functionality is limited to elements within the same category.

QGIS will need to be restarted for this change to take effect.

Show description panel¶

This option will toggle whether the Description panel at the bottom (or side) of the plugin interface is shown. By default, this is checked.

Ask confirmation before deleting¶

It is possible to make changes to the various connected servers and databases, including making deletions. When this option is checked, a dialog will show asking for confirmation before any deletions will happen.

Keep a list of previous GeoServer connections¶

Enabling this option will cause all connection information will be preserved between QGIS sessions.

Subsequent launching of QGIS and OpenGeo Explorer will show the Catalogs item populated with previous connections.

While the connection information is stored, catalog data is fetched only on request. Unpopulated catalogs are shown with a gray icon; Refresh the catalog item to populate it.

Previous saved connections shown in gray

If the catalog uses basic authentication, the password will not be stored. You will be prompted to enter it when you reconnect to the catalog. If the Configurations tab is used, connection data (wheter password or certificate-based) will be stored in the encrypted QGIS auth database. You will be prompted to enter the master password in case you haven’t used the auth database in the current QGIS session.

To delete a catalog from the list of previous connections, use the Remove option of the catalog item in the Explorer tree.

Always use REST API for uploads¶

This option currently has no effect. All uploads are done using the REST API.

Delete style when deleting layer¶

Layers in GeoServer must have a default style associated with it. It is possible to delete the layer without deleting the style though, to save the style for use with other layers.

When enabled, this option will delete the default style associated with the layer when the layer is deleted through OpenGeo Explorer, and when that style is not used by any other layer.

Delete resource when deleting layer¶

When this option is checked, the resource that is part of a layer will also be deleted from its corresponding store if the layer is deleted.

Overwrite layers when uploading group¶

When this option is enabled, OpenGeo Explorer will overwrite layers in the GeoServer catalog on upload, if a layer with the same name exists.

When this option is not enabled, if a layer with the same name already exists in GeoServer, it will be used, and the corresponding QGIS layer will not be uploaded.

Pre-upload processing hooks¶

If you need to process your data before it is uploaded, you can set up a pre-upload hook that will be run on any layer before it is sent to GeoServer. Instead of the original layer, the result of that hook will be uploaded.

Pre-upload hooks are defined separately for raster and vector layers. In both cases, they are defined as the path to a processing model (.model) or script (.py) file. The algorithm defined by that hook file will be loaded and executed to obtain the final layer to upload.

For raster layers, the hook algorithm must have both input and output be of type raster layer. For vector layers, both input and output must be of type vector layer. If the selected model does not exist or does not have the required characteristics, it will be ignored, and the original layer will be uploaded without any preprocessing.