I want to know if anyone who has experience of using both the Google Maps API and the Multimap API can give a good reason as to why one is better than the other - or maybe a list of pros and cons?
I will be working on a complete re-development of a site which currently uses the Multimap (Classic) API and want to consider the possibility of using Google Maps API instead of Multimap (now MS Bing), but I need a compelling reason to justify this decision.
The site currently provides a search mechanism allowing users to search for addresses using postcode/partial postcode or city. The current system has a sqlserver database back-end containing full address details and also uploads (geocodes this information to Multimap with a daily scheduled task). I'm wondering if it's possible with the Google API to avoid the need for the daily upload and just use it's geocoding API instead (though this is limited by Google's restriction of a certain number of geocoding requests per day).
In my experience using the two, Bing Maps are more accurate with regards to their geocaching, but Google have slightly nicer looking Road Maps.
The Google Maps API is slightly more helpful - for example, if you have 2 markers, the map automatically zooms out to the right level, Bing takes a bit more work.
Aerial maps look pretty much the same on both, as do the Hybrid maps.
My advice would be - use Bing maps for geocaching, then if you want really nice looking road maps, use Google. If you're using Aerial, Hybrid or Birdseye view, you might as well stick with Bing.
According to Wikipedia Multimap was purchased by Microsoft some years ago and its direction features were merged into the Microsoft Bing api. I suppose the Multimap API primarily exists for legacy purposes. By the end of 2010 multimap might disappear, so this is definitely a compelling reason to re-write the geocoding part of your app...
In any case I would contact Multimap how long they plan to support their API and if there is a migration path (probably to bing maps).
Bing Maps as well as Google Maps now offer real-time geocoding services over Javascript (see http://msdn.microsoft.com/en-us/library/ff710027.aspx for an example in bing). Which one to pick? Check the terms of usage and the costs of the geocoding requests per day.
Yes skip the old legacy Multimap and use Google Maps or Bing Maps. Both are in active competition and under active development. So one might be better in one area for a few months but the chances are it will change. Eg. Bing Maps was the first with multi-touch support (using Silverlight) but Google Maps now supports it with its v3 API. (unfortunately all but the most basic map overlays will crash Google Maps multi-touch apps crash with the most widely available multi-touch platform: Safari on the iPad/iPhone).
At the moment I think Bing Maps has the edge, but at the end of the day your decision is probably going to be subjective (those maps look nicer / I find the API slightly nicer / etc), or depending on the exact wording of the EULA (ie. do you pay? and how much? for your specific application).
You talked about geocoding. An increasing number of people are looking at using multiple geocoding platforms. Primarily because geocoding coverage of all the services are imperfect, but it also gives you cover if one service goes down.
Related
Starting June 11, 2018: All Gogle Maps Platform API requests must include an API key; we no longer support keyless access. I heard that the gogle maps api-key is not free. Does anyone know any free alternatives it?
I am student.I need a map api and I don't have eneugh money.
I've used openstreetmap.org for a few projects, works well. That being said... a small project using the google api will usually not generate enough traffic to warrant any costs, as you're given a certain amount of traffic for free every month.
I am about to start a new project which will be used about 80% through non-mobile devices like desktops and laptops and 20% through mobile devices. And yes, I want to use KML capabilities too, use JQuery for all my JS work and do not want users to download any plugin separately.
I have implemented two projects already using Google Maps API blissfully unaware of Google Earth API. Now I started reading about the two and nothing is clear about what is the right choice. I even referred to posts on this site so please do not mark this as a duplicate.
Google's documentation on Google Earth API states:
Welcome to the developer documentation for the Google Earth API. The Google Earth Plugin and its JavaScript API let you embed the full power of Google Earth and its 3D rendering capabilities into your web pages. Just like in the Google Maps API, you can draw markers and lines—but in 3D!
Well, with that statement from the horse's mouth, it confused me even more. Why would anyone use Maps API then. Can someone with experience in both these tools, give some definite statements for the specific environment I have described? The earlier posts do not give convincing answers.
I believe when I last looked Google Earth support in the browser is implemented through the use of Web GL which will severely limit your browser support and I think eliminate mobile devices.
While Earth may be prettier Maps is more performant and arguably stable and I would think it would be the logical choice for you in this case.
This page contradicts some of this but requires the use of a plugin which you specify you do not want.
For information on using KML layers with the Maps API see here.
Here is how I understand the situation.
There were two similar but different products co-existing for a long time:
2D Maps born on web
3D Earth born on desktop and brought to the web as plugin.
This caused a lot of confusion.
It would be beneficial to unite the two, but that only became possible recently with WebGL.
Last week Google released new Maps having Earth integrated.
Unfortunately, I was not able to find any documentation about this integration yet.
But, still, my answer is: use Maps and eventually you'll get Earth for free.
I have 3 weeks to develop a prototype. Bascially a fleet management system, browser based. It will be tracking tractors in open country, using low data rate satellite modems to report vehicle location on a regular basis.
I am struggling to get a grip on whether I want to use Google Earth or Google Maps:
ease of implementation (PHP/HTML 5, pulling data from a MySql database)
tracking each vehicle, drawing a line, toggle display of time and/or distance travelled at each location
visual appeal to user (given that it is open country, no real landmarks)
available overlays (rainfall, temperature data, elevation, etc)
anythign else?
I am toally at a loss on the mapping part (the reast I can do). Is one of Google Earth / Maps "best " for me? (not wanting to start a religious war)
Is it possible to use both and toggle between them?
Any other advice? I am googling like crazy and might not normally post this question before doing more research, but the dealine is ricdicuous. I am look at 16 hour days and need all of the help and advice that I can get. I will will have to live with the decision that I make now and I don't want to make a hasty one based on scant knowledge.
Thanks in advance...
[Update] oic. Google Earth is PC applicaion and Gogole maps is browser based. Well, I guess that that answers that, then.
[Update] Sigh! It's another of those where the head of the company uses an I-pad but the end users have Windows desktops. So he wants it browser based "just in case" he wants to look at it (which he might do twice in the first week and then never again). Why does it always seem to be this way?
To identify the right solution, you first need to identify your target audience for your app.
Will the users of the web-based app be using desktops, iPads, or
mobile devices that have Google Earth available?
Will the intented users be using large screens located at the data center (Google Earth or Google Maps will work) or remote users in the field (Google Maps might be best better fit)?
Not all mobile devices support the Google Earth application and the
mobile devices have a limited feature set.
Google Maps API, on the other hand, will run on nearly all web
browsers for a multiple of devices.
See details:
Google Earth for Mobile
http://www.google.com/earth/explore/products/mobile.html
Google Maps for Mobile
http://www.google.com/mobile/maps/
Also note if you use Google Earth API you can easily mashup Earth and Maps in single web application but again this requires those platforms that support the Google Earth client.
Here's a sample demo to try out:
http://earth-api-samples.googlecode.com/svn/trunk/demos/drive-simulator/index.html
Future proof your application. It is my impression Google Earth is on it's way out. It is hardly maintained and with browser makers actively discouraging the use of these plugins it is only a matter of time.
If you choose to use the Google mapping tools, do have a close look at Google Maps. Although Google currently offers a 3D version of Google Maps, it is not yet available for application developers. We are still stuck with 2D maps.
However, I expect that the maps API will not change drastically once 3D applications are allowed.
I am a specialist in the use of Google Earth API (planetinaction.com) and I have shifted from Google Earth to Google Maps wherever possible.
As an intermediate solution, you could build a maps based app but allow a 3D view option by popping up a Google Earth plugin. this keeps Google Earth dependencies to a minimum.
I have several questions here:
Which service to use (google vs bing) to display lots of (let say 100.000 and more) pushpins on the map?
What is a fastest way to do that, load all at the same time, or load 100 pushpins in the area you zoomed in, to use kml feeds.. (what about caching..?)
I would prefer Bing map, as it has nice birds' view. Is it a good approach to choose AJAX API vs web services or silverlight implementation for such task?
I tried Bing Map javascript API and when I run StartGeocoding(address), it points to the the street next to that address/house, when Bing Map online points directly to that house. How to reach the same precise results using javascript API?
I will have to display lots of places on the map, so I want to choose a right approach and service before starting a project.
I recommend google as well. I noticed that Bing is really big on Silverlight which i find to be more of a performance hog compared to javascript. I just like google's User Experience way better for Maps as well as their image searching/viewer (google's javascript version is faster and feels faster than Bing's silverlight counterpart).
Consider using Google Fusion Tables. Add your data to a Fusion Table and then it can be displayed using the Google Maps API very efficiently.
Which JavaScript map API do you folks think is the most powerful?
Google? Bing?
Think about which map is more suitable for you, have all the places you need. In US and Europe Google, Bing, Yahoo have pretty similar maps. However if you need other countries (in Asia, South America, Eastern Europe, Africa), the only answer is OpenStreetMap.
About API. The most powerful and flexible is OpenLayers, it allows you to connect to different map services. However it is a bit slow and complicated.
In opposite Google API is fast and small, however it is bound to Google Maps.
If you are looking for some API contacting OpenStreetMap data, try Cloudmade.
Still choose the map first, and then select the most natural API for it.
I talk about my reasons for using the Google Maps API in this answer.
Top mapping tool must be ViaMichelin.
A independant poll carried out by the IMA said
ViaMichelin
Mappy
Microsoft
Yahoo
Map 24
Google
Poll was based on brand, quality, customisation, coverage, support, SLA, price, usability, speed, and 17 other criterias.
I thought that this was an interesting article on why Redfin decided to switch from Virtual Earth (Bing) to Google Maps.
I think the most powerful map API is Mapstraction - an abstraction layer that supports all the major mapping APIs, allowing you to switch providers without having to refactor your code.