kona314 / transit-fedilerts Goto Github PK

Agency name: Lane Transit District
City/region/other locality: Lane County, Oregon (primarily the Eugene-Springfield area)
Link to alerts feed docs/info (if known):
https://www.transit.land/feeds/f-ltd~rt (not official but I couldn't find any official docs from LTD)
Other comments/discussion:
Seems to have multiple feeds rather than one?

I believe service alerts are published for each line.

Noting this as an issue because it's on the roadmap, and because it currently results in some weird user experience.

I'm using Mastodon at https://a2mi.social and I want to inspect the new CTA feed (plugins yay!). Steps here:

• Search for @[email protected] in search box
• At https://a2mi.social/@[email protected] there is a result but no timeline to view
• "Older posts from other servers are not displayed." Browse more on the original profile
• Select the "browse more"
• Cannot GET /u/cta at https://transit.alerts.social/u/cta

I think these both are minor but worth noting, referencing https://transit.alerts.social/u/theride_aata added at #1 :

1. The terms of service for use of this data is at https://www.theride.org/business/software-developers and reads

Should you use the Data for any purposes, you agree to provide the following legend, prominently displayed: "Transit scheduling, geographic, and real-time data provided by permission of AAATA/TheRide" unless otherwise agreed by AAATA/TheRide in writing. Other than displaying this legend, you are not authorized to make any use of any proprietary service marks of AAATA/TheRide, including the AAATA/TheRide logo, or any confusingly similar variant thereof.

I would suggest that the legend referenced above go on the header for the page https://transit.alerts.social/u/theride_aata where "Automated service alerts for TheRide AATA" is currently listed.

2. The feed name "theride_aata" is not current and correct - the old name "AATA" ("Ann Arbor Transportation Authority") was replaced by a new name "AAATA" ("Ann Arbor Area Transportation Authority") in 2013 after a new millage included several neighboring communities including Ypsilanti, MI.

https://www.annarbor.com/news/ann-arbor-agrees-to-ypsilantis-request-for-membership-in-aata/

A number of the alerts on the Muni feed are for stop relocations, and the message alone doesn't give enough information to show which stop was relocated:

In this case, the Entity Selector attached to the GTFS-Realtime alert probably contains a stop_id, which could be looked up in the static GTFS dump to get the stop name, and add that to the toot.

Agency name: Valley Metro
City/region/other locality: Maricopa County, AZ (Phoenix, Tempe, Chandler, and more.)
Link to alerts feed docs/info (if known):
GTFS-RT URL: https://app.mecatran.com/utw/ws/gtfsfeed/alerts/valleymetro?apiKey=4f22263f69671d7f49726c3011333e527368211f&asJson=true
More documentation: https://www.phoenixopendata.com/dataset/general-transit-feed-specification (linked from Valley Metro's website: https://www.valleymetro.org/contact/developers-resources)

Other comments/discussion: Valley Metro is a really generic name. I wonder if you want to use that or some locality-prefixed name like 'phxvalley` 😆 .

I found this project through mastadon and I've been poking around the last few days. I have a few ideas that might help streamline getting other developers up and running that I've prototyped on my local branch. I'd be happy to submit a PR if you're interested. Specifically I've played with and considered

• Adding https://github.com/nodkz/mongodb-memory-server as a dev dependency to streamline the mongodb setup and installation
• Dropping SSL cert requirements when running locally
• Setting the DOMAIN to localhost:8080 when running locally

Let me know if what you think.

Hey, thanks for this project! It may already be on your list somewhere, but it’d be great to get a TriMet account following their GTFS data. TriMet serves the greater Portland Metro area. Documentation is available here: https://developer.trimet.org/GTFS.shtml

Agency name: TransLink
City/region/other locality: Metro Vancouver, BC, Canada

Link to alerts feed docs/info (if known):

• GTFS Real-time documentation: https://www.translink.ca/about-us/doing-business-with-translink/app-developer-resources/gtfs/gtfs-realtime

• Requires registering for an API key: https://www.translink.ca/about-us/doing-business-with-translink/app-developer-resources/register

• Other developer resources: https://www.translink.ca/about-us/doing-business-with-translink/app-developer-resources

I realize that over time it might be hard to run this for every transit agency!

AAATA (aka "The Ride") serves the Ann Arbor area. Their data information is at

https://www.theride.org/business/software-developers

It looks like they have both a GTFS feed and an API. Is it possible to implement your alert system with this, or is more info or more data needed?

Eventually I'd hope for a bot to serve the a2mi.social Mastodon instance.

The TriMet feed seems to include messages to operators which are not particularly well suited to regular consumers of alerts, and mostly end up just adding to noise and generating so many messages it's hard to follow the feed for its AP account.

I would expect the types of messages posted to this feed to more or less match those types of messages that are passed through TriMet's Twitter feed, e.g., https://twitter.com/trimetalerts

Examples:
https://transit.alerts.social/o/6447f3679b136eac97572961
https://transit.alerts.social/o/64483e679b136eac97572af1
https://transit.alerts.social/o/6448919c9b136eac97572d3d
https://transit.alerts.social/o/6448b8489b136eac97572dc5
https://transit.alerts.social/o/644551929b136eac97571e00

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