[phsource]

I have to say, being able to add all the places to a list accessible from Google Maps is really key since it's one of my main tools while on a trip. I'm curious though -- what got you to choose exporting to Google My Maps vs. a Google Maps saved places place list?

For Wanderlog (https://wanderlog.com), we ended up exporting to Saved Places instead of Google My Maps. My Maps lets you do advanced things like create regions and polygons, but when using it on the Google Maps app, it seems strictly worse:

1. You have to explicitly turn on the My Maps layer, rather than the pins always showing, for it to show up on the app, and

2. When you tap on one of the My Maps pins, it doesn't show the underlying place's associated details (e.g., rating, etc.) which makes it a bit harder to go back to the source of the info.

It's definitely nicer to build on top of Saved Places, which also seems more actively maintained by Google. Did you have any reason in mind to use My Maps rather than the Saved Places?

[adl1995]

I do use Saved Places but only for storing bus terminals, Airbnbs addresses, etc. Google My Maps has the advantage of grouping places by a column (e.g. rating, reviews) and modifying icons based on the place type (which I frequently use). It also doesn't clutter the maps with landmarks (they only show up when the map is selected).

1. For me all layers are enabled by default when I load a map on the Maps application

2. I agree that this is quite annoying. The workaround I found was to add the missing information in the CSV file which then shows up in My Maps

Having said that, there are still tons of features missing from My Maps, e.g. each layer can have a limited number of places and there's no API to import the CSV file programmatically. There's a pretty hectic list of feature requests here: https://issuetracker.google.com/issues?q=google%20my%20maps%...