[Plugin: Developer's Custom Fields] Geodata

I might look into this. However, it looks as though this standard is as much to do with the meta keys as anything else. So there’s the geodata for a post, and that’s it. This would take away a little flexibility – I could imagine some situations where you’d want to store more than one location for some post types.

Also, if the key for latitude has to be geo_latitude, that would mean not using the global key prefix that the plugin uses. I’m not sure of the impacts there. At the very least, forcing gmap fields to use these keys may break existing sites using the plugin.