It's my understanding that API keys are allowed for static Google Maps displayed with this module. Allowing API keys for dynamic embedded maps as well would be a big help moving forward, and may not be that complicated to implement.
For reference, there are two ways to use the new Google Maps embedding. If you search a location, and use the "Share or embed map" option, you are given a URL in the semi-colon format that is difficult to understand. While there has been some reverse engineering (see https://andrewwhitby.com/2014/09/09/google-maps-new-embed-format/ for example) it is not fully understood. This method, as we know, does not require an API key.
The other, and proper way Google would like you to do this is using an API key. I know there's a bit of controversy around this and the billing/credit card requirement, but by all accounts, this is the way Google has been and likely will continue to push. (Given their recent change to prohibit embedding through maps.google.com URLs, they are making non-key methods more difficult to use.) When it comes to implementing map embedding only, the API is free up to 500 requests per second currently with no daily limit. That should cover most use cases for free. This comes with a URL style that is familiar, and properly documented: https://developers.google.com/maps/documentation/embed/embedding-map
The API key URL should be easy to implement. The URL options are very similar, however you would need to expose the API key option for all map types (not just static as it currently is). Here is an example of the API key URL style with sensible URL parameters:
https://www.google.com/maps/embed/v1/place?key=<YOUR_API_KEY>&q=<NAME_OF_PLACE>¢er=<MAP_COORDS_COMMA_SEPARATED>&zoom=<0-21>
Currently, Simple Google Maps 3.0.0 is entirely broken for embedding dynamic maps. Implementing Issue (3092918) Patch #24 by committing it to dev and tagging a new release will fix this for the time being. Having said that, if the API key URL option is enabled for embedded dynamic maps in this module, it would allow us to use a www.google.com URL via the API, instead of the hard-coded maps.google.com URL for the semi-colon format, which is now broken. Adding this feature would add both a helpful fix to the module and make it more future proof and convenient.
Active
4.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.