#9589: Notify data projection not compatible / available for COG

[dsuren1]

Description

This PR check for projection compatibility and notifies the user with meaningful feedback

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?

• Notify data projection not compatible / available for COG #9589

What is the new behavior?

CATALOG

TOC

NOTIFICATION

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]

@dsuren1 this PR after our recent PRs needs to be upated with master, some conflicts present.
I can not test it because I think it needs the integration with the other functionalites. Can you provide a valid test case for the COG context https://dev-mapstore.geosolutionsgroup.com/mapstore/#/context/COG ?

[dsuren1]

@dsuren1

Can you provide a valid test case for the COG context https://dev-mapstore.geosolutionsgroup.com/mapstore/#/context/COG?

For the cog test service urls, we have projection defs already defined in Dev so, maybe it's because of that, i'm not able to create a test data that satisfies all cases. However, you can test it locally by removing projection defs and adding this service url to test catalog error and import this map map_cog_notify.json to test warning and TOC

[offtherailz]

@ElenaGallo, could you please test this on DEV ? Thank you

[ElenaGallo]

Test passed @dsuren1 please backport. Thanks

[tdipisa]

@dsuren1 (FYI @ElenaGallo @offtherailz)

I've tested this as well the other issues. In this case I've reverted projDefs definitions from DEV data dir
and added COGs previosuly tested before releasing 2023.02.00 to this test map.

The notification works fine and the layer is not added to the map. Probably it would be better to let the user know why somehow (e.g possibly a link to the related user guide section? I'm open to suggestions).

There is anyway what I think is a wrong behavior. Every time the map is loaded the following notification appears independently of what is the COG layer visible in TOC (I've tried visualizing them one by one).

This is not correct because the projections are supported for all COG layers in TOC (once needed projectionDefs have been restored in DEV data dir).

[dsuren1]

@tdipisa

There is anyway what I think is a wrong behavior. Every time the map is loaded the following notification appears independently of what is the COG layer visible in TOC (I've tried visualizing them one by one).

This is not correct because the projections are supported for all COG layers in TOC (once needed projectionDefs have been restored in DEV data dir).

It's because the layer's sourceMetadata info is not saved on export and map save. I have fixed this in the PR