Please sign in to comment.
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FEATURE] Add option to force a vector layer to render as a raster
(under the layer properties, rendering tab) So why would you want this? Well, extremely detailed layers (eg polygon layers with a huge number of nodes) can cause composer exports in PDF/SVG format to be huge as all nodes are included in the exported file. This can also make the resultant file very slow to work with/open in other programs (*cough* Inkscape *cough*). Now, these you can force these layers to be rasterised so that the exported files won't have to include all the nodes contained in these layers. (Before you could also do this by forcing the composer to export as a raster, but that was an all-or-nothing solution). The ideal solution would be a simplification option for composer exports which would simplify the layers by removing redundant points at the export DPI, but this is an easy workaround for now.
- Loading branch information
Showing with 84 additions and 20 deletions.
- +15 −0 python/core/symbology-ng/qgsrendererv2.sip
- +7 −1 src/app/qgsvectorlayerproperties.cpp
- +14 −4 src/core/qgsmaprenderercustompainterjob.cpp
- +1 −0 src/core/symbology-ng/qgscategorizedsymbolrendererv2.cpp
- +1 −0 src/core/symbology-ng/qgsgraduatedsymbolrendererv2.cpp
- +1 −0 src/core/symbology-ng/qgsinvertedpolygonrenderer.cpp
- +1 −0 src/core/symbology-ng/qgspointdisplacementrenderer.cpp
- +3 −0 src/core/symbology-ng/qgsrendererv2.cpp
- +22 −5 src/core/symbology-ng/qgsrendererv2.h
- +1 −0 src/core/symbology-ng/qgsrulebasedrendererv2.cpp
- +1 −0 src/core/symbology-ng/qgssinglesymbolrendererv2.cpp
- +17 −10 src/ui/qgsvectorlayerpropertiesbase.ui