TRK Info

Getting Information from the TRK file                          Help Home

TRK Info - This option will open any TRK file and extract information concerning the track on this route. The file access is read-only and will not harm the original TRK file.  A file by the name of "<map name> TRK.txt" is created in the analyzed map folder.

The first portion of the file presents all the track connection points - vertex to vertex - such as from 34 to 35, a binary flag word (containing information such as 'straightened', 'direction', and the like), and the track KUID of that connection.

For Example:

<map name> TRK.TXT

Entry #:  14  - KUID 12345 : 67890 
     Type: tkSt
     ? =  24  ? =  4  Vertex 0 =  482  Vertex 1 =  358
     KUID 12345 : 67890 
     Flag =   0

     Addl info:  Rusty Rail NG sandy-base ; track

In the above example, the track movement is always from Vertex 0 to Vertex 1.  The vertex number referred to is found in the second part of the file described below.  There may be two entries under 'Type'; either "tkSt" or "tkBr".  The "tkSt" refers to "track stretch" and "tkBr" refers to "track bridge".  The tkBr entry will define which tracks are associated with (and running OVER) the bridge.


The 'Addl info;" field contains information obtained from either the built-in file or any KUID folders appearing in the \downloads folder.


For types of "bridge" the entry looks like this:


Entry #:  42  - KUID 12234 : 32100 
     Type: tkBr
     ? =  88  Ver: 2.4 Vertex 0 =  83  Vertex 1 =  85
     KUID 12234: 32100
     Flag =  16
     Addl info:  5t.wood; bridge
     tkSt1ID1:43  tkSt2ID2:44  tkSt3ID3:45  tkSt4ID4:46  tkSt5ID5:41 
     Vert0-1:86  Vert0-2:88  Vert0-3:90  Vert0-4:92  Vert0-5:94 
     Vert1-1:87  Vert1-2:89  Vert1-3:91  Vert1-4:93  Vert1-5:84


Notice that the additional information describes this as a "5t wood".  The Entry Numbers for the 5 types of track are listed as "tkStID1" through "tkStID5".  In this case, four of the Entry Numbers follow the "bridge" entry while tkStID5's value of 41 leads this entry.. 


The second part of the file will give you information on each vertex such as its precise location on which board it appears (Origin.H & Origin.V), and the X, Y, and Z (Horizontal, Vertical, & Height) on the specifically identified board.

For Example:

Vertex Number:  1114   Type: tkVx
     ? = -2  ? = -1
     <WC Type> =  3
     Origin.H = -3   Origin.V = -1
     Vtx X = 220.00  Vtx Y = 210.00  Vtx Z = 00.00
     Attach 1 =  1547   Side =  0      Attach 2 =  1008   Side =  1
     Attach 3 =  1113   Side =  1      Attach 4 =  854   Side =  1
     Junction Rotation =   0 < /FONT >


In the above example, the 'Type' is "tkVx" which is a vertex point.  "WC" refers to the World Coodinate system type ("3" in this case) and the Origin.H and Origin.V refer to the board on which the vertex resides.


Boards are numbered beginning at the original "first board" which is 0,0.  The numbers are given as N/S <comma> E/W. Boards moving South are numbered positively, and boards moving North are numbered negatively.  In a similar manner, boards moving West are negative and boards moving East are positive. 


The vertex X, Y, and Z values refer to the N/S, E/W, and Height position of the vertex point on an individual board.  The upper left of any board is the 0.00 of both X and Y while the lower right becomes 720.,720. Numbers are reported as X (vertical) <comma> Y (horizontal) while viewing the board with North at the top.


In the case of rails splitting, a track may have up to 4 'Attachment points'.  The attachment points refer to the first portion of the file and their "Entry #".  In this example, Attach 1 refers to Entry number 1547, and so on.  The "Side" is a bit difficult to describe and is only important for junctions or non-symmetrical track types such as bridges, catenary, and the like.  The entering 'TrackStretch' is on Side 0 and the exiting 'TrackStretch' is on Side 1.  The 'TrackStretches' are attached clockwise around the vertex.  Unused attachment points are marked with a '-1'.


As you can see, there are a few fields that I have yet to decode, but the rest are good information.