search

kona314 / transit-fedilerts

ActivityPub-compliant server for distributing transit service alerts
36 stars 0 forks source link

TriMet: All messages about blocking trains are dated 2018-11-16 #8

Open downeymj opened 1 year ago

downeymj commented 1 year ago

This is a strange one. For the TriMet feed, any post that is related to a blocking train arrive in my Mastodon instance with a published date of 2018-11-16 at 18:50, regardless of when they are sent and arrive. They are commingled amongst other messages that have the current date/time. This has been happening since the TriMet data source was added.

Some examples: https://transit.alerts.social/o/6446a1e79b136eac97572217 https://transit.alerts.social/o/6446a1e79b136eac97572219 https://transit.alerts.social/o/64453a229b136eac97571da6

kona314 commented 1 year ago

Alerts are "as-is" from TriMet's GTFS-realtime alerts feed, which for some reason is dating them that way. I couldn't tell you why that is but can forward the question to them for investigation.

On the project side, I could set it so dates more than e.g. 1 year in the past are ignored and replaced with "now," which may help band-aid the situation, but I'd prefer to fix the problem at the source if possible.