I want to use google earth on Android App, because the motion is really smooth and the attractiveness of the UI. Is there any framework or controls or APIs available for integrating google earth like UI in android apps.
I want to display a particular location
I want to zoom in/out to locations
I want to add/display markers from a particular zoom level onwards.
Hope I described my problem well. If it is not clear I will explain more.
Please give me answer.
While there isn't anything quite like Google Earth (mostly because Google doesn't offer Earth for Android), the Maps API offers the same functionality you're looking for. From what I remember of the last time I compared Maps to Earth, the only reason you'd pick Earth over Maps is if you wanted a 3-D spherical projection of the Earth at the lowest zoom levels.
Using the Google Maps API is fairly simple. Follow these steps.
Sign up for an API key.
Use your SDK Manager to download the Google APIs.
???
Profit!
Related
New to Stackoverflow, did some searching and couldn't find anything that really matched what I'm looking for unless I'm using the wrong keywords. I did find guides on how to plot a route when you know the actual route, but I'm looking to do it from actually walking it, see below:
I'm fairly new to web development and am looking to plot maps of a trail on a website using an embedded Google map or some other free map platform if it's suitable (OSM?) I have an Android phone and I'd like to actually be able to:
(1) walk this route,
(2) take the GPS data somehow &
(3) match it up to a Google map to
(4) post it on my webpage.
That will help visitors know the actual route (which is not available on Google Maps in any detail) and have somewhat of a "guide" of the near-exact trail route. I imagine this can be done, as Runkeeper and other applications do this (with additional data on speed, time, etc.) for tracking your runs. I don't really want any of that additional data as much as I would like to just capture the GPS route itself, and have it in some format that I can then use to make a map out of automatically. Not sure where to start with this, or if it can be done easily. Any information or guidance would be greatly appreciated. I have no experience in Java; very limited Javascript and OK in HTML/CSS. I've never used the Google Maps API either.
Thanks!
You may use API Picker lists to help you on the most common things you may want to do on a map or with location-based data, and this also suggests the API that most suits your needs.
Listed below are the useful APIs to plot a route on a map:
Polylines in the Google Maps Android API
Polylines in the Google Maps SDK for iOS
Polylines in the Google Maps JavaScript API
Directions mode in the Google Maps Embed API
Paths in the Google Static Maps API (a web service)
Links of useful APIs for whatever you want to do on a map can be found in the documentation.
Is it possible to ignore specific streets in the path planning process of the google maps api? I want to build an application where specific streets can be marked as barriers and furthermore an alternative route should be offered.
If not, can someone suggest an alternative to the google maps api where it's possible (for android development)?
You probably want to use the directions api and set way points in a way to avoid certain streets.
i'm developping an android application for tour guide using REST API and Json, so i need to make a map. i don't know what is the best to work with (google map API V2 or API V3 or OpenStreetMap)?? my boss tell me to avoid google map because google can withdraw it at any time.
As far as I know, Google maps v3 is not for Android. And seeing your tags on question, I think it's not an option for you.
As far as Google maps v2 and openStreetMap are concerned, I have always preferred Goole maps because it belongs to same Google Android belongs. So there are (probably) easier integrations and it makes sense to use it especially on Android. Besides, the point that "Google can withdraw it any time" doesn't make any sense to me. Think of the things you use on Android and what if "Google withdraws them".For why openStreetMap is better than Google maps (not from developer's point of view), see this
Founder: OpenStreetMap Already As Good Or Better Than Google Maps
The boss probably told you this, because it is NOT allowed to use the Google API for this purpose because of their terms. See 10.2 d) i)
(d) No Navigation, Autonomous Vehicle Control, or Enterprise Applications. You must not use the Service or Content with any products, systems, or applications for or in connection with any of the following:
(i) real-time navigation or route guidance, including but not limited to turn-by-turn route guidance that is synchronized to the position of a user's sensor-enabled device.
Does anybody know any free of charge android maps library that has 3D capabilities?
I know for sure that google maps doesn't support 3d when using the sdk library.
The provider is not a problem. I'm not married with google maps, nor any other.
The following are apps that can be used as example of what i'm trying to accomplish.
Waze
https://play.google.com/store/apps/details?id=com.waze
Route 66
https://play.google.com/store/apps/details?id=com.route66.maps5
Example
I want to mention this solution:
http://www.eegeo.com
It is crossplatform service with 3D modelling, routes tracking, traffic visualizing and a lot of other cool stuff.
I guess this question becomes obsolete now that we have the Google Maps Api V2 is out in the wild. Thanks everyone for taking your time to answer it.
Here's a quick release changelog
The API is now distributed as part of the Google Play services SDK, which you can download with the Android SDK Manager. To learn how to install the package, see Installing the Maps API SDK.
Maps are now encapsulated in the MapFragment class, an extension of Android's Fragment class. Now you can add a map as a piece of a larger Activity. With a MapFragment object, you can show a map by itself on smaller screens, such as mobile phones, or as a part of a more complex UI on larger-screen devices, such as tablets.
Because maps are encapsulated in the MapFragment class, you can implement them by extending the Android standard Activity class, rather than extending the MapActivity used in version 1.
The Maps API now uses vector tiles. Their data representation is smaller, so maps appear in your apps faster, and use less bandwidth.
Caching is improved, so users will typically see a map without empty areas.
Maps are now 3D. By moving the user's viewpoint, you can show the map with perspective.
Here's the new API documentation
Here's the Android Developers blog spot announcing the new API
And here's a screenshot of one of the new API early adopters Trulia
If you are looking for a 3D globe visualisation, you can use Gesium. Here is Hello World example.
We do provide one: Nutiteq 3D Maps SDK. This is SDK, not an application.
I wonder if we can get the same behavior and performance in own Andorid app with Google map? If you are using SDK (native development) the performance is diff to what you can experience while using last Google map from Android market. Are there any tips on it? I really like this smooth maps display while scroll up\down and labeling of street names, etc.
No you cannot get same performance while displaying maps in your own application. There are a couple of reasons for it:
Firstly, the code that google uses is different and they are google if you know what I mean.
Your application uses google play services while google maps by google doesnot.
I wonder if we can get the same behavior and performance in own Andorid app with Google map?
Probably not. The Google Maps application does not use the same code base as does the Google Maps add-on for Android.
#Urban's point is very valid -- the more stuff you do in overlays, the slower things will be. An ItemizedOverlay with 100+ points, for example, will definitely be felt.
But if you create an app using the Google Maps add-on without any overlays, the experience you see there is as fast as you are going to get. Overlays of any sort will only make things slower.