Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ScheduleAdherence for stops with different arrival/departure times #266

Open
wkulesza opened this issue Apr 18, 2023 · 4 comments
Open

ScheduleAdherence for stops with different arrival/departure times #266

wkulesza opened this issue Apr 18, 2023 · 4 comments

Comments

@wkulesza
Copy link

SchAdh value is calculated as a simple value indicating late/early/on-time based on the stop time.
We have noticed, that if there's a stop with dwell time (departure time is different than arrival time), when bus arrives on time, SchAdh would show early instead of on-time or dwell, with decreasing value of early as the time passes until the scheduled departure - then SchAdh will show finally on-time.
Is there a setting for TC, where departure time could be used rather than arrival time to calculate that value for stops with dwell time?

@changtung
Copy link
Member

Screenshots from api in this case and drop from database yesterday and today in this stop.
Screenshot from 2023-04-18 14-37-29
scr5
scr4
scr3
scr2
scr1

Bus has arrival time and in same time transitclock registers it as departure ( so there are 2 entries for stop SD02-1

@changtung
Copy link
Member

times
There are also no entries for timepointstop and waitstop in Stops database for this stop.
Also there are no arrival times for this stop despite the fact that was generated for gtfs in Datatools.

@wkulesza
Copy link
Author

We have also noticed that for this stop TC doesn't provide atStop=true value even though bus is at this stop. Another bus that stands at this stop provides atStop=true and only difference is that that stop is last or first stop on this trip. In our case it's a stop on the way.

@changtung
Copy link
Member

Screenshot from 2023-04-24 13-17-11
When we changed afterStop and beforeStop to 150 then it looks like there is couple minutes difference between arrival and departure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants