Bug report #2031
Mapserver WMS Postgis Layer with no local EXTENTS definition doesn't show up in QGIS
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Low | ||
| Assignee: |  Paolo Cavallini | ||
| Category: | Web Services clients/WMS | ||
| Affected QGIS version: | Regression?: | No | |
| Operating System: | All | Easy fix?: | No |
| Pull Request or Patch supplied: | Resolution: | ||
| Crashes QGIS or corrupts data: | Copied to github as #: | 12091 |
Description
I have a Mapserver configured for WMS.
If in the .map file there are some PostGIS layer,
you need to copy the EXTENT key on the mapfile definition on each PostGIS LAYER definition in the mapfile.
QGIS seems that is not able to detect the extend of a WMS layer of a PostGIS spatial table.
This problem doesn't occur with shapefiles.
History
#1
Updated by Ivan Mincik over 14 years ago
What is Your Mapserver version ?
I have tested this behavior in Mapserver 5.2.3 and discovered that without setting 'EXTENT' or 'wms_extent' for each PostGIS layer Mapserver is providing incorrect 'BoundingBox?' values for the layer (At least in my case.) So it can be Mapserver issue.
#2
Updated by Ivan Mincik over 14 years ago
It may be related to these tickets:
http://trac.osgeo.org/mapserver/ticket/1851
http://trac.osgeo.org/mapserver/ticket/287
I think we can resolve this ticket as 'wontfix'.
#3
Updated by Jürgen Fischer over 14 years ago
- Resolution set to upstream
- Status changed from Open to Closed