Example of using GeoPt

I can't figure out how to use GeoPt... is there an example I can look at?
https://cloud.google.com/appengine/docs/java/datastore/geosearch

@stephenplusplus

I think GeoPt is a client-side creation with a special "meaning" attached and not explicitly exposed via the JSON API.

See googleapis/google-cloud-python#1065 (comment) for more info.

The meaning field in the protobufs is not super well defined.

@stephenplusplus : Is there anywhere we use meaning=9 ?

@pcostell : Is there any chance we're making "meaning" a first-class citizen on the API for the next versions of the Cloud Datastore API?

@Alfus

No we should not expose GeoPt using meaning. V1beta3 will have a separate
geopoint value that can be used.

We intentionally do not document meaning and you should not rely on it. We
make no guarantees about what the values actually refer to and may change,
remove, or add values in the future.

/cc @Alfus

On Sat, Nov 28, 2015, 3:05 PM JJ Geewax [email protected] wrote:

I think GeoPt is client-side creation with a special "meaning" attached
and not explicitly exposed via the JSON API.

See googleapis/google-cloud-python#1065 (comment)
googleapis/google-cloud-python#1065 (comment)
for more info.

The meaning field in the protobufs is not super well defined.

@stephenplusplus https://github.com/stephenplusplus : Is there anywhere
we use meaning=9 ?

@pcostell https://github.com/pcostell : Is there any chance we're
making "meaning" a first-class citizen on the API for the next versions of
the Cloud Datastore API?

—
Reply to this email directly or view it on GitHub
#972 (comment)
.

@Alfus

ok -- great, how can I find out when V1Beta3 is out so I can give it a try

..brad

On Sat, Nov 28, 2015 at 8:58 PM, Patrick Costello [email protected]
wrote:

No we should not expose GeoPt using meaning. V1beta3 will have a separate
geopoint value that can be used.

We intentionally do not document meaning and you should not rely on it. We
make no guarantees about what the values actually refer to and may change,
remove, or add values in the future.

/cc @Alfus

On Sat, Nov 28, 2015, 3:05 PM JJ Geewax [email protected] wrote:

I think GeoPt is client-side creation with a special "meaning" attached
and not explicitly exposed via the JSON API.

See googleapis/google-cloud-python#1065 (comment)
<
googleapis/google-cloud-python#1065 (comment)

for more info.

The meaning field in the protobufs is not super well defined.

@stephenplusplus https://github.com/stephenplusplus : Is there
anywhere
we use meaning=9 ?

@pcostell https://github.com/pcostell : Is there any chance we're
making "meaning" a first-class citizen on the API for the next versions
of
the Cloud Datastore API?

—
Reply to this email directly or view it on GitHub
<
#972 (comment)

.

—
Reply to this email directly or view it on GitHub
#972 (comment)
.

Hi Brad --
We are working on it now. Part of our new version is a completely new serving stack to make Cloud Datastore more reliable and have lower latencies. As a gcloud-node user you shouldn't have to worry about the new Datastore version -- gcloud will upgrade to the new version and you shouldn't see much change (except for a new minor version that includes GeoPt support).

The v1beta3 release will not include geosearch support (which is still in Alpha in App Engine). We are making sure we iron out the usage of geosearch in GAE first.

-Patrick

Using geo point values will be shown in our docs once v1beta3 is released. Until then, it sounds like we don't plan to support them, so I'm going to close the issue. Thanks for getting this conversation started!

when is v1beta3?

On Fri, Dec 4, 2015 at 8:54 AM, Stephen Sawchuk [email protected]
wrote:

Closed #972
#972.

—
Reply to this email directly or view it on GitHub
#972 (comment)
.

Brad --

As I mentioned above we are working on it now. I'm hoping we'll be able to launch soon but I'm not able to give a more definite timeline.

-Patrick

ok -- I guess I just check back in a few weeks or months?

On Fri, Dec 4, 2015 at 1:41 PM, Patrick Costello [email protected]
wrote:

Brad --

As I mentioned above we are working on it now. I'm hoping we'll be able to
launch soon but I'm not able to give a more definite timeline.

-Patrick

—
Reply to this email directly or view it on GitHub
#972 (comment)
.