Hi, My open source nonprofit has written a server endpoint which converts the MTA API to Gtfs-rt for vehicles.
The urls are
https://kactus.catenarymaps.org/gtfsrt/?feed=f-mta~nyc~rt~lirr&category=vehicles and
https://kactus.catenarymaps.org/gtfsrt/?feed=f-mta~nyc~rt~mnr&category=vehicles

We're updating it every 500ms or less. We wrote the code in Rust. https://github.com/CatenaryMaps/kactus-gtfs-rt/blob/main/src/conversions/nyc_rail.rs

You can confirm the data accuracy here:
https://kactus.catenarymaps.org/gtfsrtasjson/?feed=f-mta~nyc~rt~lirr&category=vehicles&raw=true
https://kactus.catenarymaps.org/gtfsrtasjson/?feed=f-mta~nyc~rt~mnr&category=vehicles&raw=true

Should we add this in?

A longer term fix for #171

When I am compiling the real-time departures from the BART feeds, I only see the scheduled departures but haven't seen the real-time departures. Is the GTFSRT aspx file provided by BART broken or is it outdated?
ASPX file: https://api.bart.gov/gtfsrt/tripupdate.aspx

Hey, Transitland is an amazing product! I made a web visualization and someone on Reddit mentioned missing GTFS feeds:

• Corpus Christi, TX: https://www.ccrta.org/gtfs-feed/
• Omaha, NE: https://iowa-gtfs.com/ (not sure if this is an official source)

I see that you're transitioning from v1 to v2. Is there a way I can add new feeds to this repository?

On transitland feed registry, we can see : "The Feed Registry is now powered by Distributed Mobility Feed Registry files in the Transitland Atlas. Transitland Atlas is open to edits and additions from all on GitHub."

When we look at "SNCF" operator (https://transit.land/feed-registry/operators/o-u-sncf), data used is not accurate : we only have a specific region dataset (Pays de la Loire / PDL) instead of the national one.

But in this Transitland Atlas repository, the feed is right and points to the valid nation-wide regional trains dataset of SNCF : https://github.com/transitland/transitland-atlas/blob/master/feeds/data.sncf.com.dmfr.json

Isn't Transiland really synchronized with Transitland Atlas right now ? How to fix Transitland for this dataset ?

Best regards
Arnaud

Hello, Just writing to inform that all the feeds for 'Transport for Ireland' public transit GTFS feed URLs have been updated. The new ones can be accessed here: https://www.transportforireland.ie/transitData/PT_Data.html

I think this is an error?

There might be an error in the metadata for Via Rail. In https://github.com/transitland/transitland-atlas/blob/main/feeds/viarail.ca.dmfr.json I can see "id": "f-f-viarail~traindecharlevoix", "onestop_id": "o-f2m-traindecharlevoix", etc. but Via Rail is Canada-wide, whereas Charlevoix is just one tiny county region (where Via presumably has a stop, but there are many stops/stations out there).

I just thought it was weird when seeing it in this Transitous MR diff (c.c. @mlundblad & @jbruechert in case this does end up changing in transitland-atlas).

The Baker City Community Connection is a part of the overall Northeast Oregon Public Transit. It is no longer branded as a separate service, and is included in the http://oregon-gtfs.com/gtfs_data/northeast-or-us/northeast-or-us.zip feed.

Currently when running transitland dmfr format --save against a DMFR file in the Atlas repo, it will remove feed.urls.static_planned values even though that field is allowed in the current DMFR schema

The RT files referenced in govcbus.com.dmfr.json contain data from several agencies that are not present in the Trillium-hosted static feed referenced in the same file. There is a GTFS static file hosted by govcbus.com that contains data from the agencies present in the RT feed available at https://govcbus.com/gtfs

I'd be happy to submit a pull request to change this file to use the govcbus GTFS static feed, but before I do so, I would like to ensure that the reference to other feed isn't intended. I didn't see anything in file's version history or closed issues that would indicate either way.

Thanks
-matt

The data linked through https://planar.network/projects/feeds to the GTFS feeds for both eurostar and rail delivery group are dead links. The S3 links link nowhere.

Tlv1 has a way to mark a feed as archived. It won't have new versions fetched, but old versions will remain for historical use.

How should we implement this in Transitland Atlas and Tlv2?

For example #217

This feed no longer exists.
https://transit.land/feed-registry/operators/o-9rb-eugenetocoosbay

The auto-linked location data for the Detroit People Mover is inaccurate. It lists Ontario, Canada as a served region, but that’s not the case. I’m guessing this is because the alignment goes very close to the Detroit River and thus the U.S.-Canada border, but nonetheless it does not cross the border and only serves downtown Detroit.

What happened:

1. the cron job successfully ran the update and made this commit: 8512bd0

2. an unrelated PR was submitted against master and GH Actions failed, belatedly noticing an ID problem in the DMFR file committed by the cron job: https://github.com/transitland/transitland-atlas/pull/170/checks?check_run_id=1532689955

Options:

• have the cron job open a PR, let GH Actions run its validations, have a person actually commit the PR
• have the cron job run the validation scripts inline, only proceed to committing into master after validation scripts succeed

HUT was bought out by Groome Transportation, and no longer operates as a separate entity.
https://groometransportation.com/portland-airport/

When I entered a specific BART station ID in the departures API, I saw no departures in the departures key in the JSON request. Is the GTFS for BART departures broken?

I see that f-u0j-piemonte~autobus results in a timeout. I know that it works on my machine, and I think that they banned transitland's IPs (probably due to "high traffic"). Would be possible to know which IPs are used by transitland so that we can see if we can get them unblocked? Thanks a lot!

Hi,
there are some Feeds from the state Baden-Württemberg in Germany that are not listed in TransitLand.

There are listed here:
https://www.nvbw.de/open-data/fahrplandaten/fahrplandaten-mit-liniennetz

The license is of all these is:
https://www.govdata.de/dl-de/by-2-0
With attribution: "NVBW GmbH"

And an extra license and extra attribution for the shapes.txt:
"OpenStreetMap Contributors"
https://opendatacommons.org/licenses/odbl/

So someone could add these, cause I don't want to do this.

Several operators and agencies keep an updated version of their feeds at the Spanish Transportation Ministry data portal (National Access Point). Url:
https://nap.mitma.es/Files/List

Spreadsheet that lists which GTFS Realtime API endpoints to associate with which agency/operator is at https://opendata.transport.nsw.gov.au/dataset/reference-tables-tfnsw-gtfs-feeds/resource/30b850b7-f439-4e30-8072-e07ef62a2a36

Valley Retriever (https://transit.land/feed-registry/operators/o-9rb-valleyretriever) went out of business.
https://www.bendbulletin.com/business/bend-newport-bus-service-ends/article_84768232-e9ed-549e-a335-5b0f656c2e5a.html

nearly all boston area commuter buses have been discontinued, including f-drt-coachcompany/f-dr-coachcompany~ma~us, f-bloombus~ma~us, and f-drm-dattco, as well as f-drt0-limoliner~ma~us and f-drs-truenorthtransit~ma~us, which are marked as historic but remain on transitland. what should be done about these? should they be removed or marked as historic?

Linux Foundation has released a new version of the Community Data License Agreement permissive variant that is simpler and more straightforward: https://venturebeat.com/2021/06/23/linux-foundation-unveils-new-permissive-license-for-open-data-collaboration/

We'll consider re-licensing the contents of the Transitland Atlas under CDLA-Permissive-2.0 https://cdla.dev/permissive-2-0/

f-bsoob~me~us and f-biddeford~saco~old~orchard~beach are duplicates and seem to be pretty much identical; which one should be kept?

There are currently multiple ways to associate one or more Feeds with an Operator. This can be confusing to contributors, who are unclear which is the most appropriate way to link Feeds and Operators.

Another problem is that the tlv2 sync scripts and queries are inconsistent in how they handle Operator groupings for GTFS-RT feeds.

We'll replace the separate Operator data model files (in ./operators) with inline models/objects nested underneath each Feed model record.

By "historical" I mean that there's only a static_historic entry in urls

Specific example would be Sunset Empire Transportation District (clatsopcounty-or-us). According to https://oregon-gtfs.trilliumtransit.com/ the feed is currently valid.

I noticed that the routes weren't showing up on the Transit Land map.

Appears it may have been added in commit f4d73a6 by @evantrillium in #441

opendata.bratislava.sk.dmfr.json

Outdated

https://opendata.bratislava.sk/dataset/download/cestovny-poriadok-20220725/1 - here is link to updated feed

See https://kolejedolnoslaskie.pl/rozklady-gtfs/

This is breaking some feed URLs, for example:

Hi,
I have some GTFS data here: http://www.agenziatpl.it/open-data/gtfs
Only ATM is already available. I don't understand how to insert those data here so I leave this issue open hoping that someone will do this work :)

@drewda I'm trying to push changes to the TL repo from the command line. I've cloned the repo on my computer but I'm unable to push my changes. I get a message that says:

remote: Permission to transitland/transitland-atlas.git denied to rpedraza01. fatal: unable to access 'https://github.com/transitland/transitland-atlas.git/': The requested URL returned error: 403

Do I need to be granted some kind of access by you?

saginaw stars appears to have their gtfs in a onedrive folder... not really sure if anything can be done about that