Use ows:Keyword for WFS 2.0.0 content metadata #808
Merged
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.
I noticed when making GetCapabilities requests against WFS 2.0.0 services that the keywords list for a FeatureType was empty.
The cause was the
ContentMetadata
class searching forwfs:Keywords
rather thanows:Keywords
. A quick look at the WFS 2.0.0 specifications seems to indicate the current behaviour is incorrect.This PR corrects this behaviour. I have tested against a Geoserver instance, and the LINZ data service.