CM-010-V1-EN
When importing a Dataset file into Optibus, it must adhere to the following conditions:
Be an Excel (.xlsx or .xls) file
Contain the sheets Trips, Places, and VehicleTypes
In this article, we will go over some dataset-specific errors and issues that you may encounter during import and show how to solve them.
The Excel workbook you imported must contain one of the following sheets: BusTypes,VehicleTypes
Probable root cause
The Excel is missing one of the mandatory sheets.
Solution
Add the missing sheets so that the Excel file includes Trips, Places, and VehicleTypes.
Service IDs Error
Probable root cause
If you are getting an error message saying should have required property ‘service_ids’ it could be due to trying to import a dataset with the Parameters tab.
Solution
Remove the Parameters tab and re-import.
Enabling mid-route reliefs
To enable mid-route reliefs, you need to make sure of the following:
The StopTimes tab is populated.
You have added the mid-route reliefs per route to the ReliefPoints tab.
TypeError: Cannot read properties of undefined (reading ‘sort’)
Probable root cause
This error is caused by an improperly structured dataset. This can be due to missing columns or columns that are not properly populated.
It can be caused, for example, if you have the Service IDs and Service Name column headers but they are filled with empty or invalid data.
Solution
Check if the structure and content of the sheets are correct, then re-import.
Missing Service IDs when importing
Probable root cause
Unnecessary data is included in the dataset file
Solution
Delete the Service IDs and Service Name columns and sheets from the dataset that are not necessary. Try again with just the Trips, VehicleTypes, Places, Stops, and StopTimes sheets.
TypeError: Cannot read property ‘id’ of null
Probable root cause
The Alternative column in the Trips sheet contains a dash ('-') for the main pattern.
Solution
Delete the '-' from the main pattern so that the cells are left blank.
All stops are set as timepoints after importing
Probable root cause
Timepoint data was misconfigured in the StopTimes sheet
Solution
Go to the StopTimes sheet and make sure timepoints are set to TRUE and non-timepoints are set to FALSE in the Time Points column.
Misconfigured day offset
Probable root cause
The Day Offset column is used to keep trips that start after midnight on the same day for trips that are written in a 24-hour format.
For example, a trip that starts at five past midnight and ends at 10 past midnight, the two options to format the times are:
00:05-00:10, day offset field set to: '1'
24:05-24:10, day offset field set to: '0'
If you used day offset '1' on the second option, you will get an error.
Solution
Make sure that the day offsets are set correctly.
Patterns only contain 1 stop
Probable root cause
You might import a dataset but some alternatives/patterns are 0 km due to only having 1 stop. This could be caused by Trip IDs not matching between sheets.
Solution
Check in the StopTimes sheet that the Trip Id is the same for the whole trip when indicating the sequence. For example, if there is an empty space at the beginning it will not be recognized as part of the sequence and therefore the import might only contain one stop.