Inconsistent Travel Times via Trip Planner and Jython API

[Clint Daniels]

I'm having an issue developing matching trip times in OTP via the HTTP itinerary request and a Jython API request. The requests appear to be identical, but I can't get the same answer between the two services. I've accounted for the time zone difference from #2602. That helped me get a closer match, but it seems like the two methods should produce identical results. Is there a difference in the default settings between the two methods that leads to slightly different shorter path outcomes?

HTTP Request Results

Itinerary 1: Time=3311s, WalkDistance=452, Boardings=2

Itinerary 2: Time=3362s, WalkDistance=597, Boardings=2

Itinerary 3: Time=3331s, WalkDistance=452, Boardings=2

Jython Request Results

Time = 3360s

WalkDistance = 486

Boardings = 2

Any help or insights would be greatly appreciated.

Thank you.

Clint Daniels