LIRR Data Expired!

[David Hodge]

We just discovered that the posted LIRR data is now completed expired! The last of the calendar dates in the file appear to have been reached yesterday. (It doesn't use the calendars table, just calendar_dates. )

If I had noticed this before I would have sent this as a part of my question on subway data. Any thoughts on when new data will be posted?

Thanks!

David

[Brenner, David M]

It will be available tomorrow morning.

[David Hodge]

Great! Thank you for your speedy reply.

[Doug Kelly]

The updated LIRR GTFS lists the normal schedule, not the one the LIRR expects to run 'through the end of the year'--approx 70% of normal rush hour service.

We need a GTFS that accurately shows the service that's being provided.  Will one be provided?

[Sunny]

I don't think so, as those are only "temporary" rush hour schedules. Remember the ESA work over the summer that canceled a handful of PM rush hour trains? I don't believe those were ever put into the GTFS.

[DaveZ]

Thanks for publishing the LIRR GTFS.  Please note that the GTFS does not match up with the Modified schedule on the MTA website.  Will the modified schedule be change to the normal schedule soon?  If yes, when?  If not, can we get a GTFS data that matches the modified LIRR schedule?

[Matt]

some of the calendar dates: service_id GO403_1246 has dates January 17, 24, 25 has the incorrect year, 2012, or (according to the Barclays events schedule) they are in November

GO403_1246 also has Ronkonoma train 2090 (GO403_122090) which means that train only operates with the Barclays concert service when it should be with the weekday frequency

suggestion: have trains GO403_124106 and GO403_124108's departure times set to 24:13 to 25:02 respectively (ex below)... doing so with changing the hour from 0 to 24 would make the service_id part of the same day but going into the overnight hours, so it can be on the same service_id, GO403_1242

Example:

trip_id,arrival_time,departure_time,stop_id,stop_sequence

GO403_124106, 24:13, 24:13, 12, 1

GO403_124106, 24:19, 24:19, 13, 2

GO403_124106, 24:24, 24:24, 14, 3

GO403_124106, 24:34, 24:34, 15, 4

GO403_124108, 24:41, 24:41, 12, 1

GO403_124108, 24:47, 24:47, 13, 2

GO403_124108, 24:52, 24:52, 14, 3

GO403_124108, 25:02, 25:02, 15, 4

i hope you take this suggestion into consideration

and as mentioned in the other thread: some trips has stop sequences wrong in stop_times.txt such as GO403_123026 and GO403_123031

[Doug Kelly]

There appears to be progress towards a GTFS that matches the modified service.  Today's update has some stops and entire trips added, and it looks like the Long Beach shuttles are now included.

Any guesses on when it will be completed?

[Brenner, David M]

Trains with out of order trains have been corrected.

Also, trip GO403_122090 correctly has its service_id as GO403_1265.

Regarding trips GO403_124106 and GO403_124108 there is no current mechanism in our process to identify trains that technically run on a date after, but logically belong to, an event and service of the previous date.  Altering a service ID and/or time would have to be done by the Schedules and Fares department.