Hi. It looks like that if you set minScale/maxScale OpenLayers takes it as "calculate the intermediate resolutions". I cannot think of something better than pass your layer a scale array. I may be missing it though. Cheers. Eric
2008/9/8, Alexandre Dube <[EMAIL PROTECTED]>: > Hi everybody, > > I need some explanations regarding minScale/maxScale with 'scales' > array set on map, please. > > Release/2.7/Note > Layer : > minScale' and 'maxScale' properties no longer ignored if 'scales' > array set on map. (#1199 <http://trac.openlayers.org/ticket/1199>) > > Yeah, they are not ignored, but only both theses scales correspond the > actual map scales, not the ones between them. > > For example, I have the following scales set for my map : > > scales: [13000000, 8000000, 4000000, 2000000, 1000000, 500000, 250000, > 100000, 50000, 25000, 10000] > > If I set minScale: 1000000, maxScale: 100000 to a layer and then check > its scales array, I get the following : > index : value > 0 : 1000000.0000000001 > 1 : 464158.8833612779 // instead of 500000 > 2 : 215443.46900318837 // instead of 250000 > 3 : 99999.99999999999 > > I can understand how theses values are set this way. > I don't know why they do. > Are the values ok ? Will this affect anything ? ( because they are > different than the scales from the map ) > I don't understand why the layer could not have the values in the scales > array of the map directly instead of calculating its own... > > Sorry for the long e-mail. I only need some explanations, please. > > -- > Alexandre Dubé > Mapgears > www.mapgears.com > > _______________________________________________ > Users mailing list > [email protected] > http://openlayers.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
