Building a .lin file from .shp file is available from Files > Tools > Build PT Lines from Shp…:

Two data layers are needed to accomplish this task:

• A Shape File containing the shapes of the transit lines
• A CUBE Binary network file (.net)

Note: the shape file needs to be projected accordingly to the NET file coordinate system to have correct alignment between the two layers.

The DBF table associated to the input Shape File must have a NAME field for the line name (unique identifier). If there are multiple shapes with the same line name, the program will automatically append a number to the line name, to make them unique lines in the output .lin file.

Other line fields are optional, but if they are named as below, they will be transferred to the matching Voyager line level keywords:

• LONGNAME, ALLSTOPS, COLOR
• HEADWAY1, HEADWAY2, HEADWAY3, HEADWAY4, HEADWAY5
• HEADWAY_R1, HEADWAY_R2, HEADWAY_R3, HEADWAY_R4,HEADWAY_R5
• MODE, ONEWAY, OPERATOR, RUNTIME, TIMEFAC, XYSPEED,LAYOVER
• CIRCULAR, FARESYSTEM
• VEHICLETYP, SEATCAP, CRUSHCAP, FMCAPACITY, LOADDISTFA,CROWDCURVE
• USERN1,USERN2,USERN3,USERN4,USERN5
• USERA1,USERA2,USERA3,USERA4,USERA5

Once the input .shp file has been updated with the unique line names, the following steps should be accomplished to convert the shapes to .lin:

1. Open the .net file in the CUBE Network window.

2. Add the polylines layer with the PT services shapes .shp:

3. Escalate the .shp layer as top layer as below:

4.Select Files > Tools > Build PT Lines from Shp…

5.Save the .lin file as .lin file.

6.Select the tolerance and Unconnected Nodes if that will be used.

7.Check the report. Note: the report can be saved as TXT for automatic processing and checking of the consistency with the data.

8. Add the transit layer to the network for visually check consistency (depending on the original alignment with the network nodes).