<div dir="ltr"><div>Hello Mark,<br><br>thanks, we will try Mapcache until new Openlayers version is completed.<br><br></div>Regards,<br>Matej Serc<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/3/5 Mark Volz <span dir="ltr"><<a href="mailto:MarkVolz@co.lyon.mn.us" target="_blank">MarkVolz@co.lyon.mn.us</a>></span><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 style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hello,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I think this has more to do with Openlayers, which GeoMOOSE uses to display maps on the client side. GeoMOOSE uses Openlayers 2.x, which to my knowledge, does
not load load tiles in this way. I think the next version of Openlayers, which is in development will subsample existing tiles so that there is never any white space on the map. I don’t remember what the presentation is called, however I think it is on youtube.
In the meantime I have been quite satisfied with mapcache, which is included with some Mapserver installations. It takes about 16ms to 100ms to serve tiles.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark Volz<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">GIS Specialist<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></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>Matej Mailing<br>
<b>Sent:</b> Tuesday, March 05, 2013 7:41 AM<br>
<b>To:</b> Paul Wickman</span></p><div><div class="h5"><br>
<b>Cc:</b> <a href="mailto:geomoose-users@lists.osgeo.org" target="_blank">geomoose-users@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [Geomoose-users] Estimating tile size<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">Hi,<br>
<br>
this is almost like spamming, but it is related to the issue: Google Maps for example shows very rough rasters when zooming and then loads more details when you stop zooming or moving. We also have a number of installations where such raster's display (first
rough and then detailed) would be very useful. Can this be done with GM and perhaps more Mapserver?<br>
<br>
Thanks,<u></u><u></u></p>
</div>
<p class="MsoNormal">Matej<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">2013/1/30 Paul Wickman <<a href="mailto:paul@flatrockgeo.com" target="_blank">paul@flatrockgeo.com</a>><u></u><u></u></p>
<div>
<p class="MsoNormal">Thanks for the spreadsheet, Jim. That helps a lot.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Wed, Jan 30, 2013 at 10:07 AM, James Klassen <<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">I'd guess is in JPEGs you are looking at ~23GB and about 346GB uncompressed for all levels. The top level (most pixels) will be ~2/3 the size of all of the levels combined. I've attached a spreadsheet (ODS) that I've worked up to estimate
tile sizes. (My guess is it will get blocked by the list, so if anyone is interested email me.)<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Which tool you use kind of depends on how you plan on serving it. Direct from MapServer has a different optimization strategy than if you are using MapCache or MapProxy. I'm not sure how portable the tools I worked on are. The one I
did at the city was all in C and was essentially a modified shp2img with the tile calculation added and some extra stuff removed. What I am using now is ruby based and relies on PostGIS for indexes and MapServer for rendering. The net result is the same
though.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">The big thing quality wise it to be sure to use -r average (GDAL) or PROCESSING "RESAMPLE=AVERAGE" (mapserver) so the zoomed out levels aren't all speckled as happens when using the default nearest neighbor sampling.<u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">On Tue, Jan 29, 2013 at 1:25 PM, Basques, Bob (CI-StPaul) <<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Paul,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">The fastest approach has and seems to still be using MapServer to generate the tiles, via a script. Jim K. has even verified
this within the last couple of weeks, since he tried improving on the original system we used here and came back to it in the end with some minor upgrades.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">It doesn’t really matter how you get there, even if it takes a little longer. I think there are some MapServer utilities
that we used originally on this layer. You may want to experiment for yourself on what works best for what.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Also, in our experience, we’ve had best results using Jpeg (NOT JPEG2000!!) for aerials and PNGs for overlay tiles.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Bobb</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></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""> Paul Wickman [mailto:<a href="mailto:paul@flatrockgeo.com" target="_blank">paul@flatrockgeo.com</a>]
<br>
<b>Sent:</b> Tuesday, January 29, 2013 1:18 PM<br>
<b>To:</b> Basques, Bob (CI-StPaul)<br>
<b>Cc:</b> Brent Fraser; <a href="mailto:geomoose-users@lists.osgeo.org" target="_blank">
geomoose-users@lists.osgeo.org</a></span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><br>
<b>Subject:</b> Re: [Geomoose-users] Estimating tile size<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">Thank you kindly, Bob. Did you use gdal2tiles.py or is there another utility you like better?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <u></u><u></u></p>
<div>
<p class="MsoNormal">On Tue, Jan 29, 2013 at 1:08 PM, Basques, Bob (CI-StPaul) <<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Paul,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">For reference, I’m looking at a layer here for the City, about 56sq mi coverage at 6in pxels. Using Jpeg tiles, 1000x1000pxels
(500x500 ground units).</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Keep in mind that the City is not a rectangle . . . but the levels break down like so:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">(L0) ~27,000 tiles = 1.5 GB</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">(L1) ~ 4500 tiles = 420MB</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">(L2) ~ 1140 Tiles = 123MB</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">(L3) ~ 293 tiles = 35MB</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">(L4) ~ 83 tiles = 9.4MB</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">(L5) ~ 28 tiles = 2.5MB</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">These were generated from MRSID files originally, so I can’t give you a number on disksize, since MRSIDs are basically
compiled Pyramids to begin with. I have some other layers that started as flat rasters such as your TIFFs if you want me to put something together for those, let me know.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Bobb</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""> </span><u></u><u></u></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> Tuesday, January 29, 2013 11:28 AM<br>
<b>To:</b> Brent Fraser<br>
<b>Cc:</b> <a href="mailto:geomoose-users@lists.osgeo.org" target="_blank">geomoose-users@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [Geomoose-users] Estimating tile size</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">Yes, bytes. Zowie... I have a TIFF of an air photo for one of our other municipalities (also 6-inch resolution), which is 20 GB (uncompress). That coverage is only ~40 square
miles. So, for a single ~800 square mile county also at 6-inch resolution I'd potentially be looking at 400 GB for the uncompressed source or... somewhere on the order of ~800 GB tiled? Does that sound right?<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Anybody from MnGeo on this list with any input?<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <u></u><u></u></p>
<div>
<p class="MsoNormal">On Tue, Jan 29, 2013 at 11:15 AM, Brent Fraser <<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Do you mean how many bytes?<br>
<br>
Looking at my Landsat tile pyramids (levels 4 to 12), they're about the same number of bytes (hmm, I expected them to be double...)<br>
<br>
But my source images:<br>
- no compression on existing files (tiffs, e.g not jpeg)<br>
- 3 band (color) imagery<br>
<br>
The resulting tiles:<br>
- compressed PNGs<br>
- four bands (one alpha channel for transparency)<br>
<br>
So my guess is somewhere between "same size" to "double the number of bytes" (unless the source imagery is compressed, then it will be 5 to 10 times larger)<u></u><u></u></p>
<pre>Best Regards,<u></u><u></u></pre>
<pre>Brent Fraser<u></u><u></u></pre>
<div>
<div>
<p class="MsoNormal">On 1/28/2013 5:53 PM, Paul Wickman wrote:<u></u><u></u></p>
</div>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">Greetings,
<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></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 ;)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></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?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Many thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> Paul<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal">--
<br>
Paul Wickman<br>
CTO | Flat Rock Geographics<br>
<a href="tel:612.280.5850" 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> <u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <u></u><u></u></p>
</div>
</div>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>Geomoose-users mailing list<u></u><u></u></pre>
<pre><a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><u></u><u></u></pre>
<pre><a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><u></u><u></u></pre>
</blockquote>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal">--
<br>
Paul Wickman<br>
CTO | Flat Rock Geographics<br>
<a href="tel:612.280.5850" 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> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal">--
<br>
Paul Wickman<br>
CTO | Flat Rock Geographics<br>
<a href="tel:612.280.5850" 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> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <br>
Paul Wickman<br>
CTO | Flat Rock Geographics<br>
<a href="tel:612.280.5850" 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> <u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</div>
</blockquote></div><br></div>