INSPIRE Thematic Clusters

INSPIRE ETF validator is testing WFS-T conformance class instead of WFS Basic

24 Views

INSPIRE ETF validator is testing WFS-T conformance class instead of WFS Basic

Started by Iurie MAXIM Replies (2)

According to Requirement 62 of the Technical Guidance for the implementation of INSPIRE Download Services (http://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-download-services) implementations of Direct Access Download Services shall conform to ISO 19142 Conformance Class Basic WFS.

Even if there is no requirement to implement Transactional WFS conformance class (WFS-T) in INSPIRE, the INSPIRE ETF Validator is checking the implementation of WFS-T that is more demanding. Because of this, the ETF Validator is showing ”errors” that are not real errors, because they are not breaking any INSPIRE requirement or recommendation.

The description of the WFS 2.0 test in ETF is stating ”This executable test suite (ETS) checks WFS 2.0 implementations for conformance with respect to OGC 09-025r2/ISO 19142 (Geographic information -- Web feature service) and related standards.”. However few users are aware that there is no requirement in INSPIRE to conform to all the OGC 09-025r2/ISO 19142 requirements, and that the Requirement 62 is stating just to conform to ISO 19142 Conformance Class Basic WFS and not to Locking or Transactional WFS conformance classes that are more demanding and of current scope of INSPIRE TGs. 

According to Section 7 of the TG  for the implementation of INSPIRE Download Services (page 77) the Direct WFS must <<Implement Direct Access Download Service (Parts B & C) using ISO 19142 Web Feature Service and ISO 19143 Filter Encoding. This conformance class is inclusive of: TG Requirement 61 to TG Requirement 68>>. None of these requirements are mentioning WFS-T.

This is because the INSPIRE ETF Validator is executing the OGC CITE Team Engine Validator (http://cite.opengeospatial.org/teamengine) that is verifying as well the conformity against the Transactional WFS conformance class and Locking WFS conformance class, none of them being required by INSPIRE.

Even more, as described here, the ETF Validator is reporting CCW (counterclockwise) oriented geometries to be CW (clockwise) oriented geometries, most probably because it is considering Y,X geometries to be X,Y even if the CRS is declared http://www.opengis.net/def/crs/EPSG/0/3035 - that specifies ”Cartesian 2D CS. Axes: northing, easting (Y,X). Orientations: north, east. UoM: m.”. While the OCG CITE Validator is interpreting a geometry as being CCW, the INSPIRE ETF Validator is reporting an ”error” telling that this geometry is CW.

These two ETF Validator issues are creating unnecessary confusion.

Is there any possibility to require the contractor that made the ETF to disable the Geometry Orientation Test until will work correctly and to disable those OGC WFS 2.0 CITE tests that are not specific to Basic WFS ?

This should not be too complicated, just some lines of code must be commented or removed.

Most users and beneficiaries are not aware of these issues and considers that the tools provided under the ec.europa.eu domain are reporting errors correctly. Therefore it would be important to fix these issues as they are known or at least to advertise these known issues when executing the ETF Validation or easyer to disable these tests until will be fixed.

Does anyone else identified other non-real errors of INSPIRE ETF Validator ?

Iurie

Replies

    • Public

    By Michael LUTZ

    Dear Iurie,

    thanks for highlighting these issues. Please log any implementation issues with the INSPIRE reference validator (ideally as individual issues) in the issue tracker for the ETS (or, if they are already caused by an error in the ATS, the relevant ATS for WFS-based download services). Then, the team and INSPIRE sub-group working on the validator will start looking into them.

    Thanks,
    Michael

    • Public

    By Iurie MAXIM

    Dear Michael,

    Thank you for reply. My question and recommendation was posted here because as it can be seen, the CCW/CW issue was reported long time ago and nothing happened and people are still reporting this issue :

    24 July 2017 - https://github.com/inspire-eu-validation/ets-repository/issues/60

    19 January 2018 - https://github.com/inspire-eu-validation/ets-repository/issues/137

    22 January 2018 - https://github.com/etf-validator/etf-gmlgeox/issues/20

    29 March 2018 - https://github.com/inspire-eu-validation/ets-repository/issues/147

    The CCW/CW validation problem was even raised at the 2017 INSPIRE Conference that was held September, but still nothing happened.

    The solution that I proposed till this issue will be fixed, is simply to eliminate this test.in order not to create unnecessary confusion as non-real errors are reported as errors and either users are trying ”to fix” their services without success, either beneficiaries considers that the services are not conformant.

    Therefore I am asking again, is there any possibility to require the contractor that made the ETF to disable the Geometry Orientation Test until will work correctly and to disable those OGC WFS 2.0 CITE tests that are not specific to Basic WFS ?

    This should not be too complicated, just some lines of code must be commented or removed. For us, it took few hours to find which lines of code to be commented and I suppose that for the contractor that wrote the code could be even faster.

    Best regards,

    Iurie Maxim

Biodiversity and Management Areas Cluster

Biodiversity and Management Areas Cluster

Thematic Biodiversity and Management Areas Cluster. If themes like Protected Sites, Area Management/Restriction/Regulation Zones and Reporting Units, Habitats and Biotopes, Species Distribution, Bio-geographical Regions matters to you, join these groups!