The XPX format is designed to facilitate import of external databases into XP databases. The file format is described in detail in a separate documentation file. Basically, a simple command-line syntax is implemented to allow the creation of network elements and associated data

Importing XPX/EPA Data

This feature provides the ability to import SWMM data files created for EPA-SWMM Version 4. It can be used to import data into a new network or to append to an existing network. This function has only been implemented for data files from Version 4.00 through 4.20 coded in accordance with the format described in the USEPA Stormwater Management Model, Version 4 User's Manual (June 1988). It may be extended to include Version 3 files in a future release depending on user demands. 

EPA SWMM 4.4 and 5.0 files may be converted to XPX format using the standalone EPA-SWMM Data File Reader. This program may be accessed via the Tools -> Launch Application menu.

IMPORTANT NOTE

Although every attempt has been made to implement the undocumented features implemented in a variety of customized programs, we offer no guarantee that data will be imported exactly as originally coded.
Import is offered as a tool to assist in creating your database. All imported data MUST be verified to ensure it is a true representation of the original information before any attempt is made to use the generated results.

XPX Options

The XPX options allow the user to make Inactive data active and echo additional feedback on the imported data. Below are the descriptions of the available options when importing XPX  files. 

Inactive Data

Inactive data is data that is not needed for the simulation due to a particular option not being taken. The data in the XP database is hierarchical. So if an element in the hierarchy is taken out then the data beneath that will become Inactive.

Note: This refers only to data, not objects. This does not affect whether objects (nodes and links) are enabled for analysis in any particular mode. This is covered below.

Make Imported Data Active. If any item of Imported data is Inactive, i.e. the parent flag is not ticked, after all the data in the XPX file is imported then thedata will be made Active by ticking on the parent flag, in the order they appear in the file. Selecting Report Data made Active will create a report file containing information on all the data that had to be made Active. 

Warn if Data is Inactive. No action will be taken if imported data remains Inactive. It will still be Inactive after the Import. It will only become Active if the parent data flag is manually changed to make this data Active. The data will be imported and a warning message will be generated to indicate that some data is inactive.

No Action. No action will be taken if data is Inactive. It will still be Inactive after the Import. It will only become Active if the parent data flag is manually changed to make this data Active. The data will be imported with no warnings.

Report Successful Data Imports

Ticking this box will report all successfully imported data.

Initialise Objects

Initialises the data fields in the database ready for solve. This function checks all necessary dialog boxes of the selected field type, and confirms that data will exist in that field. 

Node. Switches on all data flags necessary for node type data 

Link. Switches on all data flags necessary for link type data

RNF data variable. Switches on all flags for run-off layer data

TRN data variable. Switches on all flags for sanitary layer data\

HDR data variable. Switches on all flags for hydraulic layer data

EPA-SWMM 4.2 Data File

Select this option to import an EPA-SWMM version 4.0 - 4.2 data file. Using this option, data for specific modules and specific data within each module may be imported. Part of a network may also be imported by only importing into existing or highlighted objects. The SWMM blocks that are supported are Runoff, TRANSPORT, EXTRAN, STORAGE/TREATMENT. Import automatically detects which block is within the data file. If multiple modes are imported EXTRAN should be imported first, on its own, and the other nodes added by re-importing the data file a second time.

Although data checking is performed on the input file, it is generally assumed the input file is a valid EPA-SWMM file which will run under version 4.2 of SWMM without error.

The name of EPA-SWMM data file may be entered manually or selected using the Select button. 

Import Object Control

Use these options to control how objects are created from the data file and which objects will be imported into. If the default values of 'Create objects' on and 'Import into all objects' are used, all objects in the input file will be imported.

Create Objects. This flag controls the import of objects found in the input file that do not already exist in the network. If this flag is OFF, data for objects will be imported only if that object already exists. If this flag is ON, objects will be created if they do not already exist. Note that the 'Import into selected objects' option overrides this option if it is ON. In that case, data is only imported into currently highlighted objects.

Import into all Objects. This option allows any existing object to be imported into, regardless of whether or not the object has been highlighted.

Import into Selected Objects. This option is quite powerful and restrictive in that it only allows network objects that are currently highlighted to have data imported into them. New objects cannot be created from the data file. This option is particularly useful when incrementally creating a network and importing a data file several times. The new objects can be highlighted and import restricted to only these objects.

Import

Use this button to perform the import when the desired parameters have been entered.

When you select Import you will be given an Import Warning. This warning dialog is simply to remind you that import can overwrite existing data and should be used with caution. If you want to continue with the import simply hit return or the OK button.

If you wish to save the current version of the database before import or change the import parameters, hit the Escape key or the Cancel button to be returned to the import parameters dialog.

Runoff Import

This dialog allows specific runoff data to be imported or ignored. Generally all data should be imported, although there may be cases where some data is not required. For example, 'Channel/pipe data' may not be required if the conduit data is to be imported from an Extran data file.

Import Interface Files. This flag controls the import of Runoff input and output interface files.

Import Descriptive Titles. This flag controls the import of the two descriptive title lines.

Import Control Parameters. This flag controls the import of Runoff Control parameters. If this flag is off the control parameters will be read, and used later in the import, but not written.

Import General Snowmelt Parameters. This flag controls the import of Runoff Job Control Snowmelt data. Turning this flag off could cause inconsistencies with the subcatchment snowmelt data.

Import Precipitation Data. This flag controls the import of Runoff rainfall data. 

Import Evaporation Data. This flag controls the import of Runoff evaporation data. 

Import Channels/Pipes Data. This flag controls the import of all channel, pipe, inlet and dummy conduit data.

Import Subcatchments. This flag controls the import of Runoff subcatchment data.

Import Water Quality Data. This flag controls the import of pollutant, landuse and erosion data.

Import Print Control. This flag controls the import of Runoff print control.

Transport Import

This dialog allows specific transport data to be imported. Generally all data should be imported, although there may be cases where some data is not required.

 


Import Descriptive TitlesThis flag controls the import of the two descriptive title lines.

Import Transport Control Parameters. This flag controls the import of Transport Control parameters. If this flag is off the control parameters will be read, and used later in the import, but not written.

Import Element Data. This flag controls the import of Transport element data comprising all conduits and non-conduits.

Import Pollutant Data. This flag controls the import of Transport pollutants.

Import Internal Storage Elements. This flag controls the import of Transport internal storage elements.

Import Node Control Data. This flag controls the import of Transport node control data. This data comprises output control for Transport elements to SWMM interface files and the output tables.

Import Infiltration Data. This flag controls the import of Transport infiltration data. This data determines the amount of additional flow into the sewer system via infiltration from various sources.

Import Sewer Inflow Data. This flag controls the import of sewer inflow data. This data comprises the daily and weekly temporal patterns for sewer inflows.

Import Study Area Data. This flag controls the import of Transport study area data. This data comprises overall measurements of sewer inflows for the whole of the catchment. Predicted flows are adjusted to match study area measurements for the whole drainage basin.

Import Process Flow Data. This flag controls the import of Transport process flow data. This data comprises direct inflows and pollutant concentrations into Transport manholes.

Import Sub-area Data. This flag controls the import of Transport sub-area data. This data comprises dry weather flow generation, using catchment and land use properties to estimate water use.

Hydrograph and Pollutograph Input. This flag controls the import of Transport Hydrograph and Pollutograph input. Data comprises direct input of hydrographs and pollutant concentrations to manholes.

Storage Treatment Import

This dialog allows specific Storage/Treatment data to be imported. Generally all data should be imported, although there may be cases where some data is not required.

Import Simulation DataThis flag controls the import of the title lines, date, time, time steps and number of time steps.

Import Print Control Data. This flag controls the import of print control data. This data comprises flags controlling the amount of printout for analysis of a treatment plant.

Import Evaporation Data. This flag controls the import of Storage/Treatment evaporation data.

Import Pollutant Data. This flag controls the import of Storage/Treatment pollutant data. This data characterises pollutants and their removal from internal storage/treatment units.

Import Treatment Unit Data. This flag controls the import of treatment unit data. This data comprises the connectivity of internal units in a storage/treatment plant, with flow directions and capacities of flow paths.

Import Detention Unit Data. This flag controls the import of detention unit data. Detention units have storage associated with them.

Import Unit Cost Data. This flag controls the import of unit cost data.

Import Flow & Concentration Time Series. This flag controls the import of flow and concentration time series directly into a storage/treatment plant.

Tidy up Network

If this flag is selected the network will be optionally rearranged after import to minimise conduits crossing over one another. This option is useful; as nodes created by import are placed in an approximate grid and the network can become quite messy when the links connecting the nodes are created. The tidy up procedure works best with purely dendritic networks.

XPX Command Reference

The XPX format is described in pseudo-EBNF notation. Note that the file format is pure token stream; tokens are separated by white space, i.e. spaces, commas and/or tabs. Keywords (shown uppercase) are not case sensitive.

 xpx_file = {command}

 The XPX file consists of a series of commands with various parameters assigned to them to operate on. There are several types of XPX commands. They are: 

  1. The node command

  2. The link command

  3. The data command

  4. The global database command
  5. The global database item command

  6. The global database data command

  7. The global storm command

  8. The table command
  9. The catchment command
  10. The makemulti command
  11. The link vertex command

  12. The cross section vertex command


CONTEXT-SENSITIVE RULES:

  • Any references to objects must already be defined i.e. NODE commands must appear before LINK commands which reference them, and similarly DATA commands must appear after the object references are defined.
  • An un-named global object is defined by an empty string (“”).
  • Object names are not case-sensitive.
  • Strings with embedded white space can be enclosed in double-quotes (“).

XPX Node Command

COMMANDNode
DESCRIPTIONThe node command defining a particular node must appear in the XPX file before any reference can be made to data or links associated with it. There is no rigid structure to the order that these command appear in provided the above rule is complied with. The node_command consists of the word NODE followed by a node_type, a node_name and an X and Y value which represent it coordinates.
SYNTAXNODE node_type node_name xy
VARIABLES

Node_type (Integer). The node_type is an integer value which specifies the shape and colour the node will appear in its screen representation when the XPX file is imported. The various values and shapes for node_type are listed below. In the current implementation of XPSWMM all resulting nodes will be circular and take on the default property specified in the File->Properties… dialog. A node will automatically become triangular in shape when storage data is active.

 Node Type Shape:

0 Circle
130 Circle
132 Circle
133 Circle
134 Circle
135 Circle

Node_name (String). The node_name must be enclosed in double quotation marks. It is an alphanumeric string representing the name of this node and will appear adjacent to the screen representation of the node.

X (Real). The X value is the horizontal plane coordinate (right is positive) used to locate the node object on the screen. This value may be a real world coordinate value or simply an arbitrary value to locate the node schematically. This is a real number of up to 20 significant figures. This number must be specified.

Y(Real). The Y value is the vertical plane coordinate (up is positive) used to locate the node object on the screen. This value may be a real world coordinate value or simply an arbitrary value to locate the node schematically. This is a real number of up to 20 significant figures. This number must be specified.

 EXAMPLE NODE 134 “mh a1” 45634.945 120341.012

XPX Link Command

COMMANDLINK
DESCRIPTIONThe link command consists of the word LINK followed by the link_type which specifies its screen appearance, the link_name, the node_from and the node_to.
SYNTAXLINK link_type link_name node_from node_to
VARIABLES

Link_type (Integer). The link_type is an integer value which specifies the type of line which will be used to represent the link on-screen. The link_type will determine whether this link (link_name) represents a sinkgle conduit (solid line) or multiple conduits or diversions (dashed line). The table below specifies the valid values for link_type and there meanings.

Link_type Line type Conduit type

0 Line Single Conduit
136 Line Single Conduit
137 Boldline Single Conduit
138 Dashline Diversion/Multi Conduit

Link_name (String) The link_name must be enclosed in double quotation marks. It is an alphanumeric string representing the name of this link and will appear on the screen representation of the link.

Node_from (String) The node_from parameter must be enclosed in double quotation marks. It is an alphanumeric string representing the name of the upstream connecting node for the link specified in link_name.

Node_to (String) The node_to parameter must be enclosed in double quotation marks. It is an alphanumeric string representing the name of the downstream connecting node for the link specified in link_name.

The node_from and node_to nodes must have been specified earlier in the XPX file using the NODE comand above. A link must be specified before any dat may be defined which is associated with the link.

EXAMPLELINK 136 “Link 1” “mh a1” “mh b1”

XPX Data Command

COMMANDDATA
DESCRIPTION

The data_command is used to assign data attributes to objects (links and nodes) which have been defined earlier in the XPX file. It must begin with the word DATA and be followed by a field_name, and object_name to attach the data to, an instance , a count and data_string, the actual data being defined.

SYNTAXDATA field_name object_name instance count {data_string}
VARIABLES

Field_name (String). The data field_name is any name that is pertinent to this type of object, either a link or node. The name is not case-sensitive. The appropriate field name may be found in this reference or by using the “Get Field Info” facility in XP (using the Dialog Icon).

Object_name (String). The object_name is any quoted string which has been previously defined as a link or node using the LINK or NODE command. The data_string will be assigned to this object_name and placed in the database field called field_name. If the field_name is a global value and not associated with an object then the object_name is defined as a pair of double quotes (i.e. “”)

Instance (Integer). The instance is an integer value which allows for multiple instances of the same data type for the one object. For example, multiple conduits in one link. The first instance of a data type is assigned a value of 0 (zero). the second instance is 1 (one) and so on. For a data type which has only one instance the value will be 0 (zero).

Count (Integer). This value specifies how many data items to expect in the following data_string. Normally this is 1 (one) except for list data. For example, user inflow hydrographs have more than 1 (one) data point. If there were 25 points in the hydrograph you would specify a count of 25 and then follow with a data string containing 25 values.

Data_string (String). This is a string of value(s) which will be placed in the database field specified by the field_name string attached to the object specified by the object_name string. There must be as many data items in the data string as is specified by the value of the count variable and they must be separated by at least 1 (one) space.

EXAMPLE
/* Add a hydrograph to a node named MHA1*/
DATA TEO "MHA1" 0 5 0.0 1.0 2.0 3.0 4.0
DATA QCARD "MHA1" 0 5 0.0 21.8 63.3 44.1 1.2
 
/* Import the length of a conduit named Link1*/
DATA LEN "Link1" 0 1 135.5
 
/*set link LB3 active in HDR Mode*/
DATA LOCMODE "LB3" 0 1 1
 
/*set node MHB1 active in RNF Mode*/
DATA LOCMODR "MHB1" 0 1 1
 
/*set node MHB1 inactive in SAN Mode*/
DATA LOCMODT "MHB1" 0 1 0

XPX Global Database Command

An enhancement of this command is provided by the GLDBITEM and GLDBDATA commands, which remove the Instance dependency and instead, search on the database name.

COMMANDGLDB
DESCRIPTIONThe GLDB command is used to enter Global Database data.
SYNTAXGLDB gldb_type_name_string instance gldb_name_string
VARIABLES

gldb_type_name_string. The gldb_type_name_string is the type of global database to be imported. The string must be enclosed in double quotes (“).

Instance (Integer). The instance is an integer value which allows for multiple instances of the same data type for the one object. For example, multiple database records. The first instance of a data type is assigned a value of 0 (zero). the second instance is 1 (one) and so on.

gldb_name_string. The gldb_name_string is the record name of global database to be imported. The string must be enclosed in double quotes (“).

EXAMPLE
GLDB "Pump Ratings" 0 "Pump #1"
GLDB "Pump Ratings" 1 "Pump #2"
GLDB "Pump Ratings" 2 "Pump #3"
GLDB "Pump Ratings" 3 "Pump #4"
GLDB "Pump Ratings" 4 "Pump #5"
DATA PRATEX " " 0 3 40.000 30.000 10.000 /* Pump Param */
DATA PRATEX " " 1 3 40.000 35.000 12.000
DATA PRATEX " " 2 3 50.000 40.000 20.000
DATA PRATEX " " 3 3 60.000 50.000 40.000
DATA PRATEX " " 4 3 60.000 50.000 40.000
DATA PRATEY " " 0 3 10.000 50.000 1000.000 /* Pump Flow */
DATA PRATEY " " 1 3 10.000 50.000 1000.000
DATA PRATEY " " 2 3 10.000 50.000 1000.000
DATA PRATEY " " 3 3 10.000 50.000 1000.000
DATA PRATEY " " 4 3 10.000 50.000 1000.000

XPX Global Database Item Command

COMMANDGLDBITEM
DESCRIPTIONThe GLDBITEM command is an enhancement to the GLDB command that uses the Global Database name rather than the instance for entering the data. It provides a much easier mechanism for updating global data.
SYNTAXGLDBITEM gldb_type_name_string gldb_name_string
VARIABLES

gldb_type_name_string. The gldb_type_name_string is the type of global database to be imported. The string must be enclosed in double quotes (“).

 gldb_name_string. The gldb_name_string is the record name of global database to be imported. The string must be enclosed in double quotes (“).

EXAMPLEGLDBITEM “Rainfall” “SCS Spillway Design"

XPX Global Database Data Command

COMMANDGLDBDATA
DESCRIPTION

The GLDBDATA command is an enhancement to the DATA command that uses the Global Database name rather than the instance for entering the data. It provides a much easier mechanism for updating global data.

SYNTAXGLDBDATA field_name gldb_type_name_string gldb_name_string count {data_string}
VARIABLES

Field_name (String). The data field_name is any name that is pertinent to this type of global database. The name is not case-sensitive. The appropriate field name may be found in this reference or by using the “Get Field Info” facility in XP (using the Dialog Icon)

gldb_type_name_string. The gldb_type_name_string is the type of global database to be imported. The string must be enclosed in double quotes (“).

gldb_name_string. The gldb_name_string is the record name of global database to be imported. The string must be enclosed in double quotes (“).

Count (Integer). This value specifies how many data items to expect in the following data_string. Normally this is 1 (one) except for list data. For example, rainfall hyetographs have more than 1 (one) data point. If there were 50 points in the hydrograph you would specify a count of 50 and then follow with a data string containing 50 values.

 Data_string (String). This is a string of value(s) which will be placed in the database field specified by the field_name string attached to the object specified by the object_name string. There must be as many data items in the data string as is specified by the value of the count variable and they must be separated by at least 1 (one) space.

EXAMPLE
GLDBITEM "Rainfall" "SCS Spillway Design"
GLDBDATA R_ROPT "Rainfall" "SCS Spillway Design" 1 0 /* User defined rainfall */
GLDBDATA R_KTYPE "Rainfall" "SCS Spillway Design" 1 0 /* Constant rainfall */
GLDBDATA R_KPREPC "Rainfall" "SCS Spillway Design" 1 2 /* Cumulative Depth */
GLDBDATA R_RMULT "Rainfall" "SCS Spillway Design" 1 1 /* Rainfall Multiplier */
GLDBDATA R_HOFF "Rainfall" "SCS Spillway Design" 1 0 /* User defined rainfall */
GLDBDATA R_KTIMEC "Rainfall" "SCS Spillway Design" 1 1 /* Time Interval in Hours */
GLDBDATA R_THISTO "Rainfall" "SCS Spillway Design" 1 0.02 /* Time Interval */
GLDBDATA R_TZRDT "Rainfall" "SCS Spillway Design" 1 "1/1/2001" /* Storm Start Date */
GLDBDATA R_TZRTM "Rainfall" "SCS Spillway Design" 1 "00:00" /* Storm Start Time */

/* Rainfall Values Read Left to Right and Top to Bottom */
GLDBDATA R_REIN "Rainfall" "SCS Spillway Design" 50
0.0080 0.0162 0.0246 0.0333 0.0425 0.0524 0.0630 0.0743 0.0863 0.0990
0.1124 0.1265 0.1420 0.1595 0.1800 0.2050 0.2550 0.3450 0.4370 0.5300
0.6030 0.6330 0.6600 0.6840 0.7050 0.7240 0.7420 0.7590 0.7750 0.7900
0.8043 0.8180 0.8312 0.8439 0.8561 0.8678 0.8790 0.8898 0.9002 0.9103
0.9201 0.9297 0.9391 0.9483 0.9573 0.9661 0.9747 0.9832 0.9916 1.0000

XPX Global Storm Command  

COMMANDGLOBAL_STORM
DESCRIPTIONImports a row of the Global Storms dialog.
SYNTAX

GLOBAL_STORM storm_number enabled  “storm_name” “group_name” “return_period” “rainfall_gldb” mult_flag multiplier

VARIABLES

Field

Description

storm_number

The number of this storm. Determines where it appears in the list of global storms. May overwrite an existing storm with this number. The first storm is 0, the second 1, and so on. If set to -1, it will add this storm to the end of the list of global storms.

enabled

Determines whether this storm is enabled.

1 = Enabled

0 = Disabled

storm_name

The name for the storm. Must be in double quotes.

group_name

The storm group this storm belongs to, or “”, if no grouping is required. Must be in double quotes.

return_period

The return period. This value must be in double quotes as it is a string value.

rainfall_gldb

The name of the rainfall global database this storm uses. Must be in double quotes.

mult_flag

The override multiplier flag.

1 = Enabled

0 = Disabled

multiplier

The multiplier. A floating point number.

EXAMPLE
GLOBAL_STORM 0 1 "MyStorm1" "" "2" "RAINFALLDB1" 1 1.67

XPX Table Command

COMMAND$TABLE ..... $TABLE_END
DESCRIPTIONXPX format has been enhanced to allow the import of CSV files. The format of the file is as below: The first line signifies the beginning of the table format. The second line contains all the XP variable names. The remaining lines (except the last) contains the object name, instance of data (usually 0), index (usually 1), and then the data for each variable.
SYNTAX

$TABLE

{field_name_string}

object_name, instance, count, {data_string}

$TABLE_END

VARIABLES

Field_name_string. The field_name_string is any name pertinent to this type of object, either link or node. The name is not case-sensitive. Any number of variables can be included in the string. The appropriate field_name_string may be found by using the “Get Field Info” facility (using the Dialog Icon).

Object_name (String). The object_name is any quoted string which has been previously defined as a link or node using the LINK or NODE command.

Instance (Integer). The instance is an integer value which allows for multiple instances of the same data type for the one object. For example, multiple conduits in one link. The first instance of a data type is assigned a value of 0 (zero). the second instance is 1 (one) and so on.

Count (Integer). This value specifies how many data items to expect in the following data_string. Lists cannot be entered in a table so the Count is always 1 (one).

Data_string (String). This is a string of values which will be placed in the database field names specified by the field_name_string. There must be as many data items in the data_string as are specified by the field_name_string. They must be separated by at least 1 (one) space or comma.

EXAMPLE
$TABLE
/* , , , DS Elev, US Elev, Length, Depth, Rougnness, Width, Side 1, Side 2 */
, , , ZP1, ZP2, LEN, DEEP, ROUGH, WIDE, TTHETA, TPHI
"LA5", 0, 1, 102.0, 102.5, 300, 9, 0.015, 0.0, 3.0, 3.0
"LA6", 0, 1, 101.5, 103.0, 300, 9, 0.015, 0.0, 3.0, 3.0
$TABLE_END

XPX Catchment Command

COMMANDCATCHMENT
DESCRIPTIONThe catchment command defines a catchment polygon and links it to a node. The particular node must appear in the XPX file before any reference can be made to it.
SYNTAX

CATCHMENT “node_name” s n

for 1 to n

CatchPoly_Pt1_X CatchPoly_Pt1Y

CatchPoly_Pt2_X CatchPoly_Pt2Y

CatchPoly_Pt3_X CatchPoly_Pt3Y

CatchPoly_Ptn_X CatchPoly_PtnY

VARIABLES

Node_name (String). The node_name must be enclosed in double quotation marks. It is an alphanumeric string representing the name of this node.

s (integer). The s value is the node subcatchment number (1 – 5).

(integer). The n value is the number of vertices in the polygon.

EXAMPLE
CATCHMENT "MH11" 1 5
 
1032150 352400
1032550 352400
1032500 352700
1032300 352600
1032100 352500
COMMANDLINK_MAKEMULTI
DESCRIPTIONThis command will convert all or specific links (single conduits) to multi-links (multiple conduits). This command is useful to convert an existing closed conduit drainage network to multi-links for simulating dual drainage or overland street flows with the pipe flow. The links must already exist or be created with the link command before these appear in the XPX file. The single conduit data in the existing link is automatically entered into the first row or conduit 1 of the multi-link.
SYNTAXLINK_MAKEMULTI “existname” “newname”
VARIABLES

“existname” (String). The name of the conduit to be converted is entered after the LINK_MAKEMULTI command. The name of the Link should be surrounded by single or double quotation marks. A wildcard (*) is allowed to indicate that all conduits should be converted to multi-links.

“newname” (String). The new name to be assigned to the multi-link that will be created from the existing link. If no name is entered the multi-link will have the same name as the original link.

EXAMPLE
/* to convert all single conduits to multi-conduit elements */
LINK_MAKEMULTI "*" ""
 
/* to convert individual single conduits to multi-conduit with new name */
LINK_MAKEMULTI "Link1" "M-Link1"
 
/* to convert individual single conduits to multi-conduit with new name */
LINK_MAKEMULTI "Link1" "" 

XPX Link Vertices Command

COMMANDVERTEX_START LINK and VERTEX_END
DESCRIPTIONThis command will insert vertices on a link to create or extend a polylink.
SYNTAX

VERTEX_START LINK “link name”

X Y

X Y

VERTEX_END

VARIABLES

“link name” (String). The name of the link to add the vertices.

X and Y (String). The X and Y coordinates for the polylink. The order of the vertices is upstream to downstream.

EXAMPLE
/* To Import intermediate vertices for link */
VERTEX_START LINK "L1"
100 200
180 240
VERTEX_END

XPX Cross Section Vertices Command

COMMANDVERTEX_START LINK_CS and VERTEX_END
DESCRIPTIONThis command will insert vertices on the cross section polyline of the nominated link.
SYNTAX

VERTEX_START LINK_CS “link name”

X Y

X Y

VERTEX_END

VARIABLES

“link name” (String). The name of the link to add the vertices.

X and Y (String). The X and Y coordinates for the polylink. The order of the vertices is upstream to downstream.

EXAMPLE
/* To Import intermediate cross section layout vertices for link */
VERTEX_START LINK_CS "L1"
100 200
180 240
VERTEX_END

Export XPX Data

Data may be written to a text file in an XPX format using this option. For each variable group to be included, click on the check box. Then select either the Selection or the All Variables radio button.

Object Selection

All Objects. All objects (links and nodes) in the network will be exported.

Selection Only. Only the objects (links and nodes) in the currently highlighted selection will be exported.

Variable Selection

Data variables may be exported for links, nodes, Job Comtrol or, Global Databases. Use the controls to add variables from the list in the left panel to the right panel.