# Incorrect Map Coordinates on lookup

**URL:** <https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854>\
**Category:** Ask for Help\
**Created:** [November 10, 2019, 1:58pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854 "2019-11-10T13:58:32Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/paul/32/1345_2.png) [@Paul](https://community.glideapps.com/u/Paul)\
**Post date:** [November 10, 2019, 1:58pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/1 "2019-11-10T13:58:32Z")

</div>

So for a free app I’m playing around with I’ve hit the address based lookup limit of 10. So I’m busily converting my 20 odd entries to coordinates based - as per [here](https://docs.glideapps.com/all/reference/layouts/map-list#troubleshooting-misplaced-pins).

It’s not accurate though, all coordinates are a little off after I read them from the URL as the docs suggest and add them into my app. There is some kind of translation happening that changes the coordinate a little - rendering it inaccurate.

Here is an example / my process.

1. Look up ‘All Day Donuts / 12 Edward St, Brunswick VIC 3056’
2. Google URL = [link](https://www.google.com/maps/place/All+Day+Donuts/@-37.7741777,144.959513,17z/data=!3m1!4b1!4m13!1m7!3m6!1s0x6ad6434aae344a81:0xf911a68b20458097!2s12+Edward+St,+Brunswick+VIC+3056!3b1!8m2!3d-37.7741686!4d144.9616568!3m4!1s0x6ad6434ab0db47a7:0x87311ef37d227348!8m2!3d-37.774182!4d144.9617017)
3. Coordinates following the URL details noted in the docs should be **-37.7741777,144.959513**

Viewing in app…

App: [https://mellowyellow.glideapp.io/](https://mellowyellow.glideapp.io/)

Go to the second tab (Eating & Drinking) and All Day Donuts should be up the top, I’ve used the  
coordinates field for a basic text field and map directly below it. I can see the visual map representation is incorrect and when you click through it is incorrect too.

It’s nearly 1am here so I’m probably missing something supremely obvious… appreciate any thoughts.

---

<div class="post-metadata">

**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\
**Post date:** [November 10, 2019, 2:30pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/2 "2019-11-10T14:30:46Z")

</div>

When I look up that location manually and then share a link to it (done through Google Maps on my phone), the url that gets shared gives me the following coordinates:

-37.774182,144.9617017

Slightly different than yours, not sure why.

---

<div class="post-metadata">

**Author:** ![Francois1](https://avatars.discourse-cdn.com/v4/letter/f/c67d28/32.png) [@Francois1](https://community.glideapps.com/u/Francois1)\
**Post date:** [November 10, 2019, 2:34pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/3 "2019-11-10T14:34:30Z")

</div>

I have exactly the same issue… 🙁

---

<div class="post-metadata">

**Author:** ![thebepps](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thebepps/32/2956_2.png) [@thebepps](https://community.glideapps.com/u/thebepps)\
**Post date:** [November 10, 2019, 3:12pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/4 "2019-11-10T15:12:44Z")

</div>

@Paul you are using a different part of the link then @kyleheney @Francois1 look at the bold part of the link below.

[https://www.google.com/maps/place/All+Day+Donuts/@](https://www.google.com/maps/place/All+Day+Donuts/@) **-37.774182,144.959513** ,17z/data=!3m1!4b1!4m13!1m7!3m6!1s0x6ad6434aae344a81:0xf911a68b20458097!2s12+Edward+St,+Brunswick+VIC+3056,+Australia!3b1!8m2!3d-37.7741686!4d144.9616568!3m4!1s0x6ad6434ab0db47a7:0x87311ef37d227348!8m2!3 **d-37.774182!4d144.9617017**

---

<div class="post-metadata">

**Author:** ![thebepps](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thebepps/32/2956_2.png) [@thebepps](https://community.glideapps.com/u/thebepps)\
**Post date:** [November 10, 2019, 3:31pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/5 "2019-11-10T15:31:59Z")

</div>

I suggest to find coordinates on OpenStreetMap, I think Mapbox uses the same source.

---

<div class="post-metadata">

**Author:** ![Francois1](https://avatars.discourse-cdn.com/v4/letter/f/c67d28/32.png) [@Francois1](https://community.glideapps.com/u/Francois1)\
**Post date:** [November 10, 2019, 3:46pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/6 "2019-11-10T15:46:36Z")

</div>

Thanks @thebepps!

It means that the GIF [here](https://docs.glideapps.com/all/reference/layouts/map-list#troubleshooting-misplaced-pins) is not true.

We should take the coordinates at the end of the URL.

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\
**Post date:** [November 10, 2019, 4:17pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/7 "2019-11-10T16:17:56Z")

</div>

Interesting! We can improve this.

---

<div class="post-metadata">

**Author:** ![Paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/paul/32/1345_2.png) [@Paul](https://community.glideapps.com/u/Paul)\
**Post date:** [November 11, 2019, 12:52am UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/8 "2019-11-11T00:52:50Z")

</div>

Ahhh thx team! Ok so to take the correct coordinates in that link you need to use the **end** coordinates, replace the ‘!4d’ with a ‘,’ and it works. 👍

1. [https://www.google.com/maps/place/All+Day+Donuts/@-37.774182,144.959513,17z/data=!3m1!4b1!4m13!1m7!3m6!1s0x6ad6434aae344a81:0xf911a68b20458097!2s12+Edward+St,+Brunswick+VIC+3056,+Australia!3b1!8m2!3d-37.7741686!4d144.9616568!3m4!1s0x6ad6434ab0db47a7:0x87311ef37d227348!8m2!3](https://www.google.com/maps/place/All+Day+Donuts/@-37.774182,144.959513,17z/data=!3m1!4b1!4m13!1m7!3m6!1s0x6ad6434aae344a81:0xf911a68b20458097!2s12+Edward+St,+Brunswick+VIC+3056,+Australia!3b1!8m2!3d-37.7741686!4d144.9616568!3m4!1s0x6ad6434ab0db47a7:0x87311ef37d227348!8m2!3) **d-37.774182!4d144.9617017**
2. -37.774182!4d144.9617017 = **-37.774182,144.9617017**
3. -37.774182,144.9617017 searches to [link](https://www.google.com/maps/place/37%C2%B046'27.1%22S+144%C2%B057'42.1%22E/@-37.7741777,144.959513,17z/data=!3m1!4b1!4m5!3m4!1s0x0:0x0!8m2!3d-37.774182!4d144.9617017). ✔

Looks good!

If @david can improve on this, or maybe provide some =IMPORTHTML calcs magic that’d make life easier for most. 👍👍

---

<div class="post-metadata">

**Author:** ![Paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/paul/32/1345_2.png) [@Paul](https://community.glideapps.com/u/Paul)\
**Post date:** [November 11, 2019, 1:00am UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/9 "2019-11-11T01:00:32Z")

</div>

This looks interesting. I’ll test a little.

[https://willgeary.github.io/data/2016/11/04/Geocoding-with-Google-Sheets.html](https://willgeary.github.io/data/2016/11/04/Geocoding-with-Google-Sheets.html)

---

<div class="post-metadata">

**Author:** ![Paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/paul/32/1345_2.png) [@Paul](https://community.glideapps.com/u/Paul)\
**Post date:** [November 11, 2019, 2:28am UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/10 "2019-11-11T02:28:29Z")

</div>

As a note it seems that I’m still running into the map limit reached notes on my free apps (not the one in the example above as I’ve gone Pro there) using coordinates instead address lookups.

As a workaround I’ve gone columns view (not bad) for my respective tabs, just means the map rendering isn’t being done until someone clicks into a specific property. Not the end of the world.

Still if the Maps list / view option using coordinates instead of addresses (to avoid lookup quotas etc) was a doable that’d be great.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [November 11, 2019, 11:22pm UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/11 "2019-11-11T23:22:32Z")

</div>

I ran into the limit in one of my apps. I switch to coordinates, but I still had the warning message. If I recall, I just had to refresh the page or the component or something like that. Once I did that, the warning message went away and I could have more than 10 points using coordinates.

---

<div class="post-metadata">

**Author:** ![Paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/paul/32/1345_2.png) [@Paul](https://community.glideapps.com/u/Paul)\
**Post date:** [November 12, 2019, 12:29am UTC](https://community.glideapps.com/t/incorrect-map-coordinates-on-lookup/1854/12 "2019-11-12T00:29:16Z")

</div>

I’ve certainly refreshed the spreadsheet and pages… I’ll remove and re-add the component and double check. 👍
