Open
Conversation
buehner
force-pushed
the
wmts-layers-in-tree
branch
from
a1ff70e to
2f44d82
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WMTS layers in SHOGun heavily rely on their GetCapabilities response. In case the document is not reachable, such a layer will disappear from the layer tree. On the opposite, WMS layers that are not reachable do NOT disappear from the tree.
To unify the behavior and list/display also erroneous WMTS layers in the tree, this introduces a fallback/dummy solution. Once the required capabilities resources should be available again, the layers would work as intended again.