Hi, @NoamRa . I'm terribly sorry about the late reply. This is an important issue that you bring up and is certainly something that should be addressed. I'm a bit tight on time at the moment, so a solution might take some time. Would you be interested in submitting a PR?

Otherwise, I think an interim solution would be to over-ride the values after they are returned by parseGeoRaster, so that:

const georaster = await parseGeoraster(url);
georaster.projection = 3857; // or whatever projection

Also, are you needing to override the projection field with a standard EPSG code or a custom projection via PROJ4 String
or WKT? I'm asking because if you are trying custom projections, I can prioritize adding custom projection support to the other family of libraries that work with georaster, as well.

Thank you.

I've noticed a similar issue with other construction methods; if I pass in a file that doesn't have embedded projection type in a Blob format, it fails (beginning here with base64 encoded version of the tiff):

const blob = new Blob([
  Uint8Array.from(atob(tiffString), (c) => c.charCodeAt(0)),
]);
const georaster = await window.parseGeoraster(
  blob,
  { projection: 4326 }
);

but the same data wrapped in an ArrayBuffer is fine:

const tiffArray = Uint8Array.from(atob(tiffString), (c) => c.charCodeAt(0));
const buffer = new ArrayBuffer(tiffArray.length);
const view = new Uint8Array(buffer);
view.set(tiffArray);
const georaster = await window.parseGeoraster(
  buffer,
  { projection: 4326 }
);

I think in all of these cases, setting this._metadata = metadata; should solve the issue.

Raised PR #96 to fix