iOS5 反向地理编码限制
我正在使用 Apple 提供的反向地理编码（链接到本文底部的开发文档）。
我已经将其设置为与我当前的项目一起使用。当我触摸地图时，触摸点会转换为我在反向地理编码中使用的坐标。但问题是，当我对欧洲、北美和南美部分地区的位置进行地理编码时，我只能获得有关地址（街道、门牌号、国家/地区等）的信息。在对非洲和亚洲的坐标进行反向地理编码时，我没有得到此信息。
我使用正向地理编码（非洲和亚洲的一些随机地址）来检查是否可以通过所有信息找到这些地址。他们可以——前向地理编码效果非常好。
那么，当我用非洲和亚洲的坐标反转地理编码时，怎么可能没有获得地址信息呢？有人经历过同样的事情吗？
I'm using the Reverse Geocoding provided by Apple (Linked to the dev documentation at the bottom of this post).
I have set this up to work with my current project. When I touch the map, the touchPoint is converted to coordinates which I use with my reverse geocoding. The problem is though, that I only get information regarding address (street, housenumber, country and so on) when I geocode a location from Europe, North America and parts of South America. I do NOT get this information when doing a reverse geocoding on coordinates from Africa and Asia.
I used Forward Geocoding (some random addresses in Africa and Asia) to check if these could be found with all the information. And they could - the forward geocoding works brilliant.
So how can it be, that I don't get address information when I reverse the geocoding with coordinates from especially Africa and Asia? Anyone experienced the same thing?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
反向地理编码（请参阅返回的错误消息 kCLErrorGeocodeFoundPartialResult 和 kCLErrorGeocodeFoundNoResult）。很多时候，只有美国、欧洲和世界上人口稠密的城市会返回完整的反向地址信息。
当 kCLErrorGeocodeFoundPartialResult 发生时，意味着只有一部分反向地理编码信息可用。这可能是街道名称（个人地址，意思是房屋/bdlg 或地段#）不可用。信息可能越来越少，只剩下国家名称。
这是因为与 Google 一起使用时，卫星仅返回纬度和纬度。长。由谷歌或其他地图公司提供数据点和数据点区域信息（指建筑物为地址占据的点周围的纬度/经度和跨度）。因为必须从世界各地的每个城市获取这些信息，然后进行验证并输入数据 - 这是 Google 十多年来一直在积极开展的一项艰巨任务。目前，地球上只有不到 7% 的陆地大部分已进行地理编码。雪上加霜的是，美国和大多数欧洲国家在市一级的组织相对良好，拥有最新的地图和地块/地块位置。对于世界许多其他地区来说，情况并非如此。
因此，开发人员需要筛选可用信息并构造注释标注信息，使其从返回的有限信息中最有意义。同样，这可能只是国家/地区名称。
另外，如果您的用户在五大湖或哈德逊河中落下一枚别针，请不要忘记海洋和内陆水域字段。
名称字段对于地标也很有帮助。
是的，最后，要弄清楚如何最好地显示从反向地理编码查找返回的地点标记数据，需要做很多工作，但您的用户会感谢您尝试了您能想到的每种可能性。
上述信息以及完整地理编码和部分地理编码国家/地区的列表位于 Apple 文档中。您会惊讶地发现这些名单上的国家如此之少！
Reverse GeoCoding (See error message returned kCLErrorGeocodeFoundPartialResult and kCLErrorGeocodeFoundNoResult). Many times only the US, Europe and densely populated cities of the world return full reverse address information.
When kCLErrorGeocodeFoundPartialResult occurs, that mean only a portion of the reverse geocode information is available. This may be the street name (individual addresses, meaning house/bdlg or lot#) is not available. This could be less and less information down to just the country name.
This is because for use with Google, the satellites only return lat & lon. It is up to Google or other mapping companies to provide data points and data point region information (meaning lat/lon and span around that point that a bldg would occupy for an address). Because this information has to be acquired from each and every single municipality around the world, then verified and data entered - it is a HUGE undertaking for which Google has been actively doing for over 10 years. In this time, there is less than 7% of the earth's land masses that is majority geocoded. Adding to this difficulty is that the US and the Majority of Europe are relatively well organized at the municipality level with up to date maps and parcel/lot locations. That same is not true for many other areas of the world.
So it is up to you, the developer, to sift through the available information and structure the annotation callout information that makes the most sense from the limited information returned. Again, this may just be the Country Name.
Also, don't forget about Ocean and InlandWater fields for if you user drops a pin in the great Lakes or the Hudson River.
the Name field is also helpful for Landmarks.
Yes, in the end, there is a lot of juggling to figure out how best to display place mark data returned from a reverse geocode lookup, but your users will thank you for trying out every possibility you can think of.
The above information as well as lists for full geocode and partial geocode countries is in the Apple Documentation. You would be surprised to see just how few countries there are on those lists!