Skip to content
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

Large GeoTIFF file cacheable for next rendering #18

Open
s9eenk opened this issue Mar 14, 2018 · 5 comments
Open

Large GeoTIFF file cacheable for next rendering #18

s9eenk opened this issue Mar 14, 2018 · 5 comments

Comments

@s9eenk
Copy link

s9eenk commented Mar 14, 2018

Hi Stuart,
I m using a large geoTIFF file around like 500 MB , want to make it caheable for next rendering in order to make it easily accessible for second time without waiting(First time it loads for two minutes). Or else any suggestion for loading it quickly for the first time.

@m-mohr
Copy link
Contributor

m-mohr commented Mar 19, 2018

There is probably not much this library can do for you. GeoTiff is not supported by browsers and the data needs to be read from a file and painted to a canvas. That needs some time, especially for files that big as yours. There is no reliable way to cache this amount of data on client side. The only solution I could think of is to convert the GeoTIFF to PNG and display these file(s) using Leaflet. Browsers can cache and render them directly.

@s9eenk
Copy link
Author

s9eenk commented Mar 19, 2018

Thank you for your response Matthias. I have worked out your solution, for display purpose that is converting GeoTIFF to PNG. But, my concern is on the values inside the GeoTIFF file , where it's been shown on 'hover' of the map. I have only two options left to make it work i.e, placing the GeoTIFF file locally (here, it initially takes sometime to get the file locally on client and retrieve the values on hover )or else publish it on the server side and get the values from server side at every hit from client side, which hampers the performance. Any help in this regard is appreciable.

@m-mohr
Copy link
Contributor

m-mohr commented Apr 27, 2018

Well, this workaround probably only works for displaying the graphics, but not for your use-case where you interact with the data. With such big files you probably need to think about other solutions like the second approach you mentioned. It's never a good idea to transfer 500MB files to the user for processing so optimize it and maybe shift this to the server side. Sorry for not having a better solution for you.

@m-mohr
Copy link
Contributor

m-mohr commented May 23, 2018

@s9eenk In the long run, Cloud Optimized GeoTiff could be a solution for your problem: http://www.cogeo.org

@chriszrc
Copy link

Have you tried using cogs yet? Any pointers on how to get started using those?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants