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

• ...

Description

Some of the files refer in their JavaDocs blocks the old https://goworldwind.org site.

Additional Information

Encountered in e.g. the Cube example and TacticalSymbol class. Notably, also found in README.md. Such references should be substituted for current ones.

Today's JSON explanation var content:
"The Crab Nebula is cataloged as M1, the first on Charles Messier's famous lis"

The original text is much longer...

In the CMake documentation section about building deployments, the documentation references the command make check, which I cannot find the final CMake build. Perhaps it's a remnant from the past?

Summary of Issue

The docs and some visualizations reference the old names for inputs and outputs: params and unknowns. Need to remove all references to those in anything the user sees.

Issue Type

• Bug
• Enhancement

Description

Search the code for references to the terms unknown and params. Change to outputs and inputs.

No need to change code variables, et

Description

When the WMS and WMTS tutorials are first opened a longitudinally aligned artifact appears. Once the globe is moved it disappears. I was not able to recreate the artifact by moving the globe.

WMS:

WMTS:
![device-2018-02-01-170601](https://user-

currently the sphinx docs do not list all of the spice functions in the toc, adjust the toc depth in the docs may fix this issue.

• 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

We should add a page to the documentation describing the space weather methods for accessing / comparing indices, as well as one for the model_utils tools.

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

• desktop
• tablet
• pnone