Opened 14 years ago
Closed 14 years ago
#1520 closed defect (fixed)
Bounding Box value doesn't affect the view of WMS Server
| Reported by: | liuar | Owned by: | liuar |
|---|---|---|---|
| Priority: | medium | Milestone: | |
| Component: | WMS Interface | Version: | 2.2.0 |
| Severity: | major | Keywords: | |
| Cc: | External ID: | 1358903 |
Description
OGC 06-042 section 7.3.3.6
If a request contains a BBox whose area does not overlap at all with the <BoundingBox> element in the service metadata for the requested layer, the server shall return empty content (that is, a blank map or an graphic elemenet file with no elements) for that map. Any features that are partly or entirely contained in the Bounding Box shall be returned in the appropriate format.
According to OGC WMS specification, MapGuide should apply a spatial filter on the request layers. Features out of the <Boundingbox> which specified by users should not appear on the WMS layer.
This might bring MapGuide some performace issues, so I also optimized the process: if the request boundingbox within the user specified boundingbox, no spatial filter will be applied.
Attachments (1)
Change History (3)
by , 14 years ago
| Attachment: | ticket 1520.patch added |
|---|
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
In order to apply spatial filter on wms layers, I created wms layers in session repository and updated their layer definitions.