地理编码API的精确度是多少？ [英] How accurate are geocoding API's and what is the most accurate?

问题描述

我正在使用Google Maps API创建具有地理编码功能的应用程序。很显然，我想使用最精确的api。我给应用程序一个地址，我需要在地图上找到它，但只要找到经纬度就可以了，然后我可以使用它将其合并到我选择的任何地图API中。出于你的经验，哪个api是最准确的？谷歌，雅虎，必应等。如果你能给出一个大概的百分比，那就太棒了。到目前为止，我使用谷歌，因为它似乎是最强大的，但我会考虑改变更准确。

解决方案

所有的免费服务只能精确到路段。对于每个路段他们存储开始和结束街道号码，然后进行插值。这节省了处理时间和磁盘空间，它还增加了对新建筑的弹性。
但是，这取决于街道号码在现实生活中的分配情况，导致地址分布均匀或聚集。街边规则也可能不一致。因此，免费和低成本的服务对于紧急服务甚至一些城市规划来说都不够好。你提到了健壮性，很好的解决方法是使用多个API 。使用最健壮的第一个。如果失败了，你的程序可以尝试一个不同的。

I'm creating an application with google maps api with geocoding functionality. Obviously, I want to use the api that is the most accurate. I'm giving the application an address and I need to find it on a map, but I would be ok with just finding the latitude and longitude, and then I can use that to incorporate it into whatever map api I choose. Out of your experience, which api is the most accurate? Google, Yahoo, Bing, etc. And if you could give an approximate percentage that would be great. So far I'm using Google, as it seems to be the most robust, but I would consider changing for more accuracy.

解决方案

All of the free services are only going to be accurate to a road segment. For each road segment they store the start and end street numbers, and then interpolate. This saves processing time and disk space, it also adds some resilience against new buildings. However, it does result in evenly distributed addresses or clumping depending on how the street numbers are allocated in real life. Also side-of-street rules may not be consistent. Hence the free and low cost services are not considered good enough for emergency services and even some urban planning.

You mentioned robustness, a good fix for this is to use multiple APIs. use the most robust first. if that fails, your program can try a different one.

这篇关于地理编码API的精确度是多少？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！