Adding Cloud Optimized GeoTiff file to ImageryTileLayer

903
3
11-15-2022 04:23 PM
UndralBatsukh
Esri Regular Contributor
5 3 903

This release adds beta support for adding Cloud Optimized GeoTiff (COG) files to an  ImageryTileLayer via the URL property. COG files can take advantage of all the capabilities of ImageryTileLayer. See the ImageryTileLayer with COG sample for more information. We also added a section for Referencing Cloud Optimized GeoTiff URL in the overview of ImageryTileLayer SDK document. Please watch the video below to learn more about this feature. Please leave me a message if you have questions or feedback. 

Happy coding! 

3 Comments
MatejVrtich
Esri Contributor

Hi,

great to see COG support in the JS API!

Are there any plans to expand it further? Say add a COG from a URL directly in the Map Viewer, save a layer referencing the COG (or add a COG layer directly to the portal content), ...maybe a STAC widget for the JS API?

Thanks,

Matej

miro_aus
New Contributor II

This functionality is absolutely amazing, thank you. I would have two things in my mind in relation to it:

1. Have a way / parameter to tell ArcGIS JS to not look for aux.xml files. Fine if it does check by default, but it would be nice to not have all these failed requests in console if you know your software/process can't / does not create aux.xml or when access to such file on server would require passing parameters in URL etc.

2. Would love to use COG as elevation layer too. Can't figure how to achieve that if it is somehow possible at all? Looking at this great tutorial: https://developers.arcgis.com/javascript/latest/sample-code/layers-custom-elevation-thematic/ a tutorial to use COG in similar way would be really appreciated.

miro_aus
New Contributor II

To the 2. I have figured it out using mentioned tutorial and method fetchPixels() of ImageryTileLayer. Works really nicely with only very rare errors when fetching tiles.

If I can have a recommendation - If possible ImageryTileLayer could be optimized to not load/fetch 1MB on load of each layer (COG file) - e.g. 50 layers (even with visibility false) result in 50MB of initial load of layers into the map. Not ideal.