there seems to be a problem with the Ferry data, the F3 and F4 calendar does not match the trips.
Hi @Halfabee, can you please provide a specific example so we can investigate further?
I could not find this in the calendar update I did this morning.
I’m still in the process of loading this morning’s static dataset. It failed this morning
But looking at the raw dataset, the trip seems to match fine:
$ grep 'DH114-3422' ferries/trips.txt DH,3422,DH114-3422,Circular Quay,,1,3422-1005,DH114,1 $ grep '3422' ferries/calendar.txt 3422,1,1,1,1,1,0,0,20170627,20170930
Note that the ferry bundle is updated after ~5am daily.
I had the calendar update at 4:00am, which seemed to be working fine until today.
I will add some more error checking.
You can also periodically make
HEAD requests to the API and check the
Last-Modified header entry to see if the file has changed
Thanks I will do that. @jxeeno
The other problem I had with the calendar is overlapping dates. @alejandro.felman
This seems a bit odd.
Ok, I understand the calendar, I think more sleep is needed.
How do you deal with fridays when they are on the same route and friday is set for two service id’s?
I think this may be a flowover issue from the Barangaroo wharf opening?
@alejandro.felman can we look into this? It results in some F4 services showing as duplicates. Trips with service_id 3422 are not reported in the real-time feed so I presume those are the incorrect ones.
This issue affects other real-time apps too.