Problems with Ferry feed


#1

Hi @alejandro.felman,

there seems to be a problem with the Ferry data, the F3 and F4 calendar does not match the trips.


#2

Hi @Halfabee, can you please provide a specific example so we can investigate further?

Thanks,
Alex


#3

I could not find this in the calendar update I did this morning.

“trip_id”:“DH114-3422”

and if you look at @jxeeno website https://anytrip.com.au/map
some of the ferries are showing as null.


#4

I’m still in the process of loading this morning’s static dataset. It failed this morning :frowning:

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.


#5

@Halfabee should all be matching fine on the AnyTrip map now


#6

Thanks @jxeeeno

I had the calendar update at 4:00am, which seemed to be working fine until today.

I will add some more error checking.


#7

You can also periodically make HEAD requests to the API and check the Last-Modified header entry to see if the file has changed :slight_smile:


#8

Thanks I will do that. @jxeeno

The other problem I had with the calendar is overlapping dates. @alejandro.felman
This seems a bit odd.

service_id,monday,tuesday,wednesday,thursday,friday,saturday,sunday,start_date,end_date
2816,0,0,0,0,0,1,0,20161212,20170930
2820,0,0,0,0,0,1,0,20161212,20170930
2846,1,1,1,1,0,0,0,20161212,20170930
2848,0,0,0,0,1,0,0,20161212,20170930
2850,0,0,0,0,0,1,0,20161212,20170930
2852,0,0,0,0,0,0,1,20161212,20170930
3072,0,0,0,0,0,1,0,20170127,20170930
3154,1,1,1,1,1,0,0,20170505,20170930
3164,0,0,0,0,0,1,0,20170505,20170930
3168,0,0,0,0,0,0,1,20170505,20170930
3176,0,0,0,0,0,0,1,20170505,20170930
3178,0,0,0,0,0,0,1,20170505,20170930
3180,0,0,0,0,0,0,1,20170505,20170930
3196,1,1,1,1,1,0,0,20170509,20170930
3422,1,1,1,1,1,0,0,20170627,20170930
3424,0,0,0,0,0,1,0,20170627,20170930
3426,0,0,0,0,0,1,0,20170627,20170930
3428,0,0,0,0,0,0,1,20170627,20170930
3430,0,0,0,0,0,0,1,20170627,20170930
3436,1,1,1,1,1,0,0,20170626,20170930
3438,1,1,1,1,0,0,0,20170626,20170930
3440,0,0,0,0,1,0,0,20170626,20170930
3452,1,1,1,1,1,0,0,20170627,20170731


#9

Ok, I understand the calendar, I think more sleep is needed. :wink:


#10

More questions.

How do you deal with fridays when they are on the same route and friday is set for two service id’s?


#11

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.


#12

Hi @jxeeno, @Halfabee, we’ll look into it. Thanks