[OpenLayers-Dev] Format.WMC and scale

[bartvde at osgis.nl]

Hi Eric,

> On your side have you figured out why the calculated minScale is
> different than the minScale value in the options?

Yes, I believe this happens when there is only a minscale or maxscale, so
not both. In WMC you can have only a MinScaleDenominator or a
MaxScaleDenominator.

> Regarding WMC, I think it makes that WMC write uses layer.minScale.
> Indeed, we need to deal with cases where the layer wasn't built out of
> WMC and no minScale option was set in the layer.

Right, that makes sense, I understand the reasoning now. Thanks.

Best regards,
Bart

> Hi Bart
>
> We've also experienced unexpected minScale/maxScale values here at
> Camptocamp. So far we haven't had a chance to investigate the problem.
> On your side have you figured out why the calculated minScale is
> different than the minScale value in the options?
>
> Regarding WMC, I think it makes that WMC write uses layer.minScale.
> Indeed, we need to deal with cases where the layer wasn't built out of
> WMC and no minScale option was set in the layer.
>
> Eric
>
> 2008/10/23, bartvde at osgis.nl <bartvde at osgis.nl>:
>> Hi list,
>>
>> question about the Format.WMC code.
>>
>> When it reads a scale from a WMC doc, it is stored in the options array
>> of
>> the layer.
>>
>> But when it writes, it uses the minScale or maxScale property of the
>> layer.
>>
>> Why is this? I would expect when writing to also use the
>> options.minScale
>> and options.maxScale.
>>
>> In my situation options.minScale is 35000 (the correct value) and
>> layer.minScale is 10000000.999999998, don't ask me why :-). So when
>> serializing the WMC the wrong information is written.
>>
>> Best regards,
>> Bart
>>
>> _______________________________________________
>> Dev mailing list
>> Dev at openlayers.org
>> http://openlayers.org/mailman/listinfo/dev
>>
>