Isochrones with Uber traffic data about openrouteservice HOT 5 OPEN

The problem isn't with the isochrones themselves, but a missing timezone decleration. If you set that in the AbstractTrafficGraphStorage (currently isn't initialised) then you can get isochrones. However, that is then hardcoding it to a single time zone which isn't the proper solution

from openrouteservice.

You're right. We were just serving Germany so far. If you're not hardcoding it, you deal with this monstrosity 😄 -->

from openrouteservice.

We had a half working solution before, where a library was used to translate coordinates into Time Zones. But it was utterly slow and not actively maintained. We had to remove it. So far, we haven't found a suitable solution. Maybe it's worth just providing a parameter to select the time zone manually for now. It should be sufficient for the smaller Uber traffic data use cases. What do you think?

from openrouteservice.

It could be worth looking into using https://github.com/evansiroky/timezone-boundary-builder. Kind of the successor to http://efele.net/maps/tz/world/

from openrouteservice.

Just found this issue: #1317

from openrouteservice.