[OpenLayers-Users] Scale Control rounding low-valued scales

[Stuart Eve]

Hi Christopher

Thanks for the reply,

 From our point of view we deal with digitised archaeological plans 
which are sometimes drawn at 1:20 or 1:10 (we are using metres as the 
units not centimetres). Therefore rounding to the nearest integer for 
scale is totally fine for us - it would be nice I guess to get right 
down to 1:1! Can you explain why the browser isn't the best for 
centimetre accuracy? The MousePosition control seems to work well and I 
have checked the coordinates of various features against my desktop GIS 
and it seems right on... In fact Openlayers is working really well 
(except for the scale read-out) we are loving it!

Stuart

Christopher Schmidt wrote:

>Stuart Eve posted ticket 503 this morning:
>  OpenLayers.Control.Scale doesn't seem to read correct scale below 1:500
>
>The problem is that any scale value less than 9500 is rounded to the
>nearest hundred. It's clear to me that rounding to the nearest hundred
>is not really neccesary: the numbers displayed will be the same length
>whether they are or aren't (or close to it, anyway).
>
>However, Stuart points out that he needs 'centimetre accuracy'. Ignoring
>the fact that the browser is probably not the best environment for
>centimetre accuracy, I'm wondering what scale level we need to support
>down to: Is rounding the scale to the nearest integer enough accuracy?
>I'd obviously say yes, but I work on scales of 1:443M, not on scales of
>1:100.
>
>Can someone educate me: what do users expect when they set a scales
>array of:
>  [105, 10.5, 1.05]
>?
>
>Stuart, I suppose this is directed mostly at you, since you're the one
>who opened the bug report.
> 
>Regards, 
>  
>