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

TN - tn-ro:RoadSurfaceCategory fails Transport Network feature in dataset #569

Closed
robblis opened this issue Jun 23, 2021 · 4 comments
Closed
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

Comments

@robblis
Copy link

robblis commented Jun 23, 2021

Hi Validator Team,

While testing Transportation Networks, I ran into a failure for the tn-ro:RoadSurfaceCategory feature test.

I get the following error in the Conformance class: GML application schemas, Transport Networks -> Basic test -> Transport Network feature in dataset.

The XML documents representing the spatial data set do not contain a feature of any of the spatial object types in the 'Transport Networks' application schemas. Therefore, the spatial data set cannot conform to this conformance class. If you have expected to find spatial objects from the application schema in the data set, please consult the statistics information to see the spatial object types that have been found.

I don't see the RoadSurfaceCategory listed in the test criteria.

Can I get some help on why this particular feature is failing this test?

Here is the serivce URL:
http://agsinspire1.esri.com/arcgis/rest/services/tnc/MapServer/exts/InspireFeatureDownload/service?VERSION=2.0.0&SERVICE=WFS&REQUEST=GetFeature&LANGUAGE=&TYPENAMES=tn-ro%3ARoadSurfaceCategory&MAXFEATURES=&COUNT=100&f=image

I've attached the returned XML if needed.

Thanks,
Robert

RoadSurfaceCategory.zip

@fabiovin fabiovin self-assigned this Jun 25, 2021
@robblis
Copy link
Author

robblis commented May 25, 2022

Hi @fabiovin ,

I just wanted to check if there's any progress on this issue. We're working on validation fixes preparing for a new release of our application and saw that this issue is still pending.

I made sure the service was online if you need to run some tests.

Thanks,
Robert

@fabiovinci
Copy link
Collaborator

Dear @robblis,

sorry for the late reply.

There was a typo in the ATS and in the ETS, there is the value "tn-ro:RoadServiceCategory" instead of "tn-ro:RoadSurfaceCategory".

We will update them and implement the fix in the staging instance.

@dperezBM, I have updated the ATS and created a PR for the ETS, could you please check if there are other occurrences of the wrong value?

@arantzaetxebarria
Copy link
Collaborator

Dear @robblis

The fix has been updated into staging environment, could you please verify that your issue now is correct? Thanks

Regards

@arantzaetxebarria arantzaetxebarria added ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing and removed under development labels Jun 3, 2022
@arantzaetxebarria arantzaetxebarria assigned robblis and unassigned dperezBM Jun 3, 2022
@arantzaetxebarria arantzaetxebarria added this to the 2022.2 milestone Jun 3, 2022
@robblis
Copy link
Author

robblis commented Jun 3, 2022

Hi @arantzaetxebarria

I've re-tested the service using the staging validator, and the test came back successful for the Conformance class: GML application schemas, Transport Networks.

Thanks for the fix,
Robert

@arantzaetxebarria arantzaetxebarria added solved Solution developed and accepted, not yet deployed non-breaking change The change makes tests less restrictive and it has no impact on resources already tested and removed ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing labels Jun 6, 2022
@fabiovinci fabiovinci added deployed in reference validator Solution deployed in production and removed solved Solution developed and accepted, not yet deployed labels Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

5 participants