How often is this likely to occur? (Once a dl table has been created, then every time the DV is changed. Hmm.)
Currently, the dl table callback takes the DV selection as an input, and uses that to determine the file which is used to determine the lat-lon from the rlat-rlon supplied in the clickData. This could conceivably be replaced by a using a fixed (configurable) file for this, at the risk of the conversion to lat-lon being slightly off when the selected DV is not the fixed file.
A better alternative: we could prevent updates when the DV is changed, and only update when the click occurs.
Including: