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

Error namespelling - Tema Area management zones/restrictions/regulations and reporting units #1092

Closed
CristinaMSL opened this issue Jul 1, 2024 · 2 comments
Assignees
Labels
user-to-fix Problem is present on user side

Comments

@CristinaMSL
Copy link

Hello, good afternoon.

I am validating a gml of the topic Area management zones/restrictions/regulations and reporting units.
After validating the gml, the following error has come up.
I am following the same steps as in previous tables, which have been validated without any problem.

image

What could be happening?
gml+testreport.zip

Below I leave attached the gml and the test report.

I am waiting for your response.

Thank you very much in advance.

@fabiovinci
Copy link
Collaborator

Dear @CristinaMSL,

regarding the specific error you reported, please note that the "spelling" element is not encoded correctly.
See the screenshot below for details:

image

In addition, upon reviewing the GML file, it appears that the encoding is incorrect as it only contains a <am:ManagementRestrictionOrRegulationZone> featureMember with numerous occurrences of a specific element (e.g. I counted 191 occurrences of the am:thematicId element).

I would recommend reviewing the method you use to generate the GML file.

@fabiovinci
Copy link
Collaborator

Dear user,

we hope the solution provided helps you resolve the issue.
So we close this issue.
If there are any further questions or problems, please do not hesitate to reopen it or create a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user-to-fix Problem is present on user side
Projects
None yet
Development

No branches or pull requests

2 participants