Forum | Appery.io

I am not sure if this is the actual case but if I understood the structure of the tutorial correctly there is a little bit of bad habits in it.
Because all the addresses from the database are being passed through the geocoder service every time the app is loaded you can easily find yourself hitting your quota, (please read google API for more information on limits. Also on larger databases you will find that google will limit the amount of geocodes that can be done at one time.
Further because your map data is being populated through the service you find that Marker titles and info windows are a real pain to program in.
I solve this issue by setting my geocoder to fire on change value event in the address field then save the data back into the database then populate the map from the database itself.
The easiest way to do this is create hidden labels linked to the geocoder and to the database then as I said set the GC to fire when the value is changed in the address field. When the user clicks save or update your GEO information gets saved to.
How about folks I know you have some of your own tricks up your sleeve????

Hello! It's better to use variables from localStorage instead hidden labels.

Maryna
Thanks I had it in my mind this would load up the local storage but now I think about it I realize your right.