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

Investigate reporting queue lengths #41

Open
dnesbitt61 opened this issue Apr 26, 2017 · 0 comments
Open

Investigate reporting queue lengths #41

dnesbitt61 opened this issue Apr 26, 2017 · 0 comments
Assignees

Comments

@dnesbitt61
Copy link
Contributor

Approach is to walk forward along GPS points and identify when speed falls below a threshold. The distance from this point to the next intersection becomes the queue length. Several questions arise:

  • What is the required GPS reporting frequency (time interval between locations)?
  • What if no OSMLR segment is reported at the intersection where the queue begins? May end up reporting a queue length to the end of the OSMLR segment, rather than the actual intersection.
  • Assumption: cannot walk backwards from an intersection and detect when speed exceeds threshold (since once the queue moves the speeds increase).
  • A taxi dropping off or picking up a passenger trigger the queue length report - does this matter or is there any way to avoid it?
@drewda drewda removed their assignment Sep 19, 2017
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