Thomas Craig
Thomas Craig
Sorry for the delayed response! > The in the above example, too much slowdown might lead to not being able to make it to the stop on time, resulting in...
> 2 is also easy: No involvement of fixed stop_times, so just ignore them and add the safe offset/factor at the end, following the equation in the spec. Noting: this...
> * Working backwards, the trip planner subtracts the driving duration (let's say 20 minutes) from the end time of the trip (10:00). Factor/offset have **not** been included yet. This...
could we hold off on that step for a few more weeks to give us time to do some software testing in OTP, make sure that this change as proposed...
Yeah, I agree that these constraints are right. Offset should be equal to or greater than 0; factor should be greater than 0. I considered whether factors should be constrained...
> However, this makes we wonder if sub-minute offsets are something that we should consider. my interpretation was that they could be included by using decimal values less than 1...
yeah, that's my understanding.
The current spec reads: > While traveling through undefined space between GeoJSON locations or stop areas, it is assumed that: > MeanTravelDuration = DrivingDuration which is the same thing as...
This looks like an improvement but I think that we should remove "based on historical data" from both definitions. I can see basing these factors/offsets on historical data as a...
> But to the actual question at hand (😆), I am still curious as to what you envision would be the condition of their requirement, or is it a general...