Rune Aasgaard created an issue |
Honoring “Customize Attributes” in choice of correct geometry column in WFS requests to PostGIS |
Issue Type: |
Bug |
---|---|
Assignee: |
Unassigned |
Created: |
08/Dec/22 12:13 PM |
Priority: |
Medium |
Reporter: |
When using a table with several geometry columns as a data source it is possible to use “Customize attributes” in the Layer dialog panel to restrict geoserver to use only one of them. This works well for WMS layers, but not for WFS layers. The following SQL examples were extracted from geoserver in “VERBOSE” logging mode. Only the column “geometry” was selected in “Customize attributes”. In both cases the correct geometry column (“geometry“) was selected for the result set, but in the request for the WFS server the wrong geometry column (“solid_geometry“) was used for the BBOX search, but this is done correctly for the WMS request. This is the database request from the WFS, using the wrong geometry column for BBOX filtering:
This is the database request from the WMS using the correct geometry column for BBOX filtering:
Is it possible to make the BBOX filtering for the WFS behave like for the WMS? |
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100212-sha1:8cdcfbb) |