Closed Dnoack49 closed 1 year ago
Thank you for reporting.
Indeed, the reported behavior seems to be the same as documented in #185.
I will discuss with the CITE team when you can expect this issue to be fixed and report back to you.
@Dnoack49 Yes, we are planning to alter the conformance tests. This will happen during the next months (approximately September - October).
@Dnoack49 The temporal filter tests seem to be successful now on the beta instance, as well as the production instance of Teamengine. Could you maybe do another test run?
Dear @bpross-52n
Thank you for the implementation. There are no more Errors within the Temporal Filter - Class. However, now I receive an error under get Features By Type in the Basic WFS - Class
This did not appear before and would probably need to be fixed as well.
@Dnoack49 Thank you for reporting. Can you please open a new issue for the new problem? Is the problem originally reported in this issue fixed? I propose to close it then.
Dear OGC-Community
after testing this WFS (INSPIRE Annex Theme "EnvironmentalManagementFacility" of us-govserv) against the WFS 2.0 class using both, the productive instance as well as the staging instance we receive the following AfterTest-errors for the endLifespanVersion-property in the Temporal Filter conformance class:
No temporal values found in results: property is "http://inspire.ec.europa.eu/schemas/act-core/4.0":endLifespanVersion.
Screenshot:![grafik](https://user-images.githubusercontent.com/8046960/179513339-6a2f1286-12ac-477d-9a90-eef1ea724f63.png)
TestReport: WFS-USEMF-DEPO.pdf
The property value is
2018-01-01T00:00:00
and the gml file delivered from the WFS passes the US-Theme conformance tests.I assume this is related to the issue #185 where , up to now, it is concluded that the ETS rather "not use a timezone to filter temporal properties that are reported by a server without a time zone". Will the conformance test be altered?
Would you please give us an advice?