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

using internal wms layers as background for printing and raster export #416

Closed
danceb opened this issue Jan 31, 2023 · 1 comment
Closed

Comments

@danceb
Copy link

danceb commented Jan 31, 2023

I have several wms layers configured as background layers in the tenantConfig.json. In the config.json the parameter printExternalLayers is true. If the parameter url of the background layer points on a address with protocol (https://something.com/wms/background) the background layer is printed or exported as raster file as expected.

What I want now, is to use internal layers as background layers instead. So I have configured them with "wmsOnly": true within the tenantConfig.json and set them as background layers with the relative url /ows/abackgroundlayer. As a different approach the files are provided via a mapproxy, here the relative url is /mapproxy/wms in my case.

The layers are shown as background layers as expected. But while raster export or printing the background layers are not shown in the result. Via debugging I recognized that the print service is trying to get the layer from the relative url /ows/abackgroundlayer and does not know, that it have to load it from http://qwc-qgis-server/ows/abackgroundlayer. If I am setting this url in the background layer config, the layer is printed correctly, but now it is not shown as background layer in the map, because now the browser doesn't know the url.

So is there a chance, to get the printing an raster export using internal wms services and dissolving the url in a correct way as the mapviewer does?

@danceb
Copy link
Author

danceb commented Feb 1, 2023

Works now with ff936c1f9adf5f5668dab2fbb95d7244d29b3aba

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

No branches or pull requests

1 participant