Enhancement #937

Use easySDI layer where it is possible

Added by Van Hoecke Hélène almost 3 years ago. Updated over 2 years ago.

Status:ClosedStart date:03/13/2015
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:SHOP
Target version:4.3.1
Sponsor:Geneva Airport (CH) Ergonomic impact:

-

Functional impact:

-


Description

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.

History

#1 Updated by Magoni Bruno almost 3 years ago

  • Status changed from New to Request For Comments

#2 Updated by Magoni Bruno almost 3 years ago

  • Priority changed from Normal to High

#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...

#4 Updated by Villemagne Jérôme over 2 years ago

TC agree with such enhancement but we must be aware that it will have impact on existing predifined perimeters whose cannot be automatically updated.

#5 Updated by Villemagne Jérôme over 2 years ago

  • Status changed from Request For Comments to Accepted
  • Assignee deleted (Technical Committee)
  • Priority changed from High to Normal

#6 Updated by Van Hoecke Hélène over 2 years ago

  • Assignee set to Van Hoecke Hélène

#7 Updated by Van Hoecke Hélène over 2 years ago

  • Category set to SHOP
  • Status changed from Accepted to Affected
  • Target version set to 4.3.1
  • Sponsor Geneva Airport (CH) added

Predefined perimeters are now configured by using an easySDI layer.

#8 Updated by Van Hoecke Hélène over 2 years ago

  • Status changed from Affected to Resolved

#9 Updated by Van Hoecke Hélène over 2 years ago

  • % Done changed from 0 to 100

#10 Updated by Van Hoecke Hélène over 2 years ago

  • Status changed from Resolved to Closed

#11 Updated by Blatti Yves over 2 years ago

We'll need to add a release note, as we cannot have a transparent update with this change !

#12 Updated by Van Hoecke Hélène over 2 years ago

  • Assignee deleted (Van Hoecke Hélène )
  • Functional impact set to -
  • Ergonomic impact set to -

Also available in: Atom PDF