Hi,
The tile cache is going OK for me; I’m using the GeoServer integrated GWC with TMS layers.
Word of warning Jim - as you may have gathered from my other thread, 600DPI uses lots of RAM on the server to generate the WMS requests. You’ll probably need to tweak some settings to get them to generate.
The first YAML template took me about a day to do (I used Stephen’s generously provided config as a guide). But now I can create a new one inside of an hour. Fortunately I’m skipping the “wait on management’s approval” stage. 
Jonathan
On 9 April 2013 20:05, Stephen V. Mather <svm@anonymised.com> wrote:
Hi Jim,
Using a tile cache in the printing module will definitely apply scaling in strange ways to the symbolization. Direct WMS rendering, however, should take into account the DPI parameter and scale fonts and symbols appropriately.
Best,
Steve
Stephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com
From: Jim White [jbw2003@anonymised.com]
Sent: Tuesday, April 09, 2013 2:44 PM
To: Jonathan Moules
Cc: geoserver-users@anonymised.comceforge.net
Subject: Re: [Geoserver-users] GeoServer Printing Module
Jonathan,
I used the print-form in the GeoExt examples to add dpi selection of 150, 300 and 600. Haven’t had time with my boss yet to go over what the PDF should look like and any changes in YAML aside from dpi and adding permissions for printing OSM.
All works good except for labels which change appearance at different dpi and sometimes don’t show at all. I am using TileCache for the label layer, so not sure what difference that makes.
Jim
On 04/09/2013 07:03 AM, Jonathan Moules wrote:
Hi Jim,
Sorry for the delay, been out for a bit.
The high end of mine is 600dpi which works fine for me. Takes a while though, at least if there are rasters in there.
I agree that YAML is a pain - one thing to note that got me for a while - spaces only, no tabs.
Jonathan
On 28 March 2013 16:24, Jim White <jbw2003@anonymised.com> wrote:
Hi Jonathan,
I added 2 lines to my print function:
printCapabilities.createURL = “http://test.zo.ncsu.edu/geoserver/pdf/create.json”;
printCapabilities.printURL = “http://test.zo.ncsu.edu/geoserver/pdf/print.pdf”;
This fixed my problem. Now I just have to figure out config.yaml. Have you tried to print at higher than 300 dpi?
Thanks,
Jim
On 03/28/2013 06:14 AM, Jonathan Moules wrote:
Hi Jim,
It should just be a matter of setting the URL in your web-app. In mine which is using GeoExt, I just set it to:
http://wppgeog3:8083/print/pdf
and make sure that URL is in my proxy and it works (its on a different machine, so no chance of localhost being used).
Jonathan
On 27 March 2013 19:16, Jim White <jbw2003@anonymised.com>wrote:
Hi,
I have installed the printing module, and have it sort of working from localhost, however when I try to access it from another IP I am redirected to
http://127.0.0.1:8080/geoserver/pdf/print.pdf
It looks like this has to do with printURL, and createURL in info.json. I use mod _proxy to access geoserver running on 8080. How do I set up my server to return the correct url and print from a computer other than localhost?
Thanks,
Jim
–
James B. White
Cary, NC
H: 919-380-9615
M: 919-698-1765
White Coding and Maps
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel’s independent game demo contest.
Compete for recognition, cash, and the chance to get your game
on Steam. $5K grand prize plus 10 genre and skill prizes.
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
Geoserver-users mailing list
Geoserver-users@anonymised.comts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
–
James B. White
Cary, NC
H: 919-380-9615
M: 919-698-1765
White Coding and Maps
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
–
James B. White
Cary, NC
H: 919-380-9615
M: 919-698-1765
White Coding and Maps
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
Stephen V. Mather