Add formats from WMS Capabilities to outputFormats
#64
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.
This PR adds the formats from the WMS Capabilities 'Formats' section into the
outputFormatsproperty ofGenericEndpointInfo.This will not retrieve any formats for WMS 1.0.0 as that handled formats very differently, all versions after that handle it the same.
The
outputFormatscan take up a lot of space in the example app as there are often quite a few formats available, particularly if the service is using GeoServer. The example service has 21 output formats. It may be worth considering tweaking this HTML to make it collapsible or something similar.Linked issue #63