Optimized processing of encoded tile data on the Garmin OneHelm Canyon Runner app by utilizing onboard proxy server caching capabilities. Reducing cursor and touch event listener counts, offloading data-storage off the device to continue working within the 150MB memory limit, and targeted-access of per-pixel data to return the SST/CHL reading from a WMS PNG tile on click. Utilized a new local performance tracking server to track performance optimization change effects on the device.

Garmin OneHelm <--> Proxy Server <--> HTTP Requests

What's in the encoded data?

Depends! We can store sea surface temperature readings, chlorophyll concentrations, salinity, and so on. So basically, just raw data. We process satellite files from known databanks to create mapping tiles with this data so we can decode them on the front-end. We have 3 channels of 8-bit data to work with, so if we're trying to store, say, the logarithmic-scaling dataset for Chlorophyll concentrations, we can normalize the single concentration value to 24-bits before we distribute those bits across each 8-bit channel.