Christopher,

thanks :)

The caching is necessary as a means to keep mobile data volume low -- it's still expensive over here. There is currently no user info on the caching.

For the compact format, I'm not sure how much that saves on transfer volume: gzip transport is enabled on the OCM server, and a JSON stream should be perfect food for gzip.

A much better solution would be possible if the OCM API allows to query for updates, for example like this:

...&updatedafter=<timestamp>

As I'm now using the charge point ID as the primary key, this would allow for more frequent updates without adding too much data volume.

Regards,
Michael

Am 01.02.2015 um 03:13 schrieb Christopher Cook:

Michael,

Nice work! If you're interested in extending the OCM integration at all you could consider:

Add &includecomments=true to the API call and you will get a UserComments list for locations where people have left check-in comments, you will also get a MediaItems list when people have added photos.

Example with lots of comments: http://api.openchargemap.io/v2/poi/?chargepointid=5546&includecomments=true

Example with several images: http://api.openchargemap.io/v2/poi/?chargepointid=23178&includecomments=true

You could add basic buttons to edit, comment and uploads photos. These would need to launch a browser activity with the appropriate URL

Edit: http://openchargemap.org/site/poi/edit/{OCM-ID}

Add Comment: http://openchargemap.org/site/poi/addcomment/{OCM-ID}

Add Photo: http://openchargemap.org/site/poi/addmediaitem/{OCM-ID}

Add A New Location (bit more complex an demanding on the browser): http://openchargemap.org/site/poi/add

I would invalidate the cache a bit more frequently than 4 weeks (depending on what it's caching). In regions where OCM is popular we would have a number of POI updates every day. I don't know if the app informs the user they're seeing cached data and lets them do anything about it?

On a tanget, we do have an experimental (subject to change) API call for smaller POI result sets: http://api.openchargemap.io/v2/compactpoi/ it's the same as the /poi call in terms of filters but it returns a much more concise result set. Might be worth looking at.

Best regards,
Christopher Cook

On 01/02/2015 06:17, Michael Balzer wrote:
Hi everyone,

I fixed the 2.3 compatibility issue. Turned out it was in fact a cache error combined with a RAM issue.

Test APK release can be downloaded from:
http://dexters-web.de/f/tw/oVMS-release-3.3.1.apk

Github kept telling me "auth error", so I created a pull request and merged it myself =>

https://github.com/openvehicles/Open-Vehicle-Android/commits/master

This includes...

Version 3.3.1: …
Michael Balzer authored 6 minutes ago

- Fixed OCM region caching, added cache validation based on time:
cache reload triggered once every 4 weeks
- Added OCM maxresults configuration (invalidates cache)
(+ changed OCM settings layout to TableLayout)
- Switched OCM JSON parsing to GSON library to reduce RAM usage;
now >500 chargepoints loadable on Android 2.3 devices again
- Implemented OCM filtering by vehicle range

Version 3.2.3: …
Michael Balzer authored 14 days ago

- OCM API update: fixes missing stations, missing detail data
and station address encoding issues
- USSD code dialog is now text field allowing "*" and "#",
default "*100#" (account balance query in most networks)
- 12V battery state display (car info)
- Renault Twizy: "Homelink" gets "Profile" and extended by "Default"

Testing & feedback is welcome :-)

Regards,
Michael
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26