I followed another posts’ advice and saved the address to db…as I understand it, you pay for the API call…not the map use itself so you only have the cost once…I absolutely stand to be corrected on that
@boston85719 This part is easy with a Group to Image or Element to Image plugin.
Just thinking out loud here:
Step 1: Input address. This will populate the map using the normal Google API setup.
Step 2: Click Next. When user clicks ‘Next,’ have a workflow to capture an image of that map element using a plugin like this and save it under the user as MapImage. You can do this everytime the user changes their address.
This way, the map won’t load everytime a user visits the page. It will only load on the screen where the user will make changes to the address, which won’t be a normal occurrence.
I haven’t tried it myself but thought it could be worth a shot.
Test it and see. Look at your google console, pull up the page and keep refreshing the page with the map and see if it counts toward an API usage or not each time the map is loaded and the address is loaded into the map.
Yeah, Google Maps are Expensive to show…I use Leafy Maps Free Plugin to use other map providers like Mapbox or Stadia to have cheaper map views…can save thousands a month compared to Google if your app gains traction.
You are right, just tested and the image of the map doesn’t come out right. Best bet would be to create your own plugin to solve the problem. I’m no expert but I’m guessing it could be done fairly quickly with a simple JS library
I’m still hoping to use the HTML element to use the Maps Static API as I believe that is supposed to show the static map, and only pay for the creation of it, and not the display of it.
Plus, I can’t build a plugin for it, and doubt others can either since no existing plugin for element to image work with maps or graphs. I’ve reached out to some of the developers of those plugins to request the feature but none have been able to add it.