{"id":10736200,"date":"2018-09-29T23:06:37","date_gmt":"2018-09-29T23:06:37","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/caching-geocodes\/"},"modified":"2018-09-29T23:06:37","modified_gmt":"2018-09-29T23:06:37","slug":"caching-geocodes","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/caching-geocodes\/","title":{"rendered":"Caching Geocodes?"},"content":{"rendered":"<p>I have a question about the way The Events Calendar utilizes the Google Maps API.  <\/p>\n<p>I could be wrong, but it looks like you are doing a Geocode request every time a page with an embedded map is displayed. <\/p>\n<p>Since Google is now charging per Geocode API call (admittedly, not a lot\u2026 but still), it seems like it would be more economical for your customers if you did a single geocode request when the venue is created, you could cache that information so that longitude and latitude information aren&#8217;t requested redundantly.<\/p>\n<p>Make sense? <\/p>\n","protected":false},"template":"","class_list":["post-10736200","topic","type-topic","status-publish","hentry","topic-tag-events","topic-tag-geocoding"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/10736200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/10736200\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=10736200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}