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.

Sign up for GitHub

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

Jump to bottom

Dataset validation : Site (AF-Theme) #809

Closed
Dnoack49 opened this issue Jun 30, 2022 · 3 comments
Closed

Dataset validation : Site (AF-Theme) #809

Dnoack49 opened this issue Jun 30, 2022 · 3 comments
Labels
deployed in reference validator Solution deployed in production non-breaking change The change makes tests less restrictive and it has no impact on resources already tested
Milestone
v2022.3

Comments

@Dnoack49
Copy link

Dnoack49 commented Jun 30, 2022 •
edited
Loading

Dear all,

I have validated these two AF-Datasets:

Holding
https://inspire.brandenburg.de/services/af_tiere_wfs?service=WFS&version=2.0.0&request=GetFeature&typenames=af:Holding&Count=10

Site
https://inspire.brandenburg.de/services/af_tiere_wfs?service=WFS&version=2.0.0&request=GetFeature&typenames=af:Site&Count=10

For the Site-Objects the following error in the conformance class GML application schemas, Agricultural and Aquaculture (Basic test / af-gml.a.1: Agricultural and Aquaculture Facilities feature in dataset) is thrown:
grafik

Here both reports for comparison:
test suite Annex III - Agricultural and aquaculture facilities (AF).zip

This is related to the issue #440 and #798.

Kind Regards
@fabiovinci fabiovinci self-assigned this Jun 30, 2022
fabiovinci added a commit to inspire-eu-validation/data-af that referenced this issue Jul 11, 2022
@fabiovinci
Add Site feature type
7232f39 
Added Site feature type according to issue 809 (INSPIRE-MIF/helpdesk-validator#809)
@fabiovinci fabiovinci assigned dperezBM and unassigned fabiovinci Jul 11, 2022
@fabiovinci
Copy link
Collaborator

The related ATS has been modified accordingly, and the change will be soon added in staging for the test.

@dperezBM dperezBM mentioned this issue Jul 11, 2022
Merged
@arantzaetxebarria
Copy link
Collaborator

Dear @Dnoack49

The fix for this issue is ready in staging environment, could you please verify?

Regards

@arantzaetxebarria arantzaetxebarria added ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing non-breaking change The change makes tests less restrictive and it has no impact on resources already tested and removed under development labels Jul 12, 2022
@Dnoack49
Copy link
Author

Dear @arantzaetxebarria ,
I have just tested it and can confirm, that the error does not occur anymore - it works as expected.
Thanks alot.

@arantzaetxebarria arantzaetxebarria added solved Solution developed and accepted, not yet deployed and removed ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing labels Jul 12, 2022
@arantzaetxebarria arantzaetxebarria added this to the 2022.3 milestone Jul 12, 2022
@fabiovinci fabiovinci mentioned this issue Jul 19, 2022
Closed
@dperezBM dperezBM mentioned this issue Sep 21, 2022
Merged
@fabiovinci fabiovinci added deployed in reference validator Solution deployed in production and removed solved Solution developed and accepted, not yet deployed labels Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deployed in reference validator Solution deployed in production non-breaking change The change makes tests less restrictive and it has no impact on resources already tested
Projects
None yet
Milestone
v2022.3
Development

No branches or pull requests
4 participants
@Dnoack49 @fabiovinci @dperezBM @arantzaetxebarria