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

• ...

For any developers who want to develop custom supplements, they need to have a src subdirectory, some C codes, and most importantly, a CMakeLists.txt file.

Here is a full list of all CMake settings that can be included in the CMakeLists.txt:

# SUPPL_NAME [required]
#	name of the supplement package. It can be different from the directory name.
set (SUPPL_NAME newsuppl1)

# SUPPL_PROGS_

From the eagle-eyed @jonseddon 🦅 👁 :

"I just noticed that the text inside the HTML <title> tag for the Iris 2.4 documentation at https://scitools.org.uk/iris/docs/v2.4.0/gallery.html says “Thumbnail gallery — Iris 2.2.0 documentation” rather than 2.4. It’s correct in the equivalent page in the version 2.3 documentation. I’ve not done an extensive search of all pages, but it looks like the

Description of the problem

Even though it's in the title, our map 🗺️ tutorial for setting map frames, ticks, titles and labels doesn't actually teach us how to set a title!

Description of the desired feature

Verde has utilities for selecting scattered spatial data based on windows and blocks (block_split and the new rolling_window). We don't really have any examples or tutorial

Hi, there is a small typo in the documentation of the function

reduce_to_pole

in fatiando.gravmag.transform. A square is missing in the numerator at

    RTP(k_x, k_y) = \frac{|k|}{
        a_1 k_x^2 + a_2 k_y^2 + a_3 k_x k_y +
        i|k|(b_1 k_x + b_2 k_y)}

(i.e, it should be \frac{|k|^2}{ ), same for the link

https://www.fatiando.org/api/gravmag.transform.html#fa

I'm using nearest_s2d in combination with the add_matrix_NaNs' 'hack' documented in #15 , but I'm getting 'smearing' of the nearest value all the way to the border with nearest_s2d when I would expect it to behave like bilinear with the 'outside' values instead missing.
Is this the intended behaviour? Can I work around this somehow by masking the output again?

![ex](https://user-images.githubu

I was able to get testing working on Cheyenne using the nwm_compute environment and the scripts in tests/local 🎉, but some of the help looks like it should be updated (incl. the README - which seems pretty dated at this point) and I'm a bit confused about some of the default options.

In particular...

Compiler

A bug report assumes that you are not trying to introduced a new feature, but instead change an existing one... hopefully correcting some latent error in the process.

Description

My take on SKOS definition comments

What would you like to see changed?

https://github.com/ESIPFed/sweet/wiki/SWEET-Annotation-Convention says if I have a comment I should create an issue, so this is my

The authors line on the workshop lesson 1 renders on top of the orange box that holds the module description (see lesson 1 for Setup Your Earth Analytics Python Env). The spacing needs to be fixed, so that there is space (separation) between the author line and the orange box for the module description, similar to the [ot

The Generating Meshes notebook currently has no explanatory text and display a pipeline which is of course not usable on the static website. Therefore it doesn't actually demonstrate what the notebook is meant to be about which is to generate meshes.

Copy-paste those to a Python interpreter will result in "invalid syntax" or similar, as quotes are set as html instead of code

Description of the desired feature

Currently Harmonica has functions to compute distances between points defined in Cartesian coordinates or in spherical geocentric coordinates. Would be nice if we add a function to compute Euclidean distances between points whose coordinates are defined in geodetic (ellipsoidal) coordinates (don't confuse it with great circle distances).
Worth noting that

The integrated summer insolation should be integrated from 152 day to 243 day (June to August), not select 'Fsw(Few<275)=0'. If I am right, please revise it.

Summary

Plot methods should be documented using a template rather than a hard-coded docstring.

Reason

You could easily add more examples and explanation

Current behaviour

Plot methods are registered using psyplot.project.register_plotter and the documentation is generated via the psyplot.project.ProjectPlotter._gen_doc method. This only gives a minimal possibility to mo

I've run into ISMN timeseries files that are turned into a series of NaNs by scaling (e.g. ARM/Anthony/ARM_ARM_Anthony_sm_0.025000_0.025000_SMP1-A_19780101_20180712.stm at lon: -98.0969, lat: 37.2134).

This seems to happen in pytesmo.scaling.gen_cdf_match (scaling.py, line 403) because SciPy's InterpolatedUnivariateSpline throws ValueError('x must be strictly increasing'). Pytesmo catches thi

Description of the desired feature

Would be nice if the gallery example corresponding to each dataset would explicit the license under it's released and a reference to its article (or doi). By facilitating this information we could encourage people to cite the models they use, and get to know under which license are they released.