<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hello again,<br>
<br>
I am reading over some of the documentation and information I can find on GDAL. <br>
<br>
I have some pretty large NITF images that I want to break up for purposes of displaying in a viewer I am developing. My current plan is to tile the images into 1024x1024 blocks. The full images are 32768x32768 pixels<br>
<br>
I was hoping that as part of my tiling, I would read in the image blocks and display them as they are on disk, and as a user zoomed out, switch to "Less detailed" versions the further out they go.<br>
<br>
I was looking at the gdaladdo sample program. Is this what I want to be looking at to try to replicate this functionality *in memory* for my viewer? Ideally all of the tiles would know what level of zoom they were at, and switch to the appropriate level of
detail accordingly. <br>
<br>
Does it sound feasible to have my code constantly switching each tile between an overview that is generated on the fly like that, or do people typically write out the lower res imagesonce to file , and re-read that new files?<br>
<br>
Thanks for answering!<br>
<br>
Derek<br>
</div>
</body>
</html>