Google Maps API vs Multimap/Bing Maps API

Posted by mdresser on Stack Overflow See other posts from Stack Overflow or by mdresser
Published on 2010-06-17T10:30:36Z Indexed on 2010/06/17 10:33 UTC
Read the original article Hit count: 1315

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).

© Stack Overflow or respective owner

Related posts about google-maps-api

Related posts about bing-maps