Fabian Schindler
Fabian Schindler
I'm having the same issue (also like to omit "patch" on a prerelease). Is there a workaround?
Perfect, thanks, I'll investigate ASAP
@kevinmehall I finally got around to fix this (as with 8caab99). All three of your supplied files now work and are decoded to the same array. Some edge cases are...
Hi @rahulbreezo Typically, a large TIFF is best not downloaded as a whole, so geotiff.js uses so called HTTP range requests to fetch slices from a remote TIFF. So the...
Hi @matthesrieke and @bsuwal! Thank you for submitting this issue! Could you please provide an example image where this happens?
Hi @sroboubi, This seems like a tricky issue and is related to the reasons why I don't like the current implementation of the blocked source. First off: I don't think...
Hi @MarByteBeep First, since you are using `fromFile`, I'm assuming that you are using the library from node.js. Is that correct? Second: please provide more information of your file. A...
@MarByteBeep Okay, the resolution is 25m, so you are requesting an image of about 100x100 px. You do not have to pass the output `width`/`height`, only if you want to...
> That 100x100 is not needed as the library will infer that from the 2500x2500 meters? I.e., > > ``` > const results = await image.readRasters({bbox: [ > 117152, >...
Hi @sroboubi Thanks for raising this issue! In the latest version you can use a [`Pool`](https://github.com/geotiffjs/geotiff.js/#using-decoder-pools-to-improve-parsing-performance) to do a multithreaded decoding. Please try it and see if this improves the...