Open bschoenfeld opened 11 years ago
Should this be a new, separate repo - one that uses the API?
Maybe. If that's the case, then the Bus Finder should be too...
On Mon, May 20, 2013 at 10:07 AM, Kevin Curry notifications@github.comwrote:
Should this be a new, separate repo - one that uses the API?
— Reply to this email directly or view it on GitHubhttps://github.com/c4hrva/hrt-bus-api/issues/32#issuecomment-18149001 .
I don't know. It wouldn't be terrible for the API to have a reference demo, though perhaps Bus Finder is well beyond reference demo. This occurred to me when I went to create issues for the Textizen polling. I decided I probably shouldn't put them here. In any case, it seems that either this project should be renamed & reorganized or broken up into separate but related projects. Not necessarily a priority...
I think the API could take over this project and we could move the bus finder to a new project that was hosted by github pages.
Sometimes the data has invalid adherences. From what I can tell, this happens when a bus has finished its route. I'd like to have a better tool for analyzing things like this. I picture a chart like this.
Small dots are location checkins. Large dots are time checks.
Adherence line: Updates between small and large dots. Line thickness is adherence value. Green for early, yellow for late, black for on time, red for invalid.
Route / Schedule line: Updates between large dots. Green if we know the route and were able to lookup the scheduled stop. Blue if we know the route, failed to lookup the scheduled stop, but we have older data that is being relied on. Yellow if we only know the route. Black if we don't know the route.