geopoint | Simple Javascript library to convert latitude | Map library

openrouteservice directions format is not identical to OSRM, so you cannot use OSRMRoadManager. If you really - really - want to use openrouteservice, you will have to develop corresponding openrouteserviceRoadManager.

Alternative: use one among the 3 routing services already accessible with OBP. Pros and cons here.

From the Firestore documentation on query limitations:

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

The way the inequality operators are implemented requires that you order on that field first. For the equality operator Firestore is able to do more on its own, for example combining information from multiple indexes in a so-called zig-zag-merge-join.

Security rules work on a document-level. Your code is trying to update the replies array in the users document, which is not allowed by any of your rules.

The match /replies in your rules applies to a replies subcollection under the users document. It has no effect on fields in the users document.

If you want the owner to update their entire document, and other signed in users to only update the replies field, you'll have to allow that in the rule on users.

Something like this:

To help the other: The documentation says : "limit() and orderBy() are not supported at the moment. limit() could be used to limit docs inside each hash individually which would result in running limit on all 9 hashes inside the specified radius. orderBy() is first run on geohashes in the library, hence appending orderBy() with another feild wouldn't produce expected results. Alternatively documents can be sorted on client side." At the bottom: here

In your scenario , the property is dynamic for each object , I would suggest you deserialize the root level as a dictionaryand then get the data you want .

Finally I found solution:

Most geoquery implementations for Firestore (like the one documented by Firebase itself) use geohash values to allow a range query on two values (lat/lon). While geohash values allow the geoquery to function, they are by definition imprecise, and they match items in a rectangular area.

When you look for documents in the green area, the range of geohashes may actually extend to include the red area:

To limit the returned items to the circular radius you want, you need to post-process the results as you're doing. In my testing the queries read about 5x more documents than needed, with some queries (typically the ones with even fewer results) reading up to 15x more. Based on that, your results seem to be about average.

If you're interesting in learning more, I recommend checking out the video of a talk I did a few years ago: Querying Firebase and Firestore based on geographic location or distance.

I think creating a new MyXFile class as you suggested might be the way to go. But as you've said you will need to override the properties you want to keep in hive. This code seems to be working as intended:

Change the location type in mappings "type": "geo_point" to "type": "geo_shape" and try