Fix bug #3179 related to OperationalLimitSet not being imported when …

…attached to an ACLineSegment with no EquipmentContainer. Signed-off-by: Romain Courtier <[email protected]>
powsybl · Oct 16, 2024 · 506923f · 506923f
1 parent bf430fd
commit 506923f
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/...on/src/test/resources/issues/operational-limits/limitsets_associated_to_equipments_EQ.xml b/...on/src/test/resources/issues/operational-limits/limitsets_associated_to_equipments_EQ.xml
@@ -104,7 +104,6 @@
     <cim:ACLineSegment.x>1</cim:ACLineSegment.x>
     <cim:ACLineSegment.x0>0.1</cim:ACLineSegment.x0>
     <cim:ConductingEquipment.BaseVoltage rdf:resource="#_BV"/>
-    <cim:Equipment.EquipmentContainer rdf:resource="#_LN"/>
 </cim:ACLineSegment>
 <cim:OperationalLimitSet rdf:ID="_OLS_ACL">
     <cim:IdentifiedObject.name>Limit set</cim:IdentifiedObject.name>

diff --git a/cgmes/cgmes-model/src/main/resources/CIM16.sparql b/cgmes/cgmes-model/src/main/resources/CIM16.sparql
@@ -389,8 +389,8 @@ WHERE
     # operational limit sets can be attached to terminals or equipments
     OPTIONAL { ?OperationalLimitSet cim:OperationalLimitSet.Terminal ?Terminal }
     OPTIONAL { GRAPH ?graph2 {
-        ?OperationalLimitSet cim:OperationalLimitSet.Equipment ?Equipment .
-        ?Equipment cim:Equipment.EquipmentContainer ?EquipmentContainer
+        ?OperationalLimitSet cim:OperationalLimitSet.Equipment ?Equipment
+        OPTIONAL { ?Equipment cim:Equipment.EquipmentContainer ?EquipmentContainer }
     }}
     ?OperationalLimitType
         a cim:OperationalLimitType ;