3.2.1There is no styles defined in the Technical Guidelines AC-MF to be supported by the INSPIRE View Services
Issue number: 8
Affected documents: TG
Themes: Atmospheric Conditions and Meteorological Geographical Features
Subject: There is no styles defined in the Technical Guidelines AC-MF to be supported by the INSPIRE View Services
Description:
In the section 11.2 Styles required to be supported by INSPIRE view services in Document D2.8.III.13-14 Data Specification on Atmospheric Conditions and Meteorological Geographical Features:
There is a wide explanation of different types of styles for meteorological features but there is not any concrete style defined.
The text is the following:
‘An even more difficult task that defining layer names, is to define a standard visualisation styles for atmospheric coverage data. Well-know and widely used, even legally mandating meteorological data visualisation styles have been defined the WMO and ICAO, but these are designed for specific usage contexts (weather forecasters and aviation), and may not be suitable for non-expert or cross-theme usage contexts.
Most meteorological properties are portrayed differently according to the intended usage: For example a ground temperature coverage could be visualised as a colour map, an isoline contour plot, or as numerical values at certain points on a map. Which visualisation is the most suitable not only depends on a use case, but also from the selected visualisation styles other layers at display.
For the reasons stated above, this document does not specify any requirements or recommendations for styling of the meteorological coverage data as INSPIRE View Service layers. It is however recommended that existing de facto or de jure standards for coverage and feature meteorological data visualisation be used when the anticipated user community is expecting them: If the service is mainly intended for meteorological expert users, then the visualisations should follow the WMO meteorological data visualisation standards as closely as possible. The compliancy with existing visualisation standards should be indicated in the layer or service metadata.’
Corrigendum:
We think that it is important to define a styles for the meteorological information to be supported by INSPIRE View services.
TC facilitator evaluation:
Notwithstanding the comments in the data specifications, it would be useful to agree a baseline styling that could be used for ACMF.
Kathi Schleidt: See comment above about the lack of layers with observational data
Themes: Atmospheric Conditions and Meteorological Geographical Features
Subject: Correction of Bookmark error in ToC - TG GGS
Description: The Table of Contents (ToC) of TG on AC-MF v3.0 currently shows 7 bookmark errors. These errors shall be corrected to provide an appropriate ToC.
Corrigendum: Correct the bookmark error in the ToC.
Discussion link:
TC facilitator evaluation:
Jordi Escriu: From Jordi Esriu: Something is wrong or mixed here.
“TG GGS” stands for the Technical Guidelines on Geographical Grid Systems, but the INSPIRE theme currently referenced in the proposal is AC-MF.
TC link(s):
3.2.3Include GoogleMapsCompatible as one of the recommended Tilematrixset
Country /Issue number:
SPAIN/1
Affected article / annex:
Annex III
TG for the implementation of INSPIRE View Services: INSPIRE Profile of WMTS 1.0.0
Subject: Include GoogleMapsCompatible as one of the recommended Tilematrixset.
Observations / problem description:
Most of the requests that WMTS services receive are for Web Mercator tiles, so WMTS services are “obliged” to support this projection and Tilematrixset. For example, more than 90 % of tile requests WMTS Services of CNIG in Spain gets in EPSG:3857.
The proposed Tilematrixset produce tile contents totally coherent and compatible with OGC Standards. We propose to extend Implementation Recommendation 21 to include other TileMatrixSet: GoogleMapsCompatible (EPSG:3857).
Proposed legislative change(s):
(including precise reference, current text and proposed amendment): Technical Guidance for the implementation of INSPIRE View Services
(proposed text in blue)
Page 78:
5.2.7 Interoperability: TileMatrixSet
Implementation Recommendation 21: Every layer offered by a INSPIRE WMTS should use the INSPIRECRS84Quad TileMatrixSet and, additionally the GoogleMapsCompatible TileMatrixSet
This document specifies two TileMatrixSets: INSPIRECRS84Quad and GoogleMapsCompatible.
The main reason for recommending a common TileMatrixSet for every INSPIRE WMTS is to ensure that every INSPIRE WMTS layer will be available with the same resolutions pyramid (and with the same CRS). The interoperability between different INSPIRE will consequently be eased.
Two of these scale sets are “irregular” global CRS84 scales sets designed, for cartographic purposes.
The third one is defined to allow quad-tree pyramids in CRS84. In addition, this pyramid offers the same Scale Denominator than the ones used by Google.
The last scale set is the usual Google scale set in Pseudo-Mercator (EPSG:3857).
The INSPIRECRS84Quad TileMatrixSet described here is based on the third Well Known Scale Sets of [OGC 07-057r7] (GoogleCRS84Quad). The difference between INSPIRECRS84Quad scale set and GoogleCRS84Quad is also explained.
Following the most current client implementations is also defined the GoogleMapsCompatible TileMatrixSetdescribed on the fourth Well Known Scale Sets of [OGC 07-057r7] (GoogleMapsCompatible). This TileMatrixSets is called World Web Mercator TileMatrix Set in OGC WMTS Simple Profile [OGC 13-082r2].
5.2.7.1 INSPIRECRS84Quad
(unchanged)
DIFFERENCE BETWEEN GoogleCRS84Quad AND INSPIRECRS84Quad
(unchanged)
5.2.7.2 GoogleMapsCompatible
Table 17: GoogleMapsCompatible – Pixel size for each level
Rationale for change(s):
(including concrete implementation evidence)
Most of the requests that WMTS services receive are for Web Mercator tiles, so WMTS services are “obliged” to support this projection and Tilematrixset because GoogleMapsCompatible Tilematrixset is used on all view client
TG view service recommends only the INSPIRECRS84Quad TileMatrixSet, but for small scale it is necessary a projection
INSPIRECRS84Quad TileMatrixSet does not have projection, and it’s necessary a tilematrixset with projection.
There are no projected CRS allowed by INSPIRE for tiled web services
WMTS Simple Profile has recently been approved as official OGC standard. The objective is to solve the frequent incompatibilities between different implementations of WMTS standard. It defines Web Mercator as one of the two SRS allowed, and “GoogleMapsCompatible Tilematrixset” (also called “Web Mercator Tilematrixset”) as one of the 2 Tiling schemas allowed.
Expected impacts (including benefits):
There will be a projected CRS allowed by INSPIRE
TG view service will adapt to current client implementations
TG view service will be compatible with OGC WMTS [OGC 07-057r7] and OGC WMTS Simple Profile [OGC 13-082r2]
TC facilitator evaluation:
Background
Change proposal derived from the "Nested Grid" initiative (namely "Spherical Mercator Grid"), a possible global grid already presented and explained to the INSPIRE community, based in WMTS Simple Profile and Pseudo-Mercator projection - EPSG:3857 (namely "INSPIRE Spherical Mercator").
Particularly, the change proposal is requesting to add the ""GoogleMapsCompatible"" (EPSG:3857) TileMatrixSet as a recommended one in the TG for the Implementation of INSPIRE View Services (applicable to WMTS).
First evaluation
In my view - Regardless the possibility to analyse and accept the "Nested grid" in the INSPIRE context, EPSG:3857 is a widely used CRS at global scale for visualization purposes. Therefore, it seems quite reasonable to accept this CRS and the corresponding TileMatrixSet for WMTS. In case of acceptance, EPSG:3857 shall be adopted in the INSPIRE context (please see the "ES - Additional CRS & GRID" complementary change proposal), at least for visualization purposes.
To be further analysed if any other additions different from those proposed to the TG are also needed in coherence (e.g. any requirements in the IR on Network Services).
Swap INSPIRE version 3 schema as default to recommended (this schema was formally developed as a ‘downward extension’ of the GeoSciML 3 conceptual model), with GeoSciML 4.1 to become default from recommended.
In the 2013 version 3.0 of the TG Robert Tomas wrote: “These aim at providing a unique encoding solution (e.g. a transformation tool) to fully address both INSPIRE and GeoSciML requirements. However, this proposed solution
{at the time this was GeoSciML 3.2 and before it became an OGC standard (schemas served from OGC) and it’s ‘Basic’ level became fully INSPIRE conformant at version 4– the Basic level was redesigned to provide the mandatory INSPIRE requirements)
needs to be tested by the wider stakeholder community as part of the INSPIRE Maintenance and Implementation Framework. Based on the results, it should be discussed whether the current default INSPIRE encoding (see Section 9.3.1. ) can be replaced by the GeoSciML encoding.”
GeoSciML 4 has been widely used and user guide documented since before the EGDI project in June 2016 and became the Geology OGC standard in March 2017. Has modern advantage that it also includes the GSML-Lite (INSPIRE compliant WMS and underlying Simple Feature WFS encoding being used for delivery of collated, applied, geoscience datasets) simplified schemas that can also refer directly to the full complex property schema objects if they are being served. Allows access to extended Geoscience schema modules as part of the standard.
Corrigendum: p. 100…replace with:
Name:GeoSciML
Version: 4.1, GML, version 3.2.1 Specification: http://www.opengeospatial.org/standards/geosciml
schemas: http://schemas.opengis.net/gsml/4.1
Character set: UTF-8
GeoSciML v 4.1 is the community developed exchange format for providing detailed geoscientific information and has now reached maturity as a global OGC standard (http://www.opengeospatial.org/standards/geosciml). It also served as the basis for the more simplified INSPIRE Geologycore data model and the GeoSciML 4.1 Basic and Borehole schemas fulfill the INSPIRE requirements whilst allowing full access to the extended rich content possibilities of GeoSciML including the GeoSciML-Lite Simple Feature SF0 WFS and INSPIRE compliant View (WMS) services. The detailed guidelines, entitled “GeoSciML 4.1 Encoding Cookbook for OneGeology and INSPIRE” document how to use GeoSciML Basic and Borehole for INSPIRE andis available at http://www.onegeology.org/docs/technical/GeoSciML_Cookbook_1.3.pdf
And various earlier references to GeoSciML in the document updated (see tracked changes).
Discussion link: https://themes.jrc.ec.europa.eu/pages/view/2888/cookbooks-that-can-be-used-for-the-conversion-of-onegeology-europe-web-services-to-INSPIRE-web-services and too many other references to list but defacto standard since well before summer 2016. At INSPIRE conference 2017 ESRI-USA agreed to include support for outputting GeoSciML 4.1 Basic and Borehole in their ArcGIS for INSPIRE software as long as it was proposed as at least a Recommended schema in the next version of the TG. Open source support for GeoSciML has been ongoing for years and it has been used as tests for the client tools being developed to read INSPIRE complex property schemas.
