<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 22, 2016 at 9:51 PM Cechini, Matthew F. (GSFC-423.0)[Science Systems & Applications, Inc.] <<a href="mailto:matthew.f.cechini@nasa.gov">matthew.f.cechini@nasa.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">A compelling situation could be a layer that has uses cases where you want it have transparency or not, making it an “overlay” or “base layer” respectively.</div></div></div></div></blockquote><div>In theory that would be a use case. In practice, I doubt that you would be using the exact same layers in an overlay or in a base layer. Plus you would probably want to use a different wms <source> in order to include the TRANSPARENT=ON|OFF KVP parameter. I.e. you need distinct tileset definitions.</div><div>Supposing the previous limitations do not apply to you (i.e. you use exact same layers in overlay or basemap, and you always set TRANSPARENT=ON in your source (letting mapcache set your transparent background to black when saving as jpeg)), you'd get an advantage by supporting both jpeg and png only if the jpeg tile file sizes are significantly smaller than the png ones, and that the network bandwidth you plan to spare with that offsets the cost of having to store all your tiles twice.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"> </div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Though, if you’re serving it as 24+1bit PNG with transparency, you’re gonna lose quality in JPEG, so you would probably want to return a 24bit PNG. And at that point, you would have to have separate layers because the mime type is the same.</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">As an aside, a member of our team did work on a JPNG approach where tiles that require transparency are PNG and those that do not are JPEG. The devil is in the details of quality mapping with that though.</div></div></div></div></blockquote><div>Mapcache supports JPNG (called "mixed" in mapcache terms) since 2012. Should that support not have been available, support for both jpeg and png for a single tileset would make more sense.</div><div><br></div><div>--</div><div>thomas</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Matt</div>
<div class="gmail_msg">
<div class="gmail_msg">.................................................................</div>
<div class="gmail_msg"><span class="m_1152247041694255238Apple-style-span gmail_msg" style="font-family:'Lucida Grande'"><span style="font-size:11pt" class="gmail_msg">Matthew Cechini</span></span></div>
<div class="gmail_msg"><span style="font-size:13px;font-family:'Lucida Grande'" class="gmail_msg">Contractor, Science Systems and Applications, Inc.</span></div>
<div class="gmail_msg"><span style="font-size:10pt;font-family:'Lucida Grande'" class="gmail_msg">NASA GIBS Systems/Software Engineer</span></div>
<div class="gmail_msg"><span class="m_1152247041694255238Apple-style-span gmail_msg" style="font-family:'Lucida Grande'"><font size="2" class="gmail_msg"><span style="font-size:10pt" class="gmail_msg">410.205.6272</span></font></span></div>
</div>
</div>
</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<span id="m_1152247041694255238OLK_SRC_BODY_SECTION" class="gmail_msg">
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt" class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">From: </span>mapserver-users <<a href="mailto:mapserver-users-bounces@lists.osgeo.org" class="gmail_msg" target="_blank">mapserver-users-bounces@lists.osgeo.org</a>> on behalf of thomas bonfort <<a href="mailto:thomas.bonfort@gmail.com" class="gmail_msg" target="_blank">thomas.bonfort@gmail.com</a>><br class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">Date: </span>Tuesday, November 22, 2016 at 1:28 PM<br class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">To: </span>tellett <<a href="mailto:thomas.ellett@statkart.no" class="gmail_msg" target="_blank">thomas.ellett@statkart.no</a>>, "<a href="mailto:mapserver-users@lists.osgeo.org" class="gmail_msg" target="_blank">mapserver-users@lists.osgeo.org</a>" <<a href="mailto:mapserver-users@lists.osgeo.org" class="gmail_msg" target="_blank">mapserver-users@lists.osgeo.org</a>><br class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">Subject: </span>Re: [mapserver-users] Mapcache support for multiple format types<br class="gmail_msg">
</div></span></div><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif" class="gmail_msg"><span id="m_1152247041694255238OLK_SRC_BODY_SECTION" class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div dir="ltr" class="gmail_msg">
<div dir="ltr" class="gmail_msg">Hi Tom,
<div class="gmail_msg">My question wasn't clear, or you did not answer my question ;-)</div>
<div class="gmail_msg">I was looking for a compelling *use-case* where the solution requires a tile server to support both jpeg and png for a given tileset. My stance for mapcache is that the data producer (i.e. you as the mapcache administrator) knows his
data and therefore which format (*singular*) is best suited for a given tileset. I'd be happy to revisit my judgment if presented with a scenario where more than one format per tileset is actually needed.</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Cheers,</div>
<div class="gmail_msg">Thomas</div>
</div>
<br class="gmail_msg">
<div class="gmail_quote gmail_msg">
<div dir="ltr" class="gmail_msg">On Tue, Nov 22, 2016 at 12:19 PM tellett <<a href="mailto:thomas.ellett@statkart.no" class="gmail_msg" target="_blank">thomas.ellett@statkart.no</a>> wrote:<br class="gmail_msg">
</div>
<blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Thomas,<br class="gmail_msg">
<br class="gmail_msg">
Really, its just so that we don't need to have 2 separate layers in the<br class="gmail_msg">
service for each format type. The norwegian mapping authority has about 25<br class="gmail_msg">
cache 'services' and so its a bit messy in the config and WMTS capabilities<br class="gmail_msg">
file if we have to have 50 tilesets instead of 25.<br class="gmail_msg">
<br class="gmail_msg">
Its no problem technically having 2 tilesets called 'topo2_png' and<br class="gmail_msg">
'topo2_jpeg' for example (they would have the same title and abstract), it<br class="gmail_msg">
just would have been preferable for us to have 1 layer support multiple<br class="gmail_msg">
formats so that the client could call the same service/layer/tileset and<br class="gmail_msg">
choose the format type through the kvp parameter. Not a show-stopper for us,<br class="gmail_msg">
we just have to change our way of thinking :)<br class="gmail_msg">
<br class="gmail_msg">
Tom<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/Mapcache-support-for-multiple-format-types-tp5296486p5296917.html" rel="noreferrer" class="gmail_msg" target="_blank">
http://osgeo-org.1560.x6.nabble.com/Mapcache-support-for-multiple-format-types-tp5296486p5296917.html</a><br class="gmail_msg">
Sent from the Mapserver - User mailing list archive at Nabble.com.<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
mapserver-users mailing list<br class="gmail_msg">
<a href="mailto:mapserver-users@lists.osgeo.org" class="gmail_msg" target="_blank">mapserver-users@lists.osgeo.org</a><br class="gmail_msg">
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a></blockquote>
</div>
</div>
</div>
</div>
</span></div></blockquote></div></div>