SEPTA Alerts feed contains null last_updated dates.

25 views
Skip to first unread message

Daniel Watson

unread,
Mar 30, 2018, 12:29:05 PM3/30/18
to SEPTAdev
Hey Septonians,

I had to make a rush SEPTA Instant fix in the last few days (i wasn't sanitising enough) and I tracked it down to *some* detour alerts having null last_updated dates in the alerts feed http://www3.septa.org/hackathon/Alerts/get_alert_data.php?&req1=all . It suddenly started happening 2 days ago. (on the 28th).

This makes it impossible for what was an already challenging job of comparing potentially new or stale alerts against previously catalogued alerts. Simply using a "new date()" would defeat the purpose of comparison (it would mean every alert with a null date would be marked as "fresh").

Many thanks for looking into this!
Daniel
 

Greg Apessos

unread,
Mar 30, 2018, 1:03:29 PM3/30/18
to SEPTAdev
Sorry about that Daniel.  This seems to be an issue when new routes are added with no previous updated.  If we replaced the rare null with 'Dec 31 1969 19:00PM', would that be make things easier on your end?

Daniel Watson

unread,
Mar 30, 2018, 1:56:48 PM3/30/18
to 'Webmaster At RideSchedules' via SEPTAdev
Hi Greg, thanks for the fast reply.

It makes sense only if when "new" alerts come in, then get updated to be a real current date, which i assume it would be as the route wouldn't be new anymore?

Many thanks!
Daniel

--
You received this message because you are subscribed to the Google Groups "SEPTAdev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to septadev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages