[Ovmsdev] Open Charge Map

[Mark Webb-Johnson]

I think there is a difference between the charging database (locations) and events (charge start/stop by a particular user at a particular time).

We chose OCM (or did OCM choose us ;-) precisely because we didn’t need another charging database. Both the Android and iPhone Apps have some integration to OCM already.

I suggest the data records for charge events that we publish should be keyed on geofencing of the latitude+longitude of the charging event. The OCM station ID can be optionally provided by the user, and other consumers could cross-reference that to provide correlation to their own databases (if they think it necessary and can abide to the OCM license terms).

Regards, Mark

On 23 May, 2014, at 4:15 pm, Paul Churchley <paul at churchley.org> wrote:

> I can see your point Lee.
> 
> I see OCM slightly different in that I see it as just one of many potential charging databases out there that OVMS may want to interact with. By using OCM as the charging database of OVMS you remove all aspect of control over the data. The data collected by the OVMS users belongs to them, and by inference to OVMS. Just giving it to OCM as our datastore means that OVMS only has "acces"s to that data via the OCM API... we wouldn't have control over the data itself. We would have lost all element of direct control including where it goes to after OCM. That would then be down to OCM.
> 
> If those issues could be overcome, of if people consider these points unimportant, then we could use the OCM database as "our" database I suppose. 
> 
> Perhaps OCM and OVMS would like to merge projects? Then this issue goes away :-) Just a thought :-)
> 
> Smartphone apps are great but I believe that the best place to do location relatively complex and comms-dependent tasks; such as matching, sending updates to OCM etc, is on the OVMS server. What if there is a new database that OVMS wants to update also? The phone app would need updating and every user would need to update their app. In fact, some of that code might be pretty big or complex and that would then reside on relatively low-powered phone devices instead of the server. I wouldn't see this as a batch task. It could still be real-time and triggered by the phone app.
> 
> 
> On 22 May 2014 23:44, Lee Howard <lee.howard at mainpine.com> wrote:
> On 05/22/2014 02:49 PM, Tom Saxton wrote:
> I'd like to make sure that whatever happens with OVMS reporting charging
> station information stays open and stand-alone, not tied exclusively to
> OCM.
> 
> Is OCM not open-enough already that it could simply be viewed as the charging-location database for OVMS?  Why should OVMS duplicate the effort of developing a charging-location database?
> 
> 
> Lee.
> 
> -- 
> *Lee Howard*
> *Mainpine, Inc. Chief Technology Officer*
> Tel: +1 866 363 6680 | Fax: +1 360 462 8160
> lee.howard at mainpine.com | www.mainpine.com
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20140523/524a3d0c/attachment.html>