Closed djhoese closed 5 years ago
In GitLab by @tims on Aug 2, 2018, 15:01
changed the description
In GitLab by @rayg-ssec on Aug 15, 2018, 13:43
assigned to @rayg-ssec
In GitLab by @rayg-ssec on Sep 26, 2018, 18:15
This looks like it's happening because of the lexical sort by (family, category, serial) in document.py's sort_product_uuids; to allow instruments with equivalent nominal bands to exist in the same family, the µm nominal wavelength is used in that instead of the band number (which varies by instrument).
The simplest solution may be to uniformly format the wavelengths so that 6.9µm lexically comes before 10.3µm, for instance - with either zero-padding or space-padding most likely. Sorting by explicit nominal wavelength becomes problematic in the case of products not having a nominal wavelength (e.g. NWP).
Will think about this tonight and see if there's a robust + correct solution that's better than padding the wavelengths in the family names.
In GitLab by @rayg-ssec on Sep 27, 2018, 10:44
One-line format string fix pushed to develop via merge of issue182-layer-load-order
In GitLab by @djhoese on Oct 25, 2018, 13:20
closed
In GitLab by @tims on Aug 2, 2018, 15:00
Went to file open, selected 16 ABI (full disk) bands and then it was bands 1-6, 13-16 and then 7 on.
PS: This is happening (at least) on Windows.