If DSG data is specified with some kind of subset, such as /X /Y /Z /T /E ranges, then the result is subsetted in other directions as well. So, for instance if the data is a set of timeseries at different stations and we
yes? list/t=10-jan-2020:15-mar-2020 temperature
then the longitude, latitude and E ranges for that subset describe the set of stations that have data in that time range. So the Lon, lat, e (and perhaps depth) ranges listed in the upper left of plots, and the top of ascii listings should reflect what's in the plot or listing.
Currently these labels show the ranges for the entire dataset.
This is fixed. There are some changes in benchmark output of "LIST" commands, and a new test is added which looks at the labels generated for plots showing the coordinates orthogonal to the plot view.
If DSG data is specified with some kind of subset, such as /X /Y /Z /T /E ranges, then the result is subsetted in other directions as well. So, for instance if the data is a set of timeseries at different stations and we
yes? list/t=10-jan-2020:15-mar-2020 temperature
then the longitude, latitude and E ranges for that subset describe the set of stations that have data in that time range. So the Lon, lat, e (and perhaps depth) ranges listed in the upper left of plots, and the top of ascii listings should reflect what's in the plot or listing.
Currently these labels show the ranges for the entire dataset.