Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python MapScript WxS Capabilities XML truncated #4668

Closed
tomkralidis opened this issue Jun 18, 2013 · 2 comments
Closed

Python MapScript WxS Capabilities XML truncated #4668

tomkralidis opened this issue Jun 18, 2013 · 2 comments

Comments

@tomkralidis
Copy link
Member

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:

  • 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

@Schpidi
Copy link
Member

Schpidi commented Jun 19, 2013

Could you maybe also post some test data? I'm having troubles to reproduce.

@tomkralidis
Copy link
Member Author

Hi: this was an artifact of using Python mapscript which was not representative of the patch fix. Updating Python mapscript fixes this issue.

Thanks much to @Schpidi and @tbonfort

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants