Popular posts

See an answer on the "missing functionality for GeoPoint" Firestore issue:

For those arriving here, I wouldn't hold your breath. I've been waiting for Geo Queries on Cloud Datastore (which Firestore is pretty much just a new iteration of) for over 5 years now. There are much better geo-native solutions out there if you want to get it done. Anything geo built on top of Firestore / Datastore is a hack at best, and from what I've seen vastly under-performs just picking the right tool the first time.

I really wish Google Cloud would give us a nice native option for this though - I mean they certainly do have the tech for it (Google Maps etc.) but they clearly aren't open to sharing that just yet...

Really sucks to see that Google isn't doing anything for that in 6 years..

We've answered this in a few other comments (geo queries are popular, who knew?!?) but it's worth answering again.

With Firestore one of the core principles is that query speed depends on the number of results, not the size of the data set. Doing geo queries which are both accurate and fast is really, really hard and we have not yet invested in that. There are some tricks you can do with geohashes though and we're working on getting out some better documentation about that.

Samuel Stern I see. My specific use-case is to show nearby posts, so I don't need accuracy but can work in clusters/chunks with customizable radius, so using geohashes would theoretically work for me. Can't wait for that documentation