-
Notifications
You must be signed in to change notification settings - Fork 23
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
Timeout when testing OGC API Features #1112
Comments
Dear @antjacques, it seems that the issue is related to the OGC Validator. We will further investigate the issue. In the meantime, you can use the Beta OGC Validator, which seems to be working. |
Thanks @fabiovinci ! Can you provide me the address of the Beta Team Engine REST API so I can try it out on my side? I cannot find it in the link you provided. Kind regards |
Dear @antjacques, the Beta Team Engine REST API should be available at the following link: https://cite.opengeospatial.org/te2/rest/suites/ |
It seems the timeout error persists, so we opened an issue in the related OGC repository |
Dear @antjacques, Looking at the answer provided by OGC, it seems that the Beta OGC Validator (which uses revision 1.7.1 of the OGC API Features test suite) include a fix for limiting the tested data. The fix will soon be available in the Official OGC Validator and consequently in the INSPIRE Validator. |
Many thanks @fabiovinci I tried to test the beta validator with the REST API but it seems that an authentication is actually needed to perform the test suite with the URL that you provided. Kr |
Dear @antjacques, for the OGC Beta Validator, you can register here: https://cite.opengeospatial.org/te2/viewSessions.jsp I confirm that the INSPIRE Validator is automatically updated with the latest version of the OGC Validator. |
Dear @antjacques, I'm reopening the issue because it may be helpful for other users. |
Dear helpdesk,
We are trying to validate our OGC API Features module linked to GeoServer.
However, after a few minutes the test ends up with a timeout error every time.
I understand that this test is using OGC engine, I suppose they are aware of this issue since validator mentions this:
The thing is that we haven't managed to get a complete test so far after many tries. Are there any fixes that they can implement to improve the availability?
Here is the test report: Test run on 11_27 - 13.09.2024 with test suite Conformance Class OGC API - Features.html.zip
Many thanks
The text was updated successfully, but these errors were encountered: