Use easySDI layer where it is possible
|Sponsor:||Geneva Airport (CH)||Ergonomic impact:||
To define a predefined perimeter in the SHOP component, we still have to define the WMS layer with the old fashioned way : select a source AND fill the layer name.
We should enforce, where it's possible, the use of easySDI layer object, like it was done for the definition of resource visualization.
With this, the availability of the layer is (more) guaranteed, use of easySDI layer is more integrated and transverse and gives consistency to the solution.
#3 Updated by Magoni Bruno over 2 years ago
I will add that such centralization will ease configuration's changes when an endpoint layer is not accessible (removed, name changed, temporary unavailable, and so on).
There is only one easySDI object to manage instead of founding where layer "XYZ" has been used inside easySDI platform...