Child of #699

Code should be more readable/'teachable'.

What are best practices? How long should examples be? Should they be similar to what we see in Android and Java?

Describe the bug
There are several places in the app where we have checkboxes that the labels are not configured properly to allow clicking to enable/disable the checkbox. We should identify all of these and fix them so that either the label or the checkbox can be clicked to update the value.

Known places:

• Tour dismiss checkbox

• Orbit tracks toggle in layer info modal

• ...

• Document build process using rollup (module -> umd)
• Using bare module specifications so they cannot be natively imported
• Scripts include THREE example files, which are not module-compliant, so a helper loader will used until then.

It appears that imagery in GeoPackage exported from GeoServer is shifted to the right by one pixel when compared to the source imagery. Compare the following are two zoomed-in screenshots from QGIS that illustrate the issue:

Source Image

_Figure 1. Source GeoTiff image viewed in QG

Review all uses of the imageryDetail to ensure the best resolution imagery is being displayed for the various platforms:

• desktop
• tablet
• pnone