反向地理编码 API (ZERO_RESULTS) 无法识别地理编码 API 坐标
Geocode API coordinates not recognized by the reverse geocode API (ZERO_RESULTS)
如果我像这样向 Geocode API 发出请求来检查位置的坐标 https://maps.googleapis.com/maps/api/geocode/json?address=Los%20Angeles,%20CA,%20United%20States&key=your-browser-key
然后它 returns 34.0522342,-118.2436849 对于 LA，如果我然后去 reverse geocode API 并输入那些坐标那么它没有显示结果？
这怎么可能？ API a 返回了一组 API b 无法识别的数据？他们不应该使用相同的数据吗？
这是某种错误，还是我哪里做错了什么？
我刚从 Google
收到以下消息
Dear Maps APIs Premium Plan customers,
Reverse geocoding results in the Geocoding API will soon be updated to provide better quality worldwide. While the new results will often be different from the current results and contain different Place IDs, they should not require adjustments in client applications.
The new results are currently rolled out to non-Premium-Plan users. We plan to make the new results the default for Premium Plan customers on September 17th 2018.
Applications can preview the new results ahead of September 17th by adding the new_reverse_geocoder=true parameter to their Geocoding API requests. Please note that adding this parameter to requests without the latlng parameter will result in an error response (INVALID_REQUEST).
The new results can also be visualized by clicking on the base map (or entering a latlng) in the Geocoder Tool at https://google-developers.appspot.com/maps/documentation/utils/geocoder/
The new results provide the following improvements:
- Increased ratio of rooftop results in favor of interpolated addresses.
- Decreased ratio of requests receiving only political results like a city or a neighborhood (ie, incomplete addresses).
- Decreased distance from input latlng coordinates to the nearest result.
- In areas with sparse coverage, establishments are returned in addition to geocodes.
- Decreased ratio of requests receiving results more than 400 meters from the input latlng.
Please let us know if you find issues with the new results. Quality issues are best reported in the Maps API public issue tracker at https://issuetracker.google.com.
因此，如您所见，Google 正在启动新版本的反向地理编码器。我用旧版本尝试了你的请求，添加了 &new_reverse_geocoder=false 参数并得到了结果
https://maps.googleapis.com/maps/api/geocode/json?latlng=34.0522342%2C-118.2436849&new_reverse_geocoder=false&key=MY_API_KEY
在这一点上，它看起来像是在新版本的反向地理编码器中回归。
更新
Google 在错误中跟踪此问题：
如果我像这样向 Geocode API 发出请求来检查位置的坐标 https://maps.googleapis.com/maps/api/geocode/json?address=Los%20Angeles,%20CA,%20United%20States&key=your-browser-key
然后它 returns 34.0522342,-118.2436849 对于 LA，如果我然后去 reverse geocode API 并输入那些坐标那么它没有显示结果？
这怎么可能？ API a 返回了一组 API b 无法识别的数据？他们不应该使用相同的数据吗？
这是某种错误，还是我哪里做错了什么？
我刚从 Google
收到以下消息Dear Maps APIs Premium Plan customers,
Reverse geocoding results in the Geocoding API will soon be updated to provide better quality worldwide. While the new results will often be different from the current results and contain different Place IDs, they should not require adjustments in client applications.
The new results are currently rolled out to non-Premium-Plan users. We plan to make the new results the default for Premium Plan customers on September 17th 2018.
Applications can preview the new results ahead of September 17th by adding the new_reverse_geocoder=true parameter to their Geocoding API requests. Please note that adding this parameter to requests without the latlng parameter will result in an error response (INVALID_REQUEST).
The new results can also be visualized by clicking on the base map (or entering a latlng) in the Geocoder Tool at https://google-developers.appspot.com/maps/documentation/utils/geocoder/
The new results provide the following improvements:
- Increased ratio of rooftop results in favor of interpolated addresses.
- Decreased ratio of requests receiving only political results like a city or a neighborhood (ie, incomplete addresses).
- Decreased distance from input latlng coordinates to the nearest result.
- In areas with sparse coverage, establishments are returned in addition to geocodes.
- Decreased ratio of requests receiving results more than 400 meters from the input latlng.
Please let us know if you find issues with the new results. Quality issues are best reported in the Maps API public issue tracker at https://issuetracker.google.com.
因此，如您所见，Google 正在启动新版本的反向地理编码器。我用旧版本尝试了你的请求，添加了 &new_reverse_geocoder=false 参数并得到了结果
https://maps.googleapis.com/maps/api/geocode/json?latlng=34.0522342%2C-118.2436849&new_reverse_geocoder=false&key=MY_API_KEY
在这一点上，它看起来像是在新版本的反向地理编码器中回归。
更新
Google 在错误中跟踪此问题：