Problem validating Utility datasets in new scheme
Opened this issue · 8 comments
Dear support,
When I'm validating each of my "Utility and governmental services" datasets (upgraded to the 5.0 scheme), I get the following type of error:
Example report : https://inspire.ec.europa.eu/validator/test-run/details.html?id=EIDbe53a295-9113-4028-8ce1-4fffdd1caa95
I've included the corresponding gml file in attachment.
US.ElectricityNetwork_Appurtenance_ElectricityStation.gml.zip
Can you please enlighten me on how to fix this issue?
With kind regards,
Jarrik
Dear @GIM-Jarrik,
I had a look at your gml and everything seems ok, the errror is very stange also because validation against official schema is passed.
We will have a further look.
Dear helpdesk,
Any news/updates concerning this issue?
Thanks for your time
Dear @fabiovinci
Any update about this issue?
We stumble upon the same error message in other themes as well.
With kind regards,
Jarrik
Dear @GIM-Jarrik,
we are still investigating the issue. It's not simple to identify the source, as the GML validates with other tools.
Could you please provide other sample gml files with the same error?
Dear @fabiovinci ,
In the meantime we were able to solve cases with similar kind of errors.
In those cases there was a mix of two different schema versions present in the output and we were able to mitigate the mistake by retaining only one of the versions.
However, for US this seems not the case.
Other examples within the US theme are the following:
examples_abstractfeature_error.zip
With kind regards,
Jarrik Schaepherders
Hi!
The solution I found for this error works only for the 4.0 schema (here emf) and it requires to have the target schemaLocation URL as 'http://'
So, for the EnvironmentalManagementFacilities theme: 'http://inspire.ec.europa.eu/schemas/us-emf/4.0 http://inspire.ec.europa.eu/schemas/us-emf/4.0/EnvironmentalManagementFacilities.xsd'
I hope this helps to find the solutions for the 5.0 schemas.
Dear helpdesk,
This message to signal that my colleague @GIM-Jarrik got the same issue as described in the first post when using application schema 4.0. We figured that it might help you to find a solution.
Best regards