No subject
Fri Sep 27 23:39:33 HKT 2013
e best place to store very fine-grained charging stats and is mostly intere=
sted in aggregated summaries instead - basically high level info that's use=
ful from a user perspective. While OCM is indeed focused on charging locati=
on information we also need to help users by identifying quality/usage info=
rmation (good and bad) with locations which is where comments/checkins come=
s in. We augment that with photos to allow users to illustrate stuff about =
the location.
Ideally if you could look-up OCM to confirm the (OCM Reference ID) identity=
of a charging location with the user at the time (choosing from nearest kn=
own locations?), then store that, which would help us then pull/associate d=
ata relevant to OCM later.
Ideally for us verbatim commentary would go to OCM as a normal comment/chec=
kin submission - we could provide standard URL format for full comment/phot=
o submissions etc via mobile browser - the user would then need to sign in =
to OCM normally. Obviously thats up to you but probably the simplest integr=
ation. We don't want to hold information of charging locations at private r=
esidences (someone's home) as the data protection/privacy issues are too co=
mplicated.
My own view of data licensing is that its a necessary evil, one I don't hav=
e a huge amount of interest in - I'd rather defer that to experts. Privacy =
is my main concern, infringing other peoples data license is obviously unde=
sirable too, to varying degrees. People can get very upset about licensing,=
very quickly.
I say go for it, make sure users know what information will become public, =
and please provide an HTTP API for querying the (shared, public) stats for =
later aggregation by OCM.
Cheers,
Chris
--_000_F64F567267C4704C8E67FD6969BA2CE11A8A3587exch2mb06email2_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<script id=3D"tinyhippos-injected">if (window.top.ripple) { window.top.ripp=
le("bootstrap").inject(window, document); }</script><style type=3D"text/css=
" id=3D"owaParaStyle"></style>
</head>
<body style=3D"word-wrap:break-word" fpstyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">Hi Mark,<br>
<br>
Yes, that sounds right in terms of what we (OCM) would want to present to t=
he user (and currently do).
<br>
<br>
OCM can take care of the import into OCM if OVMS makes an API available int=
o the more fine-grained charging status data, rather than needing to push f=
rom OVMS. We would probably add something to OCM to display this aggregated=
info as a single anonymous summary
of stats, rather than showing individual charging events. I could well ima=
gine systems such as plugshare/recargo would be interested in the data (mor=
e from a commercial perspective).<br>
<br>
In OCM we attempt to classify charging success/failure in check-ins by havi=
ng a table of common statuses, with mixed success:<br>
<br>
ID Title IsPositive I=
sAutomatedCheckin<br>
0 Did Not Visit Location NULL &nbs=
p; 0<br>
10 Charged Successfully 1 &n=
bsp; 0<br>
15 Charged Successfully (Automated Checkin) &n=
bsp; 1 1<br>
20 Failed to Charge (Equipment Not Operational) &nbs=
p; 0 0<br>
22 Failed to Charge (Equipment Not Fully Installed) =
0 0<br>
25 Failed to Charge (Equipment Problem) =
0 0<br>
30 Failed to Charge (Equipment Not Compatible)  =
; 0 0<br>
40 Failed to Charge (Required Other Access Card/Fob etc.)=
0 0<br>
50 Failed to Charge (No Charging Equipment Present) =
0 0<br>
100 Charging Spot In Use (Other EV Parked) &nb=
sp; 1 0<br>
110 Charging Spot In Use (Non-EV Parked)  =
; 0 0<br>
120 Charging Spot Not Accessible (Access locked or site c=
losed) 0 0<br>
130 Charging Spot Not Found (Inadequate or Incorrect Deta=
ils) 0 0<br>
140 Equipment & Location Confirmed Correct  =
; 1 0<br>
200 Other (Negative/Bad) 0 &=
nbsp; 0<br>
210 Other (Positive/Good) 1 =
0<br>
<br>
Other reference data (connectors etc) can be seen via the API: <a href=3D"h=
ttp://api.openchargemap.io/v2/referencedata/">
http://api.openchargemap.io/v2/referencedata/</a><br>
<br>
We do support the concept of an anonymous checkin via HTTP Post of a JSON f=
ormatted message to the OCM API but I think we'd probably require an API ke=
y for those submissions going forward (we don't currently). This theoretica=
lly allows other apps/systems to
post comments/checkins directly from their own UI.<br>
<br>
<br>
Chris
<div><br>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div id=3D"divRpF101018" style=3D"direction: ltr;"><font face=3D"Tahoma" si=
ze=3D"2" color=3D"#000000"><b>From:</b> Mark Webb-Johnson [mark at webb-johnso=
n.net]<br>
<b>Sent:</b> 12 December 2013 05:54<br>
<b>To:</b> Christopher Cook<br>
<b>Cc:</b> OVMS Developers<br>
<b>Subject:</b> Re: [Ovmsdev] Sharing Data Publicly - Public Charges<br>
</font><br>
</div>
<div></div>
<div>Chris,
<div><br>
</div>
<div>From a user point of view, what do we need?</div>
<div><br>
</div>
<div>I guess, for each station:</div>
<div><br>
</div>
<div>
<blockquote style=3D"margin:0 0 0 40px; border:none; padding:0px">
<div>a) An indication of when someone last charged successfully</div>
<div>b) A 'star' style rating system to tell me how reliable it is</div>
<div>c) Pictures</div>
<div>d) Instructions</div>
<div>e) Comments</div>
</blockquote>
</div>
<div><br>
</div>
<div>I think OVMS can help with (a) and (b) primarily.</div>
<div><br>
</div>
<div>Regards, Mark.</div>
<div><br>
<div>
<div>On 12 Dec, 2013, at 1:45 pm, Christopher Cook <<a href=3D"mailto:ch=
ristopher.cook at webprofusion.com" target=3D"_blank">christopher.cook at webprof=
usion.com</a>> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"font-family:Helvetica; font-size:24px; font-style:normal; fon=
t-variant:normal; font-weight:normal; letter-spacing:normal; line-height:no=
rmal; orphans:auto; text-align:start; text-indent:0px; text-transform:none;=
white-space:normal; widows:auto; word-spacing:0px">
<div style=3D"direction:ltr; font-family:Tahoma; font-size:10pt">
<div class=3D"moz-text-flowed" lang=3D"x-western" style=3D"font-size:14px">=
Hi Mark,<span class=3D"Apple-converted-space"> </span><br>
<br>
More information about the OvmsDev
mailing list