Map View gives you the chance to configure multiple different sets of map services, layers and layer groups visibilities in a map view.


Map view configuration

Map view configuration





Name of map view in WebOffice Client


Information for the map view in WebOffice mobile client

Metadata URL:

Configure a reference to a meta data document (must be available via HTTP) as URL.


You may configure the unique Metadata document identifier (UUID) of a Catalog Service (CSW 2.0) here. In this case you must configure the SOAP interface of the Catalog Services in Metadata Display.

Metadata short description

Metadata short description

External map view-ID

Map view ID used in parametrized calls of WebOffice.


External map view IDs may not contain spaces or special characters. Only combinations of the following letters and numbers are permitted or are intended to be used:

A to Z (uppercase letters)

A to z (lowercase letters)

0 to 9 (numeric characters)

Map view category

Display group for map view

Map view Thumbnail URL

Defines the URL for the map view Thumbnail.

Example for local address: pub/images/thumbnail.png


The configuration of thumbnails for map views and basemaps only affects the WebOffice flex Client.

Provide preview images with the size 90x50 pixels but at least with the aspect ratio of 3:2.

Use in clients without TOC?

Specifies whether this map view shall be used in clients which have no table of content (TOC).

For the WebOffice html client the visibility of the TOC can be specified, the WebOffice mobile client and the WebOffice flex client do not have a TOC.

Visible in list of map views?

Specifies whether this map view shall be shown in the list of map views.

This allows defining map views that can be used for search queries and external calls but cannot be chosen manually.

Map view properties



It is recommended to use only visibility attributes on (visible) and off (invisible). Please also consider the concept when switching between map views.

It is not possible to set a cached service above a dynamic service in the table of contents. This scenario is not supported by WebOffice, because it would cause the generation of a dynamic map image of all map services, which would prevent the performance advantages of cached map services.