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

WFS Interface for capabilities causes issues depending on the wfs setup #155

Open
lvgl-cs opened this issue Jul 11, 2024 · 0 comments
Open
Assignees

Comments

@lvgl-cs
Copy link
Contributor

lvgl-cs commented Jul 11, 2024

We might have issues with our WFS interfaces (capabilities links) depending on the wfs setup.

The main problem with priority:

If WFS proxy flag has been set, all feature types have been configured, but only a subset of featuretypes has been assigned to the GUI:

  • Capabilities General: Suddenly asks for a password even though an "internet gui/container" has been used
  • Capabilities featuretype:
    • Capabilities display works without password prompting
    • But loading in QGIS: Doesn't serve data for any featuretype

Other observations of possibly unintended behaviour:

If WFS proxy flag is set and all feature types configured + GUI assigned (internet-container):

  • Capabilities General: Works as expected
  • Capabilities featuretype:
    • Capabilities openable but with all featuretypes included
    • Loading into QGIS doesn't work though

If WFS does not have a proxy flag set (default setup)

  • Capabilities General: Works as expected
  • Capabilities featuretype: Works, but returns all featuretypes (Could be an ArcGis server problem)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants