Thanks for sharing, I was about to test your solution however when I opened my app the issue seems to be resolved … I can now see multiple locations at the correct zoom level on my map.
1 Like
Murphies law, go figure! 
Does it work on a mobile device, though?
This map should show location in CA and GA but it defaults to SF
That’s really weird. With me it’s working perfectly on my mobile device now. I didn’t change anything apart from republishing my template and app.
Are you using Pages or Apps?
Yeah. Echoing Robert’s question here. This isn’t fixed in a clients project of mine, and I’m getting same behavior as Robert’s screenshot above.
Same behavior as well 
(app still on this one)
@Ivo_Elbert says he’s working on a fix! Hopefully by next week 
3 Likes
I think this is solved by using a Relation Column as the source. Here is the Relation as source. (the top map)
Here is the Table as Source (the bottom map). Would be nice if it wasn’t so temperamental, the mobile version is simple (but this version is better in most other ways)
One extra feature would be nice - ability to set the zoom distance.
So just to be clear, the workaround is to use the Relation column as the source.
Pages
Just played around on this. Thanks for getting multi-location pins working on page maps. It’s working here. Can do a lot with this.
Also working: On open, snap-zoom level to show all pin locations within view. Both pan AND the zoom function are correct. Working as it should.
Couple requests while you’re working on maps:
*Pin Grouping
*Full(ish) screen map size for mobile. The “square” is too small.
*Results counter
Love the built in “searchbar” function for map. Excellent work. This is the kind of built-in component functionality I’ve been whining about for a year. KEEP THIS UP GLIDE!! PS this is for pages, I didn’t test apps.