Android 逆地理编码geocoding
Android 逆地理编码geocoding
iSnowFlake 发表于2年前
Android 逆地理编码geocoding
  • 发表于 2年前
  • 阅读 1040
  • 收藏 6
  • 点赞 0
  • 评论 1

腾讯云 新注册用户 域名抢购1元起>>>   

摘要: Android 逆地理编码一般有两种方式:Android 系统的Geocoder类和web api(不包含国内的百度高德封装的SDK),但是前者早就不建议使用了,本文是介绍后一种,本文说的大部分内容需要使用VPN 来查看了解。

       地理编码和逆地理编码都差不多,这里总结一下逆地理编码,根据经纬度解析出地址。Android这边逆地理编码方式主要是两种(不包含高德,百度)一种是使用Android 系统的Geocoder类来解析(这种方法过时而且不实用,经常失败,在中国和印尼都有测试数据,而且部分手机阉割了,这种方法如果想要了解请参考;另外一种是使用Google 的web api;

        请开VPN点击体验:,116.403945&language=zh-CN&sensor=false;详细的参数请参见Google 官方说明:;这里介绍Android的使用:

public interface LocationCallBack {
 void geoCodeSuccess(String address);
 void geoCodeFailure(String address); 
2.geocode 的封装
 * @author
public class BipGeoCoder {
 private List<RealTimeAddrGeoDataBean> realTimeAddrGeoDataBeans=null;
 private RequestQueue mQueue = null;
 private Context context;
 private String address;
    public BipGeoCoder(Context context) {
  this.context = context;
     * 获取地址通过Web service
    public void getAddress(final double latitude, final double longitude,final String defAddress,final LocationCallBack locationCallBack){     
        String requestUrl=VolleyParamsBuild.newBuilder().putParam("language", "en-ww")  //en-ww 可以根据业务逻辑替换为不同的国家语言
                                                  .putParam("latlng", latitude+","+longitude)
  JsonObjectRequest stringRequest = new JsonObjectRequest(requestUrl, null,
    new Response.Listener<JSONObject>() {
     public void onResponse(JSONObject response) {
         TypeFactory tf =  JsonUtil.getMapper().getTypeFactory();
         JavaType jt = tf.constructParametricType(List.class, RealTimeAddrGeoDataBean.class);
         try { 
       String json = response.getString("results").toString();
       realTimeAddrGeoDataBeans = JsonUtil.getMapper().readValue(json, jt);
         } catch (JsonParseException e) {
         } catch (JsonMappingException e) {
         } catch (IOException e) {
         } catch (JSONException e) {
       // TODO Auto-generated catch block
//         Log.d("Addr","Geocoding:"+address);
    }, new Response.ErrorListener() {
     public void onErrorResponse(VolleyError error) {

 new BipGeoCoder(getActivity()).getAddress(obj.getLatitude(), obj.getLongitude(), locationdef,new LocationCallBack() {
   public void geoCodeSuccess(String address) {
    // TODO Auto-generated method stub

   public void geoCodeFailure(String address) {
    // TODO Auto-generated method stub



以下内容来自Google ,使用前请翻墙


The Google Maps Geocoding API

This service is also available as part of the Google Maps JavaScript API, or the Java and Python client libraries.

What is Geocoding?

Geocoding is the process of converting addresses (like "1600 Amphitheatre Parkway, Mountain View, CA") into geographic coordinates (like latitude 37.423021 and longitude -122.083739), which you can use to place markers on a map, or position the map.

Reverse geocoding is the process of converting geographic coordinates into a human-readable address. The Google Maps Geocoding API's reverse geocoding service also lets you find the address for a given place ID.

The Google Maps Geocoding API provides a direct way to access these services via an HTTP request.

Before You Begin

This document is intended for website and mobile developers who want to use geocoding data within maps provided by one of the Google Maps APIs.

This service is generally designed for geocoding static (known in advance) addresses for placement of application content on a map; this service is not designed to respond in real time to user input, for example. For dynamic geocoding (for example, within a user interface element), consult the documentation for the Google Maps JavaScript API Client Geocoder and/or the Google Play services Location APIs.

Geocoding is a time and resource intensive task. Whenever possible, pre-geocode known addresses (using the Google Maps Geocoding API described here or another geocoding service), and store your results in a temporary cache of your own design.

To use the Google Maps Geocoding API, you need an API key.


Google Maps Geocoding API Request Format

A Google Maps Geocoding API request must be of the following form:

where output may be either of the following values:

  • json (recommended) indicates output in JavaScript Object Notation (JSON)

  • xml indicates output as XML

To access the Google Maps Geocoding API over HTTP, use:

HTTP is not recommended for applications that include sensitive user data, such as a user's location, in requests.

Some parameters are required while some are optional. As is standard in URLs, parameters are separated using the ampersand (&) character.

Google Maps API for Work users must include valid client and signature parameters with their Geocoding requests. Please refer to Google Maps API for Work Web Services for more information.

The rest of this page describes geocoding and reverse geocoding separately, because different parameters are available for each type of request.

Geocoding (Latitude/Longitude Lookup)

Required parameters in a geocoding request:

  • address — The street address that you want to geocode, in the format used by the national postal service of the country concerned. Additional address elements such as business names and unit, suite or floor numbers should be avoided. Please refer to the FAQ for additional guidance. 
    components — A component filter for which you wish to obtain a geocode. See Component Filtering for more information. The components filter will also be accepted as an optional parameter if an address is provided.

  • key — Your application's API key. This key identifies your application for purposes of quota management. Learn how to get a key.

Optional parameters in a geocoding request:

  • bounds — The bounding box of the viewport within which to bias geocode results more prominently. This parameter will only influence, not fully restrict, results from the geocoder. (For more information see Viewport Biasing below.)

  • language — The language in which to return results. See the list of supported domain languages. Note that we often update supported languages so this list may not be exhaustive. Iflanguage is not supplied, the geocoder will attempt to use the native language of the domain from which the request is sent wherever possible.

  • region — The region code, specified as a ccTLD ("top-level domain") two-character value. This parameter will only influence, not fully restrict, results from the geocoder. (For more information see Region Biasing below.)

  • components — The component filters, separated by a pipe (|). Each component filter consists of a component:value pair and will fully restrict the results from the geocoder. For more information see Component Filtering, below.

共有 人打赏支持
粉丝 31
博文 77
码字总数 53599
评论 (1)
(retrofit demo :
* 金额(元)
¥1 ¥5 ¥10 ¥20 其他金额
* 支付类型