Layer Consistency [Epic 5 (Discovery)]

[NEDJIMAbelgacem]

Note that discovery tasks will be completed by order of priority in line with discovery task requirements. Discovery may include documentation and/ or implementation of feature design.

Expectation:

The list of contextual layers should be the same as the layers in the filter tab for each equation

Priority:

Low

Dependencies:

None

Description:

No extra layers (e.g. capacity factor) should be included, and the contextual and filter layers should remain consistent.

Scope:

The scope of this process will depend on the results of the discovery process.

Requirements:

None

Success Criteria:

Available layers remain consistent between the filter tab and contextual layers

[NEDJIMAbelgacem]

This ticket is very related to interactive filtering. Eventually the user will not need a contextual layers and that panel will be switched into something like "Output layers".

[NEDJIMAbelgacem]

This have been addressed by making the eye button to display the filter's layer. which meant there was no need for many layers to be in the contextual layers menu. Let me know if this fixes the issue.

[ClaraIV]

This needs to be checked thoroughly for each layer as not all layers function properly, or at least not for all countries/regions. Eg., for Caspian Sea the UNESCO layer is activated and visible only upon "deactivation", and is not displayed when actually "Active" like the other layers.

Not for all countries the vector symbols are displayed properly or even consistently, see below screenshot for Airports for Solar and then for Onshore Wind; and below for another instance where we actually have symbols.

[akshay2408]

Hi @ClaraIV and @dimasciput My debugging about this task is as follows :- When I select Azerbaijan country (solar PV, 25km grid) and UNESCO filter is ON, then we have the following cases on staging and development.

This is the staging url and its response is blank image. https://cenpsr6h9g.execute-api.us-east-2.amazonaws.com/v1/layers/AZE/solar/unesco/7/80/48.png?colormap=viridis&f_unesco=1000,165570&offshore=false

This is the development url and it has response image. https://d2b8erzy6y494p.cloudfront.net/v1/layers/AZE/solar/unesco/7/80/48.png?colormap=viridis&f_unesco=1000,165570&offshore=false

Which means the data is not consistent on development and staging, I think we have different host and the s3 buckets in different region OR the buckets are not synced.