# Map Pins display at incorrect locations

**URL:** <https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286>\
**Category:** Ask for Help\
**Created:** [October 19, 2021, 2:07pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286 "2021-10-19T14:07:01Z")\
**Posts on this page:** 14\
**Page:** 2

<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:** [October 19, 2021, 3:26pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/21 "2021-10-19T15:26:29Z")

</div>

Yes, because then you allow the user to enter/edit the address as parts, and the map works – you get both of the things you want, not just one.

---

<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:** [October 19, 2021, 3:26pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/22 "2021-10-19T15:26:36Z")

</div>

> [@JC23](#):
>
> Do you consider the template column to be a better way to go over the single-cell addresses?

It should be identical…I prefer that method because then users will enter addresses in a more standardized way. That, and you can include choice components for state selection to avoid some users entering “VA” and other entering “Virginia”

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [October 19, 2021, 3:38pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/23 "2021-10-19T15:38:33Z")

</div>

I have found the most accurate method is to geocode ordinary addresses into co-ordinates. This can be done is Google Sheets with the Geocode from Awesome Tables add-on.

It will look up the addresses and output 2 columns: lon and lat. Then we simply concatenate the values of both columns into one column (with the lon & lat values separated by a comma). This the column we use to generate the map.

---

<div class="post-metadata">

**Author:** ![mwza](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mwza/32/43529_2.png) [@mwza](https://community.glideapps.com/u/mwza)\
**Post date:** [October 28, 2021, 4:50pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/24 "2021-10-28T16:50:26Z")

</div>

I was testing location component on an add form and noticed that my pin is significantly misplaced when testing the app in developer mode in chrome browser on mac compared to using the published app on ios which gave an accurate pin location.

Is this to be expected? And if so, briefly why?

Appreciate any feedback

---

<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:** [October 28, 2021, 4:55pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/25 "2021-10-28T16:55:22Z")

</div>

Depends. Does your Mac have a GPS? Are location services enabled on the browser and your Mac? The location component is going to get as close as it can. My laptop gets within a mile of my actual location. It does not have a built in gps. At best it’s probably getting your location based on your IP and ISP. Works fine on my phone, but obviously my phone has a built in gps and location permissions are enabled to pinpoint my precise location instead of a general location.

---

<div class="post-metadata">

**Author:** ![mwza](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mwza/32/43529_2.png) [@mwza](https://community.glideapps.com/u/mwza)\
**Post date:** [October 29, 2021, 3:02pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/26 "2021-10-29T15:02:52Z")

</div>

Makes sense - thank you @Jeff_Hager - I now understand why phone is better - they were both.(phone and mac) working on same wifi network so assuming phone’s gps rendered more accurate result.

---

<div class="post-metadata">

**Author:** ![Chris\_Robinson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/chris_robinson/32/35488_2.png) [@Chris\_Robinson](https://community.glideapps.com/u/Chris_Robinson)\
**Post date:** [August 19, 2022, 5:10am UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/27 "2022-08-19T05:10:01Z")

</div>

I am having the same problem.

I have two sets of lat, long data from 2 images. The data represents photos that were taken just a couple of feet from each other, and both in a park in Sunnyvale, California. I have (37.381945, -122.025369) and (37.381973, -122.025377). If I plug these numbers into Google maps they are right where they should be, but in the Glide app I am seeing 1 pin in Washington state, and 1 pin in Pakistan. ☹

---

<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:** [August 19, 2022, 11:53am UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/28 "2022-08-19T11:53:34Z")

</div>

I would double check that you entered the coordinates correctly in your table, and that the map address setting is looking at the correct column in the table. Can you share some screenshots of your table and the mall settings?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 20, 2022, 12:06am UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/29 "2022-08-20T00:06:36Z")

</div>

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/b/9b67cdced0a3579de899953cc265337c563d940f.png)

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/2/d28549f8b57317d62456bbf9df0bffd4a6b99573.jpeg)

Looks to be correct for me.

---

<div class="post-metadata">

**Author:** ![Chris\_Robinson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/chris_robinson/32/35488_2.png) [@Chris\_Robinson](https://community.glideapps.com/u/Chris_Robinson)\
**Post date:** [August 23, 2022, 6:17pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/30 "2022-08-23T18:17:30Z")

</div>

Thank you for the help everyone. I was mishandling the location data for the maps in the general settings. Fixed and easy peasy.

The comments help me understand what a good community there is here, which keeps me going through these inane errors I am making. Thank you everyone.

---

<div class="post-metadata">

**Author:** ![Chris\_Robinson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/chris_robinson/32/35488_2.png) [@Chris\_Robinson](https://community.glideapps.com/u/Chris_Robinson)\
**Post date:** [August 23, 2022, 6:19pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/31 "2022-08-23T18:19:12Z")

</div>

Thanks Jeff, I had the data correctly entered, but was pointing the address to the wrong cell in the table. End of day error that could have been fixed with a few more hours of sleep or another coffee.

---

<div class="post-metadata">

**Author:** ![Chris\_Robinson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/chris_robinson/32/35488_2.png) [@Chris\_Robinson](https://community.glideapps.com/u/Chris_Robinson)\
**Post date:** [August 23, 2022, 6:19pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/32 "2022-08-23T18:19:49Z")

</div>

Thanks for checking. It was a settings error on my part.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 24, 2022, 1:56am UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/33 "2022-08-24T01:56:47Z")

</div>

No worries, feel free to let us know if you face any further problems!

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [January 17, 2024, 4:49pm UTC](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286/34 "2024-01-17T16:49:24Z")

</div>

Closed on January 17, 2024, 4:49pm UTC



[Previous page](https://community.glideapps.com/t/map-pins-display-at-incorrect-locations/33286.md?page=1)
