Data sources
What each provider supplies, and what we do with it. Last updated 29 October 2026.
EV Copilot plans electric-car journeys in India: where to charge, how long for, and whether the car reaches the next stop. No single provider covers all of that here, so the app draws on several. This page says plainly which part comes from whom.
What comes from where
| Part of the app | Provider | How it is used |
|---|---|---|
| Base map, on web, phone and the car screen | Mapbox | Rendered live by the Mapbox SDK, which draws its own logo and attribution control. |
| Routes and turn-by-turn directions | Mapbox Directions | Requested per trip. The route geometry and the driving instructions come from the same call, so the instructions always describe the road that is drawn. |
| Charging station locations | TomTom Search | Searched along the planned route and drawn as pins on the map above. |
| Live plug availability | TomTom, then Google Places | Asked only for the stops a plan actually chose, never for every station on a route. TomTom first; Google is asked only for stations TomTom reports nothing for, because the two cover different operators. |
| Place search and geocoding | Google Places, TomTom | Turning a typed destination into a point on the map. |
| Restaurants near a charging stop | Google Places | Looked up only for stops that fall in a meal window the driver asked for. |
| Elevation along the route | Google Elevation | One request per route. Hills change how far a car gets, so a flat estimate is a wrong one. |
| Station reports from drivers | EV Copilot | Our own: a driver can report a station as working, busy or not there. Stored separately from any provider's data. |
Attribution
The map on evcopilot.co.in/app carries its attribution control in the bottom corner, naming Mapbox for the base map and TomTom and Google for the data drawn on top of it. The same credits appear in the phone and car apps.
How requests are made
The apps hold no provider API keys. Every request goes through our own backend, which holds the keys, applies per-user limits and records what was spent against which provider. That is also why a provider sees traffic from our servers rather than from individual phones.
Questions
If you are a data provider and want to see exactly how your data appears in the product, the planner at evcopilot.co.in/app is the real thing. It asks for a Google or Apple sign-in first, because the planning allowance is counted per account. If you would rather not create one, get in touch and we will walk through it with you.