-
Notifications
You must be signed in to change notification settings - Fork 2
StartDate and EndDate are coming back as Null #23
Comments
From a quick look, I'm guessing this has to do with how TriMet is representing their calendar dates in their GTFS data. Most agencies use TriMet (and some other agencies) is representing ALL transit service in
So TriMet is using the "alternate" way. I believe this tool currently relies on the existence of calendar to calculate the GTFS start and end dates. We should also support pulling these values from We're not actively working on this tool, so if you want to take a shot at a pull request supporting this that would be awesome. Otherwise, we'll try to take a look when we can. |
Looks like the current
|
Thank you! That seems to have done it. Just so I don't lose it, here's the relevant patch. I'll work on a PR with conditional logic when I get a chance.
|
@alankessler thanks for the diff! Good to know that worked. |
Also, I think the proper fix for this is actually to loop through both getAllCalendars() and getAllCalendarDates(), and save the earliest and latest dates as the start/end dates. Either file could contain the min/max date. |
I modified the tool to work with my postgres database:
alankessler@01d10c7
However, I think that's unrelated to the error I'm now getting:
I've tried with each of these trimet data sets with the same result:
https://developer.trimet.org/schedule/gtfs.zip
https://transitfeeds-data.s3-us-west-1.amazonaws.com/public/feeds/trimet/43/20170714/gtfs.zip
https://transitfeeds-data.s3-us-west-1.amazonaws.com/public/feeds/trimet/43/20170727/gtfs.zip
I'd love any suggestions on how to resolve this.
Thanks,
Alan
The text was updated successfully, but these errors were encountered: