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

Use lastLocationUpdateTime when available for last vehicle location update time #343

Closed
barbeau opened this issue Oct 28, 2015 · 1 comment
Assignees

Comments

@barbeau
Copy link
Member

barbeau commented Oct 28, 2015

In Tampa, lastLocationUpdateTime is always 0, so OBA Android is currently using the lastUpdateTime as the "last updated X seconds ago" data source for real-time vehicle positions. See OneBusAway/onebusaway-application-modules#151.

However, based on a quick look at other regions, in Puget Sound lastLocationUpdateTime is populated for some agencies - see OneBusAway/onebusaway-application-modules#151 (comment).

We should use lastLocationUpdateTime for the update time if its not equal to 0, and if it is equal to 0 then we should use lastUpdateTime instead.

@barbeau barbeau added this to the Public v2.0.x release milestone Oct 28, 2015
@barbeau barbeau self-assigned this Oct 28, 2015
barbeau added a commit that referenced this issue Oct 28, 2015
… location update time

* Add lastLocationUpdateTime to TripStatus objects used to deserialize OBA REST API response
* Add tests for the timestamps and status.getLastKnownLocation()
@barbeau
Copy link
Member Author

barbeau commented Oct 28, 2015

Fixed in develop via a5f3ffb.

@barbeau barbeau closed this as completed Oct 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant