Test steps Test steps

OGC ® Engineering Report OGC 14-057 Copyright © 2015 Open Geospatial Consortium. 30 Illustration 9, London Topo Snowflake

4.2.1.3 Scenario 3

In Scenario 3, participants tested their implementations of the OGC WMTS standard in a variety of commercial and open source GIS software. Services had to be WMTS- compliant. The goal of this use scenario was to understand the success rate of interoperability across the various GIS platforms.

4.2.1.3.1 Test steps

WMTS was run in Sprint 2 only – no WMTS was tested in Sprint 1. A very limited test plan was established for WMTS Connect to Ordnance Survey Network Service Endpoint 1: http:ondemandapi.ordnancesurveyite.co.ukosmapapiwmtsgcP7UGF35TGetCapabilities?SE RVICE=WMTSVERSION=1.0.0REQUEST=GetCapabilitiesURL=http:www.ogcplugfest.com Does your application officially support version 1.0 Indicate support for KVP, REST, SOAP OS OnDemand WMTS uses an API KeyReferrer model of authentication ‐ as many GIS clients assume a usernamepassword model there may need to be some investigation of connection functionality. Layer count, name Layers, MatrixSet, LayerStyles, Identifiers, … OGC ® Engineering Report OGC 14-057 Copyright © 2015 Open Geospatial Consortium. 31 Retrieve Tiles from osgb, Southampton Zoom into Southampton Is transparency supported? if Tile has tranparency alpha channel Retrieve Tiles from OS OpenData, Style: default TileMatrixSet OS OpenData, Identifiers 00, 01,…,10, Tile x,y. What image encoding is supported by the client? Click on a feature on the map and retrieve feature info using GetFeatureInfo if supported by the underlying WMS. Make a screenshot how the Feature Information is displayed Retrieve Legend image for the map Service Endpoint 2 External: http:datapoint.metoffice.gov.ukpublicdatainspireviewwmts?REQUEST=GetCapabilitiesk ey=APIKEY Access GetCapabilities Connect and display available layers in Geospatial Portal Service End‐Point 3 External: http:demo‐apollo.geospatial.intergraph.comerdas‐iwsogcwmts Display bluemarble layer Service End‐Point 4 External: http:sampleserver6.arcgisonline.comarcgisrestservicesWorldTimeZonesMapServerWMT S1.0.0WMTSCapabilities.xml Display layer WorldTimeZones.

4.2.1.3.2 Outcomes

Service end‐Point 1 was protected by a “Referrer URL” – this caused confusion and mixed results. Some application were able to get the capabilities document of the OGC ® Engineering Report OGC 14-057 Copyright © 2015 Open Geospatial Consortium. 32 WMTS service. Some applications were not able to handle referrer URLs at all, resulting in a service error indication. Some applications had a problem with the order of the parameters the location of the parameter in the URL key had an impact on the retrieval of service information and some applications needed the URL query string parameter to be explicitly included. Scale denominators associated with the tile matrix sets are important when using WMTS. The application understands the sparsely populated tilematrixsets and only makes requests when the screen display is at the correct scale. Determining the actual scale of the screen requires a good understanding of the physical capabilities of the screen e.g. pixel size. In Windows environments, the rule of thumb is 96dpi, however it is better to query this than to assume it. Potentially WMTS should define the assumed device pixel size in relation to the scale denominators Some application raised an issue, as the OS capabilities indicated floating point MatrixWidth and MatrixHeight values as floating point, while the WMTS schema said ‘positiveInteger’. The application “hacked” the parsing value to make it work. When applications correctly received the referrer URL authentication, access to the tiles was non trivial and limited tiles were returned. What the exact issue was could not be determined during the execution of the test script and time was too limited to investigate toughly. Service end‐Point 2 was API‐key protected. An API‐key had to be requested by the client – but no participants were able to obtain a key 2. One application was not able to parse the capabilities document and processing ended and another application was able to parse the capabilities document, but was unable to display layers in EPSG:27700 or EPSG: 4326. Service end‐Point 3 was accessible, but not all applications were able to display tiles 1 application yielded an http 500 error – the application automatically appended the version as part of the request, which caused the error Service end‐Point 4 was accessible by all participating organisations 3 and displayed the WorldTimeZones.

4.2.1.4 Scenario 4

In Scenario 4, web map services from UK GI organisations were combined to create a cascading WMS serving mapping data covering the whole of the UK. Ordnance Survey added its OS OnDemand WMS to the cascading WMS. The goal of this use case was to understand interoperability issues in cascading services that provide UK coverage, as well as the numbers of services that can be cascaded i.e., performance, overhead on known and unknown server, etc.. OGC ® Engineering Report OGC 14-057 Copyright © 2015 Open Geospatial Consortium. 33

4.2.1.4.1 Test steps

In Sprint 2, this test plan was not executed, as Sprint 1 indicated that a Cascading WMS behaves absolutely the same a non-cascading WMS. From a client application point of view, there is no distinction between a cascading WMS and non-cascading WMS.

4.2.1.4.2 Outcomes