<br><div class="gmail_quote">On Tue, Feb 2, 2010 at 3:34 PM, Wendell Turner <span dir="ltr"><<a href="mailto:wendell@enflight.com">wendell@enflight.com</a>></span> wrote:<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
<br>
</div>Is that done by listing the higher res layer items after the<br>
lower res itesm in the arguments to gdaltindex? </blockquote><div><br>Yes - draw order is from top to bottom in a map file. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">That appears<br>
to work, but is it loading tiles twice where the high res<br>
areas are?<br></blockquote></div><br>If you do not use a compound index, then yes (that's what Chris means by "paint over")<br><br>Either way you should still use MAXSCALEDENOM to stop the 250k images from being drawn at way zoomed out levels.<br>