INSPIRE-MIF / helpdesk-validator

Community discussion forum for INSPIRE validation issues
41 stars 22 forks source link

WFS 2.0 - Error on filter.temporal.DurringTests #975

Open sbunea opened 1 year ago

sbunea commented 1 year ago

Dear all,

When we testing the following service: https://inspire.mmap.ro/server/rest/services/INSPIRE/BR_download/MapServer/exts/InspireFeatureDownload/service?VERSION=2.0.0&SERVICE=WFS&REQUEST=getCapabilities on production validator using the Direct WFS test, the Temporal filter test/ org.opengis.cite.iso19142.basic.filter.temporal.DuringTests fail with the following message: OGC TEAM Engine reported a failed test: No temporal values found in results: property is "http://inspire.ec.europa.eu/schemas/br/4.0":beginLifespanVersion. expected [false] but found [true] image

Our service returns datetimes with time zones: GTB Standard Time. The existing beginLifespanVersion value in the database is: 2023-05-16T10:21:35. The validator sends this following request in UTC time zone: https://inspire.mmap.ro/server/rest/services/INSPIRE/BR_download/MapServer/exts/InspireFeatureDownload/service?service=WFS&version=2.0.0&request=GetFeature&count=10&typenames=ns94:Bio-geographicalRegion&namespaces=xmlns(xml,http://www.w3.org/XML/1998/namespace),xmlns(ns94,http://inspire.ec.europa.eu/schemas/br/4.0),xmlns(wfs,http://www.opengis.net/wfs/2.0)&filter=%3Cfes%3AFilter%20xmlns%3Ans94%3D%22http%3A%2F%2Finspire.ec.europa.eu%2Fschemas%2Fbr%2F4.0%22%20xmlns%3Awfs%3D%22http%3A%2F%2Fwww.opengis.net%2Fwfs%2F2.0%22%20xmlns%3Afes%3D%22http%3A%2F%2Fwww.opengis.net%2Ffes%2F2.0%22%3E%3Cfes%3ADuring%3E%3Cfes%3AValueReference%20xmlns%3Atns%3D%22http%3A%2F%2Finspire.ec.europa.eu%2Fschemas%2Fbr%2F4.0%22%3Etns%3AbeginLifespanVersion%3C%2Ffes%3AValueReference%3E%3Cgml%3ATimePeriod%20xmlns%3Agml%3D%22http%3A%2F%2Fwww.opengis.net%2Fgml%2F3.2%22%20frame%3D%22http%3A%2F%2Fwww.iso.org%2Fiso%2Fiso8601%22%20gml%3Aid%3D%22TP01%22%3E%3Cgml%3AbeginPosition%3E2023-05-16T09%3A21%3A35Z%3C%2Fgml%3AbeginPosition%3E%3Cgml%3AendPosition%3E2023-05-16T11%3A21%3A35Z%3C%2Fgml%3AendPosition%3E%3C%2Fgml%3ATimePeriod%3E%3C%2Ffes%3ADuring%3E%3C%2Ffes%3AFilter%3E This request returns 0 records, which is true, because the time in UTC zone, from request, are the same value like the time from the beginLifespanVersion.

If we converting the time from GTB standard time to UTC this means 2023-05-16T07:21:35, the correct request in UTC time zone should be: https://inspire.mmap.ro/server/rest/services/INSPIRE/BR_download/MapServer/exts/InspireFeatureDownload/service?service=WFS&version=2.0.0&request=GetFeature&count=10&typenames=ns28:Bio-geographicalRegion&namespaces=xmlns(xml,http://www.w3.org/XML/1998/namespace),xmlns(ns28,http://inspire.ec.europa.eu/schemas/br/4.0),xmlns(wfs,http://www.opengis.net/wfs/2.0)&filter=%3Cfes%3AFilter%20xmlns%3Ans28%3D%22http%3A%2F%2Finspire.ec.europa.eu%2Fschemas%2Fbr%2F4.0%22%20xmlns%3Awfs%3D%22http%3A%2F%2Fwww.opengis.net%2Fwfs%2F2.0%22%20xmlns%3Afes%3D%22http%3A%2F%2Fwww.opengis.net%2Ffes%2F2.0%22%3E%3Cfes%3ADuring%3E%3Cfes%3AValueReference%20xmlns%3Atns%3D%22http%3A%2F%2Finspire.ec.europa.eu%2Fschemas%2Fbr%2F4.0%22%3Etns%3AbeginLifespanVersion%3C%2Ffes%3AValueReference%3E%3Cgml%3ATimePeriod%20xmlns%3Agml%3D%22http%3A%2F%2Fwww.opengis.net%2Fgml%2F3.2%22%20frame%3D%22http%3A%2F%2Fwww.iso.org%2Fiso%2Fiso8601%22%20gml%3Aid%3D%22TP01%22%3E%3Cgml%3AbeginPosition%3E2023-05-16T06%3A21%3A35Z%3C%2Fgml%3AbeginPosition%3E%3Cgml%3AendPosition%3E2023-05-16T08%3A21%3A35Z%3C%2Fgml%3AendPosition%3E%3C%2Fgml%3ATimePeriod%3E%3C%2Ffes%3ADuring%3E%3C%2Ffes%3AFilter%3E This request return all the record from the database through the service.

The test step URI is: https://yzyiqfakm4.execute-api.eu-west-1.amazonaws.com/validator/v2/TestRuns/EID2475156c-d60d-4d76-882c-56adc170800b.html?lang=en#EID1b5f9bf0-0189-1000-b83d-f52cb7714ba0

So, could you help us to assess this issue and give us guidance?

Best regards, Simona

Test run on 13_46 - 03.07.2023 with test suite Conformance Class Direct WFS.zip

fabiovinci commented 1 year ago

Dear @sbunea,

since the error is related to the OGC WFS 2.0 Conformance Test Suite you could find the solution (or open a new issue) in the dedicated OGC repository https://github.com/opengeospatial/ets-wfs20/issues.

We will try to take a look and give you feedback.