Opened 15 years ago
Closed 14 years ago
#2031 closed bug (upstream)
Mapserver WMS Postgis Layer with no local EXTENTS definition doesn't show up in QGIS
| Reported by: | trapanator | Owned by: | pcav |
|---|---|---|---|
| Priority: | major: does not work as expected | Milestone: | Version 1.6.0 |
| Component: | WMS | Version: | Trunk |
| Keywords: | Cc: | ||
| Must Fix for Release: | Yes | Platform: | All |
| Platform Version: | Awaiting user input: | no |
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.
Change History (4)
comment:1 by , 14 years ago
| Milestone: | Version 1.5.0 → Version 1.6.0 |
|---|
comment:2 by , 14 years ago
comment:3 by , 14 years ago
| Owner: | changed from to |
|---|
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'.
comment:4 by , 14 years ago
| Resolution: | → upstream |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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.