The
latest update I can see from the docs is the release of '
google.type.LatLng'. LatLng is being maintained by engineering in the
google-cloud repository. LatLng looks to be the newer
GeoPt since it correctly uses Doubles (instead of
Floats like in GeoPt) to store Lat and Lng. For more information about the implementation of LatLng you can follow their
Git repository.
- A workaround alternative would be to use the Search API (which is a separate variation of the Datastore, instead of 'entities' it uses 'documents'). The Search API has a
GeoPoint search ability on
saved documents.