Save geotiff files and metadata to indexeddb

[gjmooney]

Description

Checklist

• PR has a descriptive title and content.
• PR description contains references to any issues the PR resolves, e.g. Resolves #XXX.
• PR has one of the labels: documentation, bug, enhancement, feature, maintenance
• Checks are passing.
  Failing lint checks can be resolved with:
  • pre-commit run --all-files
  • jlpm run lint

---

📚 Documentation preview: https://jupytergis--891.org.readthedocs.build/en/891/
💡 JupyterLite preview: https://jupytergis--891.org.readthedocs.build/en/891/lite

[github-actions]

👈 Launch a Binder on branch gjmooney/jupytergis/save_to_db

[arjxn-py]

👌 Thanks

[martinRenou]

Thanks @gjmooney !

We should discuss this, I have some concerns. We used to save the geotiff content into indexeddb, but it was removed as part of #503.

The issue is that OpenLayers supports COG properly, it only downloads what it needs for rendering, but we were downloading the full geotiff content (could be gigs of data!)

[martinRenou]

Putting my veto on this for now

[github-actions]

Integration tests report: appsharing.space

[martinRenou]

I may be misunderstanding the PR here. In which case are we using this loadGeoTiff logic? Is it only for local files that do not support COG?

[mfisher87]

In which case are we using this loadGeoTiff logic? Is it only for local files that do not support COG?

If this is the case, let's update the name!

For COGs over HTTP, I think the only thing we should be caching is the min and maximum values. Maybe all the metadata.