Skip to content

Conversation

@Lach-anonym
Copy link
Contributor

No description provided.

@Lach-anonym
Copy link
Contributor Author

Funnily enough, this feed is used by Google and it also states it's expired

@jbruechert
Copy link
Collaborator

The expiration check seems to be correct

@Lach-anonym Lach-anonym marked this pull request as draft July 7, 2025 10:12
@Lach-anonym
Copy link
Contributor Author

Again like in #1334, no feed_info.txt is present sadly

@jbruechert
Copy link
Collaborator

This one only has calendar_dates.txt which makes it even more difficult as there is no service pattern to repeat.
It's not impossible to derive something from that, but the likelyhood that it makes sense becomes even lower.

@Lach-anonym
Copy link
Contributor Author

So it means Google presents incredibly low quality data

@felixguendling
Copy link
Contributor

This one only has calendar_dates.txt

Doesn't gtfs-tidy have some kind of "compression" algorithm that derives weekly patterns from calendar_dates.txt to make the data more compact? Maybe gtfs-clean could also be used to add a feed_info.txt file?

@jbruechert
Copy link
Collaborator

This one only has calendar_dates.txt

Doesn't gtfs-tidy have some kind of "compression" algorithm that derives weekly patterns from calendar_dates.txt to make the data more compact? Maybe gtfs-clean could also be used to add a feed_info.txt file?

Yes, it can do that. But the end date of each calendar pattern is currently the last service day of the pattern, which means the different services would not have a matching end date. That could be rounded up to the highest date that doesn't have a service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants