<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Nikolay,<div><br></div><div>Seems a very similar approach:</div><div><br></div><div><img id="8e5e74d1-fa99-40c6-87ad-c6dad6f073b4" height="555" width="351" apple-width="yes" apple-height="yes" src="cid:20915F0F-7E47-4D2C-8D21-B641DCB5F4B5"></div><div><br></div><div>But, we would only show chargepoints in range.</div><div><br></div><div>Regarding using OCM, quite frankly they are sponsoring this work and I'm happy to accept. Their database is pretty extensive and global and their 'open' philosophy suits as well. The entire OVMS project (apps, server, car module software and hardware) is open source, and on github - so it is free for anyone to do with as they want.</div><div><br></div><div>Regarding the use of intents and reversing this so that the other apps do the displays, while I agree that technically that is an elegant solution, it is really beyond the scope of what we can control. We can pull free and open databases of information into OVMS, but we can't make other systems to pull data from or otherwise integrate with our intents. We could try persuasion, but I don't have high hopes to get 20+ vendors to accept our approach. Technically, on iOS, this is also a nightmare - applications are sandboxed and inter-app communication is almost impossible (and promptly shut down by Apple whenever possible). The only thing iOS has is the URL scheme.</div><div><br></div><div>In fact, essentially the same situation as OpenChargeMap in general. They can have a completely open database that anyone can contribute to and download. But, they can't force people to use it.</div><div><br></div><div>I would love a generic framework, but that is really beyond the resources we have at the moment. Even then it would be a nightmare to remove duplicates if more than one source was plugged in.</div><div><br></div><div>{soapbox}The whole situation with proprietary charge location databases is a nightmare, and very detrimental to the EV movement. If the charging stations can be used by anyone, why can't their location? I really hope that databases like OpenChargeMap can go some way to forcing the openness of this.{/soapbox}</div><div><br></div><div>Regards, Mark.</div><div><br><div><div>On 6 Mar, 2013, at 2:59 PM, Nikolay Shishkov wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Some examples:<br><br>Here is an example of a range calculation and visualization I made:<br><a href="https://play.google.com/store/apps/details?id=com.nikpix.LeafRangeCalc">https://play.google.com/store/apps/details?id=com.nikpix.LeafRangeCalc</a><br><br>And here is the integration of openchargemap I wrote in my previous e-mail:<br>https://play.google.com/store/apps/details?id=com.applications.lawsystems.leafcontrol<br><br>Here is a screenshot of the range visualization:<br>https://lh4.ggpht.com/D4dD0xdgJI8CEMAwhPa0sPp9zzsNf_j4SQksFTfZlowVdj9YfU6EFhqSzpxLf-NauQCm<br><br>Nikolay<br><br><br>________________________________<br>From: Nikolay Shishkov <nshishkov@yahoo.com><br>To: OVMS Developers <ovmsdev@lists.teslaclub.hk> <br>Sent: Wednesday, March 6, 2013 7:53 AM<br>Subject: Re: [Ovmsdev] Seeking ideas for 'range' representation<br><br><br>Mark, <br><br>Display of range can be done in a similar way openchargemap was integrated in one of the nissan leaf apps out there - some of their guys can probably show you. I think it was concentric circles.<br><br>Integration of a particular database of charging stations is a mistake - there are at least 20 such out there. On android this could be done much more elegantly by intents - we can have a "visualize range on map" intent (with parameters like - max range, kWh available, weight of car, efficiency) and have different apps implement that intent and create visualization based on the input data. This would be similar in the way the contacts app in your android phone can dial a phone number with the phone app via dialing intent.<br>I am not sure how would this best be done in the IOS world. <br><br>Note that I am partial - I am the founder of www.uppladdning.nu a database/mapping on charging sites solution for the nordic region and have had some dealings with the openchargemap before.<br><br>Nikolay<br><br><br><br><br>________________________________<br>From: Mark Webb-Johnson <mark@webb-johnson.net><br>To: OVMS Developers <ovmsdev@lists.teslaclub.hk> <br>Sent: Wednesday, March 6, 2013 2:12 AM<br>Subject: Re: [Ovmsdev] Seeking ideas for 'range' representation<br><br>Felix,<br><br>Yes, I agree. This is really not something that can ever be 100% - we just want something to represent roughly what is possible and to limit the charge stations that we show.<br><br>A nice thing about circles is that it easy to visually estimate 50% (or whatever), so I think the user can do this themselves.<br><br>Perhaps the existing outer estimated-to-ideal circle at 50% transparency, then an inner estimated-to-N%estimated circle at 25% transparency? Or is that too complex?<br><br>We're also planning to have a feature of show-route-to-charging-station, for a particular selected charging station, and that will be google maps / whatever so will show real distance by road.<br><br>Regards, Mark.<br><br>On 6 Mar, 2013, at 9:03 AM, felix bonnier wrote:<br><br><blockquote type="cite">Hi Mark,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The only thing with this is, obviously roads are not straight so a radius will never show a correct estimate. I think the range estimate would have to<br></blockquote>be only a percentage of the two values so that the range circle would be more realistic….. Maybe 60% of the values given by the car or something to that effect. Otherwise you will never make it to the next charge point………. what do you think?<br><blockquote type="cite"><br></blockquote><blockquote type="cite">felix b.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Mar 6, 2013, at 8:46 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Working with the guys at zerocarbonworld / openchargemap on the integration of Open Charge Map to the OVMS Apps, we are trying to find a way to represent range graphically.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">The first idea was a circle, centered around the car, with the inner edge of the circle being estimated range and the outer edge ideal range (or vice versa if you are coming down the mountains on a _long_ mountain road). Plugging in the values for my car today,<br></blockquote></blockquote>assuming I was somewhere in the centre of the UK, it would look something like this:<br><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><PastedGraphic-4.png><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">The idea is to represent the range, and then plot the charge points within (and perhaps also slightly outside) that range.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">That is just one idea. What do people think? Any other suggestions?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Regards, Mark.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">P.S. Work on the Apps for this has already started, so I would appreciate a quick reply. Nothing too extensive - just ideas.Thanks.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">OvmsDev mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">OvmsDev@lists.teslaclub.hk<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">OvmsDev mailing<br></blockquote>list<br><blockquote type="cite">OvmsDev@lists.teslaclub.hk<br></blockquote><blockquote type="cite">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></blockquote><br>_______________________________________________<br>OvmsDev mailing list<br>OvmsDev@lists.teslaclub.hk<br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br><br><br><br>_______________________________________________<br>OvmsDev mailing list<br>OvmsDev@lists.teslaclub.hk<br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br>_______________________________________________<br>OvmsDev mailing list<br>OvmsDev@lists.teslaclub.hk<br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></div></blockquote></div><br></div></body></html>