Search for locations with X amount of connectors

I have a seemingly simple requirement that I can’t seem to resolve. I want to be able to search for locations where X number of connectors are available.

e.g. “Show me all locations near here with a minimum of 4 chademo connectors” or “Show me locations with a minimum of 6 CCS connectors”

Using the web interface I can’t do this. Has anyone managed to do this query? Surely I can’t be the only one with this requirement?

Essentially, I want to filter the map to remove sites with only one or two chargers as in my experience these are often busy / broken / unreliable. I want to stop at charging hubs or locations with multiple chargers so that it is more likely I can just arrive and plug in.

I am now looking at querying the API myself and maybe making my own google map pulling in this data. The NumberOfPoints property in the data doesn’t make sense as seems to count all connectors - e.g when a site has multiple slow chargers and one rapid it might show 10.

My only hope now would be to pull all the data and filter it client side, counting the number of connections where ConnectionTypeID matches the criteria.

Anybody got any thoughts about this?

This is a valid request and one which I have seen asked on forums elsewhere too. Given the growing penetration of EV and the growth of charging services in Europe, many drivers now want some resilience built into their journey planning, and the option of route-planning by using either multi-charger sites, or multi-vendor sites where possible.
The conversation came up here at some point back - I thought there was a specific thread on it, but I can’t find it now (but is mentioned here: Update of symbol colors - #11 by RonnieLast) - OpenCharge map doesn’t group by “site” and it could definitely do with improvements around charging supplier hardware - such as creating hardware profiles for charger-types instead of the current system of individual plugs.
If the data is aggregated by GPS location by an app, I suppose some site grouping can be inferred, but having this built into the database at the charger level would be better.
Maybe Christopher has views on the ease or probability of implementation of such?

Yes it could be done although with our current data model the value would be limited, it would first require implementation in our API then implemented in our app. The limitation is mainly that our data model is not strict enough.

NumberOfPoints has come to mean number bays/units (e.g. number of people who could charge at the same time), so it’s kind of a misnomer. We do have a field for quantity in connection info (e.g 6 ‘CCS Type 2’, 1 ‘Chademo’ etc) but it can also be entered as 7 individual connection info entries each with the type set.

Really, where we want to get to is individually documented EVSE connections (grouped per unit), so that we could theoretically report the status of each one, but this has never been done (and nobody wants to enter 10 connections all with the same info etc). This requires data model updates, API updates and app changes. All volunteers welcome.

Regarding having your own map, that’s exactly why our API exists. Thousands of apps/services use the API to do all sorts of specific visualisations.