I don't understand. You're saying there's too many operators to reasonably connect to. How do they currently do these live maps then? It seems to me that, some

I don't understand. You're saying there's too many operators to reasonably connect to. How do they currently do these live maps then? It seems to me that, somewhere, there is a URL (or whatever specification) which some central server then fetches and aggregates to show on their map (probably briefly caches, too). This specification of where to fetch the data from each charging point from could, per my understanding, be an OpenStreetMap tag just like other metadata that we can already add. A client can either connect to the (e.g.) 50 nearest points along the upcoming route directly, or a third party can do it and funnel the data back to the client, but the ground truth of which charge points there are and how to get their current status could be in OpenStreetMap rather than fragmented across various siloed map operators Edit: actually, even if that's not the case, it's still better to show "there is a charge point here with 2x 150 kW but I don't know the current status" than not having it at all. That's static information which OpenStreetMap already has. Even if the live info spec is too elaborate or divergent for an OSM metadata field, it would still make sense to show all the points OSM is aware of in one's application because it draws more people to one's app/website