So...
I try to explain AIBTC and the three source files.
The three source files must always be named as follows, where the * is a placeholder for own characters.
It doesn't matter if a space, underscore, letter or number is used.
Only the following characters must be the same for all three files, so that AIBTC can assign these files.
Now for an explanation of the individual files and their structure using an example...
Boats*.txt (The Boats*.txt is quite simple in structure)
Code:
AC#1,30,"VEH_Larrys_schoolbus"
- AC#1 –>introduce the id number of this entry...
- 25 –>is the boat / vehicle / animal speed...
- VEH_Larrys_schoolbus –> is the model name. The model name could be found in the sim.cfg...
Plans*.txt (This is where it gets more difficult now)
Code:
AC#1,Car,1%,1Hr,00:00:00,00:01:25,99999,normal,ferry,00:30:00,00:31:25,99999,reverse,ferry
- AC#1 –> define the boat model identifier. Use the same identifiers as specified in Boats.txt
- Car –> is the vehicle name. It is not displayed or used by the traffic, but could help to distinguish plans. Avoid punctuation marks and use no more than 10 leters.
- 1% –> is the minimum traffic percent that must be configured to see this vehicle in the simulator
- 1Hr –> is the repeat frequency. You can specifiy it as a number of hours or weeks
In each order, a departure time is given. The departure is relative from the start of the period. If a vehicle has a 4 hours periods, then an order that starts at 1:45 will be repeated at 5:45, 9:45, 13:45, 17:45, and 21:45 each day.
Since one must consider the return journey with, only 1/2/4/6/8/10/12 or 24 hours periods make sense!
The further timetable consists of 5 comma-separated fields in each case for the outward and return journey:
In my example above this means...
00:00:00,00:01:25,99999,normal,ferry
- 00:00:00 --> Start time of the outward journey.
- 00:01:25 --> Arrival time of the outward journey, the duration of the travel time results from the speed of the vehicle and the length of the distance traveled. The arrival time is recalculated by the AIBTC.
Therefore always check the times before using the Traffic*.bgl if they are still in the travel period, so that it does not come to misrepresentations.
-99999 --> is the route number as defined in the file "Boats.KML". Only numeric identifiers are supported
- normal --> The fourth field is a value indicating the direction of travel on the route. If it is marked with "reverse", then the route is driven from the last point to its first point.
- ferry --> The last flag concerns the terminal parking type. A vehicle marked with FERRY will stop at the end point of the route. The default behavior is cargo, with deiser route definition the vehicle is made to find a parking place on a circle around the end point.
The further entries are for the return trip and have the same meaning as the outward trip.
For the return trip, use the same route number!
Furthermore, one vehicle, one schedule, one route, one Traffic*.bgl, as for each vehicle its own route and its own schedule!
What is still important, all times are GMT (UTC+0) times!
So when testing it is best to change the simulator to UTC time.
Routes*.kml
I use the following template for this and only change the coordinates and the name for new routes (which I create with Google Earth).
Code:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<kml xmlns="http://earth.google.com/kml/2.0">
<Document>
<name>File created with kml.KMLWriter</name>
<Placemark>
<name>99999</name>
<Style>
<LineStyle>
<color>ff0000ff</color>
<width>2</width>
</LineStyle>
</Style>
<LineString>
<tessellate>1</tessellate>
<coordinates>-96.66120783425868,33.74163821331267,0.0
-96.6612636577338,33.741989151898416,0.0
-96.66104690171778,33.74420276451621,0.0
-96.66108227334918,33.74631739445597,0.0
-96.66077231056988,33.7468213062714,0.0
-96.65975357405841,33.74714524958132,0.0
-96.65886090137064,33.74631739445597,0.0
-96.65861246176064,33.74532756767566,0.0
-96.65865579620005,33.742727022771014,0.0
-96.65870239958168,33.742196115679754,0.0
-96.65883030742407,33.741836178668734,0.0
</coordinates>
</LineString>
</Placemark>
</Document>
</kml>
You can save this file as txt file and after changing the coordinates/route number change txt to kml.
Routes*.kml -> the format mainly used by AIBTC is the GoogleEarth KML format. It can be viewed and edited with free versions of Google Earth, so it is more convenient to use this format for routes.
KML is more stable than KMZ.
The path name stored in Google Earth is used as the route identifier. If a name is not numeric, the route is skipped and cannot be used for defining plans.
Path information other than latitude and longitude is not used. If errors occur with KML files, it is recommended to remove all style information and keep only the point coordinates.
Therefore, I always use my template.
Paths in Google Earth are displayed undirected, but the direction is from the first point added to the last point.
If my example files are used, then the school bus departs on a route every hour in TE68.
Half an hour later it starts the return journey.
I hope to have shed some light on AIBTC.
