Ticket #3768 (closed patch: fixed)

Opened 2 years ago

Last modified 2 years ago

print composer & wms layers (max size)

Reported by: lutra Owned by: jef
Priority: major: does not work as expected Milestone: Version 1.7.0
Component: Printing Version: Trunk
Keywords: Cc:
Platform Version: Platform: All
Must Fix for Release: No Awaiting user input: no

Description

When printing a layout that contains a WMS layer QGIS warns the user that some servers (such UMN Mapserver) only serve images of a certain size, so if the map size in the layout is bigger than the size allowed the resulting pdf/print will show a white rectangle.

The workarounds are two:

*) lower the number of DPIs, but this will produce obviously prints with a lower quality

*) (if you have control over the server configuration) allow the server to serve bigger images: this is not really a optimal solution because usually people does not own the wms server they need to use and also because allowing the server to serve bigger image can be a problem in public wms services.

Other GIS (both proprietary and OS) packages seems to not suffer of this limitation as one can print large formats with WMS layers in it, even if the server is configured to serve small images.

Looking into the PDFs produced by this packages it results that the printed map from the WMS server is tiled, making clear what kind of workaround is used.

It will be nice in the future to have this feature in QGIS.

Attachments

tile-wms.diff Download (6.3 KB) - added by jef 2 years ago.
limit and split wms getmap requests to a given tile size.

Change History

Changed 2 years ago by jef

  • owner changed from mhugent to jef
  • type changed from enhancement to patch

the attached patch adds the opportunity to set tile sizes (eg. 256x256) and then splits up the WMS request into multiple requests.

Changed 2 years ago by jef

limit and split wms getmap requests to a given tile size.

Changed 2 years ago by lutra

Hi Jurgen, many, many thanks for looking into this and for the patch. I'm still testing it and I'll give feedback asap.

Meanwhile it seems to me that this patch fixes the problem described here #1576.

Changed 2 years ago by jef

  • status changed from new to closed
  • resolution set to fixed

applied in commit:d508f56a

Note: See TracTickets for help on using tickets.