That's the error you get when a request is made to geowebcache which does not conform to the tile grid. I guess we will have to update mapfish to respect the tile grid we use in order for this to work. I think it could also be done by careful manipulation of the print request, but it would probably be nicer for the server to do this correction itself when the tiling extensions are advertised in the capabilities document.
-- David Winslow OpenGeo - http://opengeo.org/ On Sun, Jun 19, 2011 at 10:05 PM, Ariel Nunez <[email protected]>wrote: > Hello again people, > > In the GeoNode we are setting up I had to enable printing too. I am > using the excellent bluemarble background hosted at maps.opengeo.org > but get the following error when trying to print with it: > > {{{ > java.io.IOException: Error (status=400) while reading the image from > > http://maps.opengeo.org/geowebcache/service/wms?BBOX=2905846.0%2C-748348.3%2C5389401.5%2C1977918.5&HEIGHT=4025&WIDTH=3667&map_resolution=600&VERSION=1.1.1&FORMAT=image%2Fpng&TILED=true&SERVICE=WMS&format_options=dpi%3A600&LAYERS=bluemarble&REQUEST=GetMap&STYLES=&TILESORIGIN=-20037508.34%2C-20037508.34&SRS=EPSG%3A900913 > : > Bad Request > }}} > > Copying the request directly to the browser gives the following: > > 400: X,Y values for the tile index were calculated to be > {9.160162611315974, 7.70122101518736} which had to be rounded to {9, > 8} and exceeds the threshold of 10%. Perhaps the client is using the > wrong origin ? > > Thanks in advance for any insight you may have on the origin of the error. > > Ariel. > > PS: > The images from the local GeoNode come nicely (except for some reason > the labels are not shown): > > [1] How it looks in the composer: > http://cl.ly/0Q1Q2e3D0y3x1b1h3v1M > > [2] How it looks in the PDF: > http://cl.ly/1c210P090f091q072P0D >
