Import Export

Published on May 2016 | Categories: Documents | Downloads: 79 | Comments: 0 | Views: 1080
of 3
Download PDF   Embed   Report

Comments

Content

Import/Export of external Data Formats

Import/Export of external Data
Formats
UCTE DEF (Data Exchange Format)

Import
The user can import a UCTE DEF-formatted file. The format is described in the
“UCTE data exchange format for load flow studies” from UCTE subgroup
“Network models and forecast tools”.
In general:
1. Areas and zones created during import: Areas are countries and are named
after the UCTE Country code as listed in the UCTE DEF (*). Zones are
introduced with the ##Z key lines. Whatever follows the ##Z string is the name
of the zone. If there is no zone assigned to a node or the zone name is empty
then the zone name is the same as the area name (country code).
2. Area and Zone assignment of elements: Lines, transformers and equivalents
get the area and zone of Node 1, unless it is a X-Node. In this case they are
assigned the area and zone of Node2.
3. Data consistency check: Before the import is started a topology check is
performed. During this check NEPLAN controls if all the nodes listed in the line
(##L) and transformer (##T) sections exist also in the node section (##N). It
also checks the bus code names for consistency. If errors occur during this
check the import-process will not start. Errors can occur, however, after the
import has started, and perhaps the orig. network has already been partially
updated. In this case it is better to close the project (without saving it), correct
the errors in file and retry.

Import New/Update

Select new if this is an import into an empty project
(*.nepprj). Update in all other cases

Format Ver

UCTE-Format Version

Delete non updated
elements in imported

If this option is set all elements and nodes that belong
to an “updated area” and are not updated during a file-

NEPLAN User's Guide V5

13-1

Import/Export of external Data Formats

areas

import will be deleted from the original network

Keep X-nodes in orig.
network

If this option is set, then the X-nodes that were in the
original network are not eliminated even if the crossborder connection or the other (missing) link exists in
the file. In this case the load and generation at the Xnode will be removed and the other link will be
established

Create Missing Nodes

If this option is set (only with import ‘New’) then nodes
that are not listed in the ##N section but exist in the
##L or ##T sections are created with zero generation
and demand

Run Load Flow after
import

If this option is selected then a load flow run will be
executed right after a successful import

Slack Node in
File/Network

In case of update, the user can select if the slack
should be taken from the file or from the network. If the
user selects the slack of the network then the slack
generator of the file will be converted to a PVGenerator. Likewise, if the user selects the slack of the
file, then the slack of the network is converted to a PVGenerator

History file and Logfile

These are registry entries that are updated every time
the user enters a new filename

X-node File Name

The filename is a registry entry. The text file containing
the following information. X-node name (exact), Node
1(Node From), Node 2 (Node To), i.e. the nodes
connected through the cross-border link.

Field Separator

Comma or Semicolon. Separator for the data columns
in X-node file.

As soon as the user presses the OK button NEPLAN reads the import file and
displays a new dialog with all areas and zones in the import file listed. By default
all areas are selected. If the user clicks the OK Button the file will be imported as
is. Alternatively the user can select specific areas or zones to be imported.
Please NOTE:
1. The X-nodes created after the selective import of areas HAVE NO
GENERATION OR LOAD attached to them. The user has to create load or
generating elements manually. The cross-border connections are created (only
lines are supported).
2. After the selective import of zones instead of the X-nodes the “real” nodes at
the cross-border link are created.

13-2

NEPLAN User's Guide V5

Import/Export of external Data Formats

Export
Export UCTE File

The filename of the export file.

Frequency

In Hz. The network frequency.

X-node File Name

The filename is a registry entry. The text file containing
the following information. X-node name (exact), Node
1(Node From), Node 2 (Node To), i.e. the nodes
connected through the cross-border link.

Field Separator

Comma or Semicolon. Separator for the data columns
in X-node file.

X-Node File Format:
Semi-colon or comma separated columns:

1st column: X-Node Code

2nd column: X-Node Name (can be empty)

3rd column: Node 1 (Code)

4th column: Node 2 (Code)

5th, 6th… column : additional info (they will be ignored)
Example
-------------XMO_KO11; 1BA-HR; WMOSTA1
XUG_ER11; 1BA-HR; WUGLJE1
XTR_PG11; 1BA-YU; WTREBI1

NEPLAN User's Guide V5

;HKONJS1
;HERNES1
;JPODGO1

;;Mostar;Konjsko;;;;;
;;Ugljevik;Ernestinovo;;;;;
;;Trebinje;Podgorica;;;;;

13-3

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close