Describe the bug
When loading a COG from URL, metadata values are not used. This might be intentional, but there is nothing in the documentation indicate that that's the case.
To Reproduce
Steps to reproduce the behavior:
- Add break point in GeoRaster's constructor
- Call
parseGeoraster(https://path.to/cog.tiff, { projection: "example" })
Expected behavior
Metadata is expected to be used. When parseGeoraster's input is an ArrayBuffer, it is used.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: MacOS
- Browser: Chrome
- Version: 116
Additional context
I see that there are other types of inputs where metadata is not passed as well.
Describe the bug
When loading a COG from URL, metadata values are not used. This might be intentional, but there is nothing in the documentation indicate that that's the case.
To Reproduce
Steps to reproduce the behavior:
parseGeoraster(https://path.to/cog.tiff, { projection: "example" })Expected behavior
Metadata is expected to be used. When
parseGeoraster's input is an ArrayBuffer, it is used.Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
I see that there are other types of inputs where metadata is not passed as well.