Hey Paul! It looks like that field type isn’t currently supported, but that’s an interesting idea. It seems that using that ACF field requires registering an API key, so that might complicate the implementation of this a bit, but I’ve also heard users requesting a map integration on the front end so I can imagine that combining the ACF Google Map field with some map integration would be pretty valuable. I’ll add it as a feature request for the devs to scope out and we’ll follow up here if/when this is something we’re able to add.
Out of curiosity, other than having a list of possible fields for the ACF map field in the L&L docs, what kind of functionality are you currently missing from your currently-functioning syntax? And what additional benefit would you hope to get out of that second syntax you’re suggesting?