[CSA Importer] Read CNECs borders #1124
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What is the current behavior?
CNECs were always created with a null border.
What is the new behavior (if this is a feature change)?
According to what was decided for the CSA SWE process, the border to which an AssessedElement is linked can be specified though the field
AssessedElement.OverlappingZone
.Only REE needs to specify this information since REN and RTE both only have one border so the AssessedElement's operator is enough to know said border.
A new CSA CRAC creation parameters field called
"borders"
was added to indicate how to map an AssessedElement to a specific border.name
is the name of the border that will appear in theborder
field of the CNECs in the CRACeic
is the EI Code of the borderdefault-for-tso
indicates for which operator (TSO) this border is the default border (used for TSOs with only one border)When an AssessedElement is being parsed by the importer the OverlappingZone field is read:
Does this PR introduce a breaking change or deprecate an API?