geocoding via google incurs massive charges if polling frequently

I have ~60 devices in observium. 

I've created DNS LOC records for most of the devices..

I'll be ensuring that they exist for all devices shortly.. Regardless.

It doesn't seem like there's any caching going on wrt geolocation...

This is likely increasing latency, but if nothing else, it's contributing to needless traffic. 

In my environment, observium has incurred >$300/mo in api fees from using google's geocoding API.

granted, I'm polling more often than every 5m, but I don't feel like that should matter given the relatively small number of hosts observium's looking at.

Shouldn't a location only be geolocated again if its' reported location changes?

(am I just dull and I'm missing a 'yes, cache geolocation records' config entry or something?)