Thank you. The ECW and COG files had been stored on Google Drive, exposed locally as "g:\". To eliminate that layer of abstraction I've copied the files from that "g:\" location onto my local desktop, which resides physically on this laptop's local disk (for clarity). For additional clarity, and because I may have confused Read-Only and Read-Write data source configs when reporting my experiences previously (gah, sorry), here are clearer descriptions of the behaviour. Neither files has any sidecars associated with it. Neither file has ever been touched by Release 8. The ECW was produced by GlobalMapper, and the TIF by GDAL 2.4. The image component for ECW data source, a 128*128 UINT8*4 image, under various configurations. 1. Read-Only, No Cache: Image component opens immediately, style with no ability to style 2. Read-Write, No Cache: Image component opens immediately, with no ability to style 3. Read-Only, Cache: Image component opens after ~100s "Migrating Data" dialog, with no ability to style 4. Read-Write, Cache: Image component opens after ~100s "Migrating Data" dialog, with ability to style. The 4 bands in "RGBA" (R:0,G:1,B:2,A:3) incorrectly display the transparency layer, however. Changing A:Value=0 results in correct display, though without any transparency. The image component for TIF data source (pointed at a COG), a 256*256 UINT8*3 image, under various configurations. 1. Read-Only, No Cache: Image component opens immediately, is blank, with no ability to style 2. Read-Write, No Cache: Image component opens immediately, is blank, with no ability to style 3. Read-Only, Cache: Image component opens after ~55s "Migrating Data" dialog, displays correctly (including correctly detecting the MASK as alpha), with no ability to style 4. Read-Write, Cache: Image component opens after ~57s "Migrating Data" dialog, displays correctly (including correctly detecting the MASK as alpha), with ability to style. The 3 bands in "RGB" (R:0,G:1,B:2,A:Value=0) display correctly, including transparency. I can provide the files to tech; they are ~340mb for the ECW and ~290mb for the COG. Should I email a public URL to those files? Postscript on the COG format, I'll send in a suggestion to support natively. ESRI added support for COG and offers a toolset (https://github.com/Esri/OptimizeRasters) for creating and manipulating them, as well as the NASA-favoured LERC-compressed MRF format (https://github.com/nasa-gibs/mrf/blob/master/doc/MUG.md) and (https://github.com/nasa-gibs/mrf/blob/master/spec/mrf_spec.md). Thank you again.
|