<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<script id="tinyhippos-injected">if (window.top.ripple) { window.top.ripple("bootstrap").inject(window, document); }</script><style type="text/css" id="owaParaStyle"></style>
</head>
<body style="word-wrap:break-word" fpstyle="1" ocsi="0">
<div style="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 the user (and currently do).
<br>
<br>
OCM can take care of the import into OCM if OVMS makes an API available into the more fine-grained charging status data, rather than needing to push from 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 imagine systems such as plugshare/recargo would be interested in the data (more from a commercial perspective).<br>
<br>
In OCM we attempt to classify charging success/failure in check-ins by having a table of common statuses, with mixed success:<br>
<br>
ID Title IsPositive IsAutomatedCheckin<br>
0 Did Not Visit Location NULL 0<br>
10 Charged Successfully 1 0<br>
15 Charged Successfully (Automated Checkin) 1 1<br>
20 Failed to Charge (Equipment Not Operational) 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) 1 0<br>
110 Charging Spot In Use (Non-EV Parked) 0 0<br>
120 Charging Spot Not Accessible (Access locked or site closed) 0 0<br>
130 Charging Spot Not Found (Inadequate or Incorrect Details) 0 0<br>
140 Equipment & Location Confirmed Correct 1 0<br>
200 Other (Negative/Bad) 0 0<br>
210 Other (Positive/Good) 1 0<br>
<br>
Other reference data (connectors etc) can be seen via the API: <a href="http://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 formatted message to the OCM API but I think we'd probably require an API key for those submissions going forward (we don't currently). This theoretically allows other apps/systems to
post comments/checkins directly from their own UI.<br>
<br>
<br>
Chris
<div><br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF101018" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Mark Webb-Johnson [mark@webb-johnson.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="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="mailto:christopher.cook@webprofusion.com" target="_blank">christopher.cook@webprofusion.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family:Helvetica; font-size:24px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<div style="direction:ltr; font-family:Tahoma; font-size:10pt">
<div class="moz-text-flowed" lang="x-western" style="font-size:14px">Hi Mark,<span class="Apple-converted-space"> </span><br>
<br>
>From my personal point of view this all sounds good, OCM is probably not the best place to store very fine-grained charging stats and is mostly interested in aggregated summaries instead - basically high level info that's useful from a user perspective. While
OCM is indeed focused on charging location information we also need to help users by identifying quality/usage information (good and bad) with locations which is where comments/checkins comes in. We augment that with photos to allow users to illustrate stuff
about the location.<span class="Apple-converted-space"> </span><br>
<br>
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 known locations?), then store that, which would help us then pull/associate data relevant to OCM later.<span class="Apple-converted-space"> </span><br>
<br>
Ideally for us verbatim commentary would go to OCM as a normal comment/checkin submission - we could provide standard URL format for full comment/photo 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 integration. We don't want to hold information of charging locations at private residences (someone's home) as the data protection/privacy issues are too complicated.<span class="Apple-converted-space"> </span><br>
<br>
My own view of data licensing is that its a necessary evil, one I don't have 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 undesirable too, to varying degrees.
People can get very upset about licensing, very quickly.<span class="Apple-converted-space"> </span><br>
<br>
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.<span class="Apple-converted-space"> </span><br>
<br>
Cheers,<span class="Apple-converted-space"> </span><br>
Chris</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>