|
To import a TransCAD highway network and/or a TransCAD transit network into TRANUS, they must first be converted to a link (*.links), node (*.nodes), route (*.routes), and operator (*.opers) based text files. This can be accomplished using the TransCAD export utility for EMME/2 networks.
- First open the route system in question. Opening the route system in TransCAD will also open the associated line layer for the highway system.
- Map - Layers – Show – Network Endpoints
- With the network endpoints as your active layer - Selection – Select by condition – “type in the formula that is specific to your line layer in order to create a selection set of the centroid nodes” – Set Name = Centroids
- Planning – Import Planning Data – Export to EMME/2 Batchout…
- A dialog box will be displayed – the data table attribute fields are not one-to-one so the user must specify the fields. I have provided suggested equivalencies for the TransCAD to EMME/2 conversion in Table 1 for links, Table 3 for nodes, and Table 6 for transit.
- The key fields to match for the highway export are LINK ID, DIR and CAPACITY. TRANUS also requires ORIGIN NODE, DESTINATION NODE, and DISTANCE, but there is no need for the user to specify these values as they are automatically exported by the export utility. Other fields available in TransCAD and desired in TRANUS can be specified simply by developing an equivalency between the different specified fields in EMME/2.
- The key field for the nodes is the centroids. Through the centroid selection set, the EMME/2 export will automatically recognize centroid nodes. The node ID, X coordinate, and Y coordinate will automatically be specified by the export utility
- The key fields for transit are FROM NODE, TO NODE, ROUTE, MINFREQ, and MAXFREQ. The node data is automatically exported by the export utility. Other fields can be specified by setting up equivalencies between the available data fields in TransCAD, the fields exported for EMME/2, and the fields needed for TRANUS.
- NOTE: IF YOU WANT TO MAINTAIN THE SHAPE OF YOUR TRANSIT ROUTES, DO NOT SELECT “USE STOPS”
- NOTE: Be sure to specify the appropriate coordinate system
HIGHWAY
This utility will create a highway data text file with node data records at the top and link data records at the bottom. The data file can be imported into Excel using a space delimited import. The user can then create one worksheet for the node data and one worksheet for the link data. The order of the data will be:
§ Node Data – NODE ID, X, Y
§ Link Data – ANODE, BNODE, DIST, followed by the data fields as specified in your TransCAD export
The data fields should be cleaned such that data field names and data field order match the input requirements of TRANUS. See Tables 2 and 4 for equivalency between link and node data fields. Once this editing is complete, each of the worksheets can be saved as separate comma delimited files (*.CSV). Before attempting to import into TRANUS, the extension for the link data should be change to “LINKS” and the extension for the node data should be changed to “NODES”.
If turn penalties are required, you must convert TransCAD link based table to a node based table. Use the TransCAD graphical interface with the line layer open with penalty links selected and node layer open and nodes labeled to create a node based penalty file. See Table 5 for required format.
TRANSIT
The utility will also create a transit data text file with a data record for each transit route. The data record will include the route name, data as specified by the user (this will be in the EMME/2 format), and a list of nodes upon which the transit runs. The first line of each output record contains the operator data and following lines contain the route data. Use Excel to import the data using a space delimited command and specifying a text qualifier ‘.
Copy all operator records to a blank worksheet and format as required by TRANUS. Name the worksheet OPERATORS. The order of the data will be:
§ Operator Data – ID, NAME, DESC, OPERATOR, MINFREQ, MAXFREQ, TARGOCC, MAXFLEET, SCHED
Copy all route data records (i.e. list of nodes) to a blank sheet and format as required by TRANUS. Name the worksheet ROUTES. The order of the data will be:
§ Route Data – FROM, TO, ROUTE, CODE (Where FROM is the “from node,” TO is the “to node,” and ROUTE is the route number)
Note that TRANUS requires the nodes to be in FROM/TO format rather than the node list used by EMME/2. To transpose the node list to a FROM/TO format:
§ Highlight the node list for the route
§ Copy
§ Paste into a new worksheet using Paste Special – Transpose (this will give you the “From” node)
§ Starting at the second node for the route, copy to last node and then paste in next column starting at the row for the first node (this will give you the “To” node)
§ This leaves an orphan node at the bottom of the “From” node list – simply delete this node as it is taken care of in the “To” node list
§ Fill in values for route number and code
§ Repeat this process for all routes
Once this editing is complete, each of the worksheets can be saved as separate comma delimited files (*.CSV). Before attempting to import into TRANUS, the extension for the operator data should be change to “OPERS” and the extension for the route data should be changed to “ROUTES”.
IMPORT TO TRANUS
Create a new scenario in TRANUS and import the nodes, links, opers, and routes through the project – import network command.
Table 1: Network Equivalency Table for going from TransCAD to EMME/2
|
TransCAD Field |
Match to EMME/2 field |
|
Line Layer |
[LINE LAYER] |
|
USER SPECIFIED |
[MODES] |
|
USER SPECIFIED |
[TYPE] |
|
USER SPECIFIED |
[LANES] |
|
CAPACITY |
[VDF] |
|
ID |
[UI1] |
|
DIR |
[UI2] |
|
USER SPECIFIED |
[UI3] |
|
N/A in link data table |
ANODE * |
|
N/A in link data table |
BNODE * |
|
Automatic export – no need for user to specify field |
DIST * |
* Fields automatically output by export utility.
Table 2: Network Equivalency Table for going from EMME/2 to TRANUS
|
EMME/2 field |
Match to TRANUS field |
|
[UI1] |
LINK ID |
|
ANODE * |
ORIGIN ID |
|
BNODE * |
DESTINATION ID |
|
[UI2] |
DIR |
|
USER SPECIFIED |
LINK-TYPE ID |
|
DIST * |
DISTANCE |
|
[VDF] |
CAPACITY |
|
USER SPECIFIED |
“NAME” |
|
USER SPECIFIED |
“DESCRIPTION” |
|
USER SPECIFIED |
OTHER |
* Fields automatically output by export utility.
Table 3: Node Equivalency Table for going from TransCAD to EMME/2
|
TransCAD Field |
Match to EMME2 field |
|
User specified selection set with centroid nodes |
CENTROIDS |
|
USER SPECIFIED |
[UI1] |
|
USER SPECIFIED |
[UI2] |
|
USER SPECIFIED |
[UI3] |
|
USER SPECIFIED |
[LABEL] |
|
Node ID is automatically output by the export utility, no need for user to specify. |
ID* |
|
Longitude output by export utility. |
X* |
|
Latitude output by export utility. |
Y* |
* Fields automatically output by export utility.
Table 4: Node Equivalency Table for going fromEMME/2 to TRANUS
|
EMME2 field |
Match to TRANUS field |
|
ID* |
ID |
|
X* |
X |
|
Y* |
Y |
|
[CENTROIDS] |
ZONE |
|
[UI1] |
OTHER |
|
[UI2] |
OTHER |
|
[UI3] |
OTHER |
|
[LABEL] |
OTHER |
* Fields automatically output by export utility.
Table 5: TURNS Equivalency Table
|
TransCAD Field |
Match to TRANUS field |
|
FROM ID (needs to be node) |
FROM |
|
TO ID (needs to be node) |
THRU |
|
N/A |
TO |
|
PENALTY |
DELAY |
Table 6: Transit Equivalency Table for going from TransCAD to EMME/2
|
TransCAD Field |
Match to EMME2 field |
|
ROUTE SYSTEM |
ROUTE LAYER |
|
Routes to be exported |
SELECTION |
|
USER SPECIFIED |
MODE |
|
USER SPECIFIED |
VEHTYPE |
|
USER SPECIFIED |
HEADWAY |
|
USER SPECIFIED |
SPEED |
|
USER SPECIFIED |
DESCRIPTION |
|
USER SPECIFIED |
UT1 |
|
USER SPECIFIED |
UT2 |
|
USER SPECIFIED |
UT3 |
|
USER SPECIFIED |
TTF |
|
USER SPECIFIED |
DWELL |
|
USER SPECIFIED |
LAYOVER |
|
DO NOT USE STOPS |
|