#9590: COG download metadata by default with abort fetch

[dsuren1]

Description

This PR allows fetching of COG layer metadata by default on saving the service. Basic metadata informations are added to layer.

Some geotiff source functions are not exported. Hence alias has been created to import the functions.

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Enhancement

Issue

What is the current behavior?

• Make COG download metadata by default #9590 (comment)

What is the new behavior?
Allows fetching of COG layer metadata by default and also allows cancelling of the fired request on processing the url and getImage process

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[offtherailz]

• Delete button should be disabled, or not visible, while saving, or I'm able to delete the catalog while loading.

Video.del.14-11-2023.12.02.56.webm

[offtherailz]

This solution is a big hack...

Did you try to implement it instead?
Like this as documented here, or better using axios (I'd prefer axios solution, so we have also authentication, proxy etc... out of the box, the doc do not show, for brevity, the solution with Promise) ?

const response = await fetch(someUrl);
const arrayBuffer = await response.arrayBuffer();
const tiff = await fromArrayBuffer(arrayBuffer);

If a solution like this is possible, we can have more control on it, without any hack.

Otherwise I think we have to rely on internal functions as you did in this implementation.

[dsuren1]

Yes, I did check.
fromArrayBuffer still doesn't handle signal parameter correctly. It is lost when the passed down to fromSource. Reason it cannot handled with axios is because fromSource makes bigtiff parsing logic to read tif data and converts to image object with required functions necessary for extracting metadata informations.

Maybe we can cancel the promise of fromUrl and getImage but not the actual fetch request action (which is a compromise) and in the process we can avoid the hack and also this will not impact user performance. Kindly let me know if this okay? @offtherailz

[dsuren1]

• Delete button should be disabled, or not visible, while saving, or I'm able to delete the catalog while loading.

Looks like it is an existing issue for all services. I will address it.

[offtherailz]

• Now bbox information look not to be present anymore.

tested with this: http://localhost:8081/#/viewer/46403

screencast-localhost_8081-2023.11.16-12_57_17.webm

• Comments inline

[offtherailz]

Basically, as discussed with @dsuren1 , we can canel the pending task to make the user continue operating if the "Save" takes too long, but we can not cancel the effective requests pending

This can cause the pending requests to be blocking and slowing down the load on that particular domain in any case (because of bandwitdh and max number of parallel requests allowed to a specific domain by the browser etc...)

Please report the known issue notice, or we loose memory of it.
Having an issue about it linking could be useful to track the problem too.
@tdipisa should we open it ?

I ask @dsuren1 to link the proper issue to github repo of geotiffjs, for completeness.

Suggested change

	.then((image) => resolve(image))
	.then((image) => resolve(image)) // note: the cacellation will not cancel the request because of issue in

[dsuren1]

Updated note on the function and created an issue in geotiff.js

[ElenaGallo]

Test passed, @dsuren1 please backport to the stable branch. Thanks