[mapserver-commits] r8787 - trunk/docs/development/rfc

[svn at osgeo.org]

Author: dmorissette
Date: 2009-03-12 15:25:30 -0400 (Thu, 12 Mar 2009)
New Revision: 8787

Modified:
   trunk/docs/development/rfc/ms-rfc-55.txt
Log:
Added mapfile fragments in usage examples

Modified: trunk/docs/development/rfc/ms-rfc-55.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-55.txt	2009-03-12 18:17:25 UTC (rev 8786)
+++ trunk/docs/development/rfc/ms-rfc-55.txt	2009-03-12 19:25:30 UTC (rev 8787)
@@ -80,11 +80,38 @@
 Let's say we've got a mapfile that we use to produce a 400x400 pixels
 image for use on the Web, with both defresolution and resolution set to 72.
 
+::
+
+  MAP
+    ...
+    RESOLUTION 72
+    DEFRESOLUTION 72
+    SIZE 400 400
+    ...
+  END
+
+
 In order to produce a 300dpi image for printing, the application code
 should request an image of 1667 x 1667 pixels (400*300/72=1667) and set
 resolution=300. MapServer will automagically scale all symbology sizes
 by a factor of 300/72=4.1667.
 
+The new values of size and resolution for printing will likely be passed
+as URL parameters in most applications, but for the purpose of this example,
+expressed in mapfile syntax then we'd use the following mapObj settings 
+for printing:
+
+::
+
+  MAP
+    ...
+    RESOLUTION 300
+    DEFRESOLUTION 72
+    SIZE 1667 1667
+    ...
+  END
+
+
 Example 2:
 
 An application is using a mapfile developed for map.resolution=96 with