# Add reverse geocoding - method to convert a geographic location to an address in real time

**URL:** <https://forum.getodk.org/t/add-reverse-geocoding-method-to-convert-a-geographic-location-to-an-address-in-real-time/14710>\
**Category:** Ideas\
**Tags:** geo\
**Created:** [August 23, 2018, 1:23pm UTC](https://forum.getodk.org/t/add-reverse-geocoding-method-to-convert-a-geographic-location-to-an-address-in-real-time/14710 "2018-08-23T13:23:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander\_Torrado](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/alexander_torrado/32/2720_2.png) [@Alexander\_Torrado](https://forum.getodk.org/u/Alexander_Torrado)\
**Post date:** [August 23, 2018, 1:23pm UTC](https://forum.getodk.org/t/add-reverse-geocoding-method-to-convert-a-geographic-location-to-an-address-in-real-time/14710/1 "2018-08-23T13:23:26Z")

</div>

**What is the general goal of the feature?**  
Provide an easy way to get known and standarized address from latitude and longitude data that can be input as data in forms

**What are some example use cases for this feature?**  
Collecting data from known places

**What can you contribute to making this feature a reality?**

Android documentation is [here](https://developer.android.com/reference/android/location/Geocoder#getFromLocation(double,%20double,%20int))

getFromLocation  
added in API level 1  
public List getFromLocation (double latitude,  
double longitude,  
int maxResults)  
Returns an array of Addresses that are known to describe the area immediately surrounding the given latitude and longitude. The returned addresses will be localized for the locale provided to this class's constructor.

The returned values may be obtained by means of a network lookup. The results are a best guess and are not guaranteed to be meaningful or correct. It may be useful to call this method from a thread separate from your primary UI thread.

Parameters  
latitude double: the latitude a point for the search  
longitude double: the longitude a point for the search  
maxResults int: max number of addresses to return. Smaller numbers (1 to 5) are recommended

---

<div class="post-metadata">

**Author:** ![yanokwa](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/yanokwa/32/1695_2.png) [@yanokwa](https://forum.getodk.org/u/yanokwa)\
**Post date:** [August 24, 2018, 3:36pm UTC](https://forum.getodk.org/t/add-reverse-geocoding-method-to-convert-a-geographic-location-to-an-address-in-real-time/14710/2 "2018-08-24T15:36:53Z")

</div>

Hi @Alexander_Torrado, is there a reason why this geocoding needs to be done in the form and not on the server or in the reporting stage? Why does the enumerator need to see an address?

---

<div class="post-metadata">

**Author:** ![Alexander\_Torrado](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/alexander_torrado/32/2720_2.png) [@Alexander\_Torrado](https://forum.getodk.org/u/Alexander_Torrado)\
**Post date:** [August 24, 2018, 4:04pm UTC](https://forum.getodk.org/t/add-reverse-geocoding-method-to-convert-a-geographic-location-to-an-address-in-real-time/14710/3 "2018-08-24T16:04:30Z")

</div>

Because the return addresses are a list of best guess ("The results are a best guess and are not guaranteed to be meaningful or correct") there could be a chance that enumerator confirms an address as "recognized".
