I think that's an issue with the OCM app not the database (the two things are separate). What I find silly is that yet again someone has embarked on another EV charging map when we already have more than 200... why not add the data to OCM and then export to Google Maps? In that way we have one source of the data.I've said elsewhere I've had a few problems with open charge map (especially on iPhone) and the Google map solves that problem.
Only the community can solve that problem by getting involved and resourcing the effort... I use OCM data in the OpenVehicles app and it's amazing because it's also aware of the cars range at all times.I think this map well worth keeping. It is a simple way to show this info and while OCM may have the same raw data it isn't so easy to display it in this simple and easy to understand and use way.
I'm not going to go into the issues with using that on smartphone.
Not at all... it would be trivial to add a class for future locations (if it doesn't already exist) and the main developer (Chris Cook) is one tweet away... if we want things to improve with charging location data we need to find a way of collaborating without reinventing the wheel every couple of months.Charging point databases such as OpenChargeMap do not and should not be showing projected and announced future locations.