-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Extremely Bloated PDF Vector Export under Win. #13526
Comments
Author Name: Thaddeus - (Thaddeus -) Here is some test data: 1-6-test.zip nada01_1-6_100dpi_vector_win2k.pdf "StreamsFrom+ nada01_1-6_100dpi_vector_win2k.zip" |
Author Name: Thaddeus - (Thaddeus -) This was a while ago: I'll recheck on this using the 1.7.7 later. This is using the QGIS' "Export as PDF" functionality and NOT the OS print services. As I remember, the Postscript code of the output is/appears to be corrupted, full of unnecessary operations, like saving/issuing the same PS command a few times in a row, etc. The bloated size is after unzipping the internal streams (say using PDFtk), ie, the way it has to be used/rendered by PDF application: some vector rendering of SHP produces many millions of PS code lines impossible to render on screen.
|
Author Name: Giovanni Manghi (@gioman) Yes please, check with qgis 1.7.1 or trunk and report back. I will attach here the result of exporting your project layout to PDF (using QGIS), using qgis-trunk under Windows Seven. I do not understand about the internal structure of these files, so you may want to have a look into them. The .ps version was made under Linux/QGIS-trunk.
|
Author Name: Thaddeus - (Thaddeus -) I tried 1.7.1 under Win2k and got a real nice output with a vector trace out of the SHP and everything in place: my exported PDF file is almost identical to GM's file: only differs on internal time stamp. cmp --verbose ./myPDF /tmp/otherPDF It's all great. Without being an expert though, I do believe there is some malformation/redundancy on that PDF PS code. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Antonio Locandro (Antonio Locandro) I had this issue today, I can't export a map to PDF just consisting of a CSV with about 3000 points (no labels)and an openlayers plugin basemap, size is way over 500 MB before I kill it |
Author Name: Giovanni Manghi (@gioman) Antonio Locandro wrote:
I have just tested on Windows (qgis 2.2 64bit) using a map from Openlayers and 10000 csv points, using the QGIS pdf printer, at 300 and 600 dpi and paper size up to A0. The pdf was always created very fast and with very reasonable file sizes. It would be helpful to know what configurations did you used: dpi? paper size? the pdf was created with the native pdf printer? what symbology did you used for the points (svg,other)?
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman) closing for lack of feedback.
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Thaddeus - (Thaddeus -)
Original Redmine Issue: 3466
Affected QGIS version: master
Redmine category:map_composer/printing
Assignee: Marco Hugentobler
Under Win using 1.6 I noticed the PC struggling to draw on the screen these PDF printouts to show just one pair of lat/lon point. Examining the the PDF reveals strange huge data XObjects.
The attached example was created by exporting an empty project with no objects on the Composer, that is, launch QGIS, run Composer Manager, Add a composer view and Export it.
The resulting PDF has, out of no where, 3 large embedded images, PDF objects 7, 9 and 11, each with a size of 3508 x 2480 pixels and 3 bytes per pixel in two of them, the other one is grayscale: the total cargo to process and unfold on memory is like 60 mega bytes. Also notice the PDF object 13 with malformed PS code, the third line pushes the graphic setting, and right after that pushes again, followed by pop and pop, push, push, pop, pop and finally push???
The text was updated successfully, but these errors were encountered: