-
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
AU(Administrative Units) - Error in boundary #1036
Comments
Dear @CristinaMSL, the error should be because the validator does not find any administrative unit, in the dataset, whose contour corresponds to the boundary. Could you please confirm if this is the case? If you send us the gml, we can have a look. |
Hello Fabio. Thank you very much. I will send you the gml. |
Dear @CristinaMSL, I had a look at your gml file and I confirm that the error is due to the lack of the AdministrativeUnit feature types. Please also consider that the Administrative Units data theme has been updated and the official AU application schema is now at version 5.0 (https://inspire.ec.europa.eu/schemas/au/5.0/AdministrativeUnits.xsd). |
Dear user, we hope the solution provided helps you resolve the issue. |
Dear INSPIRE support:
I have a question on the topic AU-Administrative Units.
When validating the GML, the following error appears:
XML document 'GML_au_administrative_units_v4.gml', AdministrativeBoundary 'au_administrative_units_1': Feature does not correspond to an edge in the topological structure formed by the complete boundary graph of all Administrative Units features. It is not on the boundary of any administrative unit in the dataset.
We do not know very well, why this message comes out.
We have used the FeatureType of "AdministrativeBoundary" to make the relationships.
The only thing we can think of from the message and the options given in the section: Source: Abstract Test Case 'Boundary', INSPIRE Data Specification on Administrative Units, A.3.9; is that this happens because in our project we only have 3 of 6 nationalLevel (AdministrativeHierarchyLevel).
Why could this be happening?
I am using HALE Studio and the official schema to perform my transformation.
Regards
The text was updated successfully, but these errors were encountered: