[mapserver-dev] RFC-86: scale dependant DATA substitutions

[thomas bonfort]

On Mon, Oct 8, 2012 at 4:41 PM, Stephen Woodbridge
<woodbri at swoodbridge.com> wrote:
> On 10/8/2012 9:02 AM, thomas bonfort wrote:
>>
>> Devs,
>>
>> Please take a look and comment on
>>
>> http://mapserver.org/trunk/development/rfc/ms-rfc-86.html
>
>
> Hi Thomas,
>
> Thanks, this looks like an excellent implementation to address the need I
> identified in bug #3150.
>
> I'm a little confused with your first example in the RFC, you have:
>
>   SCALETOKEN
>     NAME "foobar"
>     VALUES
>       "1000" "1000"
>       "10000" "10000"
>       "1000000" "1000000"
>     END
>   END
>
> But the discussion reference 5500, 505000. So that should be cleared up so
> it is more understandable.
Steve,
what this meant is that given the current requested scale, mapserver
will select the closest defined scaletoken. In the example here,
0=>5500 uses the 1000 value
5500=>505000 uses 10000
505000 and up uses 1000000

I agree, not very clear... you should only consider the first entry,
the second one isn't interpreted and is just used as the replacement
for the token

>
> Thanks,
>   -Steve W
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev