Thanks for bringing that context back to the discussion (I somehow missed it arriving partway along in the discussion).
I am interested in seeing this happen as: - it is not wms specific - we run into this issue when printing from uDig - it really is not wms specific; we are starting to run into this issue when working with different displays - I really don't want to see applications getting in the habit of hacking around the renderer; or we will end up maintaining hacks in a number of different places (my recent experience with the GML parsing really underscores this point for me) So this dpi setting is needed and seems fine. Andrea with renderer becoming aware of dpi - would we be able to retire the rescale style visitor (which uDig is using to hack around this problem currently)? Jody On 17/06/2010, at 8:50 PM, Andrea Aime wrote: > Ok, > the discussion about DPI and rescaling did not exacly go well... > Jody suggested that my second attempt on GeoServer mailing list > (which basically suggests to do the work only on the server side) > is clearer in terms of explanations so... let me paste it here as well: > > --------------------------------------------------------------- > > Hi, > I have someone interested in sponsoring better support for > raster printouts on high resolution devices. > > Basically they want to generate an image that when printed > at 300dpi will look like what you get on the screen, which > really means you need: > - a bigger image > - scaled up labels, strokes and whatnot > - the scale computation taking into account the scale up > and ending up with the same scale denominator as the > image on the screen > > This is how MapServer is doing it: > http://mapserver.org/development/rfc/ms-rfc-55.html > > So they state the image size and the target dpi separately. > Seems like a sane way to proceed to me. > > --------------------------------------------------------------- > > DeeGree and MapGuide also support this rescaling approach > using terms like resolution and dpi again: > > http://trac.osgeo.org/mapguide/wiki/HttpApi/RenderingService#SetDisplayDpi1.0 > http://download.deegree.org/deegree2.1/api/org/deegree/ogcwebservices/wmps/configuration/PrintMapParam.html#getTargetResolution%28%29 > > I understand this is quite WMS oriented... so if people don't > think it's a good idea to implement it in the rendering subsystem > straight I'll just rescale the styles in GeoServer when setting > up the map context and leave GeoTools untouched. > > Otherwise the idea is to have the client code pass the dpi as > a rendering hint, and apply the RescaleStyleVisitor > using targetdpi/ogcdpi as the scale factor right after the > uom rescaling has happened (and regardless of whether there > is a uom rescaling or not). > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Geotools-devel mailing list > Geotools-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
