[mapserver-dev] Vote for MS-RFC-55: Improve control of output resolution

[Brent Fraser]

Or we could add MS_FONTPOINTS as a unit and get rid of the user documentation confusion.

New User: "I changed my RESOLUTION to be 300 dpi so I could print my map, but the text is now too small!"

Experienced User: "Change/Set your LAYER's SIZEUNITS to FONTPOINTS and it will be the same size on the screen and on the printed map no matter what RESOLUTION value you choose."


I know, I know, I already made my pitch.. :)

Brent

Daniel Morissette wrote:
> Paul Spencer wrote:
>> how about RESOLUTION and OUTPUTRESOLUTION where RESOLUTION would be 
>> DEFRESOLUTION as defined in the RFC?
>>
> 
> Thought of that one too, but that would mean a change of meaning and 
> behavior for the existing RESOLUTION keyword. i.e. all apps that 
> currently use RESOLUTION would need to be adapted to use 
> OUTPUTRESOLUTION instead (in scripts or in URL params).
> 
> OTOH if we add a new keyword such as DEFRESOLUTION then existing apps 
> continue to pass/set resolution the same way. With the proposed 
> approach, the only change to existing apps may be to set DEFRESOLUTION 
> to be the same value as RESOLUTION if they do not wish to have the 
> symbology scaled, but that would be a very very rare case.
> 
> Daniel