tag:blogger.com,1999:blog-4340867754151550673.post7518821444354213183..comments2023-08-24T05:54:02.019-07:00Comments on Better Print Support: Draft ProposalCarlos Lópezhttp://www.blogger.com/profile/01288415763243540873noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4340867754151550673.post-33762271783827712762012-02-20T04:37:05.218-08:002012-02-20T04:37:05.218-08:00Call us at we24support Lexmark Printers Support nu...Call us at we24support Lexmark Printers Support number at 1-866-978-0799,Enhance your system <br />functioning and keep it clean with we24support services.<br /><a href="http://www.we24support.com/lexmark-printers-support.html" rel="nofollow">Lexmark Printers Support</a><br /><a href="http://www.we24support.com/lexmark-printers-support.html" rel="nofollow">lexmark printer technical support</a>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4340867754151550673.post-10512130998423144282010-04-07T15:39:44.925-07:002010-04-07T15:39:44.925-07:00Great to see your proposal coming together!
Here ...Great to see your proposal coming together!<br /><br />Here are my comments:<br /><br />* First Paragraph: the problem is not just when printing maps to PDF. Certainly many people target PDF output when going to print but all formats require advances to support high resolution output/scaling. But, I understand why you stated it this way, because the example of townguide pushing PNG output into a PDF certainly highlights easy problems that needs fixing. The more advanced way to provide PDF output is to render all map features as vectors into the PDF (or SVG). Even thought the PDF format can support embedded rasters, usually when high resolution output is desired the PDF will look better and be of smaller size when all vectors are used.<br /><br />* I like the way you've divided up the application into "control over scaling" and "post-processing"! Very nice.<br /><br />* "Better post-processable output" section says: "photo editing applications". Really people are using vector editing or vector drawing applications like inkscape and illustrator, not photo applications (which work on rasters). I'm sure you understand this, its likely just a typo...<br /><br />* You say "so the challenge is to investigate, design and implement an algorithm for scaling raster". Actually I think it is easy to scale rasters, and in fact the algorithms to do so (always uses to scale down) are already available inside mapnik (http://svn.mapnik.org/trunk/include/mapnik/graphics.hpp_). The trick is that certain objects need to be scaled BEFORE being painted onto raster surfaces. In some cases this is easy, e.g. if higher resolution output is requested (to be rendered by AGG) then larger fonts and line widths can be fetched before rendering, etc... I've not given it much thought, but potentially the "scaling" factor will need to be different depending on whether the output is raster (via AGG) or vector (via Cairo). Not something that needs to be solved now of course, but a fun challenge to test this summer :) Symbols are different of course, because currently mapnik only supports raster symbols which, if scaled up, look bad. But you cover this later on, so let's not worry about this to much now...<br /><br />* The next several paragraphs in that sections are great!<br /><br />* Re: "Implementation of an algorithm for scaling raster symbols if needed (this point needs to be investigated further to determine its applicability in the project" - this is good enough for the application. We can talk more about this. In particular Tom Carden has some ideas that might help that he is researching. And Artem has recommended using AGG SVG parser to read symbols in a format that can then be easily scaled.<br /><br />* in relation to writing a new svg_renderer: I talked with Artem more about this today and I want to confirm that I think this is a very good idea that it should be feasible to have a part of the project, with Artem's guidance, so he will be the primary contact in advising this. However, you say "cairo_renderer already produces SVG output, but does so in a rather slow way [7]. " I think a native svg authoring renderer certainly could be written to be faster than cairo, but the main idea is that we need something more flexible that Cairo can provide, to be able to customize our output for more of the varied usecases of SVG/Post-processing. We can talk more about these later.<br /><br />* I really admire and support your ideas about how your skills can contribute to Mapnik and GIS software as a whole. Bringing Math and Graphics skills to GIS problems is exactly the basic of this project, so great stuff.<br /><br />* I also think the collaboration with Waldemar is fantastic - thanks for making this possible.Unknownhttps://www.blogger.com/profile/01802267613105953357noreply@blogger.com