Open mraross opened 2 years ago
The sample schedules that Graeme created were only configured (in the mocked-up ferries gtfs data) to be valid until the end of 2020. If you just want the same schedules as before (which have not been validated in any way for a year or more) then the dates in the file calendar.txt in the /gtfs subdirectory of the router data directory can just be incremented by a year or two.
I see that the calendar.txt on our dev server was updated in January to extend the valid period to 2022. I'm not sure if we send you the gtfs folder ever? Here is the updated file. calendar.txt
I updated the calendar file in January because those dates had just expired. I send Brian the gtfs folder monthly in the router input package, so DataBC has been receiving this change. There must be an issue with how it is getting deployed to the router startup directory.
In demo app in prod, enter Victoria and Vancouver then turn on ferries layer and click on Swartz Bay ferry terminal as follows:
It says Schedule: Unknown which means the router can't find a schedule for that ferry. Graeme tried it on their version of the demo app and it found a schedule.
Look in directions at the ferry instructions as follows:
It says wait for 10 minutes for the ferry which is what it always says when it doesn't know the schedule.
This affects TransLink Route Planner as well.