-
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
INSPIRE Validator cannot be reached #196
Comments
Dear @JohannaOtt Thank you for the comment. We are currently performing maintenance works. You can still use the staging instance. Sorry for the inconvenience. Regards. |
Dear @JohannaOtt The INSPIRE Reference Validator at http://inspire.ec.europa.eu/validator/ is up and running again. Sorry for the inconvenience. Regards. |
Dear @danielnavarrogeo |
Now it works again. You can use: http://inspire.ec.europa.eu/validator/ Regards. |
@danielnavarrogeo I am sorry, but the validator still gets stuck for me at the exact same test |
Dear @JohannaOtt We are studying what is causing the error in the validator. It seems to be related with a gml file named 'US_govser_testDataINSPIREvalidator.gml.zip'. We are reproducing the error in a local instance. Regards |
Dear @danielnavarrogeo Thanks for investigating. This is the file I uploaded (tried as zip and as gml - got stuck at the same test). I was able to test the same file (only with a different name) successfully last week in case that helps. |
Thank you @JohannaOtt for the information. We will keep you updated. |
Dear @JohannaOtt
These appeared along all the GML in the validation, and was causing an uncontrolled exception in the validator. We made a quick test loading the WFS collection in QGIS and saving it again as a GML, and the geometries were validated. Of course this is not a valid test result because the GML was not saved using the INSPIRE schema, but at least we know that the geometries are well formed to be loaded. We need to delve deeper on the issue on why this is crashing the validator instead of just throwing an error on the Test Report. |
Dear @carlospzurita |
Dear @JohannaOtt For now, we would like to ask you to don't submit this test runs, at least until we have found a way to fix the problem. Also, can you give us permission to share the dataset causing the crash (or a simplified/anonymised version of it) with the colleagues from the Techincal Commitee for the ETF validator software in order to help find a solution? |
Dear @carlospzurita I did not do any testing today as I was not able to reach the validator. |
@carlospzurita I got feedback from the data owner that the dataset can be shared for testing/fixing purposes. |
@JohannaOtt thank you very much, we will come back to you with the results of our testing. |
Dear @JohannaOtt We have been testing with your dataset and we found the source of the error. The validator relies on the library deegree to parse GML geometries and validate them. There is an error in the srsName and srsDimension attributes detection, causing the gml:posList interpreted as 2 dimension. This is an issue that you have encountered in the past (see inspire-eu-validation/ets-repository#161) and still persist. Adding those attributes to the gml:posList on the GML file lets the validator process the geometry. This is of course a temporary solution, as these attributes are not required by the GML schema. However, until we deploy a hotfix for this issue, is a quick workaround for the validation of your datasets. |
Dear @carlospzurita |
Dear @JohannaOtt We added a workaround for this issue. Please check it out on https://github.com/inspire-eu-validation/community/issues/203#issuecomment-584600627 |
Dear @carlospzurita I just uploaded the file to the staging instance and the validator did run without crashing. Thank you for the quick fix. |
When trying to access the INSPIRE Validator at http://inspire.ec.europa.eu/validator/, I get this error:
504 Gateway Time-out
nginx/1.14.1
The staging instance at http://staging-inspire-validator.eu-west-1.elasticbeanstalk.com/etf-webapp/ still works.
The text was updated successfully, but these errors were encountered: