LIsochrone multiple GTFS with different date/time ranges leads to TransitTimesException

[Robert Fitzgerald]

hey all,

i am attempting to compute transit isochrones for the Atlanta, GA metro region. we have been given 9 GTFS datasets. each have their own date ranges in calendar.txt, but all date ranges do not overlap, so setting a valid OTP date query for within some intersecting date range was impossible. using different feeds (looking for newer ones/better overlapping ones) would break other assumptions in this research.

however, the calendar.txt files were fairly simple - a few lines, describing one range of dates, with service_ids for weekdays and weekends. i thought i could change the date ranges so that they overlap, in order to run them in OTP. also, i removed the rows in calendar_dates.txt (leaving just the header) so that any "exception_type" entries would not create any confusion.

despite this elaborate and sneaky hack job, i still seem to be getting TransitTimesExceptions. wondering if anyone has had success unifying date ranges as described, or, if there are other ways to make OTP more relaxed about it.

in "normal" situations (a single GTFS feed) my scripts for querying isochrones works fine. for example, i just computed 80000 isochrones for sampled start locations across Detroit, all with different cutoff times, using the Capital Metro GTFS spec.

thanks,

rob

[Robert Fitzgerald]

in case anyone found it confusing that i referenced a Captial Metro GTFS in Detroit: that was a typo, I meant to say "DDOT" GTFS.

[Robert Fitzgerald]

Fixed. The problem ended up being my re-compression of the GTFS specs inside of a folder instead of flat, as described in this thread. Everything is running correctly with my hack.

Thanks,

Rob