Skip to content

Most visited

Recently visited


Displaying a Location Address

The lessons Getting the Last Known Location and Receiving Location Updates describe how to get the user's location in the form of a Location object that contains latitude and longitude coordinates. Although latitude and longitude are useful for calculating distance or displaying a map position, in many cases the address of the location is more useful. For example, if you want to let your users know where they are or what is close by, a street address is more meaningful than the geographic coordinates (latitude/longitude) of the location.

Using the Geocoder class in the Android framework location APIs, you can convert an address to the corresponding geographic coordinates. This process is called geocoding. Alternatively, you can convert a geographic location to an address. The address lookup feature is also known as reverse geocoding.

This lesson shows you how to use the getFromLocation() method to convert a geographic location to an address. The method returns an estimated street address corresponding to a given latitude and longitude.

Get a geographic location

The last known location of the device is a useful starting point for the address lookup feature. The lesson on Getting the Last Known Location shows you how to use the getLastLocation() method provided by the fused location provider to find the latest location of the device.

To access the fused location provider, create an instance of FusedLocationProviderClient. To learn how to create your client, see Create a Location Services client.

To enable the fused location provider to retrieve a precise street address, set the location permission in your app manifest to ACCESS_FINE_LOCATION, as shown in the following example:

<manifest xmlns:android=""
    package="" >

  <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>

Define an intent service to fetch the address

The getFromLocation() method provided by the Geocoder class accepts a latitude and longitude and returns a list of addresses. The method is synchronous and may take a long time to do its work, so you should not call it from the main, user interface (UI) thread of your app.

The IntentService class provides a structure for running a task on a background thread. Using this class, you can handle a long-running operation without affecting your UI's responsiveness. Note that the AsyncTask class also allows you to perform background operations, but it's designed for short operations. An AsyncTask shouldn't keep a reference to the UI if the activity is re-created, such as when the device is rotated. In contrast, an IntentService doesn't need to be cancelled when the activity is rebuilt.

Define a FetchAddressIntentService class that extends IntentService. This class is your address lookup service. The intent service handles an intent asynchronously on a worker thread and stops itself when it runs out of work. The intent extras provide the data needed by the service, including a Location object for conversion to an address and a ResultReceiver object to handle the results of the address lookup. The service uses a Geocoder to fetch the address for the location and sends the results to the ResultReceiver.

Define the intent service in your app manifest

Add an entry to your app manifest that defines the intent service, as shown here:

<manifest xmlns:android=""
    package="" >

Note: The <service> element in the manifest doesn't need to include an intent filter because your main activity creates an explicit intent by specifying the name of the class to use for the intent.

Create a Geocoder

The process of converting a geographic location to an address is called reverse geocoding. To perform the main work of the intent service (your reverse geocoding request), implement onHandleIntent() within the FetchAddressIntentService class. Create a Geocoder object to handle the reverse geocoding.

A locale represents a specific geographical or linguistic region. Locale objects adjust the presentation of information, such as numbers or dates, to suit the conventions in the region that is represented by the locale. Pass a Locale object to the Geocoder object to ensure that the resulting address is localized to the user's geographic region. Here is an example:

protected void onHandleIntent(Intent intent) {
    Geocoder geocoder = new Geocoder(this, Locale.getDefault());
    // ...

Retrieve the street address data

You can now retrieve the street address from the geocoder, handle any errors that may occur, and send the results back to the activity that requested the address. To report the results of the geocoding process, you need two numeric constants that indicate success or failure. Define a Constants class to contain the values, as shown in this code snippet:

public final class Constants {
    public static final int SUCCESS_RESULT = 0;
    public static final int FAILURE_RESULT = 1;
    public static final String PACKAGE_NAME =
    public static final String RECEIVER = PACKAGE_NAME + ".RECEIVER";
    public static final String RESULT_DATA_KEY = PACKAGE_NAME +
    public static final String LOCATION_DATA_EXTRA = PACKAGE_NAME +

To get a street address corresponding to a geographical location, call getFromLocation(), passing it the latitude and longitude from the location object and the maximum number of addresses that you want returned. In this case, you want just one address. The geocoder returns an array of addresses. If no addresses are found to match the given location, it returns an empty list. If there is no backend geocoding service available, the geocoder returns null.

Check for the following errors, as shown in the code sample below:

If an error occurs, place the corresponding error message in the errorMessage variable so that you can send it back to the requesting activity.

To get the individual lines of an address object, use the getAddressLine() method that is provided by the Address class. Join the lines into a list of address fragments ready to return to the activity that requested the address.

To send the results back to the requesting activity, call the deliverResultToReceiver() method (defined in Return the address to the requestor). The results consist of the previously-mentioned numeric success/failure code and a string. In the case of a successful reverse geocoding, the string contains the address. In the case of a failure, the string contains the error message, as shown in this code sample:

protected void onHandleIntent(Intent intent) {
    String errorMessage = "";

    // Get the location passed to this service through an extra.
    Location location = intent.getParcelableExtra(

    // ...

    List<Address> addresses = null;

    try {
        addresses = geocoder.getFromLocation(
                // In this sample, get just a single address.
    } catch (IOException ioException) {
        // Catch network or other I/O problems.
        errorMessage = getString(R.string.service_not_available);
        Log.e(TAG, errorMessage, ioException);
    } catch (IllegalArgumentException illegalArgumentException) {
        // Catch invalid latitude or longitude values.
        errorMessage = getString(R.string.invalid_lat_long_used);
        Log.e(TAG, errorMessage + ". " +
                "Latitude = " + location.getLatitude() +
                ", Longitude = " +
                location.getLongitude(), illegalArgumentException);

    // Handle case where no address was found.
    if (addresses == null || addresses.size()  == 0) {
        if (errorMessage.isEmpty()) {
            errorMessage = getString(R.string.no_address_found);
            Log.e(TAG, errorMessage);
        deliverResultToReceiver(Constants.FAILURE_RESULT, errorMessage);
    } else {
        Address address = addresses.get(0);
        ArrayList<String> addressFragments = new ArrayList<String>();

        // Fetch the address lines using getAddressLine,
        // join them, and send them to the thread.
        for(int i = 0; i <= address.getMaxAddressLineIndex(); i++) {
        Log.i(TAG, getString(R.string.address_found));

Return the address to the requestor

The final action that the intent service must complete is sending the address back to a ResultReceiver in the activity that started the service. The ResultReceiver class allows you to send a numeric result code as well as a message containing the result data. The numeric code is useful for reporting the success or failure of the geocoding request. In the case of a successful reverse geocoding, the message contains the address. In the case of a failure, the message contains some text describing the reason for the failure.

You have already retrieved the address from the geocoder, trapped any errors that may occur, and called the deliverResultToReceiver() method, so now you must define the deliverResultToReceiver() method that sends a result code and message bundle to the result receiver.

For the result code, use the value that you've passed to the deliverResultToReceiver() method in the resultCode parameter. To construct the message bundle, concatenate the RESULT_DATA_KEY constant from your Constants class (defined in Retrieve the street address data) and the value in the message parameter that is passed to the deliverResultToReceiver() method, as shown in the following sample:

public class FetchAddressIntentService extends IntentService {
    protected ResultReceiver mReceiver;
    // ...
    private void deliverResultToReceiver(int resultCode, String message) {
        Bundle bundle = new Bundle();
        bundle.putString(Constants.RESULT_DATA_KEY, message);
        mReceiver.send(resultCode, bundle);

Start the intent service

The intent service, as defined in the previous section, runs in the background and fetches the address corresponding to a given geographic location. When you start the service, the Android framework instantiates and starts the service if it isn't already running, and it creates a process if needed. If the service is already running, it remains running. Because the service extends IntentService, it shuts down automatically after all intents are processed.

Start the service from your app's main activity and create an Intent to pass data to the service. You need an explicit intent because you want only your service to respond to the intent. For more information, see Intent Types.

To create an explicit intent, specify the name of the class to use for the service: FetchAddressIntentService.class. Pass this information in the intent extras:

The following code sample shows you how to start the intent service:

public class MainActivity extends AppCompatActivity implements
        ConnectionCallbacks, OnConnectionFailedListener {

    protected Location mLastLocation;
    private AddressResultReceiver mResultReceiver;

    // ...

    protected void startIntentService() {
        Intent intent = new Intent(this, FetchAddressIntentService.class);
        intent.putExtra(Constants.RECEIVER, mResultReceiver);
        intent.putExtra(Constants.LOCATION_DATA_EXTRA, mLastLocation);

Caution: To ensure that your app is secure, always use an explicit intent when starting a Service and do not declare intent filters for your services. Using an implicit intent to start a service is a security hazard because you cannot be certain of the service that will respond to the intent, and the user cannot see which service starts.

Call the above startIntentService() method when the user takes an action that requires a geocoding address lookup. For example, the user may press a Fetch address button on your app's UI. The following code snippet shows the call to the startIntentService() method in the button handler:

private void fetchAddressButtonHander(View view) {
            .addOnSuccessListener(this, new OnSuccessListener<Location<() {
                public void onSuccess(Location location) {
                    mLastKnownLocation = location;

                    // In some rare cases the location returned can be null
                    if (mLastKnownLocation == null) {

                    if (!Geocoder.isPresent()) {

                    // Start service and update UI to reflect new location

Receive the geocoding results

After the intent service handles the geocoding request, it uses a ResultReceiver to return the results to the activity that made the request. In the activity that makes the request, define an AddressResultReceiver that extends ResultReceiver to handle the response from FetchAddressIntentService.

The result includes a numeric result code (resultCode) as well as a message containing the result data (resultData). If the reverse geocoding process is successful, the resultData contains the address. In the case of a failure, the resultData contains text describing the reason for the failure. For details of the possible errors, see Return the address to the requestor.

Override the onReceiveResult() method to handle the results that are delivered to the result receiver, as shown in the following code sample:

public class MainActivity extends AppCompatActivity {

    // ...

    class AddressResultReceiver extends ResultReceiver {
        public AddressResultReceiver(Handler handler) {

        protected void onReceiveResult(int resultCode, Bundle resultData) {

            // Display the address string
            // or an error message sent from the intent service.
            mAddressOutput = resultData.getString(Constants.RESULT_DATA_KEY);

            // Show a toast message if an address was found.
            if (resultCode == Constants.SUCCESS_RESULT) {

This site uses cookies to store your preferences for site-specific language and display options.

Get the latest Android developer news and tips that will help you find success on Google Play.

* Required Fields


Sigue a Google Developers en WeChat

Browse this site in ?

You requested a page in , but your language preference for this site is .

Would you like to change your language preference and browse this site in ? If you want to change your language preference later, use the language menu at the bottom of each page.

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a short survey?
Help us improve the Android developer experience. (Dec 2017 Android Platform & Tools Survey)