Daniel,<br><br>I would introduce a new parameter of the map called 'magnification' which would be multiplied with the resolution when calculation the scale. In addition the scalefactor should also multiplied with this in msPrepareImage to achieve the desired effect.<br>
I guess it wouldn't be annoying for the user that by setting magnification = 2.0 would increase the width of the map elements 2 times. <br>magnification = 1.0 would be the default value.<br><br><br>Best regards,<br><br>
Tamas<br><br><br> <br><br><br><div class="gmail_quote">2009/2/11 Daniel Morissette <span dir="ltr"><<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dev's,<br>
<br>
When using MapServer to generate a printable map at higher resolution than the default screen resolution, say 300dpi instead of 72dpi, it is not sufficient to update the map->resolution setting since all the label and symbol sizes as well as line widths also need updating if you want to maintain the same map appearance.<br>
<br>
This issue has been discussed a few times before and I even think some have worked on this at their end. We have a client who needs a fix for this so I'd like to open a discussion on this before we go ahead and prepare a RFC.<br>
<br>
The approach I was thinking of using is to add a new map->defresolution (better names welcome) that would be the default resolution of a given mapfile, that is the reference resolution for which all sizes in labels, classes and styles are set.<br>
<br>
In normal web browsing operation, map->defresolution should be set to the same value as map->resolution (e.g. 72dpi). When you want to print a 300dpi map, then you'd set map->resolution=300, and MapServer would automagically apply a factor of map->resolution/map->defresolution to all size values in the mapfile before rendering. For instance, if your mapfile is set for a defresolution of 72dpi and you request a output resolution of 300dpi, all size values would be multiplied by 300/72=4.16 and labels, lines and symbols on the resulting map would have the same/expected relative sizes.<br>
<br>
I think I've read suggestions of setting resolution as an outputformat option before, but this may not work well with remote (e.g. WMS) services, we need something better integrated and with the proposed approach just passing a new vendor-specific resolution param in the WMS GetMap URL could do the trick.<br>
<br>
Does my explanation make sense? Has anyone worked on this problem already? Any thoughts on this before we start working on a RFC?<br>
<br>
Daniel<br><font color="#888888">
-- <br>
Daniel Morissette<br>
<a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</font></blockquote></div><br>