-
Notifications
You must be signed in to change notification settings - Fork 11
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 (nts) on request parameter in filter for wfs 2.0 #227
Comments
Thank you for reporting. |
I can confirm that several tests fail on Production (http://cite.ogc.org/teamengine/) and Beta (http://cite.ogc.org/te2/). Following test fails several times:
and
This was already described in the description of this issue. However, several other tests also fail but with a different error message: E.g. @bpross-52n Can you please do a deeper analysis why the |
@dahermansson
The GML namespace is bound to tns prefix. So, the correct namespace is used in the request. You need to configure your server to be namespace aware. |
When we use the service at https://cite.opengeospatial.org/teamengine/rest/suites/wfs20/ with the Inspire Validator we get faild tests on a bunch of tests which looks like the reason to fail is a request with a filter thats not correct. The namespace on the field in the filter is set to "tns" like in tns:Identifier
the correct way to create the filter is to use gml:Identifier
As described in the Issue 746 at Inspire-Validator we can't find any reason for it to use "tnf" as prefix/namespace in the requests.
To Reproduce
Steps to reproduce the behavior:
Validate a Inspire WFS-service.
Expected behavior
Corrected formated filters using the expected field.
Screenshots
Attached a ziped testresult (.rdf)
TN_Road_WFS2022_05_03.zip
The text was updated successfully, but these errors were encountered: