Daniel J. Dufour

I ran into this issue as well working on another project. I think the main issue is this line: https://github.com/geotiffjs/geotiff.js/blob/master/src/geotiffwriter.js#L255, which assumes that your data is in 8-bit 0-255 integer...

Thanks for the catch! I believe @sdpeyton can answer this.

Yes, great idea! We should definitely do that. We especially draw inspiration from OpenLayers who does what you suggest. Would you like the following code? ```javascript import load from 'geoblaze/load'...

@fionawhim, awesome we didn't know about `mathjs/number`. We're open to PRs if you want to submit! :-)

Also, open to PRs updating our dependencies like Chris suggested!

sample code ```js import { vectorize } from 'geoblaze'; const options = { propertyName: 'value' }; const geojson = vectorize(georaster, options); ```

Add comparison in performance to GDAL and ArcPY, rasterio across functions

Hi, @miccoh1994 . I'll update GeoBlaze dependencies and let's see if that helps.

Hi, @miccoh1994 . I believe I fixed this by upgrading the geotiff dependency and publishing a new version (https://www.npmjs.com/package/geoblaze). Could you reinstall and see if it works?

Yes, please file an issue with GeoRaster! Thank you!!