[OpenLayers-Users] Tiles outside maxExtent being loaded

[Eric Lemoine]

On Sun, Jun 1, 2008 at 3:53 PM, Christopher Schmidt
<crschmidt at metacarta.com> wrote:
> On Sun, Jun 01, 2008 at 02:10:46PM +0200, Eric Lemoine wrote:
>> On Fri, May 30, 2008 at 4:24 PM, Christopher Schmidt
>> <crschmidt at metacarta.com> wrote:
>> > On Fri, May 30, 2008 at 01:48:36PM +0100, Jon Blower wrote:
>> >> I've noticed that in my application OpenLayers is requesting tiles
>> >> outside the maximum extent of my overlay layer (which is in EPSG:4326
>> >> and hence has a maxExtent of -180,-90,180,90).  I've checked using the
>> >> Firebug console that the maxExtent is correctly set.  wrapDateLine is
>> >> set true.
>> >
>> > wrapDateLine forces displayOutsideMaxExtent, which is why you are seeing
>> > the behavior you are seeing.
>>
>> Chris, sorry for the stupid question but why does wrapDateLine force
>> displayOutsideMaxExtent? What would not function if one creates a
>> layer with wrapeDateLine:true and then does
>> layer.displayOutsideMaxExtent = false? One will end up with missing
>> tiles?
>
> The 'wrapped' tiles are, in actuality, still going from (for example)
> -360 to -180 in the 'mind' of OpenLayers. We just fake the *request*
> bbox, not the place the tile actually thinks of itself as being: without
> displayOutsideMaxExtent, this obviously wouldn't work.

I'm not familiar with the wrapdateline code, thanks for the explanation Chris.

Cheers,

--
Eric