Description
Currently, the filters appear to have suboptimal logic.
In the case of the circle, a CQL filter of this type is generated that dramatically increases the number of coordinates required as the radius increases. Example:
INTERSECTS(
geom,
POLYGON((
11.30 44.50,
11.40 44.50,
11.40 44.60,
11.30 44.60,
11.30 44.50
...
))
)
The POLYGON case can be left alone for the case of a manually drawn filter definition; this will most likely never reach a number of points sufficient to exceed the maximum length for GET requests.
How to reproduce
- create new map and add contains WMS vector layer of points
- select layer and open filters panel
- create a new Circle filter, little some kilometers
- apply the filter and save
- now increase the Cicle Ragius to big size example 200000kms
- when apply the filter in some cases geoserver request fails
Expected Result
Applying the circle filter should work for any radius size
Current Result
Other useful information
Description
Currently, the filters appear to have suboptimal logic.
In the case of the circle, a CQL filter of this type is generated that dramatically increases the number of coordinates required as the radius increases. Example:
The POLYGON case can be left alone for the case of a manually drawn filter definition; this will most likely never reach a number of points sufficient to exceed the maximum length for GET requests.
How to reproduce
Expected Result
Applying the circle filter should work for any radius size
Current Result
when apply the filter in some cases geoserver request fails for too big query
Not browser related
Other useful information