You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All works well, except for WMS GetCapabilities responses. The result is
a truncated WMS Capabilities XML which gets truncated when MapServer is
printing out the root Layer element.
commenting out LAYER.METADATA.wms_layer_group eliminates the issue,
but we require this functionality
commenting out LAYER.CLASSGROUP and LAYER.CLASS.GROUP, and
uncommenting LAYER.METADATA.wms_layer_group eliminates the issue, but we
require this functionality
the same mapfile works just fine with mapserv binary
Any suggestions? I'm wondering whether the Python SWIG implementation
affects this and the fix at #4638
The text was updated successfully, but these errors were encountered:
cc @Schpidi
Hi: using 6.2.1 (Ubuntu) built from source along with the following
patch at
https://github.com/mapserver/mapserver/commit/937dcb6857501835b5489fa4bea321105412a20b.patch, we have a requirement to implement a WxS MapScript
approach for our OWS (we have up until now using the mapserv binary).
All works well, except for WMS GetCapabilities responses. The result is
a truncated WMS Capabilities XML which gets truncated when MapServer is
printing out the root Layer element.
I've posted a minimal mapfile and the Python mapscript at
https://gist.github.com/tomkralidis/f70afd49270cb8efb62f. Observations:
but we require this functionality
uncommenting LAYER.METADATA.wms_layer_group eliminates the issue, but we
require this functionality
Any suggestions? I'm wondering whether the Python SWIG implementation
affects this and the fix at #4638
The text was updated successfully, but these errors were encountered: