# More relevant autocomplete address results

**URL:** <https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781>\
**Category:** Ask for Help\
**Tags:** api, call-api\
**Created:** [November 14, 2023, 6:53am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781 "2023-11-14T06:53:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![james](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/james/32/71213_2.png) [@james](https://community.glideapps.com/u/james)\
**Post date:** [November 14, 2023, 6:53am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/1 "2023-11-14T06:53:48Z")

</div>

I am implementing an address autocomplete using a similar approach to Bob’s hybrid form in the link below.

> [@Radar Address Complete in Form](https://community.glideapps.com/t/radar-address-complete-in-form/63658/6):
>
> What I’ve been doing lately is to use what I’m calling “hybrid” forms: show new screen action instead of form screen add an input component for any input you want to validate against another table (using relations, etc) add a form container beneath the input for the remainder of the form, but only display the form container if the input outside of the form container is “valid”. This way you still have a form experience with less updates but can still leverage the custom form experience for th…

It all works well, but I am finding the results often lean towards the USA. If I am specific enough with the address then it works fine, but for cases where we are searching a place, it nearly always returns somewhere in the USA, instead of Western Australia where we are based.

I’m guessing this is to do with the “Near” portion of the API on Glide’s end. If this is the case, I would love for this to be customisable in the Radar integration settings or on the action/column. [Documentation - API Reference | Radar](https://radar.com/documentation/api#autocomplete)

 ![Capture](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/b/7bae03178f01f17559647378d1319b133810b7ca.png)

Does anyone have advice on how I can retrieve more relevant results, or insight into how the integration might be working?

---

<div class="post-metadata">

**Author:** ![james](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/james/32/71213_2.png) [@james](https://community.glideapps.com/u/james)\
**Post date:** [November 14, 2023, 10:46am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/2 "2023-11-14T10:46:23Z")

</div>

The Google Maps integration seems to be returning better results. Will use this instead 🙂

---

<div class="post-metadata">

**Author:** ![james](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/james/32/71213_2.png) [@james](https://community.glideapps.com/u/james)\
**Post date:** [November 15, 2023, 1:29am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/3 "2023-11-15T01:29:31Z")

</div>

Referring to the address autocomplete magic as shown by @Robert_Petitto, is that still the best way to go about it with all the new features, e.g. integrations? As far as I can tell, there’s no way to do this using any of the new integrations.

> [@Address Autocomplete API](https://community.glideapps.com/t/address-autocomplete-api/39602/8):
>
> Tutorial: [[Glide: Address Autocomplete] ](https://www.youtube.com/watch?v=4a8t7fRhdo4)

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [November 15, 2023, 2:57am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/4 "2023-11-15T02:57:53Z")

</div>

Ya. From what I’ve seen, the integrations only return a single address…so if you want a list of addresses to pick from, you’ll need to call the API using the Call API column (only available for Business users now).

---

<div class="post-metadata">

**Author:** ![james](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/james/32/71213_2.png) [@james](https://community.glideapps.com/u/james)\
**Post date:** [November 15, 2023, 5:33am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/5 "2023-11-15T05:33:56Z")

</div>

Awesome. I have set up Geoapify with the Call API column, extracted the JSON using a combo of QueryJSON, Joined List, Split Text and Template columns in my helper table.

* * *

Also, in the Call API column I was able to add query parameters for the Geoapify API for “filter” and “bias” so that:

- Addresses returned are filtered to only include those from Australia
- Results are biased (sorted) based on proximity to our local area

The filter/bias parameters would be handy in the Google Maps and Radar integrations when completing partial addresses.

> **[Address Autocomplete API | Developer Documentation | Geoapify](https://apidocs.geoapify.com/docs/geocoding/address-autocomplete/#autocomplete)**
>
> The documentation contains Address Autocomplete API reference and code samples. Learn more about Address Autocomplete API inputs and data structure.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [November 15, 2023, 9:33am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/6 "2023-11-15T09:33:58Z")

</div>

> [@james](#):
>
> - Addresses returned are filtered to only include those from Australia
> - Results are biased (sorted) based on proximity to our local area

Nice!  
I need something very similar for an App I’m working on now. Will definitely take a look at Geoapify.

---

<div class="post-metadata">

**Author:** ![james](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/james/32/71213_2.png) [@james](https://community.glideapps.com/u/james)\
**Post date:** [November 15, 2023, 9:57am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/7 "2023-11-15T09:57:14Z")

</div>

This is the gist of the UI, where step 1 is a custom form on a helper table and step 2 is a form container. Behind the scenes, the flow is very similar to what Bob does.

 ![1](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/9/e9f1ffc4a21a66ff966680e127338f6016095f86.png)  
 ![2](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/1/51bb9bf55261917182d9063f027eea9dede39e47.png)  
 ![3](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/a/5/a58c84a336910018636767d3b446728c10567946.png)

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [November 22, 2023, 9:57am UTC](https://community.glideapps.com/t/more-relevant-autocomplete-address-results/67781/8 "2023-11-22T09:57:27Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
