-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
remove timezone
from timed.py
#32665
Conversation
Thanks for contributing to openpilot! In order for us to review your PR as quickly as possible, check the following:
|
Hmm, the API docs mention that this API is for extracting information from the tiles without rendering them... however we only care about knowing the timezone when rendering the map. Can we get them in the UI somehow when rendering the map? |
looked into being able to use the existing api for rendering like you said but again it didn't look like it provided the timezone information like how I went ahead and used the tilequery still and was able to get it to use Marking ready for review since tests are passing and I verified that it eta works fine by running |
Not sure what's causing simulator test to fail? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Including the timezone in the nav packet, instead of using the Timezone param, has the added benefit of this codepath being hit every time. For example, if the timezone getting code broke, most people wouldn't notice until they reset the device or crossed a timezone borundary.
779ca43
to
545e319
Compare
Added to the 0.9.8 milestone. Might be a little bit before we get to it, but looks good at first glance |
8e0afb4
to
9b92d8c
Compare
ui
: use TZID
from tilequery mapbox apitimezone
from timed.py
c6ca958
to
6f9612f
Compare
Resolves #32662
Unfortunately when looking into the response we get when getting route info their isn't any mention of timezone ids. however we can use tilequery which does return the timezone id based on the coordinates, this can be another request within
calculate_route
in theRouteEngine
class. I've started the implementation but also was curious as to whether this is fine since this does require making another request after therouteRequest
is successful.