Thanks, @NigelG. To be fair, though, @keith said pretty much the same thing in his initial reply to my query - albeit much more succinctly (which is a bit out of character for keith 
).
However, I did encounter a bug when attempting to publish a geo addr as an exposed state and then save it directly to the DB. That would generate a ācannot dehydrate a functionā error in the browser console.
Additionally, trying to save a value from a non-exposed state context that would normally be converted into a geo addr would not work. The DB field would simply be empty. I had to put the value (in this case, a string comprised of lat/lng separated by a comma) into an input field and then save the inputās value to the DB. Itās as though the automatic reverse geocoding was not working in that case. Instead, it had to go through a UI element to āforceā the conversion.
Ah well, hopefully, most of my geo-follies are behind me. 