Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WFS 2.0 Test - Temporal filter (AfterTests) in US Theme #231

Closed
Dnoack49 opened this issue Jul 18, 2022 · 5 comments · Fixed by #244
Closed

WFS 2.0 Test - Temporal filter (AfterTests) in US Theme #231

Dnoack49 opened this issue Jul 18, 2022 · 5 comments · Fixed by #244
Assignees
Labels
Projects
Milestone

Comments

@Dnoack49
Copy link

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

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?

@dstenger
Copy link
Contributor

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.

@dstenger dstenger added this to To do in CITE via automation Jul 18, 2022
@dstenger
Copy link
Contributor

dstenger commented Aug 1, 2022

@Dnoack49
Yes, we are planning to alter the conformance tests. This will happen during the next months (approximately September - October).

@dstenger dstenger added the bug label Aug 18, 2022
@dstenger dstenger moved this from To do to In progress in CITE Aug 25, 2022
@bpross-52n
Copy link
Contributor

@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?

@Dnoack49
Copy link
Author

Dnoack49 commented Oct 26, 2022

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

grafik

This did not appear before and would probably need to be fixed as well.

WFS-USEMF-DEPO.pdf

@dstenger
Copy link
Contributor

dstenger commented Oct 27, 2022

@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.

@bpross-52n bpross-52n linked a pull request Nov 3, 2022 that will close this issue
@dstenger dstenger moved this from In progress to To verify in CITE Nov 3, 2022
@dstenger dstenger assigned dstenger and unassigned bpross-52n Nov 3, 2022
@dstenger dstenger added this to the 1.39 milestone Nov 3, 2022
@Dnoack49 Dnoack49 closed this as completed Nov 4, 2022
CITE automation moved this from To verify to Done Nov 4, 2022
dstenger added a commit that referenced this issue Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
CITE
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants