WebOffice author > Edit Menu > Maps Category > Map Collection

For using the OGC Map Service (WMS) in WebOffice 10.4 SP2 the service must be OGC compliant (http://www.opengeospatial.org/compliance).

Note: In case that problems occur when trying to consume an OGC WMS service (WebOffice acts as WMS client), WebOffice 10.4 SP2 will only support OGC WMS services which are OGC compliant. OGC compliance can be proven by the WMS service provider by successfully running the "OGC TEAM Engine" (Test, Evaluation and Measurement Engine) as part of the "OGC Compliance and Interoperability Testing Initiative (CITE)". See these links for more details:

http://cite.opengeospatial.org/teamengine/

http://cite.opengeospatial.org/test_engine/wms/1.3.0/

Alternatively, tests can be performed on this site: http://www.validome.org/xml/validate/.

Note: When adding a WMS service to a WebOffice 10.4 SP2 project be sure that the projection of the WMS service fits the projection of the main map service.

Note: By using a WMS service, that is secured via basic authentication (http), certain criterias have to be fulfilled. In this case user and password are sent in the http header. WebOffice 10.4 SP2 sets the following value of the field Authorization in the http header: 'Basic: ' + <username base64 encoded> + ':' + <password base64 encoded>. User and password are taken from the configuration in WebOffice author and encoded via base64. By opening those secured WMS services either directly in the browser or in ArcCatalog, a popup window for the login should appear.

Whenever a new OGC map service is added to the WebOffice 10.4 SP2 project configuration

•configure the corresponding Reference to Map Service of Map Collection in the table of content (mandatory)

•configure the corresponding reference to map service of map collection in the Map View (optionally)

OGC WMS map service (WMS) configuration

Property	Description
Server	Complete WMS Service URL. Note: By default the parameters inspire, layer_id, login, map, name, ogc_ticket, pw, service_name are allowed in the URL, any other parameters will be ignored. Although the list of parameters can be expanded in OGC Parameter Whitelist.
Service name (GUI)	Service name of map service displayed in the WebOffice 10.4 SP2 clients.
Metadata URL	Configure a reference to a metadata document (must be available via HTTP) as URL. Note: 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	Provide a short description for the metadata (line breaks with "\n").
Copyright	Service specific copyright text to be added to the configured project copyright if the map service contributes to the map. Note: The service specific copyright will only be displayed if the map element Copyright is configured. Note: Detailed information about the use of these attributes can be found in chapters Template (File Name) and WebOffice ePaper Template (File Name).
Server normalized	The normalized WMS Service URL without any WMS parameters (will be filled automatically).
Service user	User name of user accessing OGC map service. Hint: If a domain user is used for accessing the service, then the windows domain needs to be provided in the format "domain\user". If no domain is configured then authentification is done locally.
Password	Password of user accessing OGC map service.
Show legend?	Specifies if it's possible to display the legend of the service, if the service provides a legend information. Note: The WM(T)S service has to support the GetLegendGraphic operation.

OGC WMS map service (WMS) properties

Note: An easy way to configure an OGC map service (WMS) is by using the wizard Add Service.

Note: An OGC map service (WMS) can also be preconfigured for the tool Add WMS Service in the list of WMS Services.

Note: If your application does not have direct access to the internet, be sure to configure your proxy settings in WebOffice 10.4 SP2 application configuration for proper OGC WMS functionality. See chapter Proxy-Server for HTTP Requests.

Note: See chapter Map Service Properties for details about the configuration of map service properties.

Note: See chapter Legend for details about the legend in the WebOffice html client.