For layovers was adding in the expected stop time twice when generating
predictions. This was causing predictions to be significantly off if the
expected stop time was significant for a layover stop.
Was missing generating departure times for first stop of trip for MBTA
because the layover stops are defined to be far away from the route
(about 140m). Since the match distance was greater than allowed was not
generating arrival/departure times for this case. Therefore changed the
filter to only not generate arrival/departure times for layovers if
match distance is greater than the allowable *layover* distance
allowable.
Changed so that when determining stop times for layovers that instead of
just using an average value the system now uses a biased value that
ensures that most of the time the actual stop time will be greater than
the expected time. This way predictions for the important layover stop
will be conservative and passengers won't miss their vehicles.
Had wrong (old) class name for prediction logging.
For first stop of trip biased the stop time down a few (10) seconds to
take into account that passengers need to be on vehicle a few seconds
before it physically departs a stop. This is important for first stops
of trips because the predictions are for departure times, not arrival
times.
Merge branch 'master' of ssh://git@github.com/Transitime/core.git