Opened 15 years ago
Closed 15 years ago
#2892 closed defect (invalid)
WMS GetCapabilities list of supported SRS doesn't respect on-the-fly reprojection capabilities
Reported by: | soenke | Owned by: | mapserverbugs |
---|---|---|---|
Priority: | normal | Milestone: | 5.2.1 release |
Component: | WMS Client | Version: | 5.2 |
Severity: | normal | Keywords: | |
Cc: |
Description
When including a WMS client layer, the list of supported SRS for this layer in the GetCapabilites document is set to the SRS listed in the LAYER's wms_srs. This should actually at least incluse those set on the top-level WEB.METADATA wms_srs, because it confuses clients even when it is possible to do a WMS request with an unlisted SRS.
Additionally, there are some confusions with layer/map level projections: Without specifying a PROJECTION on MAP level, MapServer bails out with
<ServiceException code="InvalidSRS"> msWMSLoadGetMapParams(): WMS server error. Cannot set new SRS on a map that doesn't have any projection set. Please make sure your mapfile has a projection defined at the top level. </ServiceException>
even when a PROJECTION is set for each LAYER.
Change History (3)
comment:1 by , 15 years ago
Milestone: | → 5.2.1 release |
---|---|
Version: | unspecified → 5.2 |
comment:2 by , 15 years ago
Component: | MapServer C Library → WMS Client |
---|---|
Owner: | changed from | to
comment:3 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
no bug, srs list conforms to OGC specification (srs listed for a layer denotes _additional_ srs)