[SoC] GSoC'13 OpenTripPlanner-for-Android Weekly Report #6
vreixo at gmail.com
Mon Jul 29 05:59:02 PDT 2013
I have chose this API because is much newer and offers much more
functionality. OSMdroid API is what was used until now in the app and is a
replacement of Google's API V1 with almost the same features.
One of the principal advantages for me is that with new API some operations
are much easier and elegant. It has an automatic MyOverlay layer to display
user's position, markers added and configured in one instruction, the same
for route lines, better controls to move the camera, etc.
This things could be done with OSMdroid API but required much more code.
This API uses a fragment natively to display the map and takes care of all
lifecycle steps regarding this (no need of save and restore map state
onPause and onResume). The fragment is much more adecuate to work with it
than the old activity and also is better for future integration with Action
bars and other components.
Also this maps are more nice to see, with the possibility to tilt, rotate
the map and the MyLocation and compass integrated. Also the possibility to
manage indoor mapping is interesting (in OTP there are some people working
For what I have read people was really waiting for the new API and has a
lot of promissing features that I didn't have explored yet.
The issues with the keys can provoke same time waste if you're not lucky
but after being configured there are no more problems and they don't
introduce any limitations and they produce usefull usage statistics.
If you only want OSM tiles is very simple, just set map type to none and
add a TileOverlay with an OSM provider. Regarding tiles, I will let the two
options in OpenTripPlanner client.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SoC