<div dir="ltr">Thanks, Brent.  Looking back, the TIFF is 20GB because it's actually extents about 1.8x beyond the municipal boundary, so your original math bears out.  I'd be looking at ~32GB for the resulting level 11-20 tiles.<div>
<br></div><div>Thanks,</div><div style>  Paul</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 29, 2013 at 12:31 PM, Brent Fraser <span dir="ltr"><<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>Remember my PNG tiles are compressed. 
      And my estimate (based on my Landsat experience) is that if you
      tiled (into compressed PNGs) your 20GB (why isn't it 12.5 GB?),
      the resulting levels 11 thru 20 would be a total of about 20GB.<br>
      <pre cols="72">Best Regards,
Brent Fraser</pre><div><div class="h5">
      On 1/29/2013 11:25 AM, Paul Wickman wrote:<br>
    </div></div></div>
    <blockquote type="cite"><div><div class="h5">
      <div dir="ltr">Ok.  So, my 20 GB uncompressed TIFF image would
        come in at roughly 26 GB tiled?  Is that per tile level?  This
        number is an order of magnitude smaller than Brent's math.
        <div><br>
        </div>
        <div>Sorry if I'm not being clear.....</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Tue, Jan 29, 2013 at 11:41 AM,
          Basques, Bob (CI-StPaul) <span dir="ltr"><<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div link="blue" vlink="purple" lang="EN-US">
              <div>
                <p class="MsoNormal"><span>Paul,</span></p>
                <p class="MsoNormal"><span> </span></p>
                <p class="MsoNormal"><span>We’ve been building these here at the City
                    for a number of years now.  Using a halving of
                    resolution for each new level.</span></p>
                <p class="MsoNormal"><span> </span></p>
                <p class="MsoNormal"><span>Generally, the space requirements will end
                    up at approximately 1.333 times the size of the
                    original data.  Assuming you aren’t trying to
                    interpolate pixels at the bottom level of course. 
                    Also, the bottom level should be roughly equal in
                    size to the original data being tiled, since the
                    data isn’t really changing, but rather only being
                    chunked up into smaller pieces.   Each new level
                    decreases in size to  approximately  1/4<sup>th</sup>
                    the previous with regard to tile numbers, and the
                    individual tiles will be roughly the same size
                    across all levels of the pyramid.</span></p>
                <p class="MsoNormal"><span> </span></p>
                <p class="MsoNormal"><span>Bobb</span></p>
                <p class="MsoNormal"><span> </span></p>
                <p class="MsoNormal"><span> </span></p>
                <p class="MsoNormal"><span> </span></p>
                <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
                  <div>
                    <div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
                      <p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
                          <a href="mailto:geomoose-users-bounces@lists.osgeo.org" target="_blank">geomoose-users-bounces@lists.osgeo.org</a>
                          [mailto:<a href="mailto:geomoose-users-bounces@lists.osgeo.org" target="_blank">geomoose-users-bounces@lists.osgeo.org</a>]
                          <b>On Behalf Of </b>Paul Wickman<br>
                          <b>Sent:</b> Monday, January 28, 2013 6:53 PM<br>
                          <b>To:</b> <a href="mailto:geomoose-users@lists.osgeo.org" target="_blank">geomoose-users@lists.osgeo.org</a><br>
                          <b>Subject:</b> [Geomoose-users] Estimating
                          tile size</span></p>
                    </div>
                  </div>
                  <div>
                    <div>
                      <p class="MsoNormal"> </p>
                      <div>
                        <p class="MsoNormal">Greetings,</p>
                        <div>
                          <p class="MsoNormal"> </p>
                        </div>
                        <div>
                          <p class="MsoNormal">I know this type of
                            question goes around often in various
                            flavors.  Difficult to estimate exact size
                            of rendered tiles, but thought I'd try to
                            get some opinions.</p>
                        </div>
                        <div>
                          <p class="MsoNormal"> </p>
                        </div>
                        <div>
                          <div>
                            <p class="MsoNormal">I see this questions
                              asked in a variety of ways and I know it's
                              not exactly precise on how to get the
                              answer, but I'll throw my question out to
                              see what I get ;)</p>
                          </div>
                          <div>
                            <p class="MsoNormal"> </p>
                          </div>
                          <div>
                            <p class="MsoNormal">We have a client who
                              would like us to tile and serve up
                              high-resolution aerial photography that
                              they own. The area is about 800 square
                              miles and the imagery is 6-inch
                              resolution. They'd like to be able to view
                              the imagery at zoom levels 11 through 20
                              (with level 20 being 1 pixel=6 inches). Is
                              there any way at all to determine how
                              large a resulting raster tile set might
                              be?</p>
                          </div>
                          <div>
                            <p class="MsoNormal"> </p>
                          </div>
                          <div>
                            <p class="MsoNormal">Many thanks,</p>
                          </div>
                          <div>
                            <p class="MsoNormal">  Paul</p>
                          </div>
                          <div>
                            <div>
                              <p class="MsoNormal"> </p>
                            </div>
                            <p class="MsoNormal">-- <br>
                              Paul Wickman<br>
                              CTO | Flat Rock Geographics<br>
                              <a href="tel:612.280.5850" value="+16122805850" target="_blank">612.280.5850</a>
                              | <a href="mailto:paul@flatrockgeo.com" target="_blank">paul@flatrockgeo.com</a><br>
                              <a href="http://www.flatrockgeo.com" target="_blank">www.flatrockgeo.com</a>
                              | <a href="http://twitter.com/flatrockgeo" target="_blank">
                                twitter.com/flatrockgeo</a> </p>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        Paul Wickman<br>
        CTO | Flat Rock Geographics<br>
        <a href="tel:612.280.5850" value="+16122805850" target="_blank">612.280.5850</a> | <a href="mailto:paul@flatrockgeo.com" target="_blank">paul@flatrockgeo.com</a><br>
        <a href="http://www.flatrockgeo.com" target="_blank">www.flatrockgeo.com</a> | <a href="http://twitter.com/flatrockgeo" target="_blank">twitter.com/flatrockgeo</a>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><div class="im"><pre>_______________________________________________
Geomoose-users mailing list
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a>
</pre>
    </div></blockquote>
    <br>
  </div>

</blockquote></div><br><br clear="all"><div><br></div>-- <br>Paul Wickman<br>CTO | Flat Rock Geographics<br>612.280.5850 | <a href="mailto:paul@flatrockgeo.com" target="_blank">paul@flatrockgeo.com</a><br><a href="http://www.flatrockgeo.com" target="_blank">www.flatrockgeo.com</a> | <a href="http://twitter.com/flatrockgeo" target="_blank">twitter.com/flatrockgeo</a>
</div>