Google 地图 API 与 Multimap/Bing 地图 API
我想知道是否有同时使用 Google Maps API 和 Multimap API 经验的人可以给出一个充分的理由来说明为什么其中一个比另一个更好 - 或者也许是优点和缺点的清单？
我将致力于对当前使用 Multimap（经典）API 的网站进行完全重新开发，并希望考虑使用 Google Maps API 而不是 Multimap（现在是 MS Bing）的可能性，但我需要一个令人信服的理由来证明其合理性这个决定。
该网站目前提供了一种搜索机制，允许用户使用邮政编码/部分邮政编码或城市搜索地址。当前系统有一个 sqlserver 数据库后端，包含完整的地址详细信息并上传（通过每日计划任务将此信息地理编码到 Multimap）。我想知道是否可以使用 Google API 来避免每日上传的需要，而只使用它的地理编码 API（尽管这受到 Google 每天一定数量的地理编码请求的限制）。
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).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
根据我使用这两个地图的经验，Bing 地图在地理藏宝方面更准确，但 Google 的路线图看起来稍微漂亮一些。
Google Maps API 稍微有用一些 - 例如，如果您有 2 个标记，地图会自动缩小到正确的级别，Bing 需要更多的工作。
两者的航空地图看起来几乎相同，混合地图也是如此。
我的建议是 - 使用 Bing 地图进行地理藏宝，然后如果您想要非常漂亮的路线图，请使用 Google。如果您使用鸟瞰图、混合视图或鸟瞰图，您不妨继续使用 Bing。
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.
根据 Wikipedia Multimap 几年前被微软收购，其方向功能被合并到微软必应 API。我认为 Multimap API 主要是为了遗留目的而存在的。到 2010 年底，multimap 可能会消失，因此这绝对是重新编写应用程序的地理编码部分的一个令人信服的理由...
无论如何，我会联系 Multimap 他们计划支持其 API 多长时间以及是否有迁移路径（可能是 bing 地图）。
Bing 地图和 Google 地图现在通过 Javascript 提供实时地理编码服务（请参阅 http://msdn.microsoft.com/en-us/library/ff710027.aspx 中的 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.
是的，跳过旧的 Multimap 并使用 Google 地图或 Bing 地图。两者都在积极竞争并积极发展。因此，一个人可能会在几个月内在某个领域表现得更好，但很可能会发生变化。例如。 Bing 地图是第一个支持多点触控（使用 Silverlight）的地图，但 Google 地图现在通过其 v3 API 支持它。 （不幸的是，除了最基本的地图覆盖之外，所有内容都会崩溃 Google 地图多点触控应用程序会在最广泛使用的多点触控平台上崩溃：iPad/iPhone 上的 Safari）。
目前，我认为 Bing 地图具有优势，但最终您的决定可能会是主观的（这些地图看起来更好/我发现 API 稍微好一些/等等），或者取决于EULA（即您是否为您的特定应用程序支付费用？以及支付多少费用？）。
您谈到了地理编码。越来越多的人正在考虑使用多个地理编码平台。主要是因为所有服务的地理编码覆盖范围并不完善，但如果一项服务出现故障，它也可以为您提供保障。
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.