TomTom availability

[robho]

This adds availability data from TomTom.

It's working, but some TODOs:

• Test and add to other data sources than Nobil
• Only the "best match" returned from TomTom is used. Potentially other matches could be used.
• Could add min/max power to TomTom queries to get better matches
• Maybe change priority among the availability services

I think the TomTom license allows use in EVMap, but I haven't looked closely into this.
Edit: Seems like the free plan only allows for 2500 requests daily and given that this implementation uses 2 requests for each availability lookup we'd only get 1250 availability requests daily.. I guess that could be quite limiting :-/

Comments are welcome!

[johan12345]

Hi, thanks for your work!

Edit: Seems like the free plan only allows for 2500 requests daily and given that this implementation uses 2 requests for each availability lookup we'd only get 1250 availability requests daily.. I guess that could be quite limiting :-/

That is quite limiting unfortunately, yes. Based on statistics from the Play Store, daily active users can often be around 1000 (users from other app stores come on top of that). On the other hand, it's hard to estimate how many of them use Nobil, how many chargers each of them looks at, and how many of those don't have realtime data from other sources available. Still, it probably doesn't leave much room to grow... and if the limit is exceeded at some point during the day, users might be confused why realtime data is not available anymore for a charger where it used to be available earlier in the day.

How good is the data from Nobil's own realtime API? Last time you said the percentage of chargers where Nobil have OCPI integration (and therefore also realtime data, right?) is quite high already. Then maybe we should rather focus on implementing that. I can try to make this available on a server with an API similar to your prototype.

[robho]

Closing this since it's difficult to use this implementation without paying TomTom or having users set up their own API key..

Regarding real-time data here in Sweden it already works quite well with the availability services EnBW, NewMotion and Tesla. To me it's mostly "McDonalds/Recharge" and "Circle K" that would be nice to have availability data for also. But it's "nice to have", and not that important to me. I know you're working on an alternative platform/implementation, when you have time, and I don't want to distract you with other stuff, like setting up a Nobil real-time data server..

Anyway, I dusted off the nobil-realtime code and tried it out. It does have real-time data for "McDonalds/Recharge" and "Circle K" and seems to work well. I can create a draft PR with the nobil real-time implementation and we could continue the Nobil discussion there (or use #360).

No pressure! EVMap works well as it is! :-)