Fix #2452 with WFSGeoCoder#2462
Merged
offtherailz merged 5 commits intogeosolutions-it:masterfrom Dec 7, 2017
Merged
Conversation
12 tasks
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
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.
Description
This enhances the wfsGeoCoder in querypanel's spatial field to use cross layer filtering.
If this option is configured, the querybuilder will show the geometry as usual, but the effective filter will be generated using "cross layer filtering" instead of the geometry.
This improve both performances and reduces the size of the filter, that can be used also as cql_filter in URL without exceeding max URL length.
Issues
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior? (You can also link to an open issue here)
Sync map do not work if the geometry is too complex
What is the new behavior?
When properly configured, the sync map works also with complex geometries.
Does this PR introduce a breaking change? (check one with "x", remove the other)
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
A limitation of this solution is that this improvement can not be applied you're working with different servers.