-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
guidance on /undefined url or decoder missing #27
Comments
Fwiw, i'm interested in this topic too. I've tried loading our gdal-generated COGs too in https://geotiffjs.github.io/cog-explorer or in a locally-deployed instance and so far nothing has been displayed in the page, even if the network console show ~180Mb downloaded in ~35 requests, and there are no other error msgs in the js console (besides the decoder.worker.js one). i dont think the decoder.worker.js thing is important, because the two openaerial/hot-osm samples load fine.. |
adding some console.log statements here and there, i've seen an openlayers assertion about the resolutions array being in the wrong order (points at https://openlayers.org/en/v4.6.5/doc/errors/#17) but the code is supposed to reverse it already.. puzzling. |
what is strange is that while my cog has 12 levels of overviews for each of the 3 bands, addSceneLayer in https://github.com/geotiffjs/cog-explorer/blob/master/src/components/mapview.jsx#L180 thinks i have 26 images per band ? maybe because some of those are overviews for the mask band..
i think at that point openlayers complains because the array has resolutions for both types and cant figure out how to sort them:
so something (in my case at least) must be done to ignore the mask bands. |
after hacking a bit the js code, it seems to me that cog-explorer wasnt tested recently with cogs produced by gdal ? after fixing the resolutions array, i'm stumbling on geokeys being null on https://github.com/geotiffjs/cog-explorer/blob/master/src/components/mapview.jsx#L196 |
hi team, i tried the explorer today and i'm a bit stuck on the interaction with our cogs.
I wonder if you have some guidance on how to debug the issue, does the explorer have some extended logging modus?
I was testing with this cog
https://dev-files.isric.org/soilgrids/latest/data_aggregated/1000m/sand/sand_30-60cm_mean_1000.tif
https://geotiffjs.github.io/cog-explorer/undefined. Something wrong with the COG? It is generated from gdal. What is the best approach to validate cogs?
Thanks for sharing your ideas, paul.
The text was updated successfully, but these errors were encountered: