Skip to content

Commit

Permalink
Fix bug #3179 related to OperationalLimitSet not being imported when …
Browse files Browse the repository at this point in the history
…attached to an ACLineSegment with no EquipmentContainer.

Signed-off-by: Romain Courtier <[email protected]>
  • Loading branch information
rcourtier committed Oct 30, 2024
1 parent 063f8c5 commit 6e9f109
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
4 changes: 2 additions & 2 deletions cgmes/cgmes-model/src/main/resources/CIM16.sparql
Original file line number Diff line number Diff line change
Expand Up @@ -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 ;
Expand Down

0 comments on commit 6e9f109

Please sign in to comment.