Request: Google Calendar event data sources, the driver now fetches both the Basic and the FUll and uses the Where: information from the Basic summary to get an address, then geocodes this using Bing and the existing API key (per the admiun UI Settings tab)  Not wholly okay with this, as the driver now requires intimate knowledge of the calling context (siteconfig) to determine whether there's a Bing API key...
Expanding upon prior commit, the geocoding process for Google Calendar driver will now 'cache' the lat/l;ng pairs for a given address. in situations where events happen at the same location, this means fewer geocodes