Geohash | GeoHash是目前比较主流实现位置服务的技术，用最简洁的Java实现GeoHash算法 | Map library

You haven't closed the bracket in the variable sql_location. It should be:

The .text attribute doesn't work here. To get the right data, it worked for me to use encode_contents(), just changing the definition of mydata like this:

Firestore has this limit on queries:

In a compound query, range (<, <=, >, >=) and not equals (!=, not-in) comparisons must all filter on the same field.

While not explicitly mentioned, start* and end* filters also fall under this limitation.

By employing a geohash, you already work around this limitation by combining the latitude and longitude in a single value that can be ordered and filtered. But by then adding a range filter on date, you are hitting the same limitation again.

The only ways to filter on latitude, longitude and date:

1. Use an equality filter for date, by storing them in a format that allows for that. For example if you want to allow filtering for a specific week, you could store the day in 2021-05-26 format, and do an in query on 7 values.
2. Find a way to combine the timestamps with the latitude and longitude in your own value type, similar to what a geohash already does for latitude and longitude. This means that you effectively have to be able to express how time relates to distance, so is typically only feasible in very well defined domains.

firebaser here

From our chat in the comments it seems that the withRadius: value is actually in meters, despite what the documentation says.

This is clearly not working as documented, so I filed a to update the docs. That change is coming in here.

The .child('key') in your code is not needed. So:

This is my Pin model in a struct:

Firestore can only filter on range on a single field. Or simpler: you can only have a single orderBy clause in your query.

What you are trying to do requires two orderBy clauses, one for geohash and one for createdOn, which isn't possible. If you were to need an equality check on a second field though, that would be possible as thstt doesn't require an orderBy clause.

What I'm wondering is whether you can add a field createdOnDay that contains just the day part of createdOn in a fixed format, and then perform an in on that with 7 values (for the days of the past week?

Maybe I shouldn't have posted the question so early, since it was a very simple error ...

The OAUTH_PROVIDERS variable should be an array!

Neither is pertinently better, but it's a typical space vs time tradeoff.

Adding the extra tags in the query adds some overhead there, but it saves you the (storage) cost for the additional index. So you're trading some small amount of runtime performance for a small amount of space/cost savings.

One thing to check is whether the query with tags can actually run on just the second index, as Firestore may be able to do a zigzag merge join. In that case you could only keep the second, smaller index and save the runtime performance of adding additional clauses, but then get a (similarly small) performance difference on the query where you do specify one or more tags.