-
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
Wrong namespace on request parameter in filter #746
Comments
Dear @dahermansson, this error is coming from the OGC TEAM engine validator, which is used as a dependency on the Direct WFS ETS. You can open the issue in their Github repository https://github.com/opengeospatial/teamengine, and include the validation result using their own TestReport format through the request: https://cite.opengeospatial.org/teamengine/rest/suites/wfs20/run?wfs=https://geo-inspire.trafikverket.se/Mapservice/wfs.axd/TN_RoadTransportNetwork?service=WFS%26request=GetCapabilities%26version=2.0.0 |
Closing this Issue as it's been tracked in opengeospatial |
Dear @dahermansson, thank you for opening the issue in the OGC repository. We can leave this issue open until the related issue is resolved by OGC, as it may be useful for other users to know about the error. |
Dear @dahermansson, it seems the OGC team provides you with a solution for your error, were you able to implement it and test it? |
Dear @dahermansson, since there was no response we will close the issue, please reopen it if the error persists. |
In tests for Basic WFS (org.opengis.cite.iso10142.basic.filter.PropertyIsLikeOperatorTestes)
we get allot of faild tests and its looks like the validator are creating the filters for some featurtypes with wrong namespace.
A faild test is reporting this request: tns:Identifier wich return an error. If i change the type in the filter to gml:identifier the request givs the correct requested response. Why is it using the namespace TNS? We can't find any referens to that namespace in our services our in Inspire specifications. Some of the test for filter are working correctly and I can't find any difference in them or our metadata to manage the namespace the validator is trying to use for these test/request.
FYI: @Mi-I
The text was updated successfully, but these errors were encountered: