You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This derived, single band COG works wonderfully with geoblaze.parse() using a local fs.readFile buffer, but when i use the same file over the localhost network with geoblaze.parse(), I get this error:
I saw both open and closed issues in your org repos with similar errors, but the contexts and problem definition seemed quite different, and I'm not sure which library is throwing the error because all errors are coming from dist/geoblaze.node.min.js. My guess is this is georaster related?
p.s thank you for this lovely library and all you've done for the amazing COG ecosystem!!!
The text was updated successfully, but these errors were encountered:
for some reason, it didn't work with next.js public directory using express, but it did work over network from blob storage. comparing and contrasting the headers left me stumped, so, although this is unsolved, i'm assuming its out of scope for this project, thanks again!
Describe the bug
This derived, single band COG works wonderfully with
geoblaze.parse()
using a localfs.readFile
buffer, but when i use the same file over the localhost network withgeoblaze.parse()
, I get this error:then I get repeats of this error in a loop, with varying negative array lengths.
Expected behavior
The
geoblaze.parse()
should work over the network if the local filesystem approach is working for that file.Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
The file was generated from this source vector file:
https://files.isric.org/soilgrids/latest/data/wrb =>
MostProbable.vrt
using:
also, I have checked the way the local fileserver is serving the files, and I think it's working fine?
`gdalinfo` output
Duplicates?
I saw both open and closed issues in your org repos with similar errors, but the contexts and problem definition seemed quite different, and I'm not sure which library is throwing the error because all errors are coming from
dist/geoblaze.node.min.js
. My guess is this is georaster related?p.s thank you for this lovely library and all you've done for the amazing COG ecosystem!!!
The text was updated successfully, but these errors were encountered: