Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
Needs more info comment that > 10 days [ID: 963198]
Comment such as: SPAM, non-actionable [ID: 963127]
Resolved actionable follow-up comments [ID: 963027]
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Currently the Routes API let's me generate
This is not sufficient for most EV users though. Users expect long routes to account for their vehicles current charge level and suggest charging stops along the way.
It would be helpful the the Routes API allowed developer to pass information about the EV properties of the vehicle, like it's current charge level, vehicle model (or maybe capacity), and what type of connecter it used. This could them be used to automatically add waypoints for users to charge.
For example, if a user is driving a vehicle=RivianR1S with charge=20% left, the best route for a long journey involves 1-2 stops at a CCS2 charging location. A vehicle=TeslaModel7 with charge=80% might not need any stops.
It's not possible to do this today using the Routes API. We can use the Places API to find chargers along the route and, while we could naively add them as waypoints, that's very far from an optimal solution.