Allow more WMTS tilematrices to pass through to frontend #991
Conversation
This file contains 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
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.
Currently we only pass through a WMTS tilematrix if it matches the current projection on the frontend. This allows more commonly used projections to be used for WMTS-layers. From user perspective this "makes more WMTS layers to work with Oskari". The admin still needs to make a conscious choice to force the reprojection for the layer with maplayer admin tools:
This way the frontend can make the best effort to show the layer even when the projection isn't matching. The projections that are passed through anyway are:
oskari-ext.propertieswith the keyoskari.native.srsBuilt-in reprojection configs added to frontend in oskariorg/oskari-frontend#2376