Lingbo Jiang created an issue |
Propose to add an option for latLongBoundingBox range checking before database query. |
Issue Type: |
Improvement |
---|---|
Assignee: |
|
Components: |
WMS |
Created: |
04/Feb/15 10:24 PM |
Labels: |
wish |
Priority: |
Major |
Reporter: |
|
Original Estimate: |
4 days |
Remaining Estimate: |
4 days |
Hi Geoserver community, For every WMS layer that has latLongBoundingBox set up in the config, GeoServer may restrict the request to the configured latLongBoundingBox. At the moment, it doesn’t, and this results in unnecessary query and wastes connections and cursors (for Oracle). Thus I propose to add an option in the code for latLongBoundingBox range checking. the option will allow to filter the none result query which is out of latLongBoundingBox range and improve the performance. If community reckon that it is the right way, I am willing to write the code to implement it. Lingbo |
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |