You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 27, 2024. It is now read-only.
We made the decision to move to Google Maps API v2 (which requires Google Play Services) due to trouble integrating old versions of OSMDroid with newer Android components.
Yes, would be interesting. Another good option would be to use Skobbler API, as you said in another conversation, which has for example the step-by-step navigation mode and other very interesting features as very good support for offline tiles, although it has the problem of not being FLOSS.
One possible problem of OSMDroid is that the last demos that I have seeing are not visually appealing at all (tiles loading, zooming, not acceleration, limited map movements,...) , but maybe this has been improved.
After looking at OSM Droid further, it does not have one-to-one parity with Google Maps API v2 interface. Instead, it provides a wrapper around Google Maps API v2, but exposes only a Maps API v1 interface to the application. More here - osmdroid/osmdroid#75 (comment).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We made the decision to move to Google Maps API v2 (which requires Google Play Services) due to trouble integrating old versions of OSMDroid with newer Android components.
There now seems to be one-to-one parity with the Google Maps API v2 interface in OSM Droid.
We should investigate this, and if possible provide a version of OTP Android that doesn't rely on Google Play Services.
The text was updated successfully, but these errors were encountered: