Hello, thanks for the answer,
I would prefer not to generate hundred (thousands ?) of coordinates for every indexed object, nor calling multiple times the api as it is a big performance / maintanability issue.
The indexed objects are users, from their settings, they can set their location and their “mobility”.
Mobility is actually “How far can you go”.
Because of our current logic, mobility is not linked to the user location (so not a radius of location) but can be any zone in the world.
So a user living in Paris, France can set is mobility to Spain, Europe, London, etc…
Within our search engine, you can filter by mobility, So if I ask something like “I want all users who could go up to Paris”
I expect it to display all users who set their mobility to a bounding box [containing / contained by / touching the bounding box] of Paris.
So these should match : France, Paris 10, Europe;
These shouldn’t: London, Lyon, Russia
I understand this seems a bit specific but I’m sure there is a lot of other use cases.