为什么Google地理编码器会给出与地图搜索不同的结果? [英] Why does the google geocoder give different results from the map search?

问题描述

例如，使用主地图搜索的位置明显不同，地理编码服务无用，至少对于我来说是无用的.

For example, searching for "36 High Street Clapham London SW4 7UR" using the geocoder gives a significantly different location from the main map search, rendering the geocoding service useless, for my purposes at least.

有人知道为什么会这样吗，是否有解决方法?

Anyone know why this is and if there's a workaround?

推荐答案

在英国地理编码中需要注意的一件事是，皇家邮政拥有英国邮政编码地理信息的版权，并且拒绝出售Google的再分发许可该信息. Google拥有许可帽，允许其将信息用于在自己的网站上进行地理编码，但不能用于其他人的网站.这并不能解释该特定地址，但确实会影响许多英国位置的地理编码.

One thing to watch out for in UK geocoding is that the Royal Mail owns the copyright to UK postcode geographic information, and has refused to sell Google a licence to redistribute that information. Google has a licence hat allows it to use the information for geocoding on its own websites, but not for other people's websites. That doesn't explain that particular address, but it does affect the geocoding of many UK locations.

前一段时间，API地理编码器中存在一个错误(maps.google.com地理编码未受影响)，导致该错误信息显示了街道上某些门牌号码的存在.这可能再次发生.请注意，伦敦Clapham High Street 34"正确地进行了地理编码，但API认为不存在36，因此仅返回了精度为6(街道)而不是精度为8(地址)的位置.这可能再次发生.如果您认为发生了这种情况，请找到几个令人信服的示例，然后将其发布到讨论组 a>.

There was a bug in the API geocoder (maps.google.com geocoding was not affected) a while ago that caused it to get wrong information about the existence of certain house numbers in a street. It's possible that this might be happening again. Note that "34 Clapham High Street, London" geocodes correctly, but the API thinks that 36 doesn't exist, and just returns a location with accuracy=6 (street) instead of accuracy=8 (address). This might possibly be happening again. If you think that's what's happening, find several convincing examples and post them to the discussion group.

这篇关于为什么Google地理编码器会给出与地图搜索不同的结果?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！