[Ovmsdev] Open Charge Map

Lee Howard lee.howard at mainpine.com
Thu Oct 16 11:18:54 HKT 2014


Could someone provide an update with respect to where the code is at 
with updating Open Charge Map?

I know that I've been saying this was on my near-proximity radar, but I 
wanted to let those who were more-familiar with OVMS do this... if they 
wanted to.

I've been keeping tabs on recent opinions regarding publishing charging 
locations, and privacy seems to be a substantial concern.  For the most 
part people don't want to see automatically-published charging locations 
for private residences or other private-access locations.  It is my 
understanding that while databases like Plugshare may welcome private 
residences others like OCM are deliberately trying to avoid inclusion of 
these for privacy reasons.

Therefore, it may not be wise to publish charging info automatically.  
Maybe the app could prompt the user each time a charge is completed with 
a simple "yes" or "no" prompt to publish (or not) the charging 
information to OCM.

Thoughts?

Thanks,

Lee.


On 05/22/2014 09:07 PM, Lee Howard wrote:
> OVMS could provide the vehicle type, the battery charge state, and by 
> interpreting information from between the start-of-charge and the 
> end-of-charge I'd think OCM could potentially interpret how much power 
> was obtained.  I'm not sure how useful all of that is.
>
> Thanks,
>
> Lee.
>
>
> On 05/22/2014 06:58 PM, Christopher Cook wrote:
>> On that topic, what other data can OVMS provide about the charging 
>> session? Just interested as to what we can/should include in OCM. For 
>> OCM this would be a flexible chunk of OVMS specific (JSON format) 
>> data attached to the checkin which OVMS can add/remove fields to over 
>> time. OVMS could also provide a textual comment "charged for 30 mins 
>> @ 240V/70A" or similar but we would have the more detailed breakdown 
>> available for later parsing.
>>
>> Chris
>>
>> On 23/05/2014 09:38, Tom Saxton wrote:
>>> I'm not proposing that OVMS develop a charging location database. It 
>>> merely stores charging reports, "at this date and time, someone 
>>> charged at 240V/70A at this longitude and latitude."
>>>
>>>      Tom
>>>
>>>> On May 22, 2014, at 3:44 PM, 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
>>
>>
>
>


-- 
*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


More information about the OvmsDev mailing list