id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
16844	Also include layers with a JPG option	naoliv	team	"I was thinking if we could offer an alternative for layers that could also be viewed in JPG.

For example, this DigitalGlobe Premium tile has a PNG version with 44K
https://a.tiles.mapbox.com/v4/digitalglobe.316c9a2e/16/24021/36857.png?access_token=pk.eyJ1IjoiZGlnaXRhbGdsb2JlIiwiYSI6ImNqZGFrZ2c2dzFlMWgyd2x0ZHdmMDB6NzYifQ.9Pl3XOO82ArX94fHV289Pg

But the same tile in JPG has 13K
https://a.tiles.mapbox.com/v4/digitalglobe.316c9a2e/16/24021/36857.jpg?access_token=pk.eyJ1IjoiZGlnaXRhbGdsb2JlIiwiYSI6ImNqZGFrZ2c2dzFlMWgyd2x0ZHdmMDB6NzYifQ.9Pl3XOO82ArX94fHV289Pg

We can have a file with only 29.5% of the PNG size, without any noticeable artifacts (PNG on left side, JPG on right side)
[[Image(https://i.imgur.com/5Pkdi9X.png)]]

I know that this is irrelevant for some people, but sometimes having a faster loading time, less bandwidth usage and (maybe) less disk space used (for caching) is a win.

What I thought: include some kind of information on every layer which could be viewed either in PNG or JPG + an option in `Imagery preferences` allowing the user to choose the format which they prefer (PNG or JPG).

Of course I could change all my local layers for this, but then I would lose any updates on them (an access token that was changed, for example)

Any comments about this, please?"	enhancement	new	normal		Core imagery			jpg png mirror	wiktorn Klumbumbus