Problems with INSPIRE WMS The performance is not good enough The symbolization is poor and predefined A solution for this is the Styled Layer Descriptor, but the performance is even worse.

WMTS Solution for raster data: Pros: Cons: Very good performance Easy to use with OpenLayers, Leaflet,… Perfect for raster data (images, topographic maps,…) Cons: A lot of storage resources required: One tile matrix set for each CRS (INSPIRE, GoogleCompatible, national CRS), for each symbolization (INSPIRE and national) and for each format (PNG, JPEG) For instance, in Spain the Orthoimagery WMTS need 2TB for each tile matrix set A predefined set of styles

Vector tiles vs image tiles Client (not the server) decides on styling Only need to tile the data once to have multiple maps Drawn vectors can look better on high-resolution displays Interaction is better (highlighting objects or getting alphanumeric information associated)

Vector tiles Solution for vector data: Vector tiles Used by MapBox, (https://www.mapbox.com/mapbox-gl-js/example/setstyle/) GoogleMaps (https://mapstyle.withgoogle.com/) ESRI vector tiles (https://blogs.esri.com/esri/arcgis/2015/07/20/vector-tiles-preview/) Spanish Prototype (using Geoserver and our database): http://laloteta08.cps.unizar.es:8080/demoVectorTiles/

What we have done and what we are doing… We have a draft modifying the TG for implementing INSPIRE view services, adding a new annex for vector tiles: Adding new format types (not only PNG, and GIF) Style and LegendURL are not useful (we have to work on this) Adding a new protocol: TMS (not needed but highly recommended)

What we have done and what we are doing… We have implemented a vector tile service using the same Geoserver we are using for our INSPIRE WMS and WMTS. We are going to implement a more complex viewer providing more functionalities than the prototype